Jeff Bailey said:
> It had never occured to me to put the debug path in the cache file. I'm
> not sure how common of a scenario that is, or it should've bitten
> someone before.
I suppose so. I don't really know why I put it there in the first place.
:-) I was debugging a program and thought that
On Fri, 2002-10-18 at 12:35, Jeff Bailey wrote:
> Do you think making libc6-dbg pre-depend instead of depend'ing on
> libc6 (= 2.3.1-1) would work?
Should --- though, according to policy, libc6 will only be unpacked. But
since it is Essential: yes, it should work that way.
What a fun bug. Hope y
On Sat, 19 Oct 2002, Anthony Towns wrote:
> On Sat, Oct 19, 2002 at 02:38:57AM +0900, GOTO Masanori wrote:
> > After upgrading libc package, then please stop-and-start network
> > services/daemons, because name service switch is changed in glibc 2.3.
>
> Uh, you're going to fix this in a new uploa
On Fri, 2002-10-18 at 12:35, Jeff Bailey wrote:
> Do you think making libc6-dbg pre-depend instead of depend'ing on
> libc6 (= 2.3.1-1) would work?
Should --- though, according to policy, libc6 will only be unpacked. But
since it is Essential: yes, it should work that way.
What a fun bug. Hope y
On Thu, 2002-10-17 at 22:38, Aaron M. Ucko wrote:
> Incidentally, you should also broaden the list of relevant services; I
> would suggest adding kdm (and other display managers?), ssh-krb5, and
> apache2 at the least.
Don't add display managers. At least with gdm I'm pretty sure that will
kill X
On Fri, Oct 18, 2002 at 11:28:25PM +0200, Rene Engelhard wrote:
> severity 165412 critical
> thanks
>
> Hi,
>
> Oskar Liljeblad wrote:
> > SIGRTMIN is defined glibc-2.3.1/sysdeps/unix/sysv/{arch}/bits/signum.h
> > as:
> >
> > #define SIGRTMIN(__libc_current_sigrtmin ())
>
> This is th
On Sat, Oct 19, 2002 at 03:51:44AM +0900, GOTO Masanori wrote:
> > In short, I doubt we will get sufficient testing on problematic
> > arches unless we take the leap and push into sid. However I would
> > make sure that the findsyms perl script I wrote has been run on the
> > debian sid package arc
Package: libc6
Version: 2.2.5-14.3
Severity: normal
The ldd script fails on non-executable files (such as most libraries)
if the file package is not installed.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.18-686-smp #1 SMP Sun Apr 14 12:07:19 EST
2002
On Fri, Oct 18, 2002 at 11:28:25PM +0200, Rene Engelhard wrote:
> severity 165412 critical
> thanks
>
> Hi,
>
> Oskar Liljeblad wrote:
> > SIGRTMIN is defined glibc-2.3.1/sysdeps/unix/sysv/{arch}/bits/signum.h
> > as:
> >
> > #define SIGRTMIN(__libc_current_sigrtmin ())
>
> This is th
Processing commands for [EMAIL PROTECTED]:
> severity 165412 critical
Bug#165412: libc6: SIGRTMIN defined as -1 with libc 2.3.1, as 32 with 2.2.5
Severity set to `critical'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
severity 165412 critical
thanks
Hi,
Oskar Liljeblad wrote:
> SIGRTMIN is defined glibc-2.3.1/sysdeps/unix/sysv/{arch}/bits/signum.h
> as:
>
> #define SIGRTMIN(__libc_current_sigrtmin ())
This is the problem. As I understand, __libc_* is now hidden and
unaccessible.
So the function is
Package: libc6
Version: 2.3.1-1
Severity: important
(I consider this important as it breaks all programs using this
signal entirely. I wouldn't blame you for lowing the severity
though...)
Ok, SIGRTMIN evaluates to -1 with libc6 2.3.1. With libc6 2.2.5
it would evaluate to 32.
SIGRTMIN is define
On Sat, Oct 19, 2002 at 03:51:44AM +0900, GOTO Masanori wrote:
> > In short, I doubt we will get sufficient testing on problematic
> > arches unless we take the leap and push into sid. However I would
> > make sure that the findsyms perl script I wrote has been run on the
> > debian sid package arc
Package: libc6
Version: 2.2.5-14.3
Severity: normal
The ldd script fails on non-executable files (such as most libraries)
if the file package is not installed.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.18-686-smp #1 SMP Sun Apr 14 12:07:19 EST 2002
Processing commands for [EMAIL PROTECTED]:
> severity 165412 critical
Bug#165412: libc6: SIGRTMIN defined as -1 with libc 2.3.1, as 32 with 2.2.5
Severity set to `critical'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
On Fri, Oct 18, 2002 at 01:19:17PM -0600, Debian GLibc CVS Master wrote:
> - debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Oops, did I get it wrogn copying from the message? Sorry!
--
learning from failures is nice in theory...
but in practice, it sucks :)
- Wolfgang Jaehrling
Repository: glibc-package/debian/packages.d
who:gotom
time: Fri Oct 18 13:19:18 MDT 2002
Log Message:
- debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Files:
changed:libc-udeb.mk
Repository: glibc-package/debian
who:gotom
time: Fri Oct 18 13:19:16 MDT 2002
Log Message:
- debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Files:
changed:changelog
On Fri, Oct 18, 2002 at 01:37:51PM -0500, Zed Pobre wrote:
> Attempting to su to root (even from root) with 2.3.1-1 on one of my
> test systems caused an immediate segfault. Also, attempting to ssh
> to root on the same system allowed login, but then immediately died.
> The problem was fixed by r
At Wed, 16 Oct 2002 09:50:19 -0400 (EDT),
Jack Howarth wrote:
>I thought the plan was to simply push glibc 2.3.1 into sid, no?
> I have been running the glibc 2.3 debian cvs source patches
> and glibc cvs (built almost daily) on debian ppc sid for about
> a month now. I have seen no issues runn
Your message dated Sat, 19 Oct 2002 03:44:13 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Processed: Re: ipopd: inetd[29700]: getpwnam: root: No such
user
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
Processing commands for [EMAIL PROTECTED]:
> reassign 165378 libc6
Bug#165378: ipopd: inetd[29700]: getpwnam: root: No such user
Bug reassigned from package `ipopd' to `libc6'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On Fri, Oct 18, 2002 at 08:03:04PM +0200, Per Lundberg wrote:
> >> The problem is that libc6-dbg is unpacked BEFORE libc6 [...]
> > Do you think making libc6-dbg pre-depend instead of depend'ing on
> > libc6 (= 2.3.1-1) would work?
> I suppose so; but I do not know exactly how the internals of d
Jeff Bailey said:
>> The problem is that libc6-dbg is unpacked BEFORE libc6 [...]
> Do you think making libc6-dbg pre-depend instead of depend'ing on
> libc6 (= 2.3.1-1) would work?
I suppose so; but I do not know exactly how the internals of dpkg work.
All I know is that my system broke down bad
Ben Collins <[EMAIL PROTECTED]> writes:
> We've been over this before. Problem is, it's almost impossible to tell
No doubt; apologies for neglecting to check the archives.
> which ones will need it till they actually fail. We've generally just
> done the libc6 upgreade and wait for bug reports o
On Fri, Oct 18, 2002 at 01:19:17PM -0600, Debian GLibc CVS Master wrote:
> - debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Oops, did I get it wrogn copying from the message? Sorry!
--
learning from failures is nice in theory...
but in practice, it sucks :)
- Wolfgang Jaehrling
On Fri, Oct 18, 2002 at 06:13:28PM +0200, Vincenzo Gervasi wrote:
>
> The update broke other packages as well.
> For example, java reports
> Error occurred during initialization of VM
> Unable to load native library:
> /usr/java/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol __libc_waitpid,
> version
On Fri, Oct 18, 2002 at 05:55:59PM +0200, Arthur de Jong wrote:
> This problem is introduced when using libc6_2.3.1-1_i386.deb, when
> reinstalling libc6_2.2.5-15_i386.deb the problem goes away.
This is a known problem, 2.3.1-2 will contain the right warning.
Restart sshd (and anything else that
If you want me to help you on other bugs, you might want to fix your
mail system. Declaring that you think spam might have come from here
without explaining what test was used is not helpful.
- Forwarded message from Mail Delivery Subsystem -
From: Mail Delivery Subsystem
To: <[EMAIL P
At Fri, 18 Oct 2002 15:57:38 +0200,
Rene Engelhard wrote:
> I yesterday upgraded glibc to the 2.3.1-1 release and suddenly my
> fetchmail does not work complaining it cannot connect to local SMTP.
>
> Downgrading all *libc* and locales Packages to 2.2.5-15 fixes that...
/etc/init.d/nscd stop
/etc
On Fri, Oct 18, 2002 at 03:57:38PM +0200, Rene Engelhard wrote:
> I yesterday upgraded glibc to the 2.3.1-1 release and suddenly my
> fetchmail does not work complaining it cannot connect to local SMTP.
> Downgrading all *libc* and locales Packages to 2.2.5-15 fixes that...
2.3.1-2 will have a w
On Fri, Oct 18, 2002 at 12:00:24PM -0400, Aaron M. Ucko wrote:
> Ben Collins <[EMAIL PROTECTED]> writes:
>
> > Heh, restart display managers is outside the scope of libc. Restarting
> > services is pushing it enough I think.
>
> Hmm, I wonder if it would be saner to have some mechanism (perhaps
>
At Fri, 18 Oct 2002 10:26:03 +0200,
Fabio Massimo Di Nitto wrote:
> like in the topic. the patch is not needed anymore.
> The new resolver in glibc-2.3.1 is now perfectly able to handle both ip6.arpa
> and ip6.int queries.
Thanks for your suggestion. I've just disabled it.
> there are some
On Fri, Oct 18, 2002 at 01:37:51PM -0500, Zed Pobre wrote:
> Attempting to su to root (even from root) with 2.3.1-1 on one of my
> test systems caused an immediate segfault. Also, attempting to ssh
> to root on the same system allowed login, but then immediately died.
> The problem was fixed by r
Repository: glibc-package/debian/packages.d
who:gotom
time: Fri Oct 18 13:19:18 MDT 2002
Log Message:
- debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Files:
changed:libc-udeb.mk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
Repository: glibc-package/debian
who:gotom
time: Fri Oct 18 13:19:16 MDT 2002
Log Message:
- debian/packages.d/libc-udeb.mk: Clean up and fix indent crap.
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
Repository: glibc-package/debian
who:gotom
time: Fri Oct 18 10:49:11 MDT 2002
Log Message:
- debian/patches/0list: disable ip6-fix.dpatch. Closes: #165287
Files:
changed:changelog
Repository: glibc-package/debian/patches
who:gotom
time: Fri Oct 18 10:49:11 MDT 2002
Log Message:
- debian/patches/0list: disable ip6-fix.dpatch. Closes: #165287
Files:
changed:0list
On Fri, Oct 18, 2002 at 05:58:53PM +0200, Per Lundberg wrote:
> The problem is that libc6-dbg is unpacked BEFORE libc6, and libc6
> 2.3.1-1 requires the new dynamic linked ld-linux.so.2 (which has not
> been installed yet). Thus, dpkg-dbg is unpacked correctly, but when
> trying to unpack libc6 (a
The update broke other packages as well.
For example, java reports
Error occurred during initialization of VM
Unable to load native library:
/usr/java/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol __libc_waitpid,
version GLIBC_2.0 not defined in file libc.so.6 with link time reference
I am not sur
At Wed, 16 Oct 2002 09:50:19 -0400 (EDT),
Jack Howarth wrote:
>I thought the plan was to simply push glibc 2.3.1 into sid, no?
> I have been running the glibc 2.3 debian cvs source patches
> and glibc cvs (built almost daily) on debian ppc sid for about
> a month now. I have seen no issues runn
Your message dated Sat, 19 Oct 2002 03:44:13 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Processed: Re: ipopd: inetd[29700]: getpwnam: root: No such user
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
On Fri, Oct 18, 2002 at 11:55:21AM -0400, Jack Howarth wrote:
>What happened to the glibc 2.3.1-1 ppc deb packages built on
> voltaire yesterday? They showed up on incoming.debian.org and seemed
> to pass okay according to the log at buildd.debian.org but were
> never moved into sid. Are they
Subject: libc6: cannot login using ssh
Package: libc6
Version: 2.3.1-1
Severity: normal
Tags: sid
This problem is introduced when using libc6_2.3.1-1_i386.deb, when reinstalling
libc6_2.2.5-15_i386.deb the problem goes away.
When I try to login from a remote (woody) host to a sid host:
% ssh spi
Ben Collins <[EMAIL PROTECTED]> writes:
> Heh, restart display managers is outside the scope of libc. Restarting
> services is pushing it enough I think.
Hmm, I wonder if it would be saner to have some mechanism (perhaps
just a directory fed to run-parts?) for packages to register
themselves for
On Fri, Oct 18, 2002 at 08:03:04PM +0200, Per Lundberg wrote:
> >> The problem is that libc6-dbg is unpacked BEFORE libc6 [...]
> > Do you think making libc6-dbg pre-depend instead of depend'ing on
> > libc6 (= 2.3.1-1) would work?
> I suppose so; but I do not know exactly how the internals of d
Package: libc6-dbg
Version: 2.3.1-1
Severity: critical
If libc6-dbg is installed, and /usr/lib/debug is the first line in
/etc/ld.so.conf, the upgrade from previous versions of libc6 to 2.3.1-1
breaks the system.
The problem is that libc6-dbg is unpacked BEFORE libc6, and libc6 2.3.1-1
requires t
Processing commands for [EMAIL PROTECTED]:
> reassign 165378 libc6
Bug#165378: ipopd: inetd[29700]: getpwnam: root: No such user
Bug reassigned from package `ipopd' to `libc6'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
What happened to the glibc 2.3.1-1 ppc deb packages built
on voltaire yesterday? They showed up on incoming.debian.org
and seemed to pass okay according to the log at buildd.debian.org
but were never moved into sid. Are they on hold or something?
Jack
Repository: glibc-package/debian/sysdeps
who:jbailey
time: Fri Oct 18 09:51:33 MDT 2002
Log Message:
- debian/sysdeps/build-options.mk: Strip libc on alpha
Files:
changed:build-options.mk
Repository: glibc-package/debian
who:jbailey
time: Fri Oct 18 09:51:33 MDT 2002
Log Message:
- debian/sysdeps/build-options.mk: Strip libc on alpha
Files:
changed:changelog
Jeff Bailey said:
>> The problem is that libc6-dbg is unpacked BEFORE libc6 [...]
> Do you think making libc6-dbg pre-depend instead of depend'ing on
> libc6 (= 2.3.1-1) would work?
I suppose so; but I do not know exactly how the internals of dpkg work.
All I know is that my system broke down bad
Jeff Bailey <[EMAIL PROTECTED]> writes:
> On Thu, Oct 17, 2002 at 12:02:08AM +0200, Falk Hueffner wrote:
>
> > > Hmm...I can't recall right now why we chose to not strip it. You
> > > could always give it a go and see what happens. I'll dig through
> > > some old notes and see if I can come up
Repository: glibc-package/debian/packages.d
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/po
Repository: glibc-package/debian/libc/DEBIAN
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/p
Repository: glibc-package/debian/rules.d
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/posti
Repository: glibc-package/debian
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/postinst: War
Repository: glibc-package/debian/control.in
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/po
On Thu, Oct 17, 2002 at 12:02:08AM +0200, Falk Hueffner wrote:
> > Hmm...I can't recall right now why we chose to not strip it. You
> > could always give it a go and see what happens. I'll dig through
> > some old notes and see if I can come up with an answer as to why
> > we did that. I seem t
We debian-glibc maintainer team got some reports and complaints about
upgrading glibc 2.3.1-1 package, so please read this if you use this
new one.
After upgrading libc package, then please stop-and-start network
services/daemons, because name service switch is changed in glibc 2.3.
ex) inetd
Ben Collins <[EMAIL PROTECTED]> writes:
> We've been over this before. Problem is, it's almost impossible to tell
No doubt; apologies for neglecting to check the archives.
> which ones will need it till they actually fail. We've generally just
> done the libc6 upgreade and wait for bug reports o
On Fri, Oct 18, 2002 at 06:13:28PM +0200, Vincenzo Gervasi wrote:
>
> The update broke other packages as well.
> For example, java reports
> Error occurred during initialization of VM
> Unable to load native library:
> /usr/java/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol __libc_waitpid,
> version
On Fri, Oct 18, 2002 at 06:01:35AM -0700, Jeff Bailey wrote:
> On Fri, Oct 18, 2002 at 10:46:38PM +1000, Jay Hap-hang Yu wrote:
>
> > Error occurred during initialization of VM
> > Unable to load native library:
> > /usr/local/sun/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol
> > __libc_waitpid, vers
close 165319
quit
After restarting inetd, all was well again...
--
mail: `echo '<[EMAIL PROTECTED]>' | sed -e 's/[A-S]//g'`
pgp: 0x506A903A; 49D5 794A EA77 F907 764F D89E 304B 93CF 506A 903A
icbm: 47° 02' 43.0" N, 07° 16' 17.5" E (WGS84)
On Fri, Oct 18, 2002 at 12:00:24PM -0400, Aaron M. Ucko wrote:
> Ben Collins <[EMAIL PROTECTED]> writes:
>
> > Heh, restart display managers is outside the scope of libc. Restarting
> > services is pushing it enough I think.
>
> Hmm, I wonder if it would be saner to have some mechanism (perhaps
>
At Fri, 18 Oct 2002 10:26:03 +0200,
Fabio Massimo Di Nitto wrote:
> like in the topic. the patch is not needed anymore.
> The new resolver in glibc-2.3.1 is now perfectly able to handle both ip6.arpa
> and ip6.int queries.
Thanks for your suggestion. I've just disabled it.
> there are some
If you want me to help you on other bugs, you might want to fix your
mail system. Declaring that you think spam might have come from here
without explaining what test was used is not helpful.
- Forwarded message from Mail Delivery Subsystem -
From: Mail Delivery Subsystem
To: <[EMAIL P
On Fri, Oct 18, 2002 at 03:57:38PM +0200, Rene Engelhard wrote:
> I yesterday upgraded glibc to the 2.3.1-1 release and suddenly my
> fetchmail does not work complaining it cannot connect to local SMTP.
> Downgrading all *libc* and locales Packages to 2.2.5-15 fixes that...
2.3.1-2 will have a w
At Fri, 18 Oct 2002 15:57:38 +0200,
Rene Engelhard wrote:
> I yesterday upgraded glibc to the 2.3.1-1 release and suddenly my
> fetchmail does not work complaining it cannot connect to local SMTP.
>
> Downgrading all *libc* and locales Packages to 2.2.5-15 fixes that...
/etc/init.d/nscd stop
/etc
On Fri, Oct 18, 2002 at 05:55:59PM +0200, Arthur de Jong wrote:
> This problem is introduced when using libc6_2.3.1-1_i386.deb, when
> reinstalling libc6_2.2.5-15_i386.deb the problem goes away.
This is a known problem, 2.3.1-2 will contain the right warning.
Restart sshd (and anything else that
On Mon, Sep 02, 2002 at 10:05:59PM +0200, Gerhard Tonn wrote:
> This means glibc 2.2.92 looks rather complete on s390.
2.3.1-1 appears to have failed to build on s390 - I'm doing another
upload this evening. Can you take a look to see what's up?
Tks,
Jeff Bailey
--
learning from failures is n
On Fri, Oct 18, 2002 at 10:03:56AM -0400, Ben Collins wrote:
> Heh, restart display managers is outside the scope of
> libc. Restarting services is pushing it enough I think.
> You are correct. I'm surprised I didn't remember that before 2.3.1
> was uploaded.
> We need to get out a 2.3.1-2 real
Ben Collins <[EMAIL PROTECTED]> writes:
> Heh, restart display managers is outside the scope of libc. Restarting
> services is pushing it enough I think.
Hm, good point, given that it may end up logging users out; never mind
that bit, then.
> You are correct. I'm surprised I didn't remember that
Repository: glibc-package/debian/patches
who:gotom
time: Fri Oct 18 10:49:11 MDT 2002
Log Message:
- debian/patches/0list: disable ip6-fix.dpatch. Closes: #165287
Files:
changed:0list
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
On Fri, Oct 18, 2002 at 05:58:53PM +0200, Per Lundberg wrote:
> The problem is that libc6-dbg is unpacked BEFORE libc6, and libc6
> 2.3.1-1 requires the new dynamic linked ld-linux.so.2 (which has not
> been installed yet). Thus, dpkg-dbg is unpacked correctly, but when
> trying to unpack libc6 (a
The update broke other packages as well.
For example, java reports
Error occurred during initialization of VM
Unable to load native library:
/usr/java/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol __libc_waitpid,
version GLIBC_2.0 not defined in file libc.so.6 with link time reference
I am not sur
Repository: glibc-package/debian
who:gotom
time: Fri Oct 18 10:49:11 MDT 2002
Log Message:
- debian/patches/0list: disable ip6-fix.dpatch. Closes: #165287
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
On Thu, Oct 17, 2002 at 10:38:43PM -0400, Aaron M. Ucko wrote:
> Package: libc6
> Version: 2.3.1-1
> Severity: important
> Tags: sid
>
> The call to dpkg --compare-versions in libc's postinst should compare
> against a higher version than 2.1.95-1; after upgrading to 2.3.1-1, I
> found that a lot
Package: libc6
Version: 2.3.1-1
Severity: critical
Justification: breaks unrelated software
Hi,
I yesterday upgraded glibc to the 2.3.1-1 release and suddenly my
fetchmail does not work complaining it cannot connect to local SMTP.
Downgrading all *libc* and locales Packages to 2.2.5-15 fixes tha
On Fri, Oct 18, 2002 at 11:55:21AM -0400, Jack Howarth wrote:
>What happened to the glibc 2.3.1-1 ppc deb packages built on
> voltaire yesterday? They showed up on incoming.debian.org and seemed
> to pass okay according to the log at buildd.debian.org but were
> never moved into sid. Are they
Subject: libc6: cannot login using ssh
Package: libc6
Version: 2.3.1-1
Severity: normal
Tags: sid
This problem is introduced when using libc6_2.3.1-1_i386.deb, when reinstalling
libc6_2.2.5-15_i386.deb the problem goes away.
When I try to login from a remote (woody) host to a sid host:
% ssh spi
Ben Collins <[EMAIL PROTECTED]> writes:
> Heh, restart display managers is outside the scope of libc. Restarting
> services is pushing it enough I think.
Hmm, I wonder if it would be saner to have some mechanism (perhaps
just a directory fed to run-parts?) for packages to register
themselves for
Package: libc6-dbg
Version: 2.3.1-1
Severity: critical
If libc6-dbg is installed, and /usr/lib/debug is the first line in
/etc/ld.so.conf, the upgrade from previous versions of libc6 to 2.3.1-1
breaks the system.
The problem is that libc6-dbg is unpacked BEFORE libc6, and libc6 2.3.1-1
requires t
On Fri, 2002-10-18 at 09:21, Jeff Bailey wrote:
On Fri, Oct 18, 2002 at 08:55:52AM -0400, Richard Black wrote:
> I realize that this is a somewhat known problem but with libc6 2.3.1,
> java 1.3.1 (even with the latest patch) does not run:
I think I read somewhere that IBM's latest 1.3.1
What happened to the glibc 2.3.1-1 ppc deb packages built
on voltaire yesterday? They showed up on incoming.debian.org
and seemed to pass okay according to the log at buildd.debian.org
but were never moved into sid. Are they on hold or something?
Jack
--
To UNSUBSCRIBE,
Repository: glibc-package/debian/sysdeps
who:jbailey
time: Fri Oct 18 09:51:33 MDT 2002
Log Message:
- debian/sysdeps/build-options.mk: Strip libc on alpha
Files:
changed:build-options.mk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
Repository: glibc-package/debian
who:jbailey
time: Fri Oct 18 09:51:33 MDT 2002
Log Message:
- debian/sysdeps/build-options.mk: Strip libc on alpha
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
On Fri, Oct 18, 2002 at 08:55:52AM -0400, Richard Black wrote:
> I realize that this is a somewhat known problem but with libc6 2.3.1,
> java 1.3.1 (even with the latest patch) does not run:
I think I read somewhere that IBM's latest 1.3.1 worked.
> Is there any way around this? If not, could a
Jeff Bailey <[EMAIL PROTECTED]> writes:
> On Thu, Oct 17, 2002 at 12:02:08AM +0200, Falk Hueffner wrote:
>
> > > Hmm...I can't recall right now why we chose to not strip it. You
> > > could always give it a go and see what happens. I'll dig through
> > > some old notes and see if I can come up
Repository: glibc-package/debian/libc/DEBIAN
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/p
Repository: glibc-package/debian/control.in
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/po
Repository: glibc-package/debian
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/postinst: War
Repository: glibc-package/debian/rules.d
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/posti
Repository: glibc-package/debian/packages.d
who:jbailey
time: Fri Oct 18 09:28:20 MDT 2002
Log Message:
glibc (2.3.1-2) unstable; urgency=low
* This is the "Why did everything stop working, mommy?" release
* Jeff Bailey <[EMAIL PROTECTED]>
- debian/libc/DEBIAN/po
Processing commands for [EMAIL PROTECTED]:
> close 165352
Bug#165352: Sun Java VM fails to start
Bug closed, send any further explanations to Jay Hap-hang Yu <[EMAIL PROTECTED]>
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On Fri, Oct 18, 2002 at 10:46:38PM +1000, Jay Hap-hang Yu wrote:
> Error occurred during initialization of VM
> Unable to load native library:
> /usr/local/sun/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol
> __libc_waitpid, version GLIBC_2.0 not defined in file libc.so.6 with
> link time reference
B
On Thu, Oct 17, 2002 at 12:02:08AM +0200, Falk Hueffner wrote:
> > Hmm...I can't recall right now why we chose to not strip it. You
> > could always give it a go and see what happens. I'll dig through
> > some old notes and see if I can come up with an answer as to why
> > we did that. I seem t
HI all,
I realize that this is a somewhat known problem but with libc6 2.3.1, java 1.3.1 (even with the latest patch) does not run:
$$ /usr/local/jdk1.3.1_05/bin/jar
Error occurred during initialization of VM
Unable to load native library: /usr/local/jdk1.3.1_05/jre/lib/i386/libjava.so:
Package: libc6
Version: 2.3.1-1
Severity: important
Running Sun's JDK 1.4.0. The following error message is shown when
"java" is executed:
Error occurred during initialization of VM
Unable to load native library:
/usr/local/sun/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol
__libc_waitpid, version GL
On Fri, Oct 18, 2002 at 06:01:35AM -0700, Jeff Bailey wrote:
> On Fri, Oct 18, 2002 at 10:46:38PM +1000, Jay Hap-hang Yu wrote:
>
> > Error occurred during initialization of VM
> > Unable to load native library:
> > /usr/local/sun/j2sdk1.4.0/jre/lib/i386/libjava.so: symbol
> > __libc_waitpid, vers
1 - 100 of 118 matches
Mail list logo
