Bug#675034: marked as done (RFS: burp/1.3.6-1)
Your message dated Wed, 30 May 2012 04:14:13 +0000
with message-id <E1SZaIX-0002NP-Qe@ravel.debian.org>
and subject line closing RFS: burp/1.3.6-1
has caused the Debian Bug report #675034,
regarding RFS: burp/1.3.6-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.)
--
675034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675034
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "burp"
* Package name : burp
Version : 1.3.6-1
Upstream Author : Graham Keeling <keeling@spamcop.net>
* URL : http://burp.grke.net/
* License : AGPLv3
Section : utils
It builds those binary packages:
burp - Simple cross-platform network BackUp and Restore Program
burp-dbg - debugging symbols for Burp
To access further information about this package, please visit the following URL:
http://mentors.debian.net/package/burp
Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/b/burp/burp_1.3.6-1.dsc
More information about hello can be obtained from http://www.example.com.
Changes since the last upload:
burp (1.3.6-1) unstable; urgency=low
* New upstream release version 1.3.6
* Removed unneeded Lintian Overides
* Update copyrights file to new standard
-- Bastiaan Franciscus van den Dikkenberg <bas@dikkenberg.net> Tue, 29 May 2012 13:29:44 +0200
Regards,
Bas van den Dikkenberg
--- End Message ---
--- Begin Message ---
Package burp version 1.3.6-1 is in unstable now.
http://packages.qa.debian.org/burp
--- End Message ---
Reply to: