Your message dated Tue, 21 Feb 2012 09:51:56 +0000
with message-id <[email protected]>
and subject line Bug#660548: Removed package(s) from unstable
has caused the Debian Bug report #52711,
regarding yada util to generate patches
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.)
--
52711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52711
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: yada
Version: 0.9
Severity: wishlist
I use the Patches: line for all my packages to keep my changes in distinct
and clearly identifiable patch files. However, generating a patch file is
a pain:
- copy the file you want to modify in file.orig
- edit file
- diff -u file.orig file > debian/newpatch.dpatch
- edit debian/newpatch.dpatch to add #PATCHOPTIONS: -p0
- move file.orig to file back
Now, let's imagine that yada makes a build-directory (under debian/ maybe)
and builds everything in this build-directory after making a copy of the
source. This would let the source untouched. If I want to modify "file",
I could go in the build-directory, where I could find the package source
already patched by the other patches. I can then modify "file" there,
and launch "yada makepatch debian/newpatch.dpatch". yada would compare
the current sources against the pristine sources (found just above) + the
other patches already applied, and generate a new patch file
debian/newpatch.dpatch containing the difference made to "file", with the
right PATCHOPTIONS added.
Well, that's not easy to explain, but did you get the idea?
Moreover, the idea of having a debian/build-directory is that making a
"debuild clean" is easier: just remove debian/build-directory, debian/tmp-*,
debian/*-stamp, etc.
One more reason to do this is that I have packages that modify binary files
that belong to the distribution (and that are needed to build the package,
such as byte codes for building Erlang). In my scripts, I have to preserve
the original files at the beginning of the build and restore them at
clean time. This is painful.
-- System Information
Debian Release: potato
Architecture: i386
Kernel: Linux antinea 2.2.13 #1 Mon Nov 8 12:40:02 CET 1999 i686
Versions of packages yada depends on:
ii dpkg-dev 1.6.3 Package building tools for Debian
ii perl-5.004 [perl5] 5.004.05-3 Larry Wall's Practical Extracting
ii perl-5.005 [perl5] 5.005.03-4 Larry Wall's Practical Extracting
--- End Message ---
--- Begin Message ---
Version: 0.55+rm
Dear submitter,
as the package yada has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/660548
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)
--- End Message ---
