Processed: reassign 872201 to libapt-pkg5.0

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 872201 libapt-pkg5.0
Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while 
processing triggers
Bug reassigned from package 'libc-bin' to 'libapt-pkg5.0'.
No longer marked as found in versions glibc/2.24-14.
Ignoring request to alter fixed versions of bug #872201 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Aurelien Jarno]

control: forcemerge 871275 -1

On 2017-08-19 11:58, Andreas Beckmann wrote:
> >   terminate called after throwing an instance of 'std::logic_error'
> > what():  basic_string::_M_construct null not valid
> 
> Could this be related to #871275 "libapt-pkg5.0: requires rebuild
> against GCC 7 and symbols/shlibs bump" which was fixed recently in apt?
> IIRC this started after making gcc-7 the default ... I'll look if there
> are new occurrences of this bug.

Ok, I am merging the two bugs.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed (with 1 error): Re: Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 871275 -1
Bug #871275 {Done: Julian Andres Klode } [libapt-pkg5.0] 
libapt-pkg5.0: requires rebuild against GCC 7 and symbols/shlibs bump
Unable to merge bugs because:
package of #872201 is 'libc-bin' not 'libapt-pkg5.0'
Failed to forcibly merge 871275: Did not alter merged bugs.


-- 
871275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871275
872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#870889: Depends: libc-bin (> 2.25) but 2.24-14 is installed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #870889 [locales] Depends: libc-bin (> 2.25) but 2.24-14 is installed
Added tag(s) moreinfo.

-- 
870889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#870889: Depends: libc-bin (> 2.25) but 2.24-14 is installed

[Axel Beckert]

Control: tag -1 + moreinfo

Hi Jidanni,

積丹尼 Dan Jacobson wrote:
> Package: locales
> Severity: important

You didn't specify the package version.

>  locales : Depends: libc-bin (> 2.25) but 2.24-14 is installed

So this is very likely from locales version 2.25-0experimental0 as
currently in Debian Experimental. Please confirm that suspected
version number or tell us which other version you're using.

> The following actions will resolve these dependencies:
> 
>  Keep the following packages at their current version:
> 1) locales [2.24-14 (now, unstable)]

So what is the problem and where's the bug?

If you install locales from experimental, you should also install
libc-bin from experimental.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Andreas Beckmann]

>   terminate called after throwing an instance of 'std::logic_error'
> what():  basic_string::_M_construct null not valid

Could this be related to #871275 "libapt-pkg5.0: requires rebuild
against GCC 7 and symbols/shlibs bump" which was fixed recently in apt?
IIRC this started after making gcc-7 the default ... I'll look if there
are new occurrences of this bug.


Andreas

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Andreas Beckmann]

Control: severity -1 important

On 2017-08-19 10:29, Aurelien Jarno wrote:
> Any news about this? This bug now blocks the migration of glibc to
> testing.

Downgrading.

Andreas

Processed: Re: Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while 
processing triggers
Severity set to 'important' from 'serious'

-- 
872201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Aurelien Jarno]

On 2017-08-16 11:54, Aurelien Jarno wrote:
> On 2017-08-16 02:41, Andreas Beckmann wrote:
> > [ adding apt@, therefore quoting fully ]
> > 
> > On 2017-08-15 22:56, Aurelien Jarno wrote:
> > > control: tag - 1 + help
> > > control: tag - 1 + moreinfo
> > > 
> > > On 2017-08-15 09:58, Andreas Beckmann wrote:
> > >> Package: libc-bin
> > >> Version: 2.24-14
> > >> Severity: serious
> > >> User: debian...@lists.debian.org
> > >> Usertags: piuparts
> > >>
> > >> Hi,
> > >>
> > >> during several tests with piuparts in sid I noticed spurious and
> > >> unreproducible errors while processing libc-bin triggers.
> > >> Often apt-get just exits with an error code (but no error message
> > >> at all) after processing the triggers.
> > >> A few times I also get an error message about an uncaught exception.
> > >> These failures usually go away after rerunning the test.
> > >>
> > >> >From the attached log (scroll to the bottom...):
> > >>
> > >>   Processing triggers for libc-bin (2.24-14) ...
> > >>   terminate called after throwing an instance of 'std::logic_error'
> > >> what():  basic_string::_M_construct null not valid
> > > 
> > > What make you think it's an issue in libc-bin? The trigger processing
> > > code just does:
> > > 
> > > if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then
> > >   ldconfig || ldconfig --verbose
> > >   exit 0
> > > fi
> > > 
> > > And there is no C++ code in ldconfig. Moreover even if ldconfig fails
> > > the error is ignored and the install should not stop.
> > 
> > OK, that probably leaves dpkg (no C++ either) and apt-get as the call
> > chain to the trigger processing ... adding apt@ to the loop.
> > #871275 could be a candidate, i.e. a g++7 rebuild might fix it.
> > 
> > I reran the test where I attached the logfile yesterday repeatedly for
> > 100 times with no failure. But I could probably dig out a dozen of
> > similar failures from other piuparts tests. (These failures will be
> > retried frequently, so will eventually succeed.)
> > 
> > If there is some way to get more debug output for this problem, I could
> > enable that globally in my piuparts instance.
> 
> I guess you can try to get a core dump. Just make sure that you run
> "ulimit -c unlimited" before running the command. The core dump will
> tell you which binary actually has the issue and should provide more
> info about the issue.

Any news about this? This bug now blocks the migration of glibc to
testing.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net