Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61378 - [tribler] It seems version 7.2.0_exp1 is experimental release, 7.1.3 is the latest

Attached to Project: Community Packages
Opened by grizzlyuser (grizzly) - Sunday, 13 January 2019, 12:00 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 29 January 2019, 22:56 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Filipe Laíns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

According to tribler GitHub releases page, 7.1.3 is the latest release, and 7.2.0_exp1 is previous experimental release:
https://github.com/Tribler/tribler/releases

According to the Arch Wiki:
> Arch Linux strives to maintain the latest stable release versions of its software

So it seems that the package should be marked out of date as the experimental release obviously cannot be considered "stable". But I'm not sure about that, and that's why would like to ask a confirmation here. In case this is correct understanding, it is also not clear how pacman will handle the upgrade of this package, since it would look like a downgrade for him.
This task depends upon

Closed by  Filipe Laíns (FFY00)
Tuesday, 29 January 2019, 22:56 GMT
Reason for closing:  Won't fix
Comment by Eli Schwartz (eschwartz) - Sunday, 13 January 2019, 18:45 GMT
It's a valid question why we are packaging the experimental version of anything.

However, it is not older than the stable release. It was released on a different development track; notice the project's v7.1.3 release is on the "release-7.1.3" branch while v7.2.0-exp1 is on "devel". This development release may have been released before the latest stable, but that just means that some fixes were cherry-picked to make a stable backport release.
Comment by grizzlyuser (grizzly) - Monday, 14 January 2019, 20:06 GMT Comment by grizzlyuser (grizzly) - Wednesday, 16 January 2019, 11:39 GMT Comment by Eli Schwartz (eschwartz) - Wednesday, 16 January 2019, 18:16 GMT
Stop that. We don't need constant updates on which version number we aren't currently packaging.
Comment by Marek Einla (mareke) - Tuesday, 29 January 2019, 20:17 GMT
Is this package up to date at the moment?
Comment by Filipe Laíns (FFY00) - Tuesday, 29 January 2019, 22:56 GMT
The "experimental" release is still stable so I feel fine having it in the repos, if you have any stability issue please report it and I'll downgrade the package.

Loading...