blob: 2e1b4b309a5776253b7316498e18a463ef6762f6 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
This directory contains my scripts to build backports of R software from Debian
sid to older Debian distributions.
Currently (2013-04-04) I am using the following setup:
~/.pbuilderrc contains:
NAME="$DIST-$ARCH"
APTCACHEHARDLINK=yes
DISTRIBUTION="$DIST"
DEBOOTSTRAPOPTS=("--arch" "$ARCH" "${DEBOOTSTRAPOPTS[@]}")
BASETGZ="`dirname $BASETGZ`/$NAME-base.tgz"
BUILDRESULT="/var/cache/pbuilder/$NAME/result/"
APTCACHE="/var/cache/pbuilder/$NAME/aptcache/"
MIRRORSITE="http://ftp.de.debian.org/debian/"
OTHERMIRROR="deb http://security.debian.org $DIST/updates main|deb http://localhost/r-cran $DIST-cran3/"
COMPONENTS="main"
This means I have the appropriate aptcache and buildresult directories set up
under /var/cache/pbuilder. I have several pbuilder images used for package
creation under /var/cache/pbuilder, among others:
/var/cache/pbuilder/squeeze-i386-base.tgz
These have a standard Debian mirror, the security sources and the Debian
backports repository setup in their /etc/apt/sources.list, as well as my local
http package source where the r-base package build results are available. I
have also imported the apt key of my repository inside the pbuilder chroots.
In the wheezey pbuilder images, the backports repository is not necessary.
When using these scripts on Debian, I configure sudo to allow my normal user to use pbuilder, apt-get
and the backporting scripts
|