Backport wireless-tools - Historique des versions

imported>SylvainBeucler : /* Upload */

2006-10-18T13:21:10Z

Upload

2006-10-08T11:27:26Z

Upload

2006-10-08T10:57:35Z

2006-10-08T10:57:15Z

2006-10-08T10:56:27Z

Upload

2006-10-08T07:53:37Z

Upload

2006-10-08T07:44:57Z

2006-10-08T00:23:40Z

2006-10-04T14:33:55Z

2006-10-04T14:33:34Z

@@ Ligne 37 : / Ligne 37 : @@
 kaol also suggested to so a source-only package, since your sponsor will rebuild the package anyway:
-  debuild -S
+  debuild -S -sa
   dput mentors wireless-tools_28-1~bpo.1_source.changes

← Version précédente		Version du 8 octobre 2006 à 11:27
Ligne 41 :		Ligne 41 :

	For the same reason, there's no issue with uploading an orig.tar.gz file even if there's already one at bpo.		For the same reason, there's no issue with uploading an orig.tar.gz file even if there's already one at bpo.
		+
		+	When you're done, please send a direct link to the .dsc file, as given by mentors.d.o's template generator:
		+	dget http://mentors.debian.net/debian/pool/main/d/dar/dar_2.3.0-5~bpo.1.dsc

← Version précédente		Version du 8 octobre 2006 à 10:57
Ligne 1 :		Ligne 1 :
		+	== debhelper ==
		+
	This one is as simple as [[Backport dar]], except that there is a missing build dependency from stable: debhelper 5.		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:		debhelper was already backported so you just have to install it:

@@ Ligne 6 : / Ligne 6 : @@
-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:
+== Trick 1: Uploaders ==
   Uploaders: Sylvain Beucler <beuc@beuc.net>
 (source: [http://backports.org/dokuwiki/doku.php?id=contribute])
 Then, the package builds cleanly:
@@ Ligne 14 : / Ligne 18 : @@
   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:
+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

← Version précédente		Version du 8 octobre 2006 à 10:56
Ligne 29 :		Ligne 29 :
	You need to give the <code>-sa</code> option to <code>debuild</code> so it includes the source tarball; otherwise, mentors.debian.net will reject your upload.		You need to give the <code>-sa</code> option to <code>debuild</code> so it includes the source tarball; otherwise, mentors.debian.net will reject your upload.

−	kaol also suggested to so a source-only package ~~(<code>-S</code>)~~ since your sponsor will rebuild the package anyway. For the same reason, there's no issue with uploading an orig.tar.gz file even if there's already one at bpo.	+	kaol also suggested to so a source-only package, since your sponsor will rebuild the package anyway:
		+	debuild -S
		+	dput mentors wireless-tools_28-1~bpo.1_source.changes
		+
		+	For the same reason, there's no issue with uploading an orig.tar.gz file even if there's already one at bpo.

← Version précédente		Version du 8 octobre 2006 à 07:53
Ligne 28 :		Ligne 28 :

	You need to give the <code>-sa</code> option to <code>debuild</code> so it includes the source tarball; otherwise, mentors.debian.net will reject your upload.		You need to give the <code>-sa</code> option to <code>debuild</code> so it includes the source tarball; otherwise, mentors.debian.net will reject your upload.
		+
		+	kaol also suggested to so a source-only package (<code>-S</code>) since your sponsor will rebuild the package anyway. For the same reason, there's no issue with uploading an orig.tar.gz file even if there's already one at bpo.

← Version précédente		Version du 8 octobre 2006 à 07:44
Ligne 20 :		Ligne 20 :

	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.		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.
		+
		+
		+	== Upload ==
		+
		+	One way to share your backport is to upload it at [http://mentors.debian.net/cgi-bin/maintainer-intro mentors.debian.net].
		+	dput mentors dar_2.3.0-5~bpo.1_i386.changes
		+
		+	You need to give the <code>-sa</code> option to <code>debuild</code> so it includes the source tarball; otherwise, mentors.debian.net will reject your upload.

@@ Ligne 2 : / Ligne 2 : @@
 debhelper was already backported so you just have to install it:
   aptitude install debhelper/sarge-backports
 Then, the package builds cleanly:
@@ Ligne 7 : / Ligne 14 : @@
   debuild -us -uc
-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?

@@ Ligne 1 : / Ligne 1 : @@
 This one is as simple as [[Backport dar]], except that there is a missing build dependency from stable: debhelper 5.
-debhelper was already backported to you just have to install it:
+debhelper was already backported so you just have to install it:
   aptitude install debhelper/sarge-backports

← Version précédente		Version du 4 octobre 2006 à 14:33
Ligne 6 :		Ligne 6 :
	dch -i		dch -i
	debuild -us -uc		debuild -us -uc
		+
		+	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?