Arch Linux

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#40725 - [libreoffice] [libreoffice-fresh] package names differ from upstream

Attached to Project: Arch Linux
Opened by Harry Kashouli (kcy29581) - Friday, 06 June 2014, 02:59 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 June 2014, 14:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Upstream has the following versions for LibreOffice:
Stable - 4.1.6
Fresh - 4.2.4
Development - 4.3.0 (both pre-release and a development candidate)

In Arch, the packages/groups are named & install:
libreoffice -> installs 4.2.4
libreoffice-fresh -> 4.3.0 (listed as pre-release and development with upstream)

Issue:
Users may search for "fresh" and not check on the upstream page which version they deem stable, causing confusion.

Suggestion:
If Arch will use "fresh" in the names, they should match the upstream version/definition. If we want to have the development version, the packages/groups need to be labelled *-development.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 10 June 2014, 14:23 GMT
Reason for closing:  Not a bug
Comment by Andrew Gaydenko (student975) - Friday, 06 June 2014, 09:20 GMT
Yes, I also was confused with "fresh" and was forced to go to upstream site to understand reality :)
My suggestion is just to rename "-fresh" to "-dev" (keeping 4.2.4 as it is).
Comment by Andreas Radke (AndyRTR) - Friday, 06 June 2014, 13:17 GMT
The plan is to use the old libreoffice pkg for upstream "-stable" branch and the libreoffice-fresh for upstream "fresh" release branch.

Right now we offer 4.2.4 in the "old" pkg that is the upstream current "fresh" release. We will stick with
4.2.x then 4.3.0 will be officially released as new "fresh" branch and will rename the old one to -stable. Then we will be in sync with upstream.

It's not our plan to use -fresh pkg for developement releases. That's right now only for preparing the new release.
Comment by Harry Kashouli (kcy29581) - Monday, 09 June 2014, 21:26 GMT
Sounds great, thanks for the update.

Loading...