diff -Nru pbuilder-0.215ubuntu7/bash_completion.d/pbuilder pbuilder-0.215+nmu4ubuntu1~ppa1/bash_completion.d/pbuilder --- pbuilder-0.215ubuntu7/bash_completion.d/pbuilder 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/bash_completion.d/pbuilder 2015-06-22 16:04:04.000000000 +0000 @@ -7,7 +7,6 @@ # adapted to pbuilder, the license is GPLv2 or later. # Copyright 2007 Junichi Uekawa -have pbuilder && { _pbuilder() { local cur prev command i @@ -75,6 +74,5 @@ esac return 0 -} +} && complete -F _pbuilder pbuilder -} diff -Nru pbuilder-0.215ubuntu7/debian/changelog pbuilder-0.215+nmu4ubuntu1~ppa1/debian/changelog --- pbuilder-0.215ubuntu7/debian/changelog 2014-03-18 12:57:13.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/changelog 2015-07-12 09:34:29.000000000 +0000 @@ -1,3 +1,131 @@ +pbuilder (0.215+nmu4ubuntu1~ppa1) trusty; urgency=medium + + * Rebuild for Trusty. + + -- Fabio Fantoni Sun, 12 Jul 2015 11:33:12 +0200 + +pbuilder (0.215+nmu4ubuntu1) wily; urgency=low + + * Merge from Debian unstable (LP #1469735). Remaining changes: + - Added basic DEP-8 autopkgtest + - debian/control: Recommend aptitude since it's needed by + pbuilder-satisfydepends + - pbuilderrc, debian/pbuilder.config: Set default archive mirror + to "archive.ubuntu.com/ubuntu". + - debian/rules: install temporary locale so man page tests don't + cause FTBFS. + - Add build-dependency on locales, which was always used but + appears to have previously been preinstalled in the build chroots. + - Remove --keyring override from default pbuilderrc + - Set default distribution to "wily" + + -- Scott Howard Tue, 07 Jul 2015 14:53:39 -0400 + +pbuilder (0.215+nmu4) unstable; urgency=low + + * Non-maintainer upload. + + [ Mattia Rizzolo ] + * debian/source/format: 3.0 (native). + * Do real cleanup, don't hide temporary files under .gitignore, rather + teach makefiles' clean targets how to deal with them properly. + * set the USER env variable to BUILDUSERNAME, to fix FTBFS of some package + which check for not being run as root using that variable. + Thanks to Tim Landscheidt for the initial patch. + Closes: #677666 + + [ Johannes Schauer ] + * move filter_arch_deps to pbuilder-satisfydepends-funcs and add tests + * build profile parsing support (Closes: #740577) + + [ Andreas Henriksson ] + * Fix DEB_BUILD_PROFILES quoting. + Thanks to Michael Stapelberg for spotting this + * Support build-profiles in classic satisfydeps + * Force dpkg-architecture to use arguments over env + * Fix up License paragraph in debian/copyright + - fixes lintian warnings: + missing-license-paragraph-in-dep5-copyright + copyright-should-refer-to-common-license-file-for-gpl + * Install bash-completion under /usr/share/ instead of /etc + - fixes lintian warning package-install-into-obsolete-dir + * Use dpkg-maintscript-helper rm_conffile to clean up + old /etc/bash_completion.d/pbuilder + * Minor syntax updates to pbuilder bash-completion to make it + function properly under its new location. + - drop "have" check and add "&&" before complete. + + [ Axel Beckert ] + * Use "none" instead of "/dev/pts" as device for the /dev/pts mount + inside the chroot (Closes: #788580) + + [ Frédéric Brière ] + * Mark pbuilder as "Multi-Arch: foreign" (Closes: #752545) + + [ Mert Dirik ] + * Add Turkish debconf template translation (Closes: #757505) + + -- Mattia Rizzolo Mon, 22 Jun 2015 15:58:41 +0000 + +pbuilder (0.215+nmu3) unstable; urgency=low + + * Non-maintainer upload. + * Enable the loopback device even when USE_NETWORK=no (Closes: #753944) + Patch based on one provided by Niko Tyni; thanks! This also allows + getting rid of the “env” hack and disabling network for pre-squeeze + chroot by setting the new namespace up before chrooting. + + -- Thorsten Glaser Fri, 11 Jul 2014 19:56:53 +0200 + +pbuilder (0.215+nmu2) unstable; urgency=low + + * Fix missing space, thanks gregoa for spotting (Closes: #753690) + + -- Thorsten Glaser Fri, 04 Jul 2014 13:20:42 +0200 + +pbuilder (0.215+nmu1) unstable; urgency=low + + [ Ivo De Decker ] + * Only set CCACHE_DIR when running as build user. (closes: #666525) + + [ Thorsten Glaser ] + * Non-maintainer upload. + * Disable network access during build by default on Linux (Closes: #748967) + * Replace use of su as requested by Helmut Grohne (Closes: #747946) + + -- Thorsten Glaser Thu, 22 May 2014 20:37:51 +0200 + +pbuilder (0.215ubuntu12) wily; urgency=medium + + * pbuilderrc: Set default distribution to "wily" + + -- Hans Joachim Desserud Sat, 27 Jun 2015 13:18:57 +0200 + +pbuilder (0.215ubuntu11) vivid; urgency=medium + + * pbuilderrc: Set default distribution to "vivid" + + -- Hans Joachim Desserud Sat, 28 Feb 2015 16:40:27 +0100 + +pbuilder (0.215ubuntu10) utopic; urgency=medium + + * Remove --keyring override from default pbuilderrc (LP: #599695) + + -- Phillip Susi Wed, 11 Jun 2014 13:37:37 -0400 + +pbuilder (0.215ubuntu9) utopic; urgency=medium + + * pbuilderrc: Set default distribution to "utopic" (lp: #1316423) + + -- B. Clausius Sun, 25 May 2014 09:14:44 +0200 + +pbuilder (0.215ubuntu8) utopic; urgency=medium + + * debian/tests/control: Updated Depends to allow more capable procenv to be + built. + + -- James Hunt Wed, 04 Jun 2014 11:27:10 +0200 + pbuilder (0.215ubuntu7) trusty; urgency=medium * debian/tests/control: build-depend on libcap-dev since procenv 0.33 now diff -Nru pbuilder-0.215ubuntu7/debian/control pbuilder-0.215+nmu4ubuntu1~ppa1/debian/control --- pbuilder-0.215ubuntu7/debian/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/control 2015-07-10 14:24:41.000000000 +0000 @@ -23,6 +23,7 @@ Package: pbuilder Architecture: all +Multi-Arch: foreign Depends: coreutils (>= 4.5.8-1), debootstrap | cdebootstrap, dpkg-dev, @@ -30,6 +31,7 @@ wget, ${misc:Depends} Recommends: fakeroot, + net-tools | iproute2, sudo, devscripts, aptitude diff -Nru pbuilder-0.215ubuntu7/debian/copyright pbuilder-0.215+nmu4ubuntu1~ppa1/debian/copyright --- pbuilder-0.215ubuntu7/debian/copyright 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/copyright 2015-06-22 16:04:04.000000000 +0000 @@ -5,22 +5,21 @@ Files: * Copyright: Copyright 2001-2007 Junichi Uekawa Copyright (C) 2010 Loïc Minier - # pbuilder -- personal Debian package builder - # Copyright (C) 2001-2007 Junichi Uekawa - # - # This program is free software; you can redistribute it and/or modify - # it under the terms of the GNU General Public License as published by - # the Free Software Foundation; either version 2 of the License, or - # (at your option) any later version. - # - # This program is distributed in the hope that it will be useful, - # but WITHOUT ANY WARRANTY; without even the implied warranty of - # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - # GNU General Public License for more details. - # - # You should have received a copy of the GNU General Public License - # along with this program; if not, write to the Free Software - # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA License: GPL-2+ - - \ No newline at end of file + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + . + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + . + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + . + On Debian systems, the full text of the GNU General Public + License version 2 can be found in the file + `/usr/share/common-licenses/GPL-2'. diff -Nru pbuilder-0.215ubuntu7/debian/pbuilder.postinst pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.postinst --- pbuilder-0.215ubuntu7/debian/pbuilder.postinst 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.postinst 2015-06-22 16:04:04.000000000 +0000 @@ -1,5 +1,9 @@ #!/bin/sh set -e . /usr/share/debconf/confmodule + +dpkg-maintscript-helper rm_conffile \ + /etc/bash_completion.d/pbuilder 0.215+nmu4~ pbuilder -- "$@" + #DEBHELPER# exit 0 diff -Nru pbuilder-0.215ubuntu7/debian/pbuilder.postrm pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.postrm --- pbuilder-0.215ubuntu7/debian/pbuilder.postrm 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.postrm 2015-06-22 16:04:04.000000000 +0000 @@ -9,5 +9,8 @@ fi fi +dpkg-maintscript-helper rm_conffile \ + /etc/bash_completion.d/pbuilder 0.215+nmu4~ pbuilder -- "$@" + #DEBHELPER# exit 0 diff -Nru pbuilder-0.215ubuntu7/debian/pbuilder.preinst pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.preinst --- pbuilder-0.215ubuntu7/debian/pbuilder.preinst 1970-01-01 00:00:00.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/pbuilder.preinst 2015-06-22 16:04:04.000000000 +0000 @@ -0,0 +1,7 @@ +#!/bin/sh +set -e + +dpkg-maintscript-helper rm_conffile \ + /etc/bash_completion.d/pbuilder 0.215+nmu4~ pbuilder -- "$@" + +#DEBHELPER# diff -Nru pbuilder-0.215ubuntu7/debian/po/tr.po pbuilder-0.215+nmu4ubuntu1~ppa1/debian/po/tr.po --- pbuilder-0.215ubuntu7/debian/po/tr.po 1970-01-01 00:00:00.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/po/tr.po 2015-06-22 16:04:04.000000000 +0000 @@ -0,0 +1,88 @@ +# Turkish translation of pbuilder package +# Copyright (C) 2014 Mert Dirik +# This file is distributed under the same license as the pbuilder package. +# Mert Dirik , 2014. +# +msgid "" +msgstr "" +"Project-Id-Version: pbuilder 0.215+nmu3\n" +"Report-Msgid-Bugs-To: pbuilder@packages.debian.org\n" +"POT-Creation-Date: 2008-03-07 00:09+0900\n" +"PO-Revision-Date: 2014-08-01 17:11+0200\n" +"Last-Translator: Mert Dirik \n" +"Language-Team: Debian L10n Turkish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 1.5.4\n" +"Language: tr\n" + +#. Type: string +#. Description +#: ../pbuilder.templates:1001 +msgid "Default mirror site:" +msgstr "Öntanımlı yansı sitesi:" + +#. Type: string +#. Description +#: ../pbuilder.templates:1001 +msgid "Please enter the default mirror you want to be used by pbuilder." +msgstr "" +"Lütfen pbuilder tarafından kullanılmasını istediğiniz öntanımlı yansıyı " +"girin." + +#. Type: string +#. Description +#: ../pbuilder.templates:1001 +msgid "" +"If you leave this field blank, there will be one attempt to autodetect this " +"information. If this attempt fails, you will be prompted again to insert " +"some valid mirror information." +msgstr "" +"Burayı boş bıraktığınız takdirde bu bilgiyi otomatik olarak algılamak için " +"bir denemede bulunulacaktır. Bu deneme başarısız olursa geçerli bir yansı " +"girmeniz için size bir istemde daha bulunulacaktır." + +#. Type: string +#. Description +#: ../pbuilder.templates:1001 +msgid "Here is a valid mirror example: http://cdn.debian.net/debian" +msgstr "Geçerli bir yansı örneği şu şekildedir: http://http.debian.net/debian" + +#. Type: error +#. Description +#: ../pbuilder.templates:2001 +msgid "Default mirror not found" +msgstr "Öntanımlı yansı bulunamadı" + +#. Type: error +#. Description +#: ../pbuilder.templates:2001 +msgid "" +"Mirror information detection failed and the user provided no mirror " +"information." +msgstr "" +"Yansı bilgisi algılama başarısız oldu ve kullanıcı yansı bilgisi girmedi." + +#. Type: error +#. Description +#: ../pbuilder.templates:2001 +msgid "Please enter valid mirror information." +msgstr "Lütfen geçerli bir yansı bilgisi girin." + +#. Type: boolean +#. Description +#: ../pbuilder.templates:3001 +msgid "Overwrite current configuration?" +msgstr "Mevcut yapılandırmanın üzerine yazılsın mı?" + +#. Type: boolean +#. Description +#: ../pbuilder.templates:3001 +msgid "" +"Your system seems to have already pbuilder configuration. Proceeding might " +"discard or overwrite part or the entire pbuilder's configuration." +msgstr "" +"Sisteminizde halihazırda bir pbuilder yapılandırması bulunuyor. Devam " +"etmeniz halinde pbuilder mevcut yapılandırmasının bir kısmı ya da tamamı " +"silinebilir, atılabilir ya da değiştirilebilir." diff -Nru pbuilder-0.215ubuntu7/debian/source/format pbuilder-0.215+nmu4ubuntu1~ppa1/debian/source/format --- pbuilder-0.215ubuntu7/debian/source/format 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/source/format 2015-06-22 08:05:23.000000000 +0000 @@ -1 +1 @@ -1.0 +3.0 (native) diff -Nru pbuilder-0.215ubuntu7/debian/tests/control pbuilder-0.215+nmu4ubuntu1~ppa1/debian/tests/control --- pbuilder-0.215ubuntu7/debian/tests/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/debian/tests/control 2015-07-10 14:24:41.000000000 +0000 @@ -1,3 +1,5 @@ Tests: build_procenv -Depends: @, debian-keyring, distro-info, lsb-release, haveged, libnuma1 [linux-i386 linux-amd64 linux-ia64 linux-mips linux-mipsel linux-powerpc linux-ppc64 linux-ppc64el linux-x32], libcap-dev [linux-any] +Depends: @, debian-keyring, distro-info, lsb-release, haveged, + libnuma-dev [linux-i386 linux-amd64 linux-ia64 linux-mips linux-mipsel linux-powerpc linux-ppc64 linux-ppc64el linux-x32], + libcap-dev [linux-any], libselinux1-dev, libapparmor-dev Restrictions: needs-root diff -Nru pbuilder-0.215ubuntu7/Documentation/debconf7/Makefile pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/Makefile --- pbuilder-0.215ubuntu7/Documentation/debconf7/Makefile 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/Makefile 2015-06-22 08:05:23.000000000 +0000 @@ -13,4 +13,4 @@ latex $< clean: - -rm *~ *.log *.aux *.snm *.toc *.out *.nav *.dvi + rm -fv *~ *.log *.aux *.snm *.toc *.out *.nav *.dvi *.pdf *.pdf Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder.pdf and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder.pdf differ diff -Nru pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.aux pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.aux --- pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.aux 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.aux 1970-01-01 00:00:00.000000000 +0000 @@ -1,90 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\beamer@endinputifotherversion {3.07pt}} -\@writefile{nav}{\beamer@endinputifotherversion {3.07pt}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{1}{1/1}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {1}{1}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{2}{2/2}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {2}{2}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{3}{3/3}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {3}{3}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{4}{4/4}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {4}{4}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{5}{5/5}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {5}{5}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{6}{6/6}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {6}{6}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{7}{7/7}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {7}{7}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{8}{8/8}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {8}{8}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{9}{9/9}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {9}{9}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{10}{10/10}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {10}{10}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{11}{11/11}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {11}{11}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{12}{12/12}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {12}{12}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{13}{13/13}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {13}{13}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{14}{14/14}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {14}{14}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{15}{15/15}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {15}{15}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{16}{16/16}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {16}{16}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{17}{17/17}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {17}{17}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{18}{18/18}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {18}{18}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{19}{19/19}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {19}{19}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{20}{20/20}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {20}{20}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{21}{21/21}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {21}{21}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{22}{22/22}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {22}{22}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{23}{23/23}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {23}{23}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{24}{24/24}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {24}{24}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{25}{25/25}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {25}{25}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{26}{26/26}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {26}{26}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{27}{27/27}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {27}{27}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{28}{28/28}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {28}{28}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{29}{29/29}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {29}{29}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{30}{30/30}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {30}{30}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{31}{31/31}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {31}{31}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{32}{32/32}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {32}{32}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{33}{33/33}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {33}{33}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{34}{34/34}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {34}{34}}} -\@writefile{nav}{\headcommand {\slideentry {0}{0}{35}{35/35}{}{0}}} -\@writefile{nav}{\headcommand {\beamer@framepages {35}{35}}} -\@writefile{nav}{\headcommand {\beamer@partpages {1}{35}}} -\@writefile{nav}{\headcommand {\beamer@subsectionpages {1}{35}}} -\@writefile{nav}{\headcommand {\beamer@sectionpages {1}{35}}} -\@writefile{nav}{\headcommand {\beamer@documentpages {35}}} -\@writefile{nav}{\headcommand {\def \inserttotalframenumber {35}}} Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.dvi and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.dvi differ diff -Nru pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.log pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.log --- pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.log 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.log 1970-01-01 00:00:00.000000000 +0000 @@ -1,1116 +0,0 @@ -This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 2007.6.10) 23 JUN 2007 21:55 -entering extended mode - %&-line parsing enabled. -**pbuilder-presentation.tex -(./pbuilder-presentation.tex -LaTeX2e <2005/12/01> -Babel and hyphenation patterns for english, usenglishmax, dumylang, noh -yphenation, croatian, bulgarian, russian, ukrainian, czech, slovak, danish, dut -ch, finnish, finnish, french, basque, french, german, ngerman, german, ngerman, - greek, monogreek, ancientgreek, ibycus, hungarian, hungarian, italian, italian -, latin, latin, mongolian, mongolian, norsk, norsk, coptic, esperanto, estonian -, icelandic, indonesian, interlingua, romanian, serbian, slovenian, turkish, up -persorbian, welsh, portuguese, portuguese, spanish, catalan, galician, spanish, - catalan, galician, swedish, swedish, loaded. -(/usr/share/texmf/tex/latex/beamer/base/beamer.cls -(/usr/share/texmf/tex/latex/beamer/base/beamerbasercs.sty -Package: beamerbasercs 2007/01/28 (rcs-revision 1.4) -) -Document Class: beamer 2007/03/11 cvs version 3.07 A class for typesetting pres -entations (rcs-revision 1.70) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasemodes.sty -Package: beamerbasemodes 2007/01/28 (rcs-revision 1.22) -\beamer@tempbox=\box26 -\beamer@tempcount=\count79 -\c@beamerpauses=\count80 - -(/usr/share/texmf/tex/latex/beamer/base/beamerbasedecode.sty -Package: beamerbasedecode 2007/01/28 (rcs-revision 1.20) -\beamer@slideinframe=\count81 -\beamer@minimum=\count82 -) -\beamer@commentbox=\box27 -\beamer@modecount=\count83 -) -\headheight=\dimen102 -\headdp=\dimen103 -\footheight=\dimen104 -\sidebarheight=\dimen105 -\beamer@tempdim=\dimen106 -\beamer@finalheight=\dimen107 -\beamer@animht=\dimen108 -\beamer@animdp=\dimen109 -\beamer@animwd=\dimen110 -\beamer@leftmargin=\dimen111 -\beamer@rightmargin=\dimen112 -\beamer@leftsidebar=\dimen113 -\beamer@rightsidebar=\dimen114 -\beamer@boxsize=\dimen115 -\beamer@vboxoffset=\dimen116 -\beamer@descdefault=\dimen117 -\beamer@descriptionwidth=\dimen118 -\beamer@lastskip=\skip41 -\beamer@areabox=\box28 -\beamer@animcurrent=\box29 -\beamer@animshowbox=\box30 -\beamer@sectionbox=\box31 -\beamer@logobox=\box32 -\beamer@linebox=\box33 -\beamer@sectioncount=\count84 -\beamer@subsubsectionmax=\count85 -\beamer@subsectionmax=\count86 -\beamer@sectionmax=\count87 -\beamer@totalheads=\count88 -\beamer@headcounter=\count89 -\beamer@partstartpage=\count90 -\beamer@sectionstartpage=\count91 -\beamer@subsectionstartpage=\count92 -\beamer@animationtempa=\count93 -\beamer@animationtempb=\count94 -\beamer@xpos=\count95 -\beamer@ypos=\count96 -\beamer@showpartnumber=\count97 -\beamer@currentsubsection=\count98 -\beamer@coveringdepth=\count99 -\beamer@sectionadjust=\count100 -\beamer@tocsectionnumber=\count101 - -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseoptions.sty -Package: beamerbaseoptions 2007/01/28 (rcs-revision 1.8) - -(/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks14 -)) -(/usr/share/texmf/tex/latex/pgf/basiclayer/pgfcore.sty -(/usr/share/texmf-texlive/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf-texlive/tex/latex/graphics/graphics.sty -Package: graphics 2006/02/20 v1.0o Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf-texlive/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/etc/texmf/tex/latex/config/graphics.cfg -File: graphics.cfg 2007/01/18 v1.5 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: dvipdfm.def on input line 90. - -(/usr/share/texmf-texlive/tex/latex/dvipdfm/dvipdfm.def -File: dvipdfm.def 1999/9/6 vx.x Driver-dependant file -)) -\Gin@req@height=\dimen119 -\Gin@req@width=\dimen120 -) -(/usr/share/texmf/tex/latex/pgf/systemlayer/pgfsys.sty -(/usr/share/texmf/tex/latex/pgf/utilities/pgfrcs.sty -(/usr/share/texmf/tex/generic/pgf/utilities/pgfrcs.code.tex -Package: pgfrcs 2006/10/11 v1.09 (rcs-revision 1.12) -)) -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys.code.tex -Package: pgfsys 2006/10/11 v1.09 (rcs-revision 1.18) -\pgf@x=\dimen121 -\pgf@y=\dimen122 -\pgf@xa=\dimen123 -\pgf@ya=\dimen124 -\pgf@xb=\dimen125 -\pgf@yb=\dimen126 -\pgf@xc=\dimen127 -\pgf@yc=\dimen128 - -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgf.cfg -File: pgf.cfg 2006/10/11 (rcs-revision 1.2) -) -Package pgfsys Info: Driver file for pgf: pgfsys-dvipdfm.def on input line 889. - - -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys-dvipdfm.def -File: pgfsys-dvipdfm.def 2006/10/11 (rcs-revision 1.10) - -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys-common-pdf.def -File: pgfsys-common-pdf.def 2006/10/11 (rcs-revision 1.6) -))) -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsyssoftpath.code.tex -File: pgfsyssoftpath.code.tex 2006/10/11 (rcs-revision 1.3) -) -(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsysprotocol.code.tex -File: pgfsysprotocol.code.tex 2006/10/11 (rcs-revision 1.3) -)) -(/usr/share/texmf/tex/latex/xcolor/xcolor.sty -Package: xcolor 2005/12/21 v2.09 LaTeX color extensions (UK) - -(/etc/texmf/tex/latex/config/color.cfg -File: color.cfg 2007/01/18 v1.5 color configuration of teTeX/TeXLive -) -Package xcolor Info: Driver file: dvipdfm.def on input line 220. -Package xcolor Info: Model `cmy' substituted by `cmy0' on input line 1328. -Package xcolor Info: Model `hsb' substituted by `rgb' on input line 1332. -Package xcolor Info: Model `RGB' extended on input line 1344. -Package xcolor Info: Model `HTML' substituted by `rgb' on input line 1346. -Package xcolor Info: Model `Hsb' substituted by `hsb' on input line 1347. -Package xcolor Info: Model `tHsb' substituted by `hsb' on input line 1348. -Package xcolor Info: Model `HSB' substituted by `hsb' on input line 1349. -Package xcolor Info: Model `Gray' substituted by `gray' on input line 1350. -Package xcolor Info: Model `wave' substituted by `hsb' on input line 1351. -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcore.code.tex -Package: pgfcore 2006/10/11 v1.09 (rcs-revision 1.4) - -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoremath.code.tex -File: pgfcoremath.code.tex 2006/10/11 (rcs-revision 1.2) -\c@pgf@counta=\count102 -\c@pgf@countb=\count103 -\c@pgf@countc=\count104 -\c@pgf@countd=\count105 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex -File: pgfcorepoints.code.tex 2006/10/11 (rcs-revision 1.5) -\pgf@picminx=\dimen129 -\pgf@picmaxx=\dimen130 -\pgf@picminy=\dimen131 -\pgf@picmaxy=\dimen132 -\pgf@pathminx=\dimen133 -\pgf@pathmaxx=\dimen134 -\pgf@pathminy=\dimen135 -\pgf@pathmaxy=\dimen136 -\pgf@tempdim=\dimen137 -\c@pgf@tempcount=\count106 -\pgf@xx=\dimen138 -\pgf@xy=\dimen139 -\pgf@yx=\dimen140 -\pgf@yy=\dimen141 -\pgf@zx=\dimen142 -\pgf@zy=\dimen143 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathconstruct.code.tex -File: pgfcorepathconstruct.code.tex 2006/10/11 (rcs-revision 1.5) -\pgf@path@lastx=\dimen144 -\pgf@path@lasty=\dimen145 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathusage.code.tex -File: pgfcorepathusage.code.tex 2006/10/11 (rcs-revision 1.6) -\pgf@shorten@end@additional=\dimen146 -\pgf@shorten@start@additional=\dimen147 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorescopes.code.tex -File: pgfcorescopes.code.tex 2006/10/11 (rcs-revision 1.18) -\pgfpic=\box34 -\pgf@hbox=\box35 -\pgf@layerbox@main=\box36 -\pgf@picture@serial@count=\count107 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoregraphicstate.code.tex -File: pgfcoregraphicstate.code.tex 2006/10/11 (rcs-revision 1.5) -\pgflinewidth=\dimen148 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoretransformations.code.tex -File: pgfcoretransformations.code.tex 2006/10/11 (rcs-revision 1.4) -\pgf@pt@x=\dimen149 -\pgf@pt@y=\dimen150 -\pgf@pt@temp=\dimen151 -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorequick.code.tex -File: pgfcorequick.code.tex 2006/10/11 (rcs-revision 1.2) -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoreobjects.code.tex -File: pgfcoreobjects.code.tex 2006/10/11 (rcs-revision 1.2) -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathprocessing.code.tex -File: pgfcorepathprocessing.code.tex 2006/10/11 (rcs-revision 1.4) -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorearrows.code.tex -File: pgfcorearrows.code.tex 2006/10/11 (rcs-revision 1.5) -) -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoreshade.code.tex -File: pgfcoreshade.code.tex 2006/10/11 (rcs-revision 1.6) -\pgf@max=\dimen152 -\pgf@sys@shading@range@num=\count108 -))) -(/usr/share/texmf/tex/latex/pgf/basiclayer/pgfbaseimage.sty -(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfbaseimage.code.tex -Package: pgfbaseimage 2006/10/11 v1.09 (rcs-revision 1.4) -)) -(/usr/share/texmf/tex/latex/pgf/utilities/xxcolor.sty -Package: xxcolor 2003/10/24 ver 0.1 -\XC@nummixins=\count109 -\XC@countmixins=\count110 -) -(/usr/share/texmf-texlive/tex/latex/amsfonts/amssymb.sty -Package: amssymb 2002/01/22 v2.2d - -(/usr/share/texmf-texlive/tex/latex/amsfonts/amsfonts.sty -Package: amsfonts 2001/10/25 v2.2f -\@emptytoks=\toks15 -\symAMSa=\mathgroup4 -\symAMSb=\mathgroup5 -LaTeX Font Info: Overwriting math alphabet `\mathfrak' in version `bold' -(Font) U/euf/m/n --> U/euf/b/n on input line 132. -)) -(/usr/share/texmf-texlive/tex/latex/geometry/geometry.sty -Package: geometry 2002/07/08 v3.2 Page Geometry -\Gm@cnth=\count111 -\Gm@cntv=\count112 -\c@Gm@tempcnt=\count113 -\Gm@bindingoffset=\dimen153 -\Gm@wd@mp=\dimen154 -\Gm@odd@mp=\dimen155 -\Gm@even@mp=\dimen156 -\Gm@dimlist=\toks16 -) -(/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty -Package: hyperref 2007/02/07 v6.75r Hypertext links for LaTeX -\@linkdim=\dimen157 -\Hy@linkcounter=\count114 -\Hy@pagecounter=\count115 - -(/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2007/02/07 v6.75r Hyperref: PDFDocEncoding definition (HO) -) -(/etc/texmf/tex/latex/config/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive -) -(/usr/share/texmf-texlive/tex/latex/oberdiek/kvoptions.sty -Package: kvoptions 2006/08/22 v2.4 Connects package keyval with LaTeX options ( -HO) -) -Package hyperref Info: Option `bookmarks' set `true' on input line 2238. -Package hyperref Info: Option `bookmarksopen' set `true' on input line 2238. -Package hyperref Info: Option `implicit' set `false' on input line 2238. -Package hyperref Info: Hyper figures OFF on input line 2288. -Package hyperref Info: Link nesting OFF on input line 2293. -Package hyperref Info: Hyper index ON on input line 2296. -Package hyperref Info: Plain pages OFF on input line 2303. -Package hyperref Info: Backreferencing OFF on input line 2308. - -Implicit mode OFF; no redefinition of LaTeX internals -Package hyperref Info: Bookmarks ON on input line 2444. -(/usr/share/texmf-texlive/tex/latex/ltxmisc/url.sty -\Urlmuskip=\muskip10 -Package: url 2005/06/27 ver 3.2 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2599. -\Fld@menulength=\count116 -\Field@Width=\dimen158 -\Fld@charsize=\dimen159 -\Choice@toks=\toks17 -\Field@toks=\toks18 -Package hyperref Info: Hyper figures OFF on input line 3102. -Package hyperref Info: Link nesting OFF on input line 3107. -Package hyperref Info: Hyper index ON on input line 3110. -Package hyperref Info: backreferencing OFF on input line 3117. -Package hyperref Info: Link coloring OFF on input line 3122. - - -Package hyperref Warning: Option `pdfpagelabels' is turned off -(hyperref) because \thepage is undefined. - -Hyperref stopped early -) -*hyperref using driver hdvipdfm* -(/usr/share/texmf-texlive/tex/latex/hyperref/hdvipdfm.def -File: hdvipdfm.def 2007/02/07 v6.75r Hyperref driver for dvipdfm -\pdfm@box=\box37 -\Fld@listcount=\count117 -) -(/usr/share/texmf-texlive/tex/latex/extsizes/size17.clo -File: size17.clo 1999/11/11 NON-Standard LaTeX file (size option) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasecompatibility.sty -Package: beamerbasecompatibility 2007/01/28 (rcs-revision 1.63) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasefont.sty -Package: beamerbasefont 2007/01/28 (rcs-revision 1.16) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasemisc.sty -Package: beamerbasemisc 2007/01/28 (rcs-revision 1.24) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasetwoscreens.sty -Package: beamerbasetwoscreens 2007/01/28 (rcs-revision 1.7) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseoverlay.sty -Package: beamerbaseoverlay 2007/01/28 (rcs-revision 1.50) -\beamer@argscount=\count118 -\beamer@lastskipcover=\skip42 -\beamer@trivlistdepth=\count119 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasetitle.sty -Package: beamerbasetitle 2007/01/28 (rcs-revision 1.25) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasesection.sty -Package: beamerbasesection 2007/01/28 (rcs-revision 1.21) -\c@lecture=\count120 -\c@part=\count121 -\c@section=\count122 -\c@subsection=\count123 -\c@subsubsection=\count124 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframe.sty -Package: beamerbaseframe 2007/01/28 (rcs-revision 1.60) -\beamer@framebox=\box38 -\beamer@frametitlebox=\box39 -\beamer@zoombox=\box40 -\beamer@zoomcount=\count125 -\beamer@zoomframecount=\count126 -\beamer@frametextheight=\dimen160 -\c@subsectionslide=\count127 -\beamer@frametopskip=\skip43 -\beamer@framebottomskip=\skip44 -\beamer@frametopskipautobreak=\skip45 -\beamer@framebottomskipautobreak=\skip46 -\beamer@envbody=\toks19 -\c@framenumber=\count128 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseverbatim.sty -Package: beamerbaseverbatim 2007/01/28 (rcs-revision 1.8) -\beamer@verbatimfileout=\write3 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframesize.sty -Package: beamerbaseframesize 2007/01/28 (rcs-revision 1.18) -\beamer@splitbox=\box41 -\beamer@autobreakcount=\count129 -\beamer@autobreaklastheight=\dimen161 -\beamer@frametitletoks=\toks20 -\beamer@framesubtitletoks=\toks21 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframecomponents.sty -Package: beamerbaseframecomponents 2007/01/28 (rcs-revision 1.41) -\beamer@footins=\box42 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasecolor.sty -Package: beamerbasecolor 2007/01/28 (rcs-revision 1.42) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasenotes.sty -Package: beamerbasenotes 2007/01/28 (rcs-revision 1.23) -\beamer@frameboxcopy=\box43 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasetoc.sty -Package: beamerbasetoc 2007/01/28 (rcs-revision 1.21) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasetemplates.sty -Package: beamerbasetemplates 2007/01/28 (rcs-revision 1.51) -\beamer@sbttoks=\toks22 - -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseauxtemplates.sty -Package: beamerbaseauxtemplates 2007/01/28 (rcs-revision 1.28) - -(/usr/share/texmf/tex/latex/beamer/base/beamerbaseboxes.sty -Package: beamerbaseboxes 2007/03/11 (rcs-revision 1.32) -\bmb@box=\box44 -\bmb@colorbox=\box45 -\bmb@boxshadow=\box46 -\bmb@boxshadowball=\box47 -\bmb@boxshadowballlarge=\box48 -\bmb@temp=\dimen162 -\bmb@dima=\dimen163 -\bmb@dimb=\dimen164 -\bmb@prevheight=\dimen165 -) -\beamer@blockheadheight=\dimen166 -)) -(/usr/share/texmf/tex/latex/beamer/base/beamerbaselocalstructure.sty -Package: beamerbaselocalstructure 2007/01/28 (rcs-revision 1.53) - -(/usr/share/texmf-texlive/tex/latex/tools/enumerate.sty -Package: enumerate 1999/03/05 v3.00 enumerate extensions (DPC) -\@enLab=\toks23 -) -\c@figure=\count130 -\c@table=\count131 -\abovecaptionskip=\skip47 -\belowcaptionskip=\skip48 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasenavigation.sty -Package: beamerbasenavigation 2007/01/28 (rcs-revision 1.36) -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasetheorems.sty -Package: beamerbasetheorems 2007/01/28 (rcs-revision 1.10) - -(/usr/share/texmf-texlive/tex/latex/amsmath/amsmath.sty -Package: amsmath 2000/07/18 v2.13 AMS math features -\@mathmargin=\skip49 - -For additional information on amsmath, use the `?' option. -(/usr/share/texmf-texlive/tex/latex/amsmath/amstext.sty -Package: amstext 2000/06/29 v2.01 - -(/usr/share/texmf-texlive/tex/latex/amsmath/amsgen.sty -File: amsgen.sty 1999/11/30 v2.0 -\@emptytoks=\toks24 -\ex@=\dimen167 -)) -(/usr/share/texmf-texlive/tex/latex/amsmath/amsbsy.sty -Package: amsbsy 1999/11/29 v1.2d -\pmbraise@=\dimen168 -) -(/usr/share/texmf-texlive/tex/latex/amsmath/amsopn.sty -Package: amsopn 1999/12/14 v2.01 operator names -) -\inf@bad=\count132 -LaTeX Info: Redefining \frac on input line 211. -\uproot@=\count133 -\leftroot@=\count134 -LaTeX Info: Redefining \overline on input line 307. -\classnum@=\count135 -\DOTSCASE@=\count136 -LaTeX Info: Redefining \ldots on input line 379. -LaTeX Info: Redefining \dots on input line 382. -LaTeX Info: Redefining \cdots on input line 467. -\Mathstrutbox@=\box49 -\strutbox@=\box50 -\big@size=\dimen169 -LaTeX Font Info: Redeclaring font encoding OML on input line 567. -LaTeX Font Info: Redeclaring font encoding OMS on input line 568. -\macc@depth=\count137 -\c@MaxMatrixCols=\count138 -\dotsspace@=\muskip11 -\c@parentequation=\count139 -\dspbrk@lvl=\count140 -\tag@help=\toks25 -\row@=\count141 -\column@=\count142 -\maxfields@=\count143 -\andhelp@=\toks26 -\eqnshift@=\dimen170 -\alignsep@=\dimen171 -\tagshift@=\dimen172 -\tagwidth@=\dimen173 -\totwidth@=\dimen174 -\lineht@=\dimen175 -\@envbody=\toks27 -\multlinegap=\skip50 -\multlinetaggap=\skip51 -\mathdisplay@stack=\toks28 -LaTeX Info: Redefining \[ on input line 2666. -LaTeX Info: Redefining \] on input line 2667. -) -(/usr/share/texmf-texlive/tex/latex/amscls/amsthm.sty -Package: amsthm 2004/08/06 v2.20 -\thm@style=\toks29 -\thm@bodyfont=\toks30 -\thm@headfont=\toks31 -\thm@notefont=\toks32 -\thm@headpunct=\toks33 -\thm@preskip=\skip52 -\thm@postskip=\skip53 -\thm@headsep=\skip54 -\dth@everypar=\toks34 -) -\c@theorem=\count144 -) -(/usr/share/texmf/tex/latex/beamer/base/beamerbasethemes.sty -Package: beamerbasethemes 2007/01/28 (rcs-revision 1.10) -) -(/usr/share/texmf/tex/latex/beamer/themes/theme/beamerthemedefault.sty -Package: beamerthemedefault 2007/01/28 (rcs-revision 1.7) - -(/usr/share/texmf/tex/latex/beamer/themes/font/beamerfontthemedefault.sty -Package: beamerfontthemedefault 2007/01/28 (rcs-revision 1.13) -) -(/usr/share/texmf/tex/latex/beamer/themes/color/beamercolorthemedefault.sty -Package: beamercolorthemedefault 2007/01/28 (rcs-revision 1.28) -) -(/usr/share/texmf/tex/latex/beamer/themes/inner/beamerinnerthemedefault.sty -Package: beamerinnerthemedefault 2007/01/28 (rcs-revision 1.20) -\beamer@dima=\dimen176 -\beamer@dimb=\dimen177 -) -(/usr/share/texmf/tex/latex/beamer/themes/outer/beamerouterthemedefault.sty -Package: beamerouterthemedefault 2007/01/28 (rcs-revision 1.14) -))) -(./pbuilder-presentation.aux) -\openout1 = `pbuilder-presentation.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 42. -LaTeX Font Info: ... okay on input line 42. --------------------- Geometry parameters -paper: user defined -landscape: -- -twocolumn: -- -twoside: -- -asymmetric: -- -h-parts: 28.45274pt, 307.28987pt, 28.45274pt -v-parts: 0.0pt, 273.14662pt, 0.0pt -hmarginratio: -- -vmarginratio: -- -lines: -- -heightrounded: -- -bindingoffset: 0.0pt -truedimen: -- -includehead: true -includefoot: true -includemp: -- -driver: dvipdfm --------------------- Page layout dimensions and switches -\paperwidth 364.19536pt -\paperheight 273.14662pt -\textwidth 307.28987pt -\textheight 244.6939pt -\oddsidemargin -43.81725pt -\evensidemargin -43.81725pt -\topmargin -72.26999pt -\headheight 14.22636pt -\headsep 0.0pt -\footskip 14.22636pt -\marginparwidth 2.0pt -\marginparsep 12.0pt -\columnsep 10.0pt -\skip\footins 14.0pt plus 5.0pt minus 3.0pt -\hoffset 0.0pt -\voffset 0.0pt -\mag 1000 - -(1in=72.27pt, 1cm=28.45pt) ------------------------ -Package hyperref Info: Link coloring OFF on input line 42. - -(/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty -Package: nameref 2006/12/27 v2.28 Cross-referencing by name of section - -(/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty -Package: refcount 2006/02/20 v3.0 Data extraction from references (HO) -) -\c@section@level=\count145 -) -LaTeX Info: Redefining \ref on input line 42. -LaTeX Info: Redefining \pageref on input line 42. - -(./pbuilder-presentation.out) (./pbuilder-presentation.out) -\@outlinefile=\write4 -\openout4 = `pbuilder-presentation.out'. - -LaTeX Font Info: Overwriting symbol font `operators' in version `normal' -(Font) OT1/cmr/m/n --> OT1/cmss/m/n on input line 42. -LaTeX Font Info: Overwriting symbol font `operators' in version `bold' -(Font) OT1/cmr/bx/n --> OT1/cmss/bx/n on input line 42. -\symnumbers=\mathgroup6 -\sympureletters=\mathgroup7 -LaTeX Font Info: Overwriting math alphabet `\mathrm' in version `normal' -(Font) OT1/cmss/m/n --> OT1/cmr/m/n on input line 42. -LaTeX Font Info: Redeclaring math alphabet \mathbf on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathbf' in version `normal' -(Font) OT1/cmr/bx/n --> OT1/cmss/bx/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathbf' in version `bold' -(Font) OT1/cmr/bx/n --> OT1/cmss/bx/n on input line 42. -LaTeX Font Info: Redeclaring math alphabet \mathsf on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathsf' in version `normal' -(Font) OT1/cmss/m/n --> OT1/cmss/m/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathsf' in version `bold' -(Font) OT1/cmss/bx/n --> OT1/cmss/m/n on input line 42. -LaTeX Font Info: Redeclaring math alphabet \mathit on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathit' in version `normal' -(Font) OT1/cmr/m/it --> OT1/cmss/m/it on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathit' in version `bold' -(Font) OT1/cmr/bx/it --> OT1/cmss/m/it on input line 42. -LaTeX Font Info: Redeclaring math alphabet \mathtt on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathtt' in version `normal' -(Font) OT1/cmtt/m/n --> OT1/cmtt/m/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathtt' in version `bold' -(Font) OT1/cmtt/m/n --> OT1/cmtt/m/n on input line 42. -LaTeX Font Info: Overwriting symbol font `numbers' in version `bold' -(Font) OT1/cmss/m/n --> OT1/cmss/bx/n on input line 42. -LaTeX Font Info: Overwriting symbol font `pureletters' in version `bold' -(Font) OT1/cmss/m/it --> OT1/cmss/bx/it on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathrm' in version `bold' -(Font) OT1/cmss/bx/n --> OT1/cmr/bx/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathbf' in version `bold' -(Font) OT1/cmss/bx/n --> OT1/cmss/bx/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathsf' in version `bold' -(Font) OT1/cmss/m/n --> OT1/cmss/bx/n on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathit' in version `bold' -(Font) OT1/cmss/m/it --> OT1/cmss/bx/it on input line 42. -LaTeX Font Info: Overwriting math alphabet `\mathtt' in version `bold' -(Font) OT1/cmtt/m/n --> OT1/cmtt/bx/n on input line 42. - -(./pbuilder-presentation.nav) - -LaTeX Font Warning: Font shape `OT1/cmss/m/n' in size <4> not available -(Font) size <5> substituted on input line 43. - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[1 - -] -LaTeX Font Info: Try loading font information for U+msa on input line 55. - (/usr/share/texmf-texlive/tex/latex/amsfonts/umsa.fd -File: umsa.fd 2002/01/19 v2.2g AMS font definitions -) -LaTeX Font Info: Try loading font information for U+msb on input line 55. - -(/usr/share/texmf-texlive/tex/latex/amsfonts/umsb.fd -File: umsb.fd 2002/01/19 v2.2g AMS font definitions -) -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[2 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[3 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[4 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[5 - -] -File: chroot.eps Graphic file (type eps) - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[6 - -] -File: chroot-pbuilder.eps Graphic file (type eps) - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[7 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[8 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[9 - -] -File: pbuildercycle.eps Graphic file (type eps) - -Overfull \hbox (17.38577pt too wide) in paragraph at lines 104--104 -[][] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[10 - -] -Overfull \vbox (2.91585pt too high) detected at line 119 - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[11 - -] -Overfull \hbox (66.17406pt too wide) in paragraph at lines 129--129 -[]\OT1/cmtt/m/n/17.28 W: /home/dancer/.pbuilderrc does not exist[] - [] - - -Overfull \hbox (208.44603pt too wide) in paragraph at lines 129--129 -[] \OT1/cmtt/m/n/17.28 -> extracting base tarball [/var/cache/pbuilder/base.tgz -][] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[12 - -] -Overfull \hbox (66.17406pt too wide) in paragraph at lines 143--143 -[]\OT1/cmtt/m/n/17.28 Current time: Sat Jan 20 12:03:34 JST 2007[] - [] - - -Overfull \hbox (599.69395pt too wide) in paragraph at lines 143--143 -[] \OT1/cmtt/m/n/17.28 -> extracting base tarball [/home/dancer/DEBIAN/pbuilder -/pbuilder/testsuite/tmp.FeeAX18779/testimage][] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[13 - -] -Overfull \hbox (30.60606pt too wide) in paragraph at lines 158--158 -[]\OT1/cmtt/m/n/17.28 # pbuilder --login --bindmount ${HOME}[] - [] - - -Overfull \hbox (66.17406pt too wide) in paragraph at lines 158--158 -[]\OT1/cmtt/m/n/17.28 Current time: Sat Jan 20 12:03:34 JST 2007[] - [] - - -Overfull \hbox (599.69395pt too wide) in paragraph at lines 158--158 -[] \OT1/cmtt/m/n/17.28 -> extracting base tarball [/home/dancer/DEBIAN/pbuilder -/pbuilder/testsuite/tmp.FeeAX18779/testimage][] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[14 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[15 - -] -Overfull \hbox (66.17406pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 W: /home/dancer/.pbuilderrc does not exist[] - [] - - -Overfull \hbox (101.74205pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-buildpackage: source package is cowdancer[] - [] - - -Overfull \hbox (57.28206pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-buildpackage: source version is 0.26[] - [] - - -Overfull \hbox (324.042pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-buildpackage: source changed by Junichi Uekawa [] - [] - - -Overfull \hbox (155.09404pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-buildpackage: source version without epoch 0.26[] - [] - - -Overfull \hbox (306.25801pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 make[1]: Entering directory `/home/dancer/DEBIAN/cowdance -r/cowdancer'[] - [] - - -Overfull \hbox (172.87804pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 rm -f *~ *.o *.lo libcowdancer.so cow-shell cowbuilder[] - - [] - - -Overfull \hbox (297.36601pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 make[1]: Leaving directory `/home/dancer/DEBIAN/cowdancer -/cowdancer'[] - [] - - -Overfull \hbox (670.82994pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-source: warning: source directory `./cowdancer' is n -ot - `cowdancer-0.26'[] - [] - - -Overfull \hbox (190.66203pt too wide) in paragraph at lines 188--188 -[]\OT1/cmtt/m/n/17.28 dpkg-source: building cowdancer in cowdancer_0.26.tar.gz[ -] - [] - - -Overfull \vbox (288.91585pt too high) detected at line 189 - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[16 - -] -File: develcycle.eps Graphic file (type eps) - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[17 - -] -Overfull \hbox (16.83325pt too wide) in paragraph at lines 222--222 -[][][][][][][] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[18 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[19 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[20 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[21 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[22 - -] -Overfull \hbox (21.71407pt too wide) in paragraph at lines 273--273 -[]\OT1/cmtt/m/n/17.28 KERNEL_IMAGE=2.6.18-4-mips-di-vmlinux[] - [] - - -Overfull \hbox (12.82207pt too wide) in paragraph at lines 273--273 -[] \OT1/cmtt/m/n/17.28 /var/cache/pbuilder/base-mips.qemu[] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[23 - -] -File: qemubuilder-create.eps Graphic file (type eps) - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[24 - -] -File: qemubuilder-build.eps Graphic file (type eps) - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[25 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[26 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[27 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[28 - -] -Overfull \hbox (235.12202pt too wide) in paragraph at lines 303--303 -[]\OT1/cmtt/m/n/17.28 $ sudo qemubuilder --login --config pbuilder-qemu-mips.co -nfig[] - [] - - -Overfull \hbox (137.31004pt too wide) in paragraph at lines 303--303 -[]\OT1/cmtt/m/n/17.28 bash: /root/.pbuilderrc: No such file or directory[] - [] - - -Overfull \hbox (395.178pt too wide) in paragraph at lines 303--303 -[]\OT1/cmtt/m/n/17.28 /home/dancer/tmp/base-mips.qemu: clean, 11585/393984 file -s, 88319/786432 blocks[] - [] - - -Overfull \hbox (217.33803pt too wide) in paragraph at lines 303--303 -[]\OT1/cmtt/m/n/17.28 1048576 bytes (1.0 MB) copied, 0.0229856 seconds, 45.6 MB -/s[] - [] - - -Overfull \vbox (46.91585pt too high) detected at line 303 - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[29 - -] -Overfull \hbox (75.06606pt too wide) in paragraph at lines 314--314 -[]\OT1/cmtt/m/n/17.28 hostname: the specified hostname is invalid[] - [] - - -Overfull \hbox (110.63405pt too wide) in paragraph at lines 314--314 -[]\OT1/cmtt/m/n/17.28 bound to 10.0.2.15 -- renewal in 35272 seconds.[] - [] - -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[30 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[31 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[32 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[33 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[34 - -] -File: openlogo-light.eps Graphic file (type eps) - -Overfull \vbox (19.70001pt too high) has occurred while \output is active [] - - -[35 - -] -\tf@nav=\write5 -\openout5 = `pbuilder-presentation.nav'. - -\tf@toc=\write6 -\openout6 = `pbuilder-presentation.toc'. - -\tf@snm=\write7 -\openout7 = `pbuilder-presentation.snm'. - - (./pbuilder-presentation.aux) - -LaTeX Font Warning: Size substitutions with differences -(Font) up to 1.0pt have occurred. - - ) -Here is how much of TeX's memory you used: - 7780 strings out of 93997 - 138717 string characters out of 1162875 - 223462 words of memory out of 1500000 - 10827 multiletter control sequences out of 10000+50000 - 12674 words of font info for 48 fonts, out of 1200000 for 2000 - 703 hyphenation exceptions out of 8191 - 41i,14n,51p,329b,505s stack positions out of 5000i,500n,6000p,200000b,5000s - -Output written on pbuilder-presentation.dvi (35 pages, 299304 bytes). diff -Nru pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.nav pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.nav --- pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.nav 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.nav 1970-01-01 00:00:00.000000000 +0000 @@ -1,76 +0,0 @@ -\beamer@endinputifotherversion {3.07pt} -\headcommand {\slideentry {0}{0}{1}{1/1}{}{0}} -\headcommand {\beamer@framepages {1}{1}} -\headcommand {\slideentry {0}{0}{2}{2/2}{}{0}} -\headcommand {\beamer@framepages {2}{2}} -\headcommand {\slideentry {0}{0}{3}{3/3}{}{0}} -\headcommand {\beamer@framepages {3}{3}} -\headcommand {\slideentry {0}{0}{4}{4/4}{}{0}} -\headcommand {\beamer@framepages {4}{4}} -\headcommand {\slideentry {0}{0}{5}{5/5}{}{0}} -\headcommand {\beamer@framepages {5}{5}} -\headcommand {\slideentry {0}{0}{6}{6/6}{}{0}} -\headcommand {\beamer@framepages {6}{6}} -\headcommand {\slideentry {0}{0}{7}{7/7}{}{0}} -\headcommand {\beamer@framepages {7}{7}} -\headcommand {\slideentry {0}{0}{8}{8/8}{}{0}} -\headcommand {\beamer@framepages {8}{8}} -\headcommand {\slideentry {0}{0}{9}{9/9}{}{0}} -\headcommand {\beamer@framepages {9}{9}} -\headcommand {\slideentry {0}{0}{10}{10/10}{}{0}} -\headcommand {\beamer@framepages {10}{10}} -\headcommand {\slideentry {0}{0}{11}{11/11}{}{0}} -\headcommand {\beamer@framepages {11}{11}} -\headcommand {\slideentry {0}{0}{12}{12/12}{}{0}} -\headcommand {\beamer@framepages {12}{12}} -\headcommand {\slideentry {0}{0}{13}{13/13}{}{0}} -\headcommand {\beamer@framepages {13}{13}} -\headcommand {\slideentry {0}{0}{14}{14/14}{}{0}} -\headcommand {\beamer@framepages {14}{14}} -\headcommand {\slideentry {0}{0}{15}{15/15}{}{0}} -\headcommand {\beamer@framepages {15}{15}} -\headcommand {\slideentry {0}{0}{16}{16/16}{}{0}} -\headcommand {\beamer@framepages {16}{16}} -\headcommand {\slideentry {0}{0}{17}{17/17}{}{0}} -\headcommand {\beamer@framepages {17}{17}} -\headcommand {\slideentry {0}{0}{18}{18/18}{}{0}} -\headcommand {\beamer@framepages {18}{18}} -\headcommand {\slideentry {0}{0}{19}{19/19}{}{0}} -\headcommand {\beamer@framepages {19}{19}} -\headcommand {\slideentry {0}{0}{20}{20/20}{}{0}} -\headcommand {\beamer@framepages {20}{20}} -\headcommand {\slideentry {0}{0}{21}{21/21}{}{0}} -\headcommand {\beamer@framepages {21}{21}} -\headcommand {\slideentry {0}{0}{22}{22/22}{}{0}} -\headcommand {\beamer@framepages {22}{22}} -\headcommand {\slideentry {0}{0}{23}{23/23}{}{0}} -\headcommand {\beamer@framepages {23}{23}} -\headcommand {\slideentry {0}{0}{24}{24/24}{}{0}} -\headcommand {\beamer@framepages {24}{24}} -\headcommand {\slideentry {0}{0}{25}{25/25}{}{0}} -\headcommand {\beamer@framepages {25}{25}} -\headcommand {\slideentry {0}{0}{26}{26/26}{}{0}} -\headcommand {\beamer@framepages {26}{26}} -\headcommand {\slideentry {0}{0}{27}{27/27}{}{0}} -\headcommand {\beamer@framepages {27}{27}} -\headcommand {\slideentry {0}{0}{28}{28/28}{}{0}} -\headcommand {\beamer@framepages {28}{28}} -\headcommand {\slideentry {0}{0}{29}{29/29}{}{0}} -\headcommand {\beamer@framepages {29}{29}} -\headcommand {\slideentry {0}{0}{30}{30/30}{}{0}} -\headcommand {\beamer@framepages {30}{30}} -\headcommand {\slideentry {0}{0}{31}{31/31}{}{0}} -\headcommand {\beamer@framepages {31}{31}} -\headcommand {\slideentry {0}{0}{32}{32/32}{}{0}} -\headcommand {\beamer@framepages {32}{32}} -\headcommand {\slideentry {0}{0}{33}{33/33}{}{0}} -\headcommand {\beamer@framepages {33}{33}} -\headcommand {\slideentry {0}{0}{34}{34/34}{}{0}} -\headcommand {\beamer@framepages {34}{34}} -\headcommand {\slideentry {0}{0}{35}{35/35}{}{0}} -\headcommand {\beamer@framepages {35}{35}} -\headcommand {\beamer@partpages {1}{35}} -\headcommand {\beamer@subsectionpages {1}{35}} -\headcommand {\beamer@sectionpages {1}{35}} -\headcommand {\beamer@documentpages {35}} -\headcommand {\def \inserttotalframenumber {35}} Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.pdf and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.pdf differ diff -Nru pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.toc pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.toc --- pbuilder-0.215ubuntu7/Documentation/debconf7/pbuilder-presentation.toc 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/debconf7/pbuilder-presentation.toc 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -\beamer@endinputifotherversion {3.07pt} diff -Nru pbuilder-0.215ubuntu7/Documentation/Makefile pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/Makefile --- pbuilder-0.215ubuntu7/Documentation/Makefile 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/Makefile 2015-06-22 08:05:23.000000000 +0000 @@ -10,6 +10,7 @@ # the main XML file which is source to all documents MASTERXML=pbuilder-doc.xml HTMLDOCS= pbuilder-doc.html pbuilder-doc.ja.html pbuilder-doc.fr.html pbuilder-doc.de.html +ALIOTH_FILEHOSTING:=alioth.debian.org all: $(HTMLDOCS) @@ -36,10 +37,21 @@ mozilla-firefox -remote "openfile($(PWD)/$<)" release: pbuilder-doc.html pbuilder-doc.xml pbuilder-doc.css pbuilder-doc.xsl pbuilder-doc.pdf - scp $^ wagner.debian.org:/home/groups/pbuilder/htdocs/ + scp $^ ${ALIOTH_FILEHOSTING}:/home/groups/pbuilder/htdocs/ -clean: - rm -f pbuilder-doc.pdf pbuilder-doc.glo pbuilder-doc.idx pbuilder-doc.log pbuilder-doc.out \ - pbuilder-doc.aux pbuilder-doc.html.tmp +clean: + rm -fv \ + pbuilder-doc.pdf \ + pbuilder-doc.glo \ + pbuilder-doc.idx \ + pbuilder-doc.log \ + pbuilder-doc.out \ + pbuilder-doc.aux \ + pbuilder-doc.html \ + pbuilder-doc.de.html \ + pbuilder-doc.fr.html \ + pbuilder-doc.ja.html \ + pbuilder-doc.html.tmp + $(MAKE) -C debconf7 $@ .PHONY: preview release-netfort release clean diff -Nru pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.de.html pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.de.html --- pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.de.html 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.de.html 1970-01-01 00:00:00.000000000 +0000 @@ -1,1033 +0,0 @@ -Pbuilder-Benutzerhandbuch

Pbuilder-Benutzerhandbuch

Aufruf und Betrieb

Junichi Uekawa

Dokumentation in Entwicklung

Inhaltsverzeichnis

1. Einfhrung in Pbuilder
1. Ziele von Pbuilder
2. Pbuilder benutzen
1. Einen Basis-Chroot-Tarball erstellen
2. Das base.tgz aktualisieren
3. Ein Paket unter Benutzung von base.tgz bauen
4. Debian-Entwicklern das Tippen erleichtern, Pdebuild
5. Konfigurationsdateien
6. Pakete innerhalb der Chroot bauen ohne Root zu sein
7. Pbuilder zur Rckportierung benutzen
8. Massenhaft Pakete bauen
9. Automatische Rckportierungsskripte
10. Pbuilder fr das automatisierte Testen von Paketen benutzen
11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen
3. User Mode Linux mit Pbuilder benutzen
1. User Mode Linux konfigurieren
2. Rootstrap konfigurieren
3. Pbuilder-uml konfigurieren
4. Betrachtungen, um Pbuilder-user-mode-linux auszufhren
5. Paralleles Ausfhren von Pbuilder-user-mode-linux
6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle -Maschine zu starten
4. Hufig gestellte Fragen
1. Fehlschlagen des Erstellens mit Pbuilder
2. Verzeichnisse, bei denen kein Bind-Mount mglich ist
3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen
4. In Pbuilder anmelden, um die Umgebung zu ndern
5. BUILDRESULTUID fr Sudo-Sitzungen setzen
6. Anmerkungen zum Gerauch von $TMPDIR
7. Ein Krzel erstellen, um pbuilder mit einer speziellen -Distribution auszufhren.
8. Umgebungsvariablen benutzen, um pbuilder fr eine -spezielle Distribution auszufhren. -
9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden
10. Wie kann erreicht werden, dass Pbuilder apt-get update ausfhrt, bevor es -versucht die Build-Abhngigkeiten zu erfllen?
11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung
12. Eine Chroot-Erinnerung erstellen
13. /var/cache/apt/archives fr den Paket-Zwischenspeicher benutzen
14. Pbuilder auf Debian-Stable-Releases zurckportiert
15. Warnung, dass LOGNAME nicht definiert wurde
16. Build-Conflikt mit wesentlichem Paket nicht mglich
17. Vermeiden der Nachricht ln: Ungltiger Link ber Gertegrenzen hinweg
18. Fakechroot benutzen
19. Debconf innerhalb von Pbuilder-Sitzungen benutzen
20. nodev-Einhngeoptionen behindern Pbuilder-Aktivitt
21. Pbuilder ist langsam
22. Pdebuild zum Frdern eines Pakets benutzen
23. Warum liegt in ../ eine source.changes-Datei?
24. Die Modi amd64 und i386
25. Tmpfs fr buildplace benutzen
26. Svn-buildpackage zusammen mit Pbuilder benutzen
5. Fehlerbehebung und Entwicklung
1. Fehler berichten
2. Mailingliste
3. IRC-Kanal
4. Informationen fr Pbuilder-Entwickler
6. Andere Verwendungen von Pbuilder
1. Pbuilder fr kleine Experimente benutzen
2. Kleine Programme innerhalb der Chroot ausfhren
7. Experimental or wishlist features of pbuilder
1. LVM benutzen
2. Cowdancer benutzen
3. Pbuilder ohne tar.gz verwenden
4. PBuilder in einem Vserver verwenden
5. Gebrauch von Ccache
8. Referenzmaterial
1. Verzeichnisstruktur auerhalb der Chroot
2. Verzeichnisstruktur innerhalb der Chroot
9. Nebenschliche archologische Einzelheiten
1. Dokumentations-Chronik
2. Mglicherweise ungenaue Hintergrundgeschichte von Pbuilder
2.1. Zeit vor Pbuilder
2.2. Geburt von Pbuilder
2.3. Und sein zweites Lebensjahr
2.4. Das fnfte Jahr von Pbuilder

Tabellenverzeichnis

5.1. Verzeichnisstruktur der Test-Suite
8.1. Verzeichnisstruktur auerhalb der Chroot
8.2. Verzeichnisstruktur innerhalb der Chroot

Kapitel 1. Einfhrung in Pbuilder

Inhaltsverzeichnis

1. Ziele von Pbuilder

1. Ziele von Pbuilder

- pbuilder steht fr Personal Builder und ist ein -automatisches System zum Bau von Debian-Paketen fr persnliche -Entwickler-Arbeitsplatzumgebungen. Ziel von pbuilder ist -es, ein einfach einzurichtendes System zum automatischen Bau von -Debian-Paketen innerhalb einer Reinraumumgebung zu sein, so dass eine -Prfung, ob ein Paket in den meisten Debian-Installationen gebaut werden -kann, mglich ist. Die Reinraumumgebung wird durch den Gebrauch eines -Chroot-Images erreicht, so dass nur eine minimale Zahl von Paketen innerhalb -der Chroot installiert wird. -

- Die Distribution Debian besteht aus freier Software, die zusammen mit -Quellen weitergegeben wird. Der Quellkode innerhalb Debians Bereich main -muss innerhalb Debian-main gebaut werden, nur mit den explizit angegebenen -installierten Build-Abhngigkeiten. -

- Das vorrangige Ziel von pbuilder unterscheidet sich von -anderen automatischen Bausystemen in Debian darin, dass es nicht das Ziel -hat, so viele Pakete wie mglich zu bauen. Es versucht nicht abzuschtzen, -was ein Paket bentigt und probiert, wenn eine Auswahl zu treffen ist, in -den meisten Fllen die schlechtest mgliche Auswahl von allen. -

- Auf diese Art versucht pbuilder sicherzustellen, dass -Pakete, die mit pbuilder getestet wurden, auf den meisten -Debian-Installationen ordentlich gebaut werden, was hoffentlich in einer -guten umfassenden Erstellbarkeit von Debian aus den Quellen resultiert. -

- Das Ziel, Debian aus den Quellen erstellbar zu machen, ist einigermaen -vollendet und hat gute Fortschritte gemacht. In frheren Zeiten, als Debian -3.0 aktuell war, gab es viele Probleme beim Bau aus den Quellen. Bei -aktuelleren Versionen von Debian ist dies viel besser. -

Kapitel 2. Pbuilder benutzen

Inhaltsverzeichnis

1. Einen Basis-Chroot-Tarball erstellen
2. Das base.tgz aktualisieren
3. Ein Paket unter Benutzung von base.tgz bauen
4. Debian-Entwicklern das Tippen erleichtern, Pdebuild
5. Konfigurationsdateien
6. Pakete innerhalb der Chroot bauen ohne Root zu sein
7. Pbuilder zur Rckportierung benutzen
8. Massenhaft Pakete bauen
9. Automatische Rckportierungsskripte
10. Pbuilder fr das automatisierte Testen von Paketen benutzen
11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen

- Es gibt mehrere einfache Befehle fr den Betrieb. Normalerweise werden die -Befehle pbuilder create, pbuilder -update und pbuilder build benutzt. Sie werden -nun nacheinander vorgestellt. -

1. Einen Basis-Chroot-Tarball erstellen

- pbuilder create wird einen Basis-Chroot-Tarball -(base.tgz) erstellen. Alle anderen Befehle werden mit dem resultierenden -base.tgz arbeiten. Falls das zu erstellende Debian-Release nicht sid sein -wird (was Vorgabe ist), muss der Kodename der Distribution mit der -Befehlszeilenoption --distribution -angegeben werden. -

- debootstrap [1] wird -benutzt, um die reine minimale Debian-Installation zu erstellen. Dann werden -Build-essential-Pakete auf der minimalen Installation unter Benutzung von -apt-get innerhalb der Chroot installiert. -

- Fr weitere Dokumentationen der Befehlszeilenoptionen lesen Sie die -Handbuchseite pbuilder.8. Zur Benutzung wird manche Konfiguration von -/etc/pbuilderrc fr die Spiegel-Site [2] ntig sein und es knnte notwendig sein, den Proxy -zu konfigurieren, um Zugriff ber HTTP zu erlauben. Einzelheiten finden Sie -in der Handbuchseite von pbuilderrc.5. -

2. Das base.tgz aktualisieren

pbuilder update will update the base.tgz. It will -extract the chroot, invoke apt-get update and -apt-get dist-upgrade inside the chroot, and then recreate -the base.tgz (the base tar-ball). -

- Es ist mglich, die Distribution zu wechseln auf die base.tgz an diesem -Punkt verweist. Geben Sie --distribution -sid ---override-config an, um die Distribution auf Sid -zu ndern. [3] -

- Weitere Dokumentationen der Befehlszeilenoptionen finden Sie auf der -Handbuchseite pbuilder.8. -

3. Ein Paket unter Benutzung von base.tgz bauen

- Um ein Paket innerhalb der Chroot zu bauen, rufen Sie pbuilder -build wasauchimmer.dsc -auf. pbuilder wird das base.tgz in ein temporres -Verzeichnis extrahieren, mit Chroot in das Verzeichnis wechseln, die -Build-Abhngigkeiten erfllen und das Paket bauen. Das gebaute Paket wird in -das Verzeichnis verschoben, das mit der Befehlszeilenoption ---buildresult angegeben wurde. -

- Die Option --basetgz kann benutzt -werden, um anzugeben, welche base.tgz benutzt werden soll. -

- pbuilder wird ein frisches Chroot-Basis-Image aus -base.tgz extrahieren (base.tgz wird mit pbuilder create -erstellt und mit pbuilder update aktualisiert). Die -Chroot wird durch Auswertung von debian/control und Aufruf von -apt-get mit Build-Abhngigkeiten bestckt. -

- Weitere Dokumentationen der Befehlszeilenoptionen finden Sie auf der -Handbuchseite pbuilder.8. -

4. Debian-Entwicklern das Tippen erleichtern, Pdebuild

- pdebuild ist ein kleines Wrapper-Skript, das die -hufigsten aller Aufgaben erledigt. Ein Debian-Entwickler knnte versuchen, -debuild auszufhren und ein Paket innerhalb eines -Debian-Quellverzeichnisses zu bauen. pdebuild wird eine -hnliche Steuerung erlauben und ermglichen, dass Pakete innerhalb der -Chroot gebaut werden, um zu prfen, ob der aktuelle Quellbaum -geschickterweise innerhalb der Chroot gebaut wird. -

- pdebuild ruft zum Bau der Quellpakete -dpkg-source und dann fr das resultierende Quellpaket -pbuilder auf. Anders als bei Debuild knnen die -resultierenden Deb-Dateien jedoch im mit ---buildresult angegebenen Verzeichnis -gefunden werden. -

- Weitere Einzelheiten finden Sie auf der Handbuchseite pdebuild.1. -

- Es gibt einen etwas anderen Betriebsmodus, der in -pdebuild seit Version 0.97 verfgbar -ist. pdebuild fhrt debian/rules clean -normalerweise auerhalb der Chroot aus; es ist jedoch mglich, dieses -Verhalten mit --use-pdebuild-internal zu -ndern, damit es innerhalb der Chroot luft. Es wird versuchen, das -Arbeitsverzeichnis innerhalb der Chroot einzuhngen und -dpkg-buildpackage darin auszufhren. Es hat die folgenden -Merkmale und ist noch nicht der Standardbetriebsmodus. -

  • - erfllt die Build-Abhngigkeiten innerhalb der Chroot, bevor das Quellpaket -erstellt wird (was ein guter Punkt ist, den -Standard-pdebuild nicht beherrscht) -

  • Das Arbeitsverzeichnis wird von innerhalb der Chroot gendert.

  • Bauen mit pdebuild garantiert nicht, dass dies mit -pbuilder funktioniert.

  • Falls das Erstellen des Quellpakets fehlschlgt, ist die Sitzung vergeudet, -die die Chroot verwendet (Erstellen einer Chroot nimmt etwas Zeit in -Anspruch, was mit Cowdancer verbessert werden sollte).

  • funktioniert nicht auf die gleiche Weise wie gewohnt; zum Beispiel hat ---buildresult keine Auswirkungen.

  • Das Bauen innerhalb der Chroot ist mit dem aktuellen Benutzer auerhalb der -Chroot ausgefhrt worden. -

5. Konfigurationsdateien

- Es ist mglich, alle Einstellungen mit Befehlszeilenoptionen -anzugeben. Wegen des Eingabekomforts ist es jedoch mglich, eine -Konfigurationsdatei zu benutzen. -

- Wenn pbuilder aufgerufen wird, werden -/etc/pbuilderrc und -${HOME}/.pbuilderrc gelesen. Die mglichen Optionen -sind in der Handbuchseite pbuilderrc.5 dokumentiert. -

- Es ist ntzlich, die Option --configfile zu benutzen, um -eine voreingestellte Konfigurationsdatei zu laden, wenn zwischen -Konfigurationsdateien verschiedener Distributionen gewechselt wird. -

- Bitte beachten Sie, dass ${HOME}/.pbuilderrc -Systemeinstellungen aufhebt. Als Vorsichtsmanahme, wenn Sie ber irgendeine -Konfiguration verfgen, mssen Sie die Konfiguration so optimieren, dass sie -bei einem Upgrade mit neuen Versionen von Pbuilder funktioniert. -

6. Pakete innerhalb der Chroot bauen ohne Root zu sein

- pbuilder requires full root privilege when it is -satisfying the build-dependencies, but most packages do not need root -privilege to build, or even refused to build when they are built as root. -pbuilder can create a user which is only used inside -pbuilder and use that user id when building, and use the -fakeroot command when root privilege is required. -

- Die Konfigurationsoption BUILDUSERID sollte auf einen Wert fr eine -Benutzer-ID gesetzt werden, die noch nicht auf dem System existiert, so dass -es fr Pakete, die mit pbuilder erstellt werden, -schwieriger wird, die Umgebung auerhalb der Chroot zu beeinflussen. Wenn -auerdem die Konfigurationsoption BUILDUSERNAME gesetzt ist, wird -pbuilder den angegebenen Benutzernamen verwenden und zum -Bauen von Paketen Fakeroot verwenden, anstatt es als Root innerhalb der -Chroot auszufhren. -

- Sogar wenn die Fakeroot-Methode benutzt wird, wird -pbuilder mit Root-Rechten ausgefhrt, wenn dies -erforderlich ist. Wenn beispielsweise Pakete in die Chroot installiert -werden, wird pbuilder mit Root-Rechten ausgefhrt. -

- Um pbuilder aufrufen zu knnen ohne Root zu sein, mssen -Sie User Mode Linux benutzen, wie es unter Kapitel3, User Mode Linux mit Pbuilder benutzen -erklrt wird. -

7. Pbuilder zur Rckportierung benutzen

- pbuilder kann benutzt werden, um Software von der letzten -Debian-Distribution auf eine ltere stabile Version zurck zu portieren, -indem eine Chroot benutzt wird, die ein Image der lteren Distribution -enthlt, und die Pakete innerhalb der Chroot erstellt werden. Es sind -mehrere Punkte zu beachten und wegen der folgenden Grnde ist automatische -Rckportierung normalerweise nicht mglich und manuelle Interaktion -erforderlich: -

  • Das Paket von der Distribution Unstable knnte von Paketen oder -Paketversionen abhngig sein, die nur in Unstable verfgbar sind. Daher ist -es vielleicht nicht mglich, Build-Abhngigkeiten zu erfllen: auf Stable -(ohne zustzliche Rckportierungsarbeiten).

  • Die Distribution Stable knnte Fehler haben, die in Unstable behoben wurden -und an denen gearbeitet werden muss.

  • Das Paket in der Distribution Unstable knnte sogar Bauprobleme in Unstable -haben.

8. Massenhaft Pakete bauen

- pbuilder kann automatisiert werden, da seine Operationen -nicht interaktiv sind. Es ist mglich, pbuilder fr -mehrere Pakete ohne Benutzerinteraktion auszufhren. Es ist bekannt, dass -mehrere solche Skripte existieren. Junichi Uekawa fhrt solch ein Skript -seit 2001 aus und reichte Fehlerberichte gegen Pakete ein, die beim Test von -pbuilder scheiterten. Es gab mehrere Probleme beim -automatischen Erstellen: -

  • Build-Abhngigkeiten mussten interaktiv installiert werden, aber einige -Pakete waren so kaputt, dass sie nicht ohne einzugreifen installiert werden -konnten (wie PostgreSQL).

  • Wenn ein Bibliothekpaket, gcc/gcj/g++ oder sogar Bison kaputtging, wurde -eine groe Zahl gescheiterter Builds gemeldet. (gcj-3.0, das kein javac -hatte, Bison, das sich strenger verhielt, etc.) -

  • Einige Leute waren ziemlich verrgert ber Berichte fehlgeschlagener Builds.

- Die meisten anfnglichen Fehler wurden im -pbuilder-Kehraus um das Jahr 2002 gelst, aber von Zeit -zu Zeit treten einige bergangsprobleme auf, die eine groe Zahl von -Debian-Archiven beeinflussen.Regressionstests haben ihren Preis. -

- Ein Skript, das in der anfnglichen Ausfhrung von Junichi Uekawa benutzt -wurde, ist im nun verbreiteten pbuilder als -pbuildd.sh enthalten. Es liegt in -/usr/share/doc/pbuilder/examples/pbuildd/ und seine -Konfiguration liegt in -/etc/pbuilder/pbuildd-config.sh. Es sollte einfach -genug fr Leute einzurichten sein, die in pbuilder -eingearbeitet sind. Es lief ziemlich lange und es sollte mglich sein, es -auch auf Ihrem System einzurichten. Diese Version des Kodes ist nicht die am -meisten getestete, sollte aber als Startpunkt funktionieren. -

- Um Pbuildd einzurichten, gibt es einige wissenswerte Punkte. -

  • Um das Bauen zu verhindern, muss in der Paketliste eine -./avoidlist-Datei verfgbar sein.

  • Es wird versuchen alles zu erstellen, sogar Pakete, die nicht fr Ihre -Architektur gedacht sind.

  • Da Sie zufllige Build-Skripte ausfhren, ist es besser, die Fakeroot-Option -von pbuilder zu benutzen, um zu verhindern, dass das -Bauen mit Root-Rechten ausgefhrt wird.

  • Da nicht alle Builds garantiert in einer endlichen Zeit beendet sind, ist es -wahrscheinlich ntig, eine Zeitberschreitung festzulegen, ansonsten knnte -Pbuildd bei einem schlechten Build zum Stillstand kommen.

  • - Einige Pakete bentigen viel Plattenplatz. Circa zwei Gigabyte scheinen fr -den Augenblick ausreichend zu sein. Falls Sie etwas anderes entdecken, -informieren Sie bitte auf Englisch den Betreuer dieser Dokumentation. -

9. Automatische Rckportierungsskripte

- Es gibt einige Leute, die pbuilder benutzen, um eine -Teilmenge von Paketen automatisch auf die Distribution Stable -zurckzuportieren. -

- Informationen darber, wie Leute dies tun wren wnschenswert. Rckmeldungen -oder Informationen, wie dies getan wird oder irgendwelche Beispiele wrden -begrt. -

10. Pbuilder fr das automatisierte Testen von Paketen benutzen

- pbuilder kann benutzt werden, um Pakete automatisch zu -testen. Es hat die Eigenschaft, das Platzieren von Hooks zu erlauben. Diese -Hooks knnen innerhalb der Chroot versuchen, Pakete zu installieren, sie -auszufhren oder was auch immer sonst noch getan werden kann. Einige -bekannte Tests und Ideen: -

  • Automatic install-remove-install-purge-upgrade-remove-upgrade-purge -test-suite (distributed as an example, B91dpkg-i), or -just check that everything installs somewhat -(execute_installtest.sh).

  • Automatisch Lintian ausfhren (verteilt als Beispiel in -/usr/share/doc/pbuilder/examples/B90lintian).

  • Automatischer Debian-Test des Pakets? Das Paket debian-test wurde aus Debian -entfernt. Eine pbuilder-Implementierung kann als -debian/pbuilder-test-Verzeichnis gefunden werden, implementiert durch das -Skript B92test-pkg.

- To use B92test-pkg script, first, add it to your hook directory. -[4]. The test files are shell scripts -placed in debian/pbuilder-test/NN_name (where NN is a -number) following run-parts standard[5] -for file names. After a successful build, packages are first tested for -installation and removal, and then each test is ran inside the chroot. The -current directory is the top directory of the source-code. This means you -can expect to be able to use ./debian/ directory from inside your scripts. -

- Example scripts for use with pbuilder-test can be found in -/usr/share/doc/pbuilder/examples/pbuilder-test. -

11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen

- Die meisten Pakete werden mit gcc oder -g++ kompiliert und benutzen die -Standardkompilerversion. Diese war fr Debian GNU/Linux 3.0 (i386) Gcc -2.95. Debian 3.0 wurde jedoch mit anderen Kompilern unter Paketnamen wie -gcc-3.2 fr die Gcc-Kompilerversion 3.2 weitergegeben. Es -war daher mglich, zu versuchen, Pakete mit verschiedenen Kompilerversionen -zu kompilieren. pentium-builder stellt eine Infrastruktur -bereit, um einen anderen Kompiler als den vorgegebenenen Gcc zum Bau von -Paketen zu benutzen, indem es ein Wrapper-Skript bereitstellt, das Gcc heit -und den echten Gcc aufruft. Um pentium-builder in -pbuilder zu benutzen, ist es mglich das Folgende in der -Konfiguration einzurichten: 

-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2

-

- Es wird pbuilder anweisen, das Paket -pentium-builder und auerdem die GCC 3.2-Kompilerpakete -innerhalb der Chroot zu installieren und die zum Funktionieren von -pentium-builder bentigten Umgebungsvariablen zu setzen. -


[1] debootstrap oder cdebootstrap knnen ausgewhlt werden

[2] - Die Spiegel-Site sollte mglichst ein lokaler Spiegel oder ein -Zwischenspeicher-Server sein, damit die ffentlichen Spiegel nicht mit -vielen Zugriffen berladen werden. Die Benutzung von Werkzeugen wie -Apt-proxy ist empfehlenswert. -

[3] Nur das Durchfhren von Upgrades wird untersttzt. Debian untersttzt -generell (noch?) kein Downgrade.

[4] Es ist mglich, die Befehlszeilenoption --hookdir -/usr/share/doc/pbuilder/examples anzugeben, um ebenfalls alle -Beispiel-Hooks einzufgen.

[5] Siehe run-parts(8). Zum Beispiel kein . in Dateinamen! -

Kapitel 3. User Mode Linux mit Pbuilder benutzen

Inhaltsverzeichnis

1. User Mode Linux konfigurieren
2. Rootstrap konfigurieren
3. Pbuilder-uml konfigurieren
4. Betrachtungen, um Pbuilder-user-mode-linux auszufhren
5. Paralleles Ausfhren von Pbuilder-user-mode-linux
6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle -Maschine zu starten

- Es ist mglich, User Mode Linux zu benutzen, indem -pbuilder-user-mode-linux anstelle von -pbuilder aufgerufen -wird. pbuilder-user-mode-linux bentigt keine Root-Rechte -und benutzt die Plattenzugriffsmethode Copy-on-write (COW) von -User-mode-linux, die normalerweise wesentlich schneller -ist als das traditionelle pbuilder. -

- User-mode-linux ist eine etwas weniger bewhrte Plattform -als die Standard-Unix-Werkzeuge, auf denen pbuilder -beruht (chroot, tar und -gzip), aber ausgereift genug, um -pbuilder-user-mode-linux seit der Version 0.59 zu -untersttzen. Und seitdem hat pbuilder-user-mode-linux -eine schnelle Entwicklung durchlebt. -

- Die Konfiguration von pbuilder-user-mode-linux erfolgt in -folgenden Schritten: -

  • Konfiguration von User Mode Linux

  • Konfiguration von Rootstrap

  • Konfiguration von Pbuilder-uml

-

1. User Mode Linux konfigurieren

- Die Einrichtung von User Mode Linux ist nicht ganz einfach. Es wre -wahrscheinlich ntzlich, wenn Sie sich selbst ein wenig darber informieren, -bevor Sie versuchen rootstrap oder -pbuilder-user-mode-linux zu benutzen. Um Einzelheiten zu -erfahren, lesen Sie -/usr/share/doc/uml-utilities/README.Debian und die -Dokumentation von user-mode-linux. (Sie liegt in einem -gesonderten Paket, user-mode-linux-doc.) -

- user-mode-linux erfordert, dass der Benutzer der Gruppe -uml-net angehrt, um das Netzwerk zu konfigurieren, auer wenn Sie Slirp -benutzen. -

- Falls Sie Ihren eigenen Kernel kompilieren, mchten Sie mglicherweise -berprfen, ob Sie Untersttzung fr TUN/TAP aktiviert haben und den -SKAS-Patch betrachten. -

2. Rootstrap konfigurieren

- rootstrap ist ein Wrapper um Debootstrap. Er erstellt ein -Debian-Platten-Image zur Benutzung mit UML. Um Rootstrap zu konfigurieren, -gibt es mehrere Anforderungen. -

  • Das Rootstrap-Paket installieren

  • - Nur TUN/TAP: den Benutzer zur Gruppe uml-net hinzufgen, um -Netzwerkzugriff zu gewhren 

    adduser dancer uml-net

    -

  • Nur TUN/TAP: prfen, ob der Kernel die TUN/TAP-Schnittstelle untersttzt -oder, falls ntig, den Kernel neu komplilieren. -

  • /etc/rootstrap/rootstrap.conf einrichten. Falls der -aktuelle Rechner beispielsweise 192.168.1.2 ist, scheint es zu -funktionieren, die folgenden Eintrge auf etwas wie das Folgende zu -ndern. 

    -transport=tuntap
-interface=eth0
-gateway=192.168.1.1
-mirror=http://192.168.1.2:8081/debian
-host=192.168.1.198
-uml=192.168.1.199
-netmask=255.255.255.0

    Einige Experimente mit der -Konfiguration und das Ausfhren von rootstrap ~/test.uml, -um es tatschlich zu testen, wren praktisch. -

    - Die Benutzung vom Slirp erfordert weniger Konfiguration. Die -Standardkonfiguration bringt ein funktionierendes Beispiel mit. -

3. Pbuilder-uml konfigurieren

- Das Folgende muss geschehen: -

  • Installation des Pakets pbuilder-uml

  • - Einrichten der Konfigurationsdatei -/etc/pbuilder/pbuilder-uml.conf auf die folgende -Weise. Sie unterscheidet sich bei Slirp. 

    -MY_ETH0=tuntap,,,192.168.1.198
-UML_IP=192.168.1.199
-UML_NETMASK=255.255.255.0
-UML_NETWORK=192.168.1.0
-UML_BROADCAST=255.255.255.255
-UML_GATEWAY=192.168.1.1
-PBUILDER_UML_IMAGE="/home/dancer/uml-image"

    -Auerdem muss sie zur Rootstrap-Konfiguration passen. -

  • - Stellen Sie sicher, dass der Benutzer in BUILDPLACE schreiben darf. ndern -Sie BUILDPLACE in der Konfigurationsdatei auf eine Stelle, auf die der -Benutzer zugreifen kann. -

  • Fhren Sie pbuilder-user-mode-linux create --distribution -sid aus, um das Image zu erstellen.

  • Versuchen Sie pbuilder-user-mode-linux build auszufhren.

-

4. Betrachtungen, um Pbuilder-user-mode-linux auszufhren

- pbuilder-user-mode-linux emuliert -pbuilder grtenteils, es gibt aber einige Unterschiede. -

  • - pbuilder-user-mode-linux untersttzt noch nicht alle -Optionen von pbuilder ordentlich. Dies ist ein Problem -und wird angesprochen, whrend besondere Bereiche entdeckt werden. -

  • - /tmp wird innerhalb von pbuilder-user-mode-linux -unterschiedlich gehandhabt. In pbuilder-user-mode-linux -wird /tmp als Tmpfs innerhalb UML eingehngt, so dass -der Zugriff auf Dateien unter /tmp von auerhalb des -User Mode Linux nicht funktioniert. Es beeinflusst Optionen wie ---configfile und wenn versucht wird, -Pakete zu bauen, die unter /tmp liegen. -

5. Paralleles Ausfhren von Pbuilder-user-mode-linux

- Um pbuilder-user-mode-linux parallel auf einem System -auszufhren, sind ein paar Dinge zu bercksichtigen. -

  • Die Methoden zum Erstellen und Aktualisieren drfen nicht laufen, wenn ein -Build-Prozess luft oder eine COW-Datei entkrftet wird.

  • - Falls Sie Slirp nicht benutzen, mssen parallel laufende Prozesse von User -Mode Linux unterschiedliche IP-Adressen haben. Der reine Versuch, -pbuilder-user-mode-linux mehrmals auszufhren, wird dazu -fhren, dass der Netzwerkzugriff fehlschlgt. Aber etwas wie das Folgende -wird funktionieren: 

    -for IP in 102 103 104 105; do
-  xterm -e pbuilder-user-mode-linux build --uml-ip 192.168.0.$IP \
-    20030107/whizzytex_1.1.1-1.dsc &
-done

    Wenn Slirp benutzt -wird, besteht dieses Problem nicht. -

6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle -Maschine zu starten

- Es ist mglich, pbuilder-user-mode-linux fr andere -Zwecke als nur das Bauen von Debian-Paketen zu -verwenden. pbuilder-user-mode-linux -login wird einem Benutzer ermglichen, eine Shell -innerhalb des pbuilder-Basis-Images von User Mode Linux -zu verwenden und pbuilder-user-mode-linux -execute wird dem Benutzer ermglichen, ein Skript -innerhalb des Images auszufhren. -

- Sie knnen das Skript benutzen, um SSH zu installieren und einen neuen -Benutzer hinzuzufgen, so dass SSH-Zugriffe innerhalb von User Mode Linux -mglich sind. -

- Beachten Sie, dass es nicht mglich ist, ein Skript von -/tmp zu benutzen, da -pbuilder-user-mode-linux ein Tmpfs unter -/tmp einhngt. -

- Das folgende Beispielskript knnte ntzlich sein, um einen Sshd innerhalb -von User Mode Linux zu starten. - 

-#!/bin/bash
-
-apt-get install -y ssh xbase-clients xterm
-echo "Geben Sie das Root-Passwort ein"
-passwd
-cp /etc/ssh/sshd_config{,-}
-sed 's/X11Forwarding.*/X11Forwarding yes/' /etc/ssh/sshd_config- > /etc/ssh/sshd_config
-
-/etc/init.d/ssh restart
-ifconfig
-echo "Zum Beenden Eingabetaste drcken"
-read

Kapitel 4. Hufig gestellte Fragen

Inhaltsverzeichnis

1. Fehlschlagen des Erstellens mit Pbuilder
2. Verzeichnisse, bei denen kein Bind-Mount mglich ist
3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen
4. In Pbuilder anmelden, um die Umgebung zu ndern
5. BUILDRESULTUID fr Sudo-Sitzungen setzen
6. Anmerkungen zum Gerauch von $TMPDIR
7. Ein Krzel erstellen, um pbuilder mit einer speziellen -Distribution auszufhren.
8. Umgebungsvariablen benutzen, um pbuilder fr eine -spezielle Distribution auszufhren. -
9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden
10. Wie kann erreicht werden, dass Pbuilder apt-get update ausfhrt, bevor es -versucht die Build-Abhngigkeiten zu erfllen?
11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung
12. Eine Chroot-Erinnerung erstellen
13. /var/cache/apt/archives fr den Paket-Zwischenspeicher benutzen
14. Pbuilder auf Debian-Stable-Releases zurckportiert
15. Warnung, dass LOGNAME nicht definiert wurde
16. Build-Conflikt mit wesentlichem Paket nicht mglich
17. Vermeiden der Nachricht ln: Ungltiger Link ber Gertegrenzen hinweg
18. Fakechroot benutzen
19. Debconf innerhalb von Pbuilder-Sitzungen benutzen
20. nodev-Einhngeoptionen behindern Pbuilder-Aktivitt
21. Pbuilder ist langsam
22. Pdebuild zum Frdern eines Pakets benutzen
23. Warum liegt in ../ eine source.changes-Datei?
24. Die Modi amd64 und i386
25. Tmpfs fr buildplace benutzen
26. Svn-buildpackage zusammen mit Pbuilder benutzen

- Hier sind bekannte Probleme und hufig gestellte Fragen dokumentiert. Dieser -Teil war anfangs in der Datei README.Debian verfgbar, wurde aber hierher -verschoben. -

1. Fehlschlagen des Erstellens mit Pbuilder

- Es kommt hufig vor, dass pbuilder die letzte Chroot -nicht erstellen kann. Versuchen Sie ein Upgrade von -pbuilder und Debootstrap durchzufhren. Es ist derzeit -nicht mglich, Software zu erstellen, die die Vergangenheit -handhabt. Zukunftsvorhersage ist eine Funktion, die spter hinzugefgt -werden knnte, wenn wir uns mit der Vergangenheit arrangieren knnen. -

- Es gibt Leute, die gelegentlich Debootstrap auf stabile Versionen -zurckportieren; jagen Sie sie. -

- Wenn in der Debootstrap-Phase Fehler auftreten, muss das Debootstrap-Skript -repariert werden. pbuilder stellt keine Mglichkeit -bereit, Debootstrap zu umgehen. -

2. Verzeichnisse, bei denen kein Bind-Mount mglich ist

- Aufgrund der Weise, wie pbuilder arbeitet, gibt es viele -Verzeichnisse, bei denen ein Bind-Mount beim Ausfhren von -pbuilder nicht mglich ist. Die Verzeichnisse umfassen -/tmp, /var/cache/pbuilder und -Systemverzeichnisse wie /etc und -/usr. Es wird empfohlen, Verzeichnisse unter dem -Home-Verzeichnis des Benutzers fr Bind-Mounts zu verwenden. -

3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen

- It is possible to invoke a shell session after a build failure. Example -hook scripts are provided as C10shell and -C11screen scripts. C10shell script will start bash -inside chroot, and C11screen script will start GNU screen inside the chroot. -

4. In Pbuilder anmelden, um die Umgebung zu ndern

- Manchmal ist es notwendig, die Chroot-Umgebung zu -verndern. login wird den Inhalt der Chroot nach dem -Abmelden entfernen. Es ist mglich unter Benutzung von Hook-Skripten eine -Shell aufzurufen. pbuilder update fhrt E-Skripte aus -und ruft beispielsweise eine Shell auf, die als -C10shell bereitgestellt wird. - 

-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell

- Auerdem ist es mglich, die Optionen --save-after-exec -und/oder --save-after-login zu der pbuilder -login-Sitzung hinzuzufgen, um das Ziel zu erreichen. Es ist -ebenfalls mglich, die Option --uml-login-nocow zur Sitzung -von pbuilder-user-mode-linux login -hinzuzufgen. -

5. BUILDRESULTUID fr Sudo-Sitzungen setzen

- Es ist mglich, 

BUILDRESULTUID=$SUDO_UID

in Pbuilderrc -einzustellen, um BUILDRESULTUID angemessen zu setzen, wenn -sudo benutzt wird. -

6. Anmerkungen zum Gerauch von $TMPDIR

- Falls Sie $TMPDIR auf einen unblichen Wert setzen, der von -/tmp abweicht, werden Sie bemerken, dass einige Fehler, -wie das Scheitern von dpkg-source, innerhalb der Chroot -auftreten. -

Es gibt zwei Optionen – Sie knnen einen Hook installieren, um dieses -Verzeichnis zu erstellen oder 

export TMPDIR=/tmp

in -Pbuilderrc setzen. Suchen Sie sich eine aus. -

- Ein Beispielskript wird als examples/D10tmp mit -Pbuilder bereitgestellt. -

7. Ein Krzel erstellen, um pbuilder mit einer speziellen -Distribution auszufhren.

- Wenn mit mehreren Chroots gearbeitet wird, wre es nett, mit Skripten zu -arbeiten, um weniger tippen zu mssen. Ein Beispielskript -pbuilder-distribution.sh wird als Muster -bereitgestellt. Der Aufruf des Skripts mit -pbuilder-squeeze wird pbuilder mit -einer Squeeze-Chroot aufrufen. -

8. Umgebungsvariablen benutzen, um pbuilder fr eine -spezielle Distribution auszufhren. -

Dieser Abschnitt[6] beschreibt kurz eine -Mglichkeit, mehrere Pbuilder-Einrichtungen zu erstellen und zu benutzen, -indem eine Pbuilderrc-Konfiguration in Ihrem Home-Pfad -($HOME/.pbuilderrc) erstellt und die Variable DIST -beim Ausfhren von Pbuilder oder Pdebuild benutzt wird. -

Richten Sie zuerst $HOME/.pbuilderrc ein, dass es wie -folgt aussieht:

- 

-if [ -n "${DIST}" ]; then
-        BASETGZ="`dirname $BASETGZ`/$DIST-base.tgz"
-        DISTRIBUTION="$DIST"
-        BUILDRESULT="/var/cache/pbuilder/$DIST/result/"
-        APTCACHE="/var/cache/pbuilder/$DIST/aptcache/"
-fi
-

Wann auch immer Sie dann Pbuilder fr eine spezielle Distribution benutzen -mchten, weisen Sie DIST einen Wert zu, der einer der fr Debian -verfgbaren Distribution oder einer auf Debian basierenden Distribution, die -Sie zufllig ausfhren, entspricht (d.h. was auch immer unter -/usr/lib/debootstrap/scripts gefunden wird). -

Hier einige Beispiele, der Ausfhrung von Pbuilder oder Pdebuild: -

-DIST=gutsy sudo pbuilder create
-
-DIST=sid sudo pbuilder create --mirror http://http.us.debian.org/debian
-
-DIST=gutsy sudo pbuilder create \
-        --othermirror "deb http://archive.ubuntu.com/ubuntu gutsy universe \
-        multiverse"
-
-DIST=gutsy sudo pbuilder update
-
-DIST=sid sudo pbuilder update --override-config --mirror \
-http://http.us.debian.org/debian \
---othermirror "deb http://http.us.debian.org/debian sid contrib non-free"
-
-DIST=gutsy pdebuild
-

9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden

- Falls Sie einige auergewhnliche Anforderungen an Ihre Apt-Einrichtung -innerhalb pbuilder haben, ist es mglich, dies ber die -Option --othermirror -anzugeben. Versuchen Sie etwas wie dies: --othermirror "deb -http://local/mirror stable main|deb-src http://local/source/repository -./" -

- Um ein lokales Dateisystem anstelle von HTTP zu benutzen, ist es ntig, -Bind-Mount zu verwenden. --bindmounts -ist eine in solchen Fllen ntzliche Befehlszeilenoption. -

- Es knnte vorteilhaft sein, Ihre Build-Pakete von innerhalb der Chroot zu -benutzen. Es ist mglich, die Aufgabe mit der folgenden Konfiguration zu -automatisieren. Richten Sie zuerst Pbuilderrc ein, um ein Bind-Mount Ihres -Verzeichnisses fr Build-Ergebnisse auszufhren. -

- 

BINDMOUNTS="/var/cache/pbuilder/result"

-

- Fgen Sie dann den folgenden Hook hinzu -

- 

-# cat /var/cache/pbuilder/hooks/D70results
-#!/bin/sh
-cd /var/cache/pbuilder/result/
-/usr/bin/dpkg-scanpackages . /dev/null > /var/cache/pbuilder/result/Packages
-/usr/bin/apt-get update

-

- Auf diese Weise knnen Sie deb -file:/var/cache/pbuilder/result benutzen. -

- -So fgen Sie einen neuen Apt-Schlssel innerhalb der Chroot hinzu: - -

- 

-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-

10. Wie kann erreicht werden, dass Pbuilder apt-get update ausfhrt, bevor es -versucht die Build-Abhngigkeiten zu erfllen?

- Sie knnen dafr Hook-Skripte benutzen. D-Skripte werden ausgefhrt, bevor -Build-Abhngigkeiten erfllt werden. -

- -Dieser Kodeausschnitt stammt von Ondrej Sury. -

11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung

- Um charakteristische Bash-Eingabeaufforderungen innerhalb -pbuilder zu erleichtern, ist es mglich, innerhalb der -pbuilderrc Umgebungsvariablen wie PS1 zu setzen. -

- Mit aktuelleren Versionen der Bash als 2.05b-2-15 ist der Wert der Variablen -debian_chroot, falls er gesetzt ist, im Wert von PS1 (der -Bash-Eingabeaufforderung) innerhalb der Chroot enthalten. In vorhergehenden -Versionen der Bash,[7] funktionierte die -Einstellung PS1 in Pbuilderrc. -

Beispiel fr debian_chroot

-	export debian_chroot="pbuild$$"

Beispiel fr PS1

-	export PS1="pbuild chroot 32165 # "

12. Eine Chroot-Erinnerung erstellen

- Bash-Eingabeaufforderungen werden Ihnen helfen, sich daran zu erinnern, dass -Sie sich innerhalb der Chroot befinden. Es gibt andere Flle, in denen Sie -mglicherweise andere Hinweise bekommen mchten, dass Sie innerhalb der -Chroot sind. Probieren Sie das Hook-Skript -examples/F90chrootmemo aus. Es wird eine Datei -innerhalb der Chroot erstellen, die /CHROOT heit. -

13. /var/cache/apt/archives fr den Paket-Zwischenspeicher benutzen

- Um Systemen mit geringer Bandbreite zu helfen, ist es mglich -/var/cache/apt/archives als Paket-Zwischenspeicher zu -benutzen. Geben Sie es einfach anstelle von -/var/cache/pbuilder/aptcache an. -

- Es ist jedoch nicht mglich, dies derzeit mit der User-Mode-Linux-Version -von pbuilder zu tun, da -/var/cache/apt/archives normalerweise nur fr Root -schreibbar ist. -

- Es wird empfohlen, zugehrige Werkzeuge wie Apt-proxy zu benutzen, da das -Zwischenspeichern von Paketen dem System auerhalb des Einflussbereichs von -pbuilder nutzen wrde. -

14. Pbuilder auf Debian-Stable-Releases zurckportiert

- Die aktuelle Stable-Rckportierung von Pbuilder ist auf backports.org -verfgbar. -

15. Warnung, dass LOGNAME nicht definiert wurde

- Sie bekommen mglicherweise viele Fehlermeldungen zu Gesicht, wenn Sie -pbuilder ausfhren. -

- 

-	dpkg-genchanges: Warnung: kein UTMP-Eintrag verfgbar und LOGNAME nicht definiert; UID des Prozesses wird benutzt (1234)

-

- Es ist derzeit sicher, diese Warnmeldung zu ignorieren. Bitte geben Sie eine -Rckmeldung, wenn Sie ein Problem mit nicht gesetztem LOGNAME haben. LOGNAME -zu setzen bereitet einige Probleme, wenn chroot -aufgerufen wird. Dpkg bentigt beispielsweise Getpwnam, um innerhalb der -Chroot erfolgreich zu sein, was bedeutet, dass LOGNAME und die zugehrige -Benutzerinformation innerhalb der Chroot eingerichtet werden mssen. -

16. Build-Conflikt mit wesentlichem Paket nicht mglich

- pbuilder erlaubt derzeit kein Build-Conflicts mit -wesentlichen Paketen. Es sollte offensichtlich sein, dass wesentliche Pakete -nicht von einem funktionierenden Debian-System entfernt werden sollten und -ein Quellpaket nicht versuchen sollte, das Entfernen solcher Pakete zu -erzwingen, wenn Leute das Paket bauen. -

17. Vermeiden der Nachricht ln: Ungltiger Link ber Gertegrenzen hinweg

- Standardmig benutzt pbuilder harte Links, um den -pbuilder-Paketzwischenspeicher zu verwalten. Es ist nicht -mglich, harte Links ber unterschiedliche Gerte hinweg zu erstellen. Daher -wird dieser Fehler, abhngig von Ihrer Einrichtung, erscheinen. Falls dies -geschieht, setzen Sie in ihrer Pbuilderrc-Datei 

APTCACHEHARDLINK=no

. Beachten Sie, dass Pakete in APTCACHE in den -lokalen Chroot-Zwischenspeicher kopiert werden. Planen Sie daher genug -Speicher auf dem Gert BUILDPLACE ein. -

18. Fakechroot benutzen

- Es ist mglich, fakechroot zu benutzen, anstatt -pbuilder als Root auszufhren; mehrere Dinge machen dies -jedoch unpraktisch. fakechroot setzt geladene -Bibliotheken auer Kraft und versucht, vorgegebene Libc-Funktionen auer -Kraft zu setzen, wenn es die Funktionalitt von virtuellem -chroot bereitstellt. Einige Bibliotheken benutzen jedoch -zum Funktionieren Libc nicht oder setzen das auer Kraft setzen von -fakechroot auer Kraft. Ein Beispiel ist -ldd. Innerhalb fakechroot wird -ldd die Abhngigkeiten von Bibliotheken auerhalb der -Chroot prfen, die nicht das erwartete Verhalten aufweisen. -

- Um das Problem zu umgehen, hat Debootstrap eine Option --variant -fakechroot. Benutzen Sie diese, so dass Ldd und Ldconfig -berschrieben werden. -

- Stellen Sie sicher, dass Sie Ihrem Pfad LD_PRELOAD korrekt gesetzt haben, -wie es in der Handbuchseite von Fakechroot beschrieben ist. -

19. Debconf innerhalb von Pbuilder-Sitzungen benutzen

- Um Debconf innerhalb von pbuilder zu benutzen, sollte -DEBIAN_FRONTEND in pbuilderrc auf -„readline“ zu setzen funktionieren. Es auf -„dialog“ zu setzen sollte ebenfalls funktionieren. Stellen Sie -aber sicher, dass Whiptail oder Dialog innerhalb der Chroot installiert -sind. -

20. nodev-Einhngeoptionen behindern Pbuilder-Aktivitt

- Falls Sie Nachrichten wie diese beim Erstellen einer Chroot sehen, sind Sie -dabei, ein Dateisystem mit einer nodev-Option einzuhngen. - 

-	/var/lib/dpkg/info/base-files.postinst: /dev/null: Keine Berechtigung

- Sie werden auerdem Probleme haben, falls Sie ein Dateisystem mit der Option -noexec oder nosuid einhngen. Stellen Sie sicher, dass Sie diese -Schalter nicht gesetzt haben, wenn Sie das Dateisystem fr -/var/cache/pbuilder oder $BUILDPLACE einhngen. -

- Dies ist kein Problem, wenn Sie user-mode-linux benutzen. -

- Sehen Sie zum Beispiel 316135 -. -

21. Pbuilder ist langsam

- pbuilder ist fters langsam. Der langsamste Teil von -pbuilder ist bei jedem Aufruf von -pbuilder das Extrahieren des tar.gz. Dies kann verhindert -werden, indem pbuilder-user-mode-linux benutzt -wird. pbuilder-user-mode-linux benutzt ein -COW-Dateisystem und muss daher das Wurzeldateisystem nicht aufrumen und neu -erstellen. -

- pbuilder-user-mode-linux ist langsamer beim Ausfhren des -tatschlichen Build-Systems, aufgrund des blichen Mehraufwands von -user-mode-linux fr Systemaufrufe. Es ist freundlicher -zur Festplatte. -

- pbuilder mit Cowdancer ist ebenfalls eine Alternative, -die die Geschwindigkeit des Pbuilder-Starts verbessert. -

22. Pdebuild zum Frdern eines Pakets benutzen

- Um ein Paket zu signieren, dass es fr die Frderung gekennzeichnet ist, ist -es mglich, die Optionen --auto-debsign -und --debsign-k von -pdebuild zu benutzen. - 

-	pdebuild  --auto-debsign  --debsign-k XXXXXXXX

23. Warum liegt in ../ eine source.changes-Datei?

- Wenn pdebuild ausgefhrt wird, wird -pbuilder Dpkg-buildpackage ausfhren, um ein -Debian-Quellpaket zu erstellen, das an pbuilder -weitergereicht wird. Eine Datei mit Namen XXXX_YYY_source.changes ist das, -was von diesem Prozess brigbleibt. Das ist harmlos, solange Sie nicht -versuchen, sie in das Debian-Archiv hochzuladen. -

- Dieses Verhalten ist anders, wenn es mittels ---use-pdebuild-internal ausgefhrt wird. -

24. Die Modi amd64 und i386

- AMD64-Architekturen sind fhig, Programme im i386-Modus auszufhren. Es ist -mglich, pbuilder zu benutzen, um Pakete auszufhren, die -die Optionen linux32 und debootstrap ---arch benutzen. Im Besonderen wird eine -Befehlszeilenoption wie die Folgende funktionieren. -

- 

-pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
-  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian
-linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz

-

25. Tmpfs fr buildplace benutzen

- Um die Geschwindigkeit der Operation zu verbessern, ist es mglich, Tmpfs -fr den Build-Ort von Pbuilder zu verwenden. Hngen Sie das Tmpfs in -/var/cache/pbuilder/build ein und setzen Sie -

APTCACHEHARDLINK=no

. -

26. Svn-buildpackage zusammen mit Pbuilder benutzen

- Der Befehl Pdebuild kann mit der Befehlszeilenoption svn-buildpackage ---svn-builder benutzt werden. [8] - 

-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"

[6] Dieser Teil der Dokumentation wurde von Andres Mejia beigetragen.

- Dieses Beispiel wurde von einem Wiki bernommen (https://wiki.ubuntu.com/PbuilderHowto). -

[7] Versionen der Bash seit und vor Debian 3.0

[8] -Zack hat diesem Blog ein Beispiel gesandt.

Kapitel 5. Fehlerbehebung und Entwicklung

Inhaltsverzeichnis

1. Fehler berichten
2. Mailingliste
3. IRC-Kanal
4. Informationen fr Pbuilder-Entwickler

1. Fehler berichten

- Um Fehler zu berichten, wre es wichtig, ein Protokoll darber zu haben, was -schiefgelaufen ist. Meistens sollte das Hinzufgen einer Option ---debug und das erneute Ausfhren der -Sitzung den Zweck erfllen. Bitte senden Sie das Protokoll einer solchen -Sitzung zusammen mit Ihrer auf Englisch verfassten Problembeschreibung, um -den Prozess der Fehlersuche zu erleichtern. -

2. Mailingliste

- Es gibt auf Alioth eine Maillingliste fr Pbuilder -(pbuilder-maint@lists.alioth.debian.org). Sie knnen sie ber die -Alioth-Web-Schnittstelle abonnieren. -http://alioth.debian.org/mail/?group_id=30778. -

3. IRC-Kanal

- Zur Koordinierung und Kommunikation wird der IRC-Kanal #pbuilder auf -irc.oftc.net benutzt. Bitte legen Sie dort Ihre Absicht dar, wenn Sie mit -irgendwelchen nderungen beginnen oder irgendeine nderung bertragen. -

4. Informationen fr Pbuilder-Entwickler

- Dieser Abschnitt versucht, aktuelle Vorgehensweisen bei der Entwicklungs zu -dokumentieren und wie Dinge allgemein in der Entwicklung funktionieren. -

- pbuilder wird mitbetreut mit Ressourcen, die auf Alioth -bereitgestellt werden. Es gibt eine Alioth-Projektseite unter -http://alioth.debian.org/projects/pbuilder. Auerdem ist die -Homepage, die diesen Text zeigt, unter -http://alioth.debian.org/projects/pbuilder verfgbar. Das Git-Depot -ist ber HTTP, Git oder (falls Sie ein Alioth-Konto haben) SSH verfgbar. - 

-git-clone git://git.debian.org/git/pbuilder/pbuilder.git
-git-clone http://git.debian.org/git/pbuilder/pbuilder.git
-git-clone ssh://git.debian.org/git/pbuilder/pbuilder.git

- Die Git-Commit-Nachricht sollte zuerst eine Zeile haben, die beschreibt, was -das Commit tut. Dies sollte auf die Weise wie debian/changelog formatiert -sein, da es mittels Git-dch wortgetreu in das Changelog kopiert wird. Die -zweite Zeile ist leer und der Rest sollte die Hintergrund- und -Zusatzinformationen im Zusammenhang mit der Implementierung des Commits -beschreiben. -

- Test-Suites sind im Verzeichnis ./testsuite/ -verfgbar. Von nderungen wird erwartet, dass sie die Test-Suites nicht -unterbrechen. ./run-test.sh ist eine Basistest-Suite, -die eine Zusammenfassung in run-test.log und -run-test-cdebootstrap.log -ablegt. ./run-test-regression.sh ist eine -Regressionstest-Suite, die das Ergebnis in -run-test-regression.log ablegt. Derzeit wird -run-test.sh tglich automatisch ausgefhrt, um sicherzustellen, dass -Pbuilder funktioniert. -

Tabelle 5.1. Verzeichnisstruktur der Test-Suite

VerzeichnisBedeutung
./testsuite/Verzeichnis fr Test-Suite
./testsuite/run-test.shTglicher Regressionstest, um zu prfen, ob nderungen am Debian-Archiv -Pbuilder unterbrechen.
./testsuite/run-test.logEine Zusammenfassung der Test-Suite
./testsuite/normal/Verzeichnis fr Test-Suite-Ergebnisse fr die Ausfhrung von Pbuilder mit -Debootstrap
./testsuite/cdebootstrap/Verzeichnis fr Test-Suite-Ergebnisse fr die Ausfhrung von Pbuilder mit -Cdebootstrap
./testsuite/run-regression.shRegressionstest-Suite, wurde jedesmal ausgefhrt, wenn etwas an Pbuilder -gendert wurde, um sicherzustellen, dass es keinen Rckschritt gibt.
./testsuite/run-regression.logZusammenfassung des Testergebnisses
./testsuite/regression/BugID-*.shRegressionstests, Rckgabewert 0 bei Erfolg, 1 bei Fehlschlag
./testsuite/regression/BugID-*Dateien, die fr die Regressionstest-Suite verwandt werden
./testsuite/regression/log/BugID-*.sh.logAusgabe des Regressionstests, Ausgabe des Skripts, an das durch -run-regression.sh weitergeleitet wurde

- Wenn nderungen vorgenommen werden, sollten die nderungen im -Git-Commit-Protokoll dokumentiert werden. Git-dch wird aus dem -Commit-Protokoll debian/changelog generieren. Schreiben Sie eine -aussagekrftige erste Zeile in Ihr Commit-Protokoll und fgen Sie jede -verfgbare Information zum Schlieen von Fehlern hinzu. debian/changelog -sollte nicht direkt bearbeitet werden, auer wenn eine neue Version -verffentlicht wird. -

- Eine TODO-Datei ist in debian/TODO verfgbar. Sie wird -meist nicht gut gepflegt, wird aber hoffentlich aktueller sein, wenn Leute -beginnen, sie zu benutzen. Zum Bearbeiten der Datei wird der -Emacs-Todoo-Modus verwandt. -

- Wenn eine neue Version von pbuilder verffentlicht wird, -ist die Version mit der Git-Markierung X.XXX (Versionsnummer) -gekennzeichnet. Dies wurde mit dem Skript ./git-tag.sh, -das im Quellkode-Verzeichnisbaum verfgbar ist, erledigt. -

Kapitel 6. Andere Verwendungen von Pbuilder

Inhaltsverzeichnis

1. Pbuilder fr kleine Experimente benutzen
2. Kleine Programme innerhalb der Chroot ausfhren

1. Pbuilder fr kleine Experimente benutzen

- Es gibt Flle, in denen es ntig ist, ein wenig zu experimentieren und Sie -das Hauptsystem nicht beschdigen wollen, wie das Installieren -experimenteller Bibliothekspakete oder das Kompilieren mit experimentellen -Kompilern. Fr diese Flle steht der Befehl pbuilder -login zur Verfgung. -

- pbuilder login ist eine Funktion zur Fehlersuche fr -pbuilder selbst, aber es ermglicht Benutzern auerdem -eine temporre Chroot zu verwenden. -

- Beachten Sie, dass die Chroot nach dem Abmelden aus der Shell bereinigt wird -und das Einhngen von Dateisystemen innerhalb der Chroot als schdlich -angesehen wird. -

2. Kleine Programme innerhalb der Chroot ausfhren

- Um die Benutzung von pbuilder fr andere Zwecke zu -erleichtern, ist pbuilder execute -verfgbar. pbuilder execute wird ein im -Befehlszeilenargument angegebenes Skript nehmen und innerhalb der Chroot -aufrufen. -

- Das Skript kann ntzlich fr Abfolgen von Operationen, wie das Installieren -von SSH oder das Hinzufgen eines neuen Benutzers innerhalb der Chroot, -sein. -

Kapitel 7. Experimental or wishlist features of pbuilder

Inhaltsverzeichnis

1. LVM benutzen
2. Cowdancer benutzen
3. Pbuilder ohne tar.gz verwenden
4. PBuilder in einem Vserver verwenden
5. Gebrauch von Ccache

- Es gibt einige fortgeschrittene Funktionen, die ber die Grundfunktionen von -pbuilder fr einige besondere Zwecke hinausgehen. -

1. LVM benutzen

- LVM2 has a useful snapshot function that features Copy-on-write images. -That could be used for pbuilder just as it can be used -for the user-mode-linux pbuilder port. lvmpbuilder -script in the examples directory implements such port. The scripts and -documentation can be found under -/usr/share/doc/pbuilder/examples/lvmpbuilder/. -

2. Cowdancer benutzen

- cowdancer erlaubt Copy-on-write-Semantiken auf dem -Dateisystem unter Benutzung von harten Links und -Hard-link-breaking-on-write-Tricks. pbuilder scheint bei -der Benutzung von cowdancer viel schneller zu sein und es -ist ein idealer Punkt fr Verbesserungen. cowbuilder, ein -Wrapper fr pbuilder, um cowdancer zu -benutzen, ist im Paket cowdancer seit Version 0.14 -verfgbar. -

- Beispielshafte Befehlszeilen fr Cowbuilder sehen aus wie folgt. -

- 

-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc

-

- Es ist auerdem mglich, Cowdancer mit dem Befehl pdebuild zu -benutzen. Geben Sie es mit der Befehlszeilenoptionen ---pbuilder an oder setzen Sie es in der -Konfigurationsoption PDEBUILD_PBUILDER. -

- 

-$ pdebuild --pbuilder cowbuilder

-

3. Pbuilder ohne tar.gz verwenden

- Die Option --no-targz von -pbuilder wird den Gebrauch von -pbuilder auf eine andere als die bliche Weise -ermglichen. Sie wird versuchen eine existierende Chroot zu benutzen und sie -nach der Arbeit damit nicht zu bereinigen. Es ist ein Betriebsmodus, der -eher sbuild gleicht. -

- Es sollte mglich sein, Basis-Chroot-Images fr dchroot -mit den folgenden Befehlen zu erstellen: 

-# pbuilder create --distribution lenny --no-targz --basetgz /chroot/lenny
-# pbuilder create --distribution squeeze --no-targz --basetgz /chroot/squeeze
-# pbuilder create --distribution sid --no-targz --basetgz /chroot/sid

-

4. PBuilder in einem Vserver verwenden

- Es ist mglich, pbuilder in einer Vserver-Umgebung zu -verwenden. Dies erfordert entweder Vserver-patches in Version 2.1.1-rc14 -oder hher oder eine Linux-Kernel-Version 2.6.16 oder hher. -

- Um pbuilder in einem Vserver zu verwenden, mssen Sie in -den ccapabilities dieses Servers -secure_mount CAPS setzen. -

5. Gebrauch von Ccache

- It is possible to use C compiler cache ccache to speed up -repeated builds of the same package (or packages that compile the same files -multiple times for some reason). Using ccache can speed -up repeated building of large packages dramatically, at the cost of some -disk space and bookkeeping. -

- To enable usage of ccache with -pbuilder, you should set CCACHEDIR in your pbuilderrc -file. -

- Current implementation of ccache support has several bugs, that CCACHEDIR -must be owned by the pbuilder build user, and parallel runs of pbuilder is -not supported. Therefore it is not enabled by default. -

Kapitel 8. Referenzmaterial

Inhaltsverzeichnis

1. Verzeichnisstruktur auerhalb der Chroot
2. Verzeichnisstruktur innerhalb der Chroot

1. Verzeichnisstruktur auerhalb der Chroot

Tabelle 8.1. Verzeichnisstruktur auerhalb der Chroot

VerzeichnisBedeutung
/etc/pbuilderrcKonfigurationsdatei
/usr/share/pbuilder/pbuilderrcStandardkonfiguration
/var/cache/pbuilder/base.tgzStandardspeicherort, den Pbuilder fr base.tgz benutzt. Dieser Tarball -enthlt eine Basis-Debian-Installation ausschlielich mit -Build-essential-Paketen. -
/var/cache/pbuilder/build/PID/Standardspeicherort, den Pbuilder fr Chroot benutzt
/var/cache/pbuilder/aptcacheStandardspeicherort, den pbuilder als -APT-Zwischenspeicher benutzen wird, um Deb-Pakete zu speichern, die -pbuilder whrend des Bauens bentigt
/var/cache/pbuilder/ccacheStandardspeicherort, den pbuilder als Zwischenspeicher -benutzen wird
/var/cache/pbuilder/resultStandardspeicherort, in den pbuilder die Deb-Dateien und -andere Dateien ablegt, die nach dem Build erzeugt werden
/var/cache/pbuilder/pbuilder-umlresultStandardspeicherort, in den pbuilder-user-mode-linux die -Deb-Dateien und andere Dateien ablegt, die nach dem Build erzeugt werden
/var/cache/pbuilder/pbuilder-mntStandardspeicherort, den pbuilder-user-mode-linux -benutzt, um das COW-Dateisystem fr die Chroot einzuhngen
/tmppbuilder-user-mode-linux wird Tmpfs fr die Arbeit -einhngen.
${HOME}/tmp/PID.cowpbuilder-user-mode-linux benutzt dieses Verzeichnis als -Speicherort des COW-Dateisystem.
${HOME}/uml-imagepbuilder-user-mode-linux benutzt dieses Verzeichnis fr -das vollstndige User-Mode-Linux-Image.

2. Verzeichnisstruktur innerhalb der Chroot

Tabelle 8.2. Verzeichnisstruktur innerhalb der Chroot

VerzeichnisBedeutung
/etc/mtab - symbolischer Link zu /proc/mounts -
/tmp/builddStandardort, der vom pbuilder benutzt wird, um die zu -verarbeitenden Debian-Pakete -abzulegen. /tmp/buildd/packagename-version/ wird das -Wurzelverzeichnis des Pakets sein, das verarbeitet wird. Die -Umgebungsvariable HOME wird von Pbuilder-buildpackage auf diesen Wert -gesetzt. --inputfile wird die Dateien hier ablegen. -
/runscriptDas Skript, das als Argument zur Ausfhrung an pbuilder -bergeben wird, wird weitergereicht. -
/tmp/hooks - Der Speicherort von Hooks -
/var/cache/apt/archives - pbuilder kopiert den Inhalt dieses Verzeichnisses zu und -vom Aptcache-Verzeichnis auerhalb der Chroot. -
/var/cache/pbuilder/ccache - pbuilder hngt dieses Verzeichnis per Bind-Mount ein, -damit es durch Ccache benutzt wird. -
/tmp/XXXXpbuilder-user-mode-linux benutzt ein Skript in -/tmp fr ein Bootstrap in User Mode Linux.

Kapitel 9. Nebenschliche archologische Einzelheiten

Inhaltsverzeichnis

1. Dokumentations-Chronik
2. Mglicherweise ungenaue Hintergrundgeschichte von Pbuilder
2.1. Zeit vor Pbuilder
2.2. Geburt von Pbuilder
2.3. Und sein zweites Lebensjahr
2.4. Das fnfte Jahr von Pbuilder

1. Dokumentations-Chronik

- Die Arbeit an diesem Dokument wurde am 28. Dezember 2002 durch Junichi -Uekawa begonnen, der versuchte zu dokumentieren, was ber -pbuilder bekannt ist. -

- Diese Dokumentation ist im Quell-Tarball und im Git-Depot (Web-basierter -Zugriff ist mglich) von pbuilder verfgbar. Eine Kopie -dieser Dokumentation knnen Sie auf der Alioth-Projektseite -fr Pbuilder finden. Dort gibt es auch -eine PDF-Version . Die Homepage fr pbuilder wird - -http://pbuilder.alioth.debian.org/ vom Alioth-Projekt gehostet. -

- Die Dokumentation wurde unter Verwendung von DocBook-XML mit dem -Emacs-PSGML-Modus und unter Verwendung von Wysidocbookxml zur -Echtzeitvorschau geschrieben. -

2. Mglicherweise ungenaue Hintergrundgeschichte von Pbuilder

- Das Folgende ist ein mglichst genauer Bericht, wie es zu -pbuilder kam und andere Versuche, ein Ergebnis wie -pbuilder zu erzielen. Dieser Teil des Dokuments war -ursprnglich in der Datei AUTHORS, um dem Anerkennung zu zollen, was vor -pbuilder existierte. -

2.1. Zeit vor Pbuilder

- Es gab einst Dbuild, das war ein Shell-Skript, um Debian-Pakete aus der -Quelle zu bauen. Lars Wirzenius schrieb dieses Skript und es war gut, kurz -und (wahrscheinlich) einfach. Es gab (vermutlich) nichts wie -Build-Abhngigkeiten und es war simpel. Es konnte verbessert werden, es -konnten nur Referenzen und keine tatschliche Quelle gefunden werden. -

- Debbuild wurde wahrscheinlich von James Troup geschrieben. Genau bekannt ist -dies nicht, da der tatschlich Kode nicht vorliegt. Es konnten nur einige -Referenzen im Netz und in den Maillinglist-Protokollen gefunden werden. -

- Sbuild ist ein Perl-Skript, um Debian-Pakete aus der Quelle zu bauen. Es -wertet Build-Abhngigkeiten aus, fhrt verschiedene andere Prfungen durch -und hat viele Hacks, um Dinge tatschlich zu bauen, einschlielich einer -Tabelle, welches Paket benutzt wird, wenn virtuelle Pakete angegeben wurden -(tut es dies immer noch?). Es untersttzt den Gebrauch einer lokalen -Datenbank fr Pakete, die keine Build-Abhngigkeiten haben. Es wurde von -Ronan Hodek geschrieben und es wurde wahrscheinlich von vielen Leuten -repariert und erweitert. Es ist Teil von Wanna-Build und wird intensiv im -Debian-Build-System benutzt. Es wird vermutlich berwiegend von Ryan Murray -betreut. -

2.2. Geburt von Pbuilder

- Wanna-Build (Sbuild) war (in der Zeit um das Jahr 2001) ziemlich schwierig -einzurichten und es war ein nie Debian-Paket. Dbuild war etwas, was -Build-Abhngigkeiten vorwegnahm. -

- Pakete aus den Quellen unter Benutzung von Build-Abhngigkeitsinformationen -innerhalb einer Chroot zu bauen klang trivial und -pbuilder war geboren. Es war ursprnglich ein -Shell-Skript mit nur wenigen Zeilen, das Debootstrap, Chroot und -Dpkg-buildpackage im gleichen Durchlauf aufrief, aber bald wurde -entschieden, dass das zu langsam sei. -

- Ja, und es dauerte fast ein Jahr, um einige Dinge in Ordnung zu bringen und -mitten in diesem Prozess wurde Debian 3.0 verffentlicht. Juhu. Debian 3.0 -konnte nicht vollstndig mit pbuilder gebaut werden, aber -die Anzahl der Pakete, die nicht gebaut werden knnen, nimmt stetig ab -(hoffentlich). -

2.3. Und sein zweites Lebensjahr

- Jemand wollte, dass pbuilder nicht als Root ausgefhrt -wird und als User Mode Linux im Laufe der Zeit ntzlicher wurde, wurde -begonnen, mit pbuilder-user-mode-linux zu -experimentieren. pbuilder-user-mode-linux blieb nicht so -funktional wie gewnscht und Bootstrap der -user-mode-linux-Umgebung erwies sich als ziemlich hart -aufgrund der Qualitt des Kodes von User Mode Linux oder der Paketierung zu -dieser Zeit, die auf die eine oder andere Art die Netzwerkuntersttzung -zerstrte. -

2.4. Das fnfte Jahr von Pbuilder

- pbuilder wird nun weitgehend als -Beinahe-Standardwerkzeug zum Testen von Paketen und dem Bauen von Paketen -in einer unberhrten Umgebung angenommen. Es gibt andere hnliche Werkzeuge, -die hnliche Aufgaben erledigen, aber sie verfolgen nicht das gleiche -Ziel. Um dieser Tatsache zu gedenken, wird pbuilder nun -von mehreren Leuten mitbetreut. -

- sbuild ist nun ein gut betreutes Debian-Paket innerhalb -von Debian und mit pbuilder als solch langsamem Monster -bevorzugen einige Leute das Nherkommen von Sbuild. Es besteht die Hoffnung, -dass die Entwicklung, um LVM-Schnappschsse oder Cowdancer zu benutzen, die -Situation etwas verbessert. -

diff -Nru pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.fr.html pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.fr.html --- pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.fr.html 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.fr.html 1970-01-01 00:00:00.000000000 +0000 @@ -1,985 +0,0 @@ -Manuel de l'utilisateur de pbuilder

Manuel de l'utilisateur de pbuilder

Mode d'emploi

Junichi Uekawa

documentation en construction

Table des matires

1. Prsentation de pbuilder
1. Buts de pbuilder
2. Utilisation de pbuilder
1. Cration de l'image de base
2. Mettre jour le fichier base.tgz
3. Construire un paquet en utilisant le fichier base.tgz
4. pdebuild ou comment viter d'en taper trop
5. Fichiers de configuration
6. Construire des paquets sans tre root dans l'environnement de base
7. Utiliser pbuilder pour les rtroportages
8. Construction des paquets en grand nombre
9. Scripts de rtroportage automatique
10. Utiliser pbuilder pour tester automatiquement les paquets
11. Utiliser pbuilder pour tester la construction en utilisant d'autres -compilateurs
3. Utiliser User-mode-linux avec pbuilder
1. Configurer user-mode-linux
2. Configurer rootstrap
3. Configurer pbuilder-uml
4. Considrations pour excuter pbuilder-user-mode-linux
5. Excution en parallle de pbuilder-user-mode-linux
6. Utiliser pbuilder-user-mode-linux pour dmarrer une machine virtuelle
4. Questions frquentes
1. chec de pbuilder create
2. Les rpertoires ne peuvent pas tre rattachs -(bind-mount)
3. Se logguer dans pbuilder pour dterminer les problmes de construction
4. Se logguer dans pbuilder pour modifier l'environnement
5. Variable BUILDRESULTUID pour les sessions utilisant sudo
6. Note propos de l'utilisation de $TMPDIR
7. Crer un raccourci pour lancer pbuilder pour une -distribution spcifique
8. Utilisation des variables d'environnement pour lancer -pbuilder pour une distribution spcifique -
9. Utiliser des sources spcifiques pour apt et des paquets locaux
10. Comment configurer pbuilder pour lancer apt-get update avant de tenter de -satisfaire les dpendances la construction
11. Utilise une invite diffrente l'intrieur de pbuilder
12. Cration d'un pense-bte de chroot
13. Utiliser /var/cache/apt/archives comme cache pour les paquets
14. Rtroportage de pbuilder vers les versions stables de Debian
15. Alerte: LOGNAME n'est pas dfini.
16. Construction impossible: conflit avec un paquet essentiel
17. viter le message "ln: Lien crois de priphrique invalide"
18. Utiliser fakechroot
19. Utiliser debconf l'intrieur d'une session pbuilder
20. L'option de montage nodev entrave le bon fonctionnement de pbuilder
21. pbuilder est lent
22. Utilisation de pdebuild pour parrainer un paquet
23. Pourquoi y'a-t-il un fichier source.changes dans ../?
24. amd64 et i386-mode
25. Utilisation de tmpfs comme emplacement de construction
26. Utiliser svn-buildpackage avec pbuilder
5. Dpistage des pannes et dveloppement
1. Rapports de bogues
2. Liste de diffusion
3. Canal IRC
4. Informations pour les dveloppeurs de pbuilder
6. Autres utilisations de pbuilder
1. Utilisation de pbuilder pour de petites exprimentations
2. Lancer de petits programmes dans l'environnement de base
7. Experimental or wishlist features of pbuilder
1. Utilisation de LVM
2. Utilisation de cowdancer
3. Utilisation de pbuilder sans tar.gz
4. Utilisation de pbuilder dans un vserver
5. Usage of ccache
8. Documents de rfrence
1. Structure des rpertoires l'extrieur de l'environnement de base
2. Structure des rpertoires l'intrieur de l'image de base
9. Quelques dtails archologiques mineurs
1. Historique de la documentation
2. Histoire peut-tre incorrecte de pbuilder
2.1. L'avant pbuilder
2.2. Naissance de pbuilder
2.3. Et la seconde anne de sa vie
2.4. Cinq annes de pbuilder

Liste des tableaux

5.1. Structure des rpertoires de la suite de tests
8.1. Structure des rpertoires l'extrieur de l'environnement de base
8.2. Structure des rpertoires l'intrieur de l'image de base

Chapitre1.Prsentation de pbuilder

Table des matires

1. Buts de pbuilder

1.Buts de pbuilder

- pbuilder signifie Personal -Builder et constitue un systme de construction automatique -des paquets Debian destin une utilisation sur une station de -dveloppement personnelle. pbuilder se veut un systme -simple mettre en place pour construire automatiquement des paquets Debian - l'intrieur d'un environnement propre afin de vrifier qu'un paquet peut -tre construit sur la plupart des installations de Debian. L'environnement -propre est ralis travers une image de base ne contenant qu'un minimum de -paquets. -

- La distribution Debian est constitue de logiciels libres accompagns des -sources. Tous les codes sources dans la section "main" de Debian doivent -tre construits uniquement l'aide des dpendances sources explicitement -spcifies et contenues galement dans la section "main". -

- L'objectif principal de pbuilder est diffrent de celui -des autres systmes de construction automatique dans Debian dans le sens o -il ne s'agit pas de construire le maximum de paquets possible. Les paquets -ncessaires ne sont pas devins et quand un choix est ncessaire, c'est le -plus souvent le plus mauvais choix qui est slectionn. -

- De cette faon, pbuilder tente de garantir que les -paquets construits travers pbuilder se construiront -certainement correctement sur la plupart des installations de Debian -permettant ainsi d'obtenir la capacit de construire Debian partir des -sources. -

- La possibilit de construire Debian partir des sources est dsormais -quasiment acquis et a vu beaucoup de progrs. l'poque de Debian 3.0, de -nombreux problmes pouvaient survenir en construisant Debian depuis les -sources. Depuis, les choses se sont grandemment amliores. -

Chapitre2.Utilisation de pbuilder

Table des matires

1. Cration de l'image de base
2. Mettre jour le fichier base.tgz
3. Construire un paquet en utilisant le fichier base.tgz
4. pdebuild ou comment viter d'en taper trop
5. Fichiers de configuration
6. Construire des paquets sans tre root dans l'environnement de base
7. Utiliser pbuilder pour les rtroportages
8. Construction des paquets en grand nombre
9. Scripts de rtroportage automatique
10. Utiliser pbuilder pour tester automatiquement les paquets
11. Utiliser pbuilder pour tester la construction en utilisant d'autres -compilateurs

- Pour tre oprationnel, il existe plusieurs commandes -simples. pbuilder create, pbuilder -update et pbuilder build sont les commandes les -plus couramment utilises. Regardons chacune de ces commandes. -

1.Cration de l'image de base

- pbuilder create will create a base chroot image tar-ball -(base.tgz). All other commands will operate on the resulting base.tgz If -the Debian release to be created within chroot is not going to be "sid" -(which is the default), the distribution code-name needs to be specified -with the --distribution command-line -option. -

- debootstrap [1] is used -to create the bare minimum Debian installation, and then build-essential -packages are installed on top of the minimum installation using -apt-get inside the chroot. -

- For fuller documentation of command-line options, see the pbuilder.8 manual -page. Some configuration will be required for -/etc/pbuilderrc for the mirror site [2] to use, and proxy configuration may be required to -allow access through HTTP. See the pbuilderrc.5 manual page for details. -

2.Mettre jour le fichier base.tgz

pbuilder update will update the base.tgz. It will -extract the chroot, invoke apt-get update and -apt-get dist-upgrade inside the chroot, and then recreate -the base.tgz (the base tar-ball). -

- It is possible to switch the distribution which the base.tgz is targeted at -at this point. Specify --distribution -sid ---override-config to change the distribution to -sid. [3] -

- Pour une documentation plus complte des options disponibles, rfrez-vous -la page de manuel pbuilder.8. -

3.Construire un paquet en utilisant le fichier base.tgz

- To build a package inside the chroot, invoke pbuilder build -whatever.dsc. pbuilder will -extract the base.tgz to a temporary working directory, enter the directory -with chroot, satisfy the build-dependencies inside chroot, and build the -package. The built packages will be moved to a directory specified with the ---buildresult command-line option. -

- The --basetgz option can be used to -specify which base.tgz to use. -

- pbuilder va extraire un environnement de base du fichier -base.tgz. (base.tgz est cr l'aide de pbuilder create -et mis jour avec pbuilder update.) Le fichier -debian/control est analys afin de dterminer les dpendances installer -avec apt-get. -

- Pour une documentation plus complte des options disponibles, rfrez-vous -la page de manuel pbuilder.8. -

4.pdebuild ou comment viter d'en taper trop

- pdebuild est un petit script qui permet d'effectuer les -tches les plus frquentes. Pour construire un paquet, un dveloppeur Debian -peut utiliser debuild dans un rpertoire source -Debian. pdebuild utilise un principe similaire et permet -de construire un paquet dans l'environnement de base et de vrifier ainsi -que le code source actuel se construit sans problme dans celui-ci. -

- pdebuild calls dpkg-source to build -the source packages, and then invokes pbuilder on the -resulting source package. However, unlike debuild, the resulting deb files -will be found in the --buildresult -directory. -

- Rfrez-vous la page de manuel pdebuild.1 pour plus de dtails. -

- There is a slightly different mode of operation available in -pdebuild since version 0.97. pdebuild -usually runs debian/rules clean outside of the chroot; -however, it is possible to change the behavior to run it inside the chroot -with the --use-pdebuild-internal. It -will try to bind mount the working directory inside chroot, and run -dpkg-buildpackage inside. It has the following -characteristics, and is not yet the default mode of operation. -

  • - Les dpendances de construction sont satisfaites l'intrieur de -l'environnement de base avant de crer le paquet source. Bien que ce soit un -bon comportement, pdebuild ne l'effectue pas par dfaut. -

  • Le rpertoire de travail est modifi depuis l'environnement de base.

  • Construire en utilisant pdebuild ne garantit pas que cela -fonctionnera galement avec pbuilder.

  • Si la construction du paquet source ne russit pas, la session utilisant -l'environnement de base est gche (la cration de cet environnement prend -un peu de temps, ce qui peut tre amlior en utilisant cowdancer).

  • Does not work in the same manner as it used to; for example, ---buildresult does not have any effect.

  • La construction dans l'environnement de base utilise le mme utilisateur -qu'en dehors de celui-ci. -

5.Fichiers de configuration

- Il est possible de spcifier tous les paramtres en utilisant les options en -ligne de commande. Toutefois, afin d'viter de retaper celles-ci chaque -fois, il est possible d'utiliser un fichier de configuration. -

- /etc/pbuilderrc et -${HOME}/.pbuilderrc sont lus lors de l'utilisation de -pbuilder. Les options possibles sont documentes dans la -page de manuel pbuilderrc.5. -

- It is useful to use --configfile option to load up a preset -configuration file when switching between configuration files for different -distributions. -

- Please note ${HOME}/.pbuilderrc supersede system -settings. Caveats is that if you have some configuration, you may need to -tweak the configuration to work with new versions of pbuilder when -upgrading. -

6.Construire des paquets sans tre root dans l'environnement de base

- pbuilder requires full root privilege when it is -satisfying the build-dependencies, but most packages do not need root -privilege to build, or even refused to build when they are built as root. -pbuilder can create a user which is only used inside -pbuilder and use that user id when building, and use the -fakeroot command when root privilege is required. -

- L'option de configuration BUILDUSERID doit correspondre la valeur d'un -identifiant utilisateur n'existant pas encore sur le systme de faon ce -qu'il soit plus difficile pour les paquets construits avec -pbuilder d'affecter le systme en dehors de -l'environnement de base. Quand l'option de configuration BUILDUSERNAME est -aussi renseigne, pbuilder utilisera le nom d'utilisateur -indiqu et fakeroot pour construire les paquets plutt que d'tre root dans -l'environnement de base. -

- Mme en utilisant ces options, pbuilder utilisera les -privilges du super-utilisateur quand ils seront rellement ncessaires, par -exemple quand il doit installer des paquets dans l'environnement de base. -

- Pour pouvoir utiliser pbuilder sans tre root, vous devez -utiliser user-mode-linux comme expliqu dans Chapitre3, Utiliser User-mode-linux avec pbuilder -

7.Utiliser pbuilder pour les rtroportages

- pbuilder peut tre utilis pour rtroporter des logiciels -de la dernire distribution Debian vers une version stable plus ancienne en -utilisant une image de base de l'ancienne distribution et en construisant -les paquets dans celle-ci. Il y a plusieurs points considrer et, en -raison de ceux-ci, le rtroportage automatique n'est gnralement pas -possible et une intervention manuelle est requise: -

  • Le paquet de la distribution unstable peut dpendre de paquets ou de -versions de paquets qui sont disponibles uniquement dans unstable. Il -peut donc tre impossible de satisfaire les dpendances de construction dans -stable (sans travail supplmentaire).

  • La distribution stable peut contenir des bugs qui ont t corrigs dans -unstable et qui ont besoin d'tre contourns.

  • Le paquet dans unstable peut avoir des problmes de construction, y -compris dans unstable.

8.Construction des paquets en grand nombre

- pbuilder peut tre automatis car le processus ne -ncessite pas d'interactions. Il est possible d'excuter -pbuilder sur plusieurs paquets de manire non -interactive. Plusieurs scripts destins cet usage existent. Junichi Uekawa -utilise un tel script depuis 2001 et a envoy des rapports de bugs pour les -paquets qui n'ont pas pu tre construits avec -pbuilder. Plusieurs problmes existent avec la -construction automatique: -

  • Les dpendances la construction doivent s'installer sans ncessiter -d'interactions. Cependant, certains paquets ne peuvent pas s'installer sans -interaction (postgresql par exemple).

  • Quand une bibliothque est casse ou qu'un problme survient sur gcc/gcj/g++ -ou mme bison, un trs grand nombre d'checs sont signals (gcj-3.0 qui n'a -pas de commande "javac", bison qui devient plus strict, etc.). -

  • Certaines personnes sont particulirement hostiles vis--vis des rapports -d'checs de construction partir des sources.

- La plupart des bugs prsents initialement dans pbuilder -ont t rsolus autour de 2002 mais ces problmes transitionnels qui -affectent une grande partie de l'archive Debian apparaissent de temps en -temps. Les tests de rgression sont alors utiles. -

- Un script qui tait utilis par Junichi Uekawa est dsormais inclus dans la -distribution de pbuilder sous le nom -pbuildd.sh. Il est disponible dans -/usr/share/doc/pbuilder/examples/pbuildd/ et son -fichier de configuration est -/etc/pbuilder/pbuildd-config.sh. Les personnes qui sont -habitues pbuilder devraient facilement pouvoir -l'utiliser. Il existe depuis un certain temps et vous devriez aussi pouvoir -l'utiliser sur votre systme. Cette version n'est pas la mieux teste mais -devrait pouvoir servir de base. -

- Pour configurer pbuildd, vous devez prendre en considration un certain -nombre de points. -

  • Un fichier ./avoidlist doit contenir la liste des -paquets qu'il ne faut pas construire.

  • Il essaiera de construire absolument tout, y compris les paquets qui ne sont -pas destins votre architecture.

  • Parce que vous allez excuter un certain nombre de scripts de construction, -utilisez l'option fakeroot de pbuilder plutt que de -l'excuter avec les privilges du super-utilisateur.

  • Parce qu'il n'est pas garanti que toutes les constructions se finiront en un -temps fini, placer une limite temporelle sur l'excution est sans doute -ncessaire. Dans le cas contraire, pbuildd peut rester indfiniment sur un -mauvais paquet.

  • - Certains paquets ncessitent beaucoup d'espace disque. Environ 2 Go sont -actuellement suffisants pour les paquets les plus gros. Si vous trouvez des -contre-exemples, informez-en le mainteneur de cette documentation. -

9.Scripts de rtroportage automatique

- Certaines personnes utilisent pbuilder pour rtroporter -automatiquement un sous-ensemble de paquets vers la distribution stable. -

- Je souhaiterais obtenir quelques informations sur la faon de faire. Un -retour sur le sujet ou des exemples seraient apprcis. -

10.Utiliser pbuilder pour tester automatiquement les paquets

- pbuilder peut tre utilis pour tester automatiquement -les paquets. Il est possible de dfinir des crochets qui vont essayer -d'installer le paquet dans l'image de base, les excuter ou toute autre -action. Voici quelques pistes: -

  • Automatic install-remove-install-purge-upgrade-remove-upgrade-purge -test-suite (distributed as an example, B91dpkg-i), or -just check that everything installs somewhat -(execute_installtest.sh).

  • Lancer automatiquement lintian. Un exemple est fourni dans -/usr/share/doc/pbuilder/examples/B90lintian).

  • Utiliser automatiquement debian-test sur le paquet. Le paquet debian-test a -t retir de Debian. Vous pouvez trouver dans le rpertoire -debian/pbuilder-test une implmentation pour -pbuilder travers le script B92test-pkg.

- To use B92test-pkg script, first, add it to your hook directory. -[4]. The test files are shell scripts -placed in debian/pbuilder-test/NN_name (where NN is a -number) following run-parts standard[5] -for file names. After a successful build, packages are first tested for -installation and removal, and then each test is ran inside the chroot. The -current directory is the top directory of the source-code. This means you -can expect to be able to use ./debian/ directory from inside your scripts. -

- Example scripts for use with pbuilder-test can be found in -/usr/share/doc/pbuilder/examples/pbuilder-test. -

11.Utiliser pbuilder pour tester la construction en utilisant d'autres -compilateurs

- Most packages are compiled with gcc or -g++ and using the default compiler version, which was gcc -2.95 for Debian GNU/Linux 3.0 (i386). However, Debian 3.0 was distributed -with other compilers, under package names such as gcc-3.2 -for gcc compiler version 3.2. It was therefore possible to try compiling -packages against different compiler versions. -pentium-builder provides an infrastructure for using a -different compiler for building packages than the default gcc, by providing -a wrapper script called gcc which calls the real gcc. To use -pentium-builder in pbuilder, it is -possible to set up the following in the configuration: 

-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2

-

- Cela indique pbuilder d'installer le paquet -pentium-builder ainsi que le compilateur GCC 3.2 dans -l'image de base puis de renseigner les variables d'environnement ncessaires -pour faire fonctionner pentium-builder. -


[1] il est possible de choisir debootstrap ou cdebootstrap

[2] - Il est prfrable d'utiliser un miroir local ou un serveur cache afin de ne -pas surcharger les miroirs publics avec un trs grand nombre -d'accs. L'utilisation d'outils tels que apt-proxy est conseille. -

[3] Seule une mise jour est possible: Debian ne supporte pas (encore?) les -retours en arrire.

[4] Il est possible d'utiliser l'option --hookdir -/usr/share/doc/pbuilder/examples pour inclure tous les crochets -donns en exemple.

[5] Voyez run-parts(8). Par exemple, n'utilisez pas '.' dans les noms de -fichiers! -

Chapitre3.Utiliser User-mode-linux avec pbuilder

Table des matires

1. Configurer user-mode-linux
2. Configurer rootstrap
3. Configurer pbuilder-uml
4. Considrations pour excuter pbuilder-user-mode-linux
5. Excution en parallle de pbuilder-user-mode-linux
6. Utiliser pbuilder-user-mode-linux pour dmarrer une machine virtuelle

- Il est possible d'utiliser user-mode-linux en invoquant -pbuilder-user-mode-linux plutt que -pbuilder. pbuilder-user-mode-linux ne -ncessite pas les privilges du super-utilisateur et utilise la mthode -copy-on-write (COW) ce qui la rend plus -rapide que le traditionnel pbuilder. -

- User-mode-linux est une plateforme moins prouve que les -outils standards sur lesquels reposent pbuilder -((chroot, tar, et -gzip) mais suffisamment mre car prsente depuis la -version 0.59. Depuis, pbuilder-user-mode-linux a connu -une volution rapide. -

- La configuration de pbuilder-user-mode-linux s'effectue -en trois tapes: -

  • Configuration de user-mode-linux

  • Configuration de rootstrap

  • Configuration de pbuilder-uml

-

1.Configurer user-mode-linux

- user-mode-linux peut prsenter quelques difficults de configuration. Il est -prfrable de se familiariser avec avant de tenter d'utiliser -rootstrap ou -pbuilder-user-mode-linux. Pour plus de dtails, -reportez-vous au fichier -/usr/share/doc/uml-utilities/README.Debian et la -documentation de user-mode-linux qui se trouve dans le -paquet user-mode-linux-doc. -

- user-mode-linux ncessite que l'utilisateur appartienne -au groupe uml-net de faon configurer le rseau, sauf si utilisez slirp. -

- Si vous compilez votre propre noyau, vrifiez que le support de TUN/TAP est -activ. Vous pouvez ventuellement appliquer le patch SKAS. -

2.Configurer rootstrap

- rootstrap est un utilitaire construit autour de -debootstrap. Il cre une image disque de Debian destine tre utilise -avec UML. Pour configurer rootstrap, il y a plusieurs prrequis. -

  • Installer le paquet rootstrap.

  • - TUN/TAP only: add the user to the uml-net group to allow access to the -network 

    adduser dancer uml-net

    -

  • Seulement pour utiliser TUN/TAP: vrifier que le noyau inclut l'interface -TUN/TAP ou recompiler le noyau si ncessaire. -

  • Set up /etc/rootstrap/rootstrap.conf. For example, if -the current host is 192.168.1.2, changing following entries to something -like this seems to work. 

    -transport=tuntap
-interface=eth0
-gateway=192.168.1.1
-mirror=http://192.168.1.2:8081/debian
-host=192.168.1.198
-uml=192.168.1.199
-netmask=255.255.255.0

    Some -experimentation with configuration and running rootstrap -~/test.uml to actually test it would be handy. -

    - Utiliser slirp ncessite moins de configuration. La configuration par dfaut -est livre avec un exemple fonctionnel. -

3.Configurer pbuilder-uml

- Suivre les tapes suivantes: -

  • Installer le paquet pbuilder-uml.

  • - Set up the configuration file -/etc/pbuilder/pbuilder-uml.conf in the following -manner. It will be different for slirp. 

    -MY_ETH0=tuntap,,,192.168.1.198
-UML_IP=192.168.1.199
-UML_NETMASK=255.255.255.0
-UML_NETWORK=192.168.1.0
-UML_BROADCAST=255.255.255.255
-UML_GATEWAY=192.168.1.1
-PBUILDER_UML_IMAGE="/home/dancer/uml-image"

    -Also, it needs to match the rootstrap configuration. -

  • - Assurez-vous que l'utilisateur a les droits pour crire dans -BUILDPLACE. Changez la valeur de BUILDPLACE dans le fichier de configuration -pour un emplacement pour lequel l'utilisateur a les droits d'criture. -

  • Run pbuilder-user-mode-linux create --distribution -sid to create the image.

  • Essayez pbuilder-user-mode-linux build.

-

4.Considrations pour excuter pbuilder-user-mode-linux

- pbuilder-user-mode-linux mule la plupart des -fonctionnalits de pbuilder avec quelques diffrences. -

  • - pbuilder-user-mode-linux ne supporte pas encore -correctement toutes les options de pbuilder. C'est un -problme qui sera rgl au fur et mesure. -

  • - /tmp is handled differently inside -pbuilder-user-mode-linux. In -pbuilder-user-mode-linux, /tmp is -mounted as tmpfs inside UML, so accessing files under -/tmp from outside user-mode-linux does not work. It -affects options like --configfile, and -when trying to build packages placed under /tmp. -

5.Excution en parallle de pbuilder-user-mode-linux

- Pour excuter pbuilder-user-mode-linux en parallle sur -un systme, un certain nombre de choses doivent tre gardes l'esprit. -

  • Les mthodes create et update ne doivent pas tre excutes lorsqu'un paquet -est en cours de construction. Dans le cas contraire, le fichier COW sera -corrompu.

  • - If you are not using slirp, user-mode-linux processes which are running in -parallel need to have different IP addresses. Just trying to run the -pbuilder-user-mode-linux several times will result in -failure to access the network. But something like the following will work: -

    -for IP in 102 103 104 105; do
-  xterm -e pbuilder-user-mode-linux build --uml-ip 192.168.0.$IP \
-    20030107/whizzytex_1.1.1-1.dsc &
-done

    When using slirp, this problem does not -exist. -

6.Utiliser pbuilder-user-mode-linux pour dmarrer une machine virtuelle

- It is possible to use pbuilder-user-mode-linux for other -uses than just building Debian packages. pbuilder-user-mode-linux -login will let a user use a shell inside the -user-mode-linux pbuilder base image, and -pbuilder-user-mode-linux execute will -allow the user to execute a script inside the image. -

- Vous pouvez utiliser un script pour installer ssh et ajouter un nouvel -utilisateur ce qui permettra d'accder l'intrieur de user-mode-linux -l'aide de ssh. -

- Il n'est pas possible d'utiliser un script depuis /tmp -en raison du fait que pbuilder-user-mode-linux monte un -tmpfs sur /tmp. -

- Le script d'exemple suivant permet de dmarrer sshd dans user-mode-linux. - 

-#!/bin/bash
-
-apt-get install -y ssh xbase-clients xterm
-echo "enter root password"
-passwd
-cp /etc/ssh/sshd_config{,-}
-sed 's/X11Forwarding.*/X11Forwarding yes/' /etc/ssh/sshd_config- > /etc/ssh/sshd_config
-
-/etc/init.d/ssh restart
-ifconfig
-echo "Hit enter to finish"
-read

Chapitre4.Questions frquentes

Table des matires

1. chec de pbuilder create
2. Les rpertoires ne peuvent pas tre rattachs -(bind-mount)
3. Se logguer dans pbuilder pour dterminer les problmes de construction
4. Se logguer dans pbuilder pour modifier l'environnement
5. Variable BUILDRESULTUID pour les sessions utilisant sudo
6. Note propos de l'utilisation de $TMPDIR
7. Crer un raccourci pour lancer pbuilder pour une -distribution spcifique
8. Utilisation des variables d'environnement pour lancer -pbuilder pour une distribution spcifique -
9. Utiliser des sources spcifiques pour apt et des paquets locaux
10. Comment configurer pbuilder pour lancer apt-get update avant de tenter de -satisfaire les dpendances la construction
11. Utilise une invite diffrente l'intrieur de pbuilder
12. Cration d'un pense-bte de chroot
13. Utiliser /var/cache/apt/archives comme cache pour les paquets
14. Rtroportage de pbuilder vers les versions stables de Debian
15. Alerte: LOGNAME n'est pas dfini.
16. Construction impossible: conflit avec un paquet essentiel
17. viter le message "ln: Lien crois de priphrique invalide"
18. Utiliser fakechroot
19. Utiliser debconf l'intrieur d'une session pbuilder
20. L'option de montage nodev entrave le bon fonctionnement de pbuilder
21. pbuilder est lent
22. Utilisation de pdebuild pour parrainer un paquet
23. Pourquoi y'a-t-il un fichier source.changes dans ../?
24. amd64 et i386-mode
25. Utilisation de tmpfs comme emplacement de construction
26. Utiliser svn-buildpackage avec pbuilder

- Les problmes frquemment recontrs et les questions les plus courantes sont -documentes ici. Cette portion tait initialement disponible dans le fichier -README.Debian mais a t dplace ici. -

1.chec de pbuilder create

- Il est frquent que pbuilder ne parvienne pas crer une -image de base rcente. Essayez de mettre jour pbuilder -et debootstrap. Pour le moment, il n'est possible de concevoir que des -logiciels sachant prendre en compte le pass. Une fois que nous serons -l'aise avec le pass, nous pourrons nous concentrer sur les prvisions du -futur. -

- Certaines personnes rtroportent de manire occasionnelle debootstrap pour -les versions stables ; trouvez-les. -

- Quand une erreur concerne la phase de debootstrap, c'est le script -debootstrap qui doit tre corrig. pbuilder ne permet pas -de pallier aux problmes de debootstrap. -

2.Les rpertoires ne peuvent pas tre rattachs -(bind-mount)

- En raison du mode de fonctionnement de pbuilder, il y a -plusieurs rpertoires qui ne peuvent pas tre rattachs lorsque -pbuilder tourne. Ces rpertoires incluent -/tmp, /var/cache/pbuilder et des -rpertoires systmes comme /etc et -/usr. Il est recommand de ne rattacher que des -rpertoires prsents dans le dossier de l'utilisateur. -

3.Se logguer dans pbuilder pour dterminer les problmes de construction

- It is possible to invoke a shell session after a build failure. Example -hook scripts are provided as C10shell and -C11screen scripts. C10shell script will start bash -inside chroot, and C11screen script will start GNU screen inside the chroot. -

4.Se logguer dans pbuilder pour modifier l'environnement

- Il est parfois ncessaire de modifier l'image de -base. login supprimera toute modification aprs -dconnexion. Il est possible de lancer un shell en utilisant les -crochets. pbuilder update excute les scripts commenant -par 'E' et un exemple pour lancer un shell est fourni sous le nom -C10shell. - 

-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell

- It is also possible to add --save-after-exec and/or ---save-after-login options to the pbuilder -login session to accomplish the goal. It is possible to add the ---uml-login-nocow option to -pbuilder-user-mode-linux login session -as well. -

5.Variable BUILDRESULTUID pour les sessions utilisant sudo

- It is possible to set 

BUILDRESULTUID=$SUDO_UID

in pbuilderrc to -set the proper BUILDRESULTUID when using sudo. -

6.Note propos de l'utilisation de $TMPDIR

- Si vous placez la variable $TMPDIR une valeur inhabituelle, des erreurs -peuvent se produire dans l'environnement de base telles que des checs de -dpkg-source. -

There are two options, you may install a hook to create that directory, or -set 

export TMPDIR=/tmp

in pbuilderrc. Take your pick. -

- Un script d'exemple est fourni sous le nom -examples/D10tmp avec pbuilder. -

7.Crer un raccourci pour lancer pbuilder pour une -distribution spcifique

- When working with multiple chroots, it would be nice to work with scripts -that reduce the amount of typing. An example script -pbuilder-distribution.sh is provided as an example. -Invoking the script as pbuilder-squeeze will invoke -pbuilder with a squeeze chroot. -

8.Utilisation des variables d'environnement pour lancer -pbuilder pour une distribution spcifique -

This section[6] describes briefly a way to -setup and use multiple pbuilder setups by creating a pbuilderrc -configuration in your home path ($HOME/.pbuilderrc) -and using the variable "DIST" when running pbuilder or pdebuild. -

Tout d'abord, mettez en place un fichier -$HOME/.pbuilderrc ressemblant ceci:

- 

-if [ -n "${DIST}" ]; then
-        BASETGZ="`dirname $BASETGZ`/$DIST-base.tgz"
-        DISTRIBUTION="$DIST"
-        BUILDRESULT="/var/cache/pbuilder/$DIST/result/"
-        APTCACHE="/var/cache/pbuilder/$DIST/aptcache/"
-fi
-

Puis, ds que vous voulez utiliser une distribution particulire avec -pbuilder, assignez la valeur de "DIST" une des distributions de Debian ou -n'importe quelle distribution base sur Debian (c'est dire n'importe -quelle valeur qui se trouve dans /usr/lib/debootstrap/scripts). -

Voici quelques exemples d'utilisation avec pbuilder ou pdebuild: -

-DIST=gutsy sudo pbuilder create
-
-DIST=sid sudo pbuilder create --mirror http://http.us.debian.org/debian
-
-DIST=gutsy sudo pbuilder create \
-        --othermirror "deb http://archive.ubuntu.com/ubuntu gutsy universe \
-        multiverse"
-
-DIST=gutsy sudo pbuilder update
-
-DIST=sid sudo pbuilder update --override-config --mirror \
-http://http.us.debian.org/debian \
---othermirror "deb http://http.us.debian.org/debian sid contrib non-free"
-
-DIST=gutsy pdebuild
-

9.Utiliser des sources spcifiques pour apt et des paquets locaux

- If you have some very specialized requirements on your apt setup inside -pbuilder, it is possible to specify that through the ---othermirror option. Try something -like: --othermirror "deb http://local/mirror stable -main|deb-src http://local/source/repository ./" -

- To use the local file system instead of HTTP, it is necessary to do -bind-mounting. --bindmounts is a -command-line option useful for such cases. -

- Utiliser les paquets que vous venez de construire dans l'environnement de -base peut tre pratique. Il est possible d'automatiser cette tche en -utilisant la configuration suivante. D'abord, configurez pbuilderrc pour -rattacher votre rpertoire contenant le rsultat des constructions. -

- 

BINDMOUNTS="/var/cache/pbuilder/result"

-

- Puis utilisez le crochet suivant -

- 

-# cat /var/cache/pbuilder/hooks/D70results
-#!/bin/sh
-cd /var/cache/pbuilder/result/
-/usr/bin/dpkg-scanpackages . /dev/null > /var/cache/pbuilder/result/Packages
-/usr/bin/apt-get update

-

- De cette faon, vous pouvez utiliser deb -file:/var/cache/pbuilder/result -

- -To add new apt-key inside chroot: - -

- 

-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-

10.Comment configurer pbuilder pour lancer apt-get update avant de tenter de -satisfaire les dpendances la construction

- Vous pouvez utiliser cet effet des crochets. Les scripts commenant par D -sont lancs avant de rsoudre les dpendances la construction. -

- -This snippet comes from Ondrej Sury. -

11.Utilise une invite diffrente l'intrieur de pbuilder

- Pour indiquer que l'on se trouve l'intrieur de -pbuilder, il est possible de modifier l'invite en -utilisant des variables comme PS1 dans pbuilderrc -

- With versions of bash more recent than 2.05b-2-15, the value of the -debian_chroot variable, if set, is included in the value of PS1 (the Bash -prompt) inside the chroot. In prior versions of bash,[7] setting PS1 in pbuilderrc worked. -

exemple pour debian_chroot

-	export debian_chroot="pbuild$$"

exemple pour PS1

-	export PS1="pbuild chroot 32165 # "

12.Cration d'un pense-bte de chroot

- L'invite de Bash vous aidera vous souvenir que vous tes dans un -environnement chroot. Dans certains cas, vous pourriez souhaiter disposer -d'autres lments l'indiquant. Utilisez le script crochet -examples/F90chrootmemo. Il crera un fichier nomm -/CHROOT dans l'environnement chroot. -

13.Utiliser /var/cache/apt/archives comme cache pour les paquets

- Pour les systmes dont la bande passante est rduite, il est possible -d'utiliser /var/cache/apt/archives comme cache pour les -paquets. Indiquez ce rpertoire la place de celui par dfaut -/var/cache/pbuilder/aptcache. -

- Il n'est cependant pas possible de faire ainsi pour le moment avec la -version pour user-mode-linux de pbuilder car -/var/cache/apt/archives n'est gnralement accessible -en criture que par root. -

- L'utilisation d'outils comme apt-proxy est recommand car la mise en cache -des paquets profite galement au reste du systme. -

14.Rtroportage de pbuilder vers les versions stables de Debian

- Currently stable back port of pbuilder is available at backports.org. -

15.Alerte: LOGNAME n'est pas dfini.

- Vous pourriez voir beaucoup de message d'alertes en excutant -pbuilder. -

- 

-	dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)

-

- Il n'est pas risqu d'ignorer ce message. Veuillez signaler tout problme -avec LOGNAME non dfini. Paramtrer LOGNAME cause quelques problmes lors de -l'appel chroot. Par exemple, dpkg a besoin de getpwnam -pour fonctionner dans le chroot, ce qui implique que LOGNAME et les -informations relatives l'utilisateur doivent tre paramtrs dans le -chroot. -

16.Construction impossible: conflit avec un paquet essentiel

- pbuilder ne peut pas permettre de conflit de -construction ('Build-Conflict') sur des paquets essentiels. Il semble -vident que les paquets essentiels ne devraient pas tre enlevs d'un -systme Debian fonctionnel et qu'un paquet source ne devrait pas essayer de -forcer la suppression de tels paquets pour des utilisateurs construisant le -paquet. -

17.viter le message "ln: Lien crois de priphrique invalide"

- By default, pbuilder uses hard links to manage the -pbuilder package cache. It is not possible to make hard -links across different devices; and thus this error will occur, depending on -your set up. If this happens, set 

APTCACHEHARDLINK=no

in -your pbuilderrc file. Note that packages in APTCACHE will -be copied into chroot local cache, so plan for enough space on -BUILDPLACE device. -

18.Utiliser fakechroot

- It is possible to use fakechroot instead of being root to -run pbuilder; however, several things make this -impractical. fakechroot overrides library loads and -tries to override default libc functions when providing the functionality of -virtual chroot. However, some binaries do no use libc to -function, or override the overriding provided by -fakechroot. One example is ldd. -Inside fakechroot, ldd will check the -library dependency outside of the chroot, which is not the expected -behavior. -

- To work around the problem, debootstrap has a --variant -fakechroot option. Use that, so that ldd and ldconfig are -overridden. -

- Assurez-vous d'avoir correctement renseign la variable LD_PRELOAD, comme -dcrit dans la page de manuel de fakechroot. -

19.Utiliser debconf l'intrieur d'une session pbuilder

- Pour utiliser debconf l'intrieur de pbuilder, placer -la variable DEBIAN_FRONTEND readline dans -pbuilderrc devrait faire l'affaire. La placer -dialog devrait aussi marcher mais assurez-vous que whiptail -ou dialog sont installs dans l'environnement de base. -

20.L'option de montage nodev entrave le bon fonctionnement de pbuilder

- Si vous voyez de tels messages d'erreur lors de la construction de l'image -de base, c'est que vous utilisez l'option nodev pour monter le systme de -fichiers. - 

-	/var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied

- Vous aurez galement des problmes si vous montez le systme de fichiers -avec l'option noexec ou nosuid. Assurez-vous qu'aucun de ces drapeaux ne -soient utiliss lorsque vous montez le systme de fichiers pour -/var/cache/pbuilder ou $BUILDPLACE. -

- Ce problme n'apparat pas en utilisant user-mode-linux. -

- Rfrez-vous 316135 -pour un exemple. -

21.pbuilder est lent

- pbuilder est souvent lent. La partie la plus lente a lieu -lors de l'extraction de l'image de base chaque fois que -pbuilder est lanc. Cela peut tre vit en utilisant -pbuilder-user-mode-linux qui utilise un systme de -fichiers COW et qui n'a donc pas besoin de nettoyer et recrer l'image de -base. -

- pbuilder-user-mode-linux est plus lent construire les -paquets en raison du temps supplmentaire de traitement pour chaque appel -systme. Il est plus amical avec le disque dur. -

- pbuilder associ cowdancer est aussi une alternative -qui amliore la vitesse de lancement de pbuilder. -

22.Utilisation de pdebuild pour parrainer un paquet

- To sign a package marking for sponsorship, it is possible to -use --auto-debsign and ---debsign-k options of -pdebuild. - 

-	pdebuild  --auto-debsign  --debsign-k XXXXXXXX

23.Pourquoi y'a-t-il un fichier source.changes dans ../?

- En lanant pdebuild, pbuilder va -lancer dpkg-buildpackage pour crer le paquet source et le fournir -pbuilder. Le fichier XXXX_YYY_source.changes est le -reliquat de ce processus. C'est sans danger moins d'essayer de l'envoyer -dans l'archive Debian. -

- This behavior is different when running through ---use-pdebuild-internal -

24.amd64 et i386-mode

- amd64 architectures are capable of running binaries in i386 mode. It is -possible to use pbuilder to run packages, using -linux32 and debootstrap ---arch option. Specifically, a command-line -option like the following will work. -

- 

-pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
-  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian
-linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz

-

25.Utilisation de tmpfs comme emplacement de construction

- To improve speed of operation, it is possible to use tmpfs for pbuilder -build location. Mount tmpfs to -/var/cache/pbuilder/build, and set 

APTCACHEHARDLINK=no

. -

26.Utiliser svn-buildpackage avec pbuilder

- pdebuild command can be used with svn-buildpackage --svn-builder -command-line option. [8] - 

-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"

[6] Cette partie de la documentation est une contribution de Andres Mejia

- Cette exemple est issu d'un wiki (https://wiki.ubuntu.com/PbuilderHowto). -

[7] Les versions de bash jusqu' Debian 3.0 incluse

[8] -Zack has posted an example on his blog.

Chapitre5.Dpistage des pannes et dveloppement

Table des matires

1. Rapports de bogues
2. Liste de diffusion
3. Canal IRC
4. Informations pour les dveloppeurs de pbuilder

1.Rapports de bogues

- To report bugs, it would be important to have a log of what's going wrong. -Most of the time, adding a --debug -option and re-running the session should do the trick. Please send the log -of such session along with your problem to ease the debugging process. -

2.Liste de diffusion

- Il existe une liste de diffusion pour pbuilder sur alioth -(pbuilder-maint@lists.alioth.debian.org). Vous pouvez vous y inscrire -travers l'interface web http://alioth.debian.org/mail/?group_id=30778. -

3.Canal IRC

- Le canal IRC #pbuilder sur irc.oftc.net est utilis pour la coordination et -la communication. Indiquez-y votre intention avant d'effectuer un changement -ou de publier une modification. -

4.Informations pour les dveloppeurs de pbuilder

- Cette section tente de documenter les actuelles pratiques de dveloppement -et comment les choses marchent dans le dveloppement. -

- pbuilder est co-maintenu sur Alioth. La page du projet -sur Alioth se trouve l'adresse -http://alioth.debian.org/projects/pbuilder. La page d'accueil est -disponible sur -http://alioth.debian.org/projects/pbuilder. Le dpt git est -disponible par http, git ou (si vous avez un compte sur alioth) ssh. - 

-git-clone git://git.debian.org/git/pbuilder/pbuilder.git
-git-clone http://git.debian.org/git/pbuilder/pbuilder.git
-git-clone ssh://git.debian.org/git/pbuilder/pbuilder.git

- Git commit message should have the first one line describing what the commit -does, formatted in the way debian/changelog is formatted because it is -copied verbatim to changelog via git-dch. The second line is empty, and the -rest should describe the background and extra information related to -implementation of the commit. -

- Les suites de tests sont disponibles dans le rpertoire -./testsuite. Les changements ne doivent pas casser ces -tests. ./run-test.sh est une suite de tests simples -dont le rsultat est plac dans run-test.log et dans -run-test-cdebootstrap.log. -./run-test-regression.sh permet de tester les -rgressions. Les rsultats se trouvent dans -run-test-regression.log. Actuellement, run-test.sh est -lanc automatiquement tous les jours pour s'assurer que pbuilder est -fonctionnel. -

Tableau5.1.Structure des rpertoires de la suite de tests

RpertoireSignification
./testsuite/Rpertoire de la suite de tests
./testsuite/run-test.shTests de rgression journaliers pour dtecter les rgressions dues aux -changements survenus dans l'archive Debian.
./testsuite/run-test.logUn rsum de la suite de tests
./testsuite/normal/Rpertoire contenant les rsultats des tests en utilisant debootstrap
./testsuite/cdebootstrap/Rpertoire contenant les rsultats des tests en utilisant cdebootstrap
./testsuite/run-regression.shTests de rgression lancs chaque fois qu'un changement est effectu sur -pbuilder pour s'assurer qu'aucune rgression n'est apparue
./testsuite/run-regression.logRsum des rsultats des tests
./testsuite/regression/BugID-*.shTests de rgression, retourne 0 en cas de succs et 1 en cas d'chec
./testsuite/regression/BugID-*Fichiers utiliss pour les tests de rgression.
./testsuite/regression/log/BugID-*.sh.logSortie des tests de rgression obtenue par redirection de la sortie des -scripts par run-regression.sh

- When making changes, changes should be documented in the Git commit log. -git-dch will generate debian/changelog from the commit log. Make the first -line of your commit log meaningful, and add any bug-closing information -available. debian/changelog should not be edited directly unless when -releasing a new version. -

- Une liste des choses faire est disponible dans -debian/TODO. Elle n'est quasiment pas maintenue mais -deviendra un peu plus jour lorsqu'elle sera plus utilise. Le mode emacs -todoo-mode est utilis pour diter ce fichier. -

- Lorsqu'une nouvelle version de pbuilder est publie, elle -est marque avec l'tiquette X.XXX (numro de version). Le script -./git-tag.sh, disponible dans l'arbre de source, effectue -cette action. -

Chapitre6.Autres utilisations de pbuilder

Table des matires

1. Utilisation de pbuilder pour de petites exprimentations
2. Lancer de petits programmes dans l'environnement de base

1.Utilisation de pbuilder pour de petites exprimentations

- Dans certains cas, vous voulez mener de petites expriences sans risquer de -casser votre systme, par exemple pour installer une bibliothque -exprimentale ou pour compiler avec un compilateur exprimental. Dans de -tels cas, la commande pbuilder login est disponible. -

- pbuilder login est une fonctionnalit de diagnostic pour -pbuilder, mais permet aux utilisateurs d'obtenir -temporairement un environnement restreint. -

- noter que l'environnement est nettoy aprs la dconnexion du shell et que -monter des systmes de fichiers dans celui-ci est dconseill. -

2.Lancer de petits programmes dans l'environnement de base

- Pour faciliter l'utilisation de pbuilder pour d'autres -usages, la commande pbuilder execute est -disponible. Celle-ci prend en paramtre un script qui sera excut dans -l'environnement de base. -

- Le script peut tre utilis pour excuter une suite d'oprations comme -l'installation de ssh et l'ajout d'un nouvel utilisateur dans -l'environnement de base. -

Chapitre7.Experimental or wishlist features of pbuilder

Table des matires

1. Utilisation de LVM
2. Utilisation de cowdancer
3. Utilisation de pbuilder sans tar.gz
4. Utilisation de pbuilder dans un vserver
5. Usage of ccache

- pbuilder dispose de certaines fonctionnalits avances -pour certains usages spcifiques. -

1.Utilisation de LVM

- LVM2 has a useful snapshot function that features Copy-on-write images. -That could be used for pbuilder just as it can be used -for the user-mode-linux pbuilder port. lvmpbuilder -script in the examples directory implements such port. The scripts and -documentation can be found under -/usr/share/doc/pbuilder/examples/lvmpbuilder/. -

2.Utilisation de cowdancer

- cowdancer utilise des liens directs et des astuces -cassant ces liens lors d'une criture pour mettre en place un mcanisme de -copy-on-write. pbuilder utilis via -cowdancer semble beaucoup plus rapide et constitue un -point d'amlioration idal. cowbuilder est un script -autour de pbuilder permettant d'utiliser -cowdancer. Celui-ci est disponible dans le paquet -cowdancer depuis la version 0.14 -

- Voici quelques exemples pour utiliser cowbuilder. -

- 

-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc

-

- It is also possible to use cowdancer with pdebuild command. Specify with -command-line option --pbuilder or set it in -PDEBUILD_PBUILDER configuration option. -

- 

-$ pdebuild --pbuilder cowbuilder

-

3.Utilisation de pbuilder sans tar.gz

- The --no-targz option of -pbuilder will allow usage of pbuilder -in a different way from conventional usage. It will try to use an existing -chroot, and will not try to clean up after working on it. It is an -operation mode more like sbuild. -

- It should be possible to create base chroot images for -dchroot with the following commands: 

-# pbuilder create --distribution lenny --no-targz --basetgz /chroot/lenny
-# pbuilder create --distribution squeeze --no-targz --basetgz /chroot/squeeze
-# pbuilder create --distribution sid --no-targz --basetgz /chroot/sid

-

4.Utilisation de pbuilder dans un vserver

- Il est possible d'utiliser pbuilder dans un vserver. Cela -ncessite soit le paquet vserver-patches en version 2.1.1-rc14 ou plus -rcent ou bien un noyau Linux 2.6.16 ou plus rcent. -

- Pour utiliser la commande pbuilder dans un vserver, vous -avez besoin de placer le CAPS -secure_mount dans les ccapabilities de -ce vserver. -

5.Usage of ccache

- It is possible to use C compiler cache ccache to speed up -repeated builds of the same package (or packages that compile the same files -multiple times for some reason). Using ccache can speed -up repeated building of large packages dramatically, at the cost of some -disk space and bookkeeping. -

- To enable usage of ccache with -pbuilder, you should set CCACHEDIR in your pbuilderrc -file. -

- Current implementation of ccache support has several bugs, that CCACHEDIR -must be owned by the pbuilder build user, and parallel runs of pbuilder is -not supported. Therefore it is not enabled by default. -

Chapitre8.Documents de rfrence

Table des matires

1. Structure des rpertoires l'extrieur de l'environnement de base
2. Structure des rpertoires l'intrieur de l'image de base

1.Structure des rpertoires l'extrieur de l'environnement de base

Tableau8.1.Structure des rpertoires l'extrieur de l'environnement de base

RpertoireSignification
/etc/pbuilderrcfichier de configuration
/usr/share/pbuilder/pbuilderrcConfiguration par dfaut
/var/cache/pbuilder/base.tgzEmplacement par dfaut utilis par pbuilder pour le fichier base.tgz -contenant l'environnement de base constitu uniquement des paquets -essentiels pour la construction des paquets. -
/var/cache/pbuilder/build/PID/Emplacement par dfaut utilis pour l'image de base
/var/cache/pbuilder/aptcacheEmplacement par dfaut utilis par pbuilder pour le cache apt pour stocker -les paquets Debian pendant le processus de construction.
/var/cache/pbuilder/ccacheDefault location pbuilder will use as cache location
/var/cache/pbuilder/resultEmplacement par dfaut o pbuilder place les paquets et -les autres fichiers crs aprs la construction
/var/cache/pbuilder/pbuilder-umlresultEmplacement par dfaut o pbuilder-user-mode-linux place -les paquets et les autres fichiers crs aprs la construction
/var/cache/pbuilder/pbuilder-mntEmplacement par dfaut o pbuilder-user-mode-linux monte -le systme de fichiers COW pour l'environnement de base.
/tmppbuilder-user-mode-linux montera le tmpfs ici.
${HOME}/tmp/PID.cowpbuilder-user-mode-linux utilise ce rpertoire comme -emplacement pour le systme de fichiers COW.
${HOME}/uml-imagepbuilder-user-mode-linux utilise ce rpertoire pour -placer l'image disque pour user-mode-linux.

2.Structure des rpertoires l'intrieur de l'image de base

Tableau8.2.Structure des rpertoires l'intrieur de l'image de base

RpertoireSignification
/etc/mtab - Lien symbolique vers /proc/mounts. -
/tmp/builddDefault place used in pbuilder to place the Debian -package to be processed. -/tmp/buildd/packagename-version/ will be the root -directory of the package being processed. HOME environment variable is set -to this value inside chroot by pbuilder-buildpackage. ---inputfile will place files here. -
/runscriptLe script utilis comme argument pour pbuilder execute -est plac ici. -
/tmp/hooks - Emplacement des crochets. -
/var/cache/apt/archives - pbuilder copie le contenu de ce rpertoire depuis et vers -le rpertoire aptcache l'extrieur de l'environnement de base. -
/var/cache/pbuilder/ccache - pbuilder bind-mounts this directory for use by ccache. -
/tmp/XXXXpbuilder-user-mode-linux utilise un script dans -/tmp pour le dmarrage initial dans user-mode-linux

Chapitre9.Quelques dtails archologiques mineurs

Table des matires

1. Historique de la documentation
2. Histoire peut-tre incorrecte de pbuilder
2.1. L'avant pbuilder
2.2. Naissance de pbuilder
2.3. Et la seconde anne de sa vie
2.4. Cinq annes de pbuilder

1.Historique de la documentation

- Ce document a t commenc le 28 dcembre 2002 par Junichi Uekawa qui -essayait de documenter ce qui tait connu propos de -pbuilder. -

- Cette documentation est disponible dans les sources de -pbuilder et depuis le dpt git de -pbuilder (un accs web est possible). Une copie de cette -documentation peut tre trouve sur la page du projet -Alioth pour pbuilder. Il existe une version en -PDF. La page d'accueil pour pbuilder est http://pbuilder.alioth.debain.org/ - hberge par le projet alioth. -

- La documentation est crite avec DocBook XML, en utilisant le mode PSGML -d'Emacs et wysidocbookxml pour la prvisualisation en direct. -

2.Histoire peut-tre incorrecte de pbuilder

- Ce qui suit explique, de manire sans doute incorrecte, comment -pbuilder a vu le jour et les autres tentatives pour -obtenir quelque chose de similaire. Cette partie de la documentation se -trouvait initialement dans le fichier AUTHORS pour citer ceux qui existaient -avant pbuilder. -

2.1.L'avant pbuilder

- Il tait une fois dbuild qui tait un script pour construire des paquets -Debian depuis les sources. Lars Wirzenius a crit ce script qui tait bon, -court et simple (probablement). Il n'y avait rien qui ressemblait aux -dpendances source ( mon avis) et il tait simple. Il aurait pu tre -amlior mais je n'ai trouv que des citations et non le code source. -

- debbuild tait probablement crit par James Troup. Je n'en suis pas sr car -je n'ai jamais trouv le code source. Je n'ai trouv que quelques citations -sur le net et dans les archives des listes de diffusion. -

- sbuild est un script crit en Perl pour construire les paquets Debian depuis -les sources. Il prend en compte les dpendances source et effectue quelques -vrifications supplmentaires et utilise un grand nombre d'astuces pour -russir construire les paquets, y compris une table de correspondance -entre les paquets virtuels et les paquets effectivement installer. Il -permet galement l'utilisation d'une base locale de paquets qui n'ont pas de -dpendances source. Il a t crit par Ronan Hodek et je suppose qu'il a t -corrig et amlior par de nombreuses personnes. Il fait partie de -wanna-build et tait trs utilis dans le systme de construction -automatique buildd de Debian. Je crois qu'il tait maintenu principalement -par Ryan Murray. -

2.2.Naissance de pbuilder

- wanna-build (sbuild) tait (en 2001) particulirement difficile configurer -et il n'est jamais devenu un paquet Debian. dbuild a permis de promouvoir -l'usage des dpendances source. -

- Construire des paquets depuis les sources en respectant les dpendances -source semblait trivial et pbuilder est n. C'tait -initialement un script shell de seulement quelques lignes qui appelait -debootstrap, chroot et dpkg-buildpackage chaque excution. Mais il a t -rapidement dcid que cette approche tait trop lente. -

- Yes, and it took almost an year to get things somewhat right, and in the -middle of the process, Debian 3.0 was released. Yay. Debian 3.0 wasn't -completely buildable with pbuilder, but the amount of -packages which are not buildable is steadily decreasing (I hope). -

2.3.Et la seconde anne de sa vie

- Quelqu'un voulait que pbuilder ne soit pas lanc sous -l'utilisateur root et j'ai commenc jouer avec -pbuilder-user-mode-linux. Ce dernier n'est pas rest -aussi fonctionnel que je l'aurais voulu et construire l'environnement -user-mode-linux tait trs difficile en raison de la -qualit du code de user-mode-linux ainsi que son empaquetage. Rgulirement, -le support du rseau tait cass d'une faon ou d'une autre. -

2.4.Cinq annes de pbuilder

- pbuilder est maintenant largement adopt comme un outil -quasi standard pour tester les paquets et construire les paquets dans un -environnement minimal. Il existe d'autres outils pour effectuer des tches -similaires mais ils n'ont pas exactement le mme but. En mmoire, -pbuilder est dsormais co-maintenu par plusieurs -personnes. -

- sbuild est maintenant un paquet Debian bien maintenu. En -raison de la lenteur de pbuilder, certaines personnes -prfrent l'approche de sbuild. Les dveloppements visant utilisant les -instantans LVM, cowloop ou cowdancer permettront sans doute d'amliorer -cette situation. -

diff -Nru pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.html pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.html --- pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.html 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.html 1970-01-01 00:00:00.000000000 +0000 @@ -1,1069 +0,0 @@ -pbuilder User's Manual

pbuilder User's Manual

Usage and operations

Junichi Uekawa

documentation in progress

Table of Contents

1. Introducing pbuilder
1. Aims of pbuilder
2. Using pbuilder
1. Creating a base chroot image tar-ball
2. Updating the base.tgz
3. Building a package using the base.tgz
4. Facilitating Debian Developers' typing, pdebuild
5. Configuration Files
6. Building packages as non-root inside the chroot
7. Using pbuilder for back-porting
8. Mass-building packages
9. Auto-backporting scripts
10. Using pbuilder for automated testing of packages
11. Using pbuilder for testing builds with alternate compilers
3. Using User-mode-linux with pbuilder
1. Configuring user-mode-linux
2. Configuring rootstrap
3. Configuring pbuilder-uml
4. Considerations for running pbuilder-user-mode-linux
5. Parallel running of pbuilder-user-mode-linux
6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine
4. Frequently asked questions
1. pbuilder create fails
2. Directories that cannot be bind-mounted
3. Logging in to pbuilder to investigate build failure
4. Logging in to pbuilder to modify the environment
5. Setting BUILDRESULTUID for sudo sessions
6. Notes on usage of $TMPDIR
7. Creating a shortcut for running pbuilder with a specific distribution
8. Using environmental variables for running pbuilder - for specific distribution -
9. Using special apt sources lists, and local packages
10. How to get pbuilder to run apt-get update before trying to satisfy build-dependency
11. Different bash prompts inside pbuilder login
12. Creating a chroot reminder
13. Using /var/cache/apt/archives for the package cache
14. pbuilder back ported to stable Debian releases
15. Warning about LOGNAME not being defined
16. Cannot Build-conflict against an essential package
17. Avoiding the "ln: Invalid cross-device link" message
18. Using fakechroot
19. Using debconf inside pbuilder sessions
20. nodev mount options hinder pbuilder activity
21. pbuilder is slow
22. Using pdebuild to sponsor package
23. Why is there a source.changes file in ../?
24. amd64 and i386-mode
25. Using tmpfs for buildplace
26. Using svn-buildpackage together with pbuilder
5. Troubleshooting and development
1. Reporting bugs
2. Mailing list
3. IRC Channel
4. Information for pbuilder developers
6. Other uses of pbuilder
1. Using pbuilder for small experiments
2. Running little programs inside the chroot
7. Experimental or wishlist features of pbuilder
1. Using LVM
2. Using cowdancer
3. Using pbuilder without tar.gz
4. Using pbuilder in a vserver
5. Usage of ccache
8. Reference materials
1. Directory structure outside the chroot
2. Directory structure inside the chroot
9. Minor archaeological details
1. Documentation history
2. Possibly inaccurate Background History of pbuilder
2.1. The Time Before pbuilder
2.2. Birth of pbuilder
2.3. And the second year of its life
2.4. Fifth year of pbuilder

List of Tables

5.1. Directory structure of the testsuite
8.1. Directory Structure outside the chroot
8.2. Directory Structure inside the chroot

Chapter1.Introducing pbuilder

Table of Contents

1. Aims of pbuilder

1.Aims of pbuilder

- pbuilder stands for - Personal Builder, and it is an automatic Debian Package Building system - for personal development workstation environments. - pbuilder aims to be an - easy-to-setup system - for auto-building Debian packages inside a clean-room - environment, so that it is possible to verify that - a package can be built on most Debian installations. - The clean-room environment is achieved through the use of - a base chroot image, - so that only minimal packages will be installed inside the - chroot. -

- The Debian distribution consists of free software - accompanied with source. - The source code within Debian's "main" section - must build within Debian "main", - with only the explicitly specified build-dependencies - installed. -

- The primary aim of pbuilder is different from other - auto-building systems in Debian in that its aim is not - to try to build as many packages as possible. - It does not try to guess - what a package needs, and in most cases it tries the - worst choice of all if there is a choice to be made. -

- In this way, pbuilder tries to ensure - that packages - tested against pbuilder will build properly in - most Debian installations, hopefully resulting - in a good overall Debian source-buildability. -

- The goal of making Debian buildable from source is somewhat - accomplished, and has seen good progress. In the past age of - Debian 3.0, there were many problems when building from - source. More recent versions of Debian is much better. -

Chapter2.Using pbuilder

Table of Contents

1. Creating a base chroot image tar-ball
2. Updating the base.tgz
3. Building a package using the base.tgz
4. Facilitating Debian Developers' typing, pdebuild
5. Configuration Files
6. Building packages as non-root inside the chroot
7. Using pbuilder for back-porting
8. Mass-building packages
9. Auto-backporting scripts
10. Using pbuilder for automated testing of packages
11. Using pbuilder for testing builds with alternate compilers

- There are several simple commands for operation. - pbuilder create, pbuilder - update, and pbuilder build commands - are the typical commands used. Let us look at the commands - one by one. -

1.Creating a base chroot image tar-ball

- pbuilder create - will create a base chroot image tar-ball (base.tgz). - All other commands will operate on the resulting base.tgz - - If the Debian release to be created within chroot is not going - to be "sid" (which is the default), the distribution code-name - needs to be specified with the - --distribution - command-line option. -

- debootstrap [1] - is used to create - the bare minimum Debian installation, - and then build-essential packages are installed on top - of the minimum installation using apt-get - inside the chroot. -

- For fuller documentation of command-line options, see - the pbuilder.8 manual page. - Some configuration will be required for /etc/pbuilderrc - for the mirror site - [2] - to use, and proxy configuration may be required to allow access - through HTTP. - See the pbuilderrc.5 manual page for details. -

2.Updating the base.tgz

pbuilder update - will update the base.tgz. - It will extract the chroot, invoke apt-get update - and apt-get dist-upgrade inside the - chroot, and then recreate the base.tgz (the base tar-ball). -

- It is possible to switch the distribution which the - base.tgz is targeted at at this point. - Specify --distribution sid --override-config to change the distribution - to sid. - [3] -

- For fuller documentation of command-line options, see - the pbuilder.8 manual page -

3.Building a package using the base.tgz

- To build a package inside the chroot, invoke - pbuilder build whatever.dsc. - pbuilder will extract - the base.tgz to a temporary working directory, - enter the directory with chroot, - satisfy the build-dependencies inside chroot, - and build the package. - The built packages will be moved to a - directory specified with - the --buildresult - command-line option. -

- The --basetgz option can be - used to specify which base.tgz to use. -

- pbuilder will extract a fresh base chroot - image from base.tgz. (base.tgz is created with - pbuilder create, and updated with - pbuilder update). The chroot is populated - with build-dependencies by parsing debian/control and invoking - apt-get. -

- For fuller documentation of command-line options, see - the pbuilder.8 manual page -

4.Facilitating Debian Developers' typing, pdebuild

- pdebuild is a little wrapper - script that does the most frequent of all tasks. - A Debian Developer may try to do debuild, and - build a package, inside a Debian source directory. - pdebuild will allow similar - control, and allow package to be built inside the chroot, - to check that the current source tree will build happily - inside the chroot. -

- pdebuild calls dpkg-source - to build the source packages, and then invokes - pbuilder on the resulting source package. - However, unlike debuild, the resulting deb files will be - found in the --buildresult - directory. -

- See the pdebuild.1 manual page for more details. -

- There is a slightly different mode of operation available - in pdebuild since version 0.97. pdebuild usually runs - debian/rules clean outside of the chroot; - however, it is possible to change the behavior to run it - inside the chroot with - the --use-pdebuild-internal. - It will try to bind mount the working directory inside chroot, - and run dpkg-buildpackage inside. - It has the following characteristics, and is not yet the - default mode of operation. -

  • - Satisfies build-dependency inside the chroot before creating source package. - (which is a good point that default pdebuild could not do). -

  • The working directory is modified - from inside the chroot.

  • Building with pdebuild does not guarantee - that it works with pbuilder.

  • If making the source package fails, - the session using the chroot is wasted - (chroot creation takes a bit of time, which should be improved with cowdancer).

  • Does not work in the same manner as it used to; - for example, --buildresult - does not have any effect.

  • The build inside chroot is ran with the current user outside chroot. -

5.Configuration Files

- It is possible to specify all settings by command-line - options. However, for typing convenience, it is possible to - use a configuration file. -

- /etc/pbuilderrc and - ${HOME}/.pbuilderrc - are read in when pbuilder is invoked. - The possible options are documented in - the pbuilderrc.5 manual page. -

- It is useful to use --configfile option to load up a preset - configuration file when switching between configuration files for - different distributions. -

- Please note ${HOME}/.pbuilderrc supersede - system settings. Caveats is that if you have some - configuration, you may need to tweak the configuration to work - with new versions of pbuilder when upgrading. -

6.Building packages as non-root inside the chroot

- pbuilder requires full root privilege - when it is satisfying the build-dependencies, but most packages do not - need root privilege to build, or even refused to build when they are built as root. - pbuilder can create a user which is only used - inside pbuilder and use that user id when - building, and use the fakeroot command - when root privilege is required. -

- BUILDUSERID configuration option should be set to a value for a user id that - does not already exist on the system, so that it is more difficult for - packages that are being built with - pbuilder to affect the environment outside the chroot. - When BUILDUSERNAME configuration option is also set, - pbuilder will use the specified user name and fakeroot for building packages, - instead of running as root inside chroot. -

- Even when using the fakerooting method, pbuilder will run with - root privilege when it is required. - For example, when installing - packages to the chroot, pbuilder will run under root privilege. -

- To be able to invoke pbuilder without being - root, you need to use user-mode-linux, as explained - in Chapter3, Using User-mode-linux with pbuilder. -

7.Using pbuilder for back-porting

- pbuilder can be used for back-porting software from - the latest Debian distribution to - the older stable distribution, by using a chroot that contains - an image of the older distribution, and building packages inside the - chroot. - There are several points to consider, and due to the following reasons, - automatic back-porting is usually not possible, and - manual interaction is required: -

  • The package from the unstable distribution - may depend on packages or versions of packages which - are only available in unstable. - Thus, it may not be possible to satisfy Build-Depends: - on stable (without additional backporting work).

  • The stable distribution may have bugs that have been - fixed in unstable which need to be worked around.

  • The package in the unstable distribution may have - problems building even on unstable.

8.Mass-building packages

- pbuilder can be automated, because its operations are - non-interactive. - It is possible to run pbuilder through multiple packages - non-interactively. - Several such scripts are known to exist. - Junichi Uekawa has been running such a script since 2001, - and has been filing bugs on packages that fail the - test of pbuilder. There were several problems with auto-building: -

  • Build-Dependencies need to install non-interactively, but - some packages are so broken that they cannot install - without interaction (like postgresql).

  • When a library package breaks, or gcc/gcj/g++ breaks, - or even bison, a large number of build failures are reported. - (gcj-3.0 which had no "javac", bison which got more strict, etc.) -

  • Some people were quite hostile against build failure reports.

- Most of the initial bugs have been resolved in the pbuilder - sweep done around 2002, but these transitional problems which - affect a large portion of Debian Archive do arise from time to - time. Regression tests have their values. -

- A script that was used by Junichi Uekawa in the initial run is now included in - the pbuilder distribution, as pbuildd.sh. - It is available in /usr/share/doc/pbuilder/examples/pbuildd/ - and its configuration is in /etc/pbuilder/pbuildd-config.sh. - It should be easy enough to set up for people who are used to - pbuilder. It has been running for quite a while, and it should be - possible to set the application up on your system also. - This version of the code is not the most tested, but should function as a starter. -

- To set up pbuildd, there are some points to be aware of. -

  • A file ./avoidlist needs to be available with the list of packages to avoid building.

  • It will try building anything, even packages - which are not aimed for your architecture.

  • Because you are running random build scripts, it is better to use - the fakeroot option of pbuilder, to avoid running the build - under root privilege.

  • Because not all builds are guaranteed to finish in a finite time, - setting a timeout is probably necessary, or pbuildd may stall with - a bad build.

  • - Some packages require a lot of disk space, - around 2GB seems to be sufficient for the largest packages for the time being. - If you find otherwise, please inform the maintainer of this documentation. -

9.Auto-backporting scripts

- There are some people who use pbuilder to automatically back-port - a subset of packages to the stable distribution. -

- I would like some information on how people are doing it, - I would appreciate any feedback or information on - how you are doing, or any examples. -

10.Using pbuilder for automated testing of packages

- pbuilder can be used for automated testing of packages. - It has the feature of allowing hooks to be placed, - and these hooks can try to install packages inside - the chroot, or run them, or whatever else that - can be done. Some known tests and ideas: -

  • Automatic install-remove-install-purge-upgrade-remove-upgrade-purge test-suite (distributed as an example, B91dpkg-i), - or just check that everything installs somewhat (execute_installtest.sh).

  • Automatically running lintian (distributed as an example in - /usr/share/doc/pbuilder/examples/B90lintian).

  • Automatic debian-test of the package? - The debian-test package has been removed from Debian. - A pbuilder implementation can be found as - debian/pbuilder-test directory, implemented through B92test-pkg script.

- To use B92test-pkg script, first, add it to your hook directory. - [4]. - The test files are shell scripts - placed in - debian/pbuilder-test/NN_name (where - NN is a number) following run-parts standard[5] - for file names. After a successful build, packages are first - tested for installation and removal, and then each test is ran - inside the chroot. The current directory is the top directory - of the source-code. This means you can expect to be able to - use ./debian/ directory from inside your scripts. -

- Example scripts for use with pbuilder-test can be found in - /usr/share/doc/pbuilder/examples/pbuilder-test. -

11.Using pbuilder for testing builds with alternate compilers

- Most packages are compiled with gcc - or g++ - and using the default compiler version, which was gcc 2.95 for Debian GNU/Linux 3.0 (i386). - However, Debian 3.0 was distributed with other compilers, under package names - such as gcc-3.2 for gcc compiler - version 3.2. - It was therefore possible to try compiling packages against different - compiler versions. - pentium-builder provides an infrastructure for - using a different compiler for building packages than the default gcc, by - providing a wrapper script called gcc which calls the real gcc. - To use pentium-builder in pbuilder, it is possible to set up the - following in the configuration: - 

-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2

-

- It will instruct pbuilder to install the pentium-builder package - and also the GCC 3.2 compiler packages inside the chroot, - and set the environment variables required for - pentium-builder to function. -


[1] debootstrap or cdebootstrap can be chosen

[2] - The mirror site should preferably be - a local mirror or a cache server, - so as not to overload the public mirrors with - a lot of access. - Use of tools such as apt-proxy would be advisable. -

[3] Only upgrading is supported. - Debian does not generally support downgrading (yet?).

[4] It is possible to specify --hookdir - /usr/share/doc/pbuilder/examples command-line - option to include all example hooks as - well.

[5] See run-parts(8). For example, no '.' in file - names! -

Chapter3.Using User-mode-linux with pbuilder

Table of Contents

1. Configuring user-mode-linux
2. Configuring rootstrap
3. Configuring pbuilder-uml
4. Considerations for running pbuilder-user-mode-linux
5. Parallel running of pbuilder-user-mode-linux
6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine

- It is possible to use user-mode-linux by invoking - pbuilder-user-mode-linux instead of - pbuilder. - pbuilder-user-mode-linux doesn't require root - privileges, and it uses the copy-on-write (COW) disk access - method of User-mode-linux which typically - makes it much faster than the traditional - pbuilder. -

- User-mode-linux is a somewhat less proven - platform than the standard Unix tools which - pbuilder relies on - (chroot, tar, and - gzip) but mature enough to support - pbuilder-user-mode-linux since its version - 0.59. And since then, - pbuilder-user-mode-linux has seen a rapid - evolution. -

- The configuration of pbuilder-user-mode-linux - goes in three steps: -

  • Configuration of user-mode-linux

  • Configuration of rootstrap

  • Configuration of pbuilder-uml

-

1.Configuring user-mode-linux

- user-mode-linux isn't completely trivial to set up. It would - probably be useful to acquaint yourself with it a bit before - attempting to use rootstrap or - pbuilder-user-mode-linux. For details, - read - /usr/share/doc/uml-utilities/README.Debian - and the user-mode-linux documentation. (It's in a separate - package, user-mode-linux-doc.) -

- user-mode-linux requires - the user to be in the uml-net group in order to configure the network - unless you are using slirp. -

- If you compile your own kernel, you may want to - verify that you enable TUN/TAP support, - and you might want to consider the SKAS patch. -

2.Configuring rootstrap

- rootstrap - is a wrapper around debootstrap. - It creates a Debian disk image for use with UML. - To configure rootstrap, there are several requirements. -

  • Install the rootstrap package.

  • - TUN/TAP only: - add the user to the uml-net group to allow access to the network - 

    adduser dancer uml-net

    -

  • TUN/TAP only: - Check that the kernel supports the TUN/TAP interface, - or recompile the kernel if necessary. -

  • Set up /etc/rootstrap/rootstrap.conf. - For example, - if the current host is 192.168.1.2, changing following - entries to something like this seems to work. - 

    -transport=tuntap
-interface=eth0
-gateway=192.168.1.1
-mirror=http://192.168.1.2:8081/debian
-host=192.168.1.198
-uml=192.168.1.199
-netmask=255.255.255.0

    - Some experimentation with configuration and running - rootstrap ~/test.uml to actually - test it would be handy. -

    - Using slirp requires less configuration. - The default configuration comes with a working example. -

3.Configuring pbuilder-uml

- The following needs to happen: -

  • Install the pbuilder-uml package.

  • - Set up the configuration file - /etc/pbuilder/pbuilder-uml.conf - in the following manner. It will be different for slirp. - 

    -MY_ETH0=tuntap,,,192.168.1.198
-UML_IP=192.168.1.199
-UML_NETMASK=255.255.255.0
-UML_NETWORK=192.168.1.0
-UML_BROADCAST=255.255.255.255
-UML_GATEWAY=192.168.1.1
-PBUILDER_UML_IMAGE="/home/dancer/uml-image"

    - Also, it needs to match the rootstrap configuration. -

  • - Make sure BUILDPLACE is writable by the user. - Change BUILDPLACE in the configuration file to a place - where the user has access. -

  • Run pbuilder-user-mode-linux create --distribution sid to create the image.

  • Try running pbuilder-user-mode-linux build.

-

4.Considerations for running pbuilder-user-mode-linux

- pbuilder-user-mode-linux emulates most of pbuilder, but there - are some differences. -

  • - pbuilder-user-mode-linux does not support all options of pbuilder - properly yet. This is a problem, and will be addressed as - specific areas are discovered. -

  • - /tmp is handled differently inside - pbuilder-user-mode-linux. In - pbuilder-user-mode-linux, - /tmp is mounted as tmpfs inside UML, - so accessing files under /tmp from - outside user-mode-linux does not work. It affects options - like --configfile, and - when trying to build packages placed under - /tmp. -

5.Parallel running of pbuilder-user-mode-linux

- To run pbuilder-user-mode-linux in parallel - on a system, there are a few things to bear in mind. -

  • The create and update methods must not be run when - a build is in progress, or the COW file will be invalidated.

  • - If you are not using slirp, user-mode-linux processes which are - running in parallel need to have different IP addresses. - Just trying to run the pbuilder-user-mode-linux - several times will result in failure to access the network. - But something like the following will work: - 

    -for IP in 102 103 104 105; do
-  xterm -e pbuilder-user-mode-linux build --uml-ip 192.168.0.$IP \
-    20030107/whizzytex_1.1.1-1.dsc &
-done

    - When using slirp, this problem does not exist. -

6.Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine

- It is possible to use - pbuilder-user-mode-linux for other uses - than just building Debian packages. - pbuilder-user-mode-linux - login will let a user use a shell - inside the user-mode-linux pbuilder base - image, and pbuilder-user-mode-linux - execute will allow the user to - execute a script inside the image. -

- You can use the script to install ssh and add a new user, - so that it is possible to access inside the user-mode-linux through ssh. -

- Note that it is not possible to use a script from - /tmp due to the way - pbuilder-user-mode-linux mounts a tmpfs at - /tmp. -

- The following example script may be useful in starting a sshd - inside user-mode-linux. - 

-#!/bin/bash
-
-apt-get install -y ssh xbase-clients xterm
-echo "enter root password"
-passwd
-cp /etc/ssh/sshd_config{,-}
-sed 's/X11Forwarding.*/X11Forwarding yes/' /etc/ssh/sshd_config- > /etc/ssh/sshd_config
-
-/etc/init.d/ssh restart
-ifconfig
-echo "Hit enter to finish"
-read

Chapter4.Frequently asked questions

Table of Contents

1. pbuilder create fails
2. Directories that cannot be bind-mounted
3. Logging in to pbuilder to investigate build failure
4. Logging in to pbuilder to modify the environment
5. Setting BUILDRESULTUID for sudo sessions
6. Notes on usage of $TMPDIR
7. Creating a shortcut for running pbuilder with a specific distribution
8. Using environmental variables for running pbuilder - for specific distribution -
9. Using special apt sources lists, and local packages
10. How to get pbuilder to run apt-get update before trying to satisfy build-dependency
11. Different bash prompts inside pbuilder login
12. Creating a chroot reminder
13. Using /var/cache/apt/archives for the package cache
14. pbuilder back ported to stable Debian releases
15. Warning about LOGNAME not being defined
16. Cannot Build-conflict against an essential package
17. Avoiding the "ln: Invalid cross-device link" message
18. Using fakechroot
19. Using debconf inside pbuilder sessions
20. nodev mount options hinder pbuilder activity
21. pbuilder is slow
22. Using pdebuild to sponsor package
23. Why is there a source.changes file in ../?
24. amd64 and i386-mode
25. Using tmpfs for buildplace
26. Using svn-buildpackage together with pbuilder

- Here, known problems and frequently asked questions are - documented. This portion was initially available in README.Debian - file, but moved here. -

1.pbuilder create fails

- It often happens that pbuilder cannot create the latest chroot. - Try upgrading pbuilder and debootstrap. - It is currently only possible to create software that handles the - past. Future prediction is a feature which may be added later after - we have become comfortable with the past. -

- There are people who occasionally back port debootstrap to stable - versions; hunt for them. -

- When there are errors with the debootstrap phase, - the debootstrap script needs to be fixed. - pbuilder does not provide a way to work around debootstrap. -

2.Directories that cannot be bind-mounted

- Because of the way pbuilder works, there - are several directories which cannot be bind-mounted when - running pbuilder. The directories include - /tmp, - /var/cache/pbuilder, and system - directories such as /etc and - /usr. The recommendation is to use - directories under the user's home directory for bind-mounts. -

3.Logging in to pbuilder to investigate build failure

- It is possible to invoke a shell session after a build - failure. Example hook scripts are provided as - C10shell and - C11screen scripts. C10shell script will - start bash inside chroot, and C11screen script will start GNU - screen inside the chroot. -

4.Logging in to pbuilder to modify the environment

- It is sometimes necessary to modify the chroot environment. - login will remove the contents of the chroot after logout. - It is possible to invoke a shell using hook scripts. - pbuilder update executes 'E' scripts, - and a sample for invoking a shell - is provided as C10shell. - 

-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell

- It is also possible to add --save-after-exec - and/or --save-after-login options - to the pbuilder login session - to accomplish the goal. - It is possible to add the --uml-login-nocow option - to pbuilder-user-mode-linux login session - as well. -

5.Setting BUILDRESULTUID for sudo sessions

- It is possible to set - 

BUILDRESULTUID=$SUDO_UID

in pbuilderrc to set - the proper BUILDRESULTUID when using sudo. -

6.Notes on usage of $TMPDIR

- If you are setting $TMPDIR to an unusual value, of other than - /tmp, you will find that some errors may occur inside the chroot, - such as dpkg-source failing. -

There are two options, you may install a hook to create that - directory, or set - 

export TMPDIR=/tmp

- in pbuilderrc. Take your pick. -

- An example script is provided as - examples/D10tmp with pbuilder. -

7.Creating a shortcut for running pbuilder with a specific distribution

- When working with multiple chroots, it would be nice to work - with scripts that reduce the amount of typing. An example - script pbuilder-distribution.sh is - provided as an example. Invoking the script as - pbuilder-squeeze will invoke - pbuilder with a squeeze chroot. -

8.Using environmental variables for running pbuilder - for specific distribution -

This section[6] - describes briefly a way to setup and use multiple pbuilder setups - by creating a pbuilderrc configuration in your home path ($HOME/.pbuilderrc) - and using the variable "DIST" when running pbuilder or pdebuild. -

First, setup $HOME/.pbuilderrc to look like:

- 

-if [ -n "${DIST}" ]; then
-        BASETGZ="`dirname $BASETGZ`/$DIST-base.tgz"
-        DISTRIBUTION="$DIST"
-        BUILDRESULT="/var/cache/pbuilder/$DIST/result/"
-        APTCACHE="/var/cache/pbuilder/$DIST/aptcache/"
-fi
-

Then, whenever you wish to use pbuilder for a particular distro, assign a value -to "DIST" that is one of the distros available for Debian or any Debian based -distro you happen to be running (i.e. whatever is found under -/usr/lib/debootstrap/scripts). -

Here's some examples on running pbuilder or pdebuild: -

-DIST=gutsy sudo pbuilder create
-
-DIST=sid sudo pbuilder create --mirror http://http.us.debian.org/debian
-
-DIST=gutsy sudo pbuilder create \
-        --othermirror "deb http://archive.ubuntu.com/ubuntu gutsy universe \
-        multiverse"
-
-DIST=gutsy sudo pbuilder update
-
-DIST=sid sudo pbuilder update --override-config --mirror \
-http://http.us.debian.org/debian \
---othermirror "deb http://http.us.debian.org/debian sid contrib non-free"
-
-DIST=gutsy pdebuild
-

9.Using special apt sources lists, and local packages

- If you have some very specialized requirements on your - apt setup inside pbuilder, - it is possible to specify that through - the --othermirror - option. - Try something like: - --othermirror "deb http://local/mirror stable main|deb-src http://local/source/repository ./" -

- To use the local file system instead of HTTP, it is necessary to do - bind-mounting. - --bindmounts - is a command-line option useful for such cases. -

- It might be convenient to use your built packages from inside the chroot. - It is possible to automate the task with the following configuration. - First, set up pbuilderrc to bindmount your build results directory. -

- 

BINDMOUNTS="/var/cache/pbuilder/result"

-

- Then, add the following hook -

- 

-# cat /var/cache/pbuilder/hooks/D70results
-#!/bin/sh
-cd /var/cache/pbuilder/result/
-/usr/bin/dpkg-scanpackages . /dev/null > /var/cache/pbuilder/result/Packages
-/usr/bin/apt-get update

-

- This way, you can use deb file:/var/cache/pbuilder/result -

- To add new apt-key inside chroot: - -

- 

-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-

10.How to get pbuilder to run apt-get update before trying to satisfy build-dependency

- You can use hook scripts for this. - D scripts are run before satisfying build-dependency. -

- - This snippet comes from Ondrej Sury. - -

11.Different bash prompts inside pbuilder login

- To make distinguishing bash prompts inside - pbuilder easier, it is possible to set - environment variables such as PS1 inside - pbuilderrc -

- With versions of bash more recent than 2.05b-2-15, - the value of the debian_chroot variable, if set, - is included in the value of PS1 (the Bash prompt) - inside the chroot. - In prior versions of bash,[7] - setting PS1 in pbuilderrc worked. -

example of debian_chroot

-	export debian_chroot="pbuild$$"

example of PS1

-	export PS1="pbuild chroot 32165 # "

12.Creating a chroot reminder

- Bash prompts will help you remember that you are inside a - chroot. There are other cases where you may want other signs - of being inside a chroot. Check out the - examples/F90chrootmemo hook script. It - will create a file called /CHROOT inside - your chroot. -

13.Using /var/cache/apt/archives for the package cache

- For the help of low-bandwidth systems, it is possible to use - /var/cache/apt/archives as the package - cache. Just specify it instead of the default - /var/cache/pbuilder/aptcache. -

- It is however not possible to do so currently with the - user-mode-linux version of pbuilder, - because /var/cache/apt/archives is - usually only writable by root. -

- Use of dedicated tools such as apt-proxy is recommended, since - caching of packages would benefit the system outside the scope - of pbuilder. -

14.pbuilder back ported to stable Debian releases

- Currently stable back port of pbuilder is available at backports.org. -

15.Warning about LOGNAME not being defined

- You might see a lot of warning messages when running pbuilder. -

- 

-	dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)

-

- It is currently safe to ignore this warning message. Please - report back if you find any problem with having LOGNAME unset. - Setting LOGNAME caused a few problems when invoking - chroot. For example, dpkg requires getpwnam - to succeed inside chroot, which means LOGNAME and the related - user information have to be set up inside chroot. -

16.Cannot Build-conflict against an essential package

- pbuilder does not currently allow Build-Conflicts against - essential packages. - It should be obvious that essential packages should not be - removed from a working Debian system, and a source - package should not try to force removal of such packages - on people building the package. -

17.Avoiding the "ln: Invalid cross-device link" message

- By default, pbuilder uses hard links to - manage the pbuilder package cache. It is - not possible to make hard links across different devices; and - thus this error will occur, depending on your set up. If this - happens, set 

APTCACHEHARDLINK=no

in your - pbuilderrc file. Note that packages in - APTCACHE will be copied into chroot local - cache, so plan for enough space on - BUILDPLACE device. -

18.Using fakechroot

- It is possible to use fakechroot instead of - being root to run pbuilder; however, - several things make this impractical. - fakechroot overrides library loads and - tries to override default libc functions when providing the - functionality of virtual chroot. However, - some binaries do no use libc to function, or override the - overriding provided by fakechroot. One - example is ldd. Inside - fakechroot, ldd will - check the library dependency outside of the chroot, which is - not the expected behavior. -

- To work around the problem, debootstrap has a - --variant fakechroot option. Use that, so - that ldd and ldconfig are overridden. -

- Make sure you have set your LD_PRELOAD path correctly, as described in - the fakechroot manpage. -

19.Using debconf inside pbuilder sessions

- To use debconf inside pbuilder, setting DEBIAN_FRONTEND to - “readline” in pbuilderrc should work. - Setting it to “dialog” should also work, but make sure - whiptail or dialog is installed inside the chroot. -

20.nodev mount options hinder pbuilder activity

- If you see messages such as this when building a chroot, you are mounting the file system with - the nodev option. - 

-	/var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied

- You will also have problems if you mount the file system with - the noexec option, or nosuid. - Make sure you do not have these flags set when mounting the file system for - /var/cache/pbuilder or $BUILDPLACE. -

- This is not a problem when using user-mode-linux. -

- See - 316135 - for example. -

21.pbuilder is slow

- pbuilder is often slow. The slowest part of - pbuilder is extracting the tar.gz every - time pbuilder is invoked. That can be - avoided by using pbuilder-user-mode-linux. - pbuilder-user-mode-linux uses COW file - system, and thus does not need to clean up and recreate the - root file system. -

- pbuilder-user-mode-linux is slower in - executing the actual build system, due to the usual - user-mode-linux overhead for system - calls. It is more friendly to the hard drive. -

- pbuilder with cowdancer is also an - alternative that improves speed of pbuilder startup. -

22.Using pdebuild to sponsor package

- To sign a package marking for sponsorship, it is possible to - use --auto-debsign and - --debsign-k options of - pdebuild. - 

-	pdebuild  --auto-debsign  --debsign-k XXXXXXXX

23.Why is there a source.changes file in ../?

- When running pdebuild, pbuilder will run dpkg-buildpackage to create a - Debian source package to pass it on to pbuilder. - File named XXXX_YYY_source.changes is what remains from that process. - It is harmless unless you try to upload it to the Debian archive. -

- This behavior is different when running through --use-pdebuild-internal -

24.amd64 and i386-mode

- amd64 architectures are capable of running binaries in i386 - mode. It is possible to use pbuilder to - run packages, using linux32 and - debootstrap --arch option. - Specifically, a command-line option like the following will - work. -

- 

-pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
-  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian
-linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz

-

25.Using tmpfs for buildplace

- To improve speed of operation, it is possible to use tmpfs for - pbuilder build location. Mount tmpfs to - /var/cache/pbuilder/build, and set - 

APTCACHEHARDLINK=no

. -

26.Using svn-buildpackage together with pbuilder

- pdebuild command can be used with svn-buildpackage - --svn-builder command-line option. - [8] - 

-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"

[6] This part of the documentation contributed by Andres Mejia

- This example was taken from a wiki (https://wiki.ubuntu.com/PbuilderHowto). -

[7] Versions of bash from and before Debian 3.0

[8] - Zack has posted an example on his blog. -

Chapter5.Troubleshooting and development

Table of Contents

1. Reporting bugs
2. Mailing list
3. IRC Channel
4. Information for pbuilder developers

1.Reporting bugs

- To report bugs, it would be important to have a log of what's - going wrong. Most of the time, adding a - --debug option and - re-running the session should do the trick. Please send the - log of such session along with your problem to ease the - debugging process. -

2.Mailing list

- There is a mailing list for pbuilder on - alioth (pbuilder-maint@lists.alioth.debian.org). You can - subscribe through the alioth web interface. - - http://alioth.debian.org/mail/?group_id=30778. -

3.IRC Channel

- For coordination and communication, - IRC channel #pbuilder on irc.oftc.net is used. - Please log your intent there when you are going to - start doing some changes and committing some change. -

4.Information for pbuilder developers

- This section tries to document current development practices - and how things generally operate in development. -

- pbuilder is co-maintained with resources - provided by Alioth. - - There is an Alioth project page at - - http://alioth.debian.org/projects/pbuilder. - Home page is also available, - at - http://alioth.debian.org/projects/pbuilder - which shows this text. - git repository is available through http, git, or (if you have an - account on alioth, ) ssh. - 

-git-clone git://git.debian.org/git/pbuilder/pbuilder.git
-git-clone http://git.debian.org/git/pbuilder/pbuilder.git
-git-clone ssh://git.debian.org/git/pbuilder/pbuilder.git

- Git commit message should have the first one line describing - what the commit does, formatted in the way debian/changelog is - formatted because it is copied verbatim to changelog via - git-dch. The second line is empty, and the rest should - describe the background and extra information related to - implementation of the commit. -

- Test-suites are available in ./testsuite/ directory. - Changes are expected not to break the test-suites. - ./run-test.sh is a basic test-suite, which puts a summary in - run-test.log, and run-test-cdebootstrap.log. - ./run-test-regression.sh is a regression test-suite, - which puts the result in run-test-regression.log. - Currently, run-test.sh is ran automatically daily to ensure that pbuilder is working. -

Table5.1.Directory structure of the testsuite

DirectoryMeaning
./testsuite/Directory for testsuite
./testsuite/run-test.shDaily regression test to test against Debian Archive changes breaking pbuilder.
./testsuite/run-test.logA summary of testsuite
./testsuite/normal/Directory for testsuite results of running pbuilder with debootstrap
./testsuite/cdebootstrap/Directory for testsuite results of running pbuilder with cdebootstrap
./testsuite/run-regression.shRegression testsuite, ran every time change is made to pbuilder to make sure there is no regression.
./testsuite/run-regression.logSummary of test result
./testsuite/regression/BugID-*.shRegression tests, exit 0 for success, exit 1 for failure
./testsuite/regression/BugID-*Files used for the regression testsuite.
./testsuite/regression/log/BugID-*.sh.logOutput of the regression test, output from the script is redirected by run-regression.sh

- When making changes, changes should be documented in the Git - commit log. git-dch will generate debian/changelog from the - commit log. Make the first line of your commit log meaningful, - and add any bug-closing information available. - debian/changelog should not be edited directly unless when - releasing a new version. -

- A TODO file is available in debian/TODO. - It's mostly not well-maintained, but hopefully it will be more - up-to-date when people start using it. emacs todoo-mode is - used in editing the file. -

- When releasing a new version of pbuilder, - the version is tagged with the git tag - X.XXX (version number). - This is done with ./git-tag.sh script available in the source tree. -

Chapter6.Other uses of pbuilder

Table of Contents

1. Using pbuilder for small experiments
2. Running little programs inside the chroot

1.Using pbuilder for small experiments

- There are cases when some small experimenting is required, and - you do not want to damage the main system, - like when installing experimental library packages, - or compiling with experimental compilers. - For such cases, the pbuilder login command is available. -

- pbuilder login is a debugging feature for - pbuilder itself, but it also allows users to have a temporary chroot. -

- Note that the chroot is cleaned after logging out of the shell, - and mounting file systems inside it is considered harmful. -

2.Running little programs inside the chroot

- To facilitate using pbuilder for other uses, - pbuilder execute is available. - pbuilder execute will take a script - specified in the command-line argument, and - invoke the script inside the chroot. -

- The script can be useful for sequences of operations such as - installing ssh and adding a new user inside the chroot. -

Chapter7.Experimental or wishlist features of pbuilder

Table of Contents

1. Using LVM
2. Using cowdancer
3. Using pbuilder without tar.gz
4. Using pbuilder in a vserver
5. Usage of ccache

- There are some advanced features, above that of the - basic feature of pbuilder, for some specific purposes. -

1.Using LVM

- LVM2 has a useful snapshot function that features Copy-on-write images. - That could be used for pbuilder just as it can be used for - the user-mode-linux pbuilder port. - lvmpbuilder script in the examples directory implements such port. - The scripts and documentation can be found under - /usr/share/doc/pbuilder/examples/lvmpbuilder/. -

2.Using cowdancer

- cowdancer allows copy-on-write semantics on - file system using hard links and hard-link-breaking-on-write - tricks. pbuilder using - cowdancer seems to be much faster and it is - one ideal point for improvement. - cowbuilder, a wrapper for - pbuilder for using - cowdancer is available from - cowdancer package since 0.14 -

- Example command-lines for cowbuilder look like the following. -

- 

-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc

-

- It is also possible to use cowdancer with pdebuild command. - Specify with command-line option --pbuilder - or set it in PDEBUILD_PBUILDER configuration option. -

- 

-$ pdebuild --pbuilder cowbuilder

-

3.Using pbuilder without tar.gz

- The --no-targz - option of pbuilder - will allow usage of pbuilder in a different way - from conventional usage. - It will try to use an existing chroot, - and will not try to clean up after - working on it. - It is an operation mode more like - sbuild. -

- It should be possible to create base chroot images - for dchroot with the following commands: - 

-# pbuilder create --distribution lenny --no-targz --basetgz /chroot/lenny
-# pbuilder create --distribution squeeze --no-targz --basetgz /chroot/squeeze
-# pbuilder create --distribution sid --no-targz --basetgz /chroot/sid

-

4.Using pbuilder in a vserver

- It is possible to use pbuilder in a vserver - environment. This requires either vserver-patches in version 2.1.1-rc14 - or higher, or a Linux kernel version 2.6.16 or higher. -

- To use pbuilder in a vserver, you need to set the - secure_mount CAPS in the - ccapabilities of this vserver. -

5.Usage of ccache

- It is possible to use C compiler cache - ccache to speed up repeated builds of the same - package (or packages that compile the same files multiple times for some - reason). Using ccache can speed up repeated building - of large packages dramatically, at the cost of some disk space and - bookkeeping. -

- To enable usage of ccache with - pbuilder, you should set CCACHEDIR in your - pbuilderrc file. -

- Current implementation of ccache support has several bugs, - that CCACHEDIR must be owned by the pbuilder build user, and - parallel runs of pbuilder is not supported. Therefore it is - not enabled by default. -

Chapter8.Reference materials

Table of Contents

1. Directory structure outside the chroot
2. Directory structure inside the chroot

1.Directory structure outside the chroot

Table8.1.Directory Structure outside the chroot

DirectoryMeaning
/etc/pbuilderrcconfiguration file
/usr/share/pbuilder/pbuilderrcDefault configuration
/var/cache/pbuilder/base.tgzDefault location pbuilder uses for base.tgz, the tar-ball containing a basic Debian installation - with only the build-essential packages. -
/var/cache/pbuilder/build/PID/Default location pbuilder uses for chroot
/var/cache/pbuilder/aptcacheDefault location pbuilder will use as apt cache, to store deb packages required during pbuilder build.
/var/cache/pbuilder/ccacheDefault location pbuilder will use as -cache location
/var/cache/pbuilder/resultDefault location pbuilder puts the deb files and other files created after build
/var/cache/pbuilder/pbuilder-umlresultDefault location pbuilder-user-mode-linux puts the deb files and other files created after build
/var/cache/pbuilder/pbuilder-mntDefault location pbuilder-user-mode-linux uses for mounting the COW file system, for chrooting.
/tmppbuilder-user-mode-linux will mount tmpfs for work.
${HOME}/tmp/PID.cowpbuilder-user-mode-linux use this directory for location of COW file system.
${HOME}/uml-imagepbuilder-user-mode-linux use this directory for user-mode-linux full disk image.

2.Directory structure inside the chroot

Table8.2.Directory Structure inside the chroot

DirectoryMeaning
/etc/mtab - symlink to /proc/mounts. -
/tmp/builddDefault place used in pbuilder - to place the Debian package to be processed. - /tmp/buildd/packagename-version/ - will be the root directory of the package being - processed. HOME environment variable is set to this - value inside chroot by pbuilder-buildpackage. - --inputfile will place files here. -
/runscriptThe - script passed as an argument to - pbuilder execute is passed on. -
/tmp/hooks - The location of hooks. -
/var/cache/apt/archives - pbuilder copies the content of this directory to and from - the aptcache directory of outside chroot. -
/var/cache/pbuilder/ccache - pbuilder bind-mounts this directory for use - by ccache. -
/tmp/XXXXpbuilder-user-mode-linux uses - a script in /tmp to bootstrap into - user-mode-linux

Chapter9.Minor archaeological details

Table of Contents

1. Documentation history
2. Possibly inaccurate Background History of pbuilder
2.1. The Time Before pbuilder
2.2. Birth of pbuilder
2.3. And the second year of its life
2.4. Fifth year of pbuilder

1.Documentation history

- This document was started on 28 Dec 2002 by - Junichi Uekawa, trying to document what is known - about pbuilder. -

- This documentation is available from the pbuilder source tar-ball, - and from the git repository of pbuilder (web-based access is possible). - A copy of this documentation can be found on the - Alioth project page for pbuilder. - There is also a PDF version. - The homepage for pbuilder is - - http://pbuilder.alioth.debian.org/ - hosted by alioth project. -

- Documentation is written using DocBook XML, - with emacs PSGML mode, and using wysidocbookxml for live - previewing. -

2.Possibly inaccurate Background History of pbuilder

- The following is a most possibly inaccurate account of how - pbuilder came to happen, and other attempts to - make something like pbuilder happen. - This part of the document was originally in the AUTHORS file, - to give credit to those who existed before pbuilder. -

2.1.The Time Before pbuilder

- There was once dbuild, which was a shell script to build - Debian packages from source. Lars Wirzenius wrote that - script, and it was good, short, and simple (probably). - There was nothing like build-depends then (I think), and it was simple. - It could have been improved, I could only find references and no actual source. -

- debbuild was probably written by James Troup. I don't know it - because I have never seen the actual code, I could only find some - references to it on the net, and mailing list logs. -

- sbuild is a perl script to build Debian packages from source. - It parses Build-Depends, and performs other miscellaneous checks, - and has a lot of hacks to actually get things building, - including a table of what package to use when virtual packages are - specified (does it do that still?). - It supports the use of a local database for packages which do not - have build-dependencies. It was written by Ronan Hodek, - and I think it was patched and fixed and extended by - several people. It is part of wanna-build, and used extensively - in the Debian buildd system. I think it was maintained - mostly by Ryan Murray. -

2.2.Birth of pbuilder

- wanna-build (sbuild) was (at the time of year 2001) quite - difficult to set up, and it was never a Debian - package. dbuild was something that predated Build-Depends. -

- Building packages from source using Build-Depends - information within a chroot sounded trivial; and - pbuilder was born. It was initially a shell script - with only a few lines, which called debootstrap - and chroot and dpkg-buildpackage in the same run, - but soon, it was decided that that's too slow. -

- Yes, and it took almost an year to get things somewhat - right, and in the middle of the process, Debian 3.0 - was released. Yay. - Debian 3.0 wasn't completely buildable with pbuilder, - but the amount of packages which are not buildable - is steadily decreasing (I hope). -

2.3.And the second year of its life

- Someone wanted pbuilder to not run as - root, and as User-mode-linux has become more useful as time - passed, I've started experimenting with - pbuilder-user-mode-linux. - pbuilder-user-mode-linux has not stayed - functional as much as I would have liked, and bootstrapping - user-mode-linux environment has been - pretty hard, due to the quality of user-mode-linux code or - packaging at that time, which kept on breaking network - support in one way or the other. -

2.4.Fifth year of pbuilder

- pbuilder is now widely adopted as a 'almost standard' tool - for testing packages, and building packages in a pristine - environment. There are other similar tools that do similar - tasks, but they do not share the exact same goal. To - commemorate this fact, pbuilder is now co-maintained with - several people. -

- sbuild is now a well-maintained Debian package within - Debian, and with pbuilder being such a slow monster, some - people prefer the approach of sbuild. Development to use - LVM-snapshots, cowloop, or cowdancer is hoped to improve the - situation somewhat. -

diff -Nru pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.ja.html pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.ja.html --- pbuilder-0.215ubuntu7/Documentation/pbuilder-doc.ja.html 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Documentation/pbuilder-doc.ja.html 1970-01-01 00:00:00.000000000 +0000 @@ -1,894 +0,0 @@ -pbuilder 利用マニュアル

pbuilder 利用マニュアル

利用と操作方法について

Uekawa Junichi [FAMILY Given]

草稿

目次

1. pbuilder の紹介
1. pbuilder の目的
2. pbuilder を利用する
1. base chroot イメージの tar 玉の作成
2. base.tgz の更新
3. base.tgz を利用してパッケージをビルドする
4. Debian Developer のタイピングを省略する、pdebuild
5. 設定ファイル
6. chroot 内部で root 以外でパッケージをビルドする
7. pbuilder をバックポートに活用する
8. パッケージを大量にビルドする
9. 自動バックポートスクリプト
10. pbuilder を自動テストに利用する
11. pbuilder でその他のコンパイラでのビルドを試験する
3. user-mode-linux を pbuilder で利用する
1. user-mode-linux の設定
2. rootstrap の設定
3. pbuilder-uml の設定
4. pbuilder-user-mode-linuxを実行する場合の検討項目
5. pbuilder-user-mode-linux を複数同時に実行させる
6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual -machine
4. FAQ （よくある質問）
1. pbuilder create が失敗する
2. bind mount できないディレクトリ
3. ビルド失敗の調査のために pbuilder 環境にログインする
4. 環境を変更するために pbuilder 環境にログインする
5. BUILDRESULTUID を sudo のセッションに追加する
6. $TMPDIRの使い方について
7. Creating a shortcut for running pbuilder with a specific -distribution
8. Using environmental variables for running pbuilder for -specific distribution -
9. Using special apt sources lists, and local packages
10. How to get pbuilder to run apt-get update before trying to satisfy -build-dependency
11. pbuilder login で bash のプロンプトを変更する
12. Creating a chroot reminder
13. Using /var/cache/apt/archives for the package cache
14. pbuilder back ported to stable Debian releases
15. Warning about LOGNAME not being defined
16. Cannot Build-conflict against an essential package
17. Avoiding the "ln: Invalid cross-device link" message
18. Using fakechroot
19. Using debconf inside pbuilder sessions
20. nodev mount options hinder pbuilder activity
21. pbuilder が遅い
22. Using pdebuild to sponsor package
23. Why is there a source.changes file in ../?
24. amd64 and i386-mode
25. Using tmpfs for buildplace
26. svn-buildpackage を pbuilder で利用する
5. Troubleshooting and development
1. Reporting bugs
2. Mailing list
3. IRC Channel
4. Information for pbuilder developers
6. Other uses of pbuilder
1. pbuilder を小規模な実験のために活用する
2. Running little programs inside the chroot
7. Experimental or wishlist features of pbuilder
1. LVMの活用
2. cowdancer の活用
3. tar.gz を利用しないで pbuilder を利用する
4. pbuilder を vserver で利用する
5. Usage of ccache
8. 参考文献
1. chroot 外部のディレクトリ構造
2. chroot 内部のディレクトリ構造
9. 些細な過去の経緯の詳細
1. マニュアルの履歴
2. Possibly inaccurate Background History of pbuilder
2.1. The Time Before pbuilder
2.2. pbuilder の誕生
2.3. そして二年目の人生
2.4. pbuilder の5年目

表の一覧

5.1. テストスイートのディレクトリ構造
8.1. chroot 内部のディレクトリ構造
8.2. chroot 内部のディレクトリ構造

第1章 pbuilder の紹介

目次

1. pbuilder の目的

1. pbuilder の目的

- pbuilder は Personal Builder -の略です。個人的なワークステーションなどの開発環境で、Debianパッケージをビルドするためのシステムです。pbuilder -はパッケージが Debian -のインストール環境のほとんどでビルドできることを確認するため、Debianパッケージをクリーンルーム内部で自動にビルドするシステムとして簡単に利用できるようになることを目指しています。クリーンルーム環境は最小限のパッケージを -chroot にインストールすることで実現しています。 -

- Debian -ディストリビューションはソースコードつきのフリーソフトウェアにより構成されています。Debianの「main」セクションにあるソフトウェアは、Build-depend -（ビルド時依存関係）として指定されたDebianの「main」セクションにあるパッケージのみがインストールされている状態でビルドできなければなりません。 -

- 主なる pbuilder -の目的は、他の自動ビルドシステムとは違います。それは、パッケージをできるだけビルドできるようなことを目的としていないところです。パッケージが何を必要としているのかを想像しようとはしません。また選択が可能であれば、最悪な選択をする場合もあります。 -

- この方針を採用することで、 pbuilder は、 pbuilder -で試験したパッケージはほとんどのDebianがインストールされた環境でビルドできるように確認することができます。これによってDebian全体としてのソースコードのビルドしやすさの向上を目指しています。 -

- Debian をソースからビルドできるようにするという目標はほぼ完了し、よく進捗しています。Debian -3.0の時代ではソースからビルドするのに問題が多数ありましたが、最近のリリースではましになってきています。 -

第2章 pbuilder を利用する

目次

1. base chroot イメージの tar 玉の作成
2. base.tgz の更新
3. base.tgz を利用してパッケージをビルドする
4. Debian Developer のタイピングを省略する、pdebuild
5. 設定ファイル
6. chroot 内部で root 以外でパッケージをビルドする
7. pbuilder をバックポートに活用する
8. パッケージを大量にビルドする
9. 自動バックポートスクリプト
10. pbuilder を自動テストに利用する
11. pbuilder でその他のコンパイラでのビルドを試験する

- 操作には、いくつかの簡単なコマンドがあります。pbuilder create、 pbuilder -update、そして pbuilder build -コマンドがよく使われます。ひとつづつ見ていきましょう。 -

1. base chroot イメージの tar 玉の作成

- pbuilder create will create a base chroot image tar-ball -(base.tgz). All other commands will operate on the resulting base.tgz If -the Debian release to be created within chroot is not going to be "sid" -(which is the default), the distribution code-name needs to be specified -with the --distribution command-line -option. -

- debootstrap [1] is used -to create the bare minimum Debian installation, and then build-essential -packages are installed on top of the minimum installation using -apt-get inside the chroot. -

- For fuller documentation of command-line options, see the pbuilder.8 manual -page. Some configuration will be required for -/etc/pbuilderrc for the mirror site [2] to use, and proxy configuration may be required to -allow access through HTTP. See the pbuilderrc.5 manual page for details. -

2. base.tgz の更新

pbuilder update will update the base.tgz. It will -extract the chroot, invoke apt-get update and -apt-get dist-upgrade inside the chroot, and then recreate -the base.tgz (the base tar-ball). -

- It is possible to switch the distribution which the base.tgz is targeted at -at this point. Specify --distribution -sid ---override-config to change the distribution to -sid. [3] -

- コマンドラインオプションの詳細なドキュメントについては、pbuilder.8 マニュアルを参照 -

3. base.tgz を利用してパッケージをビルドする

- To build a package inside the chroot, invoke pbuilder build -whatever.dsc. pbuilder will -extract the base.tgz to a temporary working directory, enter the directory -with chroot, satisfy the build-dependencies inside chroot, and build the -package. The built packages will be moved to a directory specified with the ---buildresult command-line option. -

- The --basetgz option can be used to -specify which base.tgz to use. -

- pbuilder は base.tgz から新しい -chroot イメージを展開します。（base.tgz は pbuilder create で作成され、 -pbuilder update で更新されます)。 chroot には Build-Depend関係のパッケージが -debian/control を解析して apt-get を実行することで追加されます。 -

- コマンドラインオプションの詳細なドキュメントについては、pbuilder.8 マニュアルを参照 -

4. Debian Developer のタイピングを省略する、pdebuild

- pdebuild -は、あらゆる操作の中でももっとも頻繁に行われるだろう作業を簡略化するためのラッパースクリプトです。Debian Developerは Debian -パッケージのソースディレクトリで debuild コマンドをうつことでパッケージをビルドします。 -pdebuild は同様の操作をすることで、パッケージを chroot 内部でビルドし、 -現在のツリーが chroot 内部でもビルドすることを確認します。 -

- pdebuild calls dpkg-source to build -the source packages, and then invokes pbuilder on the -resulting source package. However, unlike debuild, the resulting deb files -will be found in the --buildresult -directory. -

- 詳細は pdebuild.1 マニュアルページを参照してください。 -

- There is a slightly different mode of operation available in -pdebuild since version 0.97. pdebuild -usually runs debian/rules clean outside of the chroot; -however, it is possible to change the behavior to run it inside the chroot -with the --use-pdebuild-internal. It -will try to bind mount the working directory inside chroot, and run -dpkg-buildpackage inside. It has the following -characteristics, and is not yet the default mode of operation. -

  • - ソースパッケージを作成する際に、Build-Depend を chroot 内部で満たします。 -(以前の pdebuild でできなかったよい点です)。 -

  • 作業ディレクトリに chroot 内部から変更を加えられます。

  • pdebuild でビルドできることは pbuilder -で必ず動くということが保証されるわけではないです。

  • ソースパッケージを作るステップ自体が失敗した場合に、その chroot を利用するセッションは無駄に終わります（chroot -の作成には時間がかかる、cowdancer 等で改善します。)

  • Does not work in the same manner as it used to; for example, ---buildresult does not have any effect.

  • chroot 内部でのビルドは chroot 外部での現在のユーザで実行される。 -

5. 設定ファイル

- 設定をすべてコマンドラインで指定することも可能です。しかし、入力を簡便にするために、設定ファイルを利用することもできます。 -

- /etc/pbuilderrc と -${HOME}/.pbuilderrc が pbuilder -を実行すると読み込まれます。可能なオプションについては、 pbuilderrc.5 に解説されています。 -

- It is useful to use --configfile option to load up a preset -configuration file when switching between configuration files for different -distributions. -

- Please note ${HOME}/.pbuilderrc supersede system -settings. Caveats is that if you have some configuration, you may need to -tweak the configuration to work with new versions of pbuilder when -upgrading. -

6. chroot 内部で root 以外でパッケージをビルドする

- pbuilder requires full root privilege when it is -satisfying the build-dependencies, but most packages do not need root -privilege to build, or even refused to build when they are built as root. -pbuilder can create a user which is only used inside -pbuilder and use that user id when building, and use the -fakeroot command when root privilege is required. -

- BUILDUSERID 設定オプションは既存のユーザIDと異なるIDに設定しておきましょう。そうするとパッケージが -pbuilder -内部でビルドしている際に、chroot　外部の環境に影響をあたえにくくなります。BUILDUSERNAME が設定されている場合、その名前を -pbuilder は利用し、 chroot 内部でroot権限で動作する代わりに、fakeroot -を利用してパッケージをビルドします。 -

- fakeroot の方法を利用している場合でも、pbuilder は root 権限が必要な場面では root -権限で稼働します。例えば、chroot内部にパッケージをインストールする時にはpbuilder は root -権限で稼働します。 -

- pbuilder を root 権限を必要としないで利用する方法については、 user-mode-linux -の利用が必要です。 3章user-mode-linux を pbuilder で利用する で説明しています。 -

7. pbuilder をバックポートに活用する

- pbuilder は古いディストリビューションのchroot -を作成し、そこでパッケージをビルドすることで、Debian -の最新版のディストリビューションからソフトウエアをバックポートするのに利用することが可能です。いくつかの点を検討する必要があり、次の理由により全自動でバックポートすることは現実的では無く、手動での作業も必要になるでしょう: -

  • unstableのパッケージが unstable にしかないパッケージや、unstable -にしかないバージョンのパッケージに依存している場合がある。つまり、stable では Build-Depends: -を充足することができない(さらなるバックポートが必要になる)。

  • stable ディストリビューションには unstable で修正しているバグが含まれており、ワークアラウンドが必要になる。

  • unstable のパッケージが unstable 上であってもビルドしない場合がある。

8. パッケージを大量にビルドする

- pbuilder -は操作がインタラクティブではないため、自動的に動かすことができる。pbuilder -を複数のパッケージに関して、インタラクティブじゃないように実行することができます。それをするためのスクリプトはいくつか存在します。上川は2001年からそのようなスクリプトを実行し、 -pbuilder でビルドできない場合についてバグ報告をしていました。次のような問題が発見されました: -

  • 依存関係を充足させるためのインストールは非インタラクティブに行われる必要がありますが、一部のパッケージはインタラクティブな操作がないとインストールできないくらいに壊れているものがあります（postgresqlなど）.

  • ライブラリパッケージに問題があったり、gcc/gcj/g++ に問題がある場合、また bison もそうですが、多くのビルド失敗が報告されます。 -(gcj-3.0 に "javac" がなくなったり、bison がより厳密になったり、など） -

  • 一部の人はビルド失敗の報告に敵対的なので注意しましょう。

- 2002年ころのpbuilder -の実行により初期のバグは洗いだされました。しかし、このように移行に関連したDebian全体に影響するような問題はときどき発生します。回帰テストには価値があるのです。 -

- 上川が利用したスクリプトは今 pbuilder -ディストリビューションに含まれています。/usr/share/doc/pbuilder/examples/pbuildd/ -にあり、設定は、 /etc/pbuilder/pbuildd-config.sh -が設定ファイルです。pbuilder -になれている人であれば簡単に設定することができるはずです。しばらく実行されていたため、自分のシステムでも実行できるでしょう。ただ、まだ新しいので問題があれば -Debian BTS に登録してください。 -

- pbuildd の設定について気にしておくところがいくつかあります。 -

  • ビルドしないパッケージの一覧ファイル ./avoidlist が存在する必要があります。

  • 自分のアーキテクチャ向けでないものを含めて、あらゆるものをビルドしようとします。

  • 任意のビルドスクリプトを実行しているため、 root 権限で実行しないために、 pbuilder -のfakeroot オプションを利用するのがよいでしょう。

  • すべてのビルドが有限時間で完了することが保証されているわけではありません、そのためタイムアウトを準備しておくことが必要かもしれません。そうしないとpbuilddは悪いビルドでずっと待ち状態になる可能性もあります。

  • - 一部のパッケージは大量のディスク領域を必要とします、現時点では最大のパッケージであっても2GBくらいが十分なようです。もしそうでないという状況を発見した場合はこの文書のメンテナに連絡してください。 -

9. 自動バックポートスクリプト

- 一部の人は pbuilder を一部のパッケージを自動的に stable -ディストリビューションにバックポートするために利用しています。 -

- どのように実際にやっているのか情報をください、フィードバックや情報や例を歓迎します。 -

10. pbuilder を自動テストに利用する

- pbuilder は、自動的なテストのために利用することができます。フックを配置することができ、そのフックは -chroot 内部にパッケージをインストールしたり実行したりその他のいろいろなことを実行することができます。実行可能なテストとアイデアは次です: -

  • Automatic install-remove-install-purge-upgrade-remove-upgrade-purge -test-suite (distributed as an example, B91dpkg-i), or -just check that everything installs somewhat -(execute_installtest.sh).

  • 自動的にlintianを実行する (例として -/usr/share/doc/pbuilder/examples/B90lintianが配布されている)。

  • 自動的にパッケージの debian-test を行う? debian-test パッケージは Debian から削除されました。 -pbuilder での代替は debian/pbuilder-test -ディレクトリにあります。B92test-pkgスクリプトで実装されています。

- To use B92test-pkg script, first, add it to your hook directory. -[4]. The test files are shell scripts -placed in debian/pbuilder-test/NN_name (where NN is a -number) following run-parts standard[5] -for file names. After a successful build, packages are first tested for -installation and removal, and then each test is ran inside the chroot. The -current directory is the top directory of the source-code. This means you -can expect to be able to use ./debian/ directory from inside your scripts. -

- Example scripts for use with pbuilder-test can be found in -/usr/share/doc/pbuilder/examples/pbuilder-test. -

11. pbuilder でその他のコンパイラでのビルドを試験する

- Most packages are compiled with gcc or -g++ and using the default compiler version, which was gcc -2.95 for Debian GNU/Linux 3.0 (i386). However, Debian 3.0 was distributed -with other compilers, under package names such as gcc-3.2 -for gcc compiler version 3.2. It was therefore possible to try compiling -packages against different compiler versions. -pentium-builder provides an infrastructure for using a -different compiler for building packages than the default gcc, by providing -a wrapper script called gcc which calls the real gcc. To use -pentium-builder in pbuilder, it is -possible to set up the following in the configuration: 

-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2

-

- It will instruct pbuilder to install the -pentium-builder package and also the GCC 3.2 compiler -packages inside the chroot, and set the environment variables required for -pentium-builder to function. -


[1] debootstrap か cdebootstrap か選択することができます

[2] - 公開ミラーに多数のアクセス負荷をかけないため、ミラーはローカルミラーであることが望ましいです。apt-proxy などのツールの活用を推奨します。 -

[3] アップグレードしかサポートされていません。Debianはダウングレードをサポートしていません（現時点では？）。

[4] --hookdir /usr/share/doc/pbuilder/examples -コマンドラインオプションを指定することですべてのサンプルフックを利用することが可能です。

[5] run-parts(8) を参照してください。例えば、ファイル名に '.' はふくめられません。 -

第3章 user-mode-linux を pbuilder で利用する

目次

1. user-mode-linux の設定
2. rootstrap の設定
3. pbuilder-uml の設定
4. pbuilder-user-mode-linuxを実行する場合の検討項目
5. pbuilder-user-mode-linux を複数同時に実行させる
6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual -machine

- It is possible to use user-mode-linux by invoking -pbuilder-user-mode-linux instead of -pbuilder. pbuilder-user-mode-linux -doesn't require root privileges, and it uses the copy-on-write (COW) disk -access method of User-mode-linux which typically makes it -much faster than the traditional pbuilder. -

- User-mode-linux is a somewhat less proven platform than -the standard Unix tools which pbuilder relies on -(chroot, tar, and -gzip) but mature enough to support -pbuilder-user-mode-linux since its version 0.59. And -since then, pbuilder-user-mode-linux has seen a rapid -evolution. -

- The configuration of pbuilder-user-mode-linux goes in -three steps: -

  • user-mode-linux の設定

  • rootstrap の設定

  • pbuilder-uml の設定

-

1. user-mode-linux の設定

- user-mode-linux isn't completely trivial to set up. It would probably be -useful to acquaint yourself with it a bit before attempting to use -rootstrap or -pbuilder-user-mode-linux. For details, read -/usr/share/doc/uml-utilities/README.Debian and the -user-mode-linux documentation. (It's in a separate -package, user-mode-linux-doc.) -

- user-mode-linux requires the user to be in the uml-net -group in order to configure the network unless you are using slirp. -

- If you compile your own kernel, you may want to verify that you enable -TUN/TAP support, and you might want to consider the SKAS patch. -

2. rootstrap の設定

- rootstrap is a wrapper around debootstrap. It creates a -Debian disk image for use with UML. To configure rootstrap, there are -several requirements. -

  • rootstrap　パッケージをインストールします。

  • - TUN/TAP only: add the user to the uml-net group to allow access to the -network 

    adduser dancer uml-net

    -

  • TUN/TAPを利用している場合: カーネルが TUN/TAP -インタフェースをサポートしていることを確認してください。必要であればカーネルをリビルドしてください。 -

  • Set up /etc/rootstrap/rootstrap.conf. For example, if -the current host is 192.168.1.2, changing following entries to something -like this seems to work. 

    -transport=tuntap
-interface=eth0
-gateway=192.168.1.1
-mirror=http://192.168.1.2:8081/debian
-host=192.168.1.198
-uml=192.168.1.199
-netmask=255.255.255.0

    Some -experimentation with configuration and running rootstrap -~/test.uml to actually test it would be handy. -

    - Using slirp requires less configuration. The default configuration comes -with a working example. -

3. pbuilder-uml の設定

- 以下の設定が必要です: -

  • pbuilder-uml をインストールする

  • - Set up the configuration file -/etc/pbuilder/pbuilder-uml.conf in the following -manner. It will be different for slirp. 

    -MY_ETH0=tuntap,,,192.168.1.198
-UML_IP=192.168.1.199
-UML_NETMASK=255.255.255.0
-UML_NETWORK=192.168.1.0
-UML_BROADCAST=255.255.255.255
-UML_GATEWAY=192.168.1.1
-PBUILDER_UML_IMAGE="/home/dancer/uml-image"

    -Also, it needs to match the rootstrap configuration. -

  • - Make sure BUILDPLACE is writable by the user. Change BUILDPLACE in the -configuration file to a place where the user has access. -

  • Run pbuilder-user-mode-linux create --distribution -sid to create the image.

  • Try running pbuilder-user-mode-linux build.

-

4. pbuilder-user-mode-linuxを実行する場合の検討項目

- pbuilder-user-mode-linux emulates most of -pbuilder, but there are some differences. -

  • - pbuilder-user-mode-linux does not support all options of -pbuilder properly yet. This is a problem, and will be -addressed as specific areas are discovered. -

  • - /tmp is handled differently inside -pbuilder-user-mode-linux. In -pbuilder-user-mode-linux, /tmp is -mounted as tmpfs inside UML, so accessing files under -/tmp from outside user-mode-linux does not work. It -affects options like --configfile, and -when trying to build packages placed under /tmp. -

5. pbuilder-user-mode-linux を複数同時に実行させる

- pbuilder-user-mode-linux -を同一システム上で同時に複数実行させるにはいくつか注意するべき点があります。 - -

  • The create and update methods must not be run when a build is in progress, -or the COW file will be invalidated.

  • - If you are not using slirp, user-mode-linux processes which are running in -parallel need to have different IP addresses. Just trying to run the -pbuilder-user-mode-linux several times will result in -failure to access the network. But something like the following will work: -

    -for IP in 102 103 104 105; do
-  xterm -e pbuilder-user-mode-linux build --uml-ip 192.168.0.$IP \
-    20030107/whizzytex_1.1.1-1.dsc &
-done

    When using slirp, this problem does not -exist. -

6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual -machine

- It is possible to use pbuilder-user-mode-linux for other -uses than just building Debian packages. pbuilder-user-mode-linux -login will let a user use a shell inside the -user-mode-linux pbuilder base image, and -pbuilder-user-mode-linux execute will -allow the user to execute a script inside the image. -

- You can use the script to install ssh and add a new user, so that it is -possible to access inside the user-mode-linux through ssh. -

- Note that it is not possible to use a script from /tmp -due to the way pbuilder-user-mode-linux mounts a tmpfs at -/tmp. -

- The following example script may be useful in starting a sshd inside -user-mode-linux. - 

-#!/bin/bash
-
-apt-get install -y ssh xbase-clients xterm
-echo "enter root password"
-passwd
-cp /etc/ssh/sshd_config{,-}
-sed 's/X11Forwarding.*/X11Forwarding yes/' /etc/ssh/sshd_config- > /etc/ssh/sshd_config
-
-/etc/init.d/ssh restart
-ifconfig
-echo "Hit enter to finish"
-read

第4章 FAQ （よくある質問）

目次

1. pbuilder create が失敗する
2. bind mount できないディレクトリ
3. ビルド失敗の調査のために pbuilder 環境にログインする
4. 環境を変更するために pbuilder 環境にログインする
5. BUILDRESULTUID を sudo のセッションに追加する
6. $TMPDIRの使い方について
7. Creating a shortcut for running pbuilder with a specific -distribution
8. Using environmental variables for running pbuilder for -specific distribution -
9. Using special apt sources lists, and local packages
10. How to get pbuilder to run apt-get update before trying to satisfy -build-dependency
11. pbuilder login で bash のプロンプトを変更する
12. Creating a chroot reminder
13. Using /var/cache/apt/archives for the package cache
14. pbuilder back ported to stable Debian releases
15. Warning about LOGNAME not being defined
16. Cannot Build-conflict against an essential package
17. Avoiding the "ln: Invalid cross-device link" message
18. Using fakechroot
19. Using debconf inside pbuilder sessions
20. nodev mount options hinder pbuilder activity
21. pbuilder が遅い
22. Using pdebuild to sponsor package
23. Why is there a source.changes file in ../?
24. amd64 and i386-mode
25. Using tmpfs for buildplace
26. svn-buildpackage を pbuilder で利用する

- Here, known problems and frequently asked questions are documented. This -portion was initially available in README.Debian file, but moved here. -

1. pbuilder create が失敗する

- It often happens that pbuilder cannot create the latest -chroot. Try upgrading pbuilder and debootstrap. It is -currently only possible to create software that handles the past. Future -prediction is a feature which may be added later after we have become -comfortable with the past. -

- There are people who occasionally back port debootstrap to stable versions; -hunt for them. -

- When there are errors with the debootstrap phase, the debootstrap script -needs to be fixed. pbuilder does not provide a way to -work around debootstrap. -

2. bind mount できないディレクトリ

- Because of the way pbuilder works, there are several -directories which cannot be bind-mounted when running -pbuilder. The directories include -/tmp, /var/cache/pbuilder, and -system directories such as /etc and -/usr. The recommendation is to use directories under -the user's home directory for bind-mounts. -

3. ビルド失敗の調査のために pbuilder 環境にログインする

- It is possible to invoke a shell session after a build failure. Example -hook scripts are provided as C10shell and -C11screen scripts. C10shell script will start bash -inside chroot, and C11screen script will start GNU screen inside the chroot. -

4. 環境を変更するために pbuilder 環境にログインする

- It is sometimes necessary to modify the chroot environment. -login will remove the contents of the chroot after -logout. It is possible to invoke a shell using hook scripts. -pbuilder update executes 'E' scripts, and a sample for -invoking a shell is provided as C10shell. - 

-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell

- It is also possible to add --save-after-exec and/or ---save-after-login options to the pbuilder -login session to accomplish the goal. It is possible to add the ---uml-login-nocow option to -pbuilder-user-mode-linux login session -as well. -

5. BUILDRESULTUID を sudo のセッションに追加する

- It is possible to set 

BUILDRESULTUID=$SUDO_UID

in pbuilderrc to -set the proper BUILDRESULTUID when using sudo. -

6. $TMPDIRの使い方について

- If you are setting $TMPDIR to an unusual value, of other than -/tmp, you will find that some errors may occur inside -the chroot, such as dpkg-source failing. -

There are two options, you may install a hook to create that directory, or -set 

export TMPDIR=/tmp

in pbuilderrc. Take your pick. -

- An example script is provided as examples/D10tmp with -pbuilder. -

7. Creating a shortcut for running pbuilder with a specific -distribution

- When working with multiple chroots, it would be nice to work with scripts -that reduce the amount of typing. An example script -pbuilder-distribution.sh is provided as an example. -Invoking the script as pbuilder-squeeze will invoke -pbuilder with a squeeze chroot. -

8. Using environmental variables for running pbuilder for -specific distribution -

This section[6] describes briefly a way to -setup and use multiple pbuilder setups by creating a pbuilderrc -configuration in your home path ($HOME/.pbuilderrc) -and using the variable "DIST" when running pbuilder or pdebuild. -

First, setup $HOME/.pbuilderrc to look like:

- 

-if [ -n "${DIST}" ]; then
-        BASETGZ="`dirname $BASETGZ`/$DIST-base.tgz"
-        DISTRIBUTION="$DIST"
-        BUILDRESULT="/var/cache/pbuilder/$DIST/result/"
-        APTCACHE="/var/cache/pbuilder/$DIST/aptcache/"
-fi
-

Then, whenever you wish to use pbuilder for a particular distro, assign a -value to "DIST" that is one of the distros available for Debian or any -Debian based distro you happen to be running (i.e. whatever is found under -/usr/lib/debootstrap/scripts). -

Here's some examples on running pbuilder or pdebuild: -

-DIST=gutsy sudo pbuilder create
-
-DIST=sid sudo pbuilder create --mirror http://http.us.debian.org/debian
-
-DIST=gutsy sudo pbuilder create \
-        --othermirror "deb http://archive.ubuntu.com/ubuntu gutsy universe \
-        multiverse"
-
-DIST=gutsy sudo pbuilder update
-
-DIST=sid sudo pbuilder update --override-config --mirror \
-http://http.us.debian.org/debian \
---othermirror "deb http://http.us.debian.org/debian sid contrib non-free"
-
-DIST=gutsy pdebuild
-

9. Using special apt sources lists, and local packages

- If you have some very specialized requirements on your apt setup inside -pbuilder, it is possible to specify that through the ---othermirror option. Try something -like: --othermirror "deb http://local/mirror stable -main|deb-src http://local/source/repository ./" -

- To use the local file system instead of HTTP, it is necessary to do -bind-mounting. --bindmounts is a -command-line option useful for such cases. -

- It might be convenient to use your built packages from inside the chroot. -It is possible to automate the task with the following configuration. -First, set up pbuilderrc to bindmount your build results directory. -

- 

BINDMOUNTS="/var/cache/pbuilder/result"

-

- Then, add the following hook -

- 

-# cat /var/cache/pbuilder/hooks/D70results
-#!/bin/sh
-cd /var/cache/pbuilder/result/
-/usr/bin/dpkg-scanpackages . /dev/null > /var/cache/pbuilder/result/Packages
-/usr/bin/apt-get update

-

- This way, you can use deb -file:/var/cache/pbuilder/result -

- -To add new apt-key inside chroot: - -

- 

-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-

10. How to get pbuilder to run apt-get update before trying to satisfy -build-dependency

- You can use hook scripts for this. D scripts are run before satisfying -build-dependency. -

- -This snippet comes from Ondrej Sury. -

11. pbuilder login で bash のプロンプトを変更する

- To make distinguishing bash prompts inside pbuilder -easier, it is possible to set environment variables such as PS1 inside -pbuilderrc -

- With versions of bash more recent than 2.05b-2-15, the value of the -debian_chroot variable, if set, is included in the value of PS1 (the Bash -prompt) inside the chroot. In prior versions of bash,[7] setting PS1 in pbuilderrc worked. -

example of debian_chroot

-	export debian_chroot="pbuild$$"

example of PS1

-	export PS1="pbuild chroot 32165 # "

12. Creating a chroot reminder

- Bash prompts will help you remember that you are inside a chroot. There are -other cases where you may want other signs of being inside a chroot. Check -out the examples/F90chrootmemo hook script. It will -create a file called /CHROOT inside your chroot. -

13. Using /var/cache/apt/archives for the package cache

- For the help of low-bandwidth systems, it is possible to use -/var/cache/apt/archives as the package cache. Just -specify it instead of the default -/var/cache/pbuilder/aptcache. -

- It is however not possible to do so currently with the user-mode-linux -version of pbuilder, because -/var/cache/apt/archives is usually only writable by -root. -

- Use of dedicated tools such as apt-proxy is recommended, since caching of -packages would benefit the system outside the scope of -pbuilder. -

14. pbuilder back ported to stable Debian releases

- Currently stable back port of pbuilder is available at backports.org. -

15. Warning about LOGNAME not being defined

- You might see a lot of warning messages when running -pbuilder. -

- 

-	dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)

-

- It is currently safe to ignore this warning message. Please report back if -you find any problem with having LOGNAME unset. Setting LOGNAME caused a -few problems when invoking chroot. For example, dpkg -requires getpwnam to succeed inside chroot, which means LOGNAME and the -related user information have to be set up inside chroot. -

16. Cannot Build-conflict against an essential package

- pbuilder does not currently allow Build-Conflicts against -essential packages. It should be obvious that essential packages should not -be removed from a working Debian system, and a source package should not try -to force removal of such packages on people building the package. -

17. Avoiding the "ln: Invalid cross-device link" message

- By default, pbuilder uses hard links to manage the -pbuilder package cache. It is not possible to make hard -links across different devices; and thus this error will occur, depending on -your set up. If this happens, set 

APTCACHEHARDLINK=no

in -your pbuilderrc file. Note that packages in APTCACHE will -be copied into chroot local cache, so plan for enough space on -BUILDPLACE device. -

18. Using fakechroot

- It is possible to use fakechroot instead of being root to -run pbuilder; however, several things make this -impractical. fakechroot overrides library loads and -tries to override default libc functions when providing the functionality of -virtual chroot. However, some binaries do no use libc to -function, or override the overriding provided by -fakechroot. One example is ldd. -Inside fakechroot, ldd will check the -library dependency outside of the chroot, which is not the expected -behavior. -

- To work around the problem, debootstrap has a --variant -fakechroot option. Use that, so that ldd and ldconfig are -overridden. -

- Make sure you have set your LD_PRELOAD path correctly, as described in the -fakechroot manpage. -

19. Using debconf inside pbuilder sessions

- To use debconf inside pbuilder, setting DEBIAN_FRONTEND -to 「readline」 in pbuilderrc should work. -Setting it to 「dialog」 should also work, but make sure whiptail -or dialog is installed inside the chroot. -

20. nodev mount options hinder pbuilder activity

- If you see messages such as this when building a chroot, you are mounting -the file system with the nodev option. - 

-	/var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied

- You will also have problems if you mount the file system with the noexec -option, or nosuid. Make sure you do not have these flags set when mounting -the file system for /var/cache/pbuilder or $BUILDPLACE. -

- This is not a problem when using user-mode-linux. -

- See 316135 for example. -

21. pbuilder が遅い

- pbuilder is often slow. The slowest part of -pbuilder is extracting the tar.gz every time -pbuilder is invoked. That can be avoided by using -pbuilder-user-mode-linux. -pbuilder-user-mode-linux uses COW file system, and thus -does not need to clean up and recreate the root file system. -

- pbuilder-user-mode-linux is slower in executing the -actual build system, due to the usual user-mode-linux -overhead for system calls. It is more friendly to the hard drive. -

- pbuilder with cowdancer is also an alternative that -improves speed of pbuilder startup. -

22. Using pdebuild to sponsor package

- To sign a package marking for sponsorship, it is possible to -use --auto-debsign and ---debsign-k options of -pdebuild. - 

-	pdebuild  --auto-debsign  --debsign-k XXXXXXXX

23. Why is there a source.changes file in ../?

- When running pdebuild, pbuilder will -run dpkg-buildpackage to create a Debian source package to pass it on to -pbuilder. File named XXXX_YYY_source.changes is what -remains from that process. It is harmless unless you try to upload it to -the Debian archive. -

- This behavior is different when running through ---use-pdebuild-internal -

24. amd64 and i386-mode

- amd64 architectures are capable of running binaries in i386 mode. It is -possible to use pbuilder to run packages, using -linux32 and debootstrap ---arch option. Specifically, a command-line -option like the following will work. -

- 

-pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
-  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian
-linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz

-

25. Using tmpfs for buildplace

- To improve speed of operation, it is possible to use tmpfs for pbuilder -build location. Mount tmpfs to -/var/cache/pbuilder/build, and set 

APTCACHEHARDLINK=no

. -

26. svn-buildpackage を pbuilder で利用する

- pdebuild command can be used with svn-buildpackage --svn-builder -command-line option. [8] - 

-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"

[6] This part of the documentation contributed by Andres Mejia

- This example was taken from a wiki (https://wiki.ubuntu.com/PbuilderHowto). -

[7] Debian 3.0 以前のbash

[8] -Zack has posted an example on his blog.

第5章 Troubleshooting and development

目次

1. Reporting bugs
2. Mailing list
3. IRC Channel
4. Information for pbuilder developers

1. Reporting bugs

- To report bugs, it would be important to have a log of what's going wrong. -Most of the time, adding a --debug -option and re-running the session should do the trick. Please send the log -of such session along with your problem to ease the debugging process. -

2. Mailing list

- There is a mailing list for pbuilder on alioth -(pbuilder-maint@lists.alioth.debian.org). You can subscribe through the -alioth web interface. -http://alioth.debian.org/mail/?group_id=30778. -

3. IRC Channel

- For coordination and communication, IRC channel #pbuilder on irc.oftc.net is -used. Please log your intent there when you are going to start doing some -changes and committing some change. -

4. Information for pbuilder developers

- This section tries to document current development practices and how things -generally operate in development. -

- pbuilder is co-maintained with resources provided by -Alioth. There is an Alioth project page at -http://alioth.debian.org/projects/pbuilder. Home page is also -available, at -http://alioth.debian.org/projects/pbuilder which shows this text. -git repository is available through http, git, or (if you have an account on -alioth, ) ssh. - 

-git-clone git://git.debian.org/git/pbuilder/pbuilder.git
-git-clone http://git.debian.org/git/pbuilder/pbuilder.git
-git-clone ssh://git.debian.org/git/pbuilder/pbuilder.git

- Git commit message should have the first one line describing what the commit -does, formatted in the way debian/changelog is formatted because it is -copied verbatim to changelog via git-dch. The second line is empty, and the -rest should describe the background and extra information related to -implementation of the commit. -

- Test-suites are available in ./testsuite/ directory. -Changes are expected not to break the test-suites. -./run-test.sh is a basic test-suite, which puts a -summary in run-test.log, and -run-test-cdebootstrap.log. -./run-test-regression.sh is a regression test-suite, -which puts the result in run-test-regression.log. -Currently, run-test.sh is ran automatically daily to ensure that pbuilder is -working. -

表5.1 テストスイートのディレクトリ構造

ディレクトリ意味
./testsuite/テストスイートへのディレクトリ
./testsuite/run-test.shDaily regression test to test against Debian Archive changes breaking -pbuilder.
./testsuite/run-test.logA summary of testsuite
./testsuite/normal/Directory for testsuite results of running pbuilder with debootstrap
./testsuite/cdebootstrap/Directory for testsuite results of running pbuilder with cdebootstrap
./testsuite/run-regression.shRegression testsuite, ran every time change is made to pbuilder to make sure -there is no regression.
./testsuite/run-regression.logSummary of test result
./testsuite/regression/BugID-*.shRegression tests, exit 0 for success, exit 1 for failure
./testsuite/regression/BugID-*回帰テストスイートに利用されるファイル
./testsuite/regression/log/BugID-*.sh.log回帰テストの出力、 run-regression.sh によりスクリプトの出力がリダイレクトされる

- When making changes, changes should be documented in the Git commit log. -git-dch will generate debian/changelog from the commit log. Make the first -line of your commit log meaningful, and add any bug-closing information -available. debian/changelog should not be edited directly unless when -releasing a new version. -

- A TODO file is available in debian/TODO. It's mostly -not well-maintained, but hopefully it will be more up-to-date when people -start using it. emacs todoo-mode is used in editing the file. -

- When releasing a new version of pbuilder, the version is -tagged with the git tag X.XXX (version number). This is done with -./git-tag.sh script available in the source tree. -

第6章 Other uses of pbuilder

目次

1. pbuilder を小規模な実験のために活用する
2. Running little programs inside the chroot

1. pbuilder を小規模な実験のために活用する

- There are cases when some small experimenting is required, and you do not -want to damage the main system, like when installing experimental library -packages, or compiling with experimental compilers. For such cases, the -pbuilder login command is available. -

- pbuilder login is a debugging feature for -pbuilder itself, but it also allows users to have a -temporary chroot. -

- Note that the chroot is cleaned after logging out of the shell, and mounting -file systems inside it is considered harmful. -

2. Running little programs inside the chroot

- To facilitate using pbuilder for other uses, -pbuilder execute is available. pbuilder execute - will take a script specified in the command-line argument, and -invoke the script inside the chroot. -

- The script can be useful for sequences of operations such as installing ssh -and adding a new user inside the chroot. -

第7章 Experimental or wishlist features of pbuilder

目次

1. LVMの活用
2. cowdancer の活用
3. tar.gz を利用しないで pbuilder を利用する
4. pbuilder を vserver で利用する
5. Usage of ccache

- There are some advanced features, above that of the basic feature of -pbuilder, for some specific purposes. -

1. LVMの活用

- LVM2 has a useful snapshot function that features Copy-on-write images. -That could be used for pbuilder just as it can be used -for the user-mode-linux pbuilder port. lvmpbuilder -script in the examples directory implements such port. The scripts and -documentation can be found under -/usr/share/doc/pbuilder/examples/lvmpbuilder/. -

2. cowdancer の活用

- cowdancer allows copy-on-write semantics on file system -using hard links and hard-link-breaking-on-write tricks. -pbuilder using cowdancer seems to be -much faster and it is one ideal point for improvement. -cowbuilder, a wrapper for pbuilder for -using cowdancer is available from -cowdancer package since 0.14 -

- Example command-lines for cowbuilder look like the following. -

- 

-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc

-

- It is also possible to use cowdancer with pdebuild command. Specify with -command-line option --pbuilder or set it in -PDEBUILD_PBUILDER configuration option. -

- 

-$ pdebuild --pbuilder cowbuilder

-

3. tar.gz を利用しないで pbuilder を利用する

- The --no-targz option of -pbuilder will allow usage of pbuilder -in a different way from conventional usage. It will try to use an existing -chroot, and will not try to clean up after working on it. It is an -operation mode more like sbuild. -

- It should be possible to create base chroot images for -dchroot with the following commands: 

-# pbuilder create --distribution lenny --no-targz --basetgz /chroot/lenny
-# pbuilder create --distribution squeeze --no-targz --basetgz /chroot/squeeze
-# pbuilder create --distribution sid --no-targz --basetgz /chroot/sid

-

4. pbuilder を vserver で利用する

- It is possible to use pbuilder in a vserver environment. -This requires either vserver-patches in version 2.1.1-rc14 or higher, or a -Linux kernel version 2.6.16 or higher. -

- To use pbuilder in a vserver, you need to set the -secure_mount CAPS in the -ccapabilities of this vserver. -

5. Usage of ccache

- It is possible to use C compiler cache ccache to speed up -repeated builds of the same package (or packages that compile the same files -multiple times for some reason). Using ccache can speed -up repeated building of large packages dramatically, at the cost of some -disk space and bookkeeping. -

- To enable usage of ccache with -pbuilder, you should set CCACHEDIR in your pbuilderrc -file. -

- Current implementation of ccache support has several bugs, that CCACHEDIR -must be owned by the pbuilder build user, and parallel runs of pbuilder is -not supported. Therefore it is not enabled by default. -

第8章 参考文献

目次

1. chroot 外部のディレクトリ構造
2. chroot 内部のディレクトリ構造

1. chroot 外部のディレクトリ構造

表8.1 chroot 内部のディレクトリ構造

ディレクトリ意味
/etc/pbuilderrc設定ファイル
/usr/share/pbuilder/pbuilderrcデフォルト設定
/var/cache/pbuilder/base.tgzDefault location pbuilder uses for base.tgz, the tar-ball containing a basic -Debian installation with only the build-essential packages. -
/var/cache/pbuilder/build/PID/pbuilder がデフォルトでchroot のために利用する場所
/var/cache/pbuilder/aptcacheDefault location pbuilder will use as apt cache, to store -deb packages required during pbuilder build.
/var/cache/pbuilder/ccacheDefault location pbuilder will use as cache location
/var/cache/pbuilder/resultDefault location pbuilder puts the deb files and other -files created after build
/var/cache/pbuilder/pbuilder-umlresultDefault location pbuilder-user-mode-linux puts the deb -files and other files created after build
/var/cache/pbuilder/pbuilder-mntDefault location pbuilder-user-mode-linux uses for -mounting the COW file system, for chrooting.
/tmppbuilder-user-mode-linux will mount tmpfs for work.
${HOME}/tmp/PID.cowpbuilder-user-mode-linux use this directory for location -of COW file system.
${HOME}/uml-imagepbuilder-user-mode-linux use this directory for -user-mode-linux full disk image.

2. chroot 内部のディレクトリ構造

表8.2 chroot 内部のディレクトリ構造

ディレクトリ意味
/etc/mtab - /proc/mountsへのシンボリックリンク。 -
/tmp/builddDefault place used in pbuilder to place the Debian -package to be processed. -/tmp/buildd/packagename-version/ will be the root -directory of the package being processed. HOME environment variable is set -to this value inside chroot by pbuilder-buildpackage. ---inputfile will place files here. -
/runscriptThe script passed as an argument to pbuilder execute is -passed on. -
/tmp/hooks - フックの場所。 -
/var/cache/apt/archives - pbuilder は chroot 外部の aptcache ディレクトリからコピーしてきたり、chroot -外部の aptcache ディレクトリへコピーしたりします。 -
/var/cache/pbuilder/ccache - pbuilder bind-mounts this directory for use by ccache. -
/tmp/XXXXpbuilder-user-mode-linux は /tmp -のスクリプトを利用して user-mode-linux にブートストラップします。

第9章 些細な過去の経緯の詳細

目次

1. マニュアルの履歴
2. Possibly inaccurate Background History of pbuilder
2.1. The Time Before pbuilder
2.2. pbuilder の誕生
2.3. そして二年目の人生
2.4. pbuilder の5年目

1. マニュアルの履歴

- This document was started on 28 Dec 2002 by Junichi Uekawa, trying to -document what is known about pbuilder. -

- This documentation is available from the pbuilder source -tar-ball, and from the git repository of pbuilder -(web-based access is possible). A copy of this documentation can be found -on the Alioth project -page for pbuilder. There is also a PDF -version. The homepage for pbuilder is http://pbuilder.alioth.debian.org/ - hosted by alioth project. -

- Documentation is written using DocBook XML, with emacs PSGML mode, and using -wysidocbookxml for live previewing. -

2. Possibly inaccurate Background History of pbuilder

- The following is a most possibly inaccurate account of how -pbuilder came to happen, and other attempts to make -something like pbuilder happen. This part of the -document was originally in the AUTHORS file, to give credit to those who -existed before pbuilder. -

2.1. The Time Before pbuilder

- There was once dbuild, which was a shell script to build Debian packages -from source. Lars Wirzenius wrote that script, and it was good, short, and -simple (probably). There was nothing like build-depends then (I think), and -it was simple. It could have been improved, I could only find references -and no actual source. -

- debbuild was probably written by James Troup. I don't know it because I have -never seen the actual code, I could only find some references to it on the -net, and mailing list logs. -

- sbuild is a perl script to build Debian packages from source. It parses -Build-Depends, and performs other miscellaneous checks, and has a lot of -hacks to actually get things building, including a table of what package to -use when virtual packages are specified (does it do that still?). It -supports the use of a local database for packages which do not have -build-dependencies. It was written by Ronan Hodek, and I think it was -patched and fixed and extended by several people. It is part of wanna-build, -and used extensively in the Debian buildd system. I think it was maintained -mostly by Ryan Murray. -

2.2. pbuilder の誕生

- wanna-build (sbuild) was (at the time of year 2001) quite difficult to set -up, and it was never a Debian package. dbuild was something that predated -Build-Depends. -

- Building packages from source using Build-Depends information within a -chroot sounded trivial; and pbuilder was born. It was -initially a shell script with only a few lines, which called debootstrap and -chroot and dpkg-buildpackage in the same run, but soon, it was decided that -that's too slow. -

- Yes, and it took almost an year to get things somewhat right, and in the -middle of the process, Debian 3.0 was released. Yay. Debian 3.0 wasn't -completely buildable with pbuilder, but the amount of -packages which are not buildable is steadily decreasing (I hope). -

2.3. そして二年目の人生

- Someone wanted pbuilder to not run as root, and as -User-mode-linux has become more useful as time passed, I've started -experimenting with pbuilder-user-mode-linux. -pbuilder-user-mode-linux has not stayed functional as -much as I would have liked, and bootstrapping -user-mode-linux environment has been pretty hard, due to -the quality of user-mode-linux code or packaging at that time, which kept on -breaking network support in one way or the other. -

2.4. pbuilder の5年目

- pbuilder is now widely adopted as a 'almost standard' -tool for testing packages, and building packages in a pristine environment. -There are other similar tools that do similar tasks, but they do not share -the exact same goal. To commemorate this fact, pbuilder -is now co-maintained with several people. -

- sbuild is now a well-maintained Debian package within -Debian, and with pbuilder being such a slow monster, some -people prefer the approach of sbuild. Development to use LVM-snapshots, -cowloop, or cowdancer is hoped to improve the situation somewhat. -

diff -Nru pbuilder-0.215ubuntu7/examples/D65various-compiler-support pbuilder-0.215+nmu4ubuntu1~ppa1/examples/D65various-compiler-support --- pbuilder-0.215ubuntu7/examples/D65various-compiler-support 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/examples/D65various-compiler-support 2015-06-22 08:05:23.000000000 +0000 @@ -37,11 +37,6 @@ newcxx=/bin/false not_gcc_compat=1 ;; - asn1c) - newcc=/usr/bin/"${CHOOSE_COMPILER}" - newcxx=/bin/false - not_gcc_compat=1 - ;; *) exit 0 ;; diff -Nru pbuilder-0.215ubuntu7/Makefile pbuilder-0.215+nmu4ubuntu1~ppa1/Makefile --- pbuilder-0.215ubuntu7/Makefile 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/Makefile 2015-06-22 16:04:04.000000000 +0000 @@ -19,7 +19,7 @@ NULL := ALLDIRS += BASHCOMPLETION -BASHCOMPLETIONDIR := $(SYSCONFDIR)/bash_completion.d +BASHCOMPLETIONDIR := $(PKGDATADIR)/../bash-completion/completions/ BASHCOMPLETION_DATA += \ bash_completion.d/pbuilder \ $(NULL) @@ -58,6 +58,7 @@ pbuilder-satisfydepends-gdebi \ pbuilder-selftest \ pbuilder-uml-checkparams \ + pbuilder-unshare-wrapper \ pbuilder-updatebuildenv \ pdebuild-checkparams \ pdebuild-internal \ @@ -189,8 +190,10 @@ clean: rm -f *.bak *~ TAGS - rm -f testsuite/testimage - rm -rf testsuite/testbuild testsuite/testbuild2 + rm -rfv testsuite/testimage \ + testsuite/testbuild \ + testsuite/testbuild2 \ + testsuite/regression/work $(MAKE) -C pbuildd $@ $(MAKE) -C Documentation $@ diff -Nru pbuilder-0.215ubuntu7/patches/hoge.diff pbuilder-0.215+nmu4ubuntu1~ppa1/patches/hoge.diff --- pbuilder-0.215ubuntu7/patches/hoge.diff 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/patches/hoge.diff 1970-01-01 00:00:00.000000000 +0000 @@ -1,88 +0,0 @@ -diff -Nru pbuilder-0.199+nmu2/debian/changelog pbuilder-0.199+nmu3/debian/changelog ---- pbuilder-0.199+nmu2/debian/changelog 2011-02-19 20:02:35.000000000 +0100 -+++ pbuilder-0.199+nmu3/debian/changelog 2011-03-29 23:00:24.000000000 +0200 -@@ -1,3 +1,11 @@ -+pbuilder (0.199+nmu3) unstable; urgency=low -+ -+ * Non-Maintainer Upload. -+ * Apply patches provided by Gonéri Le Bouder to allow pbuilder to -+ create and manage chroots on kFreeBSD machines (Closes: #542837). -+ -+ -- Luca Falavigna Tue, 29 Mar 2011 22:56:44 +0200 -+ - pbuilder (0.199+nmu2) unstable; urgency=low - - * Non-maintainer upload with maintainer's permission. -diff -Nru pbuilder-0.199+nmu2/pbuilder-modules pbuilder-0.199+nmu3/pbuilder-modules ---- pbuilder-0.199+nmu2/pbuilder-modules 2010-12-28 05:29:34.000000000 +0100 -+++ pbuilder-0.199+nmu3/pbuilder-modules 2011-03-28 23:56:00.000000000 +0200 -@@ -201,6 +201,7 @@ - function umountproc () { - # push arguments on a stack to reverse direction. - local reversed -+ DEB_BUILD_ARCH_OS=$(dpkg-architecture -qDEB_BUILD_ARCH_OS) - reversed= - for mnt in $BINDMOUNTS; do - reversed="$mnt $reversed" -@@ -211,18 +212,21 @@ - if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then - umount_one "selinux" - fi -- if [ "$USEDEVPTS" = "yes" ]; then -+ if [ "$DEB_BUILD_ARCH_OS" = "linux" ] && [ "$USEDEVPTS" = "yes" ]; then - umount_one "dev/pts" - fi - if [ "$USEDEVFS" = "yes" ]; then - umount_one "dev" - fi - if [ "$USEPROC" = "yes" ]; then -- if [ -e $BUILDPLACE/proc/sys/fs/binfmt_misc/status ]; then -+ if [ "$DEB_BUILD_ARCH_OS" = "linux" ] && [ -e $BUILDPLACE/proc/sys/fs/binfmt_misc/status ]; then - umount_one "proc/sys/fs/binfmt_misc" - fi - umount_one "proc" - fi -+ if [ "$DEB_BUILD_ARCH_OS" = "kfreebsd" ]; then -+ umount_one "sys" -+ fi - } - - -@@ -230,10 +234,13 @@ - # Also create a policy-rc.d script if it doesn't already exist. - function mountproc () { - local -a mounted -+ DEB_BUILD_ARCH_OS=$(dpkg-architecture -qDEB_BUILD_ARCH_OS) - if [ "$USEPROC" = "yes" ]; then - log "I: mounting /proc filesystem" - mkdir -p $BUILDPLACE/proc -- mount -t proc /proc "$BUILDPLACE/proc" -+ PROCFS="proc" -+ [ "$DEB_BUILD_ARCH_OS" = "kfreebsd" ] && PROCFS="linprocfs" -+ mount -t $PROCFS /proc "$BUILDPLACE/proc" - ln -s ../proc/mounts $BUILDPLACE/etc/mtab 2> /dev/null || true - mounted[${#mounted[@]}]="$BUILDPLACE/proc" - fi -@@ -243,7 +250,7 @@ - mount -t devfs /dev "$BUILDPLACE/dev" - mounted[${#mounted[@]}]="$BUILDPLACE/dev" - fi -- if [ "$USEDEVPTS" = "yes" ]; then -+ if [ "$DEB_BUILD_ARCH_OS" = "linux" ] && [ "$USEDEVPTS" = "yes" ]; then - log "I: mounting /dev/pts filesystem" - mkdir -p $BUILDPLACE/dev/pts || true - TTYGRP=5 -@@ -258,10 +265,12 @@ - mount -t selinuxfs /selinux "$BUILDPLACE/selinux" - mounted[${#mounted[@]}]="$BUILDPLACE/selinux" - fi -+ MOUNTPARAMS="-obind" -+ [ "$DEB_BUILD_ARCH_OS" = "kfreebsd" ] && MOUNTPARAMS="-t nullfs" - for mnt in $BINDMOUNTS; do - log "I: Mounting $mnt" - if mkdir -p "$BUILDPLACE/$mnt" && -- mount -obind "$mnt" "$BUILDPLACE/$mnt"; then -+ mount $MOUNTPARAMS "$mnt" "$BUILDPLACE/$mnt"; then - # successful. - mounted[${#mounted[@]}]="$mnt" - else diff -Nru pbuilder-0.215ubuntu7/patches/nmu4 pbuilder-0.215+nmu4ubuntu1~ppa1/patches/nmu4 --- pbuilder-0.215ubuntu7/patches/nmu4 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/patches/nmu4 1970-01-01 00:00:00.000000000 +0000 @@ -1,466 +0,0 @@ -From pbuilder-maint-bounces+dancer=netfort.gr.jp@lists.alioth.debian.org Thu May 26 21:12:27 2011 -Return-Path: -X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on vaiop.dancer.pr.jp -X-Spam-Level: *** -X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_50,RDNS_NONE - autolearn=no version=3.3.1 -Delivered-To: dancer@netfort.gr.jp -Received: (qmail 21866 invoked by uid 0); 26 May 2011 21:12:26 -0000 -Received: from unknown (HELO wagner.debian.org) (217.196.43.132) - by aegis.netfort.gr.jp with SMTP; 26 May 2011 21:12:26 -0000 -Received: from localhost ([::1] helo=alioth.debian.org) - by wagner.debian.org with esmtp (Exim 4.72) - (envelope-from ) - id 1QPhrD-000289-9H - for dancer@netfort.gr.jp; Thu, 26 May 2011 21:12:39 +0000 -Received: from busoni.debian.org ([140.211.15.34]) - by wagner.debian.org with esmtp (Exim 4.72) - (envelope-from ) id 1QPhrA-000281-IV - for pbuilder-maint@lists.alioth.debian.org; - Thu, 26 May 2011 21:12:37 +0000 -Received: from debbugs by busoni.debian.org with local (Exim 4.72) - (envelope-from ) - id 1QPhqe-0000py-Jl; Thu, 26 May 2011 21:12:04 +0000 -X-Loop: owner@bugs.debian.org -Subject: Bug#400848: pbuilder: diff for NMU version 0.199+nmu4 -Resent-From: Thorsten Glaser -Resent-To: debian-bugs-dist@lists.debian.org -Resent-CC: Debian pbuilder maintenance team - -X-Loop: owner@bugs.debian.org -Resent-Date: Thu, 26 May 2011 21:12:02 +0000 -Resent-Message-ID: -X-Debian-PR-Message: followup 400848 -X-Debian-PR-Package: pbuilder -X-Debian-PR-Keywords: pending -X-Debian-PR-Source: pbuilder -Received: via spool by 400848-submit@bugs.debian.org id=B400848.13064441782813 - (code B ref 400848); Thu, 26 May 2011 21:12:02 +0000 -Received: (at 400848) by bugs.debian.org; 26 May 2011 21:09:38 +0000 -Received: from static-87-79-237-121.netcologne.de - ([87.79.237.121] helo=herc.mirbsd.org ident=root) - by busoni.debian.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) - (Exim 4.72) (envelope-from ) - id 1QPho6-0000is-1B; Thu, 26 May 2011 21:09:31 +0000 -Received: from herc.mirbsd.org (tg@localhost [IPv6:::1]) - by herc.mirbsd.org (8.14.5.Beta0/8.14.5.Beta0) with ESMTP id - p4QL8dHB031212 - (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); - Thu, 26 May 2011 21:08:43 GMT -Received: (from tg@localhost) - by herc.mirbsd.org (8.14.5.Beta0/8.14.5.Beta0/Submit) id p4QL8dNu009529; - Thu, 26 May 2011 21:08:39 GMT -Received: by S/MIME Plugin for MirBSD 10 Kv#10uAE-20110220 i386; - Thu May 26 21:08:38 UTC 2011 -Date: Thu, 26 May 2011 21:08:37 +0000 (UTC) -From: Thorsten Glaser -X-X-Sender: tg@herc.mirbsd.org -To: 620730@bugs.debian.org, 626431@bugs.debian.org, 627086@bugs.debian.org, - 603420@bugs.debian.org, 601250@bugs.debian.org, 603881@bugs.debian.org, - 400848@bugs.debian.org, 622624@bugs.debian.org -Message-ID: -X-Message-Flag: Your mailer is broken. Get an update at - http://www.washington.edu/pine/getpine/pcpine.html for free. -MIME-Version: 1.0 -Content-Type: MULTIPART/MIXED; BOUNDARY="0-422438018-1306444141=:6597" -Resent-Sender: Debian BTS -x-debian-approved: yes -Cc: control@bugs.debian.org -X-BeenThere: pbuilder-maint@lists.alioth.debian.org -X-Mailman-Version: 2.1.13 -Precedence: list -Reply-To: Thorsten Glaser , 400848@bugs.debian.org -List-Id: Development mailing list for pbuilder - -List-Unsubscribe: , - -List-Archive: -List-Post: -List-Help: -List-Subscribe: , - -Sender: pbuilder-maint-bounces+dancer=netfort.gr.jp@lists.alioth.debian.org -Errors-To: pbuilder-maint-bounces+dancer=netfort.gr.jp@lists.alioth.debian.org -X-SA-Exim-Connect-IP: ::1 -X-SA-Exim-Mail-From: pbuilder-maint-bounces+dancer=netfort.gr.jp@lists.alioth.debian.org -X-SA-Exim-Scanned: No (on wagner.debian.org); SAEximRunCond expanded to false - - This message is in MIME format. The first part should be readable text, - while the remaining parts are likely unreadable without MIME-aware tools. - ---0-422438018-1306444141=:6597 -Content-Type: TEXT/PLAIN; charset=utf-8 -Content-Transfer-Encoding: QUOTED-PRINTABLE - ------BEGIN PGP SIGNED MESSAGE----- -Hash: SHA384 - -tags 620730 + patch pending -tags 626431 + patch pending -tags 627086 + patch pending -tags 603420 + patch pending -tags 601250 + patch pending -tags 603881 =3D unreproducible -tags 400848 =3D unreproducible -tags 622624 =3D unreproducible -thanks - -Dear Junichi, Matt and others, - -I=E2=80=99ve prepared an NMU for pbuilder (versioned as 0.199+nmu4) and upl= -oaded -it to Debian unstable, with a two-day delay as per devref =C2=A75.11.1 sinc= -e -this fixes an RC bug older than seven days. The debdiff is attached; it -closes five bugs. I=E2=80=99m also tagging three other bugs as unreproducib= -le as -pbuilder itself (obviously) doesn=E2=80=99t FTBFS on my system and the test= - pak- -kage I used didn=E2=80=99t exhibit problems with either comment blocks or h= -ori- -zontal tabulator characters in the control file. I=E2=80=99m also attaching= - the -test package (absolutely minimal, but that=E2=80=99s what you get). - -I mostly used patches from the bugs closed as baseline for my changes, -but did a bit more usually. I=E2=80=99m a heavy user of cowbuilder, because= - on -m68k there=E2=80=99s currently no buildd and cowbuilder is all I know (and = -love, -really=E2=80=A6 someone should make a buildd flavour that uses cowbuilder i= -n- -stead of sbuild, if it goes by my will). - -Cheers. -//mirabilos -- --=20 -I believe no one can invent an algorithm. One just happens to hit upon it -when God enlightens him. Or only God invents algorithms, we merely copy the= -m. -If you don't believe in God, just consider God as Nature if you won't deny -existence.=09=09-- Coywolf Qi Hunt ------BEGIN PGP SIGNATURE----- -Version: GnuPG v1.4.7 (MirBSD) - -iQIVAwUBTd7A/Xa1NLLpkAfgAQlWfQ/+LBSpx3E2TIbR68uHpVUYBdlzocMS0pGm -6a1aL3EPXfSe/Z20ikbMmXUQ2O7AV3imLgxb1bgkQsWMTDWalvma6gXN5jVzX/Sr -upB0MOhCqC6cCj3vmpXXdAH45cnk0unYSbC7FIwgYqFlrOIPn9thU0YzRlTKpM6O -0Hkc3gZ2GsTWNVMVMzl27z3ptxN0NPuyEEQhInYiVt+bLbQSosVGgAmrKEYTf9dV -qp3fG35ZiXG3RCLDWdAAq138+2SFtIGM1DNkTT9XiwUtMwnkqrqrl327BZJBxbs4 -wmdU3kDg72rCu07tZDa8pFbamb0TEoZKDu6lHAuig4OGXXmUh60xthbAR+VRk4+j -QuPklRXCOw0mOvNCtcTqeD2qKfzZ+RyOsOQmteayrym0ozUjzk5meeFUgcKDHAHN -r9KfAxfuy9+QwVpNoAp+rc/cB6kmwjEgOQSJJpcmOEq3rorng3ybWTDFL//q/sMU -Edg3gwuWoCQjR59GTdmMnRoUOq6nA2jUvxZK/m3rhQTfXXd7wO1IiAxYNnGzKDOV -u1lVGxU4XCApcaB0gAEefKzEOKBhtLUqd6PWjVbcDbQrDTfblIOsResoKoUQF68y -o2Fjx6M3OPYOMvwq7cdO2P37Euzm1CNg4SSry3KyZSdT9lo2onbIhYGd9wds0HGt -9LO14P1nmXI=3D -=3D7BsQ ------END PGP SIGNATURE----- ---0-422438018-1306444141=:6597 -Content-Type: TEXT/PLAIN; charset=US-ASCII; name=pbuilder_0.199+nmu4.debdiff -Content-Transfer-Encoding: BASE64 -Content-ID: -Content-Description: -Content-Disposition: attachment; filename=pbuilder_0.199+nmu4.debdiff - -ZGlmZiAtTnJ1IHBidWlsZGVyLTAuMTk5K25tdTMvRG9jdW1lbnRhdGlvbi9w -YnVpbGRlci1kb2MueG1sIHBidWlsZGVyLTAuMTk5K25tdTQvRG9jdW1lbnRh -dGlvbi9wYnVpbGRlci1kb2MueG1sDQotLS0gcGJ1aWxkZXItMC4xOTkrbm11 -My9Eb2N1bWVudGF0aW9uL3BidWlsZGVyLWRvYy54bWwJMjAxMC0wMS0wMyAw -MjozODowOS4wMDAwMDAwMDAgKzAwMDANCisrKyBwYnVpbGRlci0wLjE5OStu -bXU0L0RvY3VtZW50YXRpb24vcGJ1aWxkZXItZG9jLnhtbAkyMDExLTA1LTI2 -IDIwOjI1OjI5LjAwMDAwMDAwMCArMDAwMA0KQEAgLTE2MDksNyArMTYwOSw3 -IEBADQogCSAgICAgIDwvZW50cnk+DQogCSAgICA8L3Jvdz4NCiAJICAgIDxy -b3c+DQotCSAgICAgIDxlbnRyeT48ZmlsZW5hbWU+L3J1bjwvZmlsZW5hbWU+ -PC9lbnRyeT4gDQorCSAgICAgIDxlbnRyeT48ZmlsZW5hbWU+L3J1bnNjcmlw -dDwvZmlsZW5hbWU+PC9lbnRyeT4gDQogCSAgICAgIDxlbnRyeT5UaGUNCiAJ -ICAgICAgc2NyaXB0IHBhc3NlZCBhcyBhbiBhcmd1bWVudCB0bw0KIAkgICAg -ICA8Y29tbWFuZD5wYnVpbGRlcjwvY29tbWFuZD4gZXhlY3V0ZSBpcyBwYXNz -ZWQgb24uDQpkaWZmIC1OcnUgcGJ1aWxkZXItMC4xOTkrbm11My9kZWJpYW4v -Y2hhbmdlbG9nIHBidWlsZGVyLTAuMTk5K25tdTQvZGViaWFuL2NoYW5nZWxv -Zw0KLS0tIHBidWlsZGVyLTAuMTk5K25tdTMvZGViaWFuL2NoYW5nZWxvZwky -MDExLTA0LTA4IDIzOjM2OjI1LjAwMDAwMDAwMCArMDAwMA0KKysrIHBidWls -ZGVyLTAuMTk5K25tdTQvZGViaWFuL2NoYW5nZWxvZwkyMDExLTA1LTI2IDIw -OjUwOjM2LjAwMDAwMDAwMCArMDAwMA0KQEAgLTEsMyArMSwxNyBAQA0KK3Bi -dWlsZGVyICgwLjE5OStubXU0KSB1bnN0YWJsZTsgdXJnZW5jeT1sb3cNCisN -CisgICogTm9uLW1haW50YWluZXIgdXBsb2FkLg0KKyAgKiBSZW5hbWUgdGhl -IC9ydW4gc2NyaXB0IGZyb20gLS1leGVjdXRlIHRvIC9ydW5zY3JpcHQ7IG5v -dCB1c2luZw0KKyAgICBta3RlbXAgZm9yIGNvbnNpc3RlbmN5IHdpdGggdGhl -IGRvY3VtZW50YXRpb24uIChDbG9zZXM6ICM2MjcwODYpDQorICAqIEhhbmRs -ZSBhcmNoaXRlY3R1cmUgd2lsZGNhcmRzIHdpdGggbW9yZSB0aGFuIG9uZSBh -cmNoaXRlY3R1cmUuDQorICAgIChDbG9zZXM6ICM2MjA3MzApIChDbG9zZXM6 -ICM2MjY0MzEpDQorICAqIEZpeCBwYnVpbGRlcnJjKDUpIGZvcm1hdHRpbmcu -IChDbG9zZXM6ICM2MDM0MjApDQorICAqIEZpeCBwYnVpbGRlci1zYXRpc2Z5 -ZGVwZW5kcy1jbGFzc2ljIG91dHB1dCwgaW5jbHVkaW5nIGJldHRlciBsaW5l -DQorICAgIGJyZWFrcyBhbmQgaHlwaGVuLXVzZWQtYXMtbWludXMtc2lnbiBs -aW50aWFuLiAoQ2xvc2VzOiAjNjAxMjUwKQ0KKyAgKiBQbGVhc2UgbGludGlh -bjogYWRkIGRlYmlhbi9zb3VyY2UvZm9ybWF0Lg0KKw0KKyAtLSBUaG9yc3Rl -biBHbGFzZXIgPHRnQG1pcmJzZC5kZT4gIFRodSwgMjYgTWF5IDIwMTEgMjA6 -NDk6MDQgKzAwMDANCisNCiBwYnVpbGRlciAoMC4xOTkrbm11MykgdW5zdGFi -bGU7IHVyZ2VuY3k9bG93DQogDQogICAqIE5vbi1NYWludGFpbmVyIFVwbG9h -ZC4NCmRpZmYgLU5ydSBwYnVpbGRlci0wLjE5OStubXUzL2RlYmlhbi9zb3Vy -Y2UvZm9ybWF0IHBidWlsZGVyLTAuMTk5K25tdTQvZGViaWFuL3NvdXJjZS9m -b3JtYXQNCi0tLSBwYnVpbGRlci0wLjE5OStubXUzL2RlYmlhbi9zb3VyY2Uv -Zm9ybWF0CTE5NzAtMDEtMDEgMDA6MDA6MDAuMDAwMDAwMDAwICswMDAwDQor -KysgcGJ1aWxkZXItMC4xOTkrbm11NC9kZWJpYW4vc291cmNlL2Zvcm1hdAky -MDExLTA1LTI2IDIwOjQyOjI0LjAwMDAwMDAwMCArMDAwMA0KQEAgLTAsMCAr -MSBAQA0KKzEuMA0KZGlmZiAtTnJ1IHBidWlsZGVyLTAuMTk5K25tdTMvcGJ1 -aWxkZXIgcGJ1aWxkZXItMC4xOTkrbm11NC9wYnVpbGRlcg0KLS0tIHBidWls -ZGVyLTAuMTk5K25tdTMvcGJ1aWxkZXIJMjAwOS0wMy0wNyAwMToyODo1MS4w -MDAwMDAwMDAgKzAwMDANCisrKyBwYnVpbGRlci0wLjE5OStubXU0L3BidWls -ZGVyCTIwMTEtMDUtMjYgMjA6MjY6MDcuMDAwMDAwMDAwICswMDAwDQpAQCAt -MTE2LDExICsxMTYsMTEgQEANCiAJcmVjb3Zlcl9hcHRjYWNoZQ0KIAl0cmFw -IHNhdmVhcHRjYWNoZV91bW91bnRwcm9jX2NsZWFuYnVpbGRwbGFjZV90cmFw -IGV4aXQgc2lnaHVwDQogDQotCVJVTk5BTUU9IiRCVUlMRFBMQUNFL3J1biIN -CisJUlVOTkFNRT0iJEJVSUxEUExBQ0UvcnVuc2NyaXB0Ig0KIAljYXQgIiRF -WEVDUFJPR1JBTSIgPiAiJFJVTk5BTUUiDQogCWNobW9kIGEreCAiJFJVTk5B -TUUiDQogCWV4ZWN1dGVob29rcyAiRiINCi0JKCAke0NIUk9PVEVYRUN9IC9y -dW4gIiRAIiApDQorCSggJHtDSFJPT1RFWEVDfSAvcnVuc2NyaXB0ICIkQCIg -KQ0KIAlSRVQ9JD8NCiAJcm0gLWYgIiRSVU5OQU1FIg0KIA0KZGlmZiAtTnJ1 -IHBidWlsZGVyLTAuMTk5K25tdTMvcGJ1aWxkZXItc2F0aXNmeWRlcGVuZHMt -Y2xhc3NpYyBwYnVpbGRlci0wLjE5OStubXU0L3BidWlsZGVyLXNhdGlzZnlk -ZXBlbmRzLWNsYXNzaWMNCi0tLSBwYnVpbGRlci0wLjE5OStubXUzL3BidWls -ZGVyLXNhdGlzZnlkZXBlbmRzLWNsYXNzaWMJMjAxMC0wNy0wNSAxMzowOToy -OS4wMDAwMDAwMDAgKzAwMDANCisrKyBwYnVpbGRlci0wLjE5OStubXU0L3Bi -dWlsZGVyLXNhdGlzZnlkZXBlbmRzLWNsYXNzaWMJMjAxMS0wNS0yNiAyMDo0 -MjowNS4wMDAwMDAwMDAgKzAwMDANCkBAIC03MCw3ICs3MCw3IEBADQogICAg -IGxvY2FsIEFQVEZMQUc9Ii1vIEFQVDo6SW5zdGFsbC1SZWNvbW1lbmRzPWZh -bHNlIg0KICAgICBlY2hvICIgLT4gQXR0ZW1wdGluZyB0byBwYXJzZSB0aGUg -YnVpbGQtZGVwcyAiDQogICAgIGZvciBJTlNUQUxMUEtHTVVMVEkgaW4gJChn -ZXRfYnVpbGRfZGVwcyB8IHNwbGl0X2RlcHMpOyBkbw0KLSAgICAgIGVjaG8g -IiAtPiBDb25zaWRlcmluZyBidWlsZC1kZXAkKGVjaG8gIiRJTlNUQUxMUEtH -TVVMVEkiIHwgdHIgIi8iICIgIiApIg0KKyAgICAgIGVjaG8gIiAtPiBDb25z -aWRlcmluZyBidWlsZC1kZXAgJChlY2hvICIkSU5TVEFMTFBLR01VTFRJIiB8 -IHRyICIvIiAiICIpIg0KICAgICAgIFNBVElTRklFRD0ibm8iDQogICAgICAg -Zm9yIElOU1RBTExQS0cgaW4gJChzcGxpdF9hbHRlcm5hdGVzICIkSU5TVEFM -TFBLR01VTFRJIik7IGRvDQogCUNVUlJFTlRSRUFMUEtHTkFNRT0kKGdldF9w -a2dfbmFtZSAiJElOU1RBTExQS0ciKQ0KZGlmZiAtTnJ1IHBidWlsZGVyLTAu -MTk5K25tdTMvcGJ1aWxkZXItc2F0aXNmeWRlcGVuZHMtZnVuY3MgcGJ1aWxk -ZXItMC4xOTkrbm11NC9wYnVpbGRlci1zYXRpc2Z5ZGVwZW5kcy1mdW5jcw0K -LS0tIHBidWlsZGVyLTAuMTk5K25tdTMvcGJ1aWxkZXItc2F0aXNmeWRlcGVu -ZHMtZnVuY3MJMjAxMS0wMi0xOSAxODoxNjo0NC4wMDAwMDAwMDAgKzAwMDAN -CisrKyBwYnVpbGRlci0wLjE5OStubXU0L3BidWlsZGVyLXNhdGlzZnlkZXBl -bmRzLWZ1bmNzCTIwMTEtMDUtMjYgMjA6Mjk6MTQuMDAwMDAwMDAwICswMDAw -DQpAQCAtMTIyLDcgKzEyMiw3IEBADQogICAgIGxvY2FsIElOU1RBTExQS0c9 -IiQxIg0KICAgICBsb2NhbCBBUkNIPSIkMiINCiAgICAgIyBhcmNoaXRlY3R1 -cmVzIGxpc3RlZCBiZXR3ZWVuIFsgYW5kIF0gZm9yIHRoaXMgZGVwDQotICAg -IGxvY2FsIERFUF9BUkNIRVM9IiQoZWNobyAiJElOU1RBTExQS0ciIHwgc2Vk -ICdzLy4qXFtcKC4qXClcXS4qL1wxLycpIg0KKyAgICBsb2NhbCBERVBfQVJD -SEVTPSIkKGVjaG8gIiRJTlNUQUxMUEtHIiB8IHNlZCAtZSAncy8uKlxbXCgu -KlwpXF0uKi9cMS8nIC1lICd5fC98IHwnKSINCiAgICAgbG9jYWwgUEtHPSIk -KGVjaG8gIiRJTlNUQUxMUEtHIiB8IGN1dCAtZCAnICcgLWYgMSkiDQogICAg -IGxvY2FsIFVTRV9JVA0KICAgICBsb2NhbCBJR05PUkVfSVQNCmRpZmYgLU5y -dSBwYnVpbGRlci0wLjE5OStubXUzL3BidWlsZGVycmMuNSBwYnVpbGRlci0w -LjE5OStubXU0L3BidWlsZGVycmMuNQ0KLS0tIHBidWlsZGVyLTAuMTk5K25t -dTMvcGJ1aWxkZXJyYy41CTIwMTAtMDctMDUgMTM6MTQ6MDMuMDAwMDAwMDAw -ICswMDAwDQorKysgcGJ1aWxkZXItMC4xOTkrbm11NC9wYnVpbGRlcnJjLjUJ -MjAxMS0wNS0yNiAyMDo0ODozMi4wMDAwMDAwMDAgKzAwMDANCkBAIC0zMyw3 -ICszMyw3IEBADQogdG8gdGFrZSBlZmZlY3QuDQogU2V0dGluZyB0aGlzIHZh -cmlhYmxlIG92ZXJyaWRlcyBvdGhlciBvcHRpb25zLg0KIC5UUA0KLS5CSSAi -QVJDSElURUNUVVJFPSIgImBkcGtnIC0tcHJpbnQtYXJjaGl0ZWN0dXJlYCIN -CisuQkkgIkFSQ0hJVEVDVFVSRT0iICJgZHBrZyBcLVwtcHJpbnRcLWFyY2hp -dGVjdHVyZWAiDQogU3BlY2lmeSB0aGUgZGVmYXVsdCBkaXN0cmlidXRpb24g -dG8gdXNlLg0KIFRoaXMgb3B0aW9uIG9ubHkgYWZmZWN0cyB3aGVuIGRvaW5n -DQogLkIgInBidWlsZGVyIGNyZWF0ZSINCkBAIC01MiwxMiArNTIsMTMgQEAN -CiBTcGVjaWZpZXMgdGhlIGRlZmF1bHQgbG9jYXRpb24gZm9yIHRoZSBhcmNo -aXZlZA0KIGNocm9vdCBpbWFnZSB0byBiZSBjcmVhdGVkIGFuZCB1c2VkLg0K -IFRoaXMgaXMgb3ZlcnJpZGRlbiB3aXRoIHRoZSBvcHRpb24NCi0uQlIgIi0t -YmFzZXRneiIgIi4iDQorLkJSICJcLVwtYmFzZXRneiIgIi4iDQogLlRQDQog -LkJJICJCSU5ETU9VTlRTPSIgImRpcmVjdG9yaWVzLXRvLWJpbmQtbW91bnQi -DQogV2hlbiB0aGlzIHZhbHVlIGlzIHNldCwgcGJ1aWxkZXIgd2lsbCBtb3Vu -dCB0aGVzZSBkaXJlY3RvcmllcyB1c2luZw0KIGJpbmQtbW91bnQuIERvIG5v -dCBiaW5kLW1vdW50DQogLkIgIi8iDQorLmJyDQogQW4gRXhhbXBsZToNCiAN -CiAuRVgNCkBAIC04OCwxMCArODksMTEgQEANCiBiZSBjb3BpZWQgb3ZlciB0 -byBhZnRlciB0aGUgYnVpbGRpbmcuDQogDQogVW5saWtlDQotLkIgIi0tYnVp -bGRyZXN1bHQiDQorLkIgIlwtXC1idWlsZHJlc3VsdCINCiBjb21tYW5kLWxp -bmUgb3B0aW9uLg0KIFRoZSBwYXRoIGlzIG5vdCBjYW5vbmljYWxpemVkLCBz -byB5b3Ugc2hvdWxkIHNwZWNpZnkgYSBmdWxsLXBhdGgsDQotbm90IGEgcmVs -YXRpdmUgcGF0aC4uVFANCitub3QgYSByZWxhdGl2ZSBwYXRoLg0KKy5UUA0K -IC5CSSAiQ0NBQ0hFRElSPSIgIi92YXIvY2FjaGUvcGJ1aWxkZXIvY2NhY2hl -Ig0KIFNwZWNpZmllcyB3aGVyZSBjY2FjaGUgd2lsbCBrZWVwIGl0cyBjYWNo -ZWQgY29tcGlsZXIgb3V0cHV0Lg0KIElmIHRoaXMgaXMgc3BlY2lmaWVkLCBj -Y2FjaGUgd2lsbCBiZSBpbnN0YWxsZWQgdXBvbiBwYnVpbGRlciBjcmVhdGUg -b3INCkBAIC0xMDAsNyArMTAyLDggQEANCiBzZXQgdG8gQ0NBQ0hFRElSLiAg -Tm90ZSB0aGF0IGZpbGVzIGluIENDQUNIRURJUiBhcmUgY2hvd25lZCB0bw0K -IEJVSUxEVVNFUklEICgxMjM0IGJ5IGRlZmF1bHQpLg0KIC5UUA0KLS5CSSAi -QlVJTERSRVNVTFRVSUQ9Ii5UUA0KKy5CSSAiQlVJTERSRVNVTFRVSUQ9Ig0K -Ky5UUA0KIC5CSSAiQlVJTERSRVNVTFRHSUQ9Ig0KIFNldCB0aGUgVUlEIGFu -ZCBHSUQgb2YgdGhlIGZpbGVzIGJ1aWx0IGFzIHJlc3VsdC4NCiBUaGV5IHBy -b2JhYmx5IG5lZWQgdG8gYmUgc2V0IHRvIG51bWVyaWMgVUlEIHZhbHVlcywN -CkBAIC0xMTcsNyArMTIwLDcgQEANCiAuQkkgIkJVSUxEU09VUkNFUk9PVENN -RD0iICJmYWtlcm9vdCINCiBUaGlzIG9wdGlvbiBpcyB1c2VkIG9uIGludm9j -YXRpb24gb2YgZmFrZXJvb3QNCiBmb3INCi0uQiAiZHBrZy1idWlsZHBhY2th -Z2UiDQorLkIgImRwa2dcLWJ1aWxkcGFja2FnZSINCiBpbg0KIC5CICJwZGVi -dWlsZCINCiAuVFANCkBAIC0xMzUsNyArMTM4LDcgQEANCiBOb3RlIHRoYXQg -dGhpcyB3aWxsIHJlcXVpcmUgZmFrZXJvb3QgdG8gYmUgaW5zdGFsbGVkIHdp -dGhpbg0KIHRoZSBjaHJvb3QsIGFuZCBmYWtlcm9vdCB3aWxsIGF1dG9tYXRp -Y2FsbHkgYmUgaW5zdGFsbGVkLg0KIEFuZA0KLS5CICItcmZha2Vyb290Ig0K -Ky5CICJcLXJmYWtlcm9vdCINCiB3aWxsIGJlIGFkZGVkIHRvDQogLkIgIkRF -QkJVSUxET1BUUyINCiAuVFANCkBAIC0xNDUsMTAgKzE0OCwxMSBAQA0KIFRo -aXMgb3B0aW9uIG9ubHkgYWZmZWN0cyB3aGVuIGRvaW5nDQogLkIgInBidWls -ZGVyIGNyZWF0ZSINCiBvciB3aGVuDQotLkIgIi0tb3ZlcnJpZGUtY29uZmln -Ig0KKy5CICJcLVwtb3ZlcnJpZGVcLWNvbmZpZyINCiBpcyBzcGVjaWZpZWQg -Zm9yDQogLkIgInBidWlsZGVyIHVwZGF0ZSINCi1vcHRpb24uLlRQDQorb3B0 -aW9uLg0KKy5UUA0KIC5CSSAiZXhwb3J0IGh0dHBfcHJveHk9IiAiaHR0cDov -L3lvdXItcHJveHk6ODA4MC8iDQogRGVmaW5lcyB0aGUgcHJveHkgZm9yIGh0 -dHAgY29ubmVjdGlvbi4NCiAuVFANCkBAIC0xNTksMTYgKzE2MywxNiBAQA0K -IC5UUA0KIC5CSSAiREVCQlVJTERPUFRTPSIgIiINCiBUaGUgb3B0aW9ucyBn -aXZlbiBoZXJlIHdpbGwgYmUgcGFzc2VkIG9uIHRvDQotLkJSIGRwa2ctYnVp -bGRwYWNrYWdlIC4NCisuQlIgZHBrZ1wtYnVpbGRwYWNrYWdlIC4NCiBUaGlz -IGNhbiBiZSB1c2VmdWwgZS5nLiBmb3IgYmluYXJ5LW9ubHkgYnVpbGRzLiBU -aGUgY29tbWFuZC1saW5lIG9wdGlvbg0KLS5CICItLWRlYmJ1aWxkb3B0cyIg -d2lsbCBiZSBhcHBlbmRlZCB0byBhbnkgY29udGVudHMgc3BlY2lmaWVkIGhl -cmUgYnV0DQorLkIgIlwtXC1kZWJidWlsZG9wdHMiIHdpbGwgYmUgYXBwZW5k -ZWQgdG8gYW55IGNvbnRlbnRzIHNwZWNpZmllZCBoZXJlIGJ1dA0KIG1heSBh -bHNvIGJlIHVzZWQgdG8gcmVzZXQgdGhlIGxpc3Qgb2Ygb3B0aW9ucy4NCiAN -CiBUaGUgZGVmYXVsdCB2YWx1ZSBpcyB0byBidWlsZCBzb3VyY2UgYW5kIGJp -bmFyeSBwYWNrYWdlLg0KIC5UUA0KLS5CSSAiREVCT09UU1RSQVBPUFRTPSIg -IiggJy0tdmFyaWFudD1idWlsZGQnICkiDQorLkJJICJERUJPT1RTVFJBUE9Q -VFM9IiAiKCAnXC1cLXZhcmlhbnQ9YnVpbGRkJyApIg0KIFdoZW4gdGhpcyBv -cHRpb24gaXMgc2V0IHRvDQotLkIgIi0tdmFyaWFudD1idWlsZGQiDQorLkIg -IlwtXC12YXJpYW50PWJ1aWxkZCINCiAuQiAicGJ1aWxkZXIiDQogd2lsbCBp -bnZva2UNCiAuQiAiJERFQk9PVFNUUkFQIg0KQEAgLTE4OCwxMiArMTkyLDEy -IEBADQogLlRQDQogLkJJICJERUJFTUFJTD0iICJNYWludGFpbmVyIE5hbWUg -PE1haWxAQWRkcmVzcz4iDQogSWYgdGhpcyB3YXMgc3BlY2lmaWVkLA0KLS5C -IGRwa2ctYnVpbGRwYWNrYWdlDQorLkIgZHBrZ1wtYnVpbGRwYWNrYWdlDQog -Y29tbWFuZCB3aWxsIGJlIHBhc3NlZCB3aXRoIHRoZSBuZWNlc3Nhcnkgc3Bv -bnNvcnNoaXAgb3B0aW9uDQotLkIgIi1tTWFpbnRhaW5lciBOYW1lIDxNYWls -QEFkZHJlc3M+Ig0KKy5CICJcLW1NYWludGFpbmVyIE5hbWUgPE1haWxAQWRk -cmVzcz4iDQogb24gYnVpbGRpbmcuDQogT3ZlcnJpZGRlbiB3aXRoDQotLkIg -Ii0tZGViZW1haWwiDQorLkIgIlwtXC1kZWJlbWFpbCINCiBjb21tYW5kLWxp -bmUgb3B0aW9uLg0KIFRoZSBkZWZhdWx0IGNvbmZpZ3VyYXRpb24gZm9yDQog -LkIgcGJ1aWxkZXINCkBAIC0yMTEsNyArMjE1LDcgQEANCiBUaGlzIG9wdGlv -biBvbmx5IGFmZmVjdHMgd2hlbiBkb2luZw0KIC5CICJwYnVpbGRlciBjcmVh -dGUiDQogb3Igd2hlbg0KLS5CICItLW92ZXJyaWRlLWNvbmZpZyINCisuQiAi -XC1cLW92ZXJyaWRlXC1jb25maWciDQogaXMgc3BlY2lmaWVkIGZvcg0KIC5C -ICJwYnVpbGRlciB1cGRhdGUiDQogb3B0aW9uLg0KQEAgLTIyOCw3ICsyMzIs -NyBAQA0KIFNwZWNpZmllcyB0aGUgZGVmYXVsdCBsb2NhdGlvbiBmb3IgdGhl -IHVzZXIgaG9va3MNCiBkaXJlY3RvcnkuDQogVGhpcyBpcyBvdmVycmlkZGVu -IHdpdGggdGhlIG9wdGlvbg0KLS5CUiAiLS1ob29rZGlyIiAiLiINCisuQlIg -IlwtXC1ob29rZGlyIiAiLiINCiANCiBJZiB0aGlzIGlzIHNwZWNpZmllZCwg -aG9va3MgYXJlIHNlYXJjaGVkIGZvciBpbg0KIHRoZSBjaHJvb3QsIHdoZW4g -cnVubmluZw0KQEAgLTI1MSw4ICsyNTUsOSBAQA0KIC5CSSAiT1RIRVJNSVJS -T1I9IiAiZGViIGh0dHA6Ly94eHgveHh4LyAuLyAiICJbfCIgIiBvdGhlciBk -ZWIgbGluZXMuLi4gIiAiXSINCiBUaGUgbGluZXMgd2hpY2ggaXMgYWRkZWQg -dG8gdGhlIHNvdXJjZXMubGlzdCwgZGVsaW1pdGVkIHdpdGgNCiAuQiAifCIN -Ci1MaWtlDQotLkIgImRlYiBodHRwOi8vbG9jYWwvbWlycm9yIHN0YWJsZSBt -YWlufGRlYiBmaWxlOi91c3IvbG9jYWwvbWlycm9yIC4vIg0KK0xpa2U6DQor -LmJyDQorLkIgImRlYiBodHRwOi8vbG9jYWwvbWlycm9yIHNpZCBtYWlufGRl -YiBmaWxlOi91c3IvbG9jYWwvbWlycm9yIC4vIg0KIA0KIFRoZSBkZWIgbGlu -ZXMgaGVyZSBhcmUgdGhlIG9uZXMgdGhhdCB3aWxsIGFwcGVhciBhdCB0aGUg -dG9wIG9mIHRoZQ0KIC5CICJzb3VyY2VzLmxpc3QiDQpAQCAtMjY4LDcgKzI3 -Myw3IEBADQogDQogVG8gbWFrZSBjaGFuZ2VzIG9uIG1pcnJvciBzaXRlIGVm -ZmVjdGl2ZSBvbg0KIC5CIHVwZGF0ZQ0KLS5CICItLW92ZXJyaWRlLWNvbmZp -ZyINCisuQiAiXC1cLW92ZXJyaWRlXC1jb25maWciDQogbmVlZHMgdG8gYmUg -c3BlY2lmaWVkLg0KIC5UUA0KIC5CSSAiUERFQlVJTERfUEJVSUxERVI9IiAi -cGJ1aWxkZXIiDQpAQCAtMjc5LDI2ICsyODQsMjYgQEANCiAuQiAiY293YnVp -bGRlciINCiAuVFANCiAuQkkgIlBLR05BTUVfTE9HRklMRV9FWFRFTlRJT049 -IiAiLmJ1aWxkIg0KLVRoZSBleHRlbnNpb24gb2YgZmlsZW5hbWUgdXNlZCBp -biBwa2duYW1lLWxvZ2ZpbGUgb3B0aW9uLg0KK1RoZSBleHRlbnNpb24gb2Yg -ZmlsZW5hbWUgdXNlZCBpbiBwa2duYW1lXC1sb2dmaWxlIG9wdGlvbi4NCiAu -VFANCiAuQkkgIlBLR05BTUVfTE9HRklMRT0iICJ5ZXMiDQogQWx3YXlzIHJ1 -biB3aXRoDQotLkIgIi0tcGtnbmFtZS1sb2dmaWxlIg0KKy5CICJcLVwtcGtn -bmFtZVwtbG9nZmlsZSINCiBvcHRpb24sIGFuZCBjcmVhdGUgYSBsb2dmaWxl -IG5hbWVkIGFmdGVyIHRoZSBwYWNrYWdlIG5hbWUuDQogLlRQDQotLkJJICJQ -QlVJTERFUlJPT1RDTUQ9IiAic3VkbyAtRSINCisuQkkgIlBCVUlMREVSUk9P -VENNRD0iICJzdWRvIFwtRSINCiBUaGlzIG9wdGlvbiBpcyB1c2VkIG9uIGlu -dm9jYXRpb24gb2YNCiAuQiAicGJ1aWxkZXIgYnVpbGQiDQogaW4NCiAuQiAi -cGRlYnVpbGQiDQogLlRQDQotLkJJICJQQlVJTERFUlNBVElTRllERVBFTkRT -Q01EPSIgIi91c3IvbGliL3BidWlsZGVyL3BidWlsZGVyLXNhdGlzZnlkZXBl -bmRzIg0KKy5CSSAiUEJVSUxERVJTQVRJU0ZZREVQRU5EU0NNRD0iICIvdXNy -L2xpYi9wYnVpbGRlci9wYnVpbGRlclwtc2F0aXNmeWRlcGVuZHMiDQogVGhp -cyBvcHRpb24gaXMgdXNlZCBieSB2YXJpb3VzIHBhcnRzIG9mIHBidWlsZGVy -IHRvIHNhdGlzZnkNCiAoaS5lLiBpbnN0YWxsKSB0aGUgYnVpbGQtZGVwZW5k -ZW5jaWVzIG9mIGEgcGFja2FnZS4gIFRoZXJlIGFyZSBmb3VyDQogaW1wbGVt -ZW50YXRpb25zOg0KIA0KIFRoZSAiZXhwZXJpbWVudGFsIiBpbXBsZW1lbnRh -dGlvbiwNCi0icGJ1aWxkZXItc2F0aXNmeWRlcGVuZHMtZXhwZXJpbWVudGFs -Iiwgd2hpY2ggbWlnaHQgYmUgdXNlZnVsIHRvIHB1bGwNCisicGJ1aWxkZXJc -LXNhdGlzZnlkZXBlbmRzXC1leHBlcmltZW50YWwiLCB3aGljaCBtaWdodCBi -ZSB1c2VmdWwgdG8gcHVsbA0KIHBhY2thZ2VzIGZyb20gZXhwZXJpbWVudGFs -IG9yIGZyb20gcmVwb3NpdG9yaWVzIHdpdGggYSBsb3cgQVBUIFBpbg0KIFBy -aW9yaXR5Lg0KIA0KQEAgLTMxNiwxNCArMzIxLDE0IEBADQogDQogVGhlIGRl -ZmF1bHQgaXMgbm93ICJhcHRpdHVkZSIuDQogLlRQDQotLkJJICJQQlVJTERF -UlNBVElTRllERVBFTkRTT1BUPSIgIignLS1jaGVjay1rZXknKSINCi1BcnJh -eSBvZiBmbGFncyB0byBnaXZlIHRvIHBidWlsZGVyLXNhdGlzZnlkZXBlbmRz -Lg0KLVNwZWNpZnlpbmcgLS1jaGVjay1rZXkgaGVyZSB3aWxsIHRyeSB0byB2 -ZXJpZnkga2V5IHNpZ25hdHVyZXMuDQorLkJJICJQQlVJTERFUlNBVElTRllE -RVBFTkRTT1BUPSIgIignXC1cLWNoZWNrXC1rZXknKSINCitBcnJheSBvZiBm -bGFncyB0byBnaXZlIHRvIHBidWlsZGVyXC1zYXRpc2Z5ZGVwZW5kcy4NCitT -cGVjaWZ5aW5nIFwtXC1jaGVja1wta2V5IGhlcmUgd2lsbCB0cnkgdG8gdmVy -aWZ5IGtleSBzaWduYXR1cmVzLg0KIA0KIC5UUA0KLS5CSSAiQVBUR0VUT1BU -PSIgIignLS1mb3JjZS15ZXMnKSINCi1FeHRyYSBmbGFncyB0byBnaXZlIHRv -IGFwdC1nZXQuDQotRGVmYXVsdCBpcyAtLWZvcmNlLXllcywgd2hpY2ggd2ls -bCBza2lwIGtleSB2ZXJpZmljYXRpb24gb2YgcGFja2FnZXMNCisuQkkgIkFQ -VEdFVE9QVD0iICIoJ1wtXC1mb3JjZVwteWVzJykiDQorRXh0cmEgZmxhZ3Mg -dG8gZ2l2ZSB0byBhcHRcLWdldC4NCitEZWZhdWx0IGlzIFwtXC1mb3JjZVwt -eWVzLCB3aGljaCB3aWxsIHNraXAga2V5IHZlcmlmaWNhdGlvbiBvZiBwYWNr -YWdlcw0KIHRvIGJlIGluc3RhbGxlZC4gVW5zZXQgaWYgeW91IHdhbnQgdG8g -ZW5hYmxlIGtleSB2ZXJpZmljYXRpb24uDQogDQogLlRQDQpAQCAtMzUyLDcg -KzM1Nyw3IEBADQogLkJJICJVU0VfUERFQlVJTERfSU5URVJOQUw9IiAieWVz -Ig0KIFdoZW4gdGhpcyBvcHRpb24gaXMgc2V0IHRvDQogLkkgeWVzDQotLkIg -InBkZWJ1aWxkLWludGVybmFsIg0KKy5CICJwZGVidWlsZFwtaW50ZXJuYWwi -DQogaW1wbGVtZW50YXRpb24gb2YNCiAuQiBwZGVidWlsZA0KIGlzIHVzZWQu -DQpAQCAtMzc2LDcgKzM4MSw3IEBADQogLlNIICJGSUxFUyINCiAuSSAiL2V0 -Yy9wYnVpbGRlcnJjLCAkSE9NRS8ucGJ1aWxkZXJyYyINCiAuU0ggIlNFRSBB -TFNPIg0KLS5CUiAiL3Vzci9zaGFyZS9kb2MvcGJ1aWxkZXIvcGJ1aWxkZXIt -ZG9jLmh0bWwiICIsICINCisuQlIgIi91c3Ivc2hhcmUvZG9jL3BidWlsZGVy -L3BidWlsZGVyXC1kb2MuaHRtbCIgIiwgIg0KIC5CUiAiY293YnVpbGRlciIg -Iig4KSwgIg0KIC5CUiAicGJ1aWxkZXIiICIoOCksICINCiAuQlIgInBkZWJ1 -aWxkIiAiKDEpIg0K - ---0-422438018-1306444141=:6597 -Content-Type: TEXT/PLAIN; charset=US-ASCII; name=tstpkg_1.dsc -Content-Transfer-Encoding: BASE64 -Content-ID: -Content-Description: -Content-Disposition: attachment; filename=tstpkg_1.dsc - -Rm9ybWF0OiAxLjANClNvdXJjZTogdHN0cGtnDQpCaW5hcnk6IHRzdHBrZw0K -QXJjaGl0ZWN0dXJlOiBhbGwNClZlcnNpb246IDENCk1haW50YWluZXI6IFRo -b3JzdGVuIEdsYXNlciA8dGdAbWlyYnNkLmRlPg0KQnVpbGQtRGVwZW5kczog -bWtzaCBbYW1kNjQgaTM4Nl0sIGN2cyBbIWFtZDY0ICFpMzg2XSwgeHotbHpt -YSAoPj0gNX4pLCBsZXNzDQpDaGVja3N1bXMtU2hhMTogDQogNjZlNzhkYTNm -YmViYTNiOGQzNGJiMzc5NDY2MTYxNWUzOTYyMjM5ZCA2ODggdHN0cGtnXzEu -dGFyLmd6DQpDaGVja3N1bXMtU2hhMjU2OiANCiA3OGJhMWU1NjZhYWUyNzE4 -MDI3YzZlY2U2OGMyZWZmYTJjYjFjNjdiZDA2ZGQ2Y2UzYmZmYTY2ZTI5OWYx -ODNhIDY4OCB0c3Rwa2dfMS50YXIuZ3oNCkZpbGVzOiANCiBhZDNmNmE1ZDli -MmZkZTg2ODlmYTI3YTI1MTI3Y2U4MCA2ODggdHN0cGtnXzEudGFyLmd6DQo= - ---0-422438018-1306444141=:6597 -Content-Type: APPLICATION/octet-stream; name=tstpkg_1.tar.gz -Content-Transfer-Encoding: BASE64 -Content-ID: -Content-Description: -Content-Disposition: attachment; filename=tstpkg_1.tar.gz - -H4sIAAAAAAACA+yWUW/TMBDH+4o/xVV7YINmjdMmQYFNgDYhpA1NbDxNPLjO -tTF1nMh2gO6Bz86l3QBNAl5GB8I/qXV6Tu2r//nf1TvfLhcRHw/+HDGRp+l6 -JG6P62vO0yxPJ/F00t+XT5N8AOlgC3TOCwsw+E/xN/qXOFPCjO9b/zynOI+z -dBL0vw/9ZSXMAnWzuGP9s+n0p/rzPLulf5JO+ADioP+W9Iddvgfv3rw9Pjl+ -cX589BQ6u0AjVwe6+cQYwCN4bZRXQoNFjcLhPkWjCC6qxjqPBl5pClp45hfP -a2Vnrtwv8RBovhtBksGpWEESc05vRZwU6RQe98KzQeAv87/tNLot13/O8xv/ -83jS+5/nSRz8vw12huPO2fFMmXEtlgjRnLFZp3QJkoxugCaEXUXKlNjefBBW -VtfXoAydn9YgK5TLIhj6n+//jfG20Xfu/1/1/yz+1v95mq77f0LlIvh/G/4H -XynHdkA5EDTIpq7ReMbOm85KLGDzgLBzlF41poBaOcnOrGqs8qsCmrYPC81O -hTKeXmiL3/wtoF3miub7LeeNBVGX2XQEDunZK/ugafyPE5SgLaESlCB4MWMv -+/IUHWGLpnSU0NJVcLm+F9TkSfZ+1G9A2fuqX+wDCQy+2RQoUHNQ/qHrf2ar -0aNeQSusw5KB/OjgcrhZZ7hZCD5fRfqqFrB7ePAg/bI3AmqOjrEzIZdi8f1w -XlBBVJ5OqLMUpHLIjtBJq9rNkV0gpXD9HQYn2CfgqXa260KLdhjKZiAQCAQC -gUAgEAgEAl8BAAD//xoFAAAAAP//GgUAAAAA//8aBQAAAAD//xoFAAAAAP// -GgUAAAAA//8aBQAAAAD//xoFAAAAAP//GgUAAAAA//8aBQAAAAD//6IiAAAA -AP//AwAbFwmqACgAAA== - ---0-422438018-1306444141=:6597 -Content-Type: text/plain; charset="us-ascii" -MIME-Version: 1.0 -Content-Transfer-Encoding: 7bit -Content-Disposition: inline - -_______________________________________________ -Pbuilder-maint mailing list -Pbuilder-maint@lists.alioth.debian.org -http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint ---0-422438018-1306444141=:6597-- - - - diff -Nru pbuilder-0.215ubuntu7/pbuilder-buildpackage pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-buildpackage --- pbuilder-0.215ubuntu7/pbuilder-buildpackage 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-buildpackage 2015-06-22 08:05:23.000000000 +0000 @@ -36,19 +36,41 @@ # LD_PRELOAD: Normal users don't have write access to build # environment, so cowdancer shouldn't have to run, and fakeroot # should be running later, so it shouldn't matter. - # LOGNAME: set this to shut up some tools. - # su -p : switch to user preserving env vars, we need most of them. - SUTOUSER="env LD_PRELOAD= LOGNAME=$BUILDUSERNAME su -p $BUILDUSERNAME" + # LOGNAME and USER: set this to shut up some tools. + SUTOUSER="LD_PRELOAD= LOGNAME=$BUILDUSERNAME USER=$BUILDUSERNAME /sbin/start-stop-daemon --start --pidfile /dev/null --chuid $BUILDUSERNAME --startas /bin/sh" DEBBUILDOPTS="${DEBBUILDOPTS:+$DEBBUILDOPTS }-rfakeroot" EXTRAPACKAGES="${EXTRAPACKAGES} fakeroot" log "I: using fakeroot in build." else # run the build in root - SUTOUSER="su -p " BUILDUSERID=0 BUILDUSERNAME=root + SUTOUSER="LOGNAME=$BUILDUSERNAME /bin/sh" fi +UNSHARE= +case $USENETWORK in +yes) + if [ "$DEB_BUILD_ARCH_OS" = "linux" ]; then + # omit the warning when running on kFreeBSD or Hurd + log "W: pbuilder: network will not be disabled during build!" + fi + ;; +*) + if /usr/bin/unshare -n -- /usr/lib/pbuilder/pbuilder-unshare-wrapper true; then + USENETWORK=no + UNSHARE="/usr/bin/unshare -n -- /usr/lib/pbuilder/pbuilder-unshare-wrapper" + log "I: pbuilder: network access will be disabled during build" + else + USENETWORK=yes + if [ "$DEB_BUILD_ARCH_OS" = "linux" ]; then + log "W: pbuilder: unshare CLONE_NEWNET not available" + fi + log "I: pbuilder: network access is available during build!" + fi + ;; +esac + # created files should have these UID/GIDs outside of chroot. BUILDRESULTUID="${BUILDRESULTUID:-${SUDO_UID:-0}}" @@ -92,7 +114,9 @@ recover_aptcache createbuilduser +CCACHE_ENV= setup_ccache +SUTOUSER="$CCACHE_ENV $SUTOUSER" log "I: Installing the build-deps" executehooks "D" trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe @@ -111,7 +135,7 @@ log "E: pbuilder: Failed chowning to $BUILDUSERNAME:$BUILDUSERNAME" exit 1; fi -if echo "( cd tmp/buildd; env PATH=\"$PATH\" /usr/bin/dpkg-source -x $(basename $PACKAGENAME) )" | $CHROOTEXEC $SUTOUSER ; then +if echo "( cd tmp/buildd; env PATH=\"$PATH\" /usr/bin/dpkg-source -x $(basename $PACKAGENAME) )" | $UNSHARE $CHROOTEXEC env $SUTOUSER ; then : # success else log "E: pbuilder: Failed extracting the source" @@ -131,7 +155,7 @@ fi DPKG_COMMANDLINE="cd tmp/buildd/*/ && $DPKG_COMMANDLINE" log "I: Running $DPKG_COMMANDLINE" - echo "$DPKG_COMMANDLINE" | $CHROOTEXEC $SUTOUSER + echo "$DPKG_COMMANDLINE" | $UNSHARE $CHROOTEXEC env $SUTOUSER ) & BUILD_PID=$! if [ -n "${TIMEOUT_TIME}" ]; then diff -Nru pbuilder-0.215ubuntu7/pbuilder-buildpackage-funcs pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-buildpackage-funcs --- pbuilder-0.215ubuntu7/pbuilder-buildpackage-funcs 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-buildpackage-funcs 2015-06-22 08:05:23.000000000 +0000 @@ -107,8 +107,7 @@ mkdir -p "$BUILDPLACE/$CCACHEDIR" fi chown -R $BUILDUSERID:$BUILDUSERID "$BUILDPLACE/$CCACHEDIR" - # Unfortunate difference between pbuilder-style and ccache-style config - # env vars :-/ - export CCACHE_DIR="$CCACHEDIR" + CCACHE_ENV="CCACHE_DIR=$CCACHEDIR" + unset CCACHE_DIR fi } diff -Nru pbuilder-0.215ubuntu7/pbuilder-modules pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-modules --- pbuilder-0.215ubuntu7/pbuilder-modules 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-modules 2015-06-22 16:04:04.000000000 +0000 @@ -270,7 +270,7 @@ TTYGRP=5 TTYMODE=620 [ -f /etc/default/devpts ] && . /etc/default/devpts - mount -t devpts /dev/pts "$BUILDPLACE/dev/pts" -onoexec,nosuid,gid=$TTYGRP,mode=$TTYMODE + mount -t devpts none "$BUILDPLACE/dev/pts" -onoexec,nosuid,gid=$TTYGRP,mode=$TTYMODE mounted[${#mounted[@]}]="$BUILDPLACE/dev/pts" fi if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then diff -Nru pbuilder-0.215ubuntu7/pbuilderrc pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilderrc --- pbuilder-0.215ubuntu7/pbuilderrc 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilderrc 2015-07-10 14:24:41.000000000 +0000 @@ -9,12 +9,13 @@ #export http_proxy=http://your-proxy:8080/ USEPROC=yes USEDEVPTS=yes +USENETWORK=no USERUNSHM=yes USEDEVFS=no BUILDRESULT=/var/cache/pbuilder/result/ # specifying the distribution forces the distribution on "pbuilder update" -DISTRIBUTION=saucy +DISTRIBUTION=wily # specifying the architecture passes --arch= to debootstrap; the default is # to use the architecture of the host #ARCHITECTURE=`dpkg --print-architecture` @@ -88,7 +89,6 @@ # Set the debootstrap variant to 'buildd' type. DEBOOTSTRAPOPTS=( '--variant=buildd' - '--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg' ) # or unset it to make it not a buildd type. # unset DEBOOTSTRAPOPTS diff -Nru pbuilder-0.215ubuntu7/pbuilderrc.5 pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilderrc.5 --- pbuilder-0.215ubuntu7/pbuilderrc.5 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilderrc.5 2015-06-22 08:05:23.000000000 +0000 @@ -380,6 +380,14 @@ .B /dev/pts being mounted. .TP +.BI "USENETWORK=" "no" +Specify +.B yes +when you do not want to disable network access during build. +Network is not available on a Debian buildd, so you might +want to keep the default. +Disabling network access currently only works on Linux. +.TP .BI "USERUNSHM=" "yes" Specify .B yes diff -Nru pbuilder-0.215ubuntu7/pbuilder-satisfydepends-aptitude pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-aptitude --- pbuilder-0.215ubuntu7/pbuilder-satisfydepends-aptitude 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-aptitude 2015-06-22 16:04:04.000000000 +0000 @@ -25,38 +25,6 @@ . "$PBUILDER_PKGLIBDIR"/pbuilder-satisfydepends-funcs - -# filter out dependencies sent on input not for this arch; deps can have -# multiple lines; output is on a single line or "" if empty -function filter_arch_deps() { - local arch="$1" - local INSTALLPKGMULTI - local INSTALLPKG - - # split on "," - sed 's/[[:space:]]*,[[:space:]]*/\n/g' | - while read INSTALLPKGMULTI; do - echo "$INSTALLPKGMULTI" | - # split on "|" - sed 's/[[:space:]]*|[[:space:]]*/\n/g' | - while read INSTALLPKG; do - if echo "$INSTALLPKG" | grep -q '\['; then - if checkbuilddep_archdeps "$INSTALLPKG" "$ARCH"; then - continue - fi - fi - # output the selected package - echo "$INSTALLPKG" - done | - # remove the arch list and add " | " between entries - sed 's/\[.*\]//; $,$! s/$/ |/' | - xargs --no-run-if-empty - done | - # add ", " between entries - sed '$,$! s/$/,/' | - xargs --no-run-if-empty -} - function checkbuilddep_internal () { # Use this function to fulfill the dependency (almost) local ARCH=$($CHROOTEXEC dpkg-architecture -qDEB_HOST_ARCH) @@ -65,8 +33,10 @@ local DEPENDS local CONFLICTS echo " -> Attempting to satisfy build-dependencies" - DEPENDS="$(get_build_deps | filter_arch_deps "$ARCH")" - CONFLICTS="$(get_build_conflicts | filter_arch_deps "$ARCH")" + DEPENDS="$(get_build_deps | filter_arch_deps "$ARCH" | + filter_restriction_deps "$DEB_BUILD_PROFILES" )" + CONFLICTS="$(get_build_conflicts | filter_arch_deps "$ARCH" | + filter_restriction_deps "$DEB_BUILD_PROFILES" )" echo " -> Creating pbuilder-satisfydepends-dummy package" BUILD_DEP_DEB_DIR="/tmp/satisfydepends-aptitude" BUILD_DEP_DEB_CONTROL="$BUILD_DEP_DEB_DIR/pbuilder-satisfydepends-dummy/DEBIAN/control" diff -Nru pbuilder-0.215ubuntu7/pbuilder-satisfydepends-classic pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-classic --- pbuilder-0.215ubuntu7/pbuilder-satisfydepends-classic 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-classic 2015-06-22 16:04:04.000000000 +0000 @@ -45,7 +45,7 @@ # architecture or version specifier; e.g. "/foo/(>=/2)/[i386/amd64]" becomes # "foo" get_pkg_name() { - echo "$*" | sed 's#^/*##; s#[[/(].*##' + echo "$*" | sed 's#^/*##; s#[[/(<].*##' } # filter operator and version of a "/" escaped versioned build-dep; e.g. @@ -81,6 +81,13 @@ continue fi fi + if echo "$INSTALLPKG" | grep -q '<'; then + if checkbuilddep_restrictiondeps "$INSTALLPKG" "$DEB_BUILD_PROFILES"; then + SATISFIED="yes" + echo " -> This package is not for the current build profiles" + continue + fi + fi if echo "$INSTALLPKG" | grep -q '('; then #echo "Debug: $INSTALLPKG" if ! checkbuilddep_versiondeps "$CURRENTREALPKGNAME" `get_dep_op_and_ver "$INSTALLPKG"`; then @@ -151,6 +158,13 @@ continue fi fi + if echo "$INSTALLPKG" | greq -q '<'; then + # this package has build-profiles-conflicts. + if checkbuilddep_restrictiondeps "$INSTALLPKG" "$DEB_BUILD_PROFILES"; then + echo "I: Ignoring other-buildprofiles" + continue + fi + fi if echo "$INSTALLPKG" | grep -q '('; then # this package has version-conflicts if ! checkbuilddep_versiondeps "$CURRENTREALPKGNAME" `get_dep_op_and_ver "$INSTALLPKG"`; then diff -Nru pbuilder-0.215ubuntu7/pbuilder-satisfydepends-funcs pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-funcs --- pbuilder-0.215ubuntu7/pbuilder-satisfydepends-funcs 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/pbuilder-satisfydepends-funcs 2015-06-22 16:04:04.000000000 +0000 @@ -117,6 +117,68 @@ echo "$output" } +# filter out dependencies sent on input not for this arch; deps can have +# multiple lines; output is on a single line or "" if empty +filter_arch_deps() { + local arch="$1" + local INSTALLPKGMULTI + local INSTALLPKG + + # split on "," + sed 's/[[:space:]]*,[[:space:]]*/\n/g' | + while read INSTALLPKGMULTI; do + echo "$INSTALLPKGMULTI" | + # split on "|" + sed 's/[[:space:]]*|[[:space:]]*/\n/g' | + while read INSTALLPKG; do + if echo "$INSTALLPKG" | grep -q '\['; then + if checkbuilddep_archdeps "$INSTALLPKG" "$arch"; then + continue + fi + fi + # output the selected package + echo "$INSTALLPKG" + done | + # remove the arch list and add " | " between entries + sed 's/\[.*\]//; $,$! s/$/ |/' | + xargs --no-run-if-empty + done | + # add ", " between entries + sed '$,$! s/$/,/' | + xargs --no-run-if-empty +} + +# filter out dependencies sent on input not for selected build profiles; deps +# can have multiple lines; output is on a single line or "" if empty +filter_restriction_deps() { + local profiles="$1" + local INSTALLPKGMULTI + local INSTALLPKG + + # split on "," + sed 's/[[:space:]]*,[[:space:]]*/\n/g' | + while read INSTALLPKGMULTI; do + echo "$INSTALLPKGMULTI" | + # split on "|" + sed 's/[[:space:]]*|[[:space:]]*/\n/g' | + while read INSTALLPKG; do + if echo "$INSTALLPKG" | grep -q '<'; then + if checkbuilddep_restrictiondeps "$INSTALLPKG" "$profiles"; then + continue + fi + fi + # output the selected package + echo "$INSTALLPKG" + done | + # remove the restriction list and add " | " between entries + sed 's/<.*>//; $,$! s/$/ |/' | + xargs --no-run-if-empty + done | + # add ", " between entries + sed '$,$! s/$/,/' | + xargs --no-run-if-empty +} + checkbuilddep_archdeps() { # returns FALSE on INSTALL local INSTALLPKG="$1" @@ -131,11 +193,11 @@ for d in $DEP_ARCHES; do if echo "$d" | grep -q '!'; then d="$(echo $d | sed 's/!//')" - if dpkg-architecture -a$ARCH -i$d; then + if dpkg-architecture -a$ARCH -i$d -f; then IGNORE_IT="yes" fi else - if dpkg-architecture -a$ARCH -i$d; then + if dpkg-architecture -a$ARCH -i$d -f; then USE_IT="yes" fi INCLUDE="yes" @@ -151,6 +213,48 @@ return 1 } +checkbuilddep_restrictiondeps() { + # returns FALSE on INSTALL + local INSTALLPKG="$1" + local PROFILES="$2" + # restrictions listed between < and > for this dep + local DEP_RESTRICTIONS="$(echo "$INSTALLPKG" | sed -e 's/[^<]*<\(.*\)>.*/\1/' -e 's/>\s\+&@ E: $2 returned error code $1 + echo >&2 N: Could not set up the loopback interface. + exit 1 +} + +if test -x /sbin/ifconfig; then + /sbin/ifconfig lo up || die $? ifconfig +elif test -x /sbin/ip; then + /sbin/ip link set lo up || die $? ip +elif test -x /bin/ip; then + /bin/ip link set lo up || die $? ip +else + echo >&2 E: Neither ifconfig nor ip found. + echo >&2 N: Could not set up the loopback interface. + exit 1 +fi + +exec "$@" diff -Nru pbuilder-0.215ubuntu7/test_pbuilder-satisfydepends-funcs pbuilder-0.215+nmu4ubuntu1~ppa1/test_pbuilder-satisfydepends-funcs --- pbuilder-0.215ubuntu7/test_pbuilder-satisfydepends-funcs 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/test_pbuilder-satisfydepends-funcs 2015-06-22 16:04:04.000000000 +0000 @@ -84,6 +84,72 @@ expect_output "autotools-dev (>= 1.2), debhelper, quilt (<< 12:0), libwxgtk2.8-dev" \ test_get_build_deps "yes" +expect_fail checkbuilddep_archdeps "foo [amd64]" "amd64" +expect_success checkbuilddep_archdeps "foo [i386]" "amd64" +expect_fail checkbuilddep_archdeps "foo [i386 amd64]" "amd64" +expect_success checkbuilddep_archdeps "foo [!amd64]" "amd64" +expect_success checkbuilddep_archdeps "foo [!i386 !amd64]" "amd64" + +test_filter_arch_deps() { + echo "$1" | filter_arch_deps "$2" +} + +expect_output "foo" test_filter_arch_deps "foo" "amd64" +expect_output "foo" test_filter_arch_deps "foo [amd64]" "amd64" +expect_output "bar, foo" test_filter_arch_deps "bar, foo [amd64]" "amd64" +expect_output "bar | foo" test_filter_arch_deps "bar | foo [amd64]" "amd64" +expect_output "bar" test_filter_arch_deps "bar | foo [amd64]" "i386" + +expect_fail checkbuilddep_restrictiondeps "foo " "" +expect_success checkbuilddep_restrictiondeps "foo " "stage1" +expect_fail checkbuilddep_restrictiondeps "foo " "notest" +expect_success checkbuilddep_restrictiondeps "foo " "stage1 notest" + +expect_success checkbuilddep_restrictiondeps "foo " "" +expect_fail checkbuilddep_restrictiondeps "foo " "stage1" +expect_success checkbuilddep_restrictiondeps "foo " "notest" +expect_fail checkbuilddep_restrictiondeps "foo " "stage1 notest" + +expect_fail checkbuilddep_restrictiondeps "foo " "" +expect_success checkbuilddep_restrictiondeps "foo " "stage1" +expect_success checkbuilddep_restrictiondeps "foo " "notest" +expect_success checkbuilddep_restrictiondeps "foo " "stage1 notest" + +expect_success checkbuilddep_restrictiondeps "foo " "" +expect_success checkbuilddep_restrictiondeps "foo " "stage1" +expect_success checkbuilddep_restrictiondeps "foo " "notest" +expect_fail checkbuilddep_restrictiondeps "foo " "stage1 notest" + +expect_success checkbuilddep_restrictiondeps "foo " "" +expect_success checkbuilddep_restrictiondeps "foo " "stage1" +expect_fail checkbuilddep_restrictiondeps "foo " "notest" +expect_success checkbuilddep_restrictiondeps "foo " "stage1 notest" + +expect_success checkbuilddep_restrictiondeps "foo " "" +expect_fail checkbuilddep_restrictiondeps "foo " "stage1" +expect_success checkbuilddep_restrictiondeps "foo " "notest" +expect_success checkbuilddep_restrictiondeps "foo " "stage1 notest" + +test_filter_restriction_deps() { + echo "$1" | filter_restriction_deps "$2" +} + +expect_output "foo" test_filter_restriction_deps "foo " "" +expect_output "" test_filter_restriction_deps "foo " "stage1" +expect_output "foo" test_filter_restriction_deps "foo " "stage1" +expect_output "bar, foo" test_filter_restriction_deps "bar, foo " "stage1" +expect_output "bar | foo" test_filter_restriction_deps "bar | foo " "stage1" +expect_output "bar" test_filter_restriction_deps "bar | foo " "stage1" + +test_filter_arch_restriction_deps() { + echo "$1" | filter_arch_deps "$2" | filter_restriction_deps "$3" +} + +expect_output "foo" test_filter_arch_restriction_deps "foo [amd64] " "amd64" "" +expect_output "" test_filter_arch_restriction_deps "foo [amd64] " "amd64" "" +expect_output "foo" test_filter_arch_restriction_deps "foo [amd64] " "amd64" "" +expect_output "" test_filter_arch_restriction_deps "foo [i386] " "amd64" "stage1" + expect_output "debhelper (>= 7)" test_get_build_deps_dsc testlib_summary diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control 1970-01-01 00:00:00.000000000 +0000 @@ -1,10 +0,0 @@ -Package: buildindeppkg -Source: buildarchpkg -Version: 0.1 -Architecture: all -Maintainer: Junichi Uekawa -Installed-Size: 28 -Section: unknown -Priority: extra -Description: - diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -bf5ff4686f2c9e13e9f495c99541b535 usr/share/doc/buildindeppkg/changelog.gz Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/usr/share/doc/buildindeppkg/changelog.gz and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/usr/share/doc/buildindeppkg/changelog.gz differ diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -dh_installdirs -dh_installchangelogs -dh_installdocs -dh_installexamples -dh_installman -dh_link -dh_strip -dh_compress -dh_fixperms -dh_installdeb -dh_shlibdeps -dh_gencontrol -dh_md5sums -dh_builddeb diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -misc:Depends= diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -buildarchpkg (0.1) unstable; urgency=low - - * a package that has both arch dep and indep parts. - - -- Junichi Uekawa Wed, 13 Jul 2011 21:33:33 +0900 - diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control 1970-01-01 00:00:00.000000000 +0000 @@ -1,19 +0,0 @@ -Source: buildarchpkg -Section: unknown -Priority: extra -Maintainer: Junichi Uekawa -Build-Depends: debhelper (>= 5) -Build-Depends-Indep: ghostscript -Standards-Version: 3.7.2 - -Package: buildarchpkg -Architecture: any -Depends: ${shlibs:Depends}, ${misc:Depends} -Description: - - -Package: buildindeppkg -Architecture: all -Depends: ${shlibs:Depends}, ${misc:Depends} -Description: - diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log 1970-01-01 00:00:00.000000000 +0000 @@ -1,14 +0,0 @@ -dh_installdirs -dh_installchangelogs -dh_installdocs -dh_installexamples -dh_installman -dh_link -dh_strip -dh_compress -dh_fixperms -dh_installdeb -dh_shlibdeps -dh_gencontrol -dh_md5sums -dh_builddeb diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files 1970-01-01 00:00:00.000000000 +0000 @@ -1,2 +0,0 @@ -buildarchpkg_0.1_i386.deb unknown extra -buildindeppkg_0.1_all.deb unknown extra diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules 1970-01-01 00:00:00.000000000 +0000 @@ -1,79 +0,0 @@ -#!/usr/bin/make -f - -CFLAGS = -Wall -g - -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif - -configure: configure-stamp -configure-stamp: - dh_testdir - # Add here commands to configure the package. - - touch configure-stamp - - -build: build-stamp - -build-stamp: configure-stamp - dh_testdir - - # Add here commands to compile the package. - - touch $@ - -clean: - dh_testdir - dh_testroot - rm -f build-stamp configure-stamp - - # Add here commands to clean up after the build process. - - dh_clean - -install: build - dh_testdir - dh_testroot - dh_clean -k - dh_installdirs - -# Build architecture-independent files here. -binary-indep: build install -# We have nothing to do by default. - -# Build architecture-dependent files here. -binary-arch: build install - dh_testdir - dh_testroot - dh_installchangelogs - dh_installdocs - dh_installexamples -# dh_install -# dh_installmenu -# dh_installdebconf -# dh_installlogrotate -# dh_installemacsen -# dh_installpam -# dh_installmime -# dh_python -# dh_installinit -# dh_installcron -# dh_installinfo - dh_installman - dh_link - dh_strip - dh_compress - dh_fixperms -# dh_perl -# dh_makeshlibs - dh_installdeb - dh_shlibdeps - dh_gencontrol - dh_md5sums - dh_builddeb - -binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -misc:Depends= diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control 1970-01-01 00:00:00.000000000 +0000 @@ -1,9 +0,0 @@ -Package: buildarchpkg -Version: 0.1 -Architecture: i386 -Maintainer: Junichi Uekawa -Installed-Size: 28 -Section: unknown -Priority: extra -Description: - diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -bf5ff4686f2c9e13e9f495c99541b535 usr/share/doc/buildarchpkg/changelog.gz Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/usr/share/doc/buildarchpkg/changelog.gz and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/usr/share/doc/buildarchpkg/changelog.gz differ diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README 1970-01-01 00:00:00.000000000 +0000 @@ -1,2 +0,0 @@ -This is an example package that simply succeeds, with a arch-indep build dependency -This will excercise --binary-arch. diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build 1970-01-01 00:00:00.000000000 +0000 @@ -1,88 +0,0 @@ - dpkg-buildpackage -rfakeroot -D -us -uc -j3 -i -I -dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -dpkg-buildpackage: source package buildarchpkg -dpkg-buildpackage: source version 0.1 -dpkg-buildpackage: source changed by Junichi Uekawa - dpkg-source -i -I --before-build buildarchpkg-0.1 -dpkg-buildpackage: host architecture i386 - fakeroot debian/rules clean -dh_testdir -dh_testroot -rm -f build-stamp configure-stamp -# Add here commands to clean up after the build process. -dh_clean -dh_clean: Compatibility levels before 5 are deprecated. - dpkg-source -i -I -b buildarchpkg-0.1 -dpkg-source: warning: no source format specified in debian/source/format, see dpkg-source(1) -dpkg-source: info: using source format `1.0' -dpkg-source: info: building buildarchpkg in buildarchpkg_0.1.tar.gz -dpkg-source: info: building buildarchpkg in buildarchpkg_0.1.dsc - debian/rules build -dh_testdir -# Add here commands to configure the package. -touch configure-stamp -dh_testdir -# Add here commands to compile the package. -touch build-stamp - fakeroot debian/rules binary -dh_testdir -dh_testroot -dh_clean -k -dh_clean: dh_clean -k is deprecated; use dh_prep instead -dh_clean: Compatibility levels before 5 are deprecated. -dh_installdirs -dh_installdirs: Compatibility levels before 5 are deprecated. -dh_testdir -dh_testroot -dh_installchangelogs -dh_installchangelogs: Compatibility levels before 5 are deprecated. -dh_installdocs -dh_installdocs: Compatibility levels before 5 are deprecated. -dh_installexamples -dh_installexamples: Compatibility levels before 5 are deprecated. -dh_installman -dh_installman: Compatibility levels before 5 are deprecated. -dh_link -dh_link: Compatibility levels before 5 are deprecated. -dh_strip -dh_strip: Compatibility levels before 5 are deprecated. -dh_compress -dh_compress: Compatibility levels before 5 are deprecated. -dh_fixperms -dh_fixperms: Compatibility levels before 5 are deprecated. -dh_installdeb -dh_installdeb: Compatibility levels before 5 are deprecated. -dh_shlibdeps -dh_shlibdeps: Compatibility levels before 5 are deprecated. -dh_gencontrol -dh_gencontrol: Compatibility levels before 5 are deprecated. -dpkg-gencontrol: warning: Depends field of package buildarchpkg: unknown substitution variable ${shlibs:Depends} -dpkg-gencontrol: warning: Depends field of package buildindeppkg: unknown substitution variable ${shlibs:Depends} -dh_md5sums -dh_md5sums: Compatibility levels before 5 are deprecated. -dh_builddeb -dh_builddeb: Compatibility levels before 5 are deprecated. -dpkg-deb: `../buildarchpkg_0.1_i386.deb' にパッケージ `buildarchpkg' を構築しています。 -dpkg-deb: `../buildindeppkg_0.1_all.deb' にパッケージ `buildindeppkg' を構築しています。 - dpkg-genchanges >../buildarchpkg_0.1_i386.changes -dpkg-genchanges: including full source code in upload - dpkg-source -i -I --after-build buildarchpkg-0.1 -dpkg-buildpackage: full upload; Debian-native package (full source is included) -Now running lintian... -W: buildarchpkg source: package-uses-deprecated-debhelper-compat-version 1 -W: buildarchpkg source: ancient-standards-version 3.7.2 (current is 3.9.1) -E: buildarchpkg: description-is-dh_make-template -E: buildarchpkg: section-is-dh_make-template -E: buildarchpkg: no-copyright-file -W: buildarchpkg: empty-binary-package -E: buildindeppkg: description-is-dh_make-template -E: buildindeppkg: section-is-dh_make-template -E: buildindeppkg: no-copyright-file -W: buildindeppkg: empty-binary-package -Finished running lintian. -Now signing changes and any dsc files... -Could not find a signing program (pgp or gpg)! diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes 1970-01-01 00:00:00.000000000 +0000 @@ -1,32 +0,0 @@ -Format: 1.8 -Date: Wed, 13 Jul 2011 21:33:33 +0900 -Source: buildarchpkg -Binary: buildarchpkg buildindeppkg -Architecture: source i386 all -Version: 0.1 -Distribution: unstable -Urgency: low -Maintainer: Junichi Uekawa -Changed-By: Junichi Uekawa -Description: - buildarchpkg - - buildindeppkg - -Changes: - buildarchpkg (0.1) unstable; urgency=low - . - * a package that has both arch dep and indep parts. -Checksums-Sha1: - 27ab5635b7b57fcf6bac5b748fc31d6bce03e51b 510 buildarchpkg_0.1.dsc - ecd8d27fcb20244ae1b1af6543bc2025ce9331d1 1139 buildarchpkg_0.1.tar.gz - cbe9a17df0a9b618e4be9cf95a7f7d67b0049545 1000 buildarchpkg_0.1_i386.deb - e8aececcc8a80bd22c78281408c69dffede41b6b 1012 buildindeppkg_0.1_all.deb -Checksums-Sha256: - 35b2f922a32118b5299130a201bed5364cfa95b5c98daf5e778d97d544ee67c1 510 buildarchpkg_0.1.dsc - f0627035c1081f3e07a1f50b862f3347976b79834693538a3c92341c7ad67221 1139 buildarchpkg_0.1.tar.gz - 98531c45740c89bd79f0ddbd59807bfc3968064b26527a10143702d9c058380e 1000 buildarchpkg_0.1_i386.deb - 0926421d1dcbe1d33bce769eca332243dc6bf14d5d6b8e236abb94d435ee9937 1012 buildindeppkg_0.1_all.deb -Files: - 24e69989d49f0b2a2a8197eafdac0890 510 unknown extra buildarchpkg_0.1.dsc - 19e5dddcedcb5cafffb827db19f3c4c2 1139 unknown extra buildarchpkg_0.1.tar.gz - d63ce8ae839d4767fd19824e165a5282 1000 unknown extra buildarchpkg_0.1_i386.deb - 56f4b7dbf757f582fb315eea12275227 1012 unknown extra buildindeppkg_0.1_all.deb Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.deb and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.deb differ Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/buildindeppkg_0.1_all.deb and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/buildindeppkg_0.1_all.deb differ diff -Nru pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build --- pbuilder-0.215ubuntu7/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build 1970-01-01 00:00:00.000000000 +0000 @@ -1,13 +0,0 @@ - dpkg-buildpackage -rfakeroot -D -us -uc -j3 -i -I -dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -dpkg-buildpackage: source package successpkg -dpkg-buildpackage: source version 0.1 -dpkg-buildpackage: source changed by Junichi Uekawa - dpkg-source -i -I --before-build buildarchpkg-0.1 -dpkg-buildpackage: host architecture i386 -dpkg-source: error: source package has two conflicting values - buildarchpkg and successpkg -dpkg-buildpackage: error: dpkg-source -i -I --before-build buildarchpkg-0.1 gave error exit status 255 diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/526471.log pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/526471.log --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/526471.log 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/526471.log 1970-01-01 00:00:00.000000000 +0000 @@ -1,225 +0,0 @@ -W: /home/dancer/.pbuilderrc does not exist -I: Building the build Environment -I: extracting base tarball [/var/cache/pbuilder/base.tgz] -I: creating local configuration -I: copying local configuration -I: mounting /proc filesystem -I: mounting /dev/pts filesystem -I: Mounting /home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471 -I: policy-rc.d already exists -I: user script /var/cache/pbuilder/build//18619/tmp/hooks/F01_hook starting -failpkg-F-hook-executed -I: user script /var/cache/pbuilder/build//18619/tmp/hooks/F01_hook finished -Reading package lists... -Building dependency tree... -Reading state information... -passwd is already the newest version. -The following extra packages will be installed: - cdebootstrap libdebian-installer-extra4 libdebian-installer4 libssl0.9.8 - wget -Suggested packages: - pbuilder-uml gdebi cowdancer -Recommended packages: - sudo devscripts -The following NEW packages will be installed: - cdebootstrap libdebian-installer-extra4 libdebian-installer4 libssl0.9.8 - pbuilder wget -0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. -Need to get 2144kB of archives. -After this operation, 6226kB of additional disk space will be used. -Get:1 http://localhost sid/main libssl0.9.8 0.9.8k-7 [979kB] -Get:2 http://localhost sid/main wget 1.12-1.1 [757kB] -Get:3 http://localhost sid/main libdebian-installer4 0.69 [31.0kB] -Get:4 http://localhost sid/main libdebian-installer-extra4 0.69 [12.9kB] -Get:5 http://localhost sid/main cdebootstrap 0.5.5 [32.3kB] -Get:6 http://localhost sid/main pbuilder 0.192 [331kB] -debconf: delaying package configuration, since apt-utils is not installed -Fetched 2144kB in 0s (25.7MB/s) -Selecting previously deselected package libssl0.9.8. -(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 10112 files and directories currently installed.) -Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8k-7_amd64.deb) ... -Selecting previously deselected package wget. -Unpacking wget (from .../wget_1.12-1.1_amd64.deb) ... -Selecting previously deselected package libdebian-installer4. -Unpacking libdebian-installer4 (from .../libdebian-installer4_0.69_amd64.deb) ... -Selecting previously deselected package libdebian-installer-extra4. -Unpacking libdebian-installer-extra4 (from .../libdebian-installer-extra4_0.69_amd64.deb) ... -Selecting previously deselected package cdebootstrap. -Unpacking cdebootstrap (from .../cdebootstrap_0.5.5_amd64.deb) ... -Selecting previously deselected package pbuilder. -Unpacking pbuilder (from .../pbuilder_0.192_all.deb) ... -Setting up libssl0.9.8 (0.9.8k-7) ... -Setting up wget (1.12-1.1) ... -Setting up libdebian-installer4 (0.69) ... -Setting up libdebian-installer-extra4 (0.69) ... -Setting up cdebootstrap (0.5.5) ... -Setting up pbuilder (0.192) ... -I: Setting DEBBUILDOPTS= -W: no hooks of type D found -- ignoring - -> Attempting to satisfy build-dependencies - -> Creating pbuilder-satisfydepends-dummy package -Package: pbuilder-satisfydepends-dummy -Version: 0.invalid.0 -Architecture: amd64 -Maintainer: Debian Pbuilder Team -Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder - This package was created automatically by pbuilder and should -Depends: debhelper (>= 5) -dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. -Reading package lists... -Building dependency tree... -Reading state information... -aptitude is already the newest version. -0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -Selecting previously deselected package pbuilder-satisfydepends-dummy. -(Reading database ... 10312 files and directories currently installed.) -Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ... -dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy: - pbuilder-satisfydepends-dummy depends on debhelper (>= 5); however: - Package debhelper is not installed. -dpkg: error processing pbuilder-satisfydepends-dummy (--install): - dependency problems - leaving unconfigured -Errors were encountered while processing: - pbuilder-satisfydepends-dummy -Reading package lists... -Building dependency tree... -Reading state information... -Initializing package states... -Writing extended state information... -The following NEW packages will be installed: - bsdmainutils{a} debhelper{a} file{a} gettext{a} gettext-base{a} - groff-base{a} html2text{a} intltool-debian{a} libcroco3{a} - libglib2.0-0{a} libmagic1{a} libpcre3{a} libxml2{a} man-db{a} - po-debconf{a} -The following partially installed packages will be configured: - pbuilder-satisfydepends-dummy -0 packages upgraded, 15 newly installed, 0 to remove and 0 not upgraded. -Need to get 8918kB of archives. After unpacking 26.3MB will be used. -Writing extended state information... -Get:1 http://localhost sid/main libmagic1 5.03-3 [389kB] -Get:2 http://localhost sid/main file 5.03-3 [46.9kB] -Get:3 http://localhost sid/main html2text 1.3.2a-14 [103kB] -Get:4 http://localhost sid/main libpcre3 7.8-3 [215kB] -Get:5 http://localhost sid/main libglib2.0-0 2.22.2-2 [984kB] -Get:6 http://localhost sid/main libxml2 2.7.6.dfsg-1 [876kB] -Get:7 http://localhost sid/main libcroco3 0.6.2-1 [125kB] -Get:8 http://localhost sid/main gettext-base 0.17-8 [133kB] -Get:9 http://localhost sid/main gettext 0.17-8 [2503kB] -Get:10 http://localhost sid/main intltool-debian 0.35.0+20060710.1 [30.8kB] -Get:11 http://localhost sid/main po-debconf 1.0.16 [224kB] -Get:12 http://localhost sid/main groff-base 1.20.1-6 [1156kB] -Get:13 http://localhost sid/main bsdmainutils 8.0.2 [198kB] -Get:14 http://localhost sid/main man-db 2.5.6-4 [1477kB] -Get:15 http://localhost sid/main debhelper 7.4.8 [458kB] -debconf: delaying package configuration, since apt-utils is not installed -Fetched 8918kB in 0s (40.3MB/s) -Selecting previously deselected package libmagic1. -(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 10312 files and directories currently installed.) -Unpacking libmagic1 (from .../libmagic1_5.03-3_amd64.deb) ... -Selecting previously deselected package file. -Unpacking file (from .../archives/file_5.03-3_amd64.deb) ... -Selecting previously deselected package html2text. -Unpacking html2text (from .../html2text_1.3.2a-14_amd64.deb) ... -Selecting previously deselected package libpcre3. -Unpacking libpcre3 (from .../libpcre3_7.8-3_amd64.deb) ... -Selecting previously deselected package libglib2.0-0. -Unpacking libglib2.0-0 (from .../libglib2.0-0_2.22.2-2_amd64.deb) ... -Selecting previously deselected package libxml2. -Unpacking libxml2 (from .../libxml2_2.7.6.dfsg-1_amd64.deb) ... -Selecting previously deselected package libcroco3. -Unpacking libcroco3 (from .../libcroco3_0.6.2-1_amd64.deb) ... -Selecting previously deselected package gettext-base. -Unpacking gettext-base (from .../gettext-base_0.17-8_amd64.deb) ... -Selecting previously deselected package gettext. -Unpacking gettext (from .../gettext_0.17-8_amd64.deb) ... -Selecting previously deselected package intltool-debian. -Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... -Selecting previously deselected package po-debconf. -Unpacking po-debconf (from .../po-debconf_1.0.16_all.deb) ... -Selecting previously deselected package groff-base. -Unpacking groff-base (from .../groff-base_1.20.1-6_amd64.deb) ... -Selecting previously deselected package bsdmainutils. -Unpacking bsdmainutils (from .../bsdmainutils_8.0.2_amd64.deb) ... -Selecting previously deselected package man-db. -Unpacking man-db (from .../man-db_2.5.6-4_amd64.deb) ... -Selecting previously deselected package debhelper. -Unpacking debhelper (from .../debhelper_7.4.8_all.deb) ... -Setting up libmagic1 (5.03-3) ... -Setting up file (5.03-3) ... -Setting up html2text (1.3.2a-14) ... -Setting up libpcre3 (7.8-3) ... -Setting up libglib2.0-0 (2.22.2-2) ... -Setting up libxml2 (2.7.6.dfsg-1) ... -Setting up libcroco3 (0.6.2-1) ... -Setting up gettext-base (0.17-8) ... -Setting up gettext (0.17-8) ... -Setting up intltool-debian (0.35.0+20060710.1) ... -Setting up po-debconf (1.0.16) ... -Setting up groff-base (1.20.1-6) ... -Setting up bsdmainutils (8.0.2) ... -update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. -Setting up man-db (2.5.6-4) ... -Building database of manual pages ... -Setting up debhelper (7.4.8) ... -Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... -Reading package lists... -Building dependency tree... -Reading state information... -Reading extended state information... -Initializing package states... -Writing extended state information... - -> Finished parsing the build-deps -Reading package lists... -Building dependency tree... -Reading state information... -fakeroot is already the newest version. -0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -I: user script //tmp/hooks/A01_hook starting -failpkg-A-hook-executed -I: user script //tmp/hooks/A01_hook finished -dpkg-buildpackage: set CFLAGS to default value: -g -O2 -dpkg-buildpackage: set CPPFLAGS to default value: -dpkg-buildpackage: set LDFLAGS to default value: -dpkg-buildpackage: set FFLAGS to default value: -g -O2 -dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 -dpkg-buildpackage: source package failpkg -dpkg-buildpackage: source version 0.1 -dpkg-buildpackage: source changed by Junichi Uekawa -dpkg-buildpackage: host architecture amd64 - fakeroot debian/rules clean -dh_testdir -dh_testroot -rm -f build-stamp configure-stamp -# Add here commands to clean up after the build process. -/usr/bin/make clean -make[1]: Entering directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make[1]: *** No rule to make target `clean'. Stop. -make[1]: Leaving directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make: [clean] Error 2 (ignored) -dh_clean -dh_clean: Compatibility levels before 5 are deprecated. - dpkg-source -b failpkg-0.1 -dpkg-source: info: using source format `1.0' -dpkg-source: info: building failpkg using existing failpkg_0.1.orig.tar.gz -dpkg-source: info: building failpkg in failpkg_0.1.diff.gz -dpkg-source: info: building failpkg in failpkg_0.1.dsc - debian/rules build -dh_testdir -# Add here commands to configure the package. -touch configure-stamp -dh_testdir -# Add here commands to compile the package. -/usr/bin/make -make[1]: Entering directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make[1]: *** No targets specified and no makefile found. Stop. -make[1]: Leaving directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make: *** [build-stamp] Error 2 -dpkg-buildpackage: error: debian/rules build gave error exit status 2 -I: user script //tmp/hooks/C01_failhook starting -failpkg-hook-executed -I: user script //tmp/hooks/C01_failhook finished -I: unmounting /home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471 filesystem -I: unmounting dev/pts filesystem -I: unmounting proc filesystem -I: cleaning the build env -I: removing directory /var/cache/pbuilder/build//18619 and its subdirectories diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/changelog pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/changelog --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/changelog 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/changelog 1970-01-01 00:00:00.000000000 +0000 @@ -1,6 +0,0 @@ -failpkg (0.1) unstable; urgency=low - - * a package that fails - - -- Junichi Uekawa Sun, 27 May 2007 14:27:53 +0900 - diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/control pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/control --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/control 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/control 1970-01-01 00:00:00.000000000 +0000 @@ -1,12 +0,0 @@ -Source: failpkg -Section: unknown -Priority: extra -Maintainer: Junichi Uekawa -Build-Depends: debhelper (>= 5) -Standards-Version: 3.7.2 - -Package: failpkg -Architecture: any -Depends: ${shlibs:Depends}, ${misc:Depends} -Description: - diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/rules pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/rules --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/debian/rules 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/debian/rules 1970-01-01 00:00:00.000000000 +0000 @@ -1,98 +0,0 @@ -#!/usr/bin/make -f -# -*- makefile -*- -# Sample debian/rules that uses debhelper. -# This file was originally written by Joey Hess and Craig Small. -# As a special exception, when this file is copied by dh-make into a -# dh-make output file, you may use that output file without restriction. -# This special exception was added by Craig Small in version 0.37 of dh-make. - -# Uncomment this to turn on verbose mode. -#export DH_VERBOSE=1 - - - - -CFLAGS = -Wall -g - -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif - -configure: configure-stamp -configure-stamp: - dh_testdir - # Add here commands to configure the package. - - touch configure-stamp - - -build: build-stamp - -build-stamp: configure-stamp - dh_testdir - - # Add here commands to compile the package. - $(MAKE) - #docbook-to-man debian/failpkg.sgml > failpkg.1 - - touch $@ - -clean: - dh_testdir - dh_testroot - rm -f build-stamp configure-stamp - - # Add here commands to clean up after the build process. - -$(MAKE) clean - - dh_clean - -install: build - dh_testdir - dh_testroot - dh_clean -k - dh_installdirs - - # Add here commands to install the package into debian/failpkg. - $(MAKE) DESTDIR=$(CURDIR)/debian/failpkg install - - -# Build architecture-independent files here. -binary-indep: build install -# We have nothing to do by default. - -# Build architecture-dependent files here. -binary-arch: build install - dh_testdir - dh_testroot - dh_installchangelogs - dh_installdocs - dh_installexamples -# dh_install -# dh_installmenu -# dh_installdebconf -# dh_installlogrotate -# dh_installemacsen -# dh_installpam -# dh_installmime -# dh_python -# dh_installinit -# dh_installcron -# dh_installinfo - dh_installman - dh_link - dh_strip - dh_compress - dh_fixperms -# dh_perl -# dh_makeshlibs - dh_installdeb - dh_shlibdeps - dh_gencontrol - dh_md5sums - dh_builddeb - -binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install configure diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/README pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/README --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg-0.1/README 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg-0.1/README 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -This is an example package that simply fails to build. diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1_amd64.build pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1_amd64.build --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1_amd64.build 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1_amd64.build 1970-01-01 00:00:00.000000000 +0000 @@ -1,225 +0,0 @@ -W: /home/dancer/.pbuilderrc does not exist -I: Building the build Environment -I: extracting base tarball [/var/cache/pbuilder/base.tgz] -I: creating local configuration -I: copying local configuration -I: mounting /proc filesystem -I: mounting /dev/pts filesystem -I: Mounting /home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471 -I: policy-rc.d already exists -I: user script /var/cache/pbuilder/build//18619/tmp/hooks/F01_hook starting -failpkg-F-hook-executed -I: user script /var/cache/pbuilder/build//18619/tmp/hooks/F01_hook finished -Reading package lists... -Building dependency tree... -Reading state information... -passwd is already the newest version. -The following extra packages will be installed: - cdebootstrap libdebian-installer-extra4 libdebian-installer4 libssl0.9.8 - wget -Suggested packages: - pbuilder-uml gdebi cowdancer -Recommended packages: - sudo devscripts -The following NEW packages will be installed: - cdebootstrap libdebian-installer-extra4 libdebian-installer4 libssl0.9.8 - pbuilder wget -0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. -Need to get 2144kB of archives. -After this operation, 6226kB of additional disk space will be used. -Get:1 http://localhost sid/main libssl0.9.8 0.9.8k-7 [979kB] -Get:2 http://localhost sid/main wget 1.12-1.1 [757kB] -Get:3 http://localhost sid/main libdebian-installer4 0.69 [31.0kB] -Get:4 http://localhost sid/main libdebian-installer-extra4 0.69 [12.9kB] -Get:5 http://localhost sid/main cdebootstrap 0.5.5 [32.3kB] -Get:6 http://localhost sid/main pbuilder 0.192 [331kB] -debconf: delaying package configuration, since apt-utils is not installed -Fetched 2144kB in 0s (25.7MB/s) -Selecting previously deselected package libssl0.9.8. -(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 10112 files and directories currently installed.) -Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8k-7_amd64.deb) ... -Selecting previously deselected package wget. -Unpacking wget (from .../wget_1.12-1.1_amd64.deb) ... -Selecting previously deselected package libdebian-installer4. -Unpacking libdebian-installer4 (from .../libdebian-installer4_0.69_amd64.deb) ... -Selecting previously deselected package libdebian-installer-extra4. -Unpacking libdebian-installer-extra4 (from .../libdebian-installer-extra4_0.69_amd64.deb) ... -Selecting previously deselected package cdebootstrap. -Unpacking cdebootstrap (from .../cdebootstrap_0.5.5_amd64.deb) ... -Selecting previously deselected package pbuilder. -Unpacking pbuilder (from .../pbuilder_0.192_all.deb) ... -Setting up libssl0.9.8 (0.9.8k-7) ... -Setting up wget (1.12-1.1) ... -Setting up libdebian-installer4 (0.69) ... -Setting up libdebian-installer-extra4 (0.69) ... -Setting up cdebootstrap (0.5.5) ... -Setting up pbuilder (0.192) ... -I: Setting DEBBUILDOPTS= -W: no hooks of type D found -- ignoring - -> Attempting to satisfy build-dependencies - -> Creating pbuilder-satisfydepends-dummy package -Package: pbuilder-satisfydepends-dummy -Version: 0.invalid.0 -Architecture: amd64 -Maintainer: Debian Pbuilder Team -Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder - This package was created automatically by pbuilder and should -Depends: debhelper (>= 5) -dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. -Reading package lists... -Building dependency tree... -Reading state information... -aptitude is already the newest version. -0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -Selecting previously deselected package pbuilder-satisfydepends-dummy. -(Reading database ... 10312 files and directories currently installed.) -Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ... -dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy: - pbuilder-satisfydepends-dummy depends on debhelper (>= 5); however: - Package debhelper is not installed. -dpkg: error processing pbuilder-satisfydepends-dummy (--install): - dependency problems - leaving unconfigured -Errors were encountered while processing: - pbuilder-satisfydepends-dummy -Reading package lists... -Building dependency tree... -Reading state information... -Initializing package states... -Writing extended state information... -The following NEW packages will be installed: - bsdmainutils{a} debhelper{a} file{a} gettext{a} gettext-base{a} - groff-base{a} html2text{a} intltool-debian{a} libcroco3{a} - libglib2.0-0{a} libmagic1{a} libpcre3{a} libxml2{a} man-db{a} - po-debconf{a} -The following partially installed packages will be configured: - pbuilder-satisfydepends-dummy -0 packages upgraded, 15 newly installed, 0 to remove and 0 not upgraded. -Need to get 8918kB of archives. After unpacking 26.3MB will be used. -Writing extended state information... -Get:1 http://localhost sid/main libmagic1 5.03-3 [389kB] -Get:2 http://localhost sid/main file 5.03-3 [46.9kB] -Get:3 http://localhost sid/main html2text 1.3.2a-14 [103kB] -Get:4 http://localhost sid/main libpcre3 7.8-3 [215kB] -Get:5 http://localhost sid/main libglib2.0-0 2.22.2-2 [984kB] -Get:6 http://localhost sid/main libxml2 2.7.6.dfsg-1 [876kB] -Get:7 http://localhost sid/main libcroco3 0.6.2-1 [125kB] -Get:8 http://localhost sid/main gettext-base 0.17-8 [133kB] -Get:9 http://localhost sid/main gettext 0.17-8 [2503kB] -Get:10 http://localhost sid/main intltool-debian 0.35.0+20060710.1 [30.8kB] -Get:11 http://localhost sid/main po-debconf 1.0.16 [224kB] -Get:12 http://localhost sid/main groff-base 1.20.1-6 [1156kB] -Get:13 http://localhost sid/main bsdmainutils 8.0.2 [198kB] -Get:14 http://localhost sid/main man-db 2.5.6-4 [1477kB] -Get:15 http://localhost sid/main debhelper 7.4.8 [458kB] -debconf: delaying package configuration, since apt-utils is not installed -Fetched 8918kB in 0s (40.3MB/s) -Selecting previously deselected package libmagic1. -(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 10312 files and directories currently installed.) -Unpacking libmagic1 (from .../libmagic1_5.03-3_amd64.deb) ... -Selecting previously deselected package file. -Unpacking file (from .../archives/file_5.03-3_amd64.deb) ... -Selecting previously deselected package html2text. -Unpacking html2text (from .../html2text_1.3.2a-14_amd64.deb) ... -Selecting previously deselected package libpcre3. -Unpacking libpcre3 (from .../libpcre3_7.8-3_amd64.deb) ... -Selecting previously deselected package libglib2.0-0. -Unpacking libglib2.0-0 (from .../libglib2.0-0_2.22.2-2_amd64.deb) ... -Selecting previously deselected package libxml2. -Unpacking libxml2 (from .../libxml2_2.7.6.dfsg-1_amd64.deb) ... -Selecting previously deselected package libcroco3. -Unpacking libcroco3 (from .../libcroco3_0.6.2-1_amd64.deb) ... -Selecting previously deselected package gettext-base. -Unpacking gettext-base (from .../gettext-base_0.17-8_amd64.deb) ... -Selecting previously deselected package gettext. -Unpacking gettext (from .../gettext_0.17-8_amd64.deb) ... -Selecting previously deselected package intltool-debian. -Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... -Selecting previously deselected package po-debconf. -Unpacking po-debconf (from .../po-debconf_1.0.16_all.deb) ... -Selecting previously deselected package groff-base. -Unpacking groff-base (from .../groff-base_1.20.1-6_amd64.deb) ... -Selecting previously deselected package bsdmainutils. -Unpacking bsdmainutils (from .../bsdmainutils_8.0.2_amd64.deb) ... -Selecting previously deselected package man-db. -Unpacking man-db (from .../man-db_2.5.6-4_amd64.deb) ... -Selecting previously deselected package debhelper. -Unpacking debhelper (from .../debhelper_7.4.8_all.deb) ... -Setting up libmagic1 (5.03-3) ... -Setting up file (5.03-3) ... -Setting up html2text (1.3.2a-14) ... -Setting up libpcre3 (7.8-3) ... -Setting up libglib2.0-0 (2.22.2-2) ... -Setting up libxml2 (2.7.6.dfsg-1) ... -Setting up libcroco3 (0.6.2-1) ... -Setting up gettext-base (0.17-8) ... -Setting up gettext (0.17-8) ... -Setting up intltool-debian (0.35.0+20060710.1) ... -Setting up po-debconf (1.0.16) ... -Setting up groff-base (1.20.1-6) ... -Setting up bsdmainutils (8.0.2) ... -update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. -Setting up man-db (2.5.6-4) ... -Building database of manual pages ... -Setting up debhelper (7.4.8) ... -Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... -Reading package lists... -Building dependency tree... -Reading state information... -Reading extended state information... -Initializing package states... -Writing extended state information... - -> Finished parsing the build-deps -Reading package lists... -Building dependency tree... -Reading state information... -fakeroot is already the newest version. -0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -I: user script //tmp/hooks/A01_hook starting -failpkg-A-hook-executed -I: user script //tmp/hooks/A01_hook finished -dpkg-buildpackage: set CFLAGS to default value: -g -O2 -dpkg-buildpackage: set CPPFLAGS to default value: -dpkg-buildpackage: set LDFLAGS to default value: -dpkg-buildpackage: set FFLAGS to default value: -g -O2 -dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 -dpkg-buildpackage: source package failpkg -dpkg-buildpackage: source version 0.1 -dpkg-buildpackage: source changed by Junichi Uekawa -dpkg-buildpackage: host architecture amd64 - fakeroot debian/rules clean -dh_testdir -dh_testroot -rm -f build-stamp configure-stamp -# Add here commands to clean up after the build process. -/usr/bin/make clean -make[1]: Entering directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make[1]: *** No rule to make target `clean'. Stop. -make[1]: Leaving directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make: [clean] Error 2 (ignored) -dh_clean -dh_clean: Compatibility levels before 5 are deprecated. - dpkg-source -b failpkg-0.1 -dpkg-source: info: using source format `1.0' -dpkg-source: info: building failpkg using existing failpkg_0.1.orig.tar.gz -dpkg-source: info: building failpkg in failpkg_0.1.diff.gz -dpkg-source: info: building failpkg in failpkg_0.1.dsc - debian/rules build -dh_testdir -# Add here commands to configure the package. -touch configure-stamp -dh_testdir -# Add here commands to compile the package. -/usr/bin/make -make[1]: Entering directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make[1]: *** No targets specified and no makefile found. Stop. -make[1]: Leaving directory `/home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471/failpkg-0.1' -make: *** [build-stamp] Error 2 -dpkg-buildpackage: error: debian/rules build gave error exit status 2 -I: user script //tmp/hooks/C01_failhook starting -failpkg-hook-executed -I: user script //tmp/hooks/C01_failhook finished -I: unmounting /home/dancer/DEBIAN/pbuilder/pbuilder/testsuite/regression/work/526471 filesystem -I: unmounting dev/pts filesystem -I: unmounting proc filesystem -I: cleaning the build env -I: removing directory /var/cache/pbuilder/build//18619 and its subdirectories Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1.diff.gz and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1.diff.gz differ diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1.dsc pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1.dsc --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1.dsc 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1.dsc 1970-01-01 00:00:00.000000000 +0000 @@ -1,17 +0,0 @@ -Format: 1.0 -Source: failpkg -Binary: failpkg -Architecture: any -Version: 0.1 -Maintainer: Junichi Uekawa -Standards-Version: 3.7.2 -Build-Depends: debhelper (>= 5) -Checksums-Sha1: - 21acc64770c480487aaef9f2646954d0981abf23 208 failpkg_0.1.orig.tar.gz - 48990149747ffcd5d082fd2af1391ebdea4cbab1 1178 failpkg_0.1.diff.gz -Checksums-Sha256: - 845845364e0ccc22c0414dbe01dbe43f86f2468533828d4b5f17a3c1ddeea5d0 208 failpkg_0.1.orig.tar.gz - 9c94f563bff4afb2d2de6a2ea88f8f34286c045140f20445bd3d8072b9ba3a6d 1178 failpkg_0.1.diff.gz -Files: - 355d04744c279e26b326b18016558ba7 208 failpkg_0.1.orig.tar.gz - 700b855b5c4b11364b0584f5fd604260 1178 failpkg_0.1.diff.gz Binary files /tmp/Pr23FPM9Xe/pbuilder-0.215ubuntu7/testsuite/regression/work/526471/failpkg_0.1.orig.tar.gz and /tmp/JIa7CyZDrD/pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471/failpkg_0.1.orig.tar.gz differ diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/A01_hook pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/A01_hook --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/A01_hook 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/A01_hook 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -echo failpkg-A-hook-executed diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/C01_failhook pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/C01_failhook --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/C01_failhook 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/C01_failhook 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -echo failpkg-hook-executed diff -Nru pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/F01_hook pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/F01_hook --- pbuilder-0.215ubuntu7/testsuite/regression/work/526471-hook/F01_hook 2014-03-18 12:56:24.000000000 +0000 +++ pbuilder-0.215+nmu4ubuntu1~ppa1/testsuite/regression/work/526471-hook/F01_hook 1970-01-01 00:00:00.000000000 +0000 @@ -1 +0,0 @@ -echo failpkg-F-hook-executed