Can I "vote" for updating an outdated package?
Hi there, My actual problem is that strongswan 5.9.10 has a bug [1] that affects interoperability with Apple iOS client. Upstream has a fix [2] for it which should be available in 5.9.11, but our package is flagged out-of-date on 12 June, over a month ago; well this is not a terribly long time, but since such cases do not qualify as bugs, I don't know if things are going well. Is there some kind of "voting" system that I can click to inform our TUs, to help prioritize updating packages in such cases? [1] https://github.com/strongswan/strongswan/discussions/1613 [2] https://github.com/strongswan/strongswan/commit/3d0d3f5d028a0c630f89cb4fec5b...
Hello, I would like to point out in most cases, you will just need to wait for the maintainer to get time to update the packages, they are informed when the package is flagged out of date that they need to update the package, all maintainers have their own priorities. For feature updates, or small fixes these are often not the priority, you can always email the TU and ask, however some TUs might not be so open to having people email them requesting them to update x and y packages, especially with many Arch Staff having long backlogs, so your email will probably not even be seen for a long period of time until they have caught up on all their emails. As this is a "major" issue, the best thing you can do is post the issue on the bug tracker (if it has not already been posted there) with the solution to the problem (which is bump the package to the latest version). This tends to get the package more noticed, and therefore prioritised. But at the end of the day, you just have to wait, there are tons of people waiting for packages to be updated, and maintainers can't bump a package for one person and not another. The following is extremely useful: - Posting bugs with the software, whether a bug with upstream (please link the upstream bug report if it exists within the arch bug report), or a bug with the package (such as files not being installed into the right locations, or missing dependencies etc). - Maintain packages on the AUR, this is the best way to work your way up to eventually becoming a TU (package maintainer) in which you can help out on the official repository, everyone has got to start somewhere. I know it sounds stupid that you are asking for something to be fixed, and I am telling you ways to contribute, but if you want to make a difference, that is the only way (contributing). TL;DR report the bug on the arch bug tracker linking the github discussion and commit you have sent in this email within the bug report (only do this if the bug has not already been filed), and then just wait. Hope this helps, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Sorry for the noise, I just wanted to address the question, which I forgot to answer. No there is no "vote" functionality, follow the advice in the previous email (ensuring a bug has been submitted, and waiting). Hope this answers your question, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On Mon, 24 Jul 2023 04:12:31 +0100 Polarian <polarian@polarian.dev> wrote:
Hmm but our bug reporting guidelines [1] says "A bug already fixed upstream but not in Arch because the package is not up-to-date" does not count as a bug, that's why I started in this list... [1] https://wiki.archlinux.org/title/Bug_reporting_guidelines#Reasons_for_not_be...
Hello,
I was not aware of this, I do not remember who it was, but I remember being told by one of the TUs to report issues to the bug tracker so that the maintainer was aware that a bump in the package would patch major bugs. Either that advice was wrong, the advice is controversial (as in, TUs opinion on it differ), or the ArchWiki simply does not reflect reality. I guess wait for a comment from a TU on this one. It is also highly likely that I am just an idiot and took the advice of one TU the wrong way, I am known to do that :/ Sorry for misinformation, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
participants (2)
-
Carl Lei
-
Polarian