Your message dated Mon, 14 Mar 2011 21:03:35 +0100
with message-id <[email protected]>
and subject line done: common source package created
has caused the Debian Bug report #602824,
regarding lilo: create a common source package
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.)
--
602824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602824
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lilo
Version: 1:22.8-8.3
Severity: wishlist
Hello dear maintainers,
As said in the above subject, the idea comes from the following
discussion in the below bug
https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/669363
which essentially states that applying patches can be easier with a
common source package and sebastien's idea also came from the below
article
http://raphaelhertzog.com/2010/11/05/managing-distribution-specific-patches-with-a-common-source-package/
which requires only a source format change to 3.0(quilt)
Regards
--
Bhavani Shankar.R
https://launchpad.net/~bhavi, a proud ubuntu community developer.
What matters in life is application of mind!,
It makes great sense to have some common sense..!
--- End Message ---
--- Begin Message ---
Source: lilo
Source-Version: 1:23.1-1
We believe that the bug you reported is fixed in the latest version of
lilo, which is due to be installed in the Debian FTP archive:
lilo-doc_23.1-1_all.deb
to main/l/lilo/lilo-doc_23.1-1_all.deb
lilo_23.1-1.debian.tar.gz
to main/l/lilo/lilo_23.1-1.debian.tar.gz
lilo_23.1-1.dsc
to main/l/lilo/lilo_23.1-1.dsc
lilo_23.1-1_i386.deb
to main/l/lilo/lilo_23.1-1_i386.deb
lilo_23.1.orig.tar.gz
to main/l/lilo/lilo_23.1.orig.tar.gz
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Joachim (Germany)
--- End Message ---
