You are not logged in.
Hey guys,
The josm package is out of date for more than 7 months, meaning it missed 7 major updates.
I tried to report that a package seems to be orphaned by the maintainer via a bug, which got closed, because “the package is out of date”?!
So I created some month ago an updated package for josm in the AUR, called “josm-stable” – which now got deleted, because “it's a duplicate”.
So I was wondering, what's the right approach to get this package maintained and updated – if we're not supposed to report unmaintained packages via the bugs and not supposed to make supported versions in the AUR?
Thanks in advance for advice!
Offline
Similar case is the package npm, which is flagged out-of-date for 4 months now – and is a dependency for one of my AUR packages.
Last edited by RubenKelevra (2023-02-26 21:52:02)
Offline
More than half of the packages in the official repos are currently out of date.
https://archlinux.org/packages/?sort=-l … ed=Flagged
The maintainers will probably update as soon as they they have time.
You can always build an updated package on your own, but it is forbidden to upload it to the AUR to avoid duplicates, as stated.
Edit: Spinach error corrected
Last edited by schard (2023-02-27 00:11:03)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
More than half of the packages in the official repos are currently out of date.
711 out of 14008
Go back to school!
Offline
RubenKelevra:
You may contact the maintainer and ask, how you might help.
However, often this is caused by newer versions being broken or incompatible with other packages. Arch may be bleeding edge, but it is not meant to break stuff.
Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
Missed a digit there. But the perceived number of ~1400 should have ringed a bell, since that's obviously a way too small number. *squinting for my glasses*
Inofficial first vice president of the Rust Evangelism Strike Force
Offline