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 {
"libc6";
};
On Tue, 18 Oct 2022 at 09:23, Emilio Pozuelo Monfort <[email protected]>
wrote:
> 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/510754/import/import.1
> >
> > iconv: relocation error: iconv: symbol __gconv_create_spec version
> GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
>
> Any particular reason you upgraded libc-bin but not libc6?
>
> Cheers,
> Emilio
>
--
*Guillaume Lefranc* | Director of Engineering - Technical Operations
[email protected] | +33 6 82 42 58 93 <+4930609858366>
www.productsup.com
*Products Up GmbH*
A globally operative company - *office locations*
<https://www.productsup.com/home/#contact-form__container>
HQ: Alex-Wedding-Str. 5, 10178 Berlin, Germany
HRB 214376 B Berlin Charlottenburg; VAT ID DE270578435; Tax No. 30/479/35480
