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#78034 - [nextcloud] x.0.0 version has slipped into arch

Attached to Project: Community Packages
Opened by Tormod Volden (tormod) - Wednesday, 29 March 2023, 08:43 GMT
Last edited by David Runge (dvzrv) - Thursday, 30 March 2023, 14:32 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
nextcloud x.0.0 is not considered stable but has been released into arch (again).

There was a note in the packaging files. Has it been removed intentionally?
"NOTE: do not package x.0.0 versions as they are considered beta"

References:
* https://bugs.archlinux.org/task/69710
* https://bugs.archlinux.org/task/73714

Additional info:
* nextcloud 26.0.0-1

Steps to reproduce:
* Upgrade to latest nextcloud in arch
* You now have upgraded to 26.0.0 which upstream does not consider safe for upgrades
* Prepare yourself for hours of fixing beta issues on your installation
This task depends upon

Closed by  David Runge (dvzrv)
Thursday, 30 March 2023, 14:32 GMT
Reason for closing:  Not a bug
Additional comments about closing:  We follow https://github.com/nextcloud/server/wiki /Maintenance-and-Release-Schedule
Comment by Toolybird (Toolybird) - Wednesday, 29 March 2023, 20:48 GMT
> Has it been removed intentionally?

Yes, obviously [1]. Circumstances do change over time and the PM's have made a conscious decision here to upgrade. Is it not working for you?

[1] https://github.com/archlinux/svntogit-community/commit/499604cef51f00c84f1d60f19b8843d9f9e5f5a1
Comment by Tormod Volden (tormod) - Wednesday, 29 March 2023, 22:02 GMT
I cannot tell from that commit whether it was an informed decision or a misunderstanding. Until I have proof from upstream that they have (intentionally) changed their policy about x.0.0 releases, I will not be convinced. Upstream is also a nightmare when it comes to release management and communication (see e.g. https://github.com/nextcloud/server/issues/31198) so I would be doubly careful.

> Is it not working for you?

Thank you very much, I have nextcloud safely ignored in pacman.ini :) Surely not upgrading before any x.0.1 is out. Just take a look at the closed issues in the bug tracker on x.0.0 releases, it is usually a lot of "fun". My biggest remaining problem is that any, say, 25.0.5 coming out before 26.0.1 will not be packaged in arch.
Comment by David Runge (dvzrv) - Thursday, 30 March 2023, 14:32 GMT
@tormod: We follow upstream's maintenance and release schedule [1].

Packages are in testing for a while before releasing them into the stable repositories and have received signoffs from users.
Any other information in regards to what an upstream release is considered as I would personally consider hearsay, unless it comes from upstream directly (that's also why I removed that comment again).
We have testing repositories for a reason.

[1] https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule

Loading...