Your message dated Fri, 19 Nov 2021 21:41:41 +0100 with message-id <YZgMBYs5avYi2nk3@ramacher.at> and subject line Re: Bug#994584: nmu: ricochet-im_1.1.4-3+b5 has caused the Debian Bug report #994584, regarding nmu: ricochet-im_1.1.4-3+b5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 994584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994584 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: ricochet-im_1.1.4-3+b5
- From: Paul Wise <pabs@debian.org>
- Date: Sat, 18 Sep 2021 13:58:56 +0800
- Message-id: <2978832bb92f1aca8d4f2889a4385a4a7b9185e0.camel@debian.org>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: binnmu Control: affects -1 + ricochet-im X-Debbugs-CC: ricochet-im@packages.debian.org Please rebuild ricochet-im in bullseye and unstable, the transition from GCC 9 to 10 seems to have changed the size of the C++ type Type which is breaking a runtime check of the size, the runtime error is: /usr/include/c++/9/bits/move.h:194:7: runtime error: load of value 279, which is not a valid value for type 'Type' I confirmed that rebuilding ricochet-im is enough to fix the error. The binNMUs that need scheduling are: nmu ricochet-im_1.1.4-3+b5 . ANY . bullseye . -m "Rebuild for the GCC 10 transition (Closes #992668)" nmu ricochet-im_1.1.4-3+b5 . ANY . unstable . -m "Rebuild for the GCC 10 transition (Closes #992668)" -- bye, pabs https://wiki.debian.org/PaulWiseAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Paul Wise <pabs@debian.org>, 994584-done@bugs.debian.org
- Subject: Re: Bug#994584: nmu: ricochet-im_1.1.4-3+b5
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Fri, 19 Nov 2021 21:41:41 +0100
- Message-id: <YZgMBYs5avYi2nk3@ramacher.at>
- In-reply-to: <c199cad8bbff2ef34d432689aa20fd1d4fee7c77.camel@debian.org>
- References: <2978832bb92f1aca8d4f2889a4385a4a7b9185e0.camel@debian.org> <2978832bb92f1aca8d4f2889a4385a4a7b9185e0.camel@debian.org> <c199cad8bbff2ef34d432689aa20fd1d4fee7c77.camel@debian.org>
On 2021-09-21 13:09:25 +0800, Paul Wise wrote: > On Sat, 18 Sep 2021 13:58:56 +0800 Paul Wise wrote: > > > nmu ricochet-im_1.1.4-3+b5 . ANY . unstable . -m "Rebuild for the GCC 10 transition (Closes #992668)" > > This appears to have been completed. > > > nmu ricochet-im_1.1.4-3+b5 . ANY . bullseye . -m "Rebuild for the GCC 10 transition (Closes #992668)" > > This doesn't appear to have been scheduled yet. Let's close this until we actually know what's causing #992668 Cheers -- Sebastian RamacherAttachment: signature.asc
Description: PGP signature
--- End Message ---