Martin Schulze wrote:
Martin Schulze wrote:
Package: glibc-doc
Version: 2.7-16
Please remove the following manpages from the glibc-doc distribution:
Here are some more that cause conflicts:
. pthread_attr_getschedpolicy(3)
. pthread_attr_getschedparam(3
Package: glibc-doc
Version: 2.7-16
Please remove the following manpages from the glibc-doc distribution:
. pthread_attr_destroy(3)
. pthread_attr_getdetachstate(3)
. pthread_attr_getscope(3)
. pthread_attr_init(3)
. pthread_attr_setdetachstate(3)
.
Martin Schulze wrote:
Package: glibc-doc
Version: 2.7-16
Please remove the following manpages from the glibc-doc distribution:
Here are some more that cause conflicts:
. pthread_attr_getschedpolicy(3)
. pthread_attr_getschedparam(3)
. pthread_attr_setschedpolicy(3
Martin Schulze wrote:
I stand corrected, I cannot fix this. The version of ld.so.8 comes from
the libc6 package and not from the manpages package as one might assume.
As the package has been reassigned already nothing needs to be done on
my end I guess.
For the record: On rPath Linux, OWL
Martin Schulze wrote:
On Sun, Mar 30, 2008 at 09:48:46PM +0300, ygrek wrote:
man dlopen says :
Otherwise, the
dynamic linker searches for the library as follows (see ld.so(8) for
further details):
[...]
o The directories /lib and /usr/lib are searched
Aurelien Jarno wrote:
# Automatically generated email from bts, devscripts version 2.9.26
tags 473458 + pending
Aurelien, care to explain the pending solution?
Regards,
Joey
--
Never trust an operating system you don't have source for!
Please always Cc to me when replying to me on
Michael Kerrisk wrote:
Justin Pryzby wrote:
reassign 473458 libc6
found 473458 2.7-9
thanks
On Sun, Mar 30, 2008 at 09:48:46PM +0300, ygrek wrote:
man dlopen says :
Otherwise, the
dynamic linker searches for the library as follows (see ld.so(8) for
further
Package: libc6
Version: 2.5-5
Severity: minor
# This script is existed for detecting depreciated kernel version to
# check glibc incompatibility.
This should read This script exists for... or This script does exist for...
or if you need the past tense This script existed for... (however, that
merge 409147 409148
thanks
David Broome wrote:
Package: glibc
Version: glibc-2.3.2.ds1-22sarge4
Severity: critical
Hello - tzdata in glibc for stable is based on tzdata2006b (from edits
in 2.3.2.ds1-22sarge1), this does not have the correct PST changes for
this year for 4 Canadian
Aurelien Jarno wrote:
Ok, I bet you are using a 2.4 kernel and you are actually have the same
bug as 380504. I will try to find a fix asap.
Ok, fix found, checked in our SVN, it will be in the next upload
(probably soon). Thanks to Denis Barbier for the hint.
Confirmed, this fixes
Aurelien Jarno wrote:
Martin Schulze wrote:
Package: libc6
Version: 2.3.6-16 (and newer)
When I install a libc6 that is compiled with GCC 4.1 instead of 4.0
gnupg (1.4.5-1) doesn't want to work anymore.
'gnupg --clearsign file' gets a segmentation fault. Compiling
2.3.6-16 with GCC 4.0
Aurelien Jarno wrote:
Ok, fix found, checked in our SVN, it will be in the next upload
(probably soon). Thanks to Denis Barbier for the hint.
Cool! I'm eager to try it out with one of the next upgrades.
Regards,
Joey
--
Every use of Linux is a proper use of Linux. -- Jon 'maddog'
Package: libc6
Version: 2.3.6-16 (and newer)
When I install a libc6 that is compiled with GCC 4.1 instead of 4.0
gnupg (1.4.5-1) doesn't want to work anymore.
'gnupg --clearsign file' gets a segmentation fault. Compiling
2.3.6-16 with GCC 4.0 again makes the problem go away.
2.3.6-19 still
Francesco Pipita wrote:
I got the manpages-dev package (manpages-dev_2.28-1_all.deb) and then
I tried getting the glibc-doc (glibc-doc_2.3.6-7_all.deb)
package. When unpacking the glibc-doc package, dpkg said me which
manpages-dev
and glibc-doc both contain the file
GOTO Masanori wrote:
I found NPTL/buildd kernel mismatch problem today when I saw the s390
build log failure at
http://buildd.debian.org/~jeroen/status/package.php?p=glibc
/build/buildd/glibc-2.3.5/build-tree/s390-nptl/elf/ld.so.1
--library-path ...
Norbert Veber wrote:
On Fri, Jan 14, 2005 at 10:44:13AM -0500, Norbert Veber wrote:
Package: libc6-sparc64
Version: 2.2.5-11.8
Severity: normal
Preparing to replace libc6-sparc64 2.2.5-11.5 (using
.../libc6-sparc64_2.2.5-11.8_sparc.deb) ...
Unpacking replacement libc6-sparc64
GOTO Masanori wrote:
clone 231538 -1
reassign -1 ftp.debian.org
retitle -1 sarge needs upgrade-i386 directory which gives us upgrade-path for real
i386 architecture
thanks
I'm sorry posting this mail to so many people...
Summary:
- Original bug #231538 will be fixed by debian-glibc
GOTO Masanori wrote:
That would only help mips.
I wonder what a mips machine would need with an i486 emulator.
For IA-32 we would have to patch 2.4.18, but we cannot properly
update those packages in woody without people losing their
modules (would hurt a bit on laptops...). So
Christoph Hellwig wrote:
On Fri, Mar 26, 2004 at 07:54:45PM +0100, Martin Schulze wrote:
Hence, I believe that an upgrade directory is the way to go. The
kernel package should be maintained until sarge is released and
security patches added.
Can you patch the i48 instruction emulator
GOTO Masanori wrote:
| What does sid have to do with woody?
The problem is that of providing an upgrade path from woody to sarge on
real i386 machines. Glibc (and everything else in userland) in
sarge/sid requires a kernel with the i486 emulation patch for such
machines. There is no
GOTO Masanori wrote:
So, don't we have plan to put newer kernel 2.4.24 into woody? Then I
simply put the description which I described the previous mail:
No, we don't.
Regards,
Joey
--
The good thing about standards is that there are so many to choose from.
--
GOTO Masanori wrote:
At Sat, 20 Mar 2004 13:56:31 -0500,
Nathanael Nerode wrote:
Kernel 2.4.24 is *not* present in woody.
It is in woody-proposed-updates.
Please, someone, remember to convince Martin Schulze to accept it. :-)
I don't know pure woody can have new kernel 2.4.24
Carlos O'Donell wrote:
If that is the so called solution, could somebody please do something
I requested a while ago:
http://lists.debian.org/debian-hppa/2002/debian-hppa-200212/msg00065.html
tausq: *hint* *hint*
Regards,
Joey
Joey,
I spoke with you about this,
GOTO Masanori wrote:
Oops! I'm sorry, I fixed as follows:
--- libc/DEBIAN/preinst 6 Jan 2003 13:51:53 - 1.5
+++ libc/DEBIAN/preinst 7 Jan 2003 13:27:02 -
@@ -115,10 +115,11 @@
fi
# parisc64 boxes require latest fixes in the kernel 2.4.19-pa17 or later
# (in
Carlos O'Donell wrote:
If that is the so called solution, could somebody please do something
I requested a while ago:
http://lists.debian.org/debian-hppa/2002/debian-hppa-200212/msg00065.html
tausq: *hint* *hint*
Regards,
Joey
Joey,
I spoke with you about this,
I guess this is a glibc problem, but I'm not 100% sure, of course.
paer!joey(pts/9):/tmp# apt-get update
E: Could not get lock /var/lib/apt/lists/lock - open (22 Invalid argument)
E: Unable to lock the list directory
paer!joey(pts/9):/tmp# l -d /var/lib/apt/lists/lock
I've updated glibc to the
I guess this is a glibc problem, but I'm not 100% sure, of course.
paer!joey(pts/9):/tmp# apt-get update
E: Could not get lock /var/lib/apt/lists/lock - open (22 Invalid argument)
E: Unable to lock the list directory
paer!joey(pts/9):/tmp# l -d /var/lib/apt/lists/lock
I've updated glibc to the
Jeff Bailey wrote:
Please note that this software will, at some point in the future, fail
to compile again. All this has done is buy some time. Please make sure
your software fixes the broken usage of extern int errno; and replaces
it with proper uses of the errno.h header.
Err? Did the
Jeff Bailey wrote:
Please note that this software will, at some point in the future, fail
to compile again. All this has done is buy some time. Please make sure
your software fixes the broken usage of extern int errno; and replaces
it with proper uses of the errno.h header.
Err? Did the
Daniel Jacobowitz wrote:
Uh, I'm stupid. Here we go.
This patch is not fixing the problem on IA-64 - and with this second
test I effectively knocked out merulo this time since I forgot to keep
a root shell open. *sigh*
Regards,
Joey
--
This is Linux Country. On a quiet night, you
Daniel Jacobowitz wrote:
Uh, I'm stupid. Here we go.
This patch is not fixing the problem on IA-64 - and with this second
test I effectively knocked out merulo this time since I forgot to keep
a root shell open. *sigh*
Regards,
Joey
--
This is Linux Country. On a quiet night, you
Martin Baulig wrote:
Hi,
is there any reason why we already have glibc 2.3.x binaries in sarge, but
the latest
source package is 2.2.5-14.3 ?
I finally found the .diff.gz and the .orig.tar.gz in /pool/main/g/glibc, but
/dists/sarge/main/source/Sources.gz still has 2.2.5-14.3.
Well,
Matt Zimmerman wrote:
The socket is world writable, glibc's syslog() function writes
to it, from any program. Restricting its write access to root
would effectively disable syslogging.
How so? Restricting its write access to root would still allow programs
running as root to use
33 matches
Mail list logo
