Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
** Changed in: libc (Ubuntu)
Sourcepackagename: None => libc
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
same bug for upgrade from gutsy to hoardy =/
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Meushi: Nominate it for hardy.
I'm a bit disappointed that nobody investigated this, too. Did you try
my workaround? Does it still work?
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Why did nobody ever ask me anything about this bug?
I reproduced it several times!
Well, if this is still the case, you all will find out the hard way on
the 18th of Oct.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because yo
This bug could turn out to be a big embarrassment for Ubuntu. Just like
the X breakage that leaded to developing unbreakable X. Somebody better
have a look on this!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a
Why did you subscribe me to this bug? I don't work on libc6 and I've no
idea about this bug. It's likely a local issue or due to something you
are doing or we would have received other duplicates
** Changed in: glibc (Ubuntu)
Sourcepackagename: libc => glibc
--
libc6 and/or libc6-i686 upgrade fa
I have reproduced this bug on a machine here - rendering it completely useless.
But: I have a backup which I could restore. The machine is in the state from
right before the backup.
I am willing to supply information to help solve this bug!
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.l
Maybe this is of further interest:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/88673
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
It seems as if reinstalling _all_ libs in /libs doesn't help.
I used this
for i in "e2fslibs" "libacl1" "libattr1" "libblkid1" "libbz2-1.0" "libc6"
"libcap1" "libcomerr2" "libconsole" "libdevmapper1.02" "libgcc1" "libiw28"
"libklibc" "libncurses5" "libncursesw5" "libnss-ldap" "libnss-mdns" "lib
I also got this behaviour with a feisty system.
Richte libhal-storage1 ein (0.5.9.1-6ubuntu5) ...
Richte libdb4.2 ein (4.2.52+dfsg-2ubuntu1) ...
Richte libglu1-mesa ein (7.0.1-1ubuntu3) ...
Richte eject ein (2.1.5-2ubuntu2) ...
Richte psmisc ein (22.5-1) ...
Richte libc6-i686 ein (2
Okay! Here is what worked for me.
Get the packages
libc6_2.6.1-1ubuntu10_i386.deb
libc6-i686_2.6.1-1ubuntu10_i386.deb
from a gutsy system.
Remove libc6-i686 and ubuntu-minimal:
# aptitude purge libc6-i686 ubuntu-minimal
This _will_ put out error messages. The directory /lib/tls/i606/cmov c
I nominated this for feisty, since the problem seems to be in the
removal procedure of libc6-i686.
- installing the 2.6.1 libc6-i686 from gutsy works even with feisty
- deinstalling of libc6-i686 leaves files behind
- upgrading from feisty libc6-i686 to gutsy libc6-i686 does not work
Sorry that no-one got back to you on this. Unfortunately, neither Feisty
nor Gutsy are supported anymore. Can you confirm if this is still a
problem in a supported version, preferably Jaunty? Thank you.
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
libc6 and/or libc6-i686 upg
I do not have the backup of the machine anymore. I don't think I can supply
information for this matter anymore.
If something related breaks during the next update then I'll get back to this
bug. ;-)
I suggest: Close.
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/13633
No problem guys. Thanks for updating us, and good luck!
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
--
libc6 and/or libc6-i686 upgrade fail
https://bugs.launchpad.net/bugs/136337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
erf, actually it's been a year now.
feisty and gutsy are forgotten for long, and i can't tell for jaunty
as i've moved to a distro that fits me better.
i wish you good luck anyway.
bye.
On Thu, May 28, 2009 at 11:58 PM, Teej wrote:
> Sorry that no-one got back to you on this. Unfortunately, neith
96 matches
Mail list logo
