Backport FreeType - Historique des versions

imported>SylvainBeucler : /* Cleaner compilation */

2008-06-22T16:35:35Z

Cleaner compilation

imported>SylvainBeucler le 28 mars 2008 à 09:58

2008-03-28T09:58:56Z

imported>SylvainBeucler le 18 mars 2008 à 22:22

2008-03-18T22:22:13Z

imported>SylvainBeucler le 18 mars 2008 à 22:09

2008-03-18T22:09:15Z

imported>SylvainBeucler : syntax

2008-01-14T08:52:42Z

syntax

imported>SylvainBeucler : Tracking security

2008-01-14T08:52:29Z

Tracking security

imported>SylvainBeucler : /* Versioning */

2007-12-12T18:41:41Z

Versioning

imported>SylvainBeucler : /* Versioning */

2007-12-12T18:41:22Z

Versioning

imported>SylvainBeucler : /* Versioning */

2007-12-12T18:40:59Z

Versioning

imported>SylvainBeucler : /* Versioning */

2007-12-12T18:39:34Z

Versioning

← Version précédente		Version du 22 juin 2008 à 16:35
Ligne 92 :		Ligne 92 :
	cowbuilder --create --distribution=etch		cowbuilder --create --distribution=etch
	pdebuild --pbuilder cowbuilder		pdebuild --pbuilder cowbuilder
		+
		+	Other notes:
		+	* if compiling from lenny, add <code>--debian-etch-workaround</code>
		+	* you can specify an alternate chroot with <code>--basepath</code>
		+	Example:
		+	pdebuild --pbuilder cowbuilder -- --basepath /var/cache/pbuilder/base-etch.cow --debian-etch-workaround --debbuildopts '-sa'

@@ Ligne 27 : / Ligne 27 : @@
 * Check my mail address.
-To generate the initial changelog entry template automagically, madduck suggests using <code>dch</code> and <code>dpkg-parsechangelog</code>, e.g.:
+To generate the initial changelog entry template automagically, you can use <code>dch</code> and <code>dpkg-parsechangelog</code>, e.g.:
-  dch -D etch-backports -b -v$(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo40+1 -- \
+  yes | dch -D etch-backports \
     "Rebuild for Debian Backports <http://www.backports.org/>"
 Also add your name in <code>debian/control</code>:

@@ Ligne 25 : / Ligne 25 : @@
 * Changed distribution from <code>unstable</code> to <code>etch-backports</code>
 * Added a terse explanation
-* Check my mail adress.
+* Check my mail address.
 To generate the initial changelog entry template automagically, madduck suggests using <code>dch</code> and <code>dpkg-parsechangelog</code>, e.g.:
@@ Ligne 76 : / Ligne 76 : @@
 * http://lists.debian.org/debian-security-announce/debian-security-announce-2008/msg00012.html (7 jan 2008)
 * http://security.debian.org/debian-security/pool/updates/main/f/freetype/ (timestamp 5 jan 2008)

@@ Ligne 1 : / Ligne 1 : @@
 == Versioning ==
-Backporting dar is quite simple - you just need to recompile the Lenny version in a Etch environment. It's a nice occasion to cover the very basics.
+Backporting FreeType is quite simple - you just need to recompile the Lenny version in a Etch environment. It's a nice occasion to cover the very basics.
 You need to modify <code>debian/changelog</code> though. Enter the <code>freetype-2.3.5</code> directory, and type:

← Version précédente		Version du 14 janvier 2008 à 08:52
Ligne 59 :		Ligne 59 :


−	== Tracking security =	+	== Tracking security ==

	When you backport a package, it is good to track security issues that affect it and update your package accordingly.		When you backport a package, it is good to track security issues that affect it and update your package accordingly.

← Version précédente		Version du 14 janvier 2008 à 08:52
Ligne 57 :		Ligne 57 :

	If you see some source changes that you didn't do, then your backport is not clean (probably it's a leftover from an incomplete <code>make clean</code>). Usually, just remove the current directory and extract a new clean one using <code>dpkg-source</code>.		If you see some source changes that you didn't do, then your backport is not clean (probably it's a leftover from an incomplete <code>make clean</code>). Usually, just remove the current directory and extract a new clean one using <code>dpkg-source</code>.
		+
		+
		+	== Tracking security =
		+
		+	When you backport a package, it is good to track security issues that affect it and update your package accordingly.
		+
		+	An easy way is subscribing to the [http://lists.debian.org/debian-security-announce/ debian-security-announce] mailing list, which sends a mail each time a security fix is published for Debian.
		+
		+	Understanding security is difficult though. For example, in the case of Freetype for Etch, <code>changelog.Debian</code> mentions a fix in July 2007:
		+	freetype (2.2.1-5+etch2) stable-security; urgency=high
		+
		+	* debian/patches-freetype/CVE-2007-1351_pdf-overflow: address
		+	CVE-2007-1351, an integer overflow bug in the handling of BDF fonts.
		+	Closes: #426771.
		+
		+	-- Steve Langasek <vorlon@debian.org> Mon, 09 Jul 2007 17:21:11 -0700
		+	while the security was actually published nearly 6 months later:
		+	* http://lists.debian.org/debian-security-announce/debian-security-announce-2008/msg00012.html (7 jan 2008)
		+	* http://security.debian.org/debian-security/pool/updates/main/f/freetype/ (timestamp 5 jan 2008)

@@ Ligne 8 : / Ligne 8 : @@
 If you want to use another editor, you can also:
   EDITOR=emacs dch -i
 Here's my final changelog entry:
@@ Ligne 30 : / Ligne 26 : @@
 * Added a terse explanation
 * Check my mail adress.
 Also add your name in <code>debian/control</code>:

@@ Ligne 9 : / Ligne 9 : @@
   EDITOR=emacs dch -i
-madduck suggest to use the following command to generate the initial changelog entry template (didn't try out yet):
+madduck suggest to use the following command to generate the initial changelog entry template:
-  dch -D sarge-backports -b -v$(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo.1 -- Rebuilt for sarge.
+  dch -D etch-backports -b -v$(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo40+1 -- \
 Here's my final changelog entry: