Bug#1000421: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-12-04 Thread Guillem Jover
Hi! On Sat, 2021-12-04 at 23:09:19 +, Ian Jackson wrote: > Joachim: > > I'm aware of that. And "shortly" definitely means "before the > > autoremoval" (which is currently scheduled for 2022-01-01). > > The real deadline is when I ought to take action myself, as someone > adversely affected

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-12-04 Thread Ian Jackson
Joachim: > I'm aware of that. And "shortly" definitely means "before the > autoremoval" (which is currently scheduled for 2022-01-01). The real deadline is when I ought to take action myself, as someone adversely affected by an RC bug. The timeline for fixing this is: NMU DELAYED-10 upload of

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-12-01 Thread Joachim Reichel
Hi Ian, On 28.11.21 19:21, Ian Jackson wrote: Joachim Reichel (cppcheck maintainer): I'll upload a new version cppcheck with a workaround shortly Would you mind both prioritising this fix ? FTAOD it's not just cppcheck that is scheduled for autoremoval. Any package which transitively

Bug#1000421: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-28 Thread Ian Jackson
Guillem Jover: > Bug #1000421 in package dpkg reported by you has been fixed in > the dpkg/dpkg.git Git repository Thanks for the investigation. What a nuisance. Joachim Reichel (cppcheck maintainer): > I'll upload a new version cppcheck with a workaround shortly Would you mind both

Processed: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1000146 pending Bug #1000146 [cppcheck] cppcheck: incorrect dependencies: libc6 should be >= 2.32 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000146: https://bugs.debia

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-27 Thread Joachim Reichel
The root case of the problem has now been identified (see bug #100421). I'll upload a new version cppcheck with a workaround shortly (and before the autoremoval kicks in) -- just wanting to wait a bit more for a potential new upstream release. Best regards, Joachim

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-21 Thread Joachim Reichel
severity 1000146 serious thanks Hi Alejandro, I was able to reproduce the problem. It's unclear to me why "${shlibs:Depends}" does not produce a ">= 2.32" constraint and I've asked on the debian-mentors list for comments. Obviously, I could add that constraint manually, but I would first

Processed: Re: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1000146 serious Bug #1000146 [cppcheck] cppcheck: incorrect dependencies: libc6 should be >= 2.32 Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 10001

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

2021-11-18 Thread Alejandro Colomar
Package: cppcheck Version: 2.6-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: colomar.6@gmail.com Dear Maintainer, I installed and run cppcheck on a system which I had not used for half a year. For that reason, many of its packages were outdated. glibc was on