found 669172 2.13-29
thanks
On 2012-04-18 00:38 +0200, Adam Conrad wrote:
The reason this fails in -27 as well as -28 is because it has
nothing to do with -28, it just got triggered for people by a
new eglibc upload, period.
The real bug here is that dpkg has decided that referring to
Processing commands for cont...@bugs.debian.org:
found 669172 2.13-29
Bug #669172 {Done: Adam Conrad adcon...@0c3.net} [libc6] libc6: preinst fails
in -28 and since then also in -27
Marked as found in versions eglibc/2.13-29; no longer marked as fixed in
versions eglibc/2.13-29 and reopened.
Processing commands for cont...@bugs.debian.org:
tags 669172 + pending
Bug #669172 [libc6] libc6: preinst fails in -28 and since then also in -27
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
669172:
Author: adconrad
Date: 2012-04-18 11:32:53 + (Wed, 18 Apr 2012)
New Revision: 5191
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/debhelper.in/libc.postinst
glibc-package/trunk/debian/debhelper.in/libc.preinst
Log:
Guard DPKG_MAINTSCRIPT_ARCH usage with
Processing commands for cont...@bugs.debian.org:
# Bug 654783 cloned as bug 669281
tag 669281 patch
Bug #669281 [src:python2.7] python2.7: FTBFS(kfreebsd): testsuite hang
Added tag(s) patch.
retitle 654783 race condition in libpthread causes hangs in python2.7
testsuite
Bug #654783
El 18 d’abril de 2012 15:46, Steven Chamberlain ste...@pyro.eu.org ha escrit:
With it, I hit a tst-timer5 regression during build.
Don't worry about tst-timer5, it's a fake regression. Previously it
succeeded by exitting without testing anything.
On 18/04/12 07:02, Petr Salinger wrote:
-
Processing commands for cont...@bugs.debian.org:
unblock 668240 with 654783
Bug #668240 [src:guitarix] guitarix: FTBFS(kfreebsd-i386): hangs during waf
build
668240 was blocked by: 654783
668240 was blocking: 669281
Removed blocking bug(s) of 668240: 654783
thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
unblock 668240 with 654783
Bug #668240 [src:guitarix] guitarix: FTBFS(kfreebsd-i386): hangs during waf
build
668240 was blocked by: 669281
668240 was blocking: 669281
Removed blocking bug(s) of 668240: 654783
thanks
Stopping processing here.
Author: adconrad
Date: 2012-04-18 19:59:03 + (Wed, 18 Apr 2012)
New Revision: 5192
Added:
glibc-package/tags/2.13-30/
Log:
Tag eglibc 2.13-30
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
eglibc_2.13-30_multi.changes uploaded successfully to localhost
along with the files:
glibc-doc_2.13-30_all.deb
eglibc-source_2.13-30_all.deb
locales_2.13-30_all.deb
libc6_2.13-30_amd64.deb
libc6-dev_2.13-30_amd64.deb
libc6-prof_2.13-30_amd64.deb
libc6-pic_2.13-30_amd64.deb
Your message dated Wed, 18 Apr 2012 21:06:44 +
with message-id e1skc5m-0006vd...@franck.debian.org
and subject line Bug#669172: fixed in eglibc 2.13-30
has caused the Debian Bug report #669172,
regarding libc6: preinst fails in -28 and since then also in -27
to be marked as done.
This means
Package: nscd
Version: 2.13-27
Upstream changes have resolved the problems in NEWS.Debian. Namely,
since at least 2.8 (2008), nscd correctly respects TTL in DNS
caching. [1]
Would it be possible to remove the now-incorrect statement in NEWS and
re-enable DNS caching by default?
[1]
Accepted:
eglibc-source_2.13-30_all.deb
to main/e/eglibc/eglibc-source_2.13-30_all.deb
eglibc_2.13-30.diff.gz
to main/e/eglibc/eglibc_2.13-30.diff.gz
eglibc_2.13-30.dsc
to main/e/eglibc/eglibc_2.13-30.dsc
glibc-doc_2.13-30_all.deb
to main/e/eglibc/glibc-doc_2.13-30_all.deb
There are disparities between your recently accepted upload and the
override file for the following file(s):
libc6-amd64_2.13-30_i386.deb: package says priority is standard, override says
optional.
Please note that a list of new sections were recently added to the
archive: cli-mono, database,
On 18/04/12 19:59, Robert Millan wrote:
El 18 dâabril de 2012 15:46, Steven Chamberlain ste...@pyro.eu.org ha
escrit:
With it, I hit a tst-timer5 regression during build.
Don't worry about tst-timer5, it's a fake regression. Previously it
succeeded by exitting without testing anything.
15 matches
Mail list logo