Author: aurel32
Date: 2006-05-18 05:47:33 + (Thu, 18 May 2006)
New Revision: 1487
Modified:
glibc-package/trunk/debian/rules.d/tarball.mk
Log:
backport from 2.4 branch: rename the directory of the unpacked tarball if
needed.
not necessary for 2.3.6, but it reduces the diff between the two
Just to let you know that the issue has been confirmed by an independent
party:
http://busybox.net/lists/busybox/2006-May/021510.html
Best regards,
Andree
--
Andree Leidenfrost
Sydney - Australia
signature.asc
Description: This is a digitally signed message part
Package: glibc-doc
Version: 2.3.6-7
Severity: normal
Tags: patch
File: file:///usr/share/doc/glibc-doc/html/libc_7.html#SEC121
The example code has:
while (getline (line, len, stdout) = 0)
which causes getline() to try to read from stdout, causing an error,
and the result is always a
Just tested things in an amd64 sid debootstrap chroot environment with
the libc6 packages from experimental with the following outcome:
Architecture: x86_64
libc6 version: 2.3.999.1-2
Statically compiled: (Wrongfully returns 5 on amd64!)
pid=7488
Dynamically compiled:
pid=7489
which means that
Author: aurel32
Date: 2006-05-18 15:35:00 + (Thu, 18 May 2006)
New Revision: 1489
Modified:
glibc-package/trunk/debian/changelog
Log:
Upload 2.3.6-8 to unstable
Modified: glibc-package/trunk/debian/changelog
===
---
Package: libc6-i386
Version: 2.3.6-7
Severity: important
Hi,
when building a 32bit program on amd64 I get the following problem:
[EMAIL PROTECTED]:~/mbr/mbr-1.1.5$ dpkg-shlibdeps -O
debian/tmp/sbin/install-mbr
dpkg-shlibdeps: warning: could not find any packages for libc.so.6
dpkg-shlibdeps:
glibc_2.3.6-8_amd64.changes uploaded successfully to localhost
along with the files:
glibc_2.3.6-8.dsc
glibc_2.3.6-8.diff.gz
glibc-doc_2.3.6-8_all.deb
locales_2.3.6-8_all.deb
libc6_2.3.6-8_amd64.deb
libc6-dev_2.3.6-8_amd64.deb
libc6-prof_2.3.6-8_amd64.deb
Accepted:
glibc-doc_2.3.6-8_all.deb
to pool/main/g/glibc/glibc-doc_2.3.6-8_all.deb
glibc_2.3.6-8.diff.gz
to pool/main/g/glibc/glibc_2.3.6-8.diff.gz
glibc_2.3.6-8.dsc
to pool/main/g/glibc/glibc_2.3.6-8.dsc
libc6-dbg_2.3.6-8_amd64.deb
to pool/main/g/glibc/libc6-dbg_2.3.6-8_amd64.deb
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#364251: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365651: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365547: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#367145: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:18 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#319422: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:18 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#349204: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#364666: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365647: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365676: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365838: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365677: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Thu, 18 May 2006 10:17:18 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#362763: fixed in glibc 2.3.6-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Author: aurel32
Date: 2006-05-18 17:57:10 + (Thu, 18 May 2006)
New Revision: 1491
Modified:
glibc-package/trunk/debian/changelog
Log:
Start a new changelog entry
Modified: glibc-package/trunk/debian/changelog
===
---
Package: libc6
Version: 2.3.6-7
Severity: normal
Hi,
Currently the libc6 package on amd64 ships a symlink from /lib64 to
/lib (and /usr/lib64). While the symlink is needed for things to work
shipping it in the data.tar.gz makes it impossible for any package to
put files into /lib64 or /usr/lib64
Processing commands for [EMAIL PROTECTED]:
reassign 367892 dpkg
Bug#367892: Missing /lib/ldconfig links needed by dpkg-shlibdeps
Bug reassigned from package `libc6-i386' to `dpkg'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
severity 367962 wishlist
Bug#367962: Please don't ship a /lib64 symlink in the package on amd64
Severity set to `wishlist' from `normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
reassign 367892 dpkg
thanks
Goswin Brederlow wrote:
Package: libc6-i386
Version: 2.3.6-7
Severity: important
Hi,
when building a 32bit program on amd64 I get the following problem:
[EMAIL PROTECTED]:~/mbr/mbr-1.1.5$ dpkg-shlibdeps -O debian/tmp/sbin/install-mbr
dpkg-shlibdeps: warning:
severity 367962 wishlist
thanks
Goswin Brederlow wrote:
Package: libc6
Version: 2.3.6-7
Severity: normal
Hi,
Currently the libc6 package on amd64 ships a symlink from /lib64 to
/lib (and /usr/lib64). While the symlink is needed for things to work
shipping it in the data.tar.gz makes it
Aurelien Jarno [EMAIL PROTECTED] writes:
severity 367962 wishlist
thanks
Goswin Brederlow wrote:
Package: libc6
Version: 2.3.6-7
Severity: normal
Hi,
Currently the libc6 package on amd64 ships a symlink from /lib64 to
/lib (and /usr/lib64). While the symlink is needed for things to work
Goswin von Brederlow wrote:
Aurelien Jarno [EMAIL PROTECTED] writes:
severity 367962 wishlist
thanks
Goswin Brederlow wrote:
Package: libc6
Version: 2.3.6-7
Severity: normal
Hi,
Currently the libc6 package on amd64 ships a symlink from /lib64 to
/lib (and /usr/lib64). While the symlink is
[Ccing: amd64 and dpkg developers as they are concerned by this subject]
Hi all,
[Short introduction to understand the problem]
I am asking here for help to take a decision. As some of you may know,
on amd64, the main libraries are installed into (/usr)/lib, with
(/usr)/lib64 being a symlink
Author: aurel32
Date: 2006-05-19 05:40:49 + (Fri, 19 May 2006)
New Revision: 1492
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/rules.d/build.mk
Log:
* Don't run make install with -j, as it is not SMP safe.
Modified: glibc-package/trunk/debian/changelog
30 matches
Mail list logo
