Processed: Re: Bug#903389: glibc/2.27-4 appears to break unrar-free/1:0.0.1+cvs20140707-4 autopktest: different Valgrind status codes

2018-07-10 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 valgrind Bug #903389 [src:glibc, src:unrar-free] glibc/2.27-4 appears to break unrar-free/1:0.0.1+cvs20140707-4 autopktest: different Valgrind status codes Bug reassigned from package 'src:glibc, src:unrar-free' to 'valgrind'. Ignoring request to alter

Bug#903389: glibc/2.27-4 appears to break unrar-free/1:0.0.1+cvs20140707-4 autopktest: different Valgrind status codes

2018-07-10 Thread Aurelien Jarno
control: reassign -1 valgrind control: retitle -1 valgrind can't read debug info from binaries built with -z separate-code control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=395682 control: severity -1 important control: affects -1 libc6 Hi, On 2018-07-10 12:04, Andre Naujoks wrote: >

Bug#903389: glibc/2.27-4 appears to break unrar-free/1:0.0.1+cvs20140707-4 autopktest: different Valgrind status codes

2018-07-10 Thread Andre Naujoks
Hi. Just my two cents. I think this might be the same as this: https://bugs.kde.org/show_bug.cgi?id=395682 and respectively https://sourceware.org/bugzilla/show_bug.cgi?id=23357 It seems a default option for ld (-z separate-code) was changed, which makes valgrind unable to read the binaries

Bug#903389: glibc/2.27-4 appears to break unrar-free/1:0.0.1+cvs20140707-4 autopktest: different Valgrind status codes

2018-07-10 Thread Aurelien Jarno
On 2018-07-09 13:00, Paul Gevers wrote: > Source: glibc, unrar-free > Version: glibc/2.27-4 > Version: unrar-free/1:0.0.1+cvs20140707-4 > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainers, > > With a recent upload of glibc the autopkgtest of unrar-free started