Control: tags -1 + confirmed
On Tue, Oct 18, 2022 at 09:13:05AM +0200, Guillaume Lefranc wrote:
> after upgrading libc-bin from 2.28-10+deb10u1 to 2.28-10+deb10u2, the
> following error appeared after running iconv the following way:
>
> iconv -cs -f 'UTF-8' -t 'UTF-8' /tmp/510754/import/import.
I think it was when a libc6 update broke NSS sometime in 2017, though I can
find only a reference to it in the Ubuntu bug tracker.
https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu6
We could certainly unblacklist libc6 or blacklist both. I personally think
libc-bin should depend on an equiva
On 18/10/2022 11:59, Guillaume Lefranc wrote:
Yes.
The upgrade was automatically done by unattended-upgrades, but we have
libc6 blacklisted due to issues we encountered previously
What kind of issues? Are they still relevant? Is there a bug report we could
look at?
In this case, I suggest yo
Yes.
The upgrade was automatically done by unattended-upgrades, but we have
libc6 blacklisted due to issues we encountered previously
Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
};
Unattended-Upgrade::Package-Blacklist {
"libc
On 18/10/2022 09:13, Guillaume Lefranc wrote:
Package: libc-bin
Version: 2.28-10+deb10u2
Severity: normal
Dear Maintainer,
after upgrading libc-bin from 2.28-10+deb10u1 to 2.28-10+deb10u2, the following
error appeared after running iconv the following way:
iconv -cs -f 'UTF-8' -t 'UTF-8' /tmp
Package: libc-bin
Version: 2.28-10+deb10u2
Severity: normal
Dear Maintainer,
after upgrading libc-bin from 2.28-10+deb10u1 to 2.28-10+deb10u2, the following
error appeared after running iconv the following way:
iconv -cs -f 'UTF-8' -t 'UTF-8' /tmp/510754/import/import.1
iconv: relocation error
6 matches
Mail list logo
