Processed: Re: Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable
Processing commands for cont...@bugs.debian.org: > reassign 964477 apt Bug #964477 [libc6-dev] libc6-dev: Fails to cleanly upgrade from Stable Bug reassigned from package 'libc6-dev' to 'apt'. No longer marked as found in versions glibc/2.28-10. Ignoring request to alter fixed versions of bug #964477 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 964477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable
reassign 964477 apt thanks On Sun, Jul 19, 2020 at 06:58:33PM +0200, Aurelien Jarno wrote: > On 2020-07-19 18:48, Helge Kreutzmann wrote: > > Hello Aurelien, > > sorry for answering late, I was a few days offline. > > > > On Sun, Jul 12, 2020 at 09:45:55PM +0200, Aurelien Jarno wrote: > > > On 2020-07-07 21:04, Helge Kreutzmann wrote: > > > > Package: libc6-dev > > > > Version: 2.28-10 > > > > Severity: important > > > > > > > > Until a few hours ago I run stable. Switching sources to testing and > > > > then > > > > apt-get update > > > > apt-get upgrade > > > > > > > > worked. Now: > > > > > > > > apt-get dist-ugprade tells me the following: > > > > > > > > root@samd:~# LC_ALL=C apt-get dist-upgrade > > > > Reading package lists... Done > > > > Building dependency tree > > > > Reading state information... Done > > > > Calculating upgrade... Error! > > > > Some packages could not be installed. This may mean that you have > > > > requested an impossible situation or if you are using the unstable > > > > distribution that some required packages have not yet been created > > > > or been moved out of Incoming. > > > > The following information may help to resolve the situation: > > > > > > > > The following packages have unmet dependencies: > > > > libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6 is to be > > > > installed > > > > E: Error, pkgProblemResolver::Resolve generated breaks, this may be > > > > caused by held packages. > > > > > > This break entry is correct, if we remove it gcc-8 will be left > > > potentially broken after the upgrade. I have no idea how it can be fixed > > > on the glibc side. > > > > Who would be the best party to fix this? (Sorry, at the moment I don't > > have a clue what causes this problem). > > I guess apt developers might be able to help there. > > > > > If I try to remove either libc6-dev or libgcc-8-dev then a long list of > > > > programms is scheduled for deinstallation, e.g. lots of KDE, okular, > > > > libreoffice etc. > > > > > > Have you tried installing gcc-defaults from testing before starting the > > > upgrade? > > > > I did an upgrade today (dist-upgrade is still broken) and for some > > strange reason I cannot install gcc-defaults: > > > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > E: Unable to locate package gcc-defaults > > > > I also get this in an current (unrelated) sid chroot. Strange. > > Oops sorry. gcc-defaults is the source package. You should try with one > of the corresponding binary packages, like gcc or g++. Ok, then this is not another local problem. However, it does not help. Installing gcc brings in a few packages but then dist-upgrade fails again the same way. g++ is already at the latest version. I reassign this bug to apt as suggested. Thanks for your support. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable
Hi, On 2020-07-19 18:48, Helge Kreutzmann wrote: > Hello Aurelien, > sorry for answering late, I was a few days offline. > > On Sun, Jul 12, 2020 at 09:45:55PM +0200, Aurelien Jarno wrote: > > On 2020-07-07 21:04, Helge Kreutzmann wrote: > > > Package: libc6-dev > > > Version: 2.28-10 > > > Severity: important > > > > > > Until a few hours ago I run stable. Switching sources to testing and > > > then > > > apt-get update > > > apt-get upgrade > > > > > > worked. Now: > > > > > > apt-get dist-ugprade tells me the following: > > > > > > root@samd:~# LC_ALL=C apt-get dist-upgrade > > > Reading package lists... Done > > > Building dependency tree > > > Reading state information... Done > > > Calculating upgrade... Error! > > > Some packages could not be installed. This may mean that you have > > > requested an impossible situation or if you are using the unstable > > > distribution that some required packages have not yet been created > > > or been moved out of Incoming. > > > The following information may help to resolve the situation: > > > > > > The following packages have unmet dependencies: > > > libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6 is to be > > > installed > > > E: Error, pkgProblemResolver::Resolve generated breaks, this may be > > > caused by held packages. > > > > This break entry is correct, if we remove it gcc-8 will be left > > potentially broken after the upgrade. I have no idea how it can be fixed > > on the glibc side. > > Who would be the best party to fix this? (Sorry, at the moment I don't > have a clue what causes this problem). I guess apt developers might be able to help there. > > > If I try to remove either libc6-dev or libgcc-8-dev then a long list of > > > programms is scheduled for deinstallation, e.g. lots of KDE, okular, > > > libreoffice etc. > > > > Have you tried installing gcc-defaults from testing before starting the > > upgrade? > > I did an upgrade today (dist-upgrade is still broken) and for some > strange reason I cannot install gcc-defaults: > > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package gcc-defaults > > I also get this in an current (unrelated) sid chroot. Strange. Oops sorry. gcc-defaults is the source package. You should try with one of the corresponding binary packages, like gcc or g++. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable
Hello Aurelien, sorry for answering late, I was a few days offline. On Sun, Jul 12, 2020 at 09:45:55PM +0200, Aurelien Jarno wrote: > On 2020-07-07 21:04, Helge Kreutzmann wrote: > > Package: libc6-dev > > Version: 2.28-10 > > Severity: important > > > > Until a few hours ago I run stable. Switching sources to testing and > > then > > apt-get update > > apt-get upgrade > > > > worked. Now: > > > > apt-get dist-ugprade tells me the following: > > > > root@samd:~# LC_ALL=C apt-get dist-upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Error! > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6 is to be > > installed > > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused > > by held packages. > > This break entry is correct, if we remove it gcc-8 will be left > potentially broken after the upgrade. I have no idea how it can be fixed > on the glibc side. Who would be the best party to fix this? (Sorry, at the moment I don't have a clue what causes this problem). > > If I try to remove either libc6-dev or libgcc-8-dev then a long list of > > programms is scheduled for deinstallation, e.g. lots of KDE, okular, > > libreoffice etc. > > Have you tried installing gcc-defaults from testing before starting the > upgrade? I did an upgrade today (dist-upgrade is still broken) and for some strange reason I cannot install gcc-defaults: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package gcc-defaults I also get this in an current (unrelated) sid chroot. Strange. Any help much appreciated (or pointers). Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Processed: Re: Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
Processing commands for cont...@bugs.debian.org: > severity 965091 important Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
severity 965091 important thanks Hi, On 2020-07-15 23:21, Thorsten Glaser wrote: > Package: libc6 > Version: 2.31-1 > Severity: grave > Justification: renders package unusable > > This is related to #965086 and #965087 (and, in fact, possibly > causing them). After a glibc upgrade half the system services > (postfix, sshd, apt-get(!)) don’t work any more. The set of packages involved in the glibc transition is ready and this bug is the only thing blocking the migration to testing. The patch fixing that issue is being developed upstream, but not fully ready yet. I am therefore downgraded the severity of this bug given that: - The x32 port is not an official port and doesn't have testing. Having this glibc package in testing won't change anything for that port. - The libc6-x32 is affected by the issue, but x32 syscalls are disabled by default in the debian kernels. This doesn't mean that the bug won't be fixed. Once the package has migrated to testing and we have a patch upstream, I'll do another upload fixing the issue. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#952516: please support LC_CTYPE=UTF-8
On 2020-02-25 10:04, Harald Dunkel wrote:
> Package: locales
> Version: 2.29-10
> Severity: wishlist
>
> Apparently MacOS 10.15 uses "UTF-8" instead of "C.UTF-8". This
> affects ssh terminal sessions from MacOS to Debian, e.g.
>
> # apt upgrade
> :
> :
> Processing triggers for mime-support (3.64) ...
> Processing triggers for libc-bin (2.29-10) ...
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LC_CTYPE = "UTF-8",
> LC_COLLATE = "C",
> LANG = "C"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LC_CTYPE = "UTF-8",
> LC_COLLATE = "C",
> LANG = "C"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> The workaround is to run
>
> localedef -i C -f UTF-8 UTF-8
>
> on Debian, but probably others are affected by this problem
> as well. A central solution would be reasonable.
>
> Do you think it would be possible to introduce "UTF-8" as an
> alias for "C.UTF-8"?
MacOS is wrong there. We definitely do no want to introduce such a local
in an uncoordinated way, as it will make things way more difficult to
rollback instead. Have you reported the issue to Apple?
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Bug#965323: postinst script deletes custom locales
control: tag -1 + wontfix On 2020-07-19 15:55, Harald Dunkel wrote: > Package: locales > Version: 2.28-10 > > To support MacOS terminal I have to define "UTF-8" using localedef (see > #952516). > Problem is, custom locales are wiped out by the postinst script. Sample: > > # locale -a > C > C.UTF-8 > POSIX > # localedef -i C -f UTF-8 UTF-8 > # locale -a > C > C.UTF-8 > POSIX > UTF-8 > UTF-8.utf8 > # apt reinstall locales > : > : > # locale -a > C > C.UTF-8 > POSIX > > See UTF-8 is gone? Shouldn't happen. Yes, that's normal. locales might not be compatible with the new glibc version, so all of them are removed and regenerated on upgrade. Otherwise you might end up with broken locales causing issues. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#965323: postinst script deletes custom locales
Processing control commands: > tag -1 + wontfix Bug #965323 [locales] postinst script deletes custom locales Added tag(s) wontfix. -- 965323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965323: postinst script deletes custom locales
Package: locales Version: 2.28-10 To support MacOS terminal I have to define "UTF-8" using localedef (see #952516). Problem is, custom locales are wiped out by the postinst script. Sample: # locale -a C C.UTF-8 POSIX # localedef -i C -f UTF-8 UTF-8 # locale -a C C.UTF-8 POSIX UTF-8 UTF-8.utf8 # apt reinstall locales : : # locale -a C C.UTF-8 POSIX See UTF-8 is gone? Shouldn't happen. Same for locales 2.31-1. Harri
