Différences entre versions de « Backport Gnash »

De Cliss XXI
Sauter à la navigation Sauter à la recherche
imported>SylvainBeucler
m
imported>SylvainBeucler
m (No change is actually needed)
Ligne 13 : Ligne 13 :
 
Normally the backports repository will not be used, because it has a default priority of -1. With the 'experimental' method (meant for the Debian experimental repository), backports dependencies will be used, but only if no Stable dependency could be found first, which is exactly what we want.
 
Normally the backports repository will not be used, because it has a default priority of -1. With the 'experimental' method (meant for the Debian experimental repository), backports dependencies will be used, but only if no Stable dependency could be found first, which is exactly what we want.
  
The only change we need in gnash 0.8.2-1 is to replace all the <code>base-files (>= 4.0.1)</code> with <code>base-files (>= 4.0.1~)</code> (trailing <code>~</code>), so that the backported dependency (<code>4.0.1~bpo40+1</code>) can be used. The rest of the dependencies are already edited in this regard.
+
The dependencies are already edited for use in backports.org (e.g. <code>base-files (>= 4.0.1~)</code>) so we don't have to do any change to the package. Marvelous. <code>Build-Depends</code> dependencies are not edited but it seems <code>satisfydepends-experimental</code> is able to cope with it.
  
Then we proceed with the backport:
+
We can proceed with the backport:
 
  yes | dch -D etch-backports \
 
  yes | dch -D etch-backports \
 
   --newversion $(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo40+1 \
 
   --newversion $(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo40+1 \

Version du 6 avril 2008 à 11:46

Almost all dependencies are available in Etch, so it's pretty easy to install.

Only 'base-files' needs to be backported, and it was already uploaded at backports.org by another backporter. This is an opportunity to try out automated and minimal dependency support for pbuilder.

  • Enable backports repository:
cowbuilder --login --save-after-login
echo "deb http://network/mirrors/debian-backports.org etch-backports main" > /etc/apt/sources.list.d/bpo.list
wget -O - http://backports.org/debian/archive.key | apt-key add -
aptitude update
  • In /etc/pbuilderrc, use the 'experimental' method to satisfy dependencies:
PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-experimental

Normally the backports repository will not be used, because it has a default priority of -1. With the 'experimental' method (meant for the Debian experimental repository), backports dependencies will be used, but only if no Stable dependency could be found first, which is exactly what we want.

The dependencies are already edited for use in backports.org (e.g. base-files (>= 4.0.1~)) so we don't have to do any change to the package. Marvelous. Build-Depends dependencies are not edited but it seems satisfydepends-experimental is able to cope with it.

We can proceed with the backport:

yes | dch -D etch-backports \
  --newversion $(dpkg-parsechangelog | sed -ne 's,^Version: ,,p')~bpo40+1 \
  --force-bad-version -- \
  "Rebuild for Debian Backports <http://www.backports.org/>"
# TODO: --pbuildersatisfydepends doesn't work, why?
#pdebuild --pbuilder cowbuilder --pbuildersatisfydepends /usr/lib/pbuilder/pbuilder-satisfydepends-experimental
# Meanwhile we edit /etc/pbuilderrc manually
pdebuild --pbuilder cowbuilder

Back to Backports.