Andreas Barth
2006-Mar-13 12:28 UTC
[Secure-testing-team] Re: status of getting security fixes into sarge
* Martin Schulze (joey@infodrom.org) [041210 08:30]:> Joey Hess wrote: > > perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976 > > Still missing mipsel build, should probably be re-queued or > > uploaded manually.> I suspect there is a problem with the buildd host. Perl builds (and > runs) fine in environments outside of this particular buildd. Requeuing > doesn''t change anything. Somebody would have to debug the failing 12 > test cases on that particular host, I guess...I queued perl on another mipsel-machine for a test-build with sbuild and had still one test failure. | b/Net/hostent......................# Failed test (../lib/Net/hostent.t at line 36) | FAILED at test 2 Please see http://experimental.ftbfs.de/fetch.php?&pkg=perl&ver=5.8.4-4&arch=mipsel&stamp=1102614585&file=log&as=raw for the full log. perl however builds fine with pbuilder on the same machine. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Steve Langasek
2006-Mar-13 12:28 UTC
[Secure-testing-team] Re: status of getting security fixes into sarge
On Fri, Dec 10, 2004 at 11:03:48AM +0100, Andreas Barth wrote:> * Martin Schulze (joey@infodrom.org) [041210 08:30]: > > Joey Hess wrote: > > > perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976 > > > Still missing mipsel build, should probably be re-queued or > > > uploaded manually.> > I suspect there is a problem with the buildd host. Perl builds (and > > runs) fine in environments outside of this particular buildd. Requeuing > > doesn''t change anything. Somebody would have to debug the failing 12 > > test cases on that particular host, I guess...> I queued perl on another mipsel-machine for a test-build with sbuild and > had still one test failure. > | b/Net/hostent......................# Failed test (../lib/Net/hostent.t at line 36) > | FAILED at test 2 > Please see > http://experimental.ftbfs.de/fetch.php?&pkg=perl&ver=5.8.4-4&arch=mipsel&stamp=1102614585&file=log&as=raw > for the full log. perl however builds fine with pbuilder on the same > machine.This is a failure of gethost(''localhost''), which could be caused by a name resolution problem in the build environment. Can you verify that your sbuild environment has a valid /etc/hosts? -- Steve Langasek postmodern programmer -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20041210/6f7404cc/attachment.pgp
Andreas Barth
2006-Mar-13 12:28 UTC
[Secure-testing-team] Re: status of getting security fixes into sarge
* Steve Langasek (vorlon@debian.org) [041211 08:55]:> On Fri, Dec 10, 2004 at 11:03:48AM +0100, Andreas Barth wrote: > > * Martin Schulze (joey@infodrom.org) [041210 08:30]: > > > Joey Hess wrote: > > > > perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976 > > > > Still missing mipsel build, should probably be re-queued or > > > > uploaded manually. > > > > I suspect there is a problem with the buildd host. Perl builds (and > > > runs) fine in environments outside of this particular buildd. Requeuing > > > doesn''t change anything. Somebody would have to debug the failing 12 > > > test cases on that particular host, I guess... > > > I queued perl on another mipsel-machine for a test-build with sbuild and > > had still one test failure. > > | b/Net/hostent......................# Failed test (../lib/Net/hostent.t at line 36) > > | FAILED at test 2 > > Please see > > http://experimental.ftbfs.de/fetch.php?&pkg=perl&ver=5.8.4-4&arch=mipsel&stamp=1102614585&file=log&as=raw > > for the full log. perl however builds fine with pbuilder on the same > > machine.> This is a failure of gethost(''localhost''), which could be caused by a name > resolution problem in the build environment. Can you verify that your > sbuild environment has a valid /etc/hosts?There was no /etc/hosts, but the usual resolv.conf. Well, I have copied hosts, and requeued perl now, to see what happens. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Martin Schulze
2006-Mar-13 12:28 UTC
[Secure-testing-team] Re: status of getting security fixes into sarge
Joey Hess wrote:> perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976 > Still missing mipsel build, should probably be re-queued or > uploaded manually.I suspect there is a problem with the buildd host. Perl builds (and runs) fine in environments outside of this particular buildd. Requeuing doesn''t change anything. Somebody would have to debug the failing 12 test cases on that particular host, I guess... Regards, Joey -- WARNING: Do not execute! This call violates patent DE10108564. http://www.elug.de/projekte/patent-party/patente/DE10108564 wget -O patinfo-`date +"%Y%m%d"`.html http://patinfo.ffii.org/
Steve Langasek
2006-Mar-13 12:28 UTC
[Secure-testing-team] Re: status of getting security fixes into sarge
On Thu, Dec 09, 2004 at 04:20:12PM -0500, Joey Hess wrote:> Some NMUing has been done lately on some of the older security holes in > sarge. Here are the ones the testing security team is currently tracking > that are fixed in unstable but don''t yet have a fix in sarge, plus a few > others of interest:> opendchub 0.7.14-1.1 needed, have 0.7.14-1 for CAN-2004-1127 > Will go in in a few days.Blocked by a build failure on m68k (calls automake, due to timestamp skew and lack of AM_MAINTAINER_MODE). Bug filed.> prozilla (unfixed; bug #284117) for CAN-2004-1120 > Well it''s not fixed, and no patch is known. Candidate for > removal.Tagged for removal.> mtink 1.0.5 needed, have 1.0.1-2 for CAN-2004-1110 > Goes in today.Looks good.> ppp 2.4.2+20040428-3 needed, have 2.4.2+20040428-2 for CAN-2004-1002 > Frozen, same as in last report, see maintainer''s comments IIRC.Hrm, the last status I had on this was that I was *waiting* for maintainer comments... :) Seeing none, I''ve gone ahead and pushed this in despite 278082.> cscope 15.5-1.1 needed, have 15.5-1 for CAN-2004-0996 > Should go in RSN.Yep, it''s in. Thanks, -- Steve Langasek postmodern programmer -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20041211/cf6f70b1/attachment.pgp
Joey Hess
2006-Mar-13 12:28 UTC
[Secure-testing-team] status of getting security fixes into sarge
Some NMUing has been done lately on some of the older security holes in sarge. Here are the ones the testing security team is currently tracking that are fixed in unstable but don''t yet have a fix in sarge, plus a few others of interest: opendchub 0.7.14-1.1 needed, have 0.7.14-1 for CAN-2004-1127 Will go in in a few days. prozilla (unfixed; bug #284117) for CAN-2004-1120 Well it''s not fixed, and no patch is known. Candidate for removal. mtink 1.0.5 needed, have 1.0.1-2 for CAN-2004-1110 Goes in today. ppp 2.4.2+20040428-3 needed, have 2.4.2+20040428-2 for CAN-2004-1002 Frozen, same as in last report, see maintainer''s comments IIRC. cscope 15.5-1.1 needed, have 15.5-1 for CAN-2004-0996 Should go in RSN. mailutils 1:0.5-4 needed, have 1:0.5-3 for CAN-2004-0984 Blocked for over 1 month by missing s390 builds now. perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976 Still missing mipsel build, should probably be re-queued or uploaded manually. libc6 2.3.2.ds1-19 needed, have 2.3.2.ds1-18 for CAN-2004-0968 Missing some builds and new RC bug, probably not yet ready for testing. Pity the security fix was bundled with other changes.. kernel-source-2.4.27 2.4.27-6 needed, have 2.4.27-5 for CAN-2004-0814 Too young and buggy. kernel-image-2.4.27-i386 2.4.27-6 needed, have 2.4.27-2 for CAN-2004-0814 Too young and buggy. cyrus21-imapd 2.1.17-1 needed, have 2.1.16-10 for DSA-597-1 Still blocked by perl. kaffeine 0.4.3.1-3 needed, have 0.4.3-1 for CAN-2004-1034 kdelibs 4:3.2.3-3.sarge.1 needed, have 4:3.2.3-2 for CAN-2004-0746 konqueror 4:3.2.3-1.sarge.1 needed, have 4:3.2.2-1 for CAN-2004-0721 kdelibs 4:3.2.3-3.sarge.1 needed, have 4:3.2.3-2 for CAN-2004-0721 kdelibs 4:3.2.3-3.sarge.1 needed, have 4:3.2.3-2 for CAN-2004-0690 koffice 1:1.3.4-1 needed, have 1:1.3.2-1.sarge.1 for CAN-2004-0888 kpdf 4:3.3.1-1 needed, have 4:3.2.3-1.1 for DSA-573-1 kfax 4:3.3.1-1 needed, have 4:3.2.3-1.1 for DSA-573-1 kdelibs 4:3.2.3-3.sarge.1 needed, have 4:3.2.3-2 for DSA-539 All of these are the same old same old KDE issue I''m afraid. So half of sarge''s unfixed security holes are now in kde. :-( -- see shy jo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20041209/5adba17c/attachment.pgp