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#51834 - [darktable] Stop using Beta or RC versions

Attached to Project: Community Packages
Opened by Hellracer (hellracer) - Monday, 14 November 2016, 22:32 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 15 November 2016, 11:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Currently the darktable package is available as version 2.2.0rc0-1. I really know that archlinux is providing bleeding edge software but why the hell can't you stick to stable upstream releases in the official repositories? It now happened several times that beta or rc versions had been released as well as the usage of autogenerated tar-balls from github.
The authors of darktable are always providing a warning not to use the autogenerated tar-balls and as always don't use beta versions on production.
Using the rc version is upgrading the meta data structure of the database of darktable. You can not roll back without a backup.

Stop releasing archlinux packages in the official repositories if you are incapable to verify that these are stable versions! Roll back current release to version 2.0.7 which is current stable.
See https://www.darktable.org/2016/11/darktable-2-2-0rc0-released/ for rc release notes and always stick to https://www.darktable.org/news/ to get the announcement of new stable releases.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 15 November 2016, 11:35 GMT
Reason for closing:  Fixed
Comment by Philipp Schmidt (hefeweiz3n) - Tuesday, 15 November 2016, 07:58 GMT
Agreed. I flagged the package "out of date" (not the correct usage I'm afraid) and told the maintainer the exact same thing you did here. People who really need the new functionality of darktable 2.2 can use the aur git package or create a custom one themselves, but the repos shouldn't contain RC packages when there is a perfectly good stable version out there.
Comment by François Guerraz (kubrick) - Tuesday, 15 November 2016, 09:00 GMT
I was about to open a bug report myself...
I mean WTF? It's perfectly fine to build rc packages *on the -testing repository*.
Comment by Levente Polyak (anthraxx) - Tuesday, 15 November 2016, 11:26 GMT
you need to bump the epoch
Comment by Levente Polyak (anthraxx) - Tuesday, 15 November 2016, 11:30 GMT
PS: in the same step you could include the upstream .asc signature.
https://github.com/darktable-org/darktable/releases/download/release-2.0.7/darktable-2.0.7.tar.xz.asc

Loading...