Packaging Request #3165
prusa-slicer 2.4.0 is out , please to update it
0%
Description
- steps to reproduce:
eg: 1) # pacman --debug -Syyuu base your-freedom # try me first (systemd)
or # pacman --debug -Syyuu base your-freedom your-initfreedom # try me first (openrc)
2) # pacman -S foo-openrc
3) $ foo --print hello
- expected result:
eg: i expected foo to print hello
- actual result:
eg: instead, it prints: "ERROR: invalid argument (Is the 'foo' daemon running?)"
History
Updated by oaken-source over 2 years ago
- Status changed from open to wont-fix
Please don't use this bugtracker to report out-of-date packages.
Instead, to report parabola-packaged packages out of date, please use the "Flag out-of-date" option on the package overview on www.parabloa.nu
Updated by bill-auger over 2 years ago
generally, 'out-of-date' are not bugs, nor packaging requests - there could be a category for them on the bug tracker; but there is not, intentionally - for existing packages, which could be upgraded to a new upstream release, the 'out-of-date' flags on the packages website is the proper mechanism, for users to indicate that
that alone, justifies closing this ticket; but i will make an exception, to explain/address the request, for the sake of documentation/education/pedantry
the standard arch 'prusa-slicer' is version 2.3.3 - the parabola mission statement promises to keep in sync with arch, whenever possible; so 2.3.3 is the correct parabola version today - there are no open bug reports for that package (arch nor parabola); so 2.3.3 is the only version, which parabola users should want to use today - new upstream releases of that software are not significant to parabola; because that package is managed exclusively by arch
the package is flagged 'out-of-date'; so the new upstream release is probably known to the arch maintainer already - the arch package is only one month old though; its upgrade is probably not urgent - generally, the package maintainer knows best, how to maintain each package - new upstream releases are not always desirable, for the sanity of the OS as a whole
the most important misconception to clarify though, is that upstream releases are generally not interesting to any typical user of the OS - the arch 'out-of-date' flags mechanism, is not a common feature of distros - it mainly indicates that arch has a high percentage of atypical expert users, who are willing to help the maintainers - ie: most arch and parabola users can simply ignore the versions of everything - they are truly irrelevant/inconsequential to the experience of most users
in summary:- out-of-date packages are not packaging requests for the bug tracker
- users may notify package maintainers of out-of-date packages, via the packages website
- the package maintainer knows best, how to maintain each package
- most packaging decisions are made by arch
- parabola keeps in sync with arch software
- parabola will normally not over-ride arch's packaging decisions
- newer is not always better
- it is wiser to prefer "better", where ever that differs from "newer"
- the 'out-of-date' flags are non-essential; but purely informative (an "advanced nerd thing")
- most users of most distros, are rarely affected by versions of anything, so can ignore versions
- the previous point is true, precisely because the packager may decide that the newest upstream release, is not the best version for the system, as it is, at the time