Bug 26771 - [Update Request] pidgin 2.14.1
Summary: [Update Request] pidgin 2.14.1
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://pidgin.im/posts/2020-06-2.14....
Whiteboard: MGA7-64-OK
Keywords: validated_backport
Depends on:
Blocks:
 
Reported: 2020-06-11 16:59 CEST by Zombie Ryushu
Modified: 2021-03-22 22:26 CET (History)
4 users (show)

See Also:
Source RPM: pidgin-2.13.0-4.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Zombie Ryushu 2020-06-11 16:59:03 CEST
The changes for 2.14.1 are small but important. There were some issues with the Windows installer that made it impossible to install 2.14.0 and the Mercurial revision in the About box was displaying “unknown”.
Comment 1 Lewis Smith 2020-06-11 20:05:07 CEST
Thank you for the hint, but I admit that having followed up the 2.14.0 & 2.14.1 announcements, there is little to justify updating this for Mageia 7.

I imagine we should have it for the emerging Mageia 8, to be nominally up-to-date. They talk of a future Pidgin 3.
The SRPM has various maintainers, so assigning globally; CC'ing Shlomi as the registered person.

Source RPM: pidgin => pidgin-2.13.0-4.mga7.src.rpm
CC: (none) => shlomif
Assignee: bugsquad => pkg-bugs

David Walser 2020-06-12 20:57:53 CEST

Component: RPM Packages => Backports

Comment 2 David Walser 2020-06-12 20:59:53 CEST
This would be a backport of course.  2.14.0 announcement:
https://pidgin.im/posts/2020-06-2.14.0-released/
Comment 3 Aurelien Oudelet 2020-09-20 17:29:03 CEST
Hi,
Thanks for requesting a backport to Mageia 7 for packages updated in Cauldron.

According to our current backports policy:
https://wiki.mageia.org/en/Backports_policy

- Package maintainers are under no obligation to provide backports for the packages they maintain (whereas a maintainer should provide updates to the stable releases for packages he/she maintains).
- Another packager can step in and provide backports provided he contacts maintainer about this. He must then keep the maintainer informed when working on it.
- The maintainer can refuse that some packages be backported. If hard conflicts arise (eg. the maintainer vs all other packagers), we can refer to the council.
- Packager (maintainer or not) who will submit backport will also have to provide security and bug updates if necessary.

Packager/Maintainer: If you are working on this backport request, please change status to "Assigned". Feel free to Close this if you think it is against current Backports policy.

Reporter: Your request is under investigations.
In the meantime, we suggest look for Appimage or Flatpak version of this.
Comment 4 Nicolas Lécureuil 2021-03-11 09:42:38 CET
available in backports_testing.


just the console app is missing for the moment.

I will see in a second step to fix this ( but this won't prevent tests :) )

Assignee: pkg-bugs => qa-bugs
CC: (none) => mageia

Comment 5 Herman Viaene 2021-03-18 15:29:17 CET
MGA7-64 MATE on Peaq C1011
No installation issues
Installed current version on my desktop, and could define on both a  new IRC account and send IM between the two.
OK

CC: (none) => herman.viaene
Whiteboard: (none) => MGA7-64-OK

Comment 6 Thomas Andrews 2021-03-20 18:08:46 CET
Validating. Assuming the "second step" in Comment 4 involves a second backport. If that is in error, please remove the validation.

CC: (none) => andrewsfarm
Keywords: (none) => validated_backport

Comment 7 Thomas Backlund 2021-03-22 22:26:37 CET
moved

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.