reopen 836262 thanks On Thu, 1 Sep 2016 10:04:37 +0200, Rene Engelhard <r...@debian.org> wrote:
> [ not libnihs maintainer ] so why did you take it upon yourself to close this bug? > Welcome in unstable. This is normal in unstable. > > No bug here and will sort out itself by rebuilding it (so a +b2). wrong. there is a bug. and it still isn't "sorted out". "sorting out" doesn't happen magically all by itself, it takes action. often in response to a bug report. one of the reasons that unstable exists is so that people can test it **AND REPORT BUGS**. Reporting bugs for packages in unstable is completely normal. a snarky comment "welcome to unstable" is NOT sufficient reason to close this or any other bug. This bug report should stay open until libnih1 has actually been recompiled against libc6 2.24 and uploaded to ftp-master. or anything else that actually resolves the bug rather than ignoress it. it's not a trivial bug either - given that it breaks cgmanager (by forcing it to be uninstalled) AND everything that depends on it (including most containerisation tools), this would be a release critical bug if we were nearing freeze for stretch. craig ps: i've been holding back on upgrading libc6 in sid precisely because of this bug. After waiting over a week for the magic sorting-out fairies to perform their usual miracles, i investigated further to find out that libnih1 was the cause, then checked the BTS system to see if it had already been reported. it had. and was almost immediately closed by someone other than the maintainer for no good reason. -- craig sanders <c...@taz.net.au>
