Différences entre versions de « Backport wireless-tools »
imported>SylvainBeucler m |
imported>SylvainBeucler m |
||
| Ligne 2 : | Ligne 2 : | ||
debhelper was already backported so you just have to install it: | debhelper was already backported so you just have to install it: | ||
aptitude install debhelper/sarge-backports | aptitude install debhelper/sarge-backports | ||
| + | |||
| + | Beware though that when using dh_gconf (eg for Gnome packages), there is a [http://lists.backports.org/lurker/message/20060830.124936.32b7cb6f.en.html bug]. What's its status now? | ||
| + | |||
| + | |||
| + | Trick 1: to see your backports in your Debian QA page (eg [http://qa.debian.org/developer.php?login=beuc@beuc.net]), add your e-mail in the <code>debian/control</code> files as well: | ||
| + | Uploaders: Sylvain Beucler <beuc@beuc.net> | ||
| + | (source: [http://backports.org/dokuwiki/doku.php?id=contribute]) | ||
Then, the package builds cleanly: | Then, the package builds cleanly: | ||
| Ligne 7 : | Ligne 14 : | ||
debuild -us -uc | debuild -us -uc | ||
| − | + | ||
| + | Trick 2: you may want to includes the last 2 changelog entries in his your .changes files (yours + the last upstream one, instead of just yours). This is nice, because you know what improvements you can get just by reading the mail notification: | ||
| + | |||
| + | debuild -us -uc -v27+28pre16-1 | ||
| + | |||
| + | Currently you need to manually specify the version, I don't know of an automated way to do so, even though it's shouldn't be hard to do. | ||
Version du 8 octobre 2006 à 02:23
This one is as simple as Backport dar, except that there is a missing build dependency from stable: debhelper 5. debhelper was already backported so you just have to install it:
aptitude install debhelper/sarge-backports
Beware though that when using dh_gconf (eg for Gnome packages), there is a bug. What's its status now?
Trick 1: to see your backports in your Debian QA page (eg [1]), add your e-mail in the debian/control files as well:
Uploaders: Sylvain Beucler <beuc@beuc.net>
(source: [2])
Then, the package builds cleanly:
dch -i debuild -us -uc
Trick 2: you may want to includes the last 2 changelog entries in his your .changes files (yours + the last upstream one, instead of just yours). This is nice, because you know what improvements you can get just by reading the mail notification:
debuild -us -uc -v27+28pre16-1
Currently you need to manually specify the version, I don't know of an automated way to do so, even though it's shouldn't be hard to do.