maintainer not responding
in [Debian]
|
From: Patrick Ouellette on 6 Aug 2010 09:50 I think you may be missing the poing a bit. A 'TODO' list is nice, but what is stopping YOU from forwarding the information to upstream or checking the upstream project to see if they know about the issue? What SPECIFIC package(s) in the list do YOU use, and what SPECIFIC issues are YOU having? I'm not saying all the bugs don't need to be addressed, but it is a lot easier to motivate people when someone has a specific need rather than picking a developer's package set and complaining about every one of the packages with a bug report. Again I ask YOU what efforts have YOU made to contact the maintainer? Pat By the way, your Google email link doesn't work for me to look at the referenced message. On Thu, Aug 05, 2010 at 02:38:42PM -0700, Jeremiah Mahler wrote: > > I reviewed the outstanding bugs shown in > [https://mail.google.com/mail/?shva=1#label/debian-lists/12a43a9b406864ec] > and below is a short summary of what I think needs to be done next. > The 'TODO' sections indicate something that needs to be done by a > Debian maintainer (packaging, forwarding, etc). > The 'TODO_USER' sections indicate something that could be done by a > regular user. > > #406051 qpopper corrupts mailbox when quota exceeded > TODO: forward upstream? > > #437746 libgtkglext1: Program exit via window manager window close > crashes xserver > WAITING: message sent asking for info regarding video driver. > > #537575 uninstallable in unstable > seems to be fixed in current version, installed OK > TODO: close? > > #548383 qpopper: The PAM configuration file does not fit to the > latest libpam-modules package > TODO: patch needs to be applied and checked > > #573522 qpopper: error msg.: fetchmail: Query status=3 (AUTHFAIL) > Some difference between lenny and squeeze causes qupopper to fail. > TODO: Someone familiar with qpopper may have some insight. > Or if the user provided a more detailed description of how to > reproduce this would help. > > #242944 qpopper: RFC incompliant behavior > TODO: forward upstream > > #275918 qpopper ignores -R or set reverse-lookup = false config item. > TODO: report is from 2004, check if bug still present in latest > version. > > #323492 libgtkglext1-dev: example can segfault > TODO: forward upstream > > #337022 libgtkglext1: bug somewhere near gdk_gl_get_proc_address() > in gdkglquery-x11.c:408 > reproducible bug > TODO: forward upstream > > #406687 GLXBadContext error happening only with i810 driver with DRI > TODO: forward upstream? > > #471483 not available on ppc > Is libgtkglext1 available for ppc? > According to > [http://packages.debian.org/search?keywords=libgtkglext1&searchon=names&suite=stable§ion=all] > it looks like it is available. > TODO: bug is from 2008, it seems powerpc is available now. close bug? > > #516088 E: qpopper: subprocess post-removal script returned error > exit status 1 > It seems to be working now. > WAITING: Message sent asking user to verify if problem is still present. > > #518514 pidgin-mpris: Please remove bmpx dependency > TODO: update package to remove obsolete dependency > > #587984 Outdated API - please update to 0.62 > TODO: update package for new upstream version > > #486579 qpopper: debian/watch fails to report upstream version > uscan of qpopper says it needs a new version. > TODO_USER: verify problem is still present > > #529137 qpopper: please upgrade your watch file > similar to bug#486579 > TODO: merge with #486579? > > #558512 Missing autoreconf to fix 554821 or similar bugs in the future > Detailed description of what needs to be fixed. > TODO: update package for autoreconf > > #590543 audacious-dumb: remove shared library linking > Has patch to removed dependency on libdumb.so > TODO: check if removing dependency makes sense, > update package if it does. > -- Patrick Ouellette pat(a)flying-gecko.net ne4po (at) arrl (dot) net Amateur Radio: NE4PO What kind of change have you been in the world today? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100806132900.GA6188(a)flying-gecko.net
From: Osamu Aoki on 6 Aug 2010 09:50 Hi, I thank your efforts but I have to remind you that you need to find right way to make change in Debian. None of us are paid to be full time. There are many loose ends. Reporting to wrong ML is not the best action. What you are telling us is: 1. packages maintained by nenolod(a)sacredspiral.co.uk is not getting good attention. (Unfortunately, many are there...) 2. You are not the one made patches etc. and no particular technical discussion is intended here. On Thu, Aug 05, 2010 at 02:38:42PM -0700, Jeremiah Mahler wrote: > I reviewed the outstanding bugs shown in > [https://mail.google.com/mail/?shva=1#label/debian-lists/12a43a9b406864ec] .... This debian-user(a)lists.debian.org ML is not the place to do this. I suggest you to do: 1. Send an additional mail to a bug with undeniable suggestion which demands response nicely to check whether the maintainer is active or not. 2. If you get no response, follow procedures described in: http://www.debian.org/doc/developers-reference/beyond-pkging.html#mia-qa Thanks again, Osamu -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100806132358.GA3654(a)debian.org
From: Jeremiah Mahler on 6 Aug 2010 15:40 Patrick, On Fri, Aug 6, 2010 at 6:29 AM, Patrick Ouellette <pat(a)flying-gecko.net> wrote: > I think you may be missing the poing a bit. A 'TODO' list is nice, > but what is stopping YOU from forwarding the information to upstream > or checking the upstream project to see if they know about the issue? > What was stopping me was the assumption that forwarding bugs could only be done by a maintainer. But it makes sense that there is no reason why I could not discuss these bugs with the upstream authors and report back. > What SPECIFIC package(s) in the list do YOU use, and what SPECIFIC > issues are YOU having? > > I'm not saying all the bugs don't need to be addressed, but it is a > lot easier to motivate people when someone has a specific need rather > than picking a developer's package set and complaining about every one > of the packages with a bug report. > I should focus my efforts on a micro rather than a macro level. > Again I ask YOU what efforts have YOU made to contact the maintainer? I have not attempted to contact the maintainer in any way other than through bug reports. And the bug reports as well as these messages are sent to the email for the maintainer. Is there some other method I should use? > > Pat > > By the way, your Google email link doesn't work for me to look at > the referenced message. > Sorry about that. Here is the correct link. http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=nenolod%40sacredspiral..co.uk > On Thu, Aug 05, 2010 at 02:38:42PM -0700, Jeremiah Mahler wrote: >> >> I reviewed the outstanding bugs shown in >> [https://mail.google.com/mail/?shva=1#label/debian-lists/12a43a9b406864ec] >> and below is a short summary of what I think needs to be done next. >> The 'TODO' sections indicate something that needs to be done by a >> Debian maintainer (packaging, forwarding, etc). >> The 'TODO_USER' sections indicate something that could be done by a >> regular user. >> >> #406051 qpopper corrupts mailbox when quota exceeded >> TODO: forward upstream? >> >> #437746 libgtkglext1: Program exit via window manager window close >> crashes xserver >> WAITING: message sent asking for info regarding video driver. >> >> #537575 uninstallable in unstable >> seems to be fixed in current version, installed OK >> TODO: close? >> >> #548383 qpopper: The PAM configuration file does not fit to the >> latest libpam-modules package >> TODO: patch needs to be applied and checked >> >> #573522 qpopper: error msg.: fetchmail: Query status=3 (AUTHFAIL) >> Some difference between lenny and squeeze causes qupopper to fail. >> TODO: Someone familiar with qpopper may have some insight. >> Or if the user provided a more detailed description of how to >> reproduce this would help. >> >> #242944 qpopper: RFC incompliant behavior >> TODO: forward upstream >> >> #275918 qpopper ignores -R or set reverse-lookup = false config item. >> TODO: report is from 2004, check if bug still present in latest >> version. >> >> #323492 libgtkglext1-dev: example can segfault >> TODO: forward upstream >> >> #337022 libgtkglext1: bug somewhere near gdk_gl_get_proc_address() >> in gdkglquery-x11.c:408 >> reproducible bug >> TODO: forward upstream >> >> #406687 GLXBadContext error happening only with i810 driver with DRI >> TODO: forward upstream? >> >> #471483 not available on ppc >> Is libgtkglext1 available for ppc? >> According to >> [http://packages.debian.org/search?keywords=libgtkglext1&searchon=names&suite=stable§ion=all] >> it looks like it is available. >> TODO: bug is from 2008, it seems powerpc is available now. close bug? >> >> #516088 E: qpopper: subprocess post-removal script returned error >> exit status 1 >> It seems to be working now. >> WAITING: Message sent asking user to verify if problem is still present. >> >> #518514 pidgin-mpris: Please remove bmpx dependency >> TODO: update package to remove obsolete dependency >> >> #587984 Outdated API - please update to 0.62 >> TODO: update package for new upstream version >> >> #486579 qpopper: debian/watch fails to report upstream version >> uscan of qpopper says it needs a new version. >> TODO_USER: verify problem is still present >> >> #529137 qpopper: please upgrade your watch file >> similar to bug#486579 >> TODO: merge with #486579? >> >> #558512 Missing autoreconf to fix 554821 or similar bugs in the future >> Detailed description of what needs to be fixed. >> TODO: update package for autoreconf >> >> #590543 audacious-dumb: remove shared library linking >> Has patch to removed dependency on libdumb.so >> TODO: check if removing dependency makes sense, >> update package if it does. >> > > -- > > Patrick Ouellette pat(a)flying-gecko.net > ne4po (at) arrl (dot) net Amateur Radio: NE4PO > > What kind of change have you been in the world today? > -- Jeremiah Mahler jmmahler(a)gmail.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/AANLkTimFBN-_qJOnG9V9Zx2pLYdWeRkoQ1BBZ36f+cob(a)mail.gmail.com
From: Andrei Popescu on 9 Aug 2010 05:30 On Vi, 06 aug 10, 12:36:17, Jeremiah Mahler wrote: > Patrick, > > On Fri, Aug 6, 2010 at 6:29 AM, Patrick Ouellette <pat(a)flying-gecko.net> wrote: > > I think you may be missing the poing a bit. A 'TODO' list is nice, > > but what is stopping YOU from forwarding the information to upstream > > or checking the upstream project to see if they know about the issue? > > > > What was stopping me was the assumption that forwarding bugs could > only be done by a maintainer. But it makes sense that there is no reason > why I could not discuss these bugs with the upstream authors and report back. Bugs can be manipulated by anyone, not just the maintainer. > > What SPECIFIC package(s) in the list do YOU use, and what SPECIFIC > > issues are YOU having? > > > > I'm not saying all the bugs don't need to be addressed, but it is a > > lot easier to motivate people when someone has a specific need rather > > than picking a developer's package set and complaining about every one > > of the packages with a bug report. > > > > I should focus my efforts on a micro rather than a macro level. > > > Again I ask YOU what efforts have YOU made to contact the maintainer? > > I have not attempted to contact the maintainer in any way other than through > bug reports. And the bug reports as well as these messages are sent to the > email for the maintainer. Is there some other method I should use? Your "quest" seems directed towards a particular Maintainer. My guess is you are probably more familiar with the packages on you own machine. Try rc-alert and/or wnpp-alert (finding the package containing these is left as an exercise to the potential contributor). Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Jeremiah Mahler on 10 Aug 2010 01:40 Andrei, On Mon, Aug 9, 2010 at 2:22 AM, Andrei Popescu <andreimpopescu(a)gmail.com> wrote: > On Vi, 06 aug 10, 12:36:17, Jeremiah Mahler wrote: >> Patrick, >> >> On Fri, Aug 6, 2010 at 6:29 AM, Patrick Ouellette <pat(a)flying-gecko.net> wrote: >> > I think you may be missing the poing a bit. A 'TODO' list is nice, >> > but what is stopping YOU from forwarding the information to upstream >> > or checking the upstream project to see if they know about the issue? >> > >> >> What was stopping me was the assumption that forwarding bugs could >> only be done by a maintainer. But it makes sense that there is no reason >> why I could not discuss these bugs with the upstream authors and report back. > > Bugs can be manipulated by anyone, not just the maintainer. > >> > What SPECIFIC package(s) in the list do YOU use, and what SPECIFIC >> > issues are YOU having? >> > >> > I'm not saying all the bugs don't need to be addressed, but it is a >> > lot easier to motivate people when someone has a specific need rather >> > than picking a developer's package set and complaining about every one >> > of the packages with a bug report. >> > >> >> I should focus my efforts on a micro rather than a macro level. >> >> > Again I ask YOU what efforts have YOU made to contact the maintainer? >> >> I have not attempted to contact the maintainer in any way other than through >> bug reports. And the bug reports as well as these messages are sent to the >> email for the maintainer. Is there some other method I should use? > > Your "quest" seems directed towards a particular Maintainer. My guess is > you are probably more familiar with the packages on you own machine. Try > rc-alert and/or wnpp-alert (finding the package containing these is left > as an exercise to the potential contributor). I never knew about those programs but they look great for finding bugs relevant to my system. Great tip! > > Regards, > Andrei > -- > Offtopic discussions among Debian users and developers: > http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBCAAGBQJMX8jhAAoJEHNWs3jeoi3pFNEH/3/efAxrPjFZqwpM8w76QTLB > yAtYhvrZhPaHTn9mnG7pK01iPfDU87qksJBdtD0YBViDH8WZ9JTr+idd/WxVUnLu > YL89ms4DjhZXE8o6vb0MSbEfMSvwRLjaB0WP6qksSTUnaeUmTDJzzhdn7bSBx0ay > XQTgycqc2V0wq8P1OxY9lSU8YKCkla06zRjHw4ZtlCBWkzyuDMiR00HCv4kmwazL > UD5YT9dIy/fN/MZxwPegDk+DYbVrC7EecQv4orUi64Bri6DisdNjhqYciyErJ7ru > gmDu0y1haKtaB57yDmVEf8tpf+rxmiLpfEbKfnszpSQpAx3rc416h8GA1UU6AQ4= > =7Pwe > -----END PGP SIGNATURE----- > > -- Jeremiah Mahler jmmahler(a)gmail.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/AANLkTin12JFY7SEvYs2oyGKte7Vh4xuBn2y_zCxbgatX(a)mail.gmail.com
First
|
Prev
|
Pages: 1 2 Prev: Popcon usage (online tool) Next: cciss module problem with smart array 642 in lenny |