Re: pbuilder-satisfydepends-classic profile parsing problem: slashes and spaces
Mattia, thanks for the answer, I will file a bug -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ On Thu, Oct 22, 2020 at 4:39 PM Mattia Rizzolo wrote: > > Hi! > > On Wed, Oct 21, 2020 at 10:06:02PM +0300, Alexei Fedotov wrote: > > I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic > > for the debian/control which contains > > > > Build-Depends: live-build (<= 1:20170213), ... > > > > I get the following log > > > > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils, ' > > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils' > > +++ echo 'live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils' > > ++ for INSTALLPKGMULTI in $(get_build_deps | split_deps) > > +++ echo 'live-build/(<=/1:20170213)' > > +++ tr / ' ' > > ++ echo ' -> Considering build-dep live-build (<= 1:20170213)' > > -> Considering build-dep live-build (<= 1:20170213) > > ++ SATISFIED=no > > +++ split_alternates 'live-build/(<=/1:20170213)' > > +++ echo 'live-build/(<=/1:20170213)' > > +++ sed 's/ *| */\n/g' > > ++ for INSTALLPKG in $(split_alternates "$INSTALLPKGMULTI") > > +++ get_pkg_name 'live-build/(<=/1:20170213)' > > +++ echo 'live-build/(<=/1:20170213)' > > +++ sed 's#^/*##; s#[[/(<].*##' > > ++ CURRENTREALPKGNAME=live-build > > ++ echo 'live-build/(<=/1:20170213)' > > ++ grep -q '\[' > > ++ echo 'live-build/(<=/1:20170213)' > > ++ grep -q '<' > > I reckon here is the problem ↑ > The code thinks that anything that contains a '<' is a build profile. > That's probably because it's considered rare for a Build-Depends to have > a << or a <= relation. > From that assumption on it probably just fails over itself. > > > What is the proper list to discuss the issue? How should it be addressed? > > Please file a bug against pbuilder, but don't expect it to be solved > quickly. > > In fact, nowadays I generally recommend people use the -apt resolver, > which tends to work better in most cases, besides being faster. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Re: pbuilder-satisfydepends-classic profile parsing problem: slashes and spaces
Hi! On Wed, Oct 21, 2020 at 10:06:02PM +0300, Alexei Fedotov wrote: > I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic > for the debian/control which contains > > Build-Depends: live-build (<= 1:20170213), ... > > I get the following log > > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > coreutils, findutils, ' > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > coreutils, findutils' > +++ echo 'live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > coreutils, findutils' > ++ for INSTALLPKGMULTI in $(get_build_deps | split_deps) > +++ echo 'live-build/(<=/1:20170213)' > +++ tr / ' ' > ++ echo ' -> Considering build-dep live-build (<= 1:20170213)' > -> Considering build-dep live-build (<= 1:20170213) > ++ SATISFIED=no > +++ split_alternates 'live-build/(<=/1:20170213)' > +++ echo 'live-build/(<=/1:20170213)' > +++ sed 's/ *| */\n/g' > ++ for INSTALLPKG in $(split_alternates "$INSTALLPKGMULTI") > +++ get_pkg_name 'live-build/(<=/1:20170213)' > +++ echo 'live-build/(<=/1:20170213)' > +++ sed 's#^/*##; s#[[/(<].*##' > ++ CURRENTREALPKGNAME=live-build > ++ echo 'live-build/(<=/1:20170213)' > ++ grep -q '\[' > ++ echo 'live-build/(<=/1:20170213)' > ++ grep -q '<' I reckon here is the problem ↑ The code thinks that anything that contains a '<' is a build profile. That's probably because it's considered rare for a Build-Depends to have a << or a <= relation. From that assumption on it probably just fails over itself. > What is the proper list to discuss the issue? How should it be addressed? Please file a bug against pbuilder, but don't expect it to be solved quickly. In fact, nowadays I generally recommend people use the -apt resolver, which tends to work better in most cases, besides being faster. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
pbuilder-satisfydepends-classic profile parsing problem: slashes and spaces
Hello, Mattia, folks, I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic for the debian/control which contains Build-Depends: live-build (<= 1:20170213), ... I get the following log +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils, ' +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils' +++ echo 'live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils' ++ for INSTALLPKGMULTI in $(get_build_deps | split_deps) +++ echo 'live-build/(<=/1:20170213)' +++ tr / ' ' ++ echo ' -> Considering build-dep live-build (<= 1:20170213)' -> Considering build-dep live-build (<= 1:20170213) ++ SATISFIED=no +++ split_alternates 'live-build/(<=/1:20170213)' +++ echo 'live-build/(<=/1:20170213)' +++ sed 's/ *| */\n/g' ++ for INSTALLPKG in $(split_alternates "$INSTALLPKGMULTI") +++ get_pkg_name 'live-build/(<=/1:20170213)' +++ echo 'live-build/(<=/1:20170213)' +++ sed 's#^/*##; s#[[/(<].*##' ++ CURRENTREALPKGNAME=live-build ++ echo 'live-build/(<=/1:20170213)' ++ grep -q '\[' ++ echo 'live-build/(<=/1:20170213)' ++ grep -q '<' ++ checkbuilddep_restrictiondeps 'live-build/(<=/1:20170213)' 'nocheck astrace' ++ local 'INSTALLPKG=live-build/(<=/1:20170213)' ++ local 'PROFILES=nocheck astrace' +++ echo 'echo "$INSTALLPKG" | sed -e 's/[^<]*<\(.*\)>.*/\1/' -e 'y|/| |' -e 's/>\s\+.*/\1/' -e 'y|/| |' -e 's/>\s\+http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
Re: How to build GCC for a specific machine using pbuilder?
Mikhail Morfikov wrote: > I know, but have you ever seen the debian/ dir in the gcc sources? Take a > look here[1]. > Until now I have not, but what is exactly the problem? You have what you need in the beginning include debian/rules.defs include debian/rules.unpack include debian/rules.patch control: $(control_dependencies) -mkdir -p $(stampdir) $(MAKE) -f debian/rules.conf $@ configure: control $(unpack_stamp) $(patch_stamp) $(MAKE) -f debian/rules2 $@ all the rest is supplementary so now you want to change the configuration and have a look at debian/rules2 It is more complicated, but I still don't understand what you expect here. If you know what you want to do with configure, then you can trash this and create your own simple version.
Re: How to build GCC for a specific machine using pbuilder?
On 19/06/2020 18:36, deloptes wrote: > Mikhail Morfikov wrote: > >> I've read something about setting flags like: --enable-languages= or >> --disable-multilib , which I think would speed the whole process up, but >> unfortunately I have no idea which file in the debian/ dir I should change >> to build the GCC for my machine only. Any suggestions? Also how to >> include/exclude patches so they were applied to the source -- there's no >> "debian/patches/series" file. > > usually it is in debian/rules (this is the debians make file) > > read the docs first - the thing with the patches is explained on the debian > wiki like > https://wiki.debian.org/debian/patches > https://www.debian.org/doc/manuals/maint-guide/modify.en.html > https://wiki.debian.org/debian/patches > > be patient it works > > I know, but have you ever seen the debian/ dir in the gcc sources? Take a look here[1]. [1]: https://salsa.debian.org/toolchain-team/gcc signature.asc Description: OpenPGP digital signature
Re: How to build GCC for a specific machine using pbuilder?
Mikhail Morfikov wrote: > I've read something about setting flags like: --enable-languages= or > --disable-multilib , which I think would speed the whole process up, but > unfortunately I have no idea which file in the debian/ dir I should change > to build the GCC for my machine only. Any suggestions? Also how to > include/exclude patches so they were applied to the source -- there's no > "debian/patches/series" file. usually it is in debian/rules (this is the debians make file) read the docs first - the thing with the patches is explained on the debian wiki like https://wiki.debian.org/debian/patches https://www.debian.org/doc/manuals/maint-guide/modify.en.html https://wiki.debian.org/debian/patches be patient it works
How to build GCC for a specific machine using pbuilder?
I wanted to change the GCC source a little bit by adding some patches that aren't available in Debian. I downloaded the Debian GCC source via "apt-get source" . I tried to build the source in the Debian way (using pbuilder) just to test how much time would it take. I gave up after 2h because probably it builds everything for everyone, and it's not really what I wanted it to do. I've read something about setting flags like: --enable-languages= or --disable-multilib , which I think would speed the whole process up, but unfortunately I have no idea which file in the debian/ dir I should change to build the GCC for my machine only. Any suggestions? Also how to include/exclude patches so they were applied to the source -- there's no "debian/patches/series" file. signature.asc Description: OpenPGP digital signature
Re: How to build FreeTube using pbuilder?
Mikhail Morfikov wrote: > There's an app called FreeTube[1], which is a nice alternative for other > apps playing YT vids. Unfortunately its source is a little bit different > than regular sources which can be build using the Debian build system > (pbuilder). Does anyone know how to build this app in the Debian way and > could give me some hints on how to do it properly? I know it has the > upstream .deb package to be installed in the system, but I wanted to > build myself. > > > [1] https://github.com/FreeTubeApp/FreeTube Follow the white rabbit https://github.com/flathub/io.freetubeapp.FreeTube/blob/master/io.freetubeapp.FreeTube.json => https://gitlab.com/freedesktop-sdk/freedesktop-sdk But pbuilder needs the debian directory as any other debian builder. Try to find it. regards
How to build FreeTube using pbuilder?
There's an app called FreeTube[1], which is a nice alternative for other apps playing YT vids. Unfortunately its source is a little bit different than regular sources which can be build using the Debian build system (pbuilder). Does anyone know how to build this app in the Debian way and could give me some hints on how to do it properly? I know it has the upstream .deb package to be installed in the system, but I wanted to build myself. [1] https://github.com/FreeTubeApp/FreeTube signature.asc Description: OpenPGP digital signature
Re: pbuilder ou pas?
salut Dominique, > HTH it helps indeed! au lieu de me poser trop de question, je vais packager, faire de erreurs et profiter des reviews et d'éventuels bugs pour monter en compétences. merci d'avoir partagé tes pratiques. marc
Re: pbuilder ou pas?
On Thursday, 21 March 2019 10:42:25 CET Dominique Dumont wrote: > Tu peux aussi demander de l'aide sur #debian-fr (IRC) Oops, c'est #debian-devel-fr Dod
Re: pbuilder ou pas?
On Wednesday, 6 March 2019 16:14:19 CET Marc Chantreux wrote: > * dois-je utiliser pbuilder a l'époque ou docker semble etre une facon > standard de faire des boulots dans un chroot? ou existe-t'il une autre > alternative ? Dans mon cas, je bosses sur une Debian/unstable, donc je fais les paquets en natif. Avant de faire un upload, je valide le paquet avec cowbuilder. Comme j'utilise en général dh et gbp-buildpackage [1], la validation est assez simple: gbp buildpackage --git-builder=cowbuilder --git-pbuilder > * existe-t'il une doc qui soit encore mieux que le tuto de lucas > nussbaum (et surtout qui prend en compte les aspects interactions avec > la communauté)? Je ne sais pas. J'ai appris à faire les paquets avec l'aide (par email ou IRC) de l'équipe debian-perl. Tu peux aussi demander de l'aide sur #debian-fr (IRC) > * y'a de la boite de service ou une asso qui fait eventuellement ce genre de > transfert de compétences et que vous pourriez me recommander? > m'accompagner jusqu'a l'ITP et la maintenance d'un paquet debian officiel > ? Peut-être https://debamax.com/fr/ HTH Dod [1] https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
Re: pbuilder ou pas?
hello Bernard, > > * existe-t'il une doc qui soit encore mieux que le tuto de lucas > > nussbaum (et surtout qui prend en compte les aspects interactions > > avec la communauté)? > Lucas Nussbaum avait réaliser un diaporama sur la création de paquets debian > ... merci pour l'info ... la prochaine fois je serais précis et je mettrais le lien vers ce pdf quand je parle du "tuto de lucas nussbaum" marc
Re: pbuilder ou pas?
- Mail original - > De: "Marc Chantreux" > À: debian-user-french@lists.debian.org > Envoyé: Mercredi 6 Mars 2019 16:14:19 > Objet: pbuilder ou pas? > > cher debian-fr, > > lorsque je veux faire un paquet debian, j'utilise equivs: c'est > simple > et ca suffit dans 99% de mes besoins. sauf que aujourd'hui, on me > demande de faire les choses proprement, dans les regles ... > eventuellement > pour plusieurs archis ... et meme idéalement fait un ITP à un moment. > > moi j'aime pas les règles ... et là mon coeur saigne: > > * je sais créer un paquet, pas le maintenir de version en version > * je sais créer un paquet pour *ma machine*, pas un vrai paquet pour > le > deb-src et le multiarch et touti quanti > > du coup je me demande si: > > * dois-je utiliser pbuilder a l'époque ou docker semble etre une > facon > standard de faire des boulots dans un chroot? ou existe-t'il une > autre > alternative ? > * existe-t'il une doc qui soit encore mieux que le tuto de lucas > nussbaum (et surtout qui prend en compte les aspects interactions > avec > la communauté)? > * y'a de la boite de service ou une asso qui fait eventuellement ce > genre de > transfert de compétences et que vous pourriez me recommander? > m'accompagner jusqu'a l'ITP et la maintenance d'un paquet debian > officiel ? > > cordialement, > marc bonjour, Lucas Nussbaum avait réaliser un diaporama sur la création de paquets debian ... voici le lien : https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.fr.pdf merci Dackelstein
pbuilder ou pas?
cher debian-fr, lorsque je veux faire un paquet debian, j'utilise equivs: c'est simple et ca suffit dans 99% de mes besoins. sauf que aujourd'hui, on me demande de faire les choses proprement, dans les regles ... eventuellement pour plusieurs archis ... et meme idéalement fait un ITP à un moment. moi j'aime pas les règles ... et là mon coeur saigne: * je sais créer un paquet, pas le maintenir de version en version * je sais créer un paquet pour *ma machine*, pas un vrai paquet pour le deb-src et le multiarch et touti quanti du coup je me demande si: * dois-je utiliser pbuilder a l'époque ou docker semble etre une facon standard de faire des boulots dans un chroot? ou existe-t'il une autre alternative ? * existe-t'il une doc qui soit encore mieux que le tuto de lucas nussbaum (et surtout qui prend en compte les aspects interactions avec la communauté)? * y'a de la boite de service ou une asso qui fait eventuellement ce genre de transfert de compétences et que vous pourriez me recommander? m'accompagner jusqu'a l'ITP et la maintenance d'un paquet debian officiel ? cordialement, marc
Re: Pbuilder vraag
Op 06-09-18 om 13:36 schreef Paul van der Vlis: > Hoi, > > Ik gebruik pbuilder voor het backporten van packages. > > Wat niet goed gaat, is het installeren van build-dependencies in de > chroot die uit stable-backports moeten komen. (...) Ik heb deze vraag later in de backports-mailinglijst gesteld omdat er hier geen reactie kwam. Ik ben er uit. Mensen die geïnteresseerd zijn in de oplossing kunnen daar kijken. Groet, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Pbuilder vraag
Hoi,
Ik gebruik pbuilder voor het backporten van packages.
Wat niet goed gaat, is het installeren van build-dependencies in de
chroot die uit stable-backports moeten komen.
Dus bij bijvoorbeeld een package zoals "dh-linktree" wat debhelper >= 11
nodig heeft (wat in backports zit) lukt het backporten niet.
Mijn .pbuilderrc is nogal een complex bestand, ik zal het als bijlage
meesturen (zal het overkomen?). Backports staat er wel in.
Ik heb dit geprobeerd in het configfile, maar dat geeft dezelfde fout:
PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-experimental"
Ik krijg zoiets als fout:
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 11)
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
Iemand een idee hoe ik build-dependencies uit backports kan gebruiken?
Groet,
Paul
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
# onderstaande komt van https://wiki.debian.org/PbuilderTricks
# Codenames for Debian suites according to their alias. Update these when
# needed.
UNSTABLE_CODENAME="sid"
TESTING_CODENAME="buster"
STABLE_CODENAME="stretch"
STABLE_BACKPORTS_SUITE="$STABLE_CODENAME-backports"
# List of Debian suites.
DEBIAN_SUITES=($UNSTABLE_CODENAME $TESTING_CODENAME $STABLE_CODENAME
$STABLE_BACKPORTS_SUITE
"experimental" "unstable" "testing" "stable")
# Mirrors to use. Update these to your preferred mirror.
DEBIAN_MIRROR="ftp.nl.debian.org"
# Optionally use the changelog of a package to determine the suite to use if
# none set.
if [ -z "${DIST}" ] && [ -r "debian/changelog" ]; then
DIST=$(dpkg-parsechangelog --show-field=Distribution)
fi
# Optionally set a default distribution if none is used. Note that you can set
# your own default (i.e. ${DIST:="unstable"}).
: ${DIST:="$(lsb_release --short --codename)"}
# Optionally change Debian codenames in $DIST to their aliases.
case "$DIST" in
$UNSTABLE_CODENAME)
DIST="unstable"
;;
$TESTING_CODENAME)
DIST="testing"
;;
$STABLE_CODENAME)
DIST="stable"
;;
esac
# Optionally set the architecture to the host architecture if none set. Note
# that you can set your own default (i.e. ${ARCH:="i386"}).
: ${ARCH:="$(dpkg --print-architecture)"}
NAME="$DIST"
if [ -n "${ARCH}" ]; then
NAME="$NAME-$ARCH"
DEBOOTSTRAPOPTS=("--arch" "$ARCH" "${DEBOOTSTRAPOPTS[@]}")
fi
BASETGZ="/var/cache/pbuilder/$NAME-base.tgz"
DISTRIBUTION="$DIST"
BUILDRESULT="/var/cache/pbuilder/$NAME/result/"
APTCACHE="/var/cache/pbuilder/$NAME/aptcache/"
BUILDPLACE="/var/cache/pbuilder/build/"
if $(echo ${DEBIAN_SUITES[@]} | grep -q $DIST); then
# Debian configuration
MIRRORSITE="http://$DEBIAN_MIRROR/debian/;
COMPONENTS="main contrib non-free"
if $(echo "$STABLE_CODENAME stable" | grep -q $DIST); then
OTHERMIRROR="$OTHERMIRROR | deb $MIRRORSITE $STABLE_BACKPORTS_SUITE
$COMPONENTS"
fi
else
echo "Unknown distribution: $DIST"
exit 1
fi
#
PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-experimental"
Re: pbuilder et backports
Hello, Pour la dépendance, tu dois pouvoir t'en sortir en indiquant à pbuilder d'ajouter un repo debian aux repos par défaut. Ça se fait avec l'option OTHERMIRROR dans /etc/pbuilderrc Pour le build taggué backport, la solution la plus simple que je connaisse et de produire un paquet source lui même taggué en backport. Si tu utilises gbp, la commande gbp dch -R --bpo devrait faire le job. ++ JB On 23/01/2017 14:07, Damien TOURDE wrote: > Bonjour, > > J'aimerais me créer un paquet .deb d'un soft dont l'une des BuildDeps ne > se trouve que sur jessie-backports (et sid et testing). > > Donc j'aurais bien aimé savoir si quelqu'un savait comment "simplement" > utiliser pbuilder en lui spécifiant cette dépendance mais en faisant un > build taggué "jessie-backports" et non "sid" comme par défaut. > > > Je ne sais pas si ma demande est très claire, mais pbuilder ne l'est pas > encore vraiment pour moi non-plus :-) >
Re: pbuilder et backports
Bonjour, > J'aimerais me créer un paquet .deb d'un soft dont l'une des BuildDeps ne > se trouve que sur jessie-backports (et sid et testing). > > Donc j'aurais bien aimé savoir si quelqu'un savait comment "simplement" > utiliser pbuilder en lui spécifiant cette dépendance mais en faisant un > build taggué "jessie-backports" et non "sid" comme par défaut. > > Je ne sais pas si ma demande est très claire, mais pbuilder ne l'est pas > encore vraiment pour moi non-plus :-) Je ne sais pas si ceci est possible. Une réponse dans ce sens m'intéresserai aussi. Une solution alternative serait de reconstruire le paquet de la dépendance provenant de backport puis de l'intégrer dans ton base.tgz de pbuilder. Olivier
pbuilder et backports
Bonjour, J'aimerais me créer un paquet .deb d'un soft dont l'une des BuildDeps ne se trouve que sur jessie-backports (et sid et testing). Donc j'aurais bien aimé savoir si quelqu'un savait comment "simplement" utiliser pbuilder en lui spécifiant cette dépendance mais en faisant un build taggué "jessie-backports" et non "sid" comme par défaut. Je ne sais pas si ma demande est très claire, mais pbuilder ne l'est pas encore vraiment pour moi non-plus :-)
Re: Pbuilder et multi arch
Bon alors je confirme, c'est juste parfait. Merci encore ! Pour Pbuilder, il suffit d'ajouter l'option --debbuildopts -B Le 29 février 2016 à 19:55, Olivier Bitsch <olivier.bit...@gmail.com> a écrit : > Super suggestion, je teste ça ce soir, merci beaucoup. > > Le 29 février 2016 à 11:06, Sébastien NOBILI <sebnewslet...@free.fr> a > écrit : > >> Bonjour, >> >> Le dimanche 28 février 2016 à 13:04, Olivier Bitsch a écrit : >> > Hors ces fichiers "all" s'installant aussi bien sur amd64 que sur i386 >> > n'ont pas le même hash en fonction de l'architecture à partir de >> laquelle >> > ils ont fabriqués. Ce qui pose donc ensuite des problèmes lorsque je les >> > uploade sur mon dépôt debarchiver, car les utilisateurs ont des sommes >> md5 >> > incohérente. >> >> Je n'utilise pas pbuilder mais je génère moi aussi des paquets pour i386 >> et >> amd64. >> >> Selon moi le mieux est de faire en sorte que les paquets « all » soient >> générés >> une seule fois. J'ai pris le parti de les générer uniquement dans >> l'environnement i386 et de restreindre l'environnement amd64 aux seuls >> paquets >> binaires de cette architecture. >> >> Ça se fait en passant l'argument « -B » à la commande >> « dpkg-buildpackage » (à >> positionner uniquement pour l'environnement amd64). >> >> Sébastien >> >> >
Re: Pbuilder et multi arch
Super suggestion, je teste ça ce soir, merci beaucoup. Le 29 février 2016 à 11:06, Sébastien NOBILI <sebnewslet...@free.fr> a écrit : > Bonjour, > > Le dimanche 28 février 2016 à 13:04, Olivier Bitsch a écrit : > > Hors ces fichiers "all" s'installant aussi bien sur amd64 que sur i386 > > n'ont pas le même hash en fonction de l'architecture à partir de laquelle > > ils ont fabriqués. Ce qui pose donc ensuite des problèmes lorsque je les > > uploade sur mon dépôt debarchiver, car les utilisateurs ont des sommes > md5 > > incohérente. > > Je n'utilise pas pbuilder mais je génère moi aussi des paquets pour i386 et > amd64. > > Selon moi le mieux est de faire en sorte que les paquets « all » soient > générés > une seule fois. J'ai pris le parti de les générer uniquement dans > l'environnement i386 et de restreindre l'environnement amd64 aux seuls > paquets > binaires de cette architecture. > > Ça se fait en passant l'argument « -B » à la commande > « dpkg-buildpackage » (à > positionner uniquement pour l'environnement amd64). > > Sébastien > >
Re: Pbuilder et multi arch
Bonjour, Le dimanche 28 février 2016 à 13:04, Olivier Bitsch a écrit : > Hors ces fichiers "all" s'installant aussi bien sur amd64 que sur i386 > n'ont pas le même hash en fonction de l'architecture à partir de laquelle > ils ont fabriqués. Ce qui pose donc ensuite des problèmes lorsque je les > uploade sur mon dépôt debarchiver, car les utilisateurs ont des sommes md5 > incohérente. Je n'utilise pas pbuilder mais je génère moi aussi des paquets pour i386 et amd64. Selon moi le mieux est de faire en sorte que les paquets « all » soient générés une seule fois. J'ai pris le parti de les générer uniquement dans l'environnement i386 et de restreindre l'environnement amd64 aux seuls paquets binaires de cette architecture. Ça se fait en passant l'argument « -B » à la commande « dpkg-buildpackage » (à positionner uniquement pour l'environnement amd64). Sébastien
Pbuilder et multi arch
Bonjour à tous, Pour les besoins d'une dépendance d'un paquet fonctionnant avec python (projet s'appelant noethys), je voulais backporter vers Jessie la version 3.2.0 de python-reportlab. Je peux sans soucis fabriquer mes paquets i386 et amd64 grâce à mes deux environnements pbuilder et j'ai remarqué que la compilation génère des fichiers deb i386, amd64 et all. Hors ces fichiers "all" s'installant aussi bien sur amd64 que sur i386 n'ont pas le même hash en fonction de l'architecture à partir de laquelle ils ont fabriqués. Ce qui pose donc ensuite des problèmes lorsque je les uploade sur mon dépôt debarchiver, car les utilisateurs ont des sommes md5 incohérente. Y a t'il un moyen de corriger ces hash via pbuilder. J'ai tenté quelques bidouilles avec la commande dpkg-genchanges, mais sans vraiment de succès. Merci par avance. Olivier.
Backporten met pbuilder
Op 31-03-15 om 10:37 schreef Paul van der Vlis: Op 31-03-15 om 05:33 schreef Paul Gevers: Vreemd genoeg wordt het pakket wel gewoon gebouwd: Nee hoor, want: Je hebt gelijk. Sorry. Draai voor je pdebuild aanroept eens pbuilder --update Ik heb nu dit gedraaid als root: pbuilder create --distribution wheezy Verder je script geinstalleerd in ~/.pbuilder-hooks/ Het lijkt nu goed te gaan. De gebouwde *.deb files komen trouwens elders te staan, bij mij (afhankelijk van de naam van je chroot) hier: /var/cache/pbuilder/sid-amd64/result Ja, ik heb ze gevonden in /var/cache/pbuilder/result/ . Heb mijn script geupdated, maar moet nog wel een beetje de weg vinden in pbuilder. Ik kan me voorstellen dat ik bepaalde backports moet installeren om andere te kunnen bouwen, en ik weet nog niet goed hoe dat moet. Zo is er nog wel meer. Bedankt! Groet, Paul. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/551aa389.3090...@vandervlis.nl
Re: pbuilder et compilation kernel custom
Le 30/01/2015 23:21, Sylvain L. Sauvage a écrit : Ça fait quelque temps que ça ne m’est plus arrivé mais quand le besoin se fait sentir, je suis une de ces deux pages : https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage https://wiki.debian.org/BuildingKernelFromUpstreamSources Le souci c'est que cela génère un deb pour l'archi sur laquelle tu te trouves, si tu veux faire un i386, un arm t'es coincé. (Et pour les quelques paquets qu’il m’arrive de patcher, j’avoue ne pas avoir encore trouvé l’utilité de pbuilder…) L'avantage c'est d'éviter de maintenir soit des vm de chaque release et plateforme cpu, soit des chroot ce que pbuilder maintient très bien seul. signature.asc Description: OpenPGP digital signature
Re: pbuilder et compilation kernel custom
Le mercredi 28 janvier 2015, 19:23:20 Wallace a écrit : Bonjour à tous, ’soir, […] Pour vous est ce la bonne voix pour compiler un kernel custom pour Debian? Ou faut il que je m'y prenne autrement? Ça fait quelque temps que ça ne m’est plus arrivé mais quand le besoin se fait sentir, je suis une de ces deux pages : https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage https://wiki.debian.org/BuildingKernelFromUpstreamSources (Et pour les quelques paquets qu’il m’arrive de patcher, j’avoue ne pas avoir encore trouvé l’utilité de pbuilder…) -- Sylvain Sauvage -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/2353518.PxEemfXv1s@earendil
pbuilder et compilation kernel custom
Bonjour à tous, Après avoir réussi à monter une configuration pbuilder pour construire quelques packages custom ou des recompilations avec patch de petits logiciels, je bloque néanmoins sur la compilation de kernel vanilla avec patch. Lorsque je faisais mes packages Debian pour un kernel custom, je prenais la version qui m'intéressait directement sur kernel.org, j'appliquais les patchs et les réglages que j'avais à faire dans le .config et j'utilisais make-kpgk qui est la méthode recommandée pour faire des kernel Debian. Sauf que pour pouvoir compiler un kernel avec pbuilder il faut générer un .dsc .orig et c'est seulement à partir de ces éléments que pbuilder va construire le package pour l'archi et la distribution demandée. Alors j'ai bien trouvé une façon de ne faire que le répertoire /debian/ dans les sources du package et générer les fichiers nécessaires à pbuilder avec les commandes : make-kpkg debian --initrd --revision 1 --append-to-version -patched pour préparer le kernel vanilla pour être packagé dpkg-buildpackage -nc -S pour générer le .dsc et .orig Jusque là tout va bien, le souci c'est lorsque je lance pbuilder avec ces fichiers, le makefile est appelé avec la commande clean qui supprime tout simplement le répertoire /debian/ des sources du kernel. Et forcément juste après il y a une erreur comme quoi ce répertoire n'existe pas et que les actions qui doivent y être faites ne sont plus possibles. Pour vous est ce la bonne voix pour compiler un kernel custom pour Debian? Ou faut il que je m'y prenne autrement? Je précise mes besoins, car j'ai tenté de partir des sources d'un kernel experimental pour être à jour mais vu la complexité du répertoire debian avec toutes les options pour chaque architecture, c'est overkill pour mes besoins, je souhaite juste compiler un kernel patché pour oldstable stable et jessie en amd64 et i386. Merci pour vos avis. signature.asc Description: OpenPGP digital signature
Re: pbuilder
On Thu, 27 Feb 2014 20:22:55 -0700 ghaverla ghave...@materialisations.com wrote: I guess I am trapped by an update that is midway through. I was meaning to recompile hplip, and one suggestion was pbuilder. The update wen through today. I do not know what the intended way to update the sudoers file is. What I did was edit /usr/share/psycho/users/uid (where uid=debian) to enter the following: = Cmnd_Alias PBUILDER = /usr/sbin/pbuilder /usr/lib/pbuilder/pbuilder-satsifydepends debian ALL = (root) NOPASSWD:SETENV: PBUILDER #debian ALL = NOPASSWD: /usr/sbin/pbuilder #debian ALL = NOPASSWD: /usr/lib/pbuilder/pbuilder-satsifydepends = This at least lets pbuilder run a long time, before dying with what seems a fairly common problem. cp: cannot stat 'debian/tmp/etc/dbus-1': No such file or directory. So, I will see what http://wiki.debian.org/qa.debian.org/FTBFS turns up. Gord -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140228132126.32db8df7@newmain.materia
pbuilder
I guess I am trapped by an update that is midway through. I was meaning to recompile hplip, and one suggestion was pbuilder. I set up a new user to do the compiling under, and was hoping to put the pbuilder environment in that HOME. It took a few tries to get pbuilder create from building everything in /var/cache. Got passed that. I made my few changes to the hplip package, and tried to build it. I kept having sudo kill the process because of some environment variable. The same error message goes back 4 years (or more), I seen numerous suggestions for changes to sudoers, and a few for command lines, nothing changed. Sudo killed things midway through. Well, I still had things in /var/cache, so I altered my .pbuilderrc file to once again point to /var/cache. The pbuilder process went further. Right away, pbuilder noticed I had some dependencies missing, and went about trying to satisfy them. Well, my normal apt-get has a stack of 100 or so packages that I am holding off on upgrading (many waiting for a necessary X upgrade). So instead of pbuilder just looking to upgrade half a dozen packages, it felt it needed to upgrade all of them, not just the half dozen it needed. Earlier, I had discovered I was missing libsnmp-dev and libdbus-1-dev (playing with ./configure), so it would seem that something in the debian control information for hplip is missing those 2. Those 2 were among the half dozen that pbuilder later wanted to update. After killing this runaway update I didn't want to do, I tried to manually upgrade the half dozen or so packages that pbuilder was anxious about, and most of them it says are fine on my system, a couple are trapped until some cups updates come through I guess. I can live with printing being down for a couple of days, maybe those packages will show up, and I can try building new base.tar files that supposedly have all the depends in them. I guess if I unbundle the tarball, chroot in, I should just be able to apt-get what is missing and rebundle the tarball. But, it would seem that whatever environment variable(s) is involved, the bug in pbuilder was fixed for the circumstance where everything is in /var/cache, but not if the build environment is somewhere under /home/. I have two other emergencies I was supposed to drop everything for, so I am moving on to them. If someone had more (useful) ideas on things to try with pbuilder in /home, I can try those tomorrow or Saturday I guess. If people were interested in this report, wonderful. If not, well I got some more typing practice. Gord -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140227202255.397564f2@newmain.materia
Re: Comment ne générer que les paquets binaires avec pbuilder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour à tous, Je reviens à la charge avec mes soucis pbuilder/reprepro Cette fois, c'est reprepro qui me pose problème: La génération des paquets binaires fonctionne bien, certains paquets source générent les paquets dépendants d'une architecture (suffixes i386 ou amd64) et d'autres indépendants (suffixe all). Lors de l'inclusion dans le dépôt, reprepro va chercher le fichier .changes correspondant à la compilation i386 et amd64. Pour chacune de ces architectures, reprepro va essayer d'inclure les paquets 'all'. Résultat, ces paquets 'all' provoquent un conflit car ils n'ont pas la même somme de hashage d'une architecture à l'autre. Dans le man de reprepro, je suis tombé sur l'option -A: Note that architecture all packages can be included to each architecture but are then handled separately. Thus using -A correctly allows to have different versions of an architecture all package in different architectures of the same distribution. Ceci semble bien devoir répondre à mon problème, mais malheureusement je ne trouve pas la bonne manière de spécifier cette option pour gérer plusieurs version des packages 'all' au sein d'une même distribution. Bref, je suis preneur de toute indication, Cordialement, JB On 19/05/2012 12:34, Jean Baptiste FAVRE wrote: On 19/05/2012 01:39, Charles Plessy wrote: Le Fri, May 18, 2012 at 07:17:38PM +0200, Jean Baptiste FAVRE a écrit : Y-a-t'il moyen de dire à pbuilder de ne générer que les paquets binaires, si oui comment (je n'ai pas vu l'option dans le man et Google n'est pas prolixe sur le sujet). Bonjour, Il faut dire à pbuilder de le dire à dpkg-buildpackage avec l'option --debbuildopts. Ah ben oui, forcément... bon, je retourne à la lecture du man alors :-) Merci, JB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/KFHgACgkQM2eZoKJfKd2xQQCfVJgazsAmLmUGr9xL2KiHGn/5 YfYAn25j+iEo8xjnqFaBu/YUQmOJmBSB =7+nU -END PGP SIGNATURE- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/4fca148b.5050...@jbfavre.org
Re: Comment ne générer que les paquets binaires avec pbuilder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/05/2012 01:39, Charles Plessy wrote: Le Fri, May 18, 2012 at 07:17:38PM +0200, Jean Baptiste FAVRE a écrit : Y-a-t'il moyen de dire à pbuilder de ne générer que les paquets binaires, si oui comment (je n'ai pas vu l'option dans le man et Google n'est pas prolixe sur le sujet). Bonjour, Il faut dire à pbuilder de le dire à dpkg-buildpackage avec l'option --debbuildopts. Ah ben oui, forcément... bon, je retourne à la lecture du man alors :-) Merci, JB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+3dyMACgkQM2eZoKJfKd2yvQCeNtTcdDCVue977voHajS8AnH7 fm0An36rCBwYLqQwKX3TAHatmDR5weJZ =A35t -END PGP SIGNATURE- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/4fb77723.9040...@jbfavre.org
Comment ne générer que les paquets binaires avec pbuilder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonsoir, J'essaie de packager des paquets Debian, autant pour apprendre que parce que j'en ai besoin pour le boulot. Histoire de faire les choses bien, j'utilise pbuilder pour être sûr des dépendances. Comme pbuilder réclame un paquet source, je génère ce dernier sur ma machine (en Squeeze, amd64). J'obtiens bien les fichier voulus, notamment le .dsc Lors de la compilation par pbuilder (2 distrib, 2 architectures, soit 4compilations), j'obtiens bien les paquets binaires, mais également les paquets sources (donc en quadruple), tous légèrement différents des premiers. Du coup, je ne sais pas trop quels paquets sources importer dans mon dépôts que je gère avec reprepro. Y-a-t'il moyen de dire à pbuilder de ne générer que les paquets binaires, si oui comment (je n'ai pas vu l'option dans le man et Google n'est pas prolixe sur le sujet). Si non, je choisis quel paquet source pour l'inclusion dans le dépôt ? Cordialement, JB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+2hBgACgkQM2eZoKJfKd1HxQCfUXoffDUu5G2yQLeumUY9txKx IoEAn2wRZBOZP+a4xhAjOUpSOcAjJvvH =eeZk -END PGP SIGNATURE- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/4fb68432.1010...@jbfavre.org
Re: Comment ne générer que les paquets binaires avec pbuilder
Le Fri, May 18, 2012 at 07:17:38PM +0200, Jean Baptiste FAVRE a écrit : Y-a-t'il moyen de dire à pbuilder de ne générer que les paquets binaires, si oui comment (je n'ai pas vu l'option dans le man et Google n'est pas prolixe sur le sujet). Bonjour, Il faut dire à pbuilder de le dire à dpkg-buildpackage avec l'option --debbuildopts. Amicalement, -- Charles Plessy Tsurumi, Kanagawa, Japon -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120518233909.ga4...@falafel.plessy.net
pbuilder and CONCURRENCY_LEVEL
How can I set CONCURRENCY_LEVEL when using pbuilder? CONCURRENCY_LEVEL=9 pbuilder build file.dsc doesn't work. Thank you, Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daefc2a.3050...@gmail.com
Re: pbuilder and CONCURRENCY_LEVEL
Il 20/04/2011 17:30, Niccolò Belli ha scritto: How can I set CONCURRENCY_LEVEL when using pbuilder? CONCURRENCY_LEVEL=9 pbuilder build file.dsc doesn't work. Found it, there is an option to pass parameters to dpkg-buildpackage: --debbuildopts -j9 Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daf5bb5.3050...@gmail.com
Re: pbuilder and ${shlibs:Depends}
On Thu, Mar 17, 2011 at 01:44:02PM +0200, Panayiotis Karabassis wrote: Hi, I have a question regarding pbuilder. You will *probably* have better luck asking this question on the debian-mentors mailing list. -- Religion is excellent stuff for keeping common people quiet. -- Napoleon Bonaparte -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110318103406.GD19385@fischer
Re: pbuilder and ${shlibs:Depends}
True. I will do just that. Only problem I'm not actually a Debian Maintainer. Anyway, thanks. On 03/18/2011 12:34 PM, Chris Bannister wrote: On Thu, Mar 17, 2011 at 01:44:02PM +0200, Panayiotis Karabassis wrote: Hi, I have a question regarding pbuilder. You will *probably* have better luck asking this question on the debian-mentors mailing list. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d836edf.1040...@gmail.com
pbuilder and ${shlibs:Depends}
Hi, I have a question regarding pbuilder.
My Debian package uses ${shlibs:Depends} in its Depends field.
However, in a pbuilder environment not all dependencies are installed,
and hence ${shlibs:Depends} does not expand to *all* real dependencies.
My question is: how do I add the missing dependencies?
a) Put them in Build-Depends so dpkg-shlibdeps can find them? (ugly)
b) Drop ${shlibs:Depends} and list them manually?
c) Something else?
What is the recommended way?
Thanks and regards,
Panayiotis
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d81f402.9010...@gmail.com
pbuilder ignoring trust violations
I'm playing around with pbuilder. While building a package, pbuilder needed to reference another package that I built and did not sign. Pbuilder happily ignored the lack of signature and gave this warning, but did not pause so I could read it: Untrusted packages could compromise your system's security. You should only proceed with the installation if you are certain that this is what you want to do. debhelper *** WARNING *** Ignoring these trust violations because aptitude::CmdLine::Ignore-Trust-Violations is 'true'! I'd like to change this behavior so that pbuilder at least stops and asks me how to proceed. I've been looking through the man pages and googling, but I'm not seeing it. Thanks -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100613030628.gb10...@aurora.owens.net
Re: pbuilder ignoring trust violations -- SOLVED (sort of)
On Sat, Jun 12, 2010 at 11:06:28PM -0400, Rob Owens wrote: I'm playing around with pbuilder. While building a package, pbuilder needed to reference another package that I built and did not sign. Pbuilder happily ignored the lack of signature and gave this warning, but did not pause so I could read it: Untrusted packages could compromise your system's security. You should only proceed with the installation if you are certain that this is what you want to do. debhelper *** WARNING *** Ignoring these trust violations because aptitude::CmdLine::Ignore-Trust-Violations is 'true'! I'd like to change this behavior so that pbuilder at least stops and asks me how to proceed. I've been looking through the man pages and googling, but I'm not seeing it. I've found a couple of bugs referencing this problem, and the pbuilder devs seem to think this is the way it should be. I disagree, so I worked around it like this: In /usr/lib/pbuilder I made a copy of pbuilder-satisfydepends-aptitude, and called it pbuilder-satisfydepends-aptitude-safe. I edited the safe file and changed Ignore-Trust-Violations=true to Ignore-Trust-Violations=false Then in my ~/.pbuilderrc I added the line PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-aptitude-safe Now pbuilder exits when it encounters an unsigned deb. As far as I can tell, that is. I'm still in the process of testing it but so far it seems to work. If anyone knows of a better way, please post it. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010061304.ga10...@aurora.owens.net
Re: Exporting ARCH to pbuilder through pdebuild?
2009/6/12 Boyd Stephen Smith Jr. b...@iguanasuicide.net: In 20090612042628.gk9...@penguin.codegnome.org, Todd A. Jacobs wrote: Why is pbuilder still using /var/cache/pbuilder/sid-amd64-base.tgz instead of the correct /var/cache/pbuilder/sid-i386-base.tgz in this instance? This is a question better suited for debian-devel or debian-mentors. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/ I use the following on a 64 bit box to build 32 and 64bit packages in a pbuilder chroot $ls -l /usr/bin/pbuilder-lenny-amd64 lrwxrwxrwx 1 root root 15 2008-03-17 12:02 /usr/bin/pbuilder-lenny-amd64 - pbuilder-custom $cat /usr/bin/pbuilder-custom #!/bin/sh # script from Jamin W. Collins BTS: #255165 # name this script 'pbuilder-woody', 'pbuilder-sid', 'pbuilder-sarge', 'pbuilder-experimental' etc. OPERATION=$1 DISTRIBUTION=`basename $0 | cut -f2 -d '-'` ARCH=`basename $0 | cut -f3 -d '-'` PROCEED=false BASE_DIR=/var/cache/pbuilder case $OPERATION in create|update|build|clean|login|execute ) PROCEED=true ;; esac if ( $PROCEED == true ) then shift sudo linux32 pbuilder $OPERATION \ --debootstrapopts --arch --debootstrapopts $ARCH \ --basetgz $BASE_DIR/$DISTRIBUTION-$ARCH-base.tgz \ --distribution $DISTRIBUTION \ --buildresult $BASE_DIR/result $@ else echo Invalid command... echo Valid commands are: echocreate echoupdate echobuild echoclean echologin echoexecute exit 1 fi Anton -- Anton Piatek email: an...@piatek.co.uk blog/photos:http://www.strangeparty.com pgp: [0xB307BAEF] (http://www.strangeparty.com/anton.asc) fingerprint: 116A 5F01 1E5F 1ADE 78C6 EDB3 B9B6 E622 B307 BAEF No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Exporting ARCH to pbuilder through pdebuild?
In 20090612042628.gk9...@penguin.codegnome.org, Todd A. Jacobs wrote: Why is pbuilder still using /var/cache/pbuilder/sid-amd64-base.tgz instead of the correct /var/cache/pbuilder/sid-i386-base.tgz in this instance? This is a question better suited for debian-devel or debian-mentors. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Exporting ARCH to pbuilder through pdebuild?
I have some configurations inside of my ~/.pbuilderrc that depend on the
value of ARCH in the environment. However, if I call pbuilder through
pdebuild, it doesn't seem to be picking up the ARCH environment
variable.
Currently, I'm calling it like so:
export ARCH=i386
pdebuild --auto-debsign --buildresult /tmp/$(basename $PWD) \
--debsign-k 0xABCDEFGH
but pbuilder doesn't pick it up here:
: ${ARCH:=$(dpkg --print-architecture)}
How can I ensure that pdebuild is passing on the right architecture to
pbuilder?
--
Oh, look: rocks!
-- Doctor Who, Destiny of the Daleks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Exporting ARCH to pbuilder through pdebuild?
Here is the complete .pbuilderrc:
: ${ARCH:=$(dpkg --print-architecture)}
EXTRAPACKAGES=$EXTRAPACKAGES fakeroot
USEPROC=yes
USEDEVPTS=yes
USEDEVFS=no
APTCACHEHARDLINK=yes
REMOVEPACKAGES=lilo
HOOKDIR=
export DEBIAN_FRONTEND=noninteractive
BUILDSOURCEROOTCMD=fakeroot
PBUILDERROOTCMD=sudo
DEBBUILDOPTS=-si -i
BUILDUSERID=1234
BUILDUSERNAME=pbuilder
BINDMOUNTS=
DEBOOTSTRAPOPTS[0]='--variant=buildd'
export PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
export SHELL=/bin/bash
DEBOOTSTRAP=debootstrap
PKGNAME_LOGFILE_EXTENTION=_$ARCH.build
PKGNAME_LOGFILE=yes
AUTO_DEBSIGN=yes
UNSTABLE_CODENAME=sid
TESTING_CODENAME=squeeze
STABLE_CODENAME=lenny
STABLE_BACKPORTS_SUITE=$STABLE_CODENAME-backports
DEBIAN_SUITES=(
$UNSTABLE_CODENAME $TESTING_CODENAME $STABLE_CODENAME
unstable testing stable
)
UBUNTU_SUITES=(jaunty intrepid hardy gutsy)
DEBIAN_MIRROR=ftp.us.debian.org
MULTIMEDIA_MIRROR=deb http://www.debian-multimedia.org sid main
if [ -z ${DIST} ] [ -r debian/changelog ]; then
DIST=$(dpkg-parsechangelog | awk '/^Distribution: / {print $2}')
if $(echo experimental UNRELEASED | grep -q $DIST); then
DIST=$UNSTABLE_CODENAME
fi
fi
: ${DIST:=$(lsb_release --short --codename)}
case $DIST in
unstable)
DIST=$UNSTABLE_CODENAME
;;
testing)
DIST=$TESTING_CODENAME
;;
stable)
DIST=$STABLE_CODENAME
;;
esac
NAME=$DIST
if [ -n ${ARCH} ]; then
NAME=$NAME-$ARCH
DEBOOTSTRAPOPTS=(--arch $ARCH ${debootstrapop...@]})
fi
BASETGZ=/var/cache/pbuilder/$NAME-base.tgz
DISTRIBUTION=$DIST
BUILDRESULT=/var/cache/pbuilder/$NAME/result/
APTCACHE=/var/cache/pbuilder/$NAME/aptcache/
BUILDPLACE=/var/cache/pbuilder/build/
if $(echo ${debian_suit...@]} | grep -q $DIST); then
MIRRORSITE=http://$DEBIAN_MIRROR/debian/;
COMPONENTS=main contrib non-free
OTHERMIRROR=$OTHERMIRROR | $MULTIMEDIA_MIRROR
EXTRAPACKAGES=$EXTRAPACKAGES debian-multimedia-keyring
if $(echo $STABLE_CODENAME stable | grep -q $DIST); then
EXTRAPACKAGES=$EXTRAPACKAGES debian-backports-keyring
OTHERMIRROR=$OTHERMIRROR | deb http://www.backports.org/debian
$STABLE_BACKPORTS_SUITE $COMPONENTS
fi
elif $(echo ${ubuntu_suit...@]} | grep -q $DIST); then
MIRRORSITE=http://$UBUNTU_MIRROR/ubuntu/;
COMPONENTS=main restricted universe multiverse
else
echo Unknown distribution: $DIST
exit 1
fi
#echo $BASETGZ
#exit
Note that when the last two lines are uncommented, the basetgz is correctly
reported based on the architecture (as defined by ARCH) as one of the
following:
- /var/cache/pbuilder/sid-amd64-base.tgz
- /var/cache/pbuilder/sid-i386-base.tgz
However, when called with:
ARCH=i386 pdebuild --auto-debsign --buildresult /tmp/$(basename $PWD)
pbuilder still attemps to use the amd64 tarball. I can only get around
this by explicitly calling it with:
-- --basetgz /var/cache/pbuilder/sid-i386-base.tgz
appended to the end of the pdebuild command line.
Why is pbuilder still using /var/cache/pbuilder/sid-amd64-base.tgz
instead of the correct /var/cache/pbuilder/sid-i386-base.tgz in this
instance?
--
Oh, look: rocks!
-- Doctor Who, Destiny of the Daleks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble -- bingo!
For some reason, I only saw this mail now. Thanks much for the mouthful: On Sun, Dec 28, 2008 at 7:38 AM, Osamu Aoki os...@debian.org wrote: Hi, On Sat, Dec 27, 2008 at 07:26:38PM +0200, Tshepang Lekhonkhobe wrote: ... Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. You are creating very special setting. I do not even know if you have /home/wena/live/ directory or your mirror site at http://localhost/sid works or not... I do not know permision of all these either. /home/wena/live exists and that mirror pretty well and was created using reprepro. When you have problem, do not assume thigs are in good shape. Are you sure to be mirror pretty well? reprepro being very new and experimental per its manpage. I do not know it is good choice. (Program should be fine but it may not document required options for novice users.) I'm on Sid. OK My first suggestion is to put system back to default. I stripped pbuilderrc to: MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap [note that cdebootstrap won't work since I don't have Release.gpg and I don't know how to parse --allow-authenticated to it through pbuilder] ...and am still getting the error above Bingo! ... you have broken mirror for current sid repo. Having Release.gpg is needed for current secure APT to function. reprepro can support signiture per its package description. http://wiki.debian.org/SecureApt http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#toplevelreleasefeandauthenticity What's interesting is that both debootstrap and cdebootstrap --allow-unauthenticated work pretty well. Of course, you are disabling secure apt feature which uses Release.gpg. If you are thinking about reducing bandwidth usage by the local mirror, I think http proxy is better approach. Mirroring tends to waste more BW by downloading unused contents. http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#proxyserverforapt | Since mirroring whole subsection of Debian archive wastes disk space and | network bandwidth, deployment of a local proxy server for APT is | desirable consideration when you administer many systems on LAN. APT can | be configure to use web (http) proxy server such as squid (see Section | 7.5, Other network application servers) as described in apt.conf(5) | and in /usr/share/doc/apt/examples/configure-index.gz. The http_proxy | environment variable can be used to override proxy server setting in the | /etc/apt/apt.conf file. You may wish to learn basics of APT http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html Osamu -- my place on the web: floss-and-misc.blogspot.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble
anyone who can help with this? On Wed, Dec 17, 2008 at 10:34 AM, Tshepang Lekhonkhobe tshep...@gmail.com wrote: Hi, I'm having trouble getting pbuilder create run with the following error: START [...] I: Configuring initscripts... I: Configuring sysvinit... I: Unpacking the base system... W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. pbuilder: debootstrap failed - Aborting with an error - cleaning the build env - removing directory /home/wena/live/pbuilder/build//25743 and its subdirectories END My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. -- my place on the web: floss-and-misc.blogspot.com -- my place on the web: floss-and-misc.blogspot.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble
Tshepang Lekhonkhobe wrote: anyone who can help with this? On Wed, Dec 17, 2008 at 10:34 AM, Tshepang Lekhonkhobe tshep...@gmail.com wrote: Hi, I'm having trouble getting pbuilder create run with the following error: [snip] I would suggest asking in debian-mentors@ instead. Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ developer, Debian Maintainer, APT contributor signature.asc Description: OpenPGP digital signature
Re: pbuilder trouble
Hi, On Wed, Dec 17, 2008 at 10:34:42AM +0200, Tshepang Lekhonkhobe wrote: Hi, I'm having trouble getting pbuilder create run with the following error: ... My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. You are creating very special setting. I do not even know if you have /home/wena/live/ directory or your mirror site at http://localhost/sid works or not... I do not know permision of all these either. Also you did not say what distribution sid/lenny/etch/... using... My first suggestion is to put system back to default. Osamu FYI: my ~/.pbuilderrc (essential parts for sid/lenny) MIRRORSITE=http://ftp.jp.debian.org/debian AUTO_DEBSIGN=yes BUILDRESULT=/var/cache/pbuilder/result/ DISTRIBUTION=sid DEBBUILDOPTS=-i -I -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble
On Sat, Dec 27, 2008 at 2:28 PM, Osamu Aoki os...@debian.org wrote: Hi, On Wed, Dec 17, 2008 at 10:34:42AM +0200, Tshepang Lekhonkhobe wrote: Hi, I'm having trouble getting pbuilder create run with the following error: ... My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. You are creating very special setting. I do not even know if you have /home/wena/live/ directory or your mirror site at http://localhost/sid works or not... I do not know permision of all these either. /home/wena/live exists and that mirror pretty well and was created using reprepro. Also you did not say what distribution sid/lenny/etch/... using... I'm on Sid. My first suggestion is to put system back to default. I stripped pbuilderrc to: MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap [note that cdebootstrap won't work since I don't have Release.gpg and I don't know how to parse --allow-authenticated to it through pbuilder] ...and am still getting the error above What's interesting is that both debootstrap and cdebootstrap --allow-unauthenticated work pretty well. -- my place on the web: floss-and-misc.blogspot.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble -- bingo!
Hi, On Sat, Dec 27, 2008 at 07:26:38PM +0200, Tshepang Lekhonkhobe wrote: ... Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. You are creating very special setting. I do not even know if you have /home/wena/live/ directory or your mirror site at http://localhost/sid works or not... I do not know permision of all these either. /home/wena/live exists and that mirror pretty well and was created using reprepro. When you have problem, do not assume thigs are in good shape. Are you sure to be mirror pretty well? reprepro being very new and experimental per its manpage. I do not know it is good choice. (Program should be fine but it may not document required options for novice users.) I'm on Sid. OK My first suggestion is to put system back to default. I stripped pbuilderrc to: MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap [note that cdebootstrap won't work since I don't have Release.gpg and I don't know how to parse --allow-authenticated to it through pbuilder] ...and am still getting the error above Bingo! ... you have broken mirror for current sid repo. Having Release.gpg is needed for current secure APT to function. reprepro can support signiture per its package description. http://wiki.debian.org/SecureApt http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#toplevelreleasefeandauthenticity What's interesting is that both debootstrap and cdebootstrap --allow-unauthenticated work pretty well. Of course, you are disabling secure apt feature which uses Release.gpg. If you are thinking about reducing bandwidth usage by the local mirror, I think http proxy is better approach. Mirroring tends to waste more BW by downloading unused contents. http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#proxyserverforapt | Since mirroring whole subsection of Debian archive wastes disk space and | network bandwidth, deployment of a local proxy server for APT is | desirable consideration when you administer many systems on LAN. APT can | be configure to use web (http) proxy server such as squid (see Section | 7.5, “Other network application servers”) as described in apt.conf(5) | and in /usr/share/doc/apt/examples/configure-index.gz. The http_proxy | environment variable can be used to override proxy server setting in the | /etc/apt/apt.conf file. You may wish to learn basics of APT http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
pbuilder trouble
Hi, I'm having trouble getting pbuilder create run with the following error: START [...] I: Configuring initscripts... I: Configuring sysvinit... I: Unpacking the base system... W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. pbuilder: debootstrap failed - Aborting with an error - cleaning the build env - removing directory /home/wena/live/pbuilder/build//25743 and its subdirectories END My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END Running (c)debootstrap alone gives no problems so I don't know where to start diagnosing my problem. -- my place on the web: floss-and-misc.blogspot.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble
On Wed, Dec 17, 2008 at 10:34:42AM +0200, Tshepang Lekhonkhobe wrote: Hi, I'm having trouble getting pbuilder create run with the following error: START [...] Are you sure you haven't snipped out any error message? I: Configuring initscripts... I: Configuring sysvinit... I: Unpacking the base system... W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. pbuilder: debootstrap failed - Aborting with an error - cleaning the build env - removing directory /home/wena/live/pbuilder/build//25743 and its subdirectories END My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder trouble
On Wed, Dec 17, 2008 at 11:01 AM, Tzafrir Cohen tzaf...@cohens.org.il wrote: On Wed, Dec 17, 2008 at 10:34:42AM +0200, Tshepang Lekhonkhobe wrote: Hi, I'm having trouble getting pbuilder create run with the following error: START [...] Are you sure you haven't snipped out any error message? pbuilder does get frustratingly quiet; it's --debug option doesn't spit anything that helps me I: Configuring initscripts... I: Configuring sysvinit... I: Unpacking the base system... W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. W: Failure while installing base packages. This will be re-attempted up to five times. pbuilder: debootstrap failed - Aborting with an error - cleaning the build env - removing directory /home/wena/live/pbuilder/build//25743 and its subdirectories END My /etc/pbuilerrc looks thus: START MIRRORSITE=http://localhost/sid DEBOOTSTRAP=debootstrap BUILDPLACE=/home/wena/live/pbuilder/build/ BASETGZ=/home/wena/live/pbuilder/base.tgz BUILDRESULT=/home/wena/live/pbuilder/result/ APTCACHE=/home/wena/live/pbuilder/aptcache END -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- my place on the web: floss-and-misc.blogspot.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pbuilder/chroot problems
On 2008-11-09 01:06 +0100, Boyd Stephen Smith Jr. wrote: I'm trying to set up a pbuilder environment on my laptop, and it's failing with this error: W: Failure trying to run: chroot /home/bss/debootstrap-test dpkg --force-depends --install var/cache/apt/archives/libc6_2.7-16_amd64.deb I tried etch instead of sid, thinking it might be some unstable breakage, and got an error that only differed in the version of libc6. The error looked to be coming for debootstrap, so I tried debootstrapping manually (variant=buildd) and got the same error. Then, I attempted to to the chroot command directly, and got a bit more verbose output ending in: Setting up libc6 (2.7-16) ... sh: /dev/null: Permission denied sh: /dev/null: Permission denied My crystal ball tells me that /home is mounted with the `nodev' option. Correct? Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbuilder/chroot problems
On Sunday 09 November 2008 03:05, Sven Joachim wrote: On 2008-11-09 01:06 +0100, Boyd Stephen Smith Jr. wrote: I attempted to to the chroot command directly, and got a bit more verbose output ending in: Setting up libc6 (2.7-16) ... sh: /dev/null: Permission denied sh: /dev/null: Permission denied My crystal ball tells me that /home is mounted with the `nodev' option. Correct? Brilliant! Yeah, that's my problem. I guess I was expecting 'nodev' to cause some other error, perhaps on device creation. I was initially creating my pbuilder chroots on in /var/cache and that's also mounted 'nodev'. I know chroots will need special attention but, are there any guidelines as to what filesystems are generally safe to mount 'nodev' (and 'nosuid')? -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/ pgpRhfzlhiLHU.pgp Description: PGP signature
pbuilder/chroot problems
I'm trying to set up a pbuilder environment on my laptop, and it's failing with this error: W: Failure trying to run: chroot /home/bss/debootstrap-test dpkg --force-depends --install var/cache/apt/archives/libc6_2.7-16_amd64.deb I tried etch instead of sid, thinking it might be some unstable breakage, and got an error that only differed in the version of libc6. The error looked to be coming for debootstrap, so I tried debootstrapping manually (variant=buildd) and got the same error. Then, I attempted to to the chroot command directly, and got a bit more verbose output ending in: Setting up libc6 (2.7-16) ... sh: /dev/null: Permission denied sh: /dev/null: Permission denied debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 75.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype sh: /dev/null: Permission denied sh: /dev/null: Permission denied /var/lib/dpkg/info/libc6.postinst: line 29: /dev/null: Permission denied dpkg: error processing libc6 (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: libc6 I checked the permissions of /dev/null inside the chroot and they are identical to the permissions outside the chroot: crw-rw-rw- 1 root root 1, 3 2007-05-21 10:31 debootstrap-test/dev/null crw-rw-rw- 1 root root 1, 3 2008-11-08 03:35 /dev/null Outside the chroot, I can write to either device as any user. Once I've chrooted, writing fails: sh-3.2# id uid=0(root) gid=0(root) groups=0(root) sh-3.2# echo foo /dev/null sh: /dev/null: Permission denied I can only assume that the issue is introduced by the chroot command. The chroot I'm using comes from coreutils-5.97-5.3. However, my VPS has the same version of coreutils, and it does not show similar behavior: [EMAIL PROTECTED]:~$ sudo cowbuilder --login --basepath /var/cache/pbuilder/sid.cow Password: - Copying COW directory - Invoking pbuilder - Running in no-targz mode - copying local configuration - mounting /proc filesystem - mounting /dev/pts filesystem - policy-rc.d already exists Obtaining the cached apt archive contents - entering the shell [EMAIL PROTECTED]:/# echo foo /dev/null [EMAIL PROTECTED]:/# echo $? 0 (I use cowbuilder there, but error occurs with both cowbuilder and pbuilder.) Since the chroot command delegates most of the heavy lifting to the chroot system call, I thought that this change in behavior might be due to differing kernel versions. The VPS (working) is 2.6.24-19-xen (uname -r). The laptop (broken) is 2.6.24-etchnhalf.1-amd64. Moving back to 2.6.18-[456] on this laptop would be a little annoying -- it has Intel 3945 wireless built-in, and I prefer the iwl3945 module in 2.6.24 over the ipw3945 module in 2.6.18 -- among other things, it suspends better. I don't see a bug about this, perhaps I should file one? -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/ pgpqkWbbmDHRj.pgp Description: PGP signature
sudo pbuilder create
Hi, I am trying to run : sudo pbuilder create But all I get is an error (even with --debug) it does not make sense, here is the output: ... P: Configuring package apt P: Configuring helper cdebootstrap-helper-apt E: Couldn't install system due to errors! + echo 'pbuilder: cdebootstrap failed' pbuilder: cdebootstrap failed + exit 1 Thanks for suggestions, -- Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: i386 in amd64 system mit pbuilder und orig.tar.gz bauen
On 29/09/2006 To Debian-User-Ger wrote: ich habe ein kleines problem, mit pbuilder in meinem amd64 unstable system i386 stable packete zu bauen. folgende syntax müsste meiner meinung nach funktionieren, tut sie aber nicht: $ linux32 pdebuild --buildresult `pwd`/.. --debsign-k [EMAIL PROTECTED] \ -- --basetgz /var/cache/pbuilder/i386-sarge-base.tgz \ --debbuildopts -sa -us -uc /var/cache/pbuilder/i386-sarge-base.tgz ist wie der name schon sagt eine eine i386 sarge base.tgz für pbuilder. das packet wird einwandfrei gebaut, das problem ist aber, dass die debbuildopts (-sa -us -uc) nicht berücksichtigt werden. ich benötige jedoch einen build, bei dem die orig.tar.gz beim upload mitgesendet werden. das problem ist, dass --debbuildopts offensichtlich in diesem falle (anders als dokumentiert) nicht von pbuilder akzeptiert wird. wenn ich es direkt an pdebuild gebe, funktioniert es: $ linux32 pdebuild --buildresult `pwd`/.. --debsign-k [EMAIL PROTECTED] \ --debbuildopts -sa -us -uc -- --basetgz \ /var/cache/pbuilder/i386-sarge-base.tgz ... jonas -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
i386 in amd64 system mit pbuilder und orig.tar.gz bauen
ahoi, ich habe ein kleines problem, mit pbuilder in meinem amd64 unstable system i386 stable packete zu bauen. folgende syntax müsste meiner meinung nach funktionieren, tut sie aber nicht: $ linux32 pdebuild --buildresult `pwd`/.. --debsign-k [EMAIL PROTECTED] \ -- --basetgz /var/cache/pbuilder/i386-sarge-base.tgz \ --debbuildopts -sa -us -uc /var/cache/pbuilder/i386-sarge-base.tgz ist wie der name schon sagt eine eine i386 sarge base.tgz für pbuilder. das packet wird einwandfrei gebaut, das problem ist aber, dass die debbuildopts (-sa -us -uc) nicht berücksichtigt werden. ich benötige jedoch einen build, bei dem die orig.tar.gz beim upload mitgesendet werden. hat jemand 'ne idee? ... jonas -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
How do you include orig in pbuilder?
I usually just build packages in unstable, but I am trying to learn pbuilder. I need to build a package and include the original source in the upload. With dpkg-buildpackage I just pass in -sa to do this. How do I do it with pbuilder? -- -- Joseph Smidt [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: How do you include orig in pbuilder?
On Thu, Sep 28, 2006 at 03:25:54PM -0600, Joseph Smidt wrote: I usually just build packages in unstable, but I am trying to learn pbuilder. I need to build a package and include the original source in the upload. With dpkg-buildpackage I just pass in -sa to do this. How do I do it with pbuilder? Hi Joseph, the debian-mentors mailing list would be the place to ask for help about building debian packages. And also you can ask on debian-women list for help and mentorship. cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: How do you include orig in pbuilder?
On (28/09/06 15:25), Joseph Smidt wrote: I usually just build packages in unstable, but I am trying to learn pbuilder. I need to build a package and include the original source in the upload. With dpkg-buildpackage I just pass in -sa to do this. How do I do it with pbuilder? Hi, quoting pbuilder(8): --debbuildopts [options] List of options that are passed on to dpkg-buildpackage. Over‐ rides any value given in DEBBUILDOPTS as specified in pbuilderrc.) James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
* Charles Plessy [EMAIL PROTECTED] [2006-03-01 13:00] : On Wed, Mar 01, 2006 at 03:18:37AM +0100, Frédéric Bothamy wrote : J'ai placé un debootstrap sid sans les paquets .deb (i.e. avec un apt-get clean dans le chroot une fois celui-ci créé) à http://frederic.bothamy.free.fr/debian/sid.tar.bz2. Il fait tout de même un peu plus de 40 Mo. Merci beaucoup, il n'a fallu que douze minutes pour le télécharger. Tu peux l'effacer. J'ai maintenant un nouveau problème : sh-3.1# echo toto dev/null sh: dev/null: Permission denied pourtant, /dev/null est là : sh-3.1# ls -l /dev/null crw-rw-rw- 1 root root 1, 3 Mar 1 01:51 /dev/null une idée ? Pas trop, la seule chose qui me turlupine, c'est que tu parles une fois de dev/null et l'autre fois de /dev/null. Je suppose que tu étais placé à la racine la première fois, mais ça ne coûte rien de vérifier. Ce qui est bizarre, c'est que même si c'était une typo, il devrait de mettre Pas de fichier ou répertoire (car dev/ n'existe pas) et pas Permission refusée. Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/Writing/SmartQuestionsFr Comment signaler efficacement un bug ? http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
* Charles Plessy [EMAIL PROTECTED] [2006-02-28 15:06] : [...] En fait, le but de la manoeuvre, c'est de compiler des paquets pour sid sur une sarge. Comment les développeurs abonnés à cette liste font-ils d'habitude ? Si je n'arrive pas à avoir un chroot ni pbuilder, je me Euh, ils ne font pas, du moins, je suppose que cela doit être assez rare comme situation. Ils ont plutôt un environnement unstable complet avec un pbuilder pour vérifier les constructions des paquets. Une solution pour ton cas serait peut-être de créer un chroot sarge (ce qui doit obligatoirement fonctionner), puis de le mettre à jour vers etch ou sid à partir du chroot. Il est bien possible qu'il ne soit pas garanti que les outils d'une version stable (donc figée) puissent toujours créer le chroot d'une version instable (donc en évolution perpétuelle). Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/Writing/SmartQuestionsFr Comment signaler efficacement un bug ? http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
On Tue, Feb 28, 2006 at 01:46:04PM +0100, Frédéric Bothamy wrote : Une solution pour ton cas serait peut-être de créer un chroot sarge (ce qui doit obligatoirement fonctionner), puis de le mettre à jour vers etch ou sid à partir du chroot. Bonjour et merci pour le conseil, mais : c'est mal parti... kunpuu|debootstrap|$ sudo /usr/sbin/debootstrap testing testing E: No such script: /usr/lib/debootstrap/scripts/testing kunpuu|debootstrap|$ ls -l /usr/lib/debootstrap/scripts/ total 79 -rw-r--r-- 1 root root 5433 2005-11-06 03:35 breezy lrwxrwxrwx 1 root root3 2006-02-28 00:21 etch - sid -rw-r--r-- 1 root root 7828 2005-11-06 03:35 hoary -rw-r--r-- 1 root root 5774 2005-11-06 03:35 hoary.buildd -rw-r--r-- 1 root root 3408 2005-11-06 03:35 potato -rw-r--r-- 1 root root 8387 2005-11-06 03:35 sarge -rw-r--r-- 1 root root 5672 2005-11-06 03:35 sarge.buildd -rw-r--r-- 1 root root 5902 2005-11-06 03:35 sarge.fakechroot -rw-r--r-- 1 root root 5705 2005-11-06 03:35 sid -rw-r--r-- 1 root root 7390 2005-11-06 03:35 warty -rw-r--r-- 1 root root 5656 2005-11-06 03:35 warty.buildd -rw-r--r-- 1 root root 7722 2005-11-06 03:35 woody -rw-r--r-- 1 root root 5709 2005-11-06 03:35 woody.buildd kunpuu|debootstrap|$ et avec cdebootstrap, ça ne marche pas mieux: kunpuu|debootstrap|$ sudo /usr/bin/cdebootstrap testing testing P: Retrieving Release.gpg P: Retrieving Release P: Parsing Release P: Retrieving Packages.gz P: Validating Packages P: Parsing Packages P: Retrieving libc6 P: Validating libc6 P: Retrieving gcc-4.0-base P: Validating gcc-4.0-base (...) P: Unpacking package dselect P: Unpacking package diff P: Unpacking package base-files P: Unpacking package bash P: Unpacking package findutils E: Couldn't install system due to errors! J'ai du mal à voir si ça mérite un rapport de bug. -- Charles -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
* Charles Plessy [EMAIL PROTECTED] [2006-03-01 00:05] : On Tue, Feb 28, 2006 at 01:46:04PM +0100, Frédéric Bothamy wrote : Une solution pour ton cas serait peut-être de créer un chroot sarge (ce ^ qui doit obligatoirement fonctionner), puis de le mettre à jour vers etch ou sid à partir du chroot. Bonjour et merci pour le conseil, mais : c'est mal parti... Donc : kunpuu|debootstrap|$ sudo /usr/sbin/debootstrap testing testing E: No such script: /usr/lib/debootstrap/scripts/testing kunpuu|debootstrap|$ sudo /usr/sbin/debootstrap sarge sarge [...] J'ai du mal à voir si ça mérite un rapport de bug. Si tu reproduis le problème avec sarge sarge comme paramètres, probablement oui. Sinon, je ne pense pas. Bon, je viens de tester dans un pbuilder Sarge (lui-même sur une unstable) : # debootstrap sarge sarge [...] # chroot sarge ## vi /etc/apt/sources.list [ création d'un fichier ciblant sid ] ## apt-get update ## apt-get dist-upgrade [...] ## cat /etc/debian_version testing/unstable ## Et voilà, le chroot Sarge est devenu une Sid chrootée. Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/Writing/SmartQuestionsFr Comment signaler efficacement un bug ? http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
On Tue, Feb 28, 2006 at 08:18:57PM +0100, Frédéric Bothamy wrote : * Charles Plessy [EMAIL PROTECTED] [2006-03-01 00:05] : On Tue, Feb 28, 2006 at 01:46:04PM +0100, Frédéric Bothamy wrote : Une solution pour ton cas serait peut-être de créer un chroot sarge (ce ^ Oups, mes vieux neurones lisent encore testing là où il y a écrit sarge... qui doit obligatoirement fonctionner), puis de le mettre à jour vers etch ou sid à partir du chroot. Bonjour et merci pour le conseil, mais : c'est mal parti... Donc : kunpuu|debootstrap|$ sudo /usr/sbin/debootstrap sarge sarge re-oups, j'aurai du y penser moi-même (grosse fatigue...) Voici le résultat : P: Configuring package login P: Configuring package login P: Configuring package login E: Couldn't install system due to errors! J'ai réinstallé la version de sarge, rien n'y fait. Je suis coincé. La page de man dit « Note that you will generally need a recent version of debootstrap to do this; the version currently in stable will generally have stopped working due to changes to unstable shortly after the last release. ». J'ai quelques morceaux de sid/etch dans mon installation, donc je suppose qu'il faut être complètement en sarge, ou complètement en sid, pour pouvoir bootstraper quoi que ce soit. Quelqu'un pourrait-il mettre le tar.gz d'une sid minimale à ma disposition ? Bonne journée, -- Charles -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
* Charles Plessy [EMAIL PROTECTED] [2006-03-01 09:13] : [...] Voici le résultat : P: Configuring package login P: Configuring package login P: Configuring package login E: Couldn't install system due to errors! Les messages d'erreur ne sont pas super explicites. :-( J'ai réinstallé la version de sarge, rien n'y fait. Je suis coincé. La page de man dit « Note that you will generally need a recent version of debootstrap to do this; the version currently in stable will generally have stopped working due to changes to unstable shortly after the last release. ». J'ai quelques morceaux de sid/etch dans mon installation, donc je suppose qu'il faut être complètement en sarge, ou complètement en sid, pour pouvoir bootstraper quoi que ce soit. Quelqu'un pourrait-il mettre le tar.gz d'une sid minimale à ma disposition ? J'ai placé un debootstrap sid sans les paquets .deb (i.e. avec un apt-get clean dans le chroot une fois celui-ci créé) à http://frederic.bothamy.free.fr/debian/sid.tar.bz2. Il fait tout de même un peu plus de 40 Mo. Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/Writing/SmartQuestionsFr Comment signaler efficacement un bug ? http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
On Wed, Mar 01, 2006 at 03:18:37AM +0100, Frédéric Bothamy wrote : J'ai placé un debootstrap sid sans les paquets .deb (i.e. avec un apt-get clean dans le chroot une fois celui-ci créé) à http://frederic.bothamy.free.fr/debian/sid.tar.bz2. Il fait tout de même un peu plus de 40 Mo. Merci beaucoup, il n'a fallu que douze minutes pour le télécharger. Tu peux l'effacer. J'ai maintenant un nouveau problème : sh-3.1# echo toto dev/null sh: dev/null: Permission denied pourtant, /dev/null est là : sh-3.1# ls -l /dev/null crw-rw-rw- 1 root root 1, 3 Mar 1 01:51 /dev/null une idée ? Merci encore pour le chroot, -- Charles -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
* Charles Plessy [EMAIL PROTECTED] [2006-02-26 23:55] : Bonjour à tous, Je voulais compiler un paquet de mon crû pour sid, mais je n'arrive pas à installer un chroot ni avec pbuilder ni avec debootstrap. Deboostrap me dit : torg(chroots)$ sudo /usr/sbin/debootstrap sid sid (...) E: Couldn't download libsigc++-1.2-5c102 Je ne comprends pas très bien le problème : la page « assurance qualité » indique que le paquet en question est pourtant dans les archives : http://packages.qa.debian.org/libs/libsigc++-1.2.html Quelqu'un a-t-il un indice ? Les paquets binaires fournis par ce paquet source sont libsigc++-1.2-5c2 et libsigc++-1.2-dev. Le premier a été renommé de libsigc++-1.2-5c102 le 05/07/2005. Ta version de debootstrap est peut-être trop ancienne et contient peut-être une référence sur l'ancien paquet (cf. les rapports de bogue 334506 et 326413). Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/Writing/SmartQuestionsFr Comment signaler efficacement un bug ? http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible d'utiliser debootstrap ni pbuilder.
On Mon, Feb 27, 2006 at 10:20:48AM +0100, Frédéric Bothamy wrote : * Charles Plessy [EMAIL PROTECTED] [2006-02-26 23:55] : torg(chroots)$ sudo /usr/sbin/debootstrap sid sid (...) E: Couldn't download libsigc++-1.2-5c102 Les paquets binaires fournis par ce paquet source sont libsigc++-1.2-5c2 et libsigc++-1.2-dev. Le premier a été renommé de libsigc++-1.2-5c102 le 05/07/2005. Ta version de debootstrap est peut-être trop ancienne et contient peut-être une référence sur l'ancien paquet (cf. les rapports de bogue 334506 et 326413). effectivement... * J'ai essayé de faire un fakeroot apt-get source --build debootstrap, mais la construction se bloque sur : mkdir -p dev chown 0:0 dev chmod 755 dev (cd dev /dev/MAKEDEV generic hde hdf hdg hdh sde sdf sdg sdh scd-all initrd input usb md lp rtc video isdn-io eda edb sonycd mcd mcdx cdu535 optcd sjcd cm206cd gscd lmscd sbpcd aztcd bpcd dac960 ida fd0 fd1 ataraid cciss) * j'ai donc installé la version de sid, et là ça plante encore : I: Extracting util-linux... I: Extracting zlib1g... I: Installing core packages... W: Failure trying to run: chroot /usr/local/debootstrap/sid dpkg --force-depends --install var/cache/apt/archives/libc6_2.3.6-2_i386.deb * J'ai mis les coreutils à jour (pour chroot), ce qui a entraîné un changement de libc, mais ça ne marche toujours pas. * Qu'à cela ne tienne, je ré-essaye avec pbuilder de sid : kunpuu|pbuilder|$ sudo /usr/sbin/pbuilder create --distribution sid --override-config W: /.pbuilderrc does not exist Distribution is sid. Building the build environment - running cdebootstrap E: cdebootstrap does not exist, install or change DEBOOTSTRAP option Tiens, un nouvel outil... Je l'installe, mais pbuilder échoue encore : P: Unpacking package findutils P: Unpacking package util-linux E: Couldn't install system due to errors! pbuilder: cdebootstrap failed - Aborting with an error - cleaning the build env - removing directory /var/cache/pbuilder/build//7627 and its subdirectories * Un dernier essai avec cdebootstrap : kunpuu|debootstrap|$ sudo /usr/sbin/cdebootstrap sid cdeb_sid I: Retrieving Release I: Retrieving Packages I: Validating Packages (...) P: Unpacking package findutils P: Unpacking package util-linux E: Couldn't install system due to errors! Là encore, ça ne marche pas. En fait, le but de la manoeuvre, c'est de compiler des paquets pour sid sur une sarge. Comment les développeurs abonnés à cette liste font-ils d'habitude ? Si je n'arrive pas à avoir un chroot ni pbuilder, je me sens coincé... Et comme la machine n'a ni lecteur de disquette, ni lecteur de disque dur, et qu'elle me sert de routeur (http://charles-miroir.plessy.org/kunpuu/), je n'ai pas vraiment l'intention d'installer un multiboot (derrière le routeur, c'est du powerpc, donc pas de compilation pour i386 non plus...). -- Charles Plessy -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Impossible d'utiliser debootstrap ni pbuilder.
Bonjour à tous, Je voulais compiler un paquet de mon crû pour sid, mais je n'arrive pas à installer un chroot ni avec pbuilder ni avec debootstrap. Deboostrap me dit : torg(chroots)$ sudo /usr/sbin/debootstrap sid sid (...) E: Couldn't download libsigc++-1.2-5c102 Je ne comprends pas très bien le problème : la page « assurance qualité » indique que le paquet en question est pourtant dans les archives : http://packages.qa.debian.org/libs/libsigc++-1.2.html Quelqu'un a-t-il un indice ? -- Charles -- Pensez à lire la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Pensez à rajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sarge pbuilder Problem
Hallo, ich versuche gerade mit der Sarge pbuilder Version ein sid-chroot zu erzeugen. Leider scheitert das, da anscheinend die debootstrap Version dafür zu alt ist und versucht Pakete zu installieren die es unter sid nicht mehr gibt (slang1a-utf8). Wie löst man das Problem? Ich vermute mal, es wird nur über Backports von pbuilder+debootstrap gehen oder? Markus Schulz -- Is that verb regular? Does ich kann den Mond sprengen sound less awkward than ich kann den Mond explodieren ? The first sentence is correct, the second one is just nonsense. But you will need quite a big amount of explosives to do so. I'm sure America has plenty. :)
pbuilder und apt-ftparchive
Hallo, ich versuche gerade unser eigenes apt-Archiv, das bisher nur sarge Pakete enthielt, auf ein komplexes apt-Archiv für verschiedene Distributionen umzustellen. Bisher hatten wir den upload der gebauten Pakete (dpkg-buildpackage) mit dupload erledigt. Dabei landeten diese einfach nur via scp auf einem via FTP erreichbaren Server und anschliessend wurden dpkg-scanpackages und dpkg-scansources dort entsprechend ausgeführt. Nun soll das ganze aber mittels pbuilder laufen. Für Sarge funktioniert das Bauen auch schon recht gut. Bei Sid hab ich beim chroot Bau noch Probleme (siehe anderes Posting). Was mir jetzt noch fehlt ist der Upload zum Server und das Einsortieren in die entsprechenden Verzeichnisse. Dafür sieht apt-ftparchive auf den ersten Blick passend aus. Leider ist Doku dazu nicht sonderlich aussagekräftig, geschweige denn weiss ich wie ich das am besten automatisieren kann in Verbindung mit pbuilder (unterschiedliche Result Pfade pro Distri sind schon gegeben). Gibts dafür vielleicht einige Hinweise oder HowTos? Hat jemand so etwas schon am Laufen? Wichtig wäre, das die Arbeit stark automatisierbar ist. D.h. ein Entwickler sollte aus seinem Source-Dir in der Lage sein das Source Package zu bauen und an den pbuilder zu übergeben. Dieser sollte dann den Rest bis zum Upload erledigen. Markus Schulz -- Ein zukünftiges Start-up mit keinen eigenen Patenten wird gezwungen sein, jeglichen Preis zu bezahlen, den die Branchenriesen ihm auferlegen wollen. Der Preis könnte hoch sein: Etablierte Unternehmen haben ein Interesse daran, künftige Konkurrenten auszuschließen. Bill Gates (1991)
Re: pbuilder und apt-ftparchive
On 19.10.05 12:14:15, Markus Schulz wrote: Was mir jetzt noch fehlt ist der Upload zum Server und das Einsortieren in die entsprechenden Verzeichnisse. Dafür sieht apt-ftparchive auf den ersten Blick passend aus. Da musst du das einsortieren aber selbst hinbekommen. Wenn ihr richtige Pakete baut, also inkl. .changes-Datei, kannst du dir debpool mal angucken. Das laeuft hier und wenn du das per cron-job laufen laesst werden die neuen Pakete aus dem incoming Verzeichnis automatisch einsortiert und die Paketlisten erneuert. debpool kann sowohl binary-only als auch source-uploads verkraften, allerdings ist das Loeschen von Paketen aus dem Repository nicht moeglich, bzw. liefert das dann Fehlermeldungen bei den folgenden debpool-Laeufen in der log-datei. Das liegt im wesentlichen daran, dass die DB von debpool nicht neu gebaut werden kann... Leider ist Doku dazu nicht sonderlich aussagekräftig, geschweige denn weiss ich wie ich das am besten automatisieren kann in Verbindung mit pbuilder (unterschiedliche Result Pfade pro Distri sind schon gegeben). Hmm, was hat das mit dem pbuilder zu tun? Zugegeben ich kenn mich mit dem Teil nicht aus... Bei debpool legst du die Pakete+.changes ins incoming Verzeichnis und den Rest uebernimmt debpool. Pakete die nicht korrekt eingeordnet werden koennen bzw. die sonst irgendwelche Probleme auftauchen landen dann in nem weiteren Verz. und man kann das Log ueberpruefen was da falsch gelaufen ist. Allerdings hat die aktuelle Version auch ein paar Probleme, eine aktualisierte koennte ich dir zukommen lassen. Irgendwie ist der Maintainer nicht so richtig aktiv. Achja: Paket gibts nur in experimental. Hat jemand so etwas schon am Laufen? apt-ftparchive generiert ja nur die Paketlisten fuer eine korrekt erstellte pool-Hierarchie. Da muesstest du wohl einiges an Skripte dazuschreiben, insbesondere musst du die Einsortierung selbst machen.. Andreas -- Do not sleep in a eucalyptus tree tonight. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: pbuilder und apt-ftparchive
On 19.10.05 12:14:15, Markus Schulz wrote: Wichtig wäre, das die Arbeit stark automatisierbar ist. D.h. ein Entwickler sollte aus seinem Source-Dir in der Lage sein das Source Package zu bauen und an den pbuilder zu übergeben. Dieser sollte dann den Rest bis zum Upload erledigen. PS: Vielleicht sind die echten Debian-Skripte ja was fuer dich, also die Pakete dak oder mini-dinstall (wohl eher letzteres). Andreas -- Excellent day for putting Slinkies on an escalator. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sarge pbuilder Problem
Markus Schulz [EMAIL PROTECTED] wrote: Hallo, ich versuche gerade mit der Sarge pbuilder Version ein sid-chroot zu erzeugen. Leider scheitert das, da anscheinend die debootstrap Version dafür zu alt ist und versucht Pakete zu installieren die es unter sid nicht mehr gibt (slang1a-utf8). Wie löst man das Problem? Ich vermute mal, es wird nur über Backports von pbuilder+debootstrap gehen oder? Oder. Du kannst ein sarge-base.tar.gz erzeugen und dann mit --override-config auf sid upgraden. Gruß, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: pbuilder und apt-ftparchive
Am Mittwoch, den 19.10.2005, 12:14 +0200 schrieb Markus Schulz:
ich versuche gerade unser eigenes apt-Archiv, das bisher nur sarge
Pakete enthielt, auf ein komplexes apt-Archiv für verschiedene
Distributionen umzustellen.
Bisher hatten wir den upload der gebauten Pakete (dpkg-buildpackage) mit
dupload erledigt. Dabei landeten diese einfach nur via scp auf einem
via FTP erreichbaren Server und anschliessend wurden dpkg-scanpackages
und dpkg-scansources dort entsprechend ausgeführt.
Nun soll das ganze aber mittels pbuilder laufen. Für Sarge funktioniert
das Bauen auch schon recht gut. Bei Sid hab ich beim chroot Bau noch
Probleme (siehe anderes Posting).
Sarge-Image erstellen, dann in der Konfigurationsdatei alles auf Sid
ändern und dann ein Update durchführen ('--override-config
--configfile /bla' nicht vergessen).
Was mir jetzt noch fehlt ist der Upload zum Server und das Einsortieren
in die entsprechenden Verzeichnisse.
Da gibt es diverse fertige Lösungen. Für entfernte Server eignen sich
vor allem debarchiver, debpool und die dak-Suite.
Dafür sieht apt-ftparchive auf den ersten Blick passend aus. Leider ist
Doku dazu nicht sonderlich aussagekräftig, geschweige denn weiss ich
wie ich das am besten automatisieren kann in Verbindung mit pbuilder
(unterschiedliche Result Pfade pro Distri sind schon gegeben).
Gibts dafür vielleicht einige Hinweise oder HowTos?
http://wiki.debian.org/HowToSetupADebianRepository
Hat jemand so etwas schon am Laufen?
Ich setze persönlich debarchiver ein (Howto ist auf der obigen Seite
auch verlinkt und wird gerade auf die neuen Features aktualisiert). Ist
recht einfach zu konfigurieren und handhaben. Dem Programm fehlt nur die
Pool-Struktur. Wenn du sehen willst, wie das am Ende aussieht, wirf
einen Blick unter http://debian.wgdd.de/debian/ (dists/).
Wichtig wäre, das die Arbeit stark automatisierbar ist. D.h. ein
Entwickler sollte aus seinem Source-Dir in der Lage sein das Source
Package zu bauen und an den pbuilder zu übergeben. Dieser sollte dann
den Rest bis zum Upload erledigen.
Alles machbar. Es gibt auch ein debarchiver mit pbuilder-Howto:
http://www.opal.dhs.org/programs/debarchiver/.
MfG Daniel
[SOLVED] Re: sarge pbuilder Problem
On Wednesday 19 October 2005 13:00, Frank Küster wrote: Markus Schulz [EMAIL PROTECTED] wrote: Hallo, ich versuche gerade mit der Sarge pbuilder Version ein sid-chroot zu erzeugen. Leider scheitert das, da anscheinend die debootstrap Version dafür zu alt ist und versucht Pakete zu installieren die es unter sid nicht mehr gibt (slang1a-utf8). Wie löst man das Problem? Ich vermute mal, es wird nur über Backports von pbuilder+debootstrap gehen oder? Oder. Du kannst ein sarge-base.tar.gz erzeugen und dann mit --override-config auf sid upgraden. Danke, an die Idee das Sarge einfach auf Sid upzugraden hatte ich garnicht gedacht. Markus Schulz -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Re: sarge pbuilder Problem
* Markus Schulz [EMAIL PROTECTED] [19-10-05 11:17]: Hallo, ich versuche gerade mit der Sarge pbuilder Version ein sid-chroot zu erzeugen. Leider scheitert das, da anscheinend die debootstrap Version dafür zu alt ist und versucht Pakete zu installieren die es unter sid nicht mehr gibt (slang1a-utf8). Wie löst man das Problem? Ich vermute mal, es wird nur über Backports von pbuilder+debootstrap gehen oder? Wirf mal einen Blick ins BTS.. Outstanding bugs -- Important bugs; Unclassified (7 bugs) #308169: debootstrap: can't mmap package info file Package: debootstrap (0.2.45-0.2); Severity: important; Reported by: Lex Spoon [EMAIL PROTECTED]; 163 days old. #308361: debootstrap: buildd variant needs libunwind7-dev libunwind7 on ia64 Package: debootstrap (0.2.45-0.2); Severity: important; Reported by: dann frazier [EMAIL PROTECTED]; 162 days old. #318281: debootstrap: Pbuilder problem for Sid with gcc 4.0 packages and libslang2 package Package: debootstrap (0.3.1.4); Severity: important; Reported by: Thomas Petazzoni [EMAIL PROTECTED]; 96 days old. #323362: Cannot build sid pbuilder environment Package: debootstrap; Severity: important; Reported by: Artur R. Czechowski [EMAIL PROTECTED]; 64 days old. #325385: debootstrap: not able to debootstrap sid Package: debootstrap (debootstrap 0.2.45-0.2); Severity: important; Reported by: Martin Zobel-Helas [EMAIL PROTECTED]; Tags: sarge; 52 days old. Es ist im Moment wohl nicht möglich sid zu bootstrapen. Bei mir ging es über den Umweg sarge und dann die sources-list angepassen. Gruss Jens -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: pbuilder und apt-ftparchive
On Wednesday 19 October 2005 13:48, Daniel Leidert wrote: [...] Alles machbar. Es gibt auch ein debarchiver mit pbuilder-Howto: http://www.opal.dhs.org/programs/debarchiver/. das klingt schon sehr gut. Danke an Dich und Andreas für den Input. Damit wird sich das bestimmt realisieren lassen. Markus Schulz
Re: pbuilder in Testing
On Tue, Sep 13, 2005 at 01:11:40AM +0200, Michael Rex wrote: ich habe ein Problem mit pbuilder. Momentan benutze ich Testing, aber um Pakete für Sid zu bauen habe ich mich mal mit pbuilder beschäftigt. Nur leider versagt es schon dabei, ein chroot-Environment für Sid zu bauen. Auf 'pbuilder create' reagiert es nach einiger Zeit mit downloaden und installieren letztendlich mit P: Configuring package apt E: Couldn't install root! pbuilder: cdebootstrap failed - Aborting with an error Das entspricht nicht ganz dem Fehler, den ich kenne. Aber in den jüngeren Erdgeschichte war der pbuilder bzw. debootstrap etwas problematisch. Ich hatte entsprechend ein paar Tipps aus dem BTS einen Workaround gefunden, der funktioniert. Siehe: http://workaround.org/moin/HowToUsePbuilder Vielleicht ist dir damit geholfen. Gruß, Christoph -- ~ ~ ~ .signature [Modified] 3 lines --100%--3,41 All -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: pbuilder in Testing
Quoth Christoph Haas: http://workaround.org/moin/HowToUsePbuilder Vielleicht ist dir damit geholfen. Jepp, hat das Problem gelöst. Danke. Bye, Michael -- They had no guns an no ties. What's your excuse this time? - I had ammo. -- User Friendly, 2001-02-10 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
pbuilder in Testing
Hi, ich habe ein Problem mit pbuilder. Momentan benutze ich Testing, aber um Pakete für Sid zu bauen habe ich mich mal mit pbuilder beschäftigt. Nur leider versagt es schon dabei, ein chroot-Environment für Sid zu bauen. Auf 'pbuilder create' reagiert es nach einiger Zeit mit downloaden und installieren letztendlich mit P: Configuring package apt E: Couldn't install root! pbuilder: cdebootstrap failed - Aborting with an error Kann mir jemand nen Tip geben, was da falsch läuft? 'pbuilder create --debug' liefert leider auch nichts mehr als diese Fehlermeldung. Ach ja, mal nebenbei: pbuilder dependet ja auf cdebootstrap und recommendet debootstrap. Soweit ich das von den Beschreibungen aus verstehe kümmern sich die beiden Pakete um dasselbe, oder übersehe ich da etwas? Also warum dieses Depends/Recommends? Bye, Michael -- They had no guns an no ties. What's your excuse this time? - I had ammo. -- User Friendly, 2001-02-10 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
pbuilder create fails on debootstrap
Hello everyone, I am playing around with Roberto Sanchez's Debian Package Customization HOWTO on http://familiasanchez.net/~roberto/?page=debcustomize. This is failing for me at the first step already: pbuilder create. To capture the output I used the following line: sudo pbuilder create output.std 2 output.err This results in almost as much error output as normal output, which isn't too comforting: $ wc -l output.* 626 output.err 760 output.std output.err: --- dpkg: base-passwd: dependency problems, but configuring anyway as you request: base-passwd depends on libc6 (= 2.3.2.ds1-4); however: Package libc6 is not installed. dpkg: base-files: dependency problems, but configuring anyway as you request: base-files depends on awk; however: Package awk is not installed. /var/lib/dpkg/info/base-files.postinst: line 8: /dev/null: Permission denied /var/lib/dpkg/info/base-files.postinst: line 9: /dev/null: Permission denied (...) dpkg: libc6: dependency problems, but configuring anyway as you request: libc6 depends on libdb1-compat; however: Package libdb1-compat is not installed. /var/lib/dpkg/info/libc6.postinst: line 97: /dev/null: Permission denied /var/lib/dpkg/info/libc6.postinst: line 99: /dev/null: Permission denied /var/lib/dpkg/info/libc6.postinst: line 1: /dev/null: Permission denied /var/lib/dpkg/info/libc6.postinst: line 1: /dev/null: Permission denied (...) dpkg: warning - ignoring pre-dependency problem ! Errors were encountered while processing: /var/cache/apt/archives/bash_2.05b-26_i386.deb /var/cache/apt/archives/e2fsprogs_1.37-2sarge1_i386.deb W: Failure while unpacking required packages. This will be attempted up to five times. umount: /var/cache/pbuilder/build/14648/./dev/pts: not found umount: /var/cache/pbuilder/build/14648/./dev/shm: not found umount: /var/cache/pbuilder/build/14648/./proc/bus/usb: not mounted pbuilder: debootstrap failed output.std looks better of course and starts like this: W: /home/maurits/.pbuilderrc does not exist Distribution is sarge. Building the build environment - running debootstrap I: Retrieving debootstrap.invalid_dists_sarge_Release I: Validating debootstrap.invalid_dists_sarge_Release I: Retrieving debootstrap.invalid_dists_sarge_main_binary-i386_Packages I: Validating debootstrap.invalid_dists_sarge_main_binary-i386_Packages I: Checking apt... I: Checking base-files... and ends with: Preparing to replace zlib1g 1:1.2.2-4 (using .../zlib1g_1%3a1.2.2-4_i386.deb) ... Unpacking replacement zlib1g ... - Aborting with an error - cleaning the build env - removing directory /var/cache/pbuilder/build//14648 and its subdirectories After all is done I am left with just the two files mentioned and nothing else, so it doesn't quite work for me. My system is sarge and the system I try to let pbuilder create is also sarge. The uncommented lines from /etc/pbuilderrc are: BASETGZ=/var/cache/pbuilder/base.tgz BUILDPLACE=/var/cache/pbuilder/build/ MIRRORSITE=ftp://download.xs4all.nl/pub/mirror/debian/ USEPROC=yes USEDEVPTS=yes USEDEVFS=no BUILDRESULT=/var/cache/pbuilder/result/ DISTRIBUTION=sarge APTCACHE=/var/cache/pbuilder/aptcache/ APTCACHEHARDLINK=yes REMOVEPACKAGES=lilo HOOKDIR= export DEBIAN_FRONTEND=noninteractive DEBEMAIL=Maurits van Rees [EMAIL PROTECTED] BUILDSOURCEROOTCMD=fakeroot PBUILDERROOTCMD=sudo DEBBUILDOPTS=-mMaurits van Rees [EMAIL PROTECTED] APTCONFDIR=/etc/apt/ BUILDUSERID=1234 DEBOOTSTRAPOPTS[0]='--variant=buildd' I tried this a while ago as well, tried some different settings, tried as root, tried adding ~/.pbuilderrc, tried adding --extrapackages libc6 awk dselect libdb1-compat to the command line, as pbuilder complained about these packages, but the output indicated that they were being installed even without that addition. Is there something wrong with the /dev that is being build? I tried adding BINDMOUNTS=/dev but that didn't work out. What could be wrong? I would appreciate any help. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 04:44:37PM +0200, Maurits van Rees wrote: What could be wrong? I would appreciate any help. It may or may not be related, but there's a thread in -devel atm about pbuilder being broken for unstable chroots. Try explicitly specifying either stable or testing. If you want sid, the recommended approach is to start with testing then update it to sid. -- Jon Dowland http://jon.dowland.name/ FD35 0B0A C6DD 5D91 DB7A 83D1 168B 4E71 7032 F238 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 04:44:37PM +0200, Maurits van Rees wrote.. I am playing around with Roberto Sanchez's Debian Package Customization HOWTO on http://familiasanchez.net/~roberto/?page=debcustomize. This is failing for me at the first step already: pbuilder create. Have a look at this: http://lists.debian.org/debian-devel/2005/07/msg00649.html ... which is a workaround. Essentially create a stable chroot first, then upgrade it to unstable. Keivn -- Kevin Coyner GnuPG key: 1024D/8CE11941 http://rustybear.com/publickey signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 03:56:13PM +0100, Jon Dowland wrote: It may or may not be related, but there's a thread in -devel atm about pbuilder being broken for unstable chroots. Try explicitly specifying either stable or testing. If you want sid, the recommended approach is to start with testing then update it to sid. AFAICT that thread is unrelated. I want sarge/stable. I tried specifying stable just now, but that results in an error: E: No such script: /usr/lib/debootstrap/scripts/stable.buildd In that directory are only files with sarge, woody, etcetera. I'll stick to sarge then. Thanks for trying though. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 01:06:11PM -0400, Kevin Coyner wrote: Have a look at this: http://lists.debian.org/debian-devel/2005/07/msg00649.html ... which is a workaround. Essentially create a stable chroot first, then upgrade it to unstable. And how do I create a stable chroot? *That* is the part that is not working for me. :( At the moment I just want a stable chroot and don't want to play yet with unstable. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 07:54:20PM +0200, Maurits van Rees wrote.. On Wed, Aug 17, 2005 at 01:06:11PM -0400, Kevin Coyner wrote: Have a look at this: http://lists.debian.org/debian-devel/2005/07/msg00649.html ... which is a workaround. Essentially create a stable chroot first, then upgrade it to unstable. And how do I create a stable chroot? *That* is the part that is not working for me. :( At the moment I just want a stable chroot and don't want to play yet with unstable. Oops. Missed the fact that you were trying to build stable at first even though it was clearly stated in your first email. In looking closer at your first email, I noticed you set: APTCONFDIR=/etc/apt/ in your .pbuilderrc file ... which means the apt sources will be copied from your setup. The default is to leave this blank. Do you have anything unordinary in your sources.list? Kevin -- Kevin Coyner GnuPG key: 1024D/8CE11941 http://rustybear.com/publickey signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 03:45:10PM -0400, Kevin Coyner wrote: In looking closer at your first email, I noticed you set: APTCONFDIR=/etc/apt/ in your .pbuilderrc file ... which means the apt sources will be copied from your setup. The default is to leave this blank. Do you have anything unordinary in your sources.list? Not really, I would say. Well, worth a try to remove that line from /etc/pbuilderrc. Nope, no change. :-/ I'll comment out some other settings and try again. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 10:13:57PM +0200, Maurits van Rees wrote: Not really, I would say. Well, worth a try to remove that line from /etc/pbuilderrc. Nope, no change. :-/ I'll comment out some other settings and try again. I tried with the following uncommented and non empty lines in both /etc/pbuilderrc and ~/.pbuilderrc: mauritsvanrees:~# cat .pbuilderrc | grep -v ^$ | grep -v # MIRRORSITE=ftp://download.xs4all.nl/pub/mirror/debian/ DISTRIBUTION=sarge export DEBIAN_FRONTEND=noninteractive BUILDSOURCEROOTCMD=fakeroot PBUILDERROOTCMD=sudo DEBBUILDOPTS=-mMaurits van Rees [EMAIL PROTECTED] It still doesn't work. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 04:44:37PM +0200, Maurits van Rees wrote: Hello everyone, I am playing around with Roberto Sanchez's Debian Package Customization HOWTO on http://familiasanchez.net/~roberto/?page=debcustomize. This is failing for me at the first step already: pbuilder create. Hi Maurits, Thanks for taking the time. To capture the output I used the following line: sudo pbuilder create output.std 2 output.err This results in almost as much error output as normal output, which isn't too comforting: $ wc -l output.* 626 output.err 760 output.std output.err: [SNIP error output] The uncommented lines from /etc/pbuilderrc are: BASETGZ=/var/cache/pbuilder/base.tgz BUILDPLACE=/var/cache/pbuilder/build/ MIRRORSITE=ftp://download.xs4all.nl/pub/mirror/debian/ USEPROC=yes USEDEVPTS=yes USEDEVFS=no BUILDRESULT=/var/cache/pbuilder/result/ DISTRIBUTION=sarge APTCACHE=/var/cache/pbuilder/aptcache/ APTCACHEHARDLINK=yes REMOVEPACKAGES=lilo HOOKDIR= export DEBIAN_FRONTEND=noninteractive DEBEMAIL=Maurits van Rees [EMAIL PROTECTED] BUILDSOURCEROOTCMD=fakeroot PBUILDERROOTCMD=sudo DEBBUILDOPTS=-mMaurits van Rees [EMAIL PROTECTED] APTCONFDIR=/etc/apt/ BUILDUSERID=1234 DEBOOTSTRAPOPTS[0]='--variant=buildd' I tried this a while ago as well, tried some different settings, tried as root, tried adding ~/.pbuilderrc, tried adding --extrapackages libc6 awk dselect libdb1-compat to the command line, as pbuilder complained about these packages, but the output indicated that they were being installed even without that addition. Is there something wrong with the /dev that is being build? I tried adding BINDMOUNTS=/dev but that didn't work out. What could be wrong? I would appreciate any help. I am inclined to think that the comment someone else made further up in the thread about the APTCONFDIR setting was right. Make sure that there is not a base.tgz alread there, remove or comment out the APTCONFDIR variable and try it again. Also, make sure that you are running at least pbuilder version 0.128. When I was on IRC a few days ago, Junichi (the developer/maintainer of pbuilder) said that it was really necessary to upgrade as there were problems with the older versions. Personally, I have version 0.128 and was able to create a new pbuilder chroot just now with a configuration that is functionally the same as yours. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto pgp8btyHMNeSf.pgp Description: PGP signature
Re: pbuilder create fails on debootstrap
Hi Roberto, On Wed, Aug 17, 2005 at 04:36:16PM -0400, Roberto C. Sanchez wrote: I am inclined to think that the comment someone else made further up in the thread about the APTCONFDIR setting was right. Make sure that there is not a base.tgz alread there, remove or comment out the APTCONFDIR variable and try it again. No, that wasn't it. See my reply to that message that probably arrived by now. Also, make sure that you are running at least pbuilder version 0.128. When I was on IRC a few days ago, Junichi (the developer/maintainer of pbuilder) said that it was really necessary to upgrade as there were problems with the older versions. Personally, I have version 0.128 and was able to create a new pbuilder chroot just now with a configuration that is functionally the same as yours. Since my system is sarge and the base.tgz I want to create is also sarge I am hoping that I can just do that with the pbuilder that comes with sarge, which is 0.123... Meanwhile I notice a bug report called pbuilder: cannot build sarge basetgz: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316135. That's for version 0.127, but might help me too. My /var partition is mounted nodev. I'll remount it dev and see if that helps. -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
[Solved] Re: pbuilder create fails on debootstrap
On Wed, Aug 17, 2005 at 11:15:00PM +0200, Maurits van Rees wrote: Meanwhile I notice a bug report called pbuilder: cannot build sarge basetgz: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316135. That's for version 0.127, but might help me too. My /var partition is mounted nodev. I'll remount it dev and see if that helps. And of course that solved it. :) I now have a shiny new /var/cache/pbuilder/base.tgz which looks fine. Thanks for thinking with me, everyone! -- Maurits van Rees | http://maurits.vanrees.org/ [Dutch/Nederlands] Public GnuPG key: http://maurits.vanrees.org/var/gpgkey.asc It can seem like you're doing just fine, but the creep's creeping into your mind. - Neal Morse signature.asc Description: Digital signature
Re: pbuilder create error
On Fri, Aug 05, 2005 at 12:00:48PM -0400, Roberto C. Sanchez wrote.. - mounting /dev/pts filesystem - installing dummy policy-rc.d /usr/bin/apt-get: error while loading shared libraries: open shared object file: No such file or directory - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//9487 and its THat is weird. I recently created a new pbuilder chroot and did not run into that problem. With some help from debian-mentors, I was pointed towards this link, which says it all. http://lists.debian.org/debian-devel/2005/07/msg00649.html Kevin -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbuilder create error
On Fri, Aug 05, 2005 at 11:04:55AM -0400, Kevin Coyner wrote: I've installed pbuilder on a sid box but keep getting hung up with the following error message whenever I try to execute: pbuilder create I've tried this on 3 different sid boxes and still get the same thing each time. Any thoughts would be appreicated. Thanks, Kevin Hi Kevin, while someone on this list (Hi Roberto) may be able to help, this subject would best be answered by the -mentor or -dev list. I am aware of various transitions taking place (gcc,aspell,xorg,apt...). These may affect this and lead to unexpected results. I think I was reading planet.debian.net and recall folks talking about this. Cheers, Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! `$' $' $ $ _ ,d$$$g$ ,d$$$b. $,d$$$b`$' g$b $,d$$b ,$P' `$ ,$P' `Y$ $$' `$ $ ' `$ $$' `$ $$ $ $$g$ $ $ $ ,$P $ $$ `$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $$ `Y$$P'$. `YP $$$P' ,$. `Y$$P'$ $. ,$. signature.asc Description: Digital signature
pbuilder create error
I've installed pbuilder on a sid box but keep getting hung up with the following error message whenever I try to execute: pbuilder create I've tried this on 3 different sid boxes and still get the same thing each time. Any thoughts would be appreicated. Thanks, Kevin Snippet of the error log follows: I: Configuring console-tools... I: Configuring libtextwrap1... I: Configuring console-common... W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. I: Base system installed successfully. - debootstrap finished - copying local configuration - Installing apt-lines Refreshing the base.tgz - upgrading packages - mounting /proc filesystem - mounting /dev/pts filesystem - installing dummy policy-rc.d /usr/bin/apt-get: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//9487 and its subdirectories -- Kevin Coyner GnuPG key: 1024D/8CE11941 http://rustybear.com/pubkey.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbuilder create error
On Fri, Aug 05, 2005 at 11:04:55AM -0400, Kevin Coyner wrote: I've installed pbuilder on a sid box but keep getting hung up with the following error message whenever I try to execute: pbuilder create I've tried this on 3 different sid boxes and still get the same thing each time. Any thoughts would be appreicated. Thanks, Kevin Snippet of the error log follows: I: Configuring console-tools... I: Configuring libtextwrap1... I: Configuring console-common... W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. I: Base system installed successfully. - debootstrap finished - copying local configuration - Installing apt-lines Refreshing the base.tgz - upgrading packages - mounting /proc filesystem - mounting /dev/pts filesystem - installing dummy policy-rc.d /usr/bin/apt-get: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//9487 and its subdirectories THat is weird. I recently created a new pbuilder chroot and did not run into that problem. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto pgpBxxWrjulNv.pgp Description: PGP signature
