[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#992653: glibc breaks openconnect autopkgtest: FAIL: auth-nonascii



On Sun, 22 Aug 2021 01:05:25 +0200 Aurelien Jarno
<aurelien@aurel32.net> wrote:
> control: tag -1 patch
> 
> Hi,
> 
> On 2021-08-21 21:52, Paul Gevers wrote:
> > Source: glibc, openconnect
> > Control: found -1 glibc/2.31-16
> > Control: found -1 openconnect/8.10-2
> > Severity: serious
> > Tags: sid bookworm
> > X-Debbugs-CC: debian-ci@lists.debian.org
> > User: debian-ci@lists.debian.org
> > Usertags: breaks needs-update
> > 
> > Dear maintainer(s),
> > 
> > With a recent upload of glibc the autopkgtest of openconnect fails
in
> > testing when that autopkgtest is run with the binary packages of
glibc
> > from unstable. It passes when run with only packages from testing.
In
> > tabular form:
> > 
> >                        pass            fail
> > glibc                  from testing    2.31-16
> > openconnect            from testing    8.10-2
> > versioned deps [0]     from testing    from unstable
> > all others             from testing    from testing
> > 
> > I copied some of the output at the bottom of this report.
Unfortunately,
> > the log is rather brief.
> > 
> > Currently this regression is blocking the migration of glibc to
testing
> > [1]. Due to the nature of this issue, I filed this bug report
against
> > both packages. Can you please investigate the situation and
reassign the
> > bug to the right package?
> 
> The openconnect auth-nonascii test uses two locales for its tests:
> cs_CZ.UTF-8 and cs_CZ.ISO8859-2. It get those locales from the
> locales-all package. Starting with glibc 2.31-14, non-UTF-8 locales
are
> deprecated and not provided anymore by locales-all. Therefore the
test
> fails as the cs_CZ.ISO8859-2 is not available anymore.
> 
> One option would simply be to disable the test with the
cs_CZ.ISO8859-2
> locale as done in the attached patch. If non-UTF-8 locales are not
> supported anymore, I don't think we need to test them.
> 
> Also please note that while this new glibc broke the openconnect
> testsuite, it didn't break openconnect itself which is still
functional
> from the user point of view. In that regard there is no need to
declare
> a Breaks: openconnect on the glibc side.
> 
> Regards,
> Aurelien

Hi,

Thanks for the analysis - are these locales installed by alternative
packages? Or completely gone?

-- 
Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: