Bug#307461: qa.debian.org: displays "GPG key id not found" for ALL developers
Package: qa.debian.org Severity: normal Since a couple of days, qa.debian.org/developer.php displays in red "GPG key id not found!" under general information, for all developers. I guess something's broken in the routine that looks this information up. Regards, Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307461: qa.debian.org: displays "GPG key id not found" for ALL developers
On Tue, May 03, 2005 at 11:43:36AM +0200, Thijs Kinkhorst wrote: > Package: qa.debian.org > Severity: normal > > > Since a couple of days, qa.debian.org/developer.php displays > in red "GPG key id not found!" under general information, > for all developers. I guess something's broken in the routine > that looks this information up. > You betcha. http://lists.debian.org/debian-qa/2005/05/msg2.html regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looving lesbians
Yo, it's me Little girls can't stop to touch themselves http://xcd.alizator.com/ajp/sbs.html Get off : http://rum.nonpropy.com/ajp/_ep.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Bug#287949: acknowledged by developer (Re: Bug#287949:ndiswrapper-modules depends on ndiswrapper-utils; so shouldndiswrapper-source)
Erm, this is what I now get - source compiles fine against my shiny new kernel (2.6.11.8), and resulting ndiswrapper-modules will not install because of missing dependency ndis-utils. apt-get install ndis-utils gives me ndis-utils AND kernel-image-2.6.8.2-386, which I don't need on my machine. After that, ndiswrapper-modules I built will install fine (dependencies met) Try to remove kernel-image-2.6.8-386, and I lose ndis-utils, yada yada... maybe y'all could talk to each other? It's a pain to carry around a kernel I don't need or want just to run a silly little wireless card... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#307488: please upgrade to newer libtool (libtool1.4 being removed)
Martin Michlmayr <[EMAIL PROTECTED]> writes: > libtool1.4 is no longer maintained and will be removed from the > archive after sarge is released. Please upgrade your package to use a > newer, ideally the latest, version of libtool, and make sure this gets > integrated in upstream. What about the fact that there are packages which still need it? You can't rely on reverse depends, because libtool is often used on the developer's system and need not show up on Build-Depends. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#307488: please upgrade to newer libtool (libtool1.4 being removed)
On Tue, 03 May 2005, Thomas Bushnell BSG wrote: > > libtool1.4 is no longer maintained and will be removed from the > > archive after sarge is released. Please upgrade your package to use a > > What about the fact that there are packages which still need it? You They are broken right now, and will have to be fixed, since libtool 1.4-generated breakage will not be tolerated in etch. > can't rely on reverse depends, because libtool is often used on the > developer's system and need not show up on Build-Depends. We will fix those as we find them during etch. I am sure we will build quite the upgrading-and-fixing-libtool-builds knowledge base during it, so it should not be too painful. I am far more worried with other things we will have to tack heads on, such as our known difficulty with avoiding fucked up linking of different incompatible ABIs in the same lib/dso/executable. Things like suddenly forcing all nss-modules to be incompatible with the very presence of all libraries with different versions than what they are linked with (until we deploy symbol versioning in all affected libraries), and so on... It is not something most users face, as most people live well with no nss modules loaded at all, but those who do are completely helpless to fix (it is *impossible* to fix this user-side). Major messes involving libsasl and libldap come to mind as well... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#307488: please upgrade to newer libtool (libtool1.4 being removed)
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > On Tue, 03 May 2005, Thomas Bushnell BSG wrote: >> > libtool1.4 is no longer maintained and will be removed from the >> > archive after sarge is released. Please upgrade your package to use a >> >> What about the fact that there are packages which still need it? You > > They are broken right now, and will have to be fixed, since libtool > 1.4-generated breakage will not be tolerated in etch. Why not fix libtool 1.4 not to generate the breakage? Still, as long as the people pushing the change are willing to chip in with their shoulder to the wheel in "fixing" unbroken packages that currently use libtool 1.4, I don't care. Steve Langasek did his part to send me patches that should work with gnucash, but I don't know about the other cases that exist. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#307488: please upgrade to newer libtool (libtool1.4 being removed)
On Tue, 03 May 2005, Thomas Bushnell BSG wrote: > Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > > On Tue, 03 May 2005, Thomas Bushnell BSG wrote: > >> > libtool1.4 is no longer maintained and will be removed from the > >> > archive after sarge is released. Please upgrade your package to use a > >> > >> What about the fact that there are packages which still need it? You > > > > They are broken right now, and will have to be fixed, since libtool > > 1.4-generated breakage will not be tolerated in etch. > > Why not fix libtool 1.4 not to generate the breakage? The fix *is* to update to a new libtool :) It is like trying to fix mozilla in stable so that it is 100% safe... > Still, as long as the people pushing the change are willing to chip in > with their shoulder to the wheel in "fixing" unbroken packages that > currently use libtool 1.4, I don't care. Steve Langasek did his part Evidently that is what we will be trying to do... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Is Petr Cech MIA?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm forwarding a thread from -release: http://lists.debian.org/debian-release/2005/04/msg00255.html asking if is MIA? Although his last upload is: pavuk (0.9.32-1) unstable; urgency=high * New upstream release (closes: #304553, #203089) * debian/rules: - s/dh_installmanpages/dh_installman/ - Don't install testing scripts. - Use --disable-gtk2 to force usage of gtk1.2 * debian/copyright: new upstream location -- Petr Cech <[EMAIL PROTECTED]> Wed, 20 Apr 2005 15:48:34 + He doesn't responds to emails or bug reports. I tried to contact him to his debian email with no success. I even orphaned one of his packages (phpdoc) and didn't get any response. (I know I shouldn't have done that - as noted in the -release thread). Looking at http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=phpdoc seems the he doesn't respond to bug reports (even RC ones). My final question is: can someone help with NMUing phpdoc (rc bugs has a very small patch to fix a build-depends field). Thanks. - -- Regards, Lior Kaplan [EMAIL PROTECTED] http://www.Guides.co.il Debian GNU/Linux unstable (SID) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCd7InFViURZnoHaARAvR7AJ9hkdp/kP0YHx0qlV+v51xU8iSJIwCgk5kZ uVvXloAc09gaxd3NA5+T3/A= =1/RB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
