Différences entre versions de « Backport dar »
Sauter à la navigation
Sauter à la recherche
imported>SylvainBeucler m (better log message) |
|||
Ligne 11 : | Ligne 11 : | ||
par2cmdline (0.4-6bpo1) sarge-backports; urgency=low | par2cmdline (0.4-6bpo1) sarge-backports; urgency=low | ||
− | * | + | * Rebuild for Debian Backports <http://www.backports.org/> |
+ | (new version fixes a crash in silent -qq mode) | ||
-- Sylvain Beucler <beuc@beuc.net> Fri, 23 Jun 2006 13:30:34 +0000 | -- Sylvain Beucler <beuc@beuc.net> Fri, 23 Jun 2006 13:30:34 +0000 |
Version du 25 juin 2006 à 13:24
Backporting par2 is quite simple - you just need to recompile the Etch version in a Sarge environment. It's a nice occasion to cover the very basics.
You need to modify debian/changelog
though. Enter the par2cmdline-0.4 directory, and type:
dch -i
If you want to use another editor, you can also:
EDITOR=emacs dch -i
Here's my final changelog entry:
par2cmdline (0.4-6bpo1) sarge-backports; urgency=low * Rebuild for Debian Backports <http://www.backports.org/> (new version fixes a crash in silent -qq mode) -- Sylvain Beucler <beuc@beuc.net> Fri, 23 Jun 2006 13:30:34 +0000
What did I do?
- Changed version according to bpo convention, (debian version - 1)bpo1, so 0.4-7 -> 0.4.6bpo1
- Changed distributino from
unstable
tosarge-backports
- Added a terse explanation
- Replaced
root <root@sylvain>
with a real e-mail address.
Then, in the par2cmdline-0.4 directory, start the compilation.
debuild -us -uc
Using the -sa
debuild option: not necessary: by default, if the version ends with '0' or '1' (as 'bpo1' does), dpkg-buildpackage uses the existing source release (the .orig.tar.gz file must be present in the parent directory, though).