Your message dated Tue, 05 Mar 2013 21:16:41 +0000 with message-id <1362518201.29720.15.camel@jacala.jungle.funky-badger.org> and subject line Re: Bug#690248: unblock: yforth/0.2.1-1 has caused the Debian Bug report #690248, regarding unblock: yforth/0.2.1-1 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.) -- 690248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690248 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: unblock: yforth/0.2.1-1
- From: Bdale Garbee <bdale@gag.com>
- Date: Thu, 11 Oct 2012 09:13:55 -0600
- Message-id: <87txu159e4.fsf@gag.com>
Package: release.debian.org Severity: normal Please unblock package yforth. This version is a new upstream release that fixes bug #687348 which was originally filed as RC but which I downgraded to important. The claim was that yforth had a non-free license, which I did not completely agree with. But the upstream author offered to re-license from a home-grown license to GPL v3 to eliminate any ambiguity in his intentions. The only other changes made by upstream were to roll in various patches I and others had provided in the many years since the last yforth upstream release, including a few suggestions I made on improvements to the Makefile to allow me to enable hardening build flags, etc. Since yforth is a leaf package that nothing else depends on, I hope you will agree that allowing it in to wheezy even if for no other reason than to eliminate the license freedom ambiguity pointed out in #687348 despite my downgrading of that bug to a non-RC severity is a good idea. Thanks for considering this! Regards, BdaleAttachment: pgp4emb9qjsYk.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: intrigeri <intrigeri@debian.org>, 690248-done@bugs.debian.org
- Cc: Bdale Garbee <bdale@gag.com>, Ivo De Decker <ivo.dedecker@ugent.be>
- Subject: Re: Bug#690248: unblock: yforth/0.2.1-1
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Tue, 05 Mar 2013 21:16:41 +0000
- Message-id: <1362518201.29720.15.camel@jacala.jungle.funky-badger.org>
- In-reply-to: <[🔎] 8538wcqhap.fsf@boum.org>
- References: <87txu159e4.fsf@gag.com> <20121228190408.GA13655@ugent.be> <87a9sxc0qm.fsf@gag.com> <[🔎] 8538wcqhap.fsf@boum.org>
On Sun, 2013-03-03 at 22:55 +0100, intrigeri wrote: > Bdale Garbee wrote (28 Dec 2012 21:42:25 GMT) : > > I don't care if this version promotes to wheezy or not. [...] > > Had the unblock request been processed when it was first made it > > probably would have been fine, but I see no reason to push on it at > > this point. > > Understood. > So, I recommend the release team closes this unblock request. At this stage, I have to agree. Apologies for not having resolved this one way or the other earlier. As an aside, yforth currently has out-of-date mips / s390 binaries in unstable (from 0.1beta-23) because, despite the change in -22 to use "any" in the architecture list, the package is still in Packages-arch-specific. Regards, Adam
--- End Message ---