Your message dated Sun, 26 Mar 2017 19:01:00 +0000 with message-id <48fcdd16-3210-71bf-1c54-b8cd29a9b5eb@thykier.net> and subject line Re: Bug#858585: unblock: nickle-2.79-2 has caused the Debian Bug report #858585, regarding unblock: nickle-2.79-2 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.) -- 858585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858585 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: nickle-2.79-2
- From: keithp@keithp.com ("Keith Packard")
- Date: Fri, 24 Mar 2017 06:39:42 +0100
- Message-id: <[🔎] 86o9wr44ip.fsf@hiro.keithp.com>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package nickle. I believe this was blocked as there were three uploads in the last few days? Let me explain why that was the case: 1. nickle 2.78-1 contained a fix for FTBFS bugs 857814, 857815 and 857840, along with a few other upstream fixes and features: * Add sudoku generator and solver example. * Fix write order of large queued data. * Add JSON input/output library. * Use release date in configure.in instead of `date` * Initialize 'replace' in NewTypedBox. (Closes: #857840, #857814, #857815) * Adapt test to new automake. The diffstat from the upstream changes (aside from the two additions of example code) show that this was not a major upstream release: 21 files changed, 110 insertions(+), 63 deletions(-) 2. nickle 2.79-1 contained a single fix for a sparc64 bus error on application startup which was found by the buildd run for 2.78-1, and which was also present in 2.77-1. * Fix bus error on sparc64 due to unaligned DataCache. 1 file changed, 6 insertions(+), 2 deletions(-) 3. nickle 2.79-2 has some packaging changes which fix a handful of lintian issues and has no changes outside of the debian directory. Failing to unblock 2.79-2 will cause nickle to be removed from stretch because of the FTBFS bugs in 2.77-1. That would then cause all packages depending on it to also be removed, including altos, which a number of people using Altus Metrum rocketry products depend on. Thanks for your consideration in this matter. -- -keithAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Keith Packard <keithp@keithp.com>, 858585-done@bugs.debian.org
- Subject: Re: Bug#858585: unblock: nickle-2.79-2
- From: Niels Thykier <niels@thykier.net>
- Date: Sun, 26 Mar 2017 19:01:00 +0000
- Message-id: <48fcdd16-3210-71bf-1c54-b8cd29a9b5eb@thykier.net>
- In-reply-to: <[🔎] 86o9wr44ip.fsf@hiro.keithp.com>
- References: <[🔎] 86o9wr44ip.fsf@hiro.keithp.com>
Keith Packard: > > Package: release.debian.org > Severity: normal > User: release.debian.org@packages.debian.org > Usertags: unblock > > Please unblock package nickle. > > I believe this was blocked as there were three uploads in the last few > days? Let me explain why that was the case: > > [...] > > 3. nickle 2.79-2 has some packaging changes which fix a handful of > lintian issues and has no changes outside of the debian directory. > > Failing to unblock 2.79-2 will cause nickle to be removed from stretch > because of the FTBFS bugs in 2.77-1. That would then cause all packages > depending on it to also be removed, including altos, which a number of > people using Altus Metrum rocketry products depend on. > > Thanks for your consideration in this matter. > I have unblocked nickle 2.79-2. Admittedly, I would have preferred if it had been without the debhelper compat bump. Please keep this in mind for future uploads that are targeted for stretch. Thanks, ~Niels
--- End Message ---