IRC chat on #archlinux regarding ignored bug reports

17:50 < djmattyg> what is the recommended course of action when an Arch developer ignores a bug report for over 12 months?
17:50 < djmattyg> specifically this bug: https://bugs.archlinux.org/task/42467
17:51 < kadiro> lol djmattyg
17:52 < kadiro> the developer is on vacance :/
17:52  * kadiro or need donation :'(
17:53 < djmattyg> vacance?
17:53 < zerol0g1k> djmattyg: if its not in active development im sure you can talk to a TU about getting it orphanned. otherwise basically nothing
17:53 < jasonwry1n> given the moaning on flyspray, my sympathies are with the dev…
17:54 < djmattyg> zerol0g1k: the package is being updated. it was updated within the last 24 hours.
17:54 -!- jasonwry1n is now known as jasonwryan
17:55 < zerol0g1k> dj then its that dudes call how he wants to maintain the package.
17:55 < djmattyg> jasonwryan: the moaning on the bugtracker is because this whole situation is rather silly
17:55 < djmattyg> no rationale at all has been provided for having a separate php.ini file
17:55 < zerol0g1k> smile
17:55 < djmattyg> all it has done is create confusion and trouble
17:56 < djmattyg> zerol0g1k: fine, but that's no excuse for ignoring a bug report. the least he could do is post there explaining the rationale
17:56 < jasonwryan> maybe: but whining about “getting paid by the hour” is just bullshit
17:56 < kadiro> s/vacance/holiday
17:56 < jasonwryan> is it an upstream decision?
17:56 < djmattyg> jasonwryan: those were not my words. i'm sorry one person posted that. it doesn't invalidate the rest of the complaints.
17:57 < djmattyg> no. composer generally isn't packaged by other distros because it moves so fast, and is intertwined with a web service
17:57 < jasonwryan> so it is Pierre's call then
17:57 < djmattyg> so how should I get in contact with him?
17:58 < jasonwryan> you have: the bug report is assigned
17:58 < djmattyg> he's ignored it for over a year, so clearly that isn't working.
17:58 < djmattyg> which is the whole point of my coming here. not to be judged by other people, but for a simple Q&A on how developers should be contacted
17:58 < jasonwryan> well, he clearly intends on continuing to ignore it, I guess
17:58 < jasonwryan> no-one is judging you
17:59 < djmattyg> if no one was judging me then it would have been a simple answer to the simple question of how developers should be contacted when they ignore bug
                  reports
17:59 < djmattyg> instead I had to spend five minutes explaining why it was important that the specific instance i'm dealing with matters in the first place
18:00 < jasonwryan> if you don't agree with the packaging decision (and there are some I don't), use ABS/aps
18:00 < jasonwryan> s/aps/asp
18:01 < djmattyg> okay, so what should I do about bug reports that aren't to do with opinionated packaging decisions, should this issue arise in the future?
18:01 < jasonwryan> all of the devs are volunteers; live with it is my advice
18:03 < djmattyg> I don't think i'm asking much for a bug report to be responded to when it's been open for more than a year, and the dev in question has had plenty of
                  time to update the affected package many times since then
18:04 < jasonwryan> djmattyg: maybe: but Arch is a DIY distro: it is trivial to package it yourself and get on with your life
18:05 < djmattyg> again, not really the point if this was affecting a more important package