Différences entre versions de « Backport ettercap »

De Cliss XXI
Sauter à la navigation Sauter à la recherche
 
imported>SylvainBeucler
m
 
(3 versions intermédiaires par un autre utilisateur non affichées)
Ligne 1 : Ligne 1 :
This one is as simple as [[Backport par2]], except for the strange version: 1:0.7.3-1+b1.
+
This one is as simple as [[Backport dar]], except for the strange version: <code>1:0.7.3-1+b1</code>.
  
As explained at [http://www.us.debian.org/doc/developers-reference/ch-pkgs.en.html#s-porter-guidelines], version +b1 means "1st recompilation", ie the package was recompiled without any change in the source code (but probably with a
+
As explained at [http://www.us.debian.org/doc/developers-reference/ch-pkgs.en.html#s-porter-guidelines], version <code>+b1</code> means "1st recompilation", ie the package was recompiled without any change in the source code (but probably with a different build environment).
different build environment).
+
 
 +
<code>1:</code> is a version prefix, usually because of a non-incremental version change [http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version], we don't care about it.
 +
 
 +
So the source version actually is <code>1:0.7.3-1</code>, and hence the bpo version will be <code>1:0.7.3-1~bpo.1</code>.
 +
 
 +
Note: in the [http://backports.org/debian/pool/main/e/ettercap/ backports archive], the package is called differently: this is because we used a different versioning convention at that time. You can ignore this discrepency.

Version actuelle datée du 14 septembre 2006 à 16:03

This one is as simple as Backport dar, except for the strange version: 1:0.7.3-1+b1.

As explained at [1], version +b1 means "1st recompilation", ie the package was recompiled without any change in the source code (but probably with a different build environment).

1: is a version prefix, usually because of a non-incremental version change [2], we don't care about it.

So the source version actually is 1:0.7.3-1, and hence the bpo version will be 1:0.7.3-1~bpo.1.

Note: in the backports archive, the package is called differently: this is because we used a different versioning convention at that time. You can ignore this discrepency.