Your message dated Sat, 11 Aug 2012 14:14:56 +0200 with message-id <[email protected]> and subject line Re: Bug#684292: unblock pylucene/3.5.0-1.1 has caused the Debian Bug report #684292, regarding unblock pylucene/3.5.0-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 [email protected] immediately.) -- 684292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684292 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---
- To: Debian Bug Tracking System <[email protected]>
- Subject: unblock pylucene/3.5.0-1.1
- From: Luca Falavigna <[email protected]>
- Date: Wed, 8 Aug 2012 15:50:15 +0200
- Message-id: <[🔎] CADk7b0MkMTrKrQGUjqKr4VezxAvP+W0JFtkb5fGqb34Hq_4qRQ@mail.gmail.com>
Package: release.debian.org Severity: normal User: [email protected] Usertags: unblock Please unblock package pylucene It contains a fix for FTBFS bug #684084, builds are fine now. Debdiff of changes attached. unblock pylucene/3.5.0-1.1Attachment: pylucene-3.5.0-1.1-debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: Luca Falavigna <[email protected]>, [email protected]
- Subject: Re: Bug#684292: unblock pylucene/3.5.0-1.1
- From: Niels Thykier <[email protected]>
- Date: Sat, 11 Aug 2012 14:14:56 +0200
- Message-id: <[email protected]>
- In-reply-to: <[🔎] CADk7b0MtZOEEf4UaX6en1bH36NQUkh=aXqXz+262ZjLYJ1J-_A@mail.gmail.com>
- References: <[🔎] CADk7b0MkMTrKrQGUjqKr4VezxAvP+W0JFtkb5fGqb34Hq_4qRQ@mail.gmail.com> <[🔎] CADk7b0MtZOEEf4UaX6en1bH36NQUkh=aXqXz+262ZjLYJ1J-_A@mail.gmail.com>
On 2012-08-08 15:57, Luca Falavigna wrote: > 2012/8/8 Luca Falavigna <[email protected]>: >> It contains a fix for FTBFS bug #684084, builds are fine now. > > Err... correct bug is #679368. > > Unblocked, thanks. :) ~Niels
--- End Message ---