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
Opened by Hellracer (hellracer) - Monday, 14 November 2016, 22:32 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 15 November 2016, 11:35 GMT
|
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
I mean WTF? It's perfectly fine to build rc packages *on the -testing repository*.
https://github.com/darktable-org/darktable/releases/download/release-2.0.7/darktable-2.0.7.tar.xz.asc