Bug#740577: pbuilder build profiles support NMU
Andreas Henriksson
andreas at fatal.se
Mon Jun 22 16:15:10 UTC 2015
Hello all!
On Thu, Jun 18, 2015 at 01:10:01PM +0200, Andreas Henriksson wrote:
> Hello.
>
> Build profiles is apparently live in the Debian archive now!
[...]
> This is my declaration of intent to NMU pbuilder as soon as
> I find time to pursue this further (unless anyone else handles
> this before I get a chance).
[...]
Mattia Rizzolo got in touch with me and mentioned he's interested
in working on pbuilder. His and my previously mentioned changes
are available in http://anonscm.debian.org/cgit/collab-maint/pbuilder.git/
I've now sponsored his upload to DELAYED/10 to give everyone a last
chance to test it and shout before it goes live if there are
any issues.
New debdiff including his changes attached (but please see collab-maint repo).
Regards,
Andreas Henriksson
-------------- next part --------------
diff -Nru pbuilder-0.215+nmu3/bash_completion.d/pbuilder pbuilder-0.215+nmu4/bash_completion.d/pbuilder
--- pbuilder-0.215+nmu3/bash_completion.d/pbuilder 2012-03-25 07:53:45.000000000 +0200
+++ pbuilder-0.215+nmu4/bash_completion.d/pbuilder 2015-06-22 18:04:04.000000000 +0200
@@ -7,7 +7,6 @@
# adapted to pbuilder, the license is GPLv2 or later.
# Copyright 2007 Junichi Uekawa <dancer at debian.org>
-have pbuilder && {
_pbuilder()
{
local cur prev command i
@@ -75,6 +74,5 @@
esac
return 0
-}
+} &&
complete -F _pbuilder pbuilder
-}
diff -Nru pbuilder-0.215+nmu3/debian/changelog pbuilder-0.215+nmu4/debian/changelog
--- pbuilder-0.215+nmu3/debian/changelog 2014-07-11 19:57:49.000000000 +0200
+++ pbuilder-0.215+nmu4/debian/changelog 2015-06-22 18:04:04.000000000 +0200
@@ -1,3 +1,49 @@
+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 <tim at tim-landscheidt.de> 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 <mattia at mapreri.org> Mon, 22 Jun 2015 15:58:41 +0000
+
pbuilder (0.215+nmu3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru pbuilder-0.215+nmu3/debian/control pbuilder-0.215+nmu4/debian/control
--- pbuilder-0.215+nmu3/debian/control 2014-07-11 19:56:43.000000000 +0200
+++ pbuilder-0.215+nmu4/debian/control 2015-06-22 18:04:04.000000000 +0200
@@ -20,6 +20,7 @@
Package: pbuilder
Architecture: all
+Multi-Arch: foreign
Depends: coreutils (>= 4.5.8-1),
debootstrap | cdebootstrap,
dpkg-dev,
diff -Nru pbuilder-0.215+nmu3/debian/copyright pbuilder-0.215+nmu4/debian/copyright
--- pbuilder-0.215+nmu3/debian/copyright 2012-05-31 00:26:38.000000000 +0200
+++ pbuilder-0.215+nmu4/debian/copyright 2015-06-22 18:04:04.000000000 +0200
@@ -5,22 +5,21 @@
Files: *
Copyright: Copyright 2001-2007 Junichi Uekawa
Copyright (C) 2010 Lo?c Minier <lool at dooz.org>
- # 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.215+nmu3/debian/pbuilder.postinst pbuilder-0.215+nmu4/debian/pbuilder.postinst
--- pbuilder-0.215+nmu3/debian/pbuilder.postinst 2008-03-15 03:20:30.000000000 +0100
+++ pbuilder-0.215+nmu4/debian/pbuilder.postinst 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/debian/pbuilder.postrm pbuilder-0.215+nmu4/debian/pbuilder.postrm
--- pbuilder-0.215+nmu3/debian/pbuilder.postrm 2009-02-02 05:55:23.000000000 +0100
+++ pbuilder-0.215+nmu4/debian/pbuilder.postrm 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/debian/pbuilder.preinst pbuilder-0.215+nmu4/debian/pbuilder.preinst
--- pbuilder-0.215+nmu3/debian/pbuilder.preinst 1970-01-01 01:00:00.000000000 +0100
+++ pbuilder-0.215+nmu4/debian/pbuilder.preinst 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/debian/po/tr.po pbuilder-0.215+nmu4/debian/po/tr.po
--- pbuilder-0.215+nmu3/debian/po/tr.po 1970-01-01 01:00:00.000000000 +0100
+++ pbuilder-0.215+nmu4/debian/po/tr.po 2015-06-22 18:04:04.000000000 +0200
@@ -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 <mertdirik at gmail.com>, 2014.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: pbuilder 0.215+nmu3\n"
+"Report-Msgid-Bugs-To: pbuilder at 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 <mertdirik at gmail.com>\n"
+"Language-Team: Debian L10n Turkish <debian-l10n-turkish at lists.debian.org>\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.215+nmu3/debian/source/format pbuilder-0.215+nmu4/debian/source/format
--- pbuilder-0.215+nmu3/debian/source/format 2011-06-24 12:48:46.000000000 +0200
+++ pbuilder-0.215+nmu4/debian/source/format 2015-06-22 10:05:23.000000000 +0200
@@ -1 +1 @@
-1.0
+3.0 (native)
diff -Nru pbuilder-0.215+nmu3/Documentation/debconf7/Makefile pbuilder-0.215+nmu4/Documentation/debconf7/Makefile
--- pbuilder-0.215+nmu3/Documentation/debconf7/Makefile 2007-06-15 11:40:59.000000000 +0200
+++ pbuilder-0.215+nmu4/Documentation/debconf7/Makefile 2015-06-22 10:05:23.000000000 +0200
@@ -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/8GM7rypJet/pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder.pdf and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder.pdf differ
diff -Nru pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.aux pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.aux
--- pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.aux 2007-06-23 14:55:42.000000000 +0200
+++ pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.aux 1970-01-01 01:00:00.000000000 +0100
@@ -1,90 +0,0 @@
-\relax
-\ifx\hyper at 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 at last\relax
-\fi
-
-\@writefile{toc}{\beamer at endinputifotherversion {3.07pt}}
-\@writefile{nav}{\beamer at endinputifotherversion {3.07pt}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{1}{1/1}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {1}{1}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{2}{2/2}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {2}{2}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{3}{3/3}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {3}{3}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{4}{4/4}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {4}{4}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{5}{5/5}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {5}{5}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{6}{6/6}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {6}{6}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{7}{7/7}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {7}{7}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{8}{8/8}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {8}{8}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{9}{9/9}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {9}{9}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{10}{10/10}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {10}{10}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{11}{11/11}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {11}{11}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{12}{12/12}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {12}{12}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{13}{13/13}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {13}{13}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{14}{14/14}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {14}{14}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{15}{15/15}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {15}{15}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{16}{16/16}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {16}{16}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{17}{17/17}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {17}{17}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{18}{18/18}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {18}{18}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{19}{19/19}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {19}{19}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{20}{20/20}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {20}{20}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{21}{21/21}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {21}{21}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{22}{22/22}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {22}{22}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{23}{23/23}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {23}{23}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{24}{24/24}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {24}{24}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{25}{25/25}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {25}{25}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{26}{26/26}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {26}{26}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{27}{27/27}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {27}{27}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{28}{28/28}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {28}{28}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{29}{29/29}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {29}{29}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{30}{30/30}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {30}{30}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{31}{31/31}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {31}{31}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{32}{32/32}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {32}{32}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{33}{33/33}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {33}{33}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{34}{34/34}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {34}{34}}}
-\@writefile{nav}{\headcommand {\slideentry {0}{0}{35}{35/35}{}{0}}}
-\@writefile{nav}{\headcommand {\beamer at framepages {35}{35}}}
-\@writefile{nav}{\headcommand {\beamer at partpages {1}{35}}}
-\@writefile{nav}{\headcommand {\beamer at subsectionpages {1}{35}}}
-\@writefile{nav}{\headcommand {\beamer at sectionpages {1}{35}}}
-\@writefile{nav}{\headcommand {\beamer at documentpages {35}}}
-\@writefile{nav}{\headcommand {\def \inserttotalframenumber {35}}}
Binary files /tmp/8GM7rypJet/pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.dvi and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.dvi differ
diff -Nru pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.log pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.log
--- pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.log 2007-06-23 14:55:42.000000000 +0200
+++ pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.log 1970-01-01 01:00:00.000000000 +0100
@@ -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 <v3.8h> 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 at tempbox=\box26
-\beamer at tempcount=\count79
-\c at beamerpauses=\count80
-
-(/usr/share/texmf/tex/latex/beamer/base/beamerbasedecode.sty
-Package: beamerbasedecode 2007/01/28 (rcs-revision 1.20)
-\beamer at slideinframe=\count81
-\beamer at minimum=\count82
-)
-\beamer at commentbox=\box27
-\beamer at modecount=\count83
-)
-\headheight=\dimen102
-\headdp=\dimen103
-\footheight=\dimen104
-\sidebarheight=\dimen105
-\beamer at tempdim=\dimen106
-\beamer at finalheight=\dimen107
-\beamer at animht=\dimen108
-\beamer at animdp=\dimen109
-\beamer at animwd=\dimen110
-\beamer at leftmargin=\dimen111
-\beamer at rightmargin=\dimen112
-\beamer at leftsidebar=\dimen113
-\beamer at rightsidebar=\dimen114
-\beamer at boxsize=\dimen115
-\beamer at vboxoffset=\dimen116
-\beamer at descdefault=\dimen117
-\beamer at descriptionwidth=\dimen118
-\beamer at lastskip=\skip41
-\beamer at areabox=\box28
-\beamer at animcurrent=\box29
-\beamer at animshowbox=\box30
-\beamer at sectionbox=\box31
-\beamer at logobox=\box32
-\beamer at linebox=\box33
-\beamer at sectioncount=\count84
-\beamer at subsubsectionmax=\count85
-\beamer at subsectionmax=\count86
-\beamer at sectionmax=\count87
-\beamer at totalheads=\count88
-\beamer at headcounter=\count89
-\beamer at partstartpage=\count90
-\beamer at sectionstartpage=\count91
-\beamer at subsectionstartpage=\count92
-\beamer at animationtempa=\count93
-\beamer at animationtempb=\count94
-\beamer at xpos=\count95
-\beamer at ypos=\count96
-\beamer at showpartnumber=\count97
-\beamer at currentsubsection=\count98
-\beamer at coveringdepth=\count99
-\beamer at sectionadjust=\count100
-\beamer at 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 at 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 at req@height=\dimen119
-\Gin at 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 at x=\dimen121
-\pgf at y=\dimen122
-\pgf at xa=\dimen123
-\pgf at ya=\dimen124
-\pgf at xb=\dimen125
-\pgf at yb=\dimen126
-\pgf at xc=\dimen127
-\pgf at 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 at pgf@counta=\count102
-\c at pgf@countb=\count103
-\c at pgf@countc=\count104
-\c at 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 at picminx=\dimen129
-\pgf at picmaxx=\dimen130
-\pgf at picminy=\dimen131
-\pgf at picmaxy=\dimen132
-\pgf at pathminx=\dimen133
-\pgf at pathmaxx=\dimen134
-\pgf at pathminy=\dimen135
-\pgf at pathmaxy=\dimen136
-\pgf at tempdim=\dimen137
-\c at pgf@tempcount=\count106
-\pgf at xx=\dimen138
-\pgf at xy=\dimen139
-\pgf at yx=\dimen140
-\pgf at yy=\dimen141
-\pgf at zx=\dimen142
-\pgf at zy=\dimen143
-)
-(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathconstruct.code.tex
-File: pgfcorepathconstruct.code.tex 2006/10/11 (rcs-revision 1.5)
-\pgf at path@lastx=\dimen144
-\pgf at 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 at shorten@end at additional=\dimen146
-\pgf at shorten@start at 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 at hbox=\box35
-\pgf at layerbox@main=\box36
-\pgf at picture@serial at 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 at pt@x=\dimen149
-\pgf at pt@y=\dimen150
-\pgf at 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 at max=\dimen152
-\pgf at sys@shading at 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 at nummixins=\count109
-\XC at 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 at cnth=\count111
-\Gm at cntv=\count112
-\c at Gm@tempcnt=\count113
-\Gm at bindingoffset=\dimen153
-\Gm at wd@mp=\dimen154
-\Gm at odd@mp=\dimen155
-\Gm at even@mp=\dimen156
-\Gm at 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 at linkcounter=\count114
-\Hy at 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 at menulength=\count116
-\Field at Width=\dimen158
-\Fld at charsize=\dimen159
-\Choice at toks=\toks17
-\Field at 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 at box=\box37
-\Fld at 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 at argscount=\count118
-\beamer at lastskipcover=\skip42
-\beamer at 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 at lecture=\count120
-\c at part=\count121
-\c at section=\count122
-\c at subsection=\count123
-\c at subsubsection=\count124
-)
-(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframe.sty
-Package: beamerbaseframe 2007/01/28 (rcs-revision 1.60)
-\beamer at framebox=\box38
-\beamer at frametitlebox=\box39
-\beamer at zoombox=\box40
-\beamer at zoomcount=\count125
-\beamer at zoomframecount=\count126
-\beamer at frametextheight=\dimen160
-\c at subsectionslide=\count127
-\beamer at frametopskip=\skip43
-\beamer at framebottomskip=\skip44
-\beamer at frametopskipautobreak=\skip45
-\beamer at framebottomskipautobreak=\skip46
-\beamer at envbody=\toks19
-\c at framenumber=\count128
-)
-(/usr/share/texmf/tex/latex/beamer/base/beamerbaseverbatim.sty
-Package: beamerbaseverbatim 2007/01/28 (rcs-revision 1.8)
-\beamer at verbatimfileout=\write3
-)
-(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframesize.sty
-Package: beamerbaseframesize 2007/01/28 (rcs-revision 1.18)
-\beamer at splitbox=\box41
-\beamer at autobreakcount=\count129
-\beamer at autobreaklastheight=\dimen161
-\beamer at frametitletoks=\toks20
-\beamer at framesubtitletoks=\toks21
-)
-(/usr/share/texmf/tex/latex/beamer/base/beamerbaseframecomponents.sty
-Package: beamerbaseframecomponents 2007/01/28 (rcs-revision 1.41)
-\beamer at 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 at 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 at 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 at box=\box44
-\bmb at colorbox=\box45
-\bmb at boxshadow=\box46
-\bmb at boxshadowball=\box47
-\bmb at boxshadowballlarge=\box48
-\bmb at temp=\dimen162
-\bmb at dima=\dimen163
-\bmb at dimb=\dimen164
-\bmb at prevheight=\dimen165
-)
-\beamer at 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 at figure=\count130
-\c at 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 at 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 at 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 at depth=\count137
-\c at MaxMatrixCols=\count138
-\dotsspace@=\muskip11
-\c at parentequation=\count139
-\dspbrk at lvl=\count140
-\tag at 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 at 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 at style=\toks29
-\thm at bodyfont=\toks30
-\thm at headfont=\toks31
-\thm at notefont=\toks32
-\thm at headpunct=\toks33
-\thm at preskip=\skip52
-\thm at postskip=\skip53
-\thm at headsep=\skip54
-\dth at everypar=\toks34
-)
-\c at 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 at dima=\dimen176
-\beamer at 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 at 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)
-<openlogo-light.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)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[2
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[3
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[4
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[5
-
-]
-File: chroot.eps Graphic file (type eps)
- <chroot.eps>
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[6
-
-]
-File: chroot-pbuilder.eps Graphic file (type eps)
- <chroot-pbuilder.eps>
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[7
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[8
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[9
-
-]
-File: pbuildercycle.eps Graphic file (type eps)
- <pbuildercycle.eps>
-Overfull \hbox (17.38577pt too wide) in paragraph at lines 104--104
-[][]
- []
-
-File: openlogo-light.eps Graphic file (type eps)
-<openlogo-light.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)
-<openlogo-light.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)
-<openlogo-light.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)
-<openlogo-light.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)
-<openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[14
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.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 <danc
-er at debian.org>[]
- []
-
-
-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 <sourcepackage>-<upstreamversion> `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)
-<openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[16
-
-]
-File: develcycle.eps Graphic file (type eps)
- <develcycle.eps>
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.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)
-<openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[18
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[19
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[20
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[21
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.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)
-<openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[23
-
-]
-File: qemubuilder-create.eps Graphic file (type eps)
- <qemubuilder-create.eps>
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[24
-
-]
-File: qemubuilder-build.eps Graphic file (type eps)
- <qemubuilder-build.eps>
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[25
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[26
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[27
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.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)
-<openlogo-light.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)
-<openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[30
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[31
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[32
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[33
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[34
-
-]
-File: openlogo-light.eps Graphic file (type eps)
- <openlogo-light.eps>
-Overfull \vbox (19.70001pt too high) has occurred while \output is active []
-
-
-[35
-
-]
-\tf at nav=\write5
-\openout5 = `pbuilder-presentation.nav'.
-
-\tf at toc=\write6
-\openout6 = `pbuilder-presentation.toc'.
-
-\tf at 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.215+nmu3/Documentation/debconf7/pbuilder-presentation.nav pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.nav
--- pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.nav 2007-06-23 14:55:42.000000000 +0200
+++ pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.nav 1970-01-01 01:00:00.000000000 +0100
@@ -1,76 +0,0 @@
-\beamer at endinputifotherversion {3.07pt}
-\headcommand {\slideentry {0}{0}{1}{1/1}{}{0}}
-\headcommand {\beamer at framepages {1}{1}}
-\headcommand {\slideentry {0}{0}{2}{2/2}{}{0}}
-\headcommand {\beamer at framepages {2}{2}}
-\headcommand {\slideentry {0}{0}{3}{3/3}{}{0}}
-\headcommand {\beamer at framepages {3}{3}}
-\headcommand {\slideentry {0}{0}{4}{4/4}{}{0}}
-\headcommand {\beamer at framepages {4}{4}}
-\headcommand {\slideentry {0}{0}{5}{5/5}{}{0}}
-\headcommand {\beamer at framepages {5}{5}}
-\headcommand {\slideentry {0}{0}{6}{6/6}{}{0}}
-\headcommand {\beamer at framepages {6}{6}}
-\headcommand {\slideentry {0}{0}{7}{7/7}{}{0}}
-\headcommand {\beamer at framepages {7}{7}}
-\headcommand {\slideentry {0}{0}{8}{8/8}{}{0}}
-\headcommand {\beamer at framepages {8}{8}}
-\headcommand {\slideentry {0}{0}{9}{9/9}{}{0}}
-\headcommand {\beamer at framepages {9}{9}}
-\headcommand {\slideentry {0}{0}{10}{10/10}{}{0}}
-\headcommand {\beamer at framepages {10}{10}}
-\headcommand {\slideentry {0}{0}{11}{11/11}{}{0}}
-\headcommand {\beamer at framepages {11}{11}}
-\headcommand {\slideentry {0}{0}{12}{12/12}{}{0}}
-\headcommand {\beamer at framepages {12}{12}}
-\headcommand {\slideentry {0}{0}{13}{13/13}{}{0}}
-\headcommand {\beamer at framepages {13}{13}}
-\headcommand {\slideentry {0}{0}{14}{14/14}{}{0}}
-\headcommand {\beamer at framepages {14}{14}}
-\headcommand {\slideentry {0}{0}{15}{15/15}{}{0}}
-\headcommand {\beamer at framepages {15}{15}}
-\headcommand {\slideentry {0}{0}{16}{16/16}{}{0}}
-\headcommand {\beamer at framepages {16}{16}}
-\headcommand {\slideentry {0}{0}{17}{17/17}{}{0}}
-\headcommand {\beamer at framepages {17}{17}}
-\headcommand {\slideentry {0}{0}{18}{18/18}{}{0}}
-\headcommand {\beamer at framepages {18}{18}}
-\headcommand {\slideentry {0}{0}{19}{19/19}{}{0}}
-\headcommand {\beamer at framepages {19}{19}}
-\headcommand {\slideentry {0}{0}{20}{20/20}{}{0}}
-\headcommand {\beamer at framepages {20}{20}}
-\headcommand {\slideentry {0}{0}{21}{21/21}{}{0}}
-\headcommand {\beamer at framepages {21}{21}}
-\headcommand {\slideentry {0}{0}{22}{22/22}{}{0}}
-\headcommand {\beamer at framepages {22}{22}}
-\headcommand {\slideentry {0}{0}{23}{23/23}{}{0}}
-\headcommand {\beamer at framepages {23}{23}}
-\headcommand {\slideentry {0}{0}{24}{24/24}{}{0}}
-\headcommand {\beamer at framepages {24}{24}}
-\headcommand {\slideentry {0}{0}{25}{25/25}{}{0}}
-\headcommand {\beamer at framepages {25}{25}}
-\headcommand {\slideentry {0}{0}{26}{26/26}{}{0}}
-\headcommand {\beamer at framepages {26}{26}}
-\headcommand {\slideentry {0}{0}{27}{27/27}{}{0}}
-\headcommand {\beamer at framepages {27}{27}}
-\headcommand {\slideentry {0}{0}{28}{28/28}{}{0}}
-\headcommand {\beamer at framepages {28}{28}}
-\headcommand {\slideentry {0}{0}{29}{29/29}{}{0}}
-\headcommand {\beamer at framepages {29}{29}}
-\headcommand {\slideentry {0}{0}{30}{30/30}{}{0}}
-\headcommand {\beamer at framepages {30}{30}}
-\headcommand {\slideentry {0}{0}{31}{31/31}{}{0}}
-\headcommand {\beamer at framepages {31}{31}}
-\headcommand {\slideentry {0}{0}{32}{32/32}{}{0}}
-\headcommand {\beamer at framepages {32}{32}}
-\headcommand {\slideentry {0}{0}{33}{33/33}{}{0}}
-\headcommand {\beamer at framepages {33}{33}}
-\headcommand {\slideentry {0}{0}{34}{34/34}{}{0}}
-\headcommand {\beamer at framepages {34}{34}}
-\headcommand {\slideentry {0}{0}{35}{35/35}{}{0}}
-\headcommand {\beamer at framepages {35}{35}}
-\headcommand {\beamer at partpages {1}{35}}
-\headcommand {\beamer at subsectionpages {1}{35}}
-\headcommand {\beamer at sectionpages {1}{35}}
-\headcommand {\beamer at documentpages {35}}
-\headcommand {\def \inserttotalframenumber {35}}
Binary files /tmp/8GM7rypJet/pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.pdf and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.pdf differ
diff -Nru pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.toc pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.toc
--- pbuilder-0.215+nmu3/Documentation/debconf7/pbuilder-presentation.toc 2007-06-23 14:55:42.000000000 +0200
+++ pbuilder-0.215+nmu4/Documentation/debconf7/pbuilder-presentation.toc 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-\beamer at endinputifotherversion {3.07pt}
diff -Nru pbuilder-0.215+nmu3/Documentation/Makefile pbuilder-0.215+nmu4/Documentation/Makefile
--- pbuilder-0.215+nmu3/Documentation/Makefile 2012-12-24 05:54:00.000000000 +0100
+++ pbuilder-0.215+nmu4/Documentation/Makefile 2015-06-22 10:05:23.000000000 +0200
@@ -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.215+nmu3/Documentation/pbuilder-doc.de.html pbuilder-0.215+nmu4/Documentation/pbuilder-doc.de.html
--- pbuilder-0.215+nmu3/Documentation/pbuilder-doc.de.html 2013-03-02 08:37:59.000000000 +0100
+++ pbuilder-0.215+nmu4/Documentation/pbuilder-doc.de.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,1033 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Pbuilder-Benutzerhandbuch</title><link rel="stylesheet" type="text/css" href="pbuilder-doc.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div lang="de" class="book" title="Pbuilder-Benutzerhandbuch"><div class="titlepage"><div><div><h1 class="title"><a name="idp232720"></a>Pbuilder-Benutzerhandbuch</h1></div><div><h2 class="subtitle">Aufruf und Betrieb</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Junichi</span> <span class="surname">Uekawa</span></h3></div></div></div><div><p class="releaseinfo">Dokumentation in Entwicklung</p></div></div><hr></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="chapter"><a href="#introduction">1. Einf?hrung in Pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#aim">1. Ziele von Pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#usingpbuilder">2. Pbuilder benutzen</a></span></dt><dd><dl><dt><span class="sect1"><a href="#creatingbase">1. Einen Basis-Chroot-Tarball erstellen</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Das base.tgz aktualisieren</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Ein Paket unter Benutzung von base.tgz bauen</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Debian-Entwicklern das Tippen erleichtern, Pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Konfigurationsdateien</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Pakete innerhalb der Chroot bauen ohne Root zu sein</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Pbuilder zur R?ckportierung benutzen</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Massenhaft Pakete bauen</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Automatische R?ckportierungsskripte</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Pbuilder f?r das automatisierte Testen von Paketen benutzen</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen</a></span></dt></dl></dd><dt><span class="chapter"><a href="#pbuilder-uml">3. User Mode Linux mit Pbuilder benutzen</a></span></dt><dd><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. User Mode Linux konfigurieren</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Rootstrap konfigurieren</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Pbuilder-uml konfigurieren</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Betrachtungen, um Pbuilder-user-mode-linux auszuf?hren</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Paralleles Ausf?hren von Pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle
-Maschine zu starten</a></span></dt></dl></dd><dt><span class="chapter"><a href="#faq">4. H?ufig gestellte Fragen </a></span></dt><dd><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. Fehlschlagen des Erstellens mit Pbuilder</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Verzeichnisse, bei denen kein Bind-Mount m?glich ist</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. In Pbuilder anmelden, um die Umgebung zu ?ndern</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. BUILDRESULTUID f?r Sudo-Sitzungen setzen</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Anmerkungen zum Gerauch von $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Ein K?rzel erstellen, um <span class="command"><strong>pbuilder</strong></span> mit einer speziellen
-Distribution auszuf?hren.</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Umgebungsvariablen benutzen, um <span class="command"><strong>pbuilder</strong></span> f?r eine
-spezielle Distribution auszuf?hren.
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. Wie kann erreicht werden, dass Pbuilder ?apt-get update? ausf?hrt, bevor es
-versucht die Build-Abh?ngigkeiten zu erf?llen?</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Eine Chroot-Erinnerung erstellen</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. /var/cache/apt/archives f?r den Paket-Zwischenspeicher benutzen</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. Pbuilder auf Debian-Stable-Releases zur?ckportiert</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warnung, dass LOGNAME nicht definiert wurde</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. ?Build-Conflikt? mit wesentlichem Paket nicht m?glich</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Vermeiden der Nachricht ?ln: Ung?ltiger Link ?ber Ger?tegrenzen hinweg?</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Fakechroot benutzen</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Debconf innerhalb von Pbuilder-Sitzungen benutzen</a></span></dt><dt><span class="sect1"><a href="#nodev">20. ?nodev?-Einh?ngeoptionen behindern Pbuilder-Aktivit?t</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. Pbuilder ist langsam</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Pdebuild zum F?rdern eines Pakets benutzen</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Warum liegt in ../ eine source.changes-Datei?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. Die Modi ?amd64? und ?i386?</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Tmpfs f?r ?buildplace? benutzen</a></span></dt><dt><span class="sect1"><a href="#idp6254448">26. Svn-buildpackage zusammen mit Pbuilder benutzen</a></span></dt></dl></dd><dt><span class="chapter"><a href="#develanddebug">5. Fehlerbehebung und Entwicklung</a></span></dt><dd><dl><dt><span class="sect1"><a href="#bugreport">1. Fehler berichten </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailingliste</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC-Kanal</a></span></dt><dt><span class="sect1"><a href="#development">4. Informationen f?r Pbuilder-Entwickler</a></span></dt></dl></dd><dt><span class="chapter"><a href="#otheruse">6. Andere Verwendungen von Pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#chroot">1. Pbuilder f?r kleine Experimente benutzen</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Kleine Programme innerhalb der Chroot ausf?hren</a></span></dt></dl></dd><dt><span class="chapter"><a href="#experimental">7. Experimental or wishlist features of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#lvm">1. LVM benutzen</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Cowdancer benutzen</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Pbuilder ohne tar.gz verwenden</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. PBuilder in einem Vserver verwenden</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Gebrauch von Ccache</a></span></dt></dl></dd><dt><span class="chapter"><a href="#refs">8. Referenzmaterial</a></span></dt><dd><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Verzeichnisstruktur au?erhalb der Chroot</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Verzeichnisstruktur innerhalb der Chroot</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp6404320">9. Nebens?chliche arch?ologische Einzelheiten</a></span></dt><dd><dl><dt><span class="sect1"><a href="#idp6405072">1. Dokumentations-Chronik </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. M?glicherweise ungenaue Hintergrundgeschichte von Pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp6415312">2.1. Zeit vor Pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Geburt von Pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. Und sein zweites Lebensjahr</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Das f?nfte Jahr von Pbuilder</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>Tabellenverzeichnis</b></p><dl><dt>5.1. <a href="#dirtestsuites">Verzeichnisstruktur der Test-Suite</a></dt><dt>8.1. <a href="#idp6349808">Verzeichnisstruktur au?erhalb der Chroot </a></dt><dt>8.2. <a href="#idp6381456">Verzeichnisstruktur innerhalb der Chroot </a></dt></dl></div><div class="chapter" title="Kapitel 1. Einf?hrung in Pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="introduction"></a>Kapitel 1. Einf?hrung in Pbuilder</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#aim">1. Ziele von Pbuilder</a></span></dt></dl></div><div class="sect1" title="1. Ziele von Pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="aim"></a>1. Ziele von Pbuilder</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> steht f?r ?Personal Builder? und ist ein
-automatisches System zum Bau von Debian-Paketen f?r pers?nliche
-Entwickler-Arbeitsplatzumgebungen. Ziel von <span class="command"><strong>pbuilder</strong></span> ist
-es, ein einfach einzurichtendes System zum automatischen Bau von
-Debian-Paketen innerhalb einer Reinraumumgebung zu sein, so dass eine
-Pr?fung, ob ein Paket in den meisten Debian-Installationen gebaut werden
-kann, m?glich ist. Die Reinraumumgebung wird durch den Gebrauch eines
-Chroot-Images erreicht, so dass nur eine minimale Zahl von Paketen innerhalb
-der Chroot installiert wird.
- </p><p>
- 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-Abh?ngigkeiten.
- </p><p>
- Das vorrangige Ziel von <span class="command"><strong>pbuilder</strong></span> unterscheidet sich von
-anderen automatischen Bausystemen in Debian darin, dass es nicht das Ziel
-hat, so viele Pakete wie m?glich zu bauen. Es versucht nicht abzusch?tzen,
-was ein Paket ben?tigt und probiert, wenn eine Auswahl zu treffen ist, in
-den meisten F?llen die schlechtest m?gliche Auswahl von allen.
- </p><p>
- Auf diese Art versucht <span class="command"><strong>pbuilder</strong></span> sicherzustellen, dass
-Pakete, die mit <span class="command"><strong>pbuilder</strong></span> getestet wurden, auf den meisten
-Debian-Installationen ordentlich gebaut werden, was hoffentlich in einer
-guten umfassenden Erstellbarkeit von Debian aus den Quellen resultiert.
- </p><p>
- Das Ziel, Debian aus den Quellen erstellbar zu machen, ist einigerma?en
-vollendet und hat gute Fortschritte gemacht. In fr?heren 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.
- </p></div></div><div class="chapter" title="Kapitel 2. Pbuilder benutzen"><div class="titlepage"><div><div><h2 class="title"><a name="usingpbuilder"></a>Kapitel 2. Pbuilder benutzen</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#creatingbase">1. Einen Basis-Chroot-Tarball erstellen</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Das base.tgz aktualisieren</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Ein Paket unter Benutzung von base.tgz bauen</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Debian-Entwicklern das Tippen erleichtern, Pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Konfigurationsdateien</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Pakete innerhalb der Chroot bauen ohne Root zu sein</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Pbuilder zur R?ckportierung benutzen</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Massenhaft Pakete bauen</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Automatische R?ckportierungsskripte</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Pbuilder f?r das automatisierte Testen von Paketen benutzen</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen</a></span></dt></dl></div><p>
- Es gibt mehrere einfache Befehle f?r den Betrieb. Normalerweise werden die
-Befehle <span class="command"><strong>pbuilder create</strong></span>, <span class="command"><strong>pbuilder
-update</strong></span> und <span class="command"><strong>pbuilder build</strong></span> benutzt. Sie werden
-nun nacheinander vorgestellt.
- </p><div class="sect1" title="1. Einen Basis-Chroot-Tarball erstellen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creatingbase"></a>1. Einen Basis-Chroot-Tarball erstellen</h2></div></div></div><p>
- <span class="command"><strong>pbuilder create</strong></span> 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 <span class="command"><strong><code class="option">--distribution</code></strong></span>
-angegeben werden.
- </p><p>
- <span class="command"><strong>debootstrap</strong></span> <sup>[<a name="idp4402320" href="#ftn.idp4402320" class="footnote">1</a>]</sup> wird
-benutzt, um die reine minimale Debian-Installation zu erstellen. Dann werden
-Build-essential-Pakete auf der minimalen Installation unter Benutzung von
-<span class="command"><strong>apt-get</strong></span> innerhalb der Chroot installiert.
- </p><p>
- F?r weitere Dokumentationen der Befehlszeilenoptionen lesen Sie die
-Handbuchseite pbuilder.8. Zur Benutzung wird manche Konfiguration von
-<code class="filename">/etc/pbuilderrc</code> f?r die Spiegel-Site <sup>[<a name="idp4405568" href="#ftn.idp4405568" class="footnote">2</a>]</sup> n?tig sein und es k?nnte notwendig sein, den Proxy
-zu konfigurieren, um Zugriff ?ber HTTP zu erlauben. Einzelheiten finden Sie
-in der Handbuchseite von pbuilderrc.5.
- </p></div><div class="sect1" title="2. Das base.tgz aktualisieren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="basechroot"></a>2. Das base.tgz aktualisieren</h2></div></div></div><p><span class="command"><strong>pbuilder update</strong></span> will update the base.tgz. It will
-extract the chroot, invoke <span class="command"><strong>apt-get update</strong></span> and
-<span class="command"><strong>apt-get dist-upgrade</strong></span> inside the chroot, and then recreate
-the base.tgz (the base tar-ball).
- </p><p>
- Es ist m?glich, die Distribution zu wechseln auf die base.tgz an diesem
-Punkt verweist. Geben Sie <span class="command"><strong><code class="option">--distribution
-<em class="parameter"><code>sid</code></em></code>
-<code class="option">--override-config</code></strong></span> an, um die Distribution auf Sid
-zu ?ndern. <sup>[<a name="idp69040" href="#ftn.idp69040" class="footnote">3</a>]</sup>
- </p><p>
- Weitere Dokumentationen der Befehlszeilenoptionen finden Sie auf der
-Handbuchseite pbuilder.8.
- </p></div><div class="sect1" title="3. Ein Paket unter Benutzung von base.tgz bauen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="buildpackagechroot"></a>3. Ein Paket unter Benutzung von base.tgz bauen</h2></div></div></div><p>
- Um ein Paket innerhalb der Chroot zu bauen, rufen Sie <span class="command"><strong>pbuilder
-build <code class="option">wasauchimmer.dsc</code></strong></span>
-auf. <span class="command"><strong>pbuilder</strong></span> wird das base.tgz in ein tempor?res
-Verzeichnis extrahieren, mit Chroot in das Verzeichnis wechseln, die
-Build-Abh?ngigkeiten erf?llen und das Paket bauen. Das gebaute Paket wird in
-das Verzeichnis verschoben, das mit der Befehlszeilenoption
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> angegeben wurde.
- </p><p>
- Die Option <span class="command"><strong><code class="option">--basetgz</code></strong></span> kann benutzt
-werden, um anzugeben, welche base.tgz benutzt werden soll.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> wird ein frisches Chroot-Basis-Image aus
-base.tgz extrahieren (base.tgz wird mit <span class="command"><strong>pbuilder create</strong></span>
-erstellt und mit <span class="command"><strong>pbuilder update</strong></span> aktualisiert). Die
-Chroot wird durch Auswertung von debian/control und Aufruf von
-<span class="command"><strong>apt-get</strong></span> mit Build-Abh?ngigkeiten best?ckt.
- </p><p>
- Weitere Dokumentationen der Befehlszeilenoptionen finden Sie auf der
-Handbuchseite pbuilder.8.
- </p></div><div class="sect1" title="4. Debian-Entwicklern das Tippen erleichtern, Pdebuild"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pdebuild"></a>4. Debian-Entwicklern das Tippen erleichtern, Pdebuild</h2></div></div></div><p>
- <span class="command"><strong>pdebuild</strong></span> ist ein kleines Wrapper-Skript, das die
-h?ufigsten aller Aufgaben erledigt. Ein Debian-Entwickler k?nnte versuchen,
-<span class="command"><strong>debuild</strong></span> auszuf?hren und ein Paket innerhalb eines
-Debian-Quellverzeichnisses zu bauen. <span class="command"><strong>pdebuild</strong></span> wird eine
-?hnliche Steuerung erlauben und erm?glichen, dass Pakete innerhalb der
-Chroot gebaut werden, um zu pr?fen, ob der aktuelle Quellbaum
-geschickterweise innerhalb der Chroot gebaut wird.
- </p><p>
- <span class="command"><strong>pdebuild</strong></span> ruft zum Bau der Quellpakete
-<span class="command"><strong>dpkg-source</strong></span> und dann f?r das resultierende Quellpaket
-<span class="command"><strong>pbuilder</strong></span> auf. Anders als bei Debuild k?nnen die
-resultierenden Deb-Dateien jedoch im mit
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> angegebenen Verzeichnis
-gefunden werden.
- </p><p>
- Weitere Einzelheiten finden Sie auf der Handbuchseite pdebuild.1.
- </p><p>
- Es gibt einen etwas anderen Betriebsmodus, der in
-<span class="command"><strong>pdebuild</strong></span> seit Version 0.97 verf?gbar
-ist. <span class="command"><strong>pdebuild</strong></span> f?hrt <span class="command"><strong>debian/rules clean</strong></span>
-normalerweise au?erhalb der Chroot aus; es ist jedoch m?glich, dieses
-Verhalten mit <span class="command"><strong><code class="option">--use-pdebuild-internal</code></strong></span> zu
-?ndern, damit es innerhalb der Chroot l?uft. Es wird versuchen, das
-Arbeitsverzeichnis innerhalb der Chroot einzuh?ngen und
-<span class="command"><strong>dpkg-buildpackage</strong></span> darin auszuf?hren. Es hat die folgenden
-Merkmale und ist noch nicht der Standardbetriebsmodus.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- erf?llt die Build-Abh?ngigkeiten innerhalb der Chroot, bevor das Quellpaket
-erstellt wird (was ein guter Punkt ist, den
-Standard-<span class="command"><strong>pdebuild</strong></span> nicht beherrscht)
- </p></li><li class="listitem"><p>Das Arbeitsverzeichnis wird von innerhalb der Chroot ge?ndert.</p></li><li class="listitem"><p>Bauen mit <span class="command"><strong>pdebuild</strong></span> garantiert nicht, dass dies mit
-<span class="command"><strong>pbuilder</strong></span> funktioniert.</p></li><li class="listitem"><p>Falls das Erstellen des Quellpakets fehlschl?gt, ist die Sitzung vergeudet,
-die die Chroot verwendet (Erstellen einer Chroot nimmt etwas Zeit in
-Anspruch, was mit Cowdancer verbessert werden sollte).</p></li><li class="listitem"><p>funktioniert nicht auf die gleiche Weise wie gewohnt; zum Beispiel hat
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> keine Auswirkungen.</p></li><li class="listitem"><p>Das Bauen innerhalb der Chroot ist mit dem aktuellen Benutzer au?erhalb der
-Chroot ausgef?hrt worden.
- </p></li></ul></div></div><div class="sect1" title="5. Konfigurationsdateien"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configfile"></a>5. Konfigurationsdateien</h2></div></div></div><p>
- Es ist m?glich, alle Einstellungen mit Befehlszeilenoptionen
-anzugeben. Wegen des Eingabekomforts ist es jedoch m?glich, eine
-Konfigurationsdatei zu benutzen.
- </p><p>
- Wenn <span class="command"><strong>pbuilder</strong></span> aufgerufen wird, werden
-<code class="filename">/etc/pbuilderrc</code> und
-<code class="filename">${HOME}/.pbuilderrc</code> gelesen. Die m?glichen Optionen
-sind in der Handbuchseite pbuilderrc.5 dokumentiert.
- </p><p>
- Es ist n?tzlich, die Option <code class="option">--configfile</code> zu benutzen, um
-eine voreingestellte Konfigurationsdatei zu laden, wenn zwischen
-Konfigurationsdateien verschiedener Distributionen gewechselt wird.
- </p><p>
- Bitte beachten Sie, dass <code class="filename">${HOME}/.pbuilderrc</code>
-Systemeinstellungen aufhebt. Als Vorsichtsma?nahme, wenn Sie ?ber irgendeine
-Konfiguration verf?gen, m?ssen Sie die Konfiguration so optimieren, dass sie
-bei einem Upgrade mit neuen Versionen von Pbuilder funktioniert.
- </p></div><div class="sect1" title="6. Pakete innerhalb der Chroot bauen ohne Root zu sein"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonrootchroot"></a>6. Pakete innerhalb der Chroot bauen ohne Root zu sein</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
-<span class="command"><strong>pbuilder</strong></span> can create a user which is only used inside
-<span class="command"><strong>pbuilder</strong></span> and use that user id when building, and use the
-<span class="command"><strong>fakeroot</strong></span> command when root privilege is required.
- </p><p>
- Die Konfigurationsoption BUILDUSERID sollte auf einen Wert f?r eine
-Benutzer-ID gesetzt werden, die noch nicht auf dem System existiert, so dass
-es f?r Pakete, die mit <span class="command"><strong>pbuilder</strong></span> erstellt werden,
-schwieriger wird, die Umgebung au?erhalb der Chroot zu beeinflussen. Wenn
-au?erdem die Konfigurationsoption BUILDUSERNAME gesetzt ist, wird
-<span class="command"><strong>pbuilder</strong></span> den angegebenen Benutzernamen verwenden und zum
-Bauen von Paketen Fakeroot verwenden, anstatt es als Root innerhalb der
-Chroot auszuf?hren.
- </p><p>
- Sogar wenn die Fakeroot-Methode benutzt wird, wird
-<span class="command"><strong>pbuilder</strong></span> mit Root-Rechten ausgef?hrt, wenn dies
-erforderlich ist. Wenn beispielsweise Pakete in die Chroot installiert
-werden, wird <span class="command"><strong>pbuilder</strong></span> mit Root-Rechten ausgef?hrt.
- </p><p>
- Um <span class="command"><strong>pbuilder</strong></span> aufrufen zu k?nnen ohne Root zu sein, m?ssen
-Sie User Mode Linux benutzen, wie es unter <a class="xref" href="#pbuilder-uml" title="Kapitel 3. User Mode Linux mit Pbuilder benutzen">Kapitel?3, <i>User Mode Linux mit Pbuilder benutzen</i></a>
-erkl?rt wird.
- </p></div><div class="sect1" title="7. Pbuilder zur R?ckportierung benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="backporting"></a>7. Pbuilder zur R?ckportierung benutzen</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> kann benutzt werden, um Software von der letzten
-Debian-Distribution auf eine ?ltere stabile Version zur?ck zu portieren,
-indem eine Chroot benutzt wird, die ein Image der ?lteren Distribution
-enth?lt, und die Pakete innerhalb der Chroot erstellt werden. Es sind
-mehrere Punkte zu beachten und wegen der folgenden Gr?nde ist automatische
-R?ckportierung normalerweise nicht m?glich und manuelle Interaktion
-erforderlich:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Das Paket von der Distribution Unstable k?nnte von Paketen oder
-Paketversionen abh?ngig sein, die nur in Unstable verf?gbar sind. Daher ist
-es vielleicht nicht m?glich, Build-Abh?ngigkeiten zu erf?llen: auf Stable
-(ohne zus?tzliche R?ckportierungsarbeiten).</p></li><li class="listitem"><p>Die Distribution Stable k?nnte Fehler haben, die in Unstable behoben wurden
-und an denen gearbeitet werden muss.</p></li><li class="listitem"><p>Das Paket in der Distribution Unstable k?nnte sogar Bauprobleme in Unstable
-haben.</p></li></ul></div></div><div class="sect1" title="8. Massenhaft Pakete bauen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="massbuild"></a>8. Massenhaft Pakete bauen</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> kann automatisiert werden, da seine Operationen
-nicht interaktiv sind. Es ist m?glich, <span class="command"><strong>pbuilder</strong></span> f?r
-mehrere Pakete ohne Benutzerinteraktion auszuf?hren. Es ist bekannt, dass
-mehrere solche Skripte existieren. Junichi Uekawa f?hrt solch ein Skript
-seit 2001 aus und reichte Fehlerberichte gegen Pakete ein, die beim Test von
-<span class="command"><strong>pbuilder</strong></span> scheiterten. Es gab mehrere Probleme beim
-automatischen Erstellen:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Build-Abh?ngigkeiten mussten interaktiv installiert werden, aber einige
-Pakete waren so kaputt, dass sie nicht ohne einzugreifen installiert werden
-konnten (wie PostgreSQL).</p></li><li class="listitem"><p>Wenn ein Bibliothekpaket, gcc/gcj/g++ oder sogar Bison kaputtging, wurde
-eine gro?e Zahl gescheiterter Builds gemeldet. (gcj-3.0, das kein ?javac?
-hatte, Bison, das sich strenger verhielt, etc.)
- </p></li><li class="listitem"><p>Einige Leute waren ziemlich ver?rgert ?ber Berichte fehlgeschlagener Builds.</p></li></ul></div><p>
- Die meisten anf?nglichen Fehler wurden im
-<span class="command"><strong>pbuilder</strong></span>-Kehraus um das Jahr 2002 gel?st, aber von Zeit
-zu Zeit treten einige ?bergangsprobleme auf, die eine gro?e Zahl von
-Debian-Archiven beeinflussen.Regressionstests haben ihren Preis.
- </p><p>
- Ein Skript, das in der anf?nglichen Ausf?hrung von Junichi Uekawa benutzt
-wurde, ist im nun verbreiteten <span class="command"><strong>pbuilder</strong></span> als
-<span class="command"><strong>pbuildd.sh</strong></span> enthalten. Es liegt in
-<code class="filename">/usr/share/doc/pbuilder/examples/pbuildd/</code> und seine
-Konfiguration liegt in
-<code class="filename">/etc/pbuilder/pbuildd-config.sh</code>. Es sollte einfach
-genug f?r Leute einzurichten sein, die in <span class="command"><strong>pbuilder</strong></span>
-eingearbeitet sind. Es lief ziemlich lange und es sollte m?glich sein, es
-auch auf Ihrem System einzurichten. Diese Version des Kodes ist nicht die am
-meisten getestete, sollte aber als Startpunkt funktionieren.
- </p><p>
- Um Pbuildd einzurichten, gibt es einige wissenswerte Punkte.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Um das Bauen zu verhindern, muss in der Paketliste eine
-<code class="filename">./avoidlist</code>-Datei verf?gbar sein. </p></li><li class="listitem"><p>Es wird versuchen alles zu erstellen, sogar Pakete, die nicht f?r Ihre
-Architektur gedacht sind.</p></li><li class="listitem"><p>Da Sie zuf?llige Build-Skripte ausf?hren, ist es besser, die Fakeroot-Option
-von <span class="command"><strong>pbuilder</strong></span> zu benutzen, um zu verhindern, dass das
-Bauen mit Root-Rechten ausgef?hrt wird.</p></li><li class="listitem"><p>Da nicht alle Builds garantiert in einer endlichen Zeit beendet sind, ist es
-wahrscheinlich n?tig, eine Zeit?berschreitung festzulegen, ansonsten k?nnte
-Pbuildd bei einem schlechten Build zum Stillstand kommen.</p></li><li class="listitem"><p>
- Einige Pakete ben?tigen viel Plattenplatz. Circa zwei Gigabyte scheinen f?r
-den Augenblick ausreichend zu sein. Falls Sie etwas anderes entdecken,
-informieren Sie bitte auf Englisch den Betreuer dieser Dokumentation.
- </p></li></ul></div></div><div class="sect1" title="9. Automatische R?ckportierungsskripte"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autobackport"></a>9. Automatische R?ckportierungsskripte</h2></div></div></div><p>
- Es gibt einige Leute, die <span class="command"><strong>pbuilder</strong></span> benutzen, um eine
-Teilmenge von Paketen automatisch auf die Distribution Stable
-zur?ckzuportieren.
- </p><p>
- Informationen dar?ber, wie Leute dies tun w?ren w?nschenswert. R?ckmeldungen
-oder Informationen, wie dies getan wird oder irgendwelche Beispiele w?rden
-begr??t.
- </p></div><div class="sect1" title="10. Pbuilder f?r das automatisierte Testen von Paketen benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autotesting"></a>10. Pbuilder f?r das automatisierte Testen von Paketen benutzen</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> kann benutzt werden, um Pakete automatisch zu
-testen. Es hat die Eigenschaft, das Platzieren von Hooks zu erlauben. Diese
-Hooks k?nnen innerhalb der Chroot versuchen, Pakete zu installieren, sie
-auszuf?hren oder was auch immer sonst noch getan werden kann. Einige
-bekannte Tests und Ideen:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Automatic install-remove-install-purge-upgrade-remove-upgrade-purge
-test-suite (distributed as an example, <code class="filename">B91dpkg-i</code>), or
-just check that everything installs somewhat
-(<code class="filename">execute_installtest.sh</code>).</p></li><li class="listitem"><p>Automatisch Lintian ausf?hren (verteilt als Beispiel in
-<code class="filename">/usr/share/doc/pbuilder/examples/B90lintian</code>).</p></li><li class="listitem"><p>Automatischer Debian-Test des Pakets? Das Paket debian-test wurde aus Debian
-entfernt. Eine <span class="command"><strong>pbuilder</strong></span>-Implementierung kann als
-debian/pbuilder-test-Verzeichnis gefunden werden, implementiert durch das
-Skript B92test-pkg.</p></li></ul></div><p>
- To use B92test-pkg script, first, add it to your hook directory.
-<sup>[<a name="idp6033296" href="#ftn.idp6033296" class="footnote">4</a>]</sup>. The test files are shell scripts
-placed in <code class="filename">debian/pbuilder-test/NN_name</code> (where NN is a
-number) following run-parts standard<sup>[<a name="idp6035408" href="#ftn.idp6035408" class="footnote">5</a>]</sup>
-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.
- </p><p>
- Example scripts for use with pbuilder-test can be found in
-<code class="filename">/usr/share/doc/pbuilder/examples/pbuilder-test</code>.
- </p></div><div class="sect1" title="11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altcompiler"></a>11. Pbuilder benutzen, um Builds mit alternativen Kompilern zu testen</h2></div></div></div><p>
- Die meisten Pakete werden mit <span class="command"><strong>gcc</strong></span> oder
-<span class="command"><strong>g++</strong></span> kompiliert und benutzen die
-Standardkompilerversion. Diese war f?r Debian GNU/Linux 3.0 (i386) Gcc
-2.95. Debian 3.0 wurde jedoch mit anderen Kompilern unter Paketnamen wie
-<span class="command"><strong>gcc-3.2</strong></span> f?r die Gcc-Kompilerversion 3.2 weitergegeben. Es
-war daher m?glich, zu versuchen, Pakete mit verschiedenen Kompilerversionen
-zu kompilieren. <span class="command"><strong>pentium-builder</strong></span> 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 hei?t
-und den echten Gcc aufruft. Um <span class="command"><strong>pentium-builder</strong></span> in
-<span class="command"><strong>pbuilder</strong></span> zu benutzen, ist es m?glich das Folgende in der
-Konfiguration einzurichten: </p><pre class="screen">
-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2</pre><p>
- </p><p>
- Es wird <span class="command"><strong>pbuilder</strong></span> anweisen, das Paket
-<span class="command"><strong>pentium-builder</strong></span> und au?erdem die GCC 3.2-Kompilerpakete
-innerhalb der Chroot zu installieren und die zum Funktionieren von
-<span class="command"><strong>pentium-builder</strong></span> ben?tigten Umgebungsvariablen zu setzen.
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp4402320" href="#idp4402320" class="para">1</a>] </sup>debootstrap oder cdebootstrap k?nnen ausgew?hlt werden</p></div><div class="footnote"><p><sup>[<a id="ftn.idp4405568" href="#idp4405568" class="para">2</a>] </sup>
- Die Spiegel-Site sollte m?glichst 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.
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp69040" href="#idp69040" class="para">3</a>] </sup>Nur das Durchf?hren von Upgrades wird unterst?tzt. Debian unterst?tzt
-generell (noch?) kein Downgrade.</p></div><div class="footnote"><p><sup>[<a id="ftn.idp6033296" href="#idp6033296" class="para">4</a>] </sup>Es ist m?glich, die Befehlszeilenoption <span class="command"><strong>--hookdir
-/usr/share/doc/pbuilder/examples</strong></span> anzugeben, um ebenfalls alle
-Beispiel-Hooks einzuf?gen.</p></div><div class="footnote"><p><sup>[<a id="ftn.idp6035408" href="#idp6035408" class="para">5</a>] </sup> Siehe run-parts(8). Zum Beispiel kein ?.? in Dateinamen!
- </p></div></div></div><div class="chapter" title="Kapitel 3. User Mode Linux mit Pbuilder benutzen"><div class="titlepage"><div><div><h2 class="title"><a name="pbuilder-uml"></a>Kapitel 3. User Mode Linux mit Pbuilder benutzen</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. User Mode Linux konfigurieren</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Rootstrap konfigurieren</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Pbuilder-uml konfigurieren</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Betrachtungen, um Pbuilder-user-mode-linux auszuf?hren</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Paralleles Ausf?hren von Pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle
-Maschine zu starten</a></span></dt></dl></div><p>
- Es ist m?glich, User Mode Linux zu benutzen, indem
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> anstelle von
-<span class="command"><strong>pbuilder</strong></span> aufgerufen
-wird. <span class="command"><strong>pbuilder-user-mode-linux</strong></span> ben?tigt keine Root-Rechte
-und benutzt die Plattenzugriffsmethode Copy-on-write (COW) von
-<span class="command"><strong>User-mode-linux</strong></span>, die normalerweise wesentlich schneller
-ist als das traditionelle <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- <span class="command"><strong>User-mode-linux</strong></span> ist eine etwas weniger bew?hrte Plattform
-als die Standard-Unix-Werkzeuge, auf denen <span class="command"><strong>pbuilder</strong></span>
-beruht (<span class="command"><strong>chroot</strong></span>, <span class="command"><strong>tar</strong></span> und
-<span class="command"><strong>gzip</strong></span>), aber ausgereift genug, um
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> seit der Version 0.59 zu
-unterst?tzen. Und seitdem hat <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-eine schnelle Entwicklung durchlebt.
- </p><p>
- Die Konfiguration von <span class="command"><strong>pbuilder-user-mode-linux</strong></span> erfolgt in
-folgenden Schritten:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Konfiguration von User Mode Linux</p></li><li class="listitem"><p>Konfiguration von Rootstrap</p></li><li class="listitem"><p>Konfiguration von Pbuilder-uml</p></li></ul></div><p>
- </p><div class="sect1" title="1. User Mode Linux konfigurieren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="user-mode-linux-config"></a>1. User Mode Linux konfigurieren</h2></div></div></div><p>
- Die Einrichtung von User Mode Linux ist nicht ganz einfach. Es w?re
-wahrscheinlich n?tzlich, wenn Sie sich selbst ein wenig dar?ber informieren,
-bevor Sie versuchen <span class="command"><strong>rootstrap</strong></span> oder
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> zu benutzen. Um Einzelheiten zu
-erfahren, lesen Sie
-<code class="filename">/usr/share/doc/uml-utilities/README.Debian</code> und die
-Dokumentation von <span class="command"><strong>user-mode-linux</strong></span>. (Sie liegt in einem
-gesonderten Paket, user-mode-linux-doc.)
- </p><p>
- <span class="command"><strong>user-mode-linux</strong></span> erfordert, dass der Benutzer der Gruppe
-?uml-net? angeh?rt, um das Netzwerk zu konfigurieren, au?er wenn Sie Slirp
-benutzen.
- </p><p>
- Falls Sie Ihren eigenen Kernel kompilieren, m?chten Sie m?glicherweise
-?berpr?fen, ob Sie Unterst?tzung f?r TUN/TAP aktiviert haben und den
-SKAS-Patch betrachten.
- </p></div><div class="sect1" title="2. Rootstrap konfigurieren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="rootstrap"></a>2. Rootstrap konfigurieren</h2></div></div></div><p>
- <span class="command"><strong>rootstrap</strong></span> ist ein Wrapper um Debootstrap. Er erstellt ein
-Debian-Platten-Image zur Benutzung mit UML. Um Rootstrap zu konfigurieren,
-gibt es mehrere Anforderungen.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Das Rootstrap-Paket installieren</p></li><li class="listitem"><p>
- Nur TUN/TAP: den Benutzer zur Gruppe ?uml-net? hinzuf?gen, um
-Netzwerkzugriff zu gew?hren </p><pre class="screen">adduser dancer uml-net</pre><p>
- </p></li><li class="listitem"><p>Nur TUN/TAP: pr?fen, ob der Kernel die TUN/TAP-Schnittstelle unterst?tzt
-oder, falls n?tig, den Kernel neu komplilieren.
- </p></li><li class="listitem"><p><code class="filename">/etc/rootstrap/rootstrap.conf</code> einrichten. Falls der
-aktuelle Rechner beispielsweise 192.168.1.2 ist, scheint es zu
-funktionieren, die folgenden Eintr?ge auf etwas wie das Folgende zu
-?ndern. </p><pre class="screen">
-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</pre><p> Einige Experimente mit der
-Konfiguration und das Ausf?hren von <span class="command"><strong>rootstrap ~/test.uml</strong></span>,
-um es tats?chlich zu testen, w?ren praktisch.
- </p><p>
- Die Benutzung vom Slirp erfordert weniger Konfiguration. Die
-Standardkonfiguration bringt ein funktionierendes Beispiel mit.
- </p></li></ul></div></div><div class="sect1" title="3. Pbuilder-uml konfigurieren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlconfig"></a>3. Pbuilder-uml konfigurieren</h2></div></div></div><p>
- Das Folgende muss geschehen:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Installation des Pakets pbuilder-uml</p></li><li class="listitem"><p>
- Einrichten der Konfigurationsdatei
-<code class="filename">/etc/pbuilder/pbuilder-uml.conf</code> auf die folgende
-Weise. Sie unterscheidet sich bei Slirp. </p><pre class="screen">
-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"</pre><p>
-Au?erdem muss sie zur Rootstrap-Konfiguration passen.
- </p></li><li class="listitem"><p>
- 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.
- </p></li><li class="listitem"><p>F?hren Sie <span class="command"><strong>pbuilder-user-mode-linux <code class="option">create --distribution
-sid</code></strong></span> aus, um das Image zu erstellen.</p></li><li class="listitem"><p>Versuchen Sie <span class="command"><strong>pbuilder-user-mode-linux build</strong></span> auszuf?hren.</p></li></ul></div><p>
- </p></div><div class="sect1" title="4. Betrachtungen, um Pbuilder-user-mode-linux auszuf?hren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="consideruml"></a>4. Betrachtungen, um Pbuilder-user-mode-linux auszuf?hren</h2></div></div></div><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> emuliert
-<span class="command"><strong>pbuilder</strong></span> gr??tenteils, es gibt aber einige Unterschiede.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> unterst?tzt noch nicht alle
-Optionen von <span class="command"><strong>pbuilder</strong></span> ordentlich. Dies ist ein Problem
-und wird angesprochen, w?hrend besondere Bereiche entdeckt werden.
- </p></li><li class="listitem"><p>
- /tmp wird innerhalb von <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-unterschiedlich gehandhabt. In <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-wird <code class="filename">/tmp</code> als Tmpfs innerhalb UML eingeh?ngt, so dass
-der Zugriff auf Dateien unter <code class="filename">/tmp</code> von au?erhalb des
-User Mode Linux nicht funktioniert. Es beeinflusst Optionen wie
-<span class="command"><strong><code class="option">--configfile</code></strong></span> und wenn versucht wird,
-Pakete zu bauen, die unter <code class="filename">/tmp</code> liegen.
- </p></li></ul></div></div><div class="sect1" title="5. Paralleles Ausf?hren von Pbuilder-user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paralleluml"></a>5. Paralleles Ausf?hren von Pbuilder-user-mode-linux</h2></div></div></div><p>
- Um <span class="command"><strong>pbuilder-user-mode-linux</strong></span> parallel auf einem System
-auszuf?hren, sind ein paar Dinge zu ber?cksichtigen.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Die Methoden zum Erstellen und Aktualisieren d?rfen nicht laufen, wenn ein
-Build-Prozess l?uft oder eine COW-Datei entkr?ftet wird.</p></li><li class="listitem"><p>
- Falls Sie Slirp nicht benutzen, m?ssen parallel laufende Prozesse von User
-Mode Linux unterschiedliche IP-Adressen haben. Der reine Versuch,
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> mehrmals auszuf?hren, wird dazu
-f?hren, dass der Netzwerkzugriff fehlschl?gt. Aber etwas wie das Folgende
-wird funktionieren: </p><pre class="screen">
-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</pre><p> Wenn Slirp benutzt
-wird, besteht dieses Problem nicht.
- </p></li></ul></div></div><div class="sect1" title="6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle Maschine zu starten"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlwrap"></a>6. Pbuilder-user-mode-linux als Wrapper-Skript benutzen, um eine virtuelle
-Maschine zu starten</h2></div></div></div><p>
- Es ist m?glich, <span class="command"><strong>pbuilder-user-mode-linux</strong></span> f?r andere
-Zwecke als nur das Bauen von Debian-Paketen zu
-verwenden. <span class="command"><strong>pbuilder-user-mode-linux
-<code class="option">login</code></strong></span> wird einem Benutzer erm?glichen, eine Shell
-innerhalb des <span class="command"><strong>pbuilder</strong></span>-Basis-Images von User Mode Linux
-zu verwenden und <span class="command"><strong>pbuilder-user-mode-linux
-<code class="option">execute</code></strong></span> wird dem Benutzer erm?glichen, ein Skript
-innerhalb des Images auszuf?hren.
- </p><p>
- Sie k?nnen das Skript benutzen, um SSH zu installieren und einen neuen
-Benutzer hinzuzuf?gen, so dass SSH-Zugriffe innerhalb von User Mode Linux
-m?glich sind.
- </p><p>
- Beachten Sie, dass es nicht m?glich ist, ein Skript von
-<code class="filename">/tmp</code> zu benutzen, da
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> ein Tmpfs unter
-<code class="filename">/tmp</code> einh?ngt.
- </p><p>
- Das folgende Beispielskript k?nnte n?tzlich sein, um einen Sshd innerhalb
-von User Mode Linux zu starten.
- </p><pre class="screen">
-#!/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 dr?cken"
-read</pre></div></div><div class="chapter" title="Kapitel 4. H?ufig gestellte Fragen"><div class="titlepage"><div><div><h2 class="title"><a name="faq"></a>Kapitel 4. H?ufig gestellte Fragen </h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. Fehlschlagen des Erstellens mit Pbuilder</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Verzeichnisse, bei denen kein Bind-Mount m?glich ist</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. In Pbuilder anmelden, um die Umgebung zu ?ndern</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. BUILDRESULTUID f?r Sudo-Sitzungen setzen</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Anmerkungen zum Gerauch von $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Ein K?rzel erstellen, um <span class="command"><strong>pbuilder</strong></span> mit einer speziellen
-Distribution auszuf?hren.</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Umgebungsvariablen benutzen, um <span class="command"><strong>pbuilder</strong></span> f?r eine
-spezielle Distribution auszuf?hren.
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. Wie kann erreicht werden, dass Pbuilder ?apt-get update? ausf?hrt, bevor es
-versucht die Build-Abh?ngigkeiten zu erf?llen?</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Eine Chroot-Erinnerung erstellen</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. /var/cache/apt/archives f?r den Paket-Zwischenspeicher benutzen</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. Pbuilder auf Debian-Stable-Releases zur?ckportiert</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warnung, dass LOGNAME nicht definiert wurde</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. ?Build-Conflikt? mit wesentlichem Paket nicht m?glich</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Vermeiden der Nachricht ?ln: Ung?ltiger Link ?ber Ger?tegrenzen hinweg?</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Fakechroot benutzen</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Debconf innerhalb von Pbuilder-Sitzungen benutzen</a></span></dt><dt><span class="sect1"><a href="#nodev">20. ?nodev?-Einh?ngeoptionen behindern Pbuilder-Aktivit?t</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. Pbuilder ist langsam</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Pdebuild zum F?rdern eines Pakets benutzen</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Warum liegt in ../ eine source.changes-Datei?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. Die Modi ?amd64? und ?i386?</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Tmpfs f?r ?buildplace? benutzen</a></span></dt><dt><span class="sect1"><a href="#idp6254448">26. Svn-buildpackage zusammen mit Pbuilder benutzen</a></span></dt></dl></div><p>
- Hier sind bekannte Probleme und h?ufig gestellte Fragen dokumentiert. Dieser
-Teil war anfangs in der Datei README.Debian verf?gbar, wurde aber hierher
-verschoben.
- </p><div class="sect1" title="1. Fehlschlagen des Erstellens mit Pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuildercreatefail"></a>1. Fehlschlagen des Erstellens mit Pbuilder</h2></div></div></div><p>
- Es kommt h?ufig vor, dass <span class="command"><strong>pbuilder</strong></span> die letzte Chroot
-nicht erstellen kann. Versuchen Sie ein Upgrade von
-<span class="command"><strong>pbuilder</strong></span> und Debootstrap durchzuf?hren. Es ist derzeit
-nicht m?glich, Software zu erstellen, die die Vergangenheit
-handhabt. Zukunftsvorhersage ist eine Funktion, die sp?ter hinzugef?gt
-werden k?nnte, wenn wir uns mit der Vergangenheit arrangieren k?nnen.
- </p><p>
- Es gibt Leute, die gelegentlich Debootstrap auf stabile Versionen
-zur?ckportieren; jagen Sie sie.
- </p><p>
- Wenn in der Debootstrap-Phase Fehler auftreten, muss das Debootstrap-Skript
-repariert werden. <span class="command"><strong>pbuilder</strong></span> stellt keine M?glichkeit
-bereit, Debootstrap zu umgehen.
- </p></div><div class="sect1" title="2. Verzeichnisse, bei denen kein Bind-Mount m?glich ist"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bindmountlimits"></a>2. Verzeichnisse, bei denen kein Bind-Mount m?glich ist</h2></div></div></div><p>
- Aufgrund der Weise, wie <span class="command"><strong>pbuilder</strong></span> arbeitet, gibt es viele
-Verzeichnisse, bei denen ein Bind-Mount beim Ausf?hren von
-<span class="command"><strong>pbuilder</strong></span> nicht m?glich ist. Die Verzeichnisse umfassen
-<code class="filename">/tmp</code>, <code class="filename">/var/cache/pbuilder</code> und
-Systemverzeichnisse wie <code class="filename">/etc</code> und
-<code class="filename">/usr</code>. Es wird empfohlen, Verzeichnisse unter dem
-Home-Verzeichnis des Benutzers f?r Bind-Mounts zu verwenden.
- </p></div><div class="sect1" title="3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="shellafterfail"></a>3. In Pbuilder anmelden, um Fehlschlagen des Builds zu untersuchen</h2></div></div></div><p>
- It is possible to invoke a shell session after a build failure. Example
-hook scripts are provided as <code class="filename">C10shell</code> and
-<code class="filename">C11screen</code> scripts. C10shell script will start bash
-inside chroot, and C11screen script will start GNU screen inside the chroot.
- </p></div><div class="sect1" title="4. In Pbuilder anmelden, um die Umgebung zu ?ndern"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modifyupdate"></a>4. In Pbuilder anmelden, um die Umgebung zu ?ndern</h2></div></div></div><p>
- Manchmal ist es notwendig, die Chroot-Umgebung zu
-ver?ndern. <span class="command"><strong>login</strong></span> wird den Inhalt der Chroot nach dem
-Abmelden entfernen. Es ist m?glich unter Benutzung von Hook-Skripten eine
-Shell aufzurufen. <span class="command"><strong>pbuilder update</strong></span> f?hrt ?E?-Skripte aus
-und ruft beispielsweise eine Shell auf, die als
-<code class="filename">C10shell</code> bereitgestellt wird.
- </p><pre class="screen">
-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell</pre><p>
- Au?erdem ist es m?glich, die Optionen <code class="option">--save-after-exec</code>
-und/oder <code class="option">--save-after-login</code> zu der <span class="command"><strong>pbuilder
-login</strong></span>-Sitzung hinzuzuf?gen, um das Ziel zu erreichen. Es ist
-ebenfalls m?glich, die Option <code class="option">--uml-login-nocow</code> zur Sitzung
-von <span class="command"><strong>pbuilder-user-mode-linux <code class="option">login</code></strong></span>
-hinzuzuf?gen.
- </p></div><div class="sect1" title="5. BUILDRESULTUID f?r Sudo-Sitzungen setzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="BUILDRESULTUID"></a>5. BUILDRESULTUID f?r Sudo-Sitzungen setzen</h2></div></div></div><p>
- Es ist m?glich, </p><pre class="screen">BUILDRESULTUID=$SUDO_UID</pre><p> in Pbuilderrc
-einzustellen, um BUILDRESULTUID angemessen zu setzen, wenn
-<span class="command"><strong>sudo</strong></span> benutzt wird.
- </p></div><div class="sect1" title="6. Anmerkungen zum Gerauch von $TMPDIR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpdir"></a>6. Anmerkungen zum Gerauch von $TMPDIR</h2></div></div></div><p>
- Falls Sie $TMPDIR auf einen un?blichen Wert setzen, der von
-<code class="filename">/tmp</code> abweicht, werden Sie bemerken, dass einige Fehler,
-wie das Scheitern von <span class="command"><strong>dpkg-source</strong></span>, innerhalb der Chroot
-auftreten.
- </p><p>Es gibt zwei Optionen – Sie k?nnen einen Hook installieren, um dieses
-Verzeichnis zu erstellen oder </p><pre class="screen">export TMPDIR=/tmp</pre><p> in
-Pbuilderrc setzen. Suchen Sie sich eine aus.
- </p><p>
- Ein Beispielskript wird als <code class="filename">examples/D10tmp</code> mit
-Pbuilder bereitgestellt.
- </p></div><div class="sect1" title="7. Ein K?rzel erstellen, um pbuilder mit einer speziellen Distribution auszuf?hren."><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="DISTRIBUTIONSWITCH"></a>7. Ein K?rzel erstellen, um <span class="command"><strong>pbuilder</strong></span> mit einer speziellen
-Distribution auszuf?hren.</h2></div></div></div><p>
- Wenn mit mehreren Chroots gearbeitet wird, w?re es nett, mit Skripten zu
-arbeiten, um weniger tippen zu m?ssen. Ein Beispielskript
-<code class="filename">pbuilder-distribution.sh</code> wird als Muster
-bereitgestellt. Der Aufruf des Skripts mit
-<code class="filename">pbuilder-squeeze</code> wird <span class="command"><strong>pbuilder</strong></span> mit
-einer Squeeze-Chroot aufrufen.
- </p></div><div class="sect1" title="8. Umgebungsvariablen benutzen, um pbuilder f?r eine spezielle Distribution auszuf?hren."><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ENVVARDISTRIBUTIONSWITCH"></a>8. Umgebungsvariablen benutzen, um <span class="command"><strong>pbuilder</strong></span> f?r eine
-spezielle Distribution auszuf?hren.
- </h2></div></div></div><p> Dieser Abschnitt<sup>[<a name="idp6152368" href="#ftn.idp6152368" class="footnote">6</a>]</sup> beschreibt kurz eine
-M?glichkeit, mehrere Pbuilder-Einrichtungen zu erstellen und zu benutzen,
-indem eine Pbuilderrc-Konfiguration in Ihrem Home-Pfad
-(<code class="filename">$HOME/.pbuilderrc</code>) erstellt und die Variable ?DIST?
-beim Ausf?hren von Pbuilder oder Pdebuild benutzt wird.
-</p><p> Richten Sie zuerst <code class="filename">$HOME/.pbuilderrc</code> ein, dass es wie
-folgt aussieht:</p><p>
- </p><pre class="screen">
-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
-</pre><p>Wann auch immer Sie dann Pbuilder f?r eine spezielle Distribution benutzen
-m?chten, weisen Sie ?DIST? einen Wert zu, der einer der f?r Debian
-verf?gbaren Distribution oder einer auf Debian basierenden Distribution, die
-Sie zuf?llig ausf?hren, entspricht (d.h. was auch immer unter
-/usr/lib/debootstrap/scripts gefunden wird).
- </p><p>Hier einige Beispiele, der Ausf?hrung von Pbuilder oder Pdebuild:
-</p><pre class="screen">
-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
-</pre></div><div class="sect1" title="9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="usingspecialaptsources"></a>9. Spezielle Listen von Apt-Quellen und lokale Pakete verwenden</h2></div></div></div><p>
- Falls Sie einige au?ergew?hnliche Anforderungen an Ihre Apt-Einrichtung
-innerhalb <span class="command"><strong>pbuilder</strong></span> haben, ist es m?glich, dies ?ber die
-Option <span class="command"><strong><code class="option">--othermirror</code></strong></span>
-anzugeben. Versuchen Sie etwas wie dies: <span class="command"><strong><code class="option">--othermirror "deb
-http://local/mirror stable main|deb-src http://local/source/repository
-./"</code></strong></span>
- </p><p>
- Um ein lokales Dateisystem anstelle von HTTP zu benutzen, ist es n?tig,
-Bind-Mount zu verwenden. <span class="command"><strong><code class="option">--bindmounts</code></strong></span>
-ist eine in solchen F?llen n?tzliche Befehlszeilenoption.
- </p><p>
- Es k?nnte vorteilhaft sein, Ihre Build-Pakete von innerhalb der Chroot zu
-benutzen. Es ist m?glich, die Aufgabe mit der folgenden Konfiguration zu
-automatisieren. Richten Sie zuerst Pbuilderrc ein, um ein Bind-Mount Ihres
-Verzeichnisses f?r Build-Ergebnisse auszuf?hren.
- </p><p>
- </p><pre class="screen">BINDMOUNTS="/var/cache/pbuilder/result"</pre><p>
- </p><p>
- F?gen Sie dann den folgenden Hook hinzu
- </p><p>
- </p><pre class="screen">
-# 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</pre><p>
- </p><p>
- Auf diese Weise k?nnen Sie <code class="filename">deb
-file:/var/cache/pbuilder/result</code> benutzen.
- </p><p>
-
-So f?gen Sie einen neuen Apt-Schl?ssel innerhalb der Chroot hinzu:
-
- </p><p>
- </p><pre class="screen">
-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-</pre></div><div class="sect1" title="10. Wie kann erreicht werden, dass Pbuilder ?apt-get update? ausf?hrt, bevor es versucht die Build-Abh?ngigkeiten zu erf?llen?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="apt-getupdateonbuild-depend"></a>10. Wie kann erreicht werden, dass Pbuilder ?apt-get update? ausf?hrt, bevor es
-versucht die Build-Abh?ngigkeiten zu erf?llen?</h2></div></div></div><p>
- Sie k?nnen daf?r Hook-Skripte benutzen. D-Skripte werden ausgef?hrt, bevor
-Build-Abh?ngigkeiten erf?llt werden.
- </p><p>
- <a class="ulink" href="http://lists.debian.org/debian-devel/2006/05/msg00550.html" target="_top">
-Dieser Kodeausschnitt stammt von Ondrej Sury. </a>
- </p></div><div class="sect1" title="11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bashprompt"></a>11. Unterschiedliche Eingabeaufforderungen innerhalb der Pbuilder-Anmeldung</h2></div></div></div><p>
- Um charakteristische Bash-Eingabeaufforderungen innerhalb
-<span class="command"><strong>pbuilder</strong></span> zu erleichtern, ist es m?glich, innerhalb der
-<code class="filename">pbuilderrc</code> Umgebungsvariablen wie PS1 zu setzen.
- </p><p>
- 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,<sup>[<a name="idp6179568" href="#ftn.idp6179568" class="footnote">7</a>]</sup> funktionierte die
-Einstellung PS1 in Pbuilderrc.
- </p><p>Beispiel f?r ?debian_chroot?</p><pre class="screen">
- export debian_chroot="pbuild$$"</pre><p>Beispiel f?r PS1</p><pre class="screen">
- export PS1="pbuild chroot 32165 # "</pre></div><div class="sect1" title="12. Eine Chroot-Erinnerung erstellen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chrootmemo"></a>12. Eine Chroot-Erinnerung erstellen</h2></div></div></div><p>
- Bash-Eingabeaufforderungen werden Ihnen helfen, sich daran zu erinnern, dass
-Sie sich innerhalb der Chroot befinden. Es gibt andere F?lle, in denen Sie
-m?glicherweise andere Hinweise bekommen m?chten, dass Sie innerhalb der
-Chroot sind. Probieren Sie das Hook-Skript
-<code class="filename">examples/F90chrootmemo</code> aus. Es wird eine Datei
-innerhalb der Chroot erstellen, die <code class="filename">/CHROOT</code> hei?t.
- </p></div><div class="sect1" title="13. /var/cache/apt/archives f?r den Paket-Zwischenspeicher benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="packagecachearchives"></a>13. /var/cache/apt/archives f?r den Paket-Zwischenspeicher benutzen</h2></div></div></div><p>
- Um Systemen mit geringer Bandbreite zu helfen, ist es m?glich
-<code class="filename">/var/cache/apt/archives</code> als Paket-Zwischenspeicher zu
-benutzen. Geben Sie es einfach anstelle von
-<code class="filename">/var/cache/pbuilder/aptcache</code> an.
- </p><p>
- Es ist jedoch nicht m?glich, dies derzeit mit der User-Mode-Linux-Version
-von <span class="command"><strong>pbuilder</strong></span> zu tun, da
-<code class="filename">/var/cache/apt/archives</code> normalerweise nur f?r Root
-schreibbar ist.
- </p><p>
- Es wird empfohlen, zugeh?rige Werkzeuge wie Apt-proxy zu benutzen, da das
-Zwischenspeichern von Paketen dem System au?erhalb des Einflussbereichs von
-<span class="command"><strong>pbuilder</strong></span> nutzen w?rde.
- </p></div><div class="sect1" title="14. Pbuilder auf Debian-Stable-Releases zur?ckportiert"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="stablebackport"></a>14. Pbuilder auf Debian-Stable-Releases zur?ckportiert</h2></div></div></div><p>
- Die aktuelle Stable-R?ckportierung von Pbuilder ist auf backports.org
-verf?gbar.
- </p></div><div class="sect1" title="15. Warnung, dass LOGNAME nicht definiert wurde"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="LOGNAME"></a>15. Warnung, dass LOGNAME nicht definiert wurde</h2></div></div></div><p>
- Sie bekommen m?glicherweise viele Fehlermeldungen zu Gesicht, wenn Sie
-<span class="command"><strong>pbuilder</strong></span> ausf?hren.
- </p><p>
- </p><pre class="screen">
- dpkg-genchanges: Warnung: kein UTMP-Eintrag verf?gbar und LOGNAME nicht definiert; UID des Prozesses wird benutzt (1234)</pre><p>
- </p><p>
- Es ist derzeit sicher, diese Warnmeldung zu ignorieren. Bitte geben Sie eine
-R?ckmeldung, wenn Sie ein Problem mit nicht gesetztem LOGNAME haben. LOGNAME
-zu setzen bereitet einige Probleme, wenn <span class="command"><strong>chroot</strong></span>
-aufgerufen wird. Dpkg ben?tigt beispielsweise Getpwnam, um innerhalb der
-Chroot erfolgreich zu sein, was bedeutet, dass LOGNAME und die zugeh?rige
-Benutzerinformation innerhalb der Chroot eingerichtet werden m?ssen.
- </p></div><div class="sect1" title="16. ?Build-Conflikt? mit wesentlichem Paket nicht m?glich"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nobuildconflictessential"></a>16. ?Build-Conflikt? mit wesentlichem Paket nicht m?glich</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
- </p></div><div class="sect1" title="17. Vermeiden der Nachricht ?ln: Ung?ltiger Link ?ber Ger?tegrenzen hinweg?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lninvalidcrossdevicelink"></a>17. Vermeiden der Nachricht ?ln: Ung?ltiger Link ?ber Ger?tegrenzen hinweg?</h2></div></div></div><p>
- Standardm??ig benutzt <span class="command"><strong>pbuilder</strong></span> harte Links, um den
-<span class="command"><strong>pbuilder</strong></span>-Paketzwischenspeicher zu verwalten. Es ist nicht
-m?glich, harte Links ?ber unterschiedliche Ger?te hinweg zu erstellen. Daher
-wird dieser Fehler, abh?ngig von Ihrer Einrichtung, erscheinen. Falls dies
-geschieht, setzen Sie in ihrer Pbuilderrc-Datei </p><pre class="screen">APTCACHEHARDLINK=no</pre><p>. Beachten Sie, dass Pakete in <span class="command"><strong>APTCACHE</strong></span> in den
-lokalen Chroot-Zwischenspeicher kopiert werden. Planen Sie daher genug
-Speicher auf dem Ger?t <span class="command"><strong>BUILDPLACE</strong></span> ein.
- </p></div><div class="sect1" title="18. Fakechroot benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="fakechroot"></a>18. Fakechroot benutzen</h2></div></div></div><p>
- Es ist m?glich, <span class="command"><strong>fakechroot</strong></span> zu benutzen, anstatt
-<span class="command"><strong>pbuilder</strong></span> als Root auszuf?hren; mehrere Dinge machen dies
-jedoch unpraktisch. <span class="command"><strong>fakechroot</strong></span> setzt geladene
-Bibliotheken au?er Kraft und versucht, vorgegebene Libc-Funktionen au?er
-Kraft zu setzen, wenn es die Funktionalit?t von virtuellem
-<span class="command"><strong>chroot</strong></span> bereitstellt. Einige Bibliotheken benutzen jedoch
-zum Funktionieren Libc nicht oder setzen das au?er Kraft setzen von
-<span class="command"><strong>fakechroot</strong></span> au?er Kraft. Ein Beispiel ist
-<span class="command"><strong>ldd</strong></span>. Innerhalb <span class="command"><strong>fakechroot</strong></span> wird
-<span class="command"><strong>ldd</strong></span> die Abh?ngigkeiten von Bibliotheken au?erhalb der
-Chroot pr?fen, die nicht das erwartete Verhalten aufweisen.
- </p><p>
- Um das Problem zu umgehen, hat Debootstrap eine Option <code class="option">--variant
-fakechroot</code>. Benutzen Sie diese, so dass Ldd und Ldconfig
-?berschrieben werden.
- </p><p>
- Stellen Sie sicher, dass Sie Ihrem Pfad LD_PRELOAD korrekt gesetzt haben,
-wie es in der Handbuchseite von Fakechroot beschrieben ist.
- </p></div><div class="sect1" title="19. Debconf innerhalb von Pbuilder-Sitzungen benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="debconfinsidepbuilder"></a>19. Debconf innerhalb von Pbuilder-Sitzungen benutzen</h2></div></div></div><p>
- Um Debconf innerhalb von <span class="command"><strong>pbuilder</strong></span> zu benutzen, sollte
-DEBIAN_FRONTEND in <code class="filename">pbuilderrc</code> auf
-<span class="quote">„<span class="quote">readline</span>“</span> zu setzen funktionieren. Es auf
-<span class="quote">„<span class="quote">dialog</span>“</span> zu setzen sollte ebenfalls funktionieren. Stellen Sie
-aber sicher, dass Whiptail oder Dialog innerhalb der Chroot installiert
-sind.
- </p></div><div class="sect1" title="20. ?nodev?-Einh?ngeoptionen behindern Pbuilder-Aktivit?t"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nodev"></a>20. ?nodev?-Einh?ngeoptionen behindern Pbuilder-Aktivit?t</h2></div></div></div><p>
- Falls Sie Nachrichten wie diese beim Erstellen einer Chroot sehen, sind Sie
-dabei, ein Dateisystem mit einer ?nodev?-Option einzuh?ngen.
- </p><pre class="screen">
- /var/lib/dpkg/info/base-files.postinst: /dev/null: Keine Berechtigung</pre><p>
- Sie werden au?erdem Probleme haben, falls Sie ein Dateisystem mit der Option
-?noexec? oder ?nosuid? einh?ngen. Stellen Sie sicher, dass Sie diese
-Schalter nicht gesetzt haben, wenn Sie das Dateisystem f?r
-<code class="filename">/var/cache/pbuilder</code> oder $BUILDPLACE einh?ngen.
- </p><p>
- Dies ist kein Problem, wenn Sie <span class="command"><strong>user-mode-linux</strong></span> benutzen.
- </p><p>
- Sehen Sie zum Beispiel <a class="ulink" href="http://bugs.debian.org/316135" target="_top"> 316135
-</a>.
- </p></div><div class="sect1" title="21. Pbuilder ist langsam"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="faqslowpbuilder"></a>21. Pbuilder ist langsam</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> ist ?fters langsam. Der langsamste Teil von
-<span class="command"><strong>pbuilder</strong></span> ist bei jedem Aufruf von
-<span class="command"><strong>pbuilder</strong></span> das Extrahieren des tar.gz. Dies kann verhindert
-werden, indem <span class="command"><strong>pbuilder-user-mode-linux</strong></span> benutzt
-wird. <span class="command"><strong>pbuilder-user-mode-linux</strong></span> benutzt ein
-COW-Dateisystem und muss daher das Wurzeldateisystem nicht aufr?umen und neu
-erstellen.
- </p><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> ist langsamer beim Ausf?hren des
-tats?chlichen Build-Systems, aufgrund des ?blichen Mehraufwands von
-<span class="command"><strong>user-mode-linux</strong></span> f?r Systemaufrufe. Es ist freundlicher
-zur Festplatte.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> mit Cowdancer ist ebenfalls eine Alternative,
-die die Geschwindigkeit des Pbuilder-Starts verbessert.
- </p></div><div class="sect1" title="22. Pdebuild zum F?rdern eines Pakets benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sponsor"></a>22. Pdebuild zum F?rdern eines Pakets benutzen</h2></div></div></div><p>
- Um ein Paket zu signieren, dass es f?r die F?rderung gekennzeichnet ist, ist
-es m?glich, die Optionen<span class="command"><strong><code class="option"> --auto-debsign</code></strong></span>
-und <span class="command"><strong><code class="option">--debsign-k</code></strong></span> von
-<span class="command"><strong>pdebuild</strong></span> zu benutzen.
- </p><pre class="screen">
- <span class="command"><strong>pdebuild <code class="option">--auto-debsign </code> <code class="option">--debsign-k </code><em class="parameter"><code>XXXXXXXX</code></em></strong></span></pre></div><div class="sect1" title="23. Warum liegt in ../ eine source.changes-Datei?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sourcechanges"></a>23. Warum liegt in ../ eine source.changes-Datei?</h2></div></div></div><p>
- Wenn <span class="command"><strong>pdebuild</strong></span> ausgef?hrt wird, wird
-<span class="command"><strong>pbuilder</strong></span> Dpkg-buildpackage ausf?hren, um ein
-Debian-Quellpaket zu erstellen, das an <span class="command"><strong>pbuilder</strong></span>
-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.
- </p><p>
- Dieses Verhalten ist anders, wenn es mittels
-<code class="option">--use-pdebuild-internal</code> ausgef?hrt wird.
- </p></div><div class="sect1" title="24. Die Modi ?amd64? und ?i386?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="amd64i386"></a>24. Die Modi ?amd64? und ?i386?</h2></div></div></div><p>
- AMD64-Architekturen sind f?hig, Programme im i386-Modus auszuf?hren. Es ist
-m?glich, <span class="command"><strong>pbuilder</strong></span> zu benutzen, um Pakete auszuf?hren, die
-die Optionen <span class="command"><strong>linux32</strong></span> und <span class="command"><strong>debootstrap
-<code class="option">--arch</code></strong></span> benutzen. Im Besonderen wird eine
-Befehlszeilenoption wie die Folgende funktionieren.
- </p><p>
- </p><pre class="screen">
-<span class="command"><strong>pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
- --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian</strong></span>
-<span class="command"><strong>linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz</strong></span></pre><p>
- </p></div><div class="sect1" title="25. Tmpfs f?r ?buildplace? benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpfsforpbuilder"></a>25. Tmpfs f?r ?buildplace? benutzen</h2></div></div></div><p>
- Um die Geschwindigkeit der Operation zu verbessern, ist es m?glich, Tmpfs
-f?r den Build-Ort von Pbuilder zu verwenden. H?ngen Sie das Tmpfs in
-<code class="filename">/var/cache/pbuilder/build</code> ein und setzen Sie
-</p><pre class="screen">APTCACHEHARDLINK=no</pre><p>.
- </p></div><div class="sect1" title="26. Svn-buildpackage zusammen mit Pbuilder benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp6254448"></a>26. Svn-buildpackage zusammen mit Pbuilder benutzen</h2></div></div></div><p>
- Der Befehl Pdebuild kann mit der Befehlszeilenoption ?svn-buildpackage
---svn-builder? benutzt werden. <sup>[<a name="idp6255808" href="#ftn.idp6255808" class="footnote">8</a>]</sup>
- </p><pre class="screen">
-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"</pre></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp6152368" href="#idp6152368" class="para">6</a>] </sup>Dieser Teil der Dokumentation wurde von Andres Mejia beigetragen.</p><p>
- Dieses Beispiel wurde von einem Wiki ?bernommen (<a class="ulink" href="https://wiki.ubuntu.com/PbuilderHowto" target="_top">https://wiki.ubuntu.com/PbuilderHowto</a>).
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp6179568" href="#idp6179568" class="para">7</a>] </sup>Versionen der Bash seit und vor Debian 3.0</p></div><div class="footnote"><p><sup>[<a id="ftn.idp6255808" href="#idp6255808" class="para">8</a>] </sup><a class="ulink" href="http://upsilon.cc/~zack/blog/posts/2007/09/svn-cowbuilder/" target="_top">
-Zack hat diesem Blog ein Beispiel gesandt.</a></p></div></div></div><div class="chapter" title="Kapitel 5. Fehlerbehebung und Entwicklung"><div class="titlepage"><div><div><h2 class="title"><a name="develanddebug"></a>Kapitel 5. Fehlerbehebung und Entwicklung</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#bugreport">1. Fehler berichten </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailingliste</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC-Kanal</a></span></dt><dt><span class="sect1"><a href="#development">4. Informationen f?r Pbuilder-Entwickler</a></span></dt></dl></div><div class="sect1" title="1. Fehler berichten"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreport"></a>1. Fehler berichten </h2></div></div></div><p>
- Um Fehler zu berichten, w?re es wichtig, ein Protokoll dar?ber zu haben, was
-schiefgelaufen ist. Meistens sollte das Hinzuf?gen einer Option
-<span class="command"><strong><code class="option">--debug</code></strong></span> und das erneute Ausf?hren der
-Sitzung den Zweck erf?llen. Bitte senden Sie das Protokoll einer solchen
-Sitzung zusammen mit Ihrer auf Englisch verfassten Problembeschreibung, um
-den Prozess der Fehlersuche zu erleichtern.
- </p></div><div class="sect1" title="2. Mailingliste"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mailinglist"></a>2. Mailingliste</h2></div></div></div><p>
- Es gibt auf Alioth eine Maillingliste f?r Pbuilder
-(pbuilder-maint at lists.alioth.debian.org). Sie k?nnen sie ?ber die
-Alioth-Web-Schnittstelle abonnieren. <a class="ulink" href="http://alioth.debian.org/mail/?group_id=30778" target="_top">
-http://alioth.debian.org/mail/?group_id=30778</a>.
- </p></div><div class="sect1" title="3. IRC-Kanal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="IRCchannel"></a>3. IRC-Kanal</h2></div></div></div><p>
- 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.
- </p></div><div class="sect1" title="4. Informationen f?r Pbuilder-Entwickler"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="development"></a>4. Informationen f?r Pbuilder-Entwickler</h2></div></div></div><p>
- Dieser Abschnitt versucht, aktuelle Vorgehensweisen bei der Entwicklungs zu
-dokumentieren und wie Dinge allgemein in der Entwicklung funktionieren.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> wird mitbetreut mit Ressourcen, die auf Alioth
-bereitgestellt werden. Es gibt eine Alioth-Projektseite unter <a class="ulink" href="http://alioth.debian.org/projects/pbuilder" target="_top">
-http://alioth.debian.org/projects/pbuilder</a>. Au?erdem ist die
-Homepage, die diesen Text zeigt, unter <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
-http://alioth.debian.org/projects/pbuilder</a> verf?gbar. Das Git-Depot
-ist ?ber HTTP, Git oder (falls Sie ein Alioth-Konto haben) SSH verf?gbar.
- </p><pre class="screen">
-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</pre><p>
- 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.
- </p><p>
- Test-Suites sind im Verzeichnis <code class="filename">./testsuite/</code>
-verf?gbar. Von ?nderungen wird erwartet, dass sie die Test-Suites nicht
-unterbrechen. <code class="filename">./run-test.sh</code> ist eine Basistest-Suite,
-die eine Zusammenfassung in <code class="filename">run-test.log</code> und
-<code class="filename">run-test-cdebootstrap.log</code>
-ablegt. <code class="filename">./run-test-regression.sh</code> ist eine
-Regressionstest-Suite, die das Ergebnis in
-<code class="filename">run-test-regression.log</code> ablegt. Derzeit wird
-run-test.sh t?glich automatisch ausgef?hrt, um sicherzustellen, dass
-Pbuilder funktioniert.
- </p><div class="table"><a name="dirtestsuites"></a><p class="title"><b>Tabelle 5.1. Verzeichnisstruktur der Test-Suite</b></p><div class="table-contents"><table summary="Verzeichnisstruktur der Test-Suite" border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Verzeichnis</th><th align="left">Bedeutung</th></tr></thead><tbody><tr><td align="left"><code class="filename">./testsuite/</code></td><td align="left">Verzeichnis f?r Test-Suite</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.sh</code></td><td align="left">T?glicher Regressionstest, um zu pr?fen, ob ?nderungen am Debian-Archiv
-Pbuilder unterbrechen.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.log</code></td><td align="left">Eine Zusammenfassung der Test-Suite</td></tr><tr><td align="left"><code class="filename">./testsuite/normal/</code></td><td align="left">Verzeichnis f?r Test-Suite-Ergebnisse f?r die Ausf?hrung von Pbuilder mit
-Debootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/cdebootstrap/</code></td><td align="left">Verzeichnis f?r Test-Suite-Ergebnisse f?r die Ausf?hrung von Pbuilder mit
-Cdebootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.sh</code></td><td align="left">Regressionstest-Suite, wurde jedesmal ausgef?hrt, wenn etwas an Pbuilder
-ge?ndert wurde, um sicherzustellen, dass es keinen R?ckschritt gibt.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.log</code></td><td align="left">Zusammenfassung des Testergebnisses</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*.sh</code></td><td align="left">Regressionstests, R?ckgabewert 0 bei Erfolg, 1 bei Fehlschlag</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*</code></td><td align="left">Dateien, die f?r die Regressionstest-Suite verwandt werden</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/log/BugID-*.sh.log</code></td><td align="left">Ausgabe des Regressionstests, Ausgabe des Skripts, an das durch
-run-regression.sh weitergeleitet wurde</td></tr></tbody></table></div></div><br class="table-break"><p>
- 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
-aussagekr?ftige erste Zeile in Ihr Commit-Protokoll und f?gen Sie jede
-verf?gbare Information zum Schlie?en von Fehlern hinzu. debian/changelog
-sollte nicht direkt bearbeitet werden, au?er wenn eine neue Version
-ver?ffentlicht wird.
- </p><p>
- Eine TODO-Datei ist in <code class="filename">debian/TODO</code> verf?gbar. 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.
- </p><p>
- Wenn eine neue Version von <span class="command"><strong>pbuilder</strong></span> ver?ffentlicht wird,
-ist die Version mit der Git-Markierung X.XXX (Versionsnummer)
-gekennzeichnet. Dies wurde mit dem Skript <span class="command"><strong>./git-tag.sh</strong></span>,
-das im Quellkode-Verzeichnisbaum verf?gbar ist, erledigt.
- </p></div></div><div class="chapter" title="Kapitel 6. Andere Verwendungen von Pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="otheruse"></a>Kapitel 6. Andere Verwendungen von Pbuilder</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#chroot">1. Pbuilder f?r kleine Experimente benutzen</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Kleine Programme innerhalb der Chroot ausf?hren</a></span></dt></dl></div><div class="sect1" title="1. Pbuilder f?r kleine Experimente benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chroot"></a>1. Pbuilder f?r kleine Experimente benutzen</h2></div></div></div><p>
- Es gibt F?lle, in denen es n?tig ist, ein wenig zu experimentieren und Sie
-das Hauptsystem nicht besch?digen wollen, wie das Installieren
-experimenteller Bibliothekspakete oder das Kompilieren mit experimentellen
-Kompilern. F?r diese F?lle steht der Befehl <span class="command"><strong>pbuilder
-login</strong></span> zur Verf?gung.
- </p><p>
- <span class="command"><strong>pbuilder login </strong></span> ist eine Funktion zur Fehlersuche f?r
-<span class="command"><strong>pbuilder</strong></span> selbst, aber es erm?glicht Benutzern au?erdem
-eine tempor?re Chroot zu verwenden.
- </p><p>
- Beachten Sie, dass die Chroot nach dem Abmelden aus der Shell bereinigt wird
-und das Einh?ngen von Dateisystemen innerhalb der Chroot als sch?dlich
-angesehen wird.
- </p></div><div class="sect1" title="2. Kleine Programme innerhalb der Chroot ausf?hren"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="runningprograms"></a>2. Kleine Programme innerhalb der Chroot ausf?hren</h2></div></div></div><p>
- Um die Benutzung von <span class="command"><strong>pbuilder</strong></span> f?r andere Zwecke zu
-erleichtern, ist <span class="command"><strong>pbuilder execute</strong></span>
-verf?gbar. <span class="command"><strong>pbuilder execute </strong></span> wird ein im
-Befehlszeilenargument angegebenes Skript nehmen und innerhalb der Chroot
-aufrufen.
- </p><p>
- Das Skript kann n?tzlich f?r Abfolgen von Operationen, wie das Installieren
-von SSH oder das Hinzuf?gen eines neuen Benutzers innerhalb der Chroot,
-sein.
- </p></div></div><div class="chapter" title="Kapitel 7. Experimental or wishlist features of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="experimental"></a>Kapitel 7. Experimental or wishlist features of pbuilder</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#lvm">1. LVM benutzen</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Cowdancer benutzen</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Pbuilder ohne tar.gz verwenden</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. PBuilder in einem Vserver verwenden</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Gebrauch von Ccache</a></span></dt></dl></div><p>
- Es gibt einige fortgeschrittene Funktionen, die ?ber die Grundfunktionen von
-<span class="command"><strong>pbuilder</strong></span> f?r einige besondere Zwecke hinausgehen.
- </p><div class="sect1" title="1. LVM benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lvm"></a>1. LVM benutzen</h2></div></div></div><p>
- LVM2 has a useful snapshot function that features Copy-on-write images.
-That could be used for <span class="command"><strong>pbuilder</strong></span> just as it can be used
-for the user-mode-linux <span class="command"><strong>pbuilder</strong></span> port. lvmpbuilder
-script in the examples directory implements such port. The scripts and
-documentation can be found under
-<code class="filename">/usr/share/doc/pbuilder/examples/lvmpbuilder/</code>.
- </p></div><div class="sect1" title="2. Cowdancer benutzen"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cowdancer"></a>2. Cowdancer benutzen</h2></div></div></div><p>
- <span class="command"><strong>cowdancer</strong></span> erlaubt Copy-on-write-Semantiken auf dem
-Dateisystem unter Benutzung von harten Links und
-Hard-link-breaking-on-write-Tricks. <span class="command"><strong>pbuilder</strong></span> scheint bei
-der Benutzung von <span class="command"><strong>cowdancer</strong></span> viel schneller zu sein und es
-ist ein idealer Punkt f?r Verbesserungen. <span class="command"><strong>cowbuilder</strong></span>, ein
-Wrapper f?r <span class="command"><strong>pbuilder</strong></span>, um <span class="command"><strong>cowdancer</strong></span> zu
-benutzen, ist im Paket <span class="command"><strong>cowdancer</strong></span> seit Version 0.14
-verf?gbar.
- </p><p>
- Beispielshafte Befehlszeilen f?r Cowbuilder sehen aus wie folgt.
- </p><p>
- </p><pre class="screen">
-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc</pre><p>
- </p><p>
- Es ist au?erdem m?glich, Cowdancer mit dem Befehl ?pdebuild? zu
-benutzen. Geben Sie es mit der Befehlszeilenoptionen
-<code class="option">--pbuilder</code> an oder setzen Sie es in der
-Konfigurationsoption PDEBUILD_PBUILDER.
- </p><p>
- </p><pre class="screen">
-$ pdebuild --pbuilder cowbuilder</pre><p>
- </p></div><div class="sect1" title="3. Pbuilder ohne tar.gz verwenden"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="withouttargz"></a>3. Pbuilder ohne tar.gz verwenden</h2></div></div></div><p>
- Die Option <span class="command"><strong><code class="option">--no-targz</code></strong></span> von
-<span class="command"><strong>pbuilder</strong></span> wird den Gebrauch von
-<span class="command"><strong>pbuilder</strong></span> auf eine andere als die ?bliche Weise
-erm?glichen. Sie wird versuchen eine existierende Chroot zu benutzen und sie
-nach der Arbeit damit nicht zu bereinigen. Es ist ein Betriebsmodus, der
-eher <span class="command"><strong>sbuild</strong></span> gleicht.
- </p><p>
- Es sollte m?glich sein, Basis-Chroot-Images f?r <span class="command"><strong>dchroot</strong></span>
-mit den folgenden Befehlen zu erstellen: </p><pre class="screen">
-# 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</pre><p>
- </p></div><div class="sect1" title="4. PBuilder in einem Vserver verwenden"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="inavserver"></a>4. PBuilder in einem Vserver verwenden</h2></div></div></div><p>
- Es ist m?glich, <span class="command"><strong>pbuilder</strong></span> in einer Vserver-Umgebung zu
-verwenden. Dies erfordert entweder Vserver-patches in Version 2.1.1-rc14
-oder h?her oder eine Linux-Kernel-Version 2.6.16 oder h?her.
- </p><p>
- Um <span class="command"><strong>pbuilder</strong></span> in einem Vserver zu verwenden, m?ssen Sie in
-den <span class="command"><strong>ccapabilities</strong></span> dieses Servers
-<span class="command"><strong>secure_mount</strong></span> <span class="command"><strong>CAPS</strong></span> setzen.
- </p></div><div class="sect1" title="5. Gebrauch von Ccache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ccache"></a>5. Gebrauch von Ccache</h2></div></div></div><p>
- It is possible to use C compiler cache <span class="command"><strong>ccache</strong></span> to speed up
-repeated builds of the same package (or packages that compile the same files
-multiple times for some reason). Using <span class="command"><strong>ccache</strong></span> can speed
-up repeated building of large packages dramatically, at the cost of some
-disk space and bookkeeping.
- </p><p>
- To enable usage of <span class="command"><strong>ccache</strong></span> with
-<span class="command"><strong>pbuilder</strong></span>, you should set CCACHEDIR in your pbuilderrc
-file.
- </p><p>
- 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.
- </p></div></div><div class="chapter" title="Kapitel 8. Referenzmaterial"><div class="titlepage"><div><div><h2 class="title"><a name="refs"></a>Kapitel 8. Referenzmaterial</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Verzeichnisstruktur au?erhalb der Chroot</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Verzeichnisstruktur innerhalb der Chroot</a></span></dt></dl></div><div class="sect1" title="1. Verzeichnisstruktur au?erhalb der Chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructoutside"></a>1. Verzeichnisstruktur au?erhalb der Chroot</h2></div></div></div><div class="table"><a name="idp6349808"></a><p class="title"><b>Tabelle 8.1. Verzeichnisstruktur au?erhalb der Chroot </b></p><div class="table-contents"><table summary="Verzeichnisstruktur au?erhalb der Chroot " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Verzeichnis</th><th align="left">Bedeutung</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/pbuilderrc</code></td><td align="left">Konfigurationsdatei</td></tr><tr><td align="left"><code class="filename">/usr/share/pbuilder/pbuilderrc</code></td><td align="left">Standardkonfiguration</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/base.tgz</code></td><td align="left">Standardspeicherort, den Pbuilder f?r base.tgz benutzt. Dieser Tarball
-enth?lt eine Basis-Debian-Installation ausschlie?lich mit
-Build-essential-Paketen.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/build/PID/</code></td><td align="left">Standardspeicherort, den Pbuilder f?r Chroot benutzt</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/aptcache</code></td><td align="left">Standardspeicherort, den <span class="command"><strong>pbuilder</strong></span> als
-APT-Zwischenspeicher benutzen wird, um Deb-Pakete zu speichern, die
-<span class="command"><strong>pbuilder</strong></span> w?hrend des Bauens ben?tigt</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">Standardspeicherort, den <span class="command"><strong>pbuilder</strong></span> als Zwischenspeicher
-benutzen wird</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/result</code></td><td align="left">Standardspeicherort, in den <span class="command"><strong>pbuilder</strong></span> die Deb-Dateien und
-andere Dateien ablegt, die nach dem Build erzeugt werden</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-umlresult</code></td><td align="left">Standardspeicherort, in den <span class="command"><strong>pbuilder-user-mode-linux</strong></span> die
-Deb-Dateien und andere Dateien ablegt, die nach dem Build erzeugt werden </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-mnt</code></td><td align="left">Standardspeicherort, den <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-benutzt, um das COW-Dateisystem f?r die Chroot einzuh?ngen</td></tr><tr><td align="left"><code class="filename">/tmp</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> wird Tmpfs f?r die Arbeit
-einh?ngen.</td></tr><tr><td align="left"><code class="filename">${HOME}/tmp/PID.cow</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> benutzt dieses Verzeichnis als
-Speicherort des COW-Dateisystem.</td></tr><tr><td align="left"><code class="filename">${HOME}/uml-image</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> benutzt dieses Verzeichnis f?r
-das vollst?ndige User-Mode-Linux-Image.</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" title="2. Verzeichnisstruktur innerhalb der Chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructinside"></a>2. Verzeichnisstruktur innerhalb der Chroot</h2></div></div></div><div class="table"><a name="idp6381456"></a><p class="title"><b>Tabelle 8.2. Verzeichnisstruktur innerhalb der Chroot </b></p><div class="table-contents"><table summary="Verzeichnisstruktur innerhalb der Chroot " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Verzeichnis</th><th align="left">Bedeutung</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/mtab</code></td><td align="left">
- symbolischer Link zu <code class="filename">/proc/mounts</code>
- </td></tr><tr><td align="left"><code class="filename">/tmp/buildd</code></td><td align="left">Standardort, der vom <span class="command"><strong>pbuilder</strong></span> benutzt wird, um die zu
-verarbeitenden Debian-Pakete
-abzulegen. <code class="filename">/tmp/buildd/packagename-version/</code> wird das
-Wurzelverzeichnis des Pakets sein, das verarbeitet wird. Die
-Umgebungsvariable HOME wird von Pbuilder-buildpackage auf diesen Wert
-gesetzt. <code class="option">--inputfile</code> wird die Dateien hier ablegen.
- </td></tr><tr><td align="left"><code class="filename">/runscript</code></td><td align="left">Das Skript, das als Argument zur Ausf?hrung an <span class="command"><strong>pbuilder</strong></span>
-?bergeben wird, wird weitergereicht.
- </td></tr><tr><td align="left"><code class="filename">/tmp/hooks</code></td><td align="left">
- Der Speicherort von Hooks
- </td></tr><tr><td align="left"><code class="filename">/var/cache/apt/archives</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> kopiert den Inhalt dieses Verzeichnisses zu und
-vom Aptcache-Verzeichnis au?erhalb der Chroot.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> h?ngt dieses Verzeichnis per Bind-Mount ein,
-damit es durch Ccache benutzt wird.
- </td></tr><tr><td align="left"><code class="filename">/tmp/XXXX</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> benutzt ein Skript in
-<code class="filename">/tmp</code> f?r ein Bootstrap in User Mode Linux.</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="chapter" title="Kapitel 9. Nebens?chliche arch?ologische Einzelheiten"><div class="titlepage"><div><div><h2 class="title"><a name="idp6404320"></a>Kapitel 9. Nebens?chliche arch?ologische Einzelheiten</h2></div></div></div><div class="toc"><p><b>Inhaltsverzeichnis</b></p><dl><dt><span class="sect1"><a href="#idp6405072">1. Dokumentations-Chronik </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. M?glicherweise ungenaue Hintergrundgeschichte von Pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp6415312">2.1. Zeit vor Pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Geburt von Pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. Und sein zweites Lebensjahr</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Das f?nfte Jahr von Pbuilder</a></span></dt></dl></dd></dl></div><div class="sect1" title="1. Dokumentations-Chronik"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp6405072"></a>1. Dokumentations-Chronik </h2></div></div></div><p>
- Die Arbeit an diesem Dokument wurde am 28. Dezember 2002 durch Junichi
-Uekawa begonnen, der versuchte zu dokumentieren, was ?ber
-<span class="command"><strong>pbuilder</strong></span> bekannt ist.
- </p><p>
- Diese Dokumentation ist im Quell-Tarball und im Git-Depot (Web-basierter
-Zugriff ist m?glich) von <span class="command"><strong>pbuilder</strong></span> verf?gbar. Eine Kopie
-dieser Dokumentation k?nnen Sie auf der <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.html" target="_top">Alioth-Projektseite
-f?r Pbuilder</a> finden. <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.pdf" target="_top"> Dort gibt es auch
-eine PDF-Version </a>. Die Homepage f?r <span class="command"><strong>pbuilder</strong></span> wird
-<a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
-http://pbuilder.alioth.debian.org/ </a> vom Alioth-Projekt gehostet.
- </p><p>
- Die Dokumentation wurde unter Verwendung von DocBook-XML mit dem
-Emacs-PSGML-Modus und unter Verwendung von Wysidocbookxml zur
-Echtzeitvorschau geschrieben.
- </p></div><div class="sect1" title="2. M?glicherweise ungenaue Hintergrundgeschichte von Pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderbackgroundhistory"></a>2. M?glicherweise ungenaue Hintergrundgeschichte von Pbuilder</h2></div></div></div><p>
- Das Folgende ist ein m?glichst genauer Bericht, wie es zu
-<span class="command"><strong>pbuilder</strong></span> kam und andere Versuche, ein Ergebnis wie
-<span class="command"><strong>pbuilder</strong></span> zu erzielen. Dieser Teil des Dokuments war
-urspr?nglich in der Datei AUTHORS, um dem Anerkennung zu zollen, was vor
-<span class="command"><strong>pbuilder</strong></span> existierte.
- </p><div class="sect2" title="2.1. Zeit vor Pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="idp6415312"></a>2.1. Zeit vor Pbuilder</h3></div></div></div><p>
- 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-Abh?ngigkeiten und es war simpel. Es konnte verbessert werden, es
-konnten nur Referenzen und keine tats?chliche Quelle gefunden werden.
- </p><p>
- Debbuild wurde wahrscheinlich von James Troup geschrieben. Genau bekannt ist
-dies nicht, da der tats?chlich Kode nicht vorliegt. Es konnten nur einige
-Referenzen im Netz und in den Maillinglist-Protokollen gefunden werden.
- </p><p>
- Sbuild ist ein Perl-Skript, um Debian-Pakete aus der Quelle zu bauen. Es
-wertet Build-Abh?ngigkeiten aus, f?hrt verschiedene andere Pr?fungen durch
-und hat viele Hacks, um Dinge tats?chlich zu bauen, einschlie?lich einer
-Tabelle, welches Paket benutzt wird, wenn virtuelle Pakete angegeben wurden
-(tut es dies immer noch?). Es unterst?tzt den Gebrauch einer lokalen
-Datenbank f?r Pakete, die keine Build-Abh?ngigkeiten 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.
- </p></div><div class="sect2" title="2.2. Geburt von Pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="birth"></a>2.2. Geburt von Pbuilder</h3></div></div></div><p>
- 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-Abh?ngigkeiten vorwegnahm.
- </p><p>
- Pakete aus den Quellen unter Benutzung von Build-Abh?ngigkeitsinformationen
-innerhalb einer Chroot zu bauen klang trivial und
-<span class="command"><strong>pbuilder</strong></span> war geboren. Es war urspr?nglich 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.
- </p><p>
- Ja, und es dauerte fast ein Jahr, um einige Dinge in Ordnung zu bringen und
-mitten in diesem Prozess wurde Debian 3.0 ver?ffentlicht. Juhu. Debian 3.0
-konnte nicht vollst?ndig mit <span class="command"><strong>pbuilder</strong></span> gebaut werden, aber
-die Anzahl der Pakete, die nicht gebaut werden k?nnen, nimmt stetig ab
-(hoffentlich).
- </p></div><div class="sect2" title="2.3. Und sein zweites Lebensjahr"><div class="titlepage"><div><div><h3 class="title"><a name="secondyear"></a>2.3. Und sein zweites Lebensjahr</h3></div></div></div><p>
- Jemand wollte, dass <span class="command"><strong>pbuilder</strong></span> nicht als Root ausgef?hrt
-wird und als User Mode Linux im Laufe der Zeit n?tzlicher wurde, wurde
-begonnen, mit <span class="command"><strong>pbuilder-user-mode-linux</strong></span> zu
-experimentieren. <span class="command"><strong>pbuilder-user-mode-linux</strong></span> blieb nicht so
-funktional wie gew?nscht und Bootstrap der
-<span class="command"><strong>user-mode-linux</strong></span>-Umgebung erwies sich als ziemlich hart
-aufgrund der Qualit?t des Kodes von User Mode Linux oder der Paketierung zu
-dieser Zeit, die auf die eine oder andere Art die Netzwerkunterst?tzung
-zerst?rte.
- </p></div><div class="sect2" title="2.4. Das f?nfte Jahr von Pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="fifthyear"></a>2.4. Das f?nfte Jahr von Pbuilder</h3></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> wird nun weitgehend als
-?Beinahe-Standardwerkzeug? zum Testen von Paketen und dem Bauen von Paketen
-in einer unber?hrten Umgebung angenommen. Es gibt andere ?hnliche Werkzeuge,
-die ?hnliche Aufgaben erledigen, aber sie verfolgen nicht das gleiche
-Ziel. Um dieser Tatsache zu gedenken, wird <span class="command"><strong>pbuilder</strong></span> nun
-von mehreren Leuten mitbetreut.
- </p><p>
- <span class="command"><strong>sbuild</strong></span> ist nun ein gut betreutes Debian-Paket innerhalb
-von Debian und mit <span class="command"><strong>pbuilder</strong></span> als solch langsamem Monster
-bevorzugen einige Leute das N?herkommen von Sbuild. Es besteht die Hoffnung,
-dass die Entwicklung, um LVM-Schnappsch?sse oder Cowdancer zu benutzen, die
-Situation etwas verbessert.
- </p></div></div></div></div></body></html>
diff -Nru pbuilder-0.215+nmu3/Documentation/pbuilder-doc.fr.html pbuilder-0.215+nmu4/Documentation/pbuilder-doc.fr.html
--- pbuilder-0.215+nmu3/Documentation/pbuilder-doc.fr.html 2013-03-02 08:38:00.000000000 +0100
+++ pbuilder-0.215+nmu4/Documentation/pbuilder-doc.fr.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,985 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Manuel de l'utilisateur de pbuilder</title><link rel="stylesheet" type="text/css" href="pbuilder-doc.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div lang="fr" class="book" title="Manuel de l'utilisateur de pbuilder"><div class="titlepage"><div><div><h1 class="title"><a name="idp25434368"></a>Manuel de l'utilisateur de pbuilder</h1></div><div><h2 class="subtitle">Mode d'emploi</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Junichi</span> <span class="surname">Uekawa</span></h3></div></div></div><div><p class="releaseinfo">documentation en construction</p></div></div><hr></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="chapter"><a href="#introduction">1. Pr?sentation de pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#aim">1. Buts de pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#usingpbuilder">2. Utilisation de pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#creatingbase">1. Cr?ation de l'image de base</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Mettre ? jour le fichier base.tgz</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Construire un paquet en utilisant le fichier base.tgz</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. pdebuild ou comment ?viter d'en taper trop</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Fichiers de configuration</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Construire des paquets sans ?tre root dans l'environnement de base</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Utiliser pbuilder pour les r?troportages</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Construction des paquets en grand nombre</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Scripts de r?troportage automatique</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Utiliser pbuilder pour tester automatiquement les paquets</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Utiliser pbuilder pour tester la construction en utilisant d'autres
-compilateurs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#pbuilder-uml">3. Utiliser User-mode-linux avec pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. Configurer user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Configurer rootstrap</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Configurer pbuilder-uml</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Consid?rations pour ex?cuter pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Ex?cution en parall?le de pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Utiliser pbuilder-user-mode-linux pour d?marrer une machine virtuelle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#faq">4. Questions fr?quentes </a></span></dt><dd><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. ?chec de <span class="command"><strong>pbuilder create</strong></span></a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Les r?pertoires ne peuvent pas ?tre rattach?s
-(<span class="foreignphrase"><em class="foreignphrase">bind-mount</em></span>)</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. Se logguer dans pbuilder pour d?terminer les probl?mes de construction</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. Se logguer dans pbuilder pour modifier l'environnement</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. Variable BUILDRESULTUID pour les sessions utilisant sudo</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Note ? propos de l'utilisation de $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Cr?er un raccourci pour lancer <span class="command"><strong>pbuilder</strong></span> pour une
-distribution sp?cifique</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Utilisation des variables d'environnement pour lancer
-<span class="command"><strong>pbuilder</strong></span> pour une distribution sp?cifique
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Utiliser des sources sp?cifiques pour apt et des paquets locaux</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. Comment configurer pbuilder pour lancer apt-get update avant de tenter de
-satisfaire les d?pendances ? la construction</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Utilise une invite diff?rente ? l'int?rieur de pbuilder</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Cr?ation d'un pense-b?te de chroot</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Utiliser /var/cache/apt/archives comme cache pour les paquets</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. R?troportage de pbuilder vers les versions stables de Debian</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Alerte: LOGNAME n'est pas d?fini.</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Construction impossible: conflit avec un paquet essentiel</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. ?viter le message "ln: Lien crois? de p?riph?rique invalide"</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Utiliser fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Utiliser debconf ? l'int?rieur d'une session pbuilder</a></span></dt><dt><span class="sect1"><a href="#nodev">20. L'option de montage nodev entrave le bon fonctionnement de pbuilder</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder est lent</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Utilisation de pdebuild pour parrainer un paquet</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Pourquoi y'a-t-il un fichier source.changes dans ../??</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 et i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Utilisation de tmpfs comme emplacement de construction</a></span></dt><dt><span class="sect1"><a href="#idp31061904">26. Utiliser svn-buildpackage avec pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#develanddebug">5. D?pistage des pannes et d?veloppement</a></span></dt><dd><dl><dt><span class="sect1"><a href="#bugreport">1. Rapports de bogues </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Liste de diffusion</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. Canal IRC</a></span></dt><dt><span class="sect1"><a href="#development">4. Informations pour les d?veloppeurs de pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#otheruse">6. Autres utilisations de pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#chroot">1. Utilisation de pbuilder pour de petites exp?rimentations</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Lancer de petits programmes dans l'environnement de base</a></span></dt></dl></dd><dt><span class="chapter"><a href="#experimental">7. Experimental or wishlist features of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#lvm">1. Utilisation de LVM</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Utilisation de cowdancer</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Utilisation de pbuilder sans tar.gz</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. Utilisation de pbuilder dans un vserver</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></dd><dt><span class="chapter"><a href="#refs">8. Documents de r?f?rence</a></span></dt><dd><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Structure des r?pertoires ? l'ext?rieur de l'environnement de base</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Structure des r?pertoires ? l'int?rieur de l'image de base</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp31209552">9. Quelques d?tails arch?ologiques mineurs</a></span></dt><dd><dl><dt><span class="sect1"><a href="#idp31210288">1. Historique de la documentation </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Histoire peut-?tre incorrecte de pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp31220576">2.1. L'avant pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Naissance de pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. Et la seconde ann?e de sa vie</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Cinq ann?es de pbuilder</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>Liste des tableaux</b></p><dl><dt>5.1. <a href="#dirtestsuites">Structure des r?pertoires de la suite de tests</a></dt><dt>8.1. <a href="#idp31155760">Structure des r?pertoires ? l'ext?rieur de l'environnement de base </a></dt><dt>8.2. <a href="#idp31186880">Structure des r?pertoires ? l'int?rieur de l'image de base </a></dt></dl></div><div class="chapter" title="Chapitre?1.?Pr?sentation de pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="introduction"></a>Chapitre?1.?Pr?sentation de pbuilder</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#aim">1. Buts de pbuilder</a></span></dt></dl></div><div class="sect1" title="1.?Buts de pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="aim"></a>1.?Buts de pbuilder</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> signifie <span class="foreignphrase"><em class="foreignphrase">Personal
-Builder</em></span> et constitue un syst?me de construction automatique
-des paquets Debian destin? ? une utilisation sur une station de
-d?veloppement personnelle. <span class="command"><strong>pbuilder</strong></span> se veut un syst?me
-simple ? mettre en place pour construire automatiquement des paquets Debian
-? l'int?rieur d'un environnement propre afin de v?rifier qu'un paquet peut
-?tre construit sur la plupart des installations de Debian. L'environnement
-propre est r?alis? ? travers une image de base ne contenant qu'un minimum de
-paquets.
- </p><p>
- La distribution Debian est constitu?e de logiciels libres accompagn?s des
-sources. Tous les codes sources dans la section "main" de Debian doivent
-?tre construits uniquement ? l'aide des d?pendances sources explicitement
-sp?cifi?es et contenues ?galement dans la section "main".
- </p><p>
- L'objectif principal de <span class="command"><strong>pbuilder</strong></span> est diff?rent de celui
-des autres syst?mes de construction automatique dans Debian dans le sens o?
-il ne s'agit pas de construire le maximum de paquets possible. Les paquets
-n?cessaires ne sont pas devin?s et quand un choix est n?cessaire, c'est le
-plus souvent le plus mauvais choix qui est s?lectionn?.
- </p><p>
- De cette fa?on, <span class="command"><strong>pbuilder</strong></span> tente de garantir que les
-paquets construits ? travers <span class="command"><strong>pbuilder</strong></span> se construiront
-certainement correctement sur la plupart des installations de Debian
-permettant ainsi d'obtenir la capacit? de construire Debian ? partir des
-sources.
- </p><p>
- La possibilit? de construire Debian ? partir des sources est d?sormais
-quasiment acquis et a vu beaucoup de progr?s. ? l'?poque de Debian 3.0, de
-nombreux probl?mes pouvaient survenir en construisant Debian depuis les
-sources. Depuis, les choses se sont grandemment am?lior?es.
- </p></div></div><div class="chapter" title="Chapitre?2.?Utilisation de pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="usingpbuilder"></a>Chapitre?2.?Utilisation de pbuilder</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#creatingbase">1. Cr?ation de l'image de base</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Mettre ? jour le fichier base.tgz</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Construire un paquet en utilisant le fichier base.tgz</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. pdebuild ou comment ?viter d'en taper trop</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Fichiers de configuration</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Construire des paquets sans ?tre root dans l'environnement de base</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Utiliser pbuilder pour les r?troportages</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Construction des paquets en grand nombre</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Scripts de r?troportage automatique</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Utiliser pbuilder pour tester automatiquement les paquets</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Utiliser pbuilder pour tester la construction en utilisant d'autres
-compilateurs</a></span></dt></dl></div><p>
- Pour ?tre op?rationnel, il existe plusieurs commandes
-simples. <span class="command"><strong>pbuilder create</strong></span>, <span class="command"><strong>pbuilder
-update</strong></span> et <span class="command"><strong>pbuilder build</strong></span> sont les commandes les
-plus couramment utilis?es. Regardons chacune de ces commandes.
- </p><div class="sect1" title="1.?Cr?ation de l'image de base"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creatingbase"></a>1.?Cr?ation de l'image de base</h2></div></div></div><p>
- <span class="command"><strong>pbuilder create</strong></span> 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 <span class="command"><strong><code class="option">--distribution</code></strong></span> command-line
-option.
- </p><p>
- <span class="command"><strong>debootstrap</strong></span> <sup>[<a name="idp29716480" href="#ftn.idp29716480" class="footnote">1</a>]</sup> is used
-to create the bare minimum Debian installation, and then build-essential
-packages are installed on top of the minimum installation using
-<span class="command"><strong>apt-get</strong></span> inside the chroot.
- </p><p>
- For fuller documentation of command-line options, see the pbuilder.8 manual
-page. Some configuration will be required for
-<code class="filename">/etc/pbuilderrc</code> for the mirror site <sup>[<a name="idp25318352" href="#ftn.idp25318352" class="footnote">2</a>]</sup> to use, and proxy configuration may be required to
-allow access through HTTP. See the pbuilderrc.5 manual page for details.
- </p></div><div class="sect1" title="2.?Mettre ? jour le fichier base.tgz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="basechroot"></a>2.?Mettre ? jour le fichier base.tgz</h2></div></div></div><p><span class="command"><strong>pbuilder update</strong></span> will update the base.tgz. It will
-extract the chroot, invoke <span class="command"><strong>apt-get update</strong></span> and
-<span class="command"><strong>apt-get dist-upgrade</strong></span> inside the chroot, and then recreate
-the base.tgz (the base tar-ball).
- </p><p>
- It is possible to switch the distribution which the base.tgz is targeted at
-at this point. Specify <span class="command"><strong><code class="option">--distribution
-<em class="parameter"><code>sid</code></em></code>
-<code class="option">--override-config</code></strong></span> to change the distribution to
-sid. <sup>[<a name="idp25325696" href="#ftn.idp25325696" class="footnote">3</a>]</sup>
- </p><p>
- Pour une documentation plus compl?te des options disponibles, r?f?rez-vous ?
-la page de manuel pbuilder.8.
- </p></div><div class="sect1" title="3.?Construire un paquet en utilisant le fichier base.tgz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="buildpackagechroot"></a>3.?Construire un paquet en utilisant le fichier base.tgz</h2></div></div></div><p>
- To build a package inside the chroot, invoke <span class="command"><strong>pbuilder build
-<code class="option">whatever.dsc</code></strong></span>. <span class="command"><strong>pbuilder</strong></span> 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
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> command-line option.
- </p><p>
- The <span class="command"><strong><code class="option">--basetgz</code></strong></span> option can be used to
-specify which base.tgz to use.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> va extraire un environnement de base du fichier
-base.tgz. (base.tgz est cr?? ? l'aide de <span class="command"><strong>pbuilder create</strong></span>
-et mis ? jour avec <span class="command"><strong>pbuilder update</strong></span>.) Le fichier
-debian/control est analys? afin de d?terminer les d?pendances ? installer
-avec <span class="command"><strong>apt-get</strong></span>.
- </p><p>
- Pour une documentation plus compl?te des options disponibles, r?f?rez-vous ?
-la page de manuel pbuilder.8.
- </p></div><div class="sect1" title="4.?pdebuild ou comment ?viter d'en taper trop"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pdebuild"></a>4.?pdebuild ou comment ?viter d'en taper trop</h2></div></div></div><p>
- <span class="command"><strong>pdebuild</strong></span> est un petit script qui permet d'effectuer les
-t?ches les plus fr?quentes. Pour construire un paquet, un d?veloppeur Debian
-peut utiliser <span class="command"><strong>debuild</strong></span> dans un r?pertoire source
-Debian. <span class="command"><strong>pdebuild</strong></span> utilise un principe similaire et permet
-de construire un paquet dans l'environnement de base et de v?rifier ainsi
-que le code source actuel se construit sans probl?me dans celui-ci.
- </p><p>
- <span class="command"><strong>pdebuild</strong></span> calls <span class="command"><strong>dpkg-source</strong></span> to build
-the source packages, and then invokes <span class="command"><strong>pbuilder</strong></span> on the
-resulting source package. However, unlike debuild, the resulting deb files
-will be found in the <span class="command"><strong><code class="option">--buildresult</code></strong></span>
-directory.
- </p><p>
- R?f?rez-vous ? la page de manuel pdebuild.1 pour plus de d?tails.
- </p><p>
- There is a slightly different mode of operation available in
-<span class="command"><strong>pdebuild</strong></span> since version 0.97. <span class="command"><strong>pdebuild</strong></span>
-usually runs <span class="command"><strong>debian/rules clean</strong></span> outside of the chroot;
-however, it is possible to change the behavior to run it inside the chroot
-with the <span class="command"><strong><code class="option">--use-pdebuild-internal</code></strong></span>. It
-will try to bind mount the working directory inside chroot, and run
-<span class="command"><strong>dpkg-buildpackage</strong></span> inside. It has the following
-characteristics, and is not yet the default mode of operation.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- Les d?pendances de construction sont satisfaites ? l'int?rieur de
-l'environnement de base avant de cr?er le paquet source. Bien que ce soit un
-bon comportement, <span class="command"><strong>pdebuild</strong></span> ne l'effectue pas par d?faut.
- </p></li><li class="listitem"><p>Le r?pertoire de travail est modifi? depuis l'environnement de base.</p></li><li class="listitem"><p>Construire en utilisant <span class="command"><strong>pdebuild</strong></span> ne garantit pas que cela
-fonctionnera ?galement avec <span class="command"><strong>pbuilder</strong></span>.</p></li><li class="listitem"><p>Si la construction du paquet source ne r?ussit pas, la session utilisant
-l'environnement de base est g?ch?e (la cr?ation de cet environnement prend
-un peu de temps, ce qui peut ?tre am?lior? en utilisant cowdancer).</p></li><li class="listitem"><p>Does not work in the same manner as it used to; for example,
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> does not have any effect.</p></li><li class="listitem"><p>La construction dans l'environnement de base utilise le m?me utilisateur
-qu'en dehors de celui-ci.
- </p></li></ul></div></div><div class="sect1" title="5.?Fichiers de configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configfile"></a>5.?Fichiers de configuration</h2></div></div></div><p>
- Il est possible de sp?cifier tous les param?tres 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.
- </p><p>
- <code class="filename">/etc/pbuilderrc</code> et
-<code class="filename">${HOME}/.pbuilderrc</code> sont lus lors de l'utilisation de
-<span class="command"><strong>pbuilder</strong></span>. Les options possibles sont document?es dans la
-page de manuel pbuilderrc.5.
- </p><p>
- It is useful to use <code class="option">--configfile</code> option to load up a preset
-configuration file when switching between configuration files for different
-distributions.
- </p><p>
- Please note <code class="filename">${HOME}/.pbuilderrc</code> 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.
- </p></div><div class="sect1" title="6.?Construire des paquets sans ?tre root dans l'environnement de base"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonrootchroot"></a>6.?Construire des paquets sans ?tre root dans l'environnement de base</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
-<span class="command"><strong>pbuilder</strong></span> can create a user which is only used inside
-<span class="command"><strong>pbuilder</strong></span> and use that user id when building, and use the
-<span class="command"><strong>fakeroot</strong></span> command when root privilege is required.
- </p><p>
- L'option de configuration BUILDUSERID doit correspondre ? la valeur d'un
-identifiant utilisateur n'existant pas encore sur le syst?me de fa?on ? ce
-qu'il soit plus difficile pour les paquets construits avec
-<span class="command"><strong>pbuilder</strong></span> d'affecter le syst?me en dehors de
-l'environnement de base. Quand l'option de configuration BUILDUSERNAME est
-aussi renseign?e, <span class="command"><strong>pbuilder</strong></span> utilisera le nom d'utilisateur
-indiqu? et fakeroot pour construire les paquets plut?t que d'?tre root dans
-l'environnement de base.
- </p><p>
- M?me en utilisant ces options, <span class="command"><strong>pbuilder</strong></span> utilisera les
-privil?ges du super-utilisateur quand ils seront r?ellement n?cessaires, par
-exemple quand il doit installer des paquets dans l'environnement de base.
- </p><p>
- Pour pouvoir utiliser <span class="command"><strong>pbuilder</strong></span> sans ?tre root, vous devez
-utiliser user-mode-linux comme expliqu? dans <a class="xref" href="#pbuilder-uml" title="Chapitre?3.?Utiliser User-mode-linux avec pbuilder">Chapitre?3, <i>Utiliser User-mode-linux avec pbuilder</i></a>
- </p></div><div class="sect1" title="7.?Utiliser pbuilder pour les r?troportages"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="backporting"></a>7.?Utiliser pbuilder pour les r?troportages</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> peut ?tre utilis? pour r?troporter des logiciels
-de la derni?re 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 ? consid?rer et, en
-raison de ceux-ci, le r?troportage automatique n'est g?n?ralement pas
-possible et une intervention manuelle est requise?:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Le paquet de la distribution ??unstable?? peut d?pendre de paquets ou de
-versions de paquets qui sont disponibles uniquement dans ??unstable??. Il
-peut donc ?tre impossible de satisfaire les d?pendances de construction dans
-??stable?? (sans travail suppl?mentaire).</p></li><li class="listitem"><p>La distribution ??stable?? peut contenir des bugs qui ont ?t? corrig?s dans
-??unstable?? et qui ont besoin d'?tre contourn?s.</p></li><li class="listitem"><p>Le paquet dans ??unstable?? peut avoir des probl?mes de construction, y
-compris dans ??unstable??.</p></li></ul></div></div><div class="sect1" title="8.?Construction des paquets en grand nombre"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="massbuild"></a>8.?Construction des paquets en grand nombre</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> peut ?tre automatis? car le processus ne
-n?cessite pas d'interactions. Il est possible d'ex?cuter
-<span class="command"><strong>pbuilder</strong></span> sur plusieurs paquets de mani?re non
-interactive. Plusieurs scripts destin?s ? 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
-<span class="command"><strong>pbuilder</strong></span>. Plusieurs probl?mes existent avec la
-construction automatique?:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Les d?pendances ? la construction doivent s'installer sans n?cessiter
-d'interactions. Cependant, certains paquets ne peuvent pas s'installer sans
-interaction (postgresql par exemple).</p></li><li class="listitem"><p>Quand une biblioth?que est cass?e ou qu'un probl?me survient sur gcc/gcj/g++
-ou m?me bison, un tr?s grand nombre d'?checs sont signal?s (gcj-3.0 qui n'a
-pas de commande "javac", bison qui devient plus strict, etc.).
- </p></li><li class="listitem"><p>Certaines personnes sont particuli?rement hostiles vis-?-vis des rapports
-d'?checs de construction ? partir des sources.</p></li></ul></div><p>
- La plupart des bugs pr?sents initialement dans <span class="command"><strong>pbuilder</strong></span>
-ont ?t? r?solus autour de 2002 mais ces probl?mes transitionnels qui
-affectent une grande partie de l'archive Debian apparaissent de temps en
-temps. Les tests de r?gression sont alors utiles.
- </p><p>
- Un script qui ?tait utilis? par Junichi Uekawa est d?sormais inclus dans la
-distribution de <span class="command"><strong>pbuilder</strong></span> sous le nom
-<span class="command"><strong>pbuildd.sh</strong></span>. Il est disponible dans
-<code class="filename">/usr/share/doc/pbuilder/examples/pbuildd/</code> et son
-fichier de configuration est
-<code class="filename">/etc/pbuilder/pbuildd-config.sh</code>. Les personnes qui sont
-habitu?es ? <span class="command"><strong>pbuilder</strong></span> devraient facilement pouvoir
-l'utiliser. Il existe depuis un certain temps et vous devriez aussi pouvoir
-l'utiliser sur votre syst?me. Cette version n'est pas la mieux test?e mais
-devrait pouvoir servir de base.
- </p><p>
- Pour configurer pbuildd, vous devez prendre en consid?ration un certain
-nombre de points.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Un fichier <code class="filename">./avoidlist</code> doit contenir la liste des
-paquets qu'il ne faut pas construire. </p></li><li class="listitem"><p>Il essaiera de construire absolument tout, y compris les paquets qui ne sont
-pas destin?s ? votre architecture.</p></li><li class="listitem"><p>Parce que vous allez ex?cuter un certain nombre de scripts de construction,
-utilisez l'option fakeroot de <span class="command"><strong>pbuilder</strong></span> plut?t que de
-l'ex?cuter avec les privil?ges du super-utilisateur.</p></li><li class="listitem"><p>Parce qu'il n'est pas garanti que toutes les constructions se finiront en un
-temps fini, placer une limite temporelle sur l'ex?cution est sans doute
-n?cessaire. Dans le cas contraire, pbuildd peut rester ind?finiment sur un
-mauvais paquet.</p></li><li class="listitem"><p>
- Certains paquets n?cessitent 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.
- </p></li></ul></div></div><div class="sect1" title="9.?Scripts de r?troportage automatique"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autobackport"></a>9.?Scripts de r?troportage automatique</h2></div></div></div><p>
- Certaines personnes utilisent <span class="command"><strong>pbuilder</strong></span> pour r?troporter
-automatiquement un sous-ensemble de paquets vers la distribution stable.
- </p><p>
- Je souhaiterais obtenir quelques informations sur la fa?on de faire. Un
-retour sur le sujet ou des exemples seraient appr?ci?s.
- </p></div><div class="sect1" title="10.?Utiliser pbuilder pour tester automatiquement les paquets"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autotesting"></a>10.?Utiliser pbuilder pour tester automatiquement les paquets</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> peut ?tre utilis? pour tester automatiquement
-les paquets. Il est possible de d?finir des crochets qui vont essayer
-d'installer le paquet dans l'image de base, les ex?cuter ou toute autre
-action. Voici quelques pistes?:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Automatic install-remove-install-purge-upgrade-remove-upgrade-purge
-test-suite (distributed as an example, <code class="filename">B91dpkg-i</code>), or
-just check that everything installs somewhat
-(<code class="filename">execute_installtest.sh</code>).</p></li><li class="listitem"><p>Lancer automatiquement lintian. Un exemple est fourni dans
-<code class="filename">/usr/share/doc/pbuilder/examples/B90lintian</code>).</p></li><li class="listitem"><p>Utiliser automatiquement debian-test sur le paquet. Le paquet debian-test a
-?t? retir? de Debian. Vous pouvez trouver dans le r?pertoire
-<code class="filename">debian/pbuilder-test</code> une impl?mentation pour
-<span class="command"><strong>pbuilder</strong></span> ? travers le script B92test-pkg.</p></li></ul></div><p>
- To use B92test-pkg script, first, add it to your hook directory.
-<sup>[<a name="idp30848288" href="#ftn.idp30848288" class="footnote">4</a>]</sup>. The test files are shell scripts
-placed in <code class="filename">debian/pbuilder-test/NN_name</code> (where NN is a
-number) following run-parts standard<sup>[<a name="idp30850288" href="#ftn.idp30850288" class="footnote">5</a>]</sup>
-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.
- </p><p>
- Example scripts for use with pbuilder-test can be found in
-<code class="filename">/usr/share/doc/pbuilder/examples/pbuilder-test</code>.
- </p></div><div class="sect1" title="11.?Utiliser pbuilder pour tester la construction en utilisant d'autres compilateurs"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altcompiler"></a>11.?Utiliser pbuilder pour tester la construction en utilisant d'autres
-compilateurs</h2></div></div></div><p>
- Most packages are compiled with <span class="command"><strong>gcc</strong></span> or
-<span class="command"><strong>g++</strong></span> 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 <span class="command"><strong>gcc-3.2</strong></span>
-for gcc compiler version 3.2. It was therefore possible to try compiling
-packages against different compiler versions.
-<span class="command"><strong>pentium-builder</strong></span> 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
-<span class="command"><strong>pentium-builder</strong></span> in <span class="command"><strong>pbuilder</strong></span>, it is
-possible to set up the following in the configuration: </p><pre class="screen">
-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2</pre><p>
- </p><p>
- Cela indique ? <span class="command"><strong>pbuilder</strong></span> d'installer le paquet
-<span class="command"><strong>pentium-builder</strong></span> ainsi que le compilateur GCC 3.2 dans
-l'image de base puis de renseigner les variables d'environnement n?cessaires
-pour faire fonctionner <span class="command"><strong>pentium-builder</strong></span>.
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp29716480" href="#idp29716480" class="para">1</a>] </sup>il est possible de choisir debootstrap ou cdebootstrap</p></div><div class="footnote"><p><sup>[<a id="ftn.idp25318352" href="#idp25318352" class="para">2</a>] </sup>
- Il est pr?f?rable d'utiliser un miroir local ou un serveur cache afin de ne
-pas surcharger les miroirs publics avec un tr?s grand nombre
-d'acc?s. L'utilisation d'outils tels que apt-proxy est conseill?e.
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp25325696" href="#idp25325696" class="para">3</a>] </sup>Seule une mise ? jour est possible?: Debian ne supporte pas (encore??) les
-retours en arri?re.</p></div><div class="footnote"><p><sup>[<a id="ftn.idp30848288" href="#idp30848288" class="para">4</a>] </sup>Il est possible d'utiliser l'option <span class="command"><strong>--hookdir
-/usr/share/doc/pbuilder/examples</strong></span> pour inclure tous les crochets
-donn?s en exemple.</p></div><div class="footnote"><p><sup>[<a id="ftn.idp30850288" href="#idp30850288" class="para">5</a>] </sup> Voyez run-parts(8). Par exemple, n'utilisez pas '.' dans les noms de
-fichiers?!
- </p></div></div></div><div class="chapter" title="Chapitre?3.?Utiliser User-mode-linux avec pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="pbuilder-uml"></a>Chapitre?3.?Utiliser User-mode-linux avec pbuilder</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. Configurer user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Configurer rootstrap</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Configurer pbuilder-uml</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Consid?rations pour ex?cuter pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Ex?cution en parall?le de pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Utiliser pbuilder-user-mode-linux pour d?marrer une machine virtuelle</a></span></dt></dl></div><p>
- Il est possible d'utiliser user-mode-linux en invoquant
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> plut?t que
-<span class="command"><strong>pbuilder</strong></span>. <span class="command"><strong>pbuilder-user-mode-linux</strong></span> ne
-n?cessite pas les privil?ges du super-utilisateur et utilise la m?thode
-<span class="foreignphrase"><em class="foreignphrase">copy-on-write (COW)</em></span> ce qui la rend plus
-rapide que le traditionnel <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- <span class="command"><strong>User-mode-linux</strong></span> est une plateforme moins ?prouv?e que les
-outils standards sur lesquels reposent <span class="command"><strong>pbuilder</strong></span>
-((<span class="command"><strong>chroot</strong></span>, <span class="command"><strong>tar</strong></span>, et
-<span class="command"><strong>gzip</strong></span>) mais suffisamment m?re car pr?sente depuis la
-version 0.59. Depuis, <span class="command"><strong>pbuilder-user-mode-linux</strong></span> a connu
-une ?volution rapide.
- </p><p>
- La configuration de <span class="command"><strong>pbuilder-user-mode-linux</strong></span> s'effectue
-en trois ?tapes?:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Configuration de user-mode-linux</p></li><li class="listitem"><p>Configuration de rootstrap</p></li><li class="listitem"><p>Configuration de pbuilder-uml</p></li></ul></div><p>
- </p><div class="sect1" title="1.?Configurer user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="user-mode-linux-config"></a>1.?Configurer user-mode-linux</h2></div></div></div><p>
- user-mode-linux peut pr?senter quelques difficult?s de configuration. Il est
-pr?f?rable de se familiariser avec avant de tenter d'utiliser
-<span class="command"><strong>rootstrap</strong></span> ou
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>. Pour plus de d?tails,
-reportez-vous au fichier
-<code class="filename">/usr/share/doc/uml-utilities/README.Debian</code> et ? la
-documentation de <span class="command"><strong>user-mode-linux</strong></span> qui se trouve dans le
-paquet user-mode-linux-doc.
- </p><p>
- <span class="command"><strong>user-mode-linux</strong></span> n?cessite que l'utilisateur appartienne
-au groupe uml-net de fa?on ? configurer le r?seau, sauf si utilisez slirp.
- </p><p>
- Si vous compilez votre propre noyau, v?rifiez que le support de TUN/TAP est
-activ?. Vous pouvez ?ventuellement appliquer le patch SKAS.
- </p></div><div class="sect1" title="2.?Configurer rootstrap"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="rootstrap"></a>2.?Configurer rootstrap</h2></div></div></div><p>
- <span class="command"><strong>rootstrap</strong></span> est un utilitaire construit autour de
-debootstrap. Il cr?e une image disque de Debian destin?e ? ?tre utilis?e
-avec UML. Pour configurer rootstrap, il y a plusieurs pr?requis.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Installer le paquet rootstrap.</p></li><li class="listitem"><p>
- TUN/TAP only: add the user to the uml-net group to allow access to the
-network </p><pre class="screen">adduser dancer uml-net</pre><p>
- </p></li><li class="listitem"><p>Seulement pour utiliser TUN/TAP?: v?rifier que le noyau inclut l'interface
-TUN/TAP ou recompiler le noyau si n?cessaire.
- </p></li><li class="listitem"><p>Set up <code class="filename">/etc/rootstrap/rootstrap.conf</code>. For example, if
-the current host is 192.168.1.2, changing following entries to something
-like this seems to work. </p><pre class="screen">
-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</pre><p> Some
-experimentation with configuration and running <span class="command"><strong>rootstrap
-~/test.uml</strong></span> to actually test it would be handy.
- </p><p>
- Utiliser slirp n?cessite moins de configuration. La configuration par d?faut
-est livr?e avec un exemple fonctionnel.
- </p></li></ul></div></div><div class="sect1" title="3.?Configurer pbuilder-uml"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlconfig"></a>3.?Configurer pbuilder-uml</h2></div></div></div><p>
- Suivre les ?tapes suivantes?:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Installer le paquet pbuilder-uml.</p></li><li class="listitem"><p>
- Set up the configuration file
-<code class="filename">/etc/pbuilder/pbuilder-uml.conf</code> in the following
-manner. It will be different for slirp. </p><pre class="screen">
-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"</pre><p>
-Also, it needs to match the rootstrap configuration.
- </p></li><li class="listitem"><p>
- 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.
- </p></li><li class="listitem"><p>Run <span class="command"><strong>pbuilder-user-mode-linux <code class="option">create --distribution
-sid</code></strong></span> to create the image.</p></li><li class="listitem"><p>Essayez <span class="command"><strong>pbuilder-user-mode-linux build</strong></span>.</p></li></ul></div><p>
- </p></div><div class="sect1" title="4.?Consid?rations pour ex?cuter pbuilder-user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="consideruml"></a>4.?Consid?rations pour ex?cuter pbuilder-user-mode-linux</h2></div></div></div><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> ?mule la plupart des
-fonctionnalit?s de <span class="command"><strong>pbuilder</strong></span> avec quelques diff?rences.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> ne supporte pas encore
-correctement toutes les options de <span class="command"><strong>pbuilder</strong></span>. C'est un
-probl?me qui sera r?gl? au fur et ? mesure.
- </p></li><li class="listitem"><p>
- /tmp is handled differently inside
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>. In
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>, <code class="filename">/tmp</code> is
-mounted as tmpfs inside UML, so accessing files under
-<code class="filename">/tmp</code> from outside user-mode-linux does not work. It
-affects options like <span class="command"><strong><code class="option">--configfile</code></strong></span>, and
-when trying to build packages placed under <code class="filename">/tmp</code>.
- </p></li></ul></div></div><div class="sect1" title="5.?Ex?cution en parall?le de pbuilder-user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paralleluml"></a>5.?Ex?cution en parall?le de pbuilder-user-mode-linux</h2></div></div></div><p>
- Pour ex?cuter <span class="command"><strong>pbuilder-user-mode-linux</strong></span> en parall?le sur
-un syst?me, un certain nombre de choses doivent ?tre gard?es ? l'esprit.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Les m?thodes create et update ne doivent pas ?tre ex?cut?es lorsqu'un paquet
-est en cours de construction. Dans le cas contraire, le fichier COW sera
-corrompu.</p></li><li class="listitem"><p>
- 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
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> several times will result in
-failure to access the network. But something like the following will work:
-</p><pre class="screen">
-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</pre><p> When using slirp, this problem does not
-exist.
- </p></li></ul></div></div><div class="sect1" title="6.?Utiliser pbuilder-user-mode-linux pour d?marrer une machine virtuelle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlwrap"></a>6.?Utiliser pbuilder-user-mode-linux pour d?marrer une machine virtuelle</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>pbuilder-user-mode-linux</strong></span> for other
-uses than just building Debian packages. <span class="command"><strong>pbuilder-user-mode-linux
-<code class="option">login</code></strong></span> will let a user use a shell inside the
-user-mode-linux <span class="command"><strong>pbuilder</strong></span> base image, and
-<span class="command"><strong>pbuilder-user-mode-linux <code class="option">execute</code></strong></span> will
-allow the user to execute a script inside the image.
- </p><p>
- Vous pouvez utiliser un script pour installer ssh et ajouter un nouvel
-utilisateur ce qui permettra d'acc?der ? l'int?rieur de user-mode-linux ?
-l'aide de ssh.
- </p><p>
- Il n'est pas possible d'utiliser un script depuis <code class="filename">/tmp</code>
-en raison du fait que <span class="command"><strong>pbuilder-user-mode-linux</strong></span> monte un
-tmpfs sur <code class="filename">/tmp</code>.
- </p><p>
- Le script d'exemple suivant permet de d?marrer sshd dans user-mode-linux.
- </p><pre class="screen">
-#!/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</pre></div></div><div class="chapter" title="Chapitre?4.?Questions fr?quentes"><div class="titlepage"><div><div><h2 class="title"><a name="faq"></a>Chapitre?4.?Questions fr?quentes </h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. ?chec de <span class="command"><strong>pbuilder create</strong></span></a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Les r?pertoires ne peuvent pas ?tre rattach?s
-(<span class="foreignphrase"><em class="foreignphrase">bind-mount</em></span>)</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. Se logguer dans pbuilder pour d?terminer les probl?mes de construction</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. Se logguer dans pbuilder pour modifier l'environnement</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. Variable BUILDRESULTUID pour les sessions utilisant sudo</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Note ? propos de l'utilisation de $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Cr?er un raccourci pour lancer <span class="command"><strong>pbuilder</strong></span> pour une
-distribution sp?cifique</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Utilisation des variables d'environnement pour lancer
-<span class="command"><strong>pbuilder</strong></span> pour une distribution sp?cifique
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Utiliser des sources sp?cifiques pour apt et des paquets locaux</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. Comment configurer pbuilder pour lancer apt-get update avant de tenter de
-satisfaire les d?pendances ? la construction</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Utilise une invite diff?rente ? l'int?rieur de pbuilder</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Cr?ation d'un pense-b?te de chroot</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Utiliser /var/cache/apt/archives comme cache pour les paquets</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. R?troportage de pbuilder vers les versions stables de Debian</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Alerte: LOGNAME n'est pas d?fini.</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Construction impossible: conflit avec un paquet essentiel</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. ?viter le message "ln: Lien crois? de p?riph?rique invalide"</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Utiliser fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Utiliser debconf ? l'int?rieur d'une session pbuilder</a></span></dt><dt><span class="sect1"><a href="#nodev">20. L'option de montage nodev entrave le bon fonctionnement de pbuilder</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder est lent</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Utilisation de pdebuild pour parrainer un paquet</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Pourquoi y'a-t-il un fichier source.changes dans ../??</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 et i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Utilisation de tmpfs comme emplacement de construction</a></span></dt><dt><span class="sect1"><a href="#idp31061904">26. Utiliser svn-buildpackage avec pbuilder</a></span></dt></dl></div><p>
- Les probl?mes fr?quemment recontr?s et les questions les plus courantes sont
-document?es ici. Cette portion ?tait initialement disponible dans le fichier
-README.Debian mais a ?t? d?plac?e ici.
- </p><div class="sect1" title="1.??chec de pbuilder create"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuildercreatefail"></a>1.??chec de <span class="command"><strong>pbuilder create</strong></span></h2></div></div></div><p>
- Il est fr?quent que <span class="command"><strong>pbuilder</strong></span> ne parvienne pas ? cr?er une
-image de base r?cente. Essayez de mettre ? jour <span class="command"><strong>pbuilder</strong></span>
-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 pr?visions du
-futur.
- </p><p>
- Certaines personnes r?troportent de mani?re occasionnelle debootstrap pour
-les versions stables ; trouvez-les.
- </p><p>
- Quand une erreur concerne la phase de debootstrap, c'est le script
-debootstrap qui doit ?tre corrig?. <span class="command"><strong>pbuilder</strong></span> ne permet pas
-de pallier aux probl?mes de debootstrap.
- </p></div><div class="sect1" title="2.?Les r?pertoires ne peuvent pas ?tre rattach?s (bind-mount)"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bindmountlimits"></a>2.?Les r?pertoires ne peuvent pas ?tre rattach?s
-(<span class="foreignphrase"><em class="foreignphrase">bind-mount</em></span>)</h2></div></div></div><p>
- En raison du mode de fonctionnement de <span class="command"><strong>pbuilder</strong></span>, il y a
-plusieurs r?pertoires qui ne peuvent pas ?tre rattach?s lorsque
-<span class="command"><strong>pbuilder</strong></span> tourne. Ces r?pertoires incluent
-<code class="filename">/tmp</code>, <code class="filename">/var/cache/pbuilder</code> et des
-r?pertoires syst?mes comme <code class="filename">/etc</code> et
-<code class="filename">/usr</code>. Il est recommand? de ne rattacher que des
-r?pertoires pr?sents dans le dossier de l'utilisateur.
- </p></div><div class="sect1" title="3.?Se logguer dans pbuilder pour d?terminer les probl?mes de construction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="shellafterfail"></a>3.?Se logguer dans pbuilder pour d?terminer les probl?mes de construction</h2></div></div></div><p>
- It is possible to invoke a shell session after a build failure. Example
-hook scripts are provided as <code class="filename">C10shell</code> and
-<code class="filename">C11screen</code> scripts. C10shell script will start bash
-inside chroot, and C11screen script will start GNU screen inside the chroot.
- </p></div><div class="sect1" title="4.?Se logguer dans pbuilder pour modifier l'environnement"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modifyupdate"></a>4.?Se logguer dans pbuilder pour modifier l'environnement</h2></div></div></div><p>
- Il est parfois n?cessaire de modifier l'image de
-base. <span class="command"><strong>login</strong></span> supprimera toute modification apr?s
-d?connexion. Il est possible de lancer un shell en utilisant les
-crochets. <span class="command"><strong>pbuilder update</strong></span> ex?cute les scripts commen?ant
-par 'E' et un exemple pour lancer un shell est fourni sous le nom
-<code class="filename">C10shell</code>.
- </p><pre class="screen">
-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell</pre><p>
- It is also possible to add <code class="option">--save-after-exec</code> and/or
-<code class="option">--save-after-login</code> options to the <span class="command"><strong>pbuilder
-login</strong></span> session to accomplish the goal. It is possible to add the
-<code class="option">--uml-login-nocow</code> option to
-<span class="command"><strong>pbuilder-user-mode-linux <code class="option">login</code></strong></span> session
-as well.
- </p></div><div class="sect1" title="5.?Variable BUILDRESULTUID pour les sessions utilisant sudo"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="BUILDRESULTUID"></a>5.?Variable BUILDRESULTUID pour les sessions utilisant sudo</h2></div></div></div><p>
- It is possible to set </p><pre class="screen">BUILDRESULTUID=$SUDO_UID</pre><p> in pbuilderrc to
-set the proper BUILDRESULTUID when using <span class="command"><strong>sudo</strong></span>.
- </p></div><div class="sect1" title="6.?Note ? propos de l'utilisation de $TMPDIR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpdir"></a>6.?Note ? propos de l'utilisation de $TMPDIR</h2></div></div></div><p>
- Si vous placez la variable $TMPDIR ? une valeur inhabituelle, des erreurs
-peuvent se produire dans l'environnement de base telles que des ?checs de
-<span class="command"><strong>dpkg-source</strong></span>.
- </p><p>There are two options, you may install a hook to create that directory, or
-set </p><pre class="screen">export TMPDIR=/tmp</pre><p> in pbuilderrc. Take your pick.
- </p><p>
- Un script d'exemple est fourni sous le nom
-<code class="filename">examples/D10tmp</code> avec <span class="command"><strong>pbuilder</strong></span>.
- </p></div><div class="sect1" title="7.?Cr?er un raccourci pour lancer pbuilder pour une distribution sp?cifique"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="DISTRIBUTIONSWITCH"></a>7.?Cr?er un raccourci pour lancer <span class="command"><strong>pbuilder</strong></span> pour une
-distribution sp?cifique</h2></div></div></div><p>
- When working with multiple chroots, it would be nice to work with scripts
-that reduce the amount of typing. An example script
-<code class="filename">pbuilder-distribution.sh</code> is provided as an example.
-Invoking the script as <code class="filename">pbuilder-squeeze</code> will invoke
-<span class="command"><strong>pbuilder</strong></span> with a squeeze chroot.
- </p></div><div class="sect1" title="8.?Utilisation des variables d'environnement pour lancer pbuilder pour une distribution sp?cifique"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ENVVARDISTRIBUTIONSWITCH"></a>8.?Utilisation des variables d'environnement pour lancer
-<span class="command"><strong>pbuilder</strong></span> pour une distribution sp?cifique
- </h2></div></div></div><p> This section<sup>[<a name="idp30965360" href="#ftn.idp30965360" class="footnote">6</a>]</sup> describes briefly a way to
-setup and use multiple pbuilder setups by creating a pbuilderrc
-configuration in your home path (<code class="filename">$HOME/.pbuilderrc</code>)
-and using the variable "DIST" when running pbuilder or pdebuild.
-</p><p> Tout d'abord, mettez en place un fichier
-<code class="filename">$HOME/.pbuilderrc</code> ressemblant ? ceci?:</p><p>
- </p><pre class="screen">
-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
-</pre><p>Puis, d?s que vous voulez utiliser une distribution particuli?re avec
-pbuilder, assignez la valeur de "DIST" ? une des distributions de Debian ou
-n'importe quelle distribution bas?e sur Debian (c'est ? dire ? n'importe
-quelle valeur qui se trouve dans /usr/lib/debootstrap/scripts).
- </p><p>Voici quelques exemples d'utilisation avec pbuilder ou pdebuild?:
-</p><pre class="screen">
-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
-</pre></div><div class="sect1" title="9.?Utiliser des sources sp?cifiques pour apt et des paquets locaux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="usingspecialaptsources"></a>9.?Utiliser des sources sp?cifiques pour apt et des paquets locaux</h2></div></div></div><p>
- If you have some very specialized requirements on your apt setup inside
-<span class="command"><strong>pbuilder</strong></span>, it is possible to specify that through the
-<span class="command"><strong><code class="option">--othermirror</code></strong></span> option. Try something
-like: <span class="command"><strong><code class="option">--othermirror "deb http://local/mirror stable
-main|deb-src http://local/source/repository ./"</code></strong></span>
- </p><p>
- To use the local file system instead of HTTP, it is necessary to do
-bind-mounting. <span class="command"><strong><code class="option">--bindmounts</code></strong></span> is a
-command-line option useful for such cases.
- </p><p>
- Utiliser les paquets que vous venez de construire dans l'environnement de
-base peut ?tre pratique. Il est possible d'automatiser cette t?che en
-utilisant la configuration suivante. D'abord, configurez pbuilderrc pour
-rattacher votre r?pertoire contenant le r?sultat des constructions.
- </p><p>
- </p><pre class="screen">BINDMOUNTS="/var/cache/pbuilder/result"</pre><p>
- </p><p>
- Puis utilisez le crochet suivant
- </p><p>
- </p><pre class="screen">
-# 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</pre><p>
- </p><p>
- De cette fa?on, vous pouvez utiliser <code class="filename">deb
-file:/var/cache/pbuilder/result</code>
- </p><p>
-
-To add new apt-key inside chroot:
-
- </p><p>
- </p><pre class="screen">
-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-</pre></div><div class="sect1" title="10.?Comment configurer pbuilder pour lancer apt-get update avant de tenter de satisfaire les d?pendances ? la construction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="apt-getupdateonbuild-depend"></a>10.?Comment configurer pbuilder pour lancer apt-get update avant de tenter de
-satisfaire les d?pendances ? la construction</h2></div></div></div><p>
- Vous pouvez utiliser ? cet effet des crochets. Les scripts commen?ant par D
-sont lanc?s avant de r?soudre les d?pendances ? la construction.
- </p><p>
- <a class="ulink" href="http://lists.debian.org/debian-devel/2006/05/msg00550.html" target="_top">
-This snippet comes from Ondrej Sury. </a>
- </p></div><div class="sect1" title="11.?Utilise une invite diff?rente ? l'int?rieur de pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bashprompt"></a>11.?Utilise une invite diff?rente ? l'int?rieur de pbuilder</h2></div></div></div><p>
- Pour indiquer que l'on se trouve ? l'int?rieur de
-<span class="command"><strong>pbuilder</strong></span>, il est possible de modifier l'invite en
-utilisant des variables comme PS1 dans <code class="filename">pbuilderrc</code>
- </p><p>
- 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,<sup>[<a name="idp30991216" href="#ftn.idp30991216" class="footnote">7</a>]</sup> setting PS1 in pbuilderrc worked.
- </p><p>exemple pour debian_chroot</p><pre class="screen">
- export debian_chroot="pbuild$$"</pre><p>exemple pour PS1</p><pre class="screen">
- export PS1="pbuild chroot 32165 # "</pre></div><div class="sect1" title="12.?Cr?ation d'un pense-b?te de chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chrootmemo"></a>12.?Cr?ation d'un pense-b?te de chroot</h2></div></div></div><p>
- L'invite de Bash vous aidera ? vous souvenir que vous ?tes dans un
-environnement chroot?. Dans certains cas, vous pourriez souhaiter disposer
-d'autres ?l?ments l'indiquant. Utilisez le script crochet
-<code class="filename">examples/F90chrootmemo</code>. Il cr?era un fichier nomm?
-<code class="filename">/CHROOT</code> dans l'environnement chroot?.
- </p></div><div class="sect1" title="13.?Utiliser /var/cache/apt/archives comme cache pour les paquets"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="packagecachearchives"></a>13.?Utiliser /var/cache/apt/archives comme cache pour les paquets</h2></div></div></div><p>
- Pour les syst?mes dont la bande passante est r?duite, il est possible
-d'utiliser <code class="filename">/var/cache/apt/archives</code> comme cache pour les
-paquets. Indiquez ce r?pertoire ? la place de celui par d?faut
-<code class="filename">/var/cache/pbuilder/aptcache</code>.
- </p><p>
- Il n'est cependant pas possible de faire ainsi pour le moment avec la
-version pour user-mode-linux de <span class="command"><strong>pbuilder</strong></span> car
-<code class="filename">/var/cache/apt/archives</code> n'est g?n?ralement accessible
-en ?criture que par root.
- </p><p>
- L'utilisation d'outils comme apt-proxy est recommand? car la mise en cache
-des paquets profite ?galement au reste du syst?me.
- </p></div><div class="sect1" title="14.?R?troportage de pbuilder vers les versions stables de Debian"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="stablebackport"></a>14.?R?troportage de pbuilder vers les versions stables de Debian</h2></div></div></div><p>
- Currently stable back port of pbuilder is available at backports.org.
- </p></div><div class="sect1" title="15.?Alerte: LOGNAME n'est pas d?fini."><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="LOGNAME"></a>15.?Alerte: LOGNAME n'est pas d?fini.</h2></div></div></div><p>
- Vous pourriez voir beaucoup de message d'alertes en ex?cutant
-<span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- </p><pre class="screen">
- dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)</pre><p>
- </p><p>
- Il n'est pas risqu? d'ignorer ce message. Veuillez signaler tout probl?me
-avec LOGNAME non d?fini. Param?trer LOGNAME cause quelques probl?mes lors de
-l'appel ? <span class="command"><strong>chroot</strong></span>. 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 param?tr?s dans le
-chroot.
- </p></div><div class="sect1" title="16.?Construction impossible: conflit avec un paquet essentiel"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nobuildconflictessential"></a>16.?Construction impossible: conflit avec un paquet essentiel</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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 enlev?s d'un
-syst?me Debian fonctionnel et qu'un paquet source ne devrait pas essayer de
-forcer la suppression de tels paquets pour des utilisateurs construisant le
-paquet.
- </p></div><div class="sect1" title='17.??viter le message "ln: Lien crois? de p?riph?rique invalide"'><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lninvalidcrossdevicelink"></a>17.??viter le message "ln: Lien crois? de p?riph?rique invalide"</h2></div></div></div><p>
- By default, <span class="command"><strong>pbuilder</strong></span> uses hard links to manage the
-<span class="command"><strong>pbuilder</strong></span> 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 </p><pre class="screen">APTCACHEHARDLINK=no</pre><p> in
-your pbuilderrc file. Note that packages in <span class="command"><strong>APTCACHE</strong></span> will
-be copied into chroot local cache, so plan for enough space on
-<span class="command"><strong>BUILDPLACE</strong></span> device.
- </p></div><div class="sect1" title="18.?Utiliser fakechroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="fakechroot"></a>18.?Utiliser fakechroot</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>fakechroot</strong></span> instead of being root to
-run <span class="command"><strong>pbuilder</strong></span>; however, several things make this
-impractical. <span class="command"><strong>fakechroot</strong></span> overrides library loads and
-tries to override default libc functions when providing the functionality of
-virtual <span class="command"><strong>chroot</strong></span>. However, some binaries do no use libc to
-function, or override the overriding provided by
-<span class="command"><strong>fakechroot</strong></span>. One example is <span class="command"><strong>ldd</strong></span>.
-Inside <span class="command"><strong>fakechroot</strong></span>, <span class="command"><strong>ldd</strong></span> will check the
-library dependency outside of the chroot, which is not the expected
-behavior.
- </p><p>
- To work around the problem, debootstrap has a <code class="option">--variant
-fakechroot</code> option. Use that, so that ldd and ldconfig are
-overridden.
- </p><p>
- Assurez-vous d'avoir correctement renseign? la variable LD_PRELOAD, comme
-d?crit dans la page de manuel de fakechroot.
- </p></div><div class="sect1" title="19.?Utiliser debconf ? l'int?rieur d'une session pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="debconfinsidepbuilder"></a>19.?Utiliser debconf ? l'int?rieur d'une session pbuilder</h2></div></div></div><p>
- Pour utiliser debconf ? l'int?rieur de <span class="command"><strong>pbuilder</strong></span>, placer
-la variable DEBIAN_FRONTEND ? <span class="quote">??<span class="quote">readline</span>??</span> dans
-<code class="filename">pbuilderrc</code> devrait faire l'affaire. La placer ?
-<span class="quote">??<span class="quote">dialog</span>??</span> devrait aussi marcher mais assurez-vous que whiptail
-ou dialog sont install?s dans l'environnement de base.
- </p></div><div class="sect1" title="20.?L'option de montage nodev entrave le bon fonctionnement de pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nodev"></a>20.?L'option de montage nodev entrave le bon fonctionnement de pbuilder</h2></div></div></div><p>
- 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 syst?me de
-fichiers.
- </p><pre class="screen">
- /var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied</pre><p>
- Vous aurez ?galement des probl?mes si vous montez le syst?me de fichiers
-avec l'option noexec ou nosuid. Assurez-vous qu'aucun de ces drapeaux ne
-soient utilis?s lorsque vous montez le syst?me de fichiers pour
-<code class="filename">/var/cache/pbuilder</code> ou $BUILDPLACE.
- </p><p>
- Ce probl?me n'appara?t pas en utilisant <span class="command"><strong>user-mode-linux</strong></span>.
- </p><p>
- R?f?rez-vous ? <a class="ulink" href="http://bugs.debian.org/316135" target="_top"> 316135 </a>
-pour un exemple.
- </p></div><div class="sect1" title="21.?pbuilder est lent"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="faqslowpbuilder"></a>21.?pbuilder est lent</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> est souvent lent. La partie la plus lente a lieu
-lors de l'extraction de l'image de base chaque fois que
-<span class="command"><strong>pbuilder</strong></span> est lanc?. Cela peut ?tre ?vit? en utilisant
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> qui utilise un syst?me de
-fichiers COW et qui n'a donc pas besoin de nettoyer et recr?er l'image de
-base.
- </p><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> est plus lent ? construire les
-paquets en raison du temps suppl?mentaire de traitement pour chaque appel
-syst?me. Il est plus amical avec le disque dur.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> associ? ? cowdancer est aussi une alternative
-qui am?liore la vitesse de lancement de pbuilder.
- </p></div><div class="sect1" title="22.?Utilisation de pdebuild pour parrainer un paquet"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sponsor"></a>22.?Utilisation de pdebuild pour parrainer un paquet</h2></div></div></div><p>
- To sign a package marking for sponsorship, it is possible to
-use<span class="command"><strong><code class="option"> --auto-debsign</code></strong></span> and
-<span class="command"><strong><code class="option">--debsign-k</code></strong></span> options of
-<span class="command"><strong>pdebuild</strong></span>.
- </p><pre class="screen">
- <span class="command"><strong>pdebuild <code class="option">--auto-debsign </code> <code class="option">--debsign-k </code><em class="parameter"><code>XXXXXXXX</code></em></strong></span></pre></div><div class="sect1" title="23.?Pourquoi y'a-t-il un fichier source.changes dans ../??"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sourcechanges"></a>23.?Pourquoi y'a-t-il un fichier source.changes dans ../??</h2></div></div></div><p>
- En lan?ant <span class="command"><strong>pdebuild</strong></span>, <span class="command"><strong>pbuilder</strong></span> va
-lancer dpkg-buildpackage pour cr?er le paquet source et le fournir ?
-<span class="command"><strong>pbuilder</strong></span>. 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.
- </p><p>
- This behavior is different when running through
-<code class="option">--use-pdebuild-internal</code>
- </p></div><div class="sect1" title="24.?amd64 et i386-mode"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="amd64i386"></a>24.?amd64 et i386-mode</h2></div></div></div><p>
- amd64 architectures are capable of running binaries in i386 mode. It is
-possible to use <span class="command"><strong>pbuilder</strong></span> to run packages, using
-<span class="command"><strong>linux32</strong></span> and <span class="command"><strong>debootstrap
-<code class="option">--arch</code></strong></span> option. Specifically, a command-line
-option like the following will work.
- </p><p>
- </p><pre class="screen">
-<span class="command"><strong>pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
- --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian</strong></span>
-<span class="command"><strong>linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz</strong></span></pre><p>
- </p></div><div class="sect1" title="25.?Utilisation de tmpfs comme emplacement de construction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpfsforpbuilder"></a>25.?Utilisation de tmpfs comme emplacement de construction</h2></div></div></div><p>
- To improve speed of operation, it is possible to use tmpfs for pbuilder
-build location. Mount tmpfs to
-<code class="filename">/var/cache/pbuilder/build</code>, and set </p><pre class="screen">APTCACHEHARDLINK=no</pre><p>.
- </p></div><div class="sect1" title="26.?Utiliser svn-buildpackage avec pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31061904"></a>26.?Utiliser svn-buildpackage avec pbuilder</h2></div></div></div><p>
- pdebuild command can be used with svn-buildpackage --svn-builder
-command-line option. <sup>[<a name="idp31063152" href="#ftn.idp31063152" class="footnote">8</a>]</sup>
- </p><pre class="screen">
-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"</pre></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp30965360" href="#idp30965360" class="para">6</a>] </sup>Cette partie de la documentation est une contribution de Andres Mejia</p><p>
- Cette exemple est issu d'un wiki (<a class="ulink" href="https://wiki.ubuntu.com/PbuilderHowto" target="_top">https://wiki.ubuntu.com/PbuilderHowto</a>).
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp30991216" href="#idp30991216" class="para">7</a>] </sup>Les versions de bash jusqu'? Debian 3.0 incluse</p></div><div class="footnote"><p><sup>[<a id="ftn.idp31063152" href="#idp31063152" class="para">8</a>] </sup><a class="ulink" href="http://upsilon.cc/~zack/blog/posts/2007/09/svn-cowbuilder/" target="_top">
-Zack has posted an example on his blog. </a></p></div></div></div><div class="chapter" title="Chapitre?5.?D?pistage des pannes et d?veloppement"><div class="titlepage"><div><div><h2 class="title"><a name="develanddebug"></a>Chapitre?5.?D?pistage des pannes et d?veloppement</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#bugreport">1. Rapports de bogues </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Liste de diffusion</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. Canal IRC</a></span></dt><dt><span class="sect1"><a href="#development">4. Informations pour les d?veloppeurs de pbuilder</a></span></dt></dl></div><div class="sect1" title="1.?Rapports de bogues"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreport"></a>1.?Rapports de bogues </h2></div></div></div><p>
- To report bugs, it would be important to have a log of what's going wrong.
-Most of the time, adding a <span class="command"><strong><code class="option">--debug</code></strong></span>
-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.
- </p></div><div class="sect1" title="2.?Liste de diffusion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mailinglist"></a>2.?Liste de diffusion</h2></div></div></div><p>
- Il existe une liste de diffusion pour <span class="command"><strong>pbuilder</strong></span> sur alioth
-(pbuilder-maint at lists.alioth.debian.org). Vous pouvez vous y inscrire ?
-travers l'interface web <a class="ulink" href="http://alioth.debian.org/mail/?group_id=30778" target="_top">http://alioth.debian.org/mail/?group_id=30778</a>.
- </p></div><div class="sect1" title="3.?Canal IRC"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="IRCchannel"></a>3.?Canal IRC</h2></div></div></div><p>
- 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.
- </p></div><div class="sect1" title="4.?Informations pour les d?veloppeurs de pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="development"></a>4.?Informations pour les d?veloppeurs de pbuilder</h2></div></div></div><p>
- Cette section tente de documenter les actuelles pratiques de d?veloppement
-et comment les choses marchent dans le d?veloppement.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> est co-maintenu sur Alioth. La page du projet
-sur Alioth se trouve ? l'adresse <a class="ulink" href="http://alioth.debian.org/projects/pbuilder" target="_top">
-http://alioth.debian.org/projects/pbuilder</a>. La page d'accueil est
-disponible sur <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
-http://alioth.debian.org/projects/pbuilder</a>. Le d?p?t git est
-disponible par http, git ou (si vous avez un compte sur alioth) ssh.
- </p><pre class="screen">
-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</pre><p>
- 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.
- </p><p>
- Les suites de tests sont disponibles dans le r?pertoire
-<code class="filename">./testsuite</code>. Les changements ne doivent pas casser ces
-tests. <code class="filename">./run-test.sh</code> est une suite de tests simples
-dont le r?sultat est plac? dans <code class="filename">run-test.log</code> et dans
-<code class="filename">run-test-cdebootstrap.log</code>.
-<code class="filename">./run-test-regression.sh</code> permet de tester les
-r?gressions. Les r?sultats se trouvent dans
-<code class="filename">run-test-regression.log</code>. Actuellement, run-test.sh est
-lanc? automatiquement tous les jours pour s'assurer que pbuilder est
-fonctionnel.
- </p><div class="table"><a name="dirtestsuites"></a><p class="title"><b>Tableau?5.1.?Structure des r?pertoires de la suite de tests</b></p><div class="table-contents"><table summary="Structure des r?pertoires de la suite de tests" border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">R?pertoire</th><th align="left">Signification</th></tr></thead><tbody><tr><td align="left"><code class="filename">./testsuite/</code></td><td align="left">R?pertoire de la suite de tests</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.sh</code></td><td align="left">Tests de r?gression journaliers pour d?tecter les r?gressions dues aux
-changements survenus dans l'archive Debian.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.log</code></td><td align="left">Un r?sum? de la suite de tests</td></tr><tr><td align="left"><code class="filename">./testsuite/normal/</code></td><td align="left">R?pertoire contenant les r?sultats des tests en utilisant debootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/cdebootstrap/</code></td><td align="left">R?pertoire contenant les r?sultats des tests en utilisant cdebootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.sh</code></td><td align="left">Tests de r?gression lanc?s chaque fois qu'un changement est effectu? sur
-pbuilder pour s'assurer qu'aucune r?gression n'est apparue</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.log</code></td><td align="left">R?sum? des r?sultats des tests</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*.sh</code></td><td align="left">Tests de r?gression, retourne 0 en cas de succ?s et 1 en cas d'?chec</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*</code></td><td align="left">Fichiers utilis?s pour les tests de r?gression.</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/log/BugID-*.sh.log</code></td><td align="left">Sortie des tests de r?gression obtenue par redirection de la sortie des
-scripts par run-regression.sh</td></tr></tbody></table></div></div><br class="table-break"><p>
- 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.
- </p><p>
- Une liste des choses ? faire est disponible dans
-<code class="filename">debian/TODO</code>. Elle n'est quasiment pas maintenue mais
-deviendra un peu plus ? jour lorsqu'elle sera plus utilis?e. Le mode emacs
-todoo-mode est utilis? pour ?diter ce fichier.
- </p><p>
- Lorsqu'une nouvelle version de <span class="command"><strong>pbuilder</strong></span> est publi?e, elle
-est marqu?e avec l'?tiquette X.XXX (num?ro de version). Le script
-<span class="command"><strong>./git-tag.sh</strong></span>, disponible dans l'arbre de source, effectue
-cette action.
- </p></div></div><div class="chapter" title="Chapitre?6.?Autres utilisations de pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="otheruse"></a>Chapitre?6.?Autres utilisations de pbuilder</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#chroot">1. Utilisation de pbuilder pour de petites exp?rimentations</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Lancer de petits programmes dans l'environnement de base</a></span></dt></dl></div><div class="sect1" title="1.?Utilisation de pbuilder pour de petites exp?rimentations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chroot"></a>1.?Utilisation de pbuilder pour de petites exp?rimentations</h2></div></div></div><p>
- Dans certains cas, vous voulez mener de petites exp?riences sans risquer de
-casser votre syst?me, par exemple pour installer une biblioth?que
-exp?rimentale ou pour compiler avec un compilateur exp?rimental. Dans de
-tels cas, la commande <span class="command"><strong>pbuilder login</strong></span> est disponible.
- </p><p>
- <span class="command"><strong>pbuilder login</strong></span> est une fonctionnalit? de diagnostic pour
-<span class="command"><strong>pbuilder</strong></span>, mais permet aux utilisateurs d'obtenir
-temporairement un environnement restreint.
- </p><p>
- ? noter que l'environnement est nettoy? apr?s la d?connexion du shell et que
-monter des syst?mes de fichiers dans celui-ci est d?conseill?.
- </p></div><div class="sect1" title="2.?Lancer de petits programmes dans l'environnement de base"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="runningprograms"></a>2.?Lancer de petits programmes dans l'environnement de base</h2></div></div></div><p>
- Pour faciliter l'utilisation de <span class="command"><strong>pbuilder</strong></span> pour d'autres
-usages, la commande <span class="command"><strong>pbuilder execute</strong></span> est
-disponible. Celle-ci prend en param?tre un script qui sera ex?cut? dans
-l'environnement de base.
- </p><p>
- Le script peut ?tre utilis? pour ex?cuter une suite d'op?rations comme
-l'installation de ssh et l'ajout d'un nouvel utilisateur dans
-l'environnement de base.
- </p></div></div><div class="chapter" title="Chapitre?7.?Experimental or wishlist features of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="experimental"></a>Chapitre?7.?Experimental or wishlist features of pbuilder</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#lvm">1. Utilisation de LVM</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Utilisation de cowdancer</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Utilisation de pbuilder sans tar.gz</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. Utilisation de pbuilder dans un vserver</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></div><p>
- <span class="command"><strong>pbuilder</strong></span> dispose de certaines fonctionnalit?s avanc?es
-pour certains usages sp?cifiques.
- </p><div class="sect1" title="1.?Utilisation de LVM"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lvm"></a>1.?Utilisation de LVM</h2></div></div></div><p>
- LVM2 has a useful snapshot function that features Copy-on-write images.
-That could be used for <span class="command"><strong>pbuilder</strong></span> just as it can be used
-for the user-mode-linux <span class="command"><strong>pbuilder</strong></span> port. lvmpbuilder
-script in the examples directory implements such port. The scripts and
-documentation can be found under
-<code class="filename">/usr/share/doc/pbuilder/examples/lvmpbuilder/</code>.
- </p></div><div class="sect1" title="2.?Utilisation de cowdancer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cowdancer"></a>2.?Utilisation de cowdancer</h2></div></div></div><p>
- <span class="command"><strong>cowdancer</strong></span> utilise des liens directs et des astuces
-cassant ces liens lors d'une ?criture pour mettre en place un m?canisme de
-??copy-on-write??. <span class="command"><strong>pbuilder</strong></span> utilis? via
-<span class="command"><strong>cowdancer</strong></span> semble beaucoup plus rapide et constitue un
-point d'am?lioration id?al. <span class="command"><strong>cowbuilder</strong></span> est un script
-autour de <span class="command"><strong>pbuilder</strong></span> permettant d'utiliser
-<span class="command"><strong>cowdancer</strong></span>. Celui-ci est disponible dans le paquet
-<span class="command"><strong>cowdancer</strong></span> depuis la version 0.14
- </p><p>
- Voici quelques exemples pour utiliser cowbuilder.
- </p><p>
- </p><pre class="screen">
-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc</pre><p>
- </p><p>
- It is also possible to use cowdancer with pdebuild command. Specify with
-command-line option <code class="option">--pbuilder</code> or set it in
-PDEBUILD_PBUILDER configuration option.
- </p><p>
- </p><pre class="screen">
-$ pdebuild --pbuilder cowbuilder</pre><p>
- </p></div><div class="sect1" title="3.?Utilisation de pbuilder sans tar.gz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="withouttargz"></a>3.?Utilisation de pbuilder sans tar.gz</h2></div></div></div><p>
- The <span class="command"><strong><code class="option">--no-targz</code></strong></span> option of
-<span class="command"><strong>pbuilder</strong></span> will allow usage of <span class="command"><strong>pbuilder</strong></span>
-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 <span class="command"><strong>sbuild</strong></span>.
- </p><p>
- It should be possible to create base chroot images for
-<span class="command"><strong>dchroot</strong></span> with the following commands: </p><pre class="screen">
-# 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</pre><p>
- </p></div><div class="sect1" title="4.?Utilisation de pbuilder dans un vserver"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="inavserver"></a>4.?Utilisation de pbuilder dans un vserver</h2></div></div></div><p>
- Il est possible d'utiliser <span class="command"><strong>pbuilder</strong></span> dans un vserver. Cela
-n?cessite soit le paquet vserver-patches en version 2.1.1-rc14 ou plus
-r?cent ou bien un noyau Linux 2.6.16 ou plus r?cent.
- </p><p>
- Pour utiliser la commande <span class="command"><strong>pbuilder</strong></span> dans un vserver, vous
-avez besoin de placer le <span class="command"><strong>CAPS</strong></span>
-<span class="command"><strong>secure_mount</strong></span> dans les <span class="command"><strong>ccapabilities</strong></span> de
-ce vserver.
- </p></div><div class="sect1" title="5.?Usage of ccache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ccache"></a>5.?Usage of ccache</h2></div></div></div><p>
- It is possible to use C compiler cache <span class="command"><strong>ccache</strong></span> to speed up
-repeated builds of the same package (or packages that compile the same files
-multiple times for some reason). Using <span class="command"><strong>ccache</strong></span> can speed
-up repeated building of large packages dramatically, at the cost of some
-disk space and bookkeeping.
- </p><p>
- To enable usage of <span class="command"><strong>ccache</strong></span> with
-<span class="command"><strong>pbuilder</strong></span>, you should set CCACHEDIR in your pbuilderrc
-file.
- </p><p>
- 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.
- </p></div></div><div class="chapter" title="Chapitre?8.?Documents de r?f?rence"><div class="titlepage"><div><div><h2 class="title"><a name="refs"></a>Chapitre?8.?Documents de r?f?rence</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Structure des r?pertoires ? l'ext?rieur de l'environnement de base</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Structure des r?pertoires ? l'int?rieur de l'image de base</a></span></dt></dl></div><div class="sect1" title="1.?Structure des r?pertoires ? l'ext?rieur de l'environnement de base"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructoutside"></a>1.?Structure des r?pertoires ? l'ext?rieur de l'environnement de base</h2></div></div></div><div class="table"><a name="idp31155760"></a><p class="title"><b>Tableau?8.1.?Structure des r?pertoires ? l'ext?rieur de l'environnement de base </b></p><div class="table-contents"><table summary="Structure des r?pertoires ? l'ext?rieur de l'environnement de base " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">R?pertoire</th><th align="left">Signification</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/pbuilderrc</code></td><td align="left">fichier de configuration</td></tr><tr><td align="left"><code class="filename">/usr/share/pbuilder/pbuilderrc</code></td><td align="left">Configuration par d?faut</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/base.tgz</code></td><td align="left">Emplacement par d?faut utilis? par pbuilder pour le fichier base.tgz
-contenant l'environnement de base constitu? uniquement des paquets
-essentiels pour la construction des paquets.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/build/PID/</code></td><td align="left">Emplacement par d?faut utilis? pour l'image de base</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/aptcache</code></td><td align="left">Emplacement par d?faut utilis? par pbuilder pour le cache apt pour stocker
-les paquets Debian pendant le processus de construction.</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> will use as cache location</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/result</code></td><td align="left">Emplacement par d?faut o? <span class="command"><strong>pbuilder</strong></span> place les paquets et
-les autres fichiers cr??s apr?s la construction</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-umlresult</code></td><td align="left">Emplacement par d?faut o? <span class="command"><strong>pbuilder-user-mode-linux</strong></span> place
-les paquets et les autres fichiers cr??s apr?s la construction </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-mnt</code></td><td align="left">Emplacement par d?faut o? <span class="command"><strong>pbuilder-user-mode-linux</strong></span> monte
-le syst?me de fichiers COW pour l'environnement de base.</td></tr><tr><td align="left"><code class="filename">/tmp</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> montera le tmpfs ici.</td></tr><tr><td align="left"><code class="filename">${HOME}/tmp/PID.cow</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> utilise ce r?pertoire comme
-emplacement pour le syst?me de fichiers COW.</td></tr><tr><td align="left"><code class="filename">${HOME}/uml-image</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> utilise ce r?pertoire pour
-placer l'image disque pour user-mode-linux.</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" title="2.?Structure des r?pertoires ? l'int?rieur de l'image de base"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructinside"></a>2.?Structure des r?pertoires ? l'int?rieur de l'image de base</h2></div></div></div><div class="table"><a name="idp31186880"></a><p class="title"><b>Tableau?8.2.?Structure des r?pertoires ? l'int?rieur de l'image de base </b></p><div class="table-contents"><table summary="Structure des r?pertoires ? l'int?rieur de l'image de base " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">R?pertoire</th><th align="left">Signification</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/mtab</code></td><td align="left">
- Lien symbolique vers <code class="filename">/proc/mounts</code>.
- </td></tr><tr><td align="left"><code class="filename">/tmp/buildd</code></td><td align="left">Default place used in <span class="command"><strong>pbuilder</strong></span> to place the Debian
-package to be processed.
-<code class="filename">/tmp/buildd/packagename-version/</code> will be the root
-directory of the package being processed. HOME environment variable is set
-to this value inside chroot by pbuilder-buildpackage.
-<code class="option">--inputfile</code> will place files here.
- </td></tr><tr><td align="left"><code class="filename">/runscript</code></td><td align="left">Le script utilis? comme argument pour <span class="command"><strong>pbuilder execute</strong></span>
-est plac? ici.
- </td></tr><tr><td align="left"><code class="filename">/tmp/hooks</code></td><td align="left">
- Emplacement des crochets.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/apt/archives</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> copie le contenu de ce r?pertoire depuis et vers
-le r?pertoire aptcache ? l'ext?rieur de l'environnement de base.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> bind-mounts this directory for use by ccache.
- </td></tr><tr><td align="left"><code class="filename">/tmp/XXXX</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> utilise un script dans
-<code class="filename">/tmp</code> pour le d?marrage initial dans user-mode-linux</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="chapter" title="Chapitre?9.?Quelques d?tails arch?ologiques mineurs"><div class="titlepage"><div><div><h2 class="title"><a name="idp31209552"></a>Chapitre?9.?Quelques d?tails arch?ologiques mineurs</h2></div></div></div><div class="toc"><p><b>Table des mati?res</b></p><dl><dt><span class="sect1"><a href="#idp31210288">1. Historique de la documentation </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Histoire peut-?tre incorrecte de pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp31220576">2.1. L'avant pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Naissance de pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. Et la seconde ann?e de sa vie</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Cinq ann?es de pbuilder</a></span></dt></dl></dd></dl></div><div class="sect1" title="1.?Historique de la documentation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31210288"></a>1.?Historique de la documentation </h2></div></div></div><p>
- Ce document a ?t? commenc? le 28 d?cembre 2002 par Junichi Uekawa qui
-essayait de documenter ce qui ?tait connu ? propos de
-<span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- Cette documentation est disponible dans les sources de
-<span class="command"><strong>pbuilder</strong></span> et depuis le d?p?t git de
-<span class="command"><strong>pbuilder</strong></span> (un acc?s web est possible). Une copie de cette
-documentation peut ?tre trouv?e sur <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.html" target="_top">la page du projet
-Alioth pour pbuilder</a>. Il existe une <a class="ulink" href="" target="_top">version en
-PDF</a>. La page d'accueil pour <span class="command"><strong>pbuilder</strong></span> est <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">http://pbuilder.alioth.debain.org/
-</a> h?berg?e par le projet alioth.
- </p><p>
- La documentation est ?crite avec DocBook XML, en utilisant le mode PSGML
-d'Emacs et wysidocbookxml pour la pr?visualisation en direct.
- </p></div><div class="sect1" title="2.?Histoire peut-?tre incorrecte de pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderbackgroundhistory"></a>2.?Histoire peut-?tre incorrecte de pbuilder</h2></div></div></div><p>
- Ce qui suit explique, de mani?re sans doute incorrecte, comment
-<span class="command"><strong>pbuilder</strong></span> 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 <span class="command"><strong>pbuilder</strong></span>.
- </p><div class="sect2" title="2.1.?L'avant pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="idp31220576"></a>2.1.?L'avant pbuilder</h3></div></div></div><p>
- 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
-d?pendances source (? mon avis) et il ?tait simple. Il aurait pu ?tre
-am?lior? mais je n'ai trouv? que des citations et non le code source.
- </p><p>
- debbuild ?tait probablement ?crit par James Troup. Je n'en suis pas s?r 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.
- </p><p>
- sbuild est un script ?crit en Perl pour construire les paquets Debian depuis
-les sources. Il prend en compte les d?pendances source et effectue quelques
-v?rifications suppl?mentaires et utilise un grand nombre d'astuces pour
-r?ussir ? 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
-d?pendances source. Il a ?t? ?crit par Ronan Hodek et je suppose qu'il a ?t?
-corrig? et am?lior? par de nombreuses personnes. Il fait partie de
-wanna-build et ?tait tr?s utilis? dans le syst?me de construction
-automatique buildd de Debian. Je crois qu'il ?tait maintenu principalement
-par Ryan Murray.
- </p></div><div class="sect2" title="2.2.?Naissance de pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="birth"></a>2.2.?Naissance de pbuilder</h3></div></div></div><p>
- wanna-build (sbuild) ?tait (en 2001) particuli?rement difficile ? configurer
-et il n'est jamais devenu un paquet Debian. dbuild a permis de promouvoir
-l'usage des d?pendances source.
- </p><p>
- Construire des paquets depuis les sources en respectant les d?pendances
-source semblait trivial et <span class="command"><strong>pbuilder</strong></span> est n?. C'?tait
-initialement un script shell de seulement quelques lignes qui appelait
-debootstrap, chroot et dpkg-buildpackage ? chaque ex?cution. Mais il a ?t?
-rapidement d?cid? que cette approche ?tait trop lente.
- </p><p>
- 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 <span class="command"><strong>pbuilder</strong></span>, but the amount of
-packages which are not buildable is steadily decreasing (I hope).
- </p></div><div class="sect2" title="2.3.?Et la seconde ann?e de sa vie"><div class="titlepage"><div><div><h3 class="title"><a name="secondyear"></a>2.3.?Et la seconde ann?e de sa vie</h3></div></div></div><p>
- Quelqu'un voulait que <span class="command"><strong>pbuilder</strong></span> ne soit pas lanc? sous
-l'utilisateur root et j'ai commenc? ? jouer avec
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>. Ce dernier n'est pas rest?
-aussi fonctionnel que je l'aurais voulu et construire l'environnement
-<span class="command"><strong>user-mode-linux</strong></span> ?tait tr?s difficile en raison de la
-qualit? du code de user-mode-linux ainsi que son empaquetage. R?guli?rement,
-le support du r?seau ?tait cass? d'une fa?on ou d'une autre.
- </p></div><div class="sect2" title="2.4.?Cinq ann?es de pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="fifthyear"></a>2.4.?Cinq ann?es de pbuilder</h3></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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 t?ches
-similaires mais ils n'ont pas exactement le m?me but. En m?moire,
-<span class="command"><strong>pbuilder</strong></span> est d?sormais co-maintenu par plusieurs
-personnes.
- </p><p>
- <span class="command"><strong>sbuild</strong></span> est maintenant un paquet Debian bien maintenu. En
-raison de la lenteur de <span class="command"><strong>pbuilder</strong></span>, certaines personnes
-pr?f?rent l'approche de sbuild. Les d?veloppements visant ? utilisant les
-instantan?s LVM, cowloop ou cowdancer permettront sans doute d'am?liorer
-cette situation.
- </p></div></div></div></div></body></html>
diff -Nru pbuilder-0.215+nmu3/Documentation/pbuilder-doc.html pbuilder-0.215+nmu4/Documentation/pbuilder-doc.html
--- pbuilder-0.215+nmu3/Documentation/pbuilder-doc.html 2012-12-24 05:52:22.000000000 +0100
+++ pbuilder-0.215+nmu4/Documentation/pbuilder-doc.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,1069 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pbuilder User's Manual</title><link rel="stylesheet" type="text/css" href="pbuilder-doc.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div lang="en" class="book" title="pbuilder User's Manual"><div class="titlepage"><div><div><h1 class="title"><a name="idp52041696"></a>pbuilder User's Manual</h1></div><div><h2 class="subtitle">Usage and operations</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Junichi</span> <span class="surname">Uekawa</span></h3></div></div></div><div><p class="releaseinfo">documentation in progress</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#introduction">1. Introducing pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#aim">1. Aims of pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#usingpbuilder">2. Using pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#creatingbase">1. Creating a base chroot image tar-ball</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Updating the base.tgz</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Building a package using the base.tgz</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Facilitating Debian Developers' typing, pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Configuration Files</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Building packages as non-root inside the chroot</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Using pbuilder for back-porting</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Mass-building packages</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Auto-backporting scripts</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Using pbuilder for automated testing of packages</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Using pbuilder for testing builds with alternate compilers</a></span></dt></dl></dd><dt><span class="chapter"><a href="#pbuilder-uml">3. Using User-mode-linux with pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. Configuring user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Configuring rootstrap</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Configuring pbuilder-uml</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Considerations for running pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Parallel running of pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine</a></span></dt></dl></dd><dt><span class="chapter"><a href="#faq">4. Frequently asked questions </a></span></dt><dd><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. pbuilder create fails</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Directories that cannot be bind-mounted</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. Logging in to pbuilder to investigate build failure</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. Logging in to pbuilder to modify the environment</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. Setting BUILDRESULTUID for sudo sessions</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Notes on usage of $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific distribution</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Using environmental variables for running <span class="command"><strong>pbuilder</strong></span>
- for specific distribution
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Using special apt sources lists, and local packages</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. How to get pbuilder to run apt-get update before trying to satisfy build-dependency</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Different bash prompts inside pbuilder login</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Creating a chroot reminder</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Using /var/cache/apt/archives for the package cache</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. pbuilder back ported to stable Debian releases</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warning about LOGNAME not being defined</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Cannot Build-conflict against an essential package</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Avoiding the "ln: Invalid cross-device link" message</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Using fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Using debconf inside pbuilder sessions</a></span></dt><dt><span class="sect1"><a href="#nodev">20. nodev mount options hinder pbuilder activity</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder is slow</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Using pdebuild to sponsor package</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Why is there a source.changes file in ../?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 and i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Using tmpfs for buildplace</a></span></dt><dt><span class="sect1"><a href="#idp57743216">26. Using svn-buildpackage together with pbuilder</a></span></dt></dl></dd><dt><span class="chapter"><a href="#develanddebug">5. Troubleshooting and development</a></span></dt><dd><dl><dt><span class="sect1"><a href="#bugreport">1. Reporting bugs </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailing list</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC Channel</a></span></dt><dt><span class="sect1"><a href="#development">4. Information for pbuilder developers</a></span></dt></dl></dd><dt><span class="chapter"><a href="#otheruse">6. Other uses of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#chroot">1. Using pbuilder for small experiments</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Running little programs inside the chroot</a></span></dt></dl></dd><dt><span class="chapter"><a href="#experimental">7. Experimental or wishlist features of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#lvm">1. Using LVM</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Using cowdancer</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Using pbuilder without tar.gz</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. Using pbuilder in a vserver</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></dd><dt><span class="chapter"><a href="#refs">8. Reference materials</a></span></dt><dd><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Directory structure outside the chroot</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Directory structure inside the chroot</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp57886192">9. Minor archaeological details</a></span></dt><dd><dl><dt><span class="sect1"><a href="#idp57886832">1. Documentation history </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Possibly inaccurate Background History of pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp57896896">2.1. The Time Before pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Birth of pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. And the second year of its life</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Fifth year of pbuilder</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>5.1. <a href="#dirtestsuites">Directory structure of the testsuite</a></dt><dt>8.1. <a href="#idp57833296">Directory Structure outside the chroot </a></dt><dt>8.2. <a href="#idp57863936">Directory Structure inside the chroot </a></dt></dl></div><div class="chapter" title="Chapter?1.?Introducing pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="introduction"></a>Chapter?1.?Introducing pbuilder</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#aim">1. Aims of pbuilder</a></span></dt></dl></div><div class="sect1" title="1.?Aims of pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="aim"></a>1.?Aims of pbuilder</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> stands for
- Personal Builder, and it is an automatic Debian Package Building system
- for personal development workstation environments.
- <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- 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.
- </p><p>
- The primary aim of <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- In this way, <span class="command"><strong>pbuilder</strong></span> tries to ensure
- that packages
- tested against <span class="command"><strong>pbuilder</strong></span> will build properly in
- most Debian installations, hopefully resulting
- in a good overall Debian source-buildability.
- </p><p>
- 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.
- </p></div></div><div class="chapter" title="Chapter?2.?Using pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="usingpbuilder"></a>Chapter?2.?Using pbuilder</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#creatingbase">1. Creating a base chroot image tar-ball</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. Updating the base.tgz</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. Building a package using the base.tgz</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Facilitating Debian Developers' typing, pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. Configuration Files</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. Building packages as non-root inside the chroot</a></span></dt><dt><span class="sect1"><a href="#backporting">7. Using pbuilder for back-porting</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. Mass-building packages</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. Auto-backporting scripts</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. Using pbuilder for automated testing of packages</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. Using pbuilder for testing builds with alternate compilers</a></span></dt></dl></div><p>
- There are several simple commands for operation.
- <span class="command"><strong>pbuilder create</strong></span>, <span class="command"><strong>pbuilder
- update</strong></span>, and <span class="command"><strong>pbuilder build</strong></span> commands
- are the typical commands used. Let us look at the commands
- one by one.
- </p><div class="sect1" title="1.?Creating a base chroot image tar-ball"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creatingbase"></a>1.?Creating a base chroot image tar-ball</h2></div></div></div><p>
- <span class="command"><strong>pbuilder create</strong></span>
- 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
- <span class="command"><strong><code class="option">--distribution</code></strong></span>
- command-line option.
- </p><p>
- <span class="command"><strong>debootstrap</strong></span> <sup>[<a name="idp52238768" href="#ftn.idp52238768" class="footnote">1</a>]</sup>
- is used to create
- the bare minimum Debian installation,
- and then build-essential packages are installed on top
- of the minimum installation using <span class="command"><strong>apt-get</strong></span>
- inside the chroot.
- </p><p>
- For fuller documentation of command-line options, see
- the pbuilder.8 manual page.
- Some configuration will be required for <code class="filename">/etc/pbuilderrc</code>
- for the mirror site
- <sup>[<a name="idp52241680" href="#ftn.idp52241680" class="footnote">2</a>]</sup>
- to use, and proxy configuration may be required to allow access
- through HTTP.
- See the pbuilderrc.5 manual page for details.
- </p></div><div class="sect1" title="2.?Updating the base.tgz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="basechroot"></a>2.?Updating the base.tgz</h2></div></div></div><p><span class="command"><strong>pbuilder update</strong></span>
- will update the base.tgz.
- It will extract the chroot, invoke <span class="command"><strong>apt-get update</strong></span>
- and <span class="command"><strong>apt-get dist-upgrade</strong></span> inside the
- chroot, and then recreate the base.tgz (the base tar-ball).
- </p><p>
- It is possible to switch the distribution which the
- base.tgz is targeted at at this point.
- Specify <span class="command"><strong><code class="option">--distribution <em class="parameter"><code>sid</code></em></code> <code class="option">--override-config</code></strong></span> to change the distribution
- to sid.
- <sup>[<a name="idp52071072" href="#ftn.idp52071072" class="footnote">3</a>]</sup>
- </p><p>
- For fuller documentation of command-line options, see
- the pbuilder.8 manual page
- </p></div><div class="sect1" title="3.?Building a package using the base.tgz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="buildpackagechroot"></a>3.?Building a package using the base.tgz</h2></div></div></div><p>
- To build a package inside the chroot, invoke
- <span class="command"><strong>pbuilder build <code class="option">whatever.dsc</code></strong></span>.
- <span class="command"><strong>pbuilder</strong></span> 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 <span class="command"><strong><code class="option">--buildresult</code></strong></span>
- command-line option.
- </p><p>
- The <span class="command"><strong><code class="option">--basetgz</code></strong></span> option can be
- used to specify which base.tgz to use.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> will extract a fresh base chroot
- image from base.tgz. (base.tgz is created with
- <span class="command"><strong>pbuilder create</strong></span>, and updated with
- <span class="command"><strong>pbuilder update</strong></span>). The chroot is populated
- with build-dependencies by parsing debian/control and invoking
- <span class="command"><strong>apt-get</strong></span>.
- </p><p>
- For fuller documentation of command-line options, see
- the pbuilder.8 manual page
- </p></div><div class="sect1" title="4.?Facilitating Debian Developers' typing, pdebuild"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pdebuild"></a>4.?Facilitating Debian Developers' typing, pdebuild</h2></div></div></div><p>
- <span class="command"><strong>pdebuild</strong></span> is a little wrapper
- script that does the most frequent of all tasks.
- A Debian Developer may try to do <span class="command"><strong>debuild</strong></span>, and
- build a package, inside a Debian source directory.
- <span class="command"><strong>pdebuild</strong></span> 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.
- </p><p>
- <span class="command"><strong>pdebuild</strong></span> calls <span class="command"><strong>dpkg-source</strong></span>
- to build the source packages, and then invokes
- <span class="command"><strong>pbuilder</strong></span> on the resulting source package.
- However, unlike debuild, the resulting deb files will be
- found in the <span class="command"><strong><code class="option">--buildresult</code></strong></span>
- directory.
- </p><p>
- See the pdebuild.1 manual page for more details.
- </p><p>
- There is a slightly different mode of operation available
- in <span class="command"><strong>pdebuild</strong></span> since version 0.97. <span class="command"><strong>pdebuild</strong></span> usually runs
- <span class="command"><strong>debian/rules clean</strong></span> outside of the chroot;
- however, it is possible to change the behavior to run it
- inside the chroot with
- the <span class="command"><strong><code class="option">--use-pdebuild-internal</code></strong></span>.
- It will try to bind mount the working directory inside chroot,
- and run <span class="command"><strong>dpkg-buildpackage</strong></span> inside.
- It has the following characteristics, and is not yet the
- default mode of operation.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- Satisfies build-dependency inside the chroot before creating source package.
- (which is a good point that default <span class="command"><strong>pdebuild</strong></span> could not do).
- </p></li><li class="listitem"><p>The working directory is modified
- from inside the chroot.</p></li><li class="listitem"><p>Building with <span class="command"><strong>pdebuild</strong></span> does not guarantee
- that it works with <span class="command"><strong>pbuilder</strong></span>.</p></li><li class="listitem"><p>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).</p></li><li class="listitem"><p>Does not work in the same manner as it used to;
- for example, <span class="command"><strong><code class="option">--buildresult</code></strong></span>
- does not have any effect.</p></li><li class="listitem"><p>The build inside chroot is ran with the current user outside chroot.
- </p></li></ul></div></div><div class="sect1" title="5.?Configuration Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configfile"></a>5.?Configuration Files</h2></div></div></div><p>
- It is possible to specify all settings by command-line
- options. However, for typing convenience, it is possible to
- use a configuration file.
- </p><p>
- <code class="filename">/etc/pbuilderrc</code> and
- <code class="filename">${HOME}/.pbuilderrc</code>
- are read in when <span class="command"><strong>pbuilder</strong></span> is invoked.
- The possible options are documented in
- the pbuilderrc.5 manual page.
- </p><p>
- It is useful to use <code class="option">--configfile</code> option to load up a preset
- configuration file when switching between configuration files for
- different distributions.
- </p><p>
- Please note <code class="filename">${HOME}/.pbuilderrc</code> 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.
- </p></div><div class="sect1" title="6.?Building packages as non-root inside the chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonrootchroot"></a>6.?Building packages as non-root inside the chroot</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
- <span class="command"><strong>pbuilder</strong></span> can create a user which is only used
- inside <span class="command"><strong>pbuilder</strong></span> and use that user id when
- building, and use the <span class="command"><strong>fakeroot</strong></span> command
- when root privilege is required.
- </p><p>
- 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
- <span class="command"><strong>pbuilder</strong></span> to affect the environment outside the chroot.
- When BUILDUSERNAME configuration option is also set,
- <span class="command"><strong>pbuilder</strong></span> will use the specified user name and fakeroot for building packages,
- instead of running as root inside chroot.
- </p><p>
- Even when using the fakerooting method, <span class="command"><strong>pbuilder</strong></span> will run with
- root privilege when it is required.
- For example, when installing
- packages to the chroot, <span class="command"><strong>pbuilder</strong></span> will run under root privilege.
- </p><p>
- To be able to invoke <span class="command"><strong>pbuilder</strong></span> without being
- root, you need to use user-mode-linux, as explained
- in <a class="xref" href="#pbuilder-uml" title="Chapter?3.?Using User-mode-linux with pbuilder">Chapter?3, <i>Using User-mode-linux with pbuilder</i></a>.
- </p></div><div class="sect1" title="7.?Using pbuilder for back-porting"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="backporting"></a>7.?Using pbuilder for back-porting</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>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).</p></li><li class="listitem"><p>The stable distribution may have bugs that have been
- fixed in unstable which need to be worked around.</p></li><li class="listitem"><p>The package in the unstable distribution may have
- problems building even on unstable.</p></li></ul></div></div><div class="sect1" title="8.?Mass-building packages"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="massbuild"></a>8.?Mass-building packages</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> can be automated, because its operations are
- non-interactive.
- It is possible to run <span class="command"><strong>pbuilder</strong></span> 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 <span class="command"><strong>pbuilder</strong></span>. There were several problems with auto-building:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Build-Dependencies need to install non-interactively, but
- some packages are so broken that they cannot install
- without interaction (like postgresql).</p></li><li class="listitem"><p>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.)
- </p></li><li class="listitem"><p>Some people were quite hostile against build failure reports.</p></li></ul></div><p>
- Most of the initial bugs have been resolved in the <span class="command"><strong>pbuilder</strong></span>
- 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.
- </p><p>
- A script that was used by Junichi Uekawa in the initial run is now included in
- the <span class="command"><strong>pbuilder</strong></span> distribution, as <span class="command"><strong>pbuildd.sh</strong></span>.
- It is available in <code class="filename">/usr/share/doc/pbuilder/examples/pbuildd/</code>
- and its configuration is in <code class="filename">/etc/pbuilder/pbuildd-config.sh</code>.
- It should be easy enough to set up for people who are used to
- <span class="command"><strong>pbuilder</strong></span>. 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.
- </p><p>
- To set up pbuildd, there are some points to be aware of.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A file <code class="filename">./avoidlist</code> needs to be available with the list of packages to avoid building. </p></li><li class="listitem"><p>It will try building anything, even packages
- which are not aimed for your architecture.</p></li><li class="listitem"><p>Because you are running random build scripts, it is better to use
- the fakeroot option of <span class="command"><strong>pbuilder</strong></span>, to avoid running the build
- under root privilege.</p></li><li class="listitem"><p>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.</p></li><li class="listitem"><p>
- 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.
- </p></li></ul></div></div><div class="sect1" title="9.?Auto-backporting scripts"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autobackport"></a>9.?Auto-backporting scripts</h2></div></div></div><p>
- There are some people who use <span class="command"><strong>pbuilder</strong></span> to automatically back-port
- a subset of packages to the stable distribution.
- </p><p>
- 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.
- </p></div><div class="sect1" title="10.?Using pbuilder for automated testing of packages"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autotesting"></a>10.?Using pbuilder for automated testing of packages</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Automatic install-remove-install-purge-upgrade-remove-upgrade-purge test-suite (distributed as an example, <code class="filename">B91dpkg-i</code>),
- or just check that everything installs somewhat (<code class="filename">execute_installtest.sh</code>).</p></li><li class="listitem"><p>Automatically running lintian (distributed as an example in
- <code class="filename">/usr/share/doc/pbuilder/examples/B90lintian</code>).</p></li><li class="listitem"><p>Automatic debian-test of the package?
- The debian-test package has been removed from Debian.
- A <span class="command"><strong>pbuilder</strong></span> implementation can be found as
- debian/pbuilder-test directory, implemented through B92test-pkg script.</p></li></ul></div><p>
- To use B92test-pkg script, first, add it to your hook directory.
- <sup>[<a name="idp57538608" href="#ftn.idp57538608" class="footnote">4</a>]</sup>.
- The test files are shell scripts
- placed in
- <code class="filename">debian/pbuilder-test/NN_name</code> (where
- NN is a number) following run-parts standard<sup>[<a name="idp57540576" href="#ftn.idp57540576" class="footnote">5</a>]</sup>
- 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.
- </p><p>
- Example scripts for use with pbuilder-test can be found in
- <code class="filename">/usr/share/doc/pbuilder/examples/pbuilder-test</code>.
- </p></div><div class="sect1" title="11.?Using pbuilder for testing builds with alternate compilers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altcompiler"></a>11.?Using pbuilder for testing builds with alternate compilers</h2></div></div></div><p>
- Most packages are compiled with <span class="command"><strong>gcc</strong></span>
- or <span class="command"><strong>g++</strong></span>
- 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 <span class="command"><strong>gcc-3.2</strong></span> for gcc compiler
- version 3.2.
- It was therefore possible to try compiling packages against different
- compiler versions.
- <span class="command"><strong>pentium-builder</strong></span> 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 <span class="command"><strong>pentium-builder</strong></span> in <span class="command"><strong>pbuilder</strong></span>, it is possible to set up the
- following in the configuration:
- </p><pre class="screen">
-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2</pre><p>
- </p><p>
- It will instruct <span class="command"><strong>pbuilder</strong></span> to install the <span class="command"><strong>pentium-builder</strong></span> package
- and also the GCC 3.2 compiler packages inside the chroot,
- and set the environment variables required for
- <span class="command"><strong>pentium-builder</strong></span> to function.
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp52238768" href="#idp52238768" class="para">1</a>] </sup>debootstrap or cdebootstrap can be chosen</p></div><div class="footnote"><p><sup>[<a id="ftn.idp52241680" href="#idp52241680" class="para">2</a>] </sup>
- 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.
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp52071072" href="#idp52071072" class="para">3</a>] </sup>Only upgrading is supported.
- Debian does not generally support downgrading (yet?).</p></div><div class="footnote"><p><sup>[<a id="ftn.idp57538608" href="#idp57538608" class="para">4</a>] </sup>It is possible to specify <span class="command"><strong>--hookdir
- /usr/share/doc/pbuilder/examples</strong></span> command-line
- option to include all example hooks as
- well.</p></div><div class="footnote"><p><sup>[<a id="ftn.idp57540576" href="#idp57540576" class="para">5</a>] </sup> See run-parts(8). For example, no '.' in file
- names!
- </p></div></div></div><div class="chapter" title="Chapter?3.?Using User-mode-linux with pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="pbuilder-uml"></a>Chapter?3.?Using User-mode-linux with pbuilder</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. Configuring user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. Configuring rootstrap</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. Configuring pbuilder-uml</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. Considerations for running pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. Parallel running of pbuilder-user-mode-linux</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine</a></span></dt></dl></div><p>
- It is possible to use user-mode-linux by invoking
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> instead of
- <span class="command"><strong>pbuilder</strong></span>.
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> doesn't require root
- privileges, and it uses the copy-on-write (COW) disk access
- method of <span class="command"><strong>User-mode-linux</strong></span> which typically
- makes it much faster than the traditional
- <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- <span class="command"><strong>User-mode-linux</strong></span> is a somewhat less proven
- platform than the standard Unix tools which
- <span class="command"><strong>pbuilder</strong></span> relies on
- (<span class="command"><strong>chroot</strong></span>, <span class="command"><strong>tar</strong></span>, and
- <span class="command"><strong>gzip</strong></span>) but mature enough to support
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> since its version
- 0.59. And since then,
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> has seen a rapid
- evolution.
- </p><p>
- The configuration of <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
- goes in three steps:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Configuration of user-mode-linux</p></li><li class="listitem"><p>Configuration of rootstrap</p></li><li class="listitem"><p>Configuration of pbuilder-uml</p></li></ul></div><p>
- </p><div class="sect1" title="1.?Configuring user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="user-mode-linux-config"></a>1.?Configuring user-mode-linux</h2></div></div></div><p>
- 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 <span class="command"><strong>rootstrap</strong></span> or
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span>. For details,
- read
- <code class="filename">/usr/share/doc/uml-utilities/README.Debian</code>
- and the <span class="command"><strong>user-mode-linux</strong></span> documentation. (It's in a separate
- package, user-mode-linux-doc.)
- </p><p>
- <span class="command"><strong>user-mode-linux</strong></span> requires
- the user to be in the uml-net group in order to configure the network
- unless you are using slirp.
- </p><p>
- 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.
- </p></div><div class="sect1" title="2.?Configuring rootstrap"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="rootstrap"></a>2.?Configuring rootstrap</h2></div></div></div><p>
- <span class="command"><strong>rootstrap</strong></span>
- is a wrapper around debootstrap.
- It creates a Debian disk image for use with UML.
- To configure rootstrap, there are several requirements.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Install the rootstrap package.</p></li><li class="listitem"><p>
- TUN/TAP only:
- add the user to the uml-net group to allow access to the network
- </p><pre class="screen">adduser dancer uml-net</pre><p>
- </p></li><li class="listitem"><p>TUN/TAP only:
- Check that the kernel supports the TUN/TAP interface,
- or recompile the kernel if necessary.
- </p></li><li class="listitem"><p>Set up <code class="filename">/etc/rootstrap/rootstrap.conf</code>.
- For example,
- if the current host is 192.168.1.2, changing following
- entries to something like this seems to work.
- </p><pre class="screen">
-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</pre><p>
- Some experimentation with configuration and running
- <span class="command"><strong>rootstrap ~/test.uml</strong></span> to actually
- test it would be handy.
- </p><p>
- Using slirp requires less configuration.
- The default configuration comes with a working example.
- </p></li></ul></div></div><div class="sect1" title="3.?Configuring pbuilder-uml"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlconfig"></a>3.?Configuring pbuilder-uml</h2></div></div></div><p>
- The following needs to happen:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Install the pbuilder-uml package.</p></li><li class="listitem"><p>
- Set up the configuration file
- <code class="filename">/etc/pbuilder/pbuilder-uml.conf</code>
- in the following manner. It will be different for slirp.
- </p><pre class="screen">
-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"</pre><p>
- Also, it needs to match the rootstrap configuration.
- </p></li><li class="listitem"><p>
- Make sure BUILDPLACE is writable by the user.
- Change BUILDPLACE in the configuration file to a place
- where the user has access.
- </p></li><li class="listitem"><p>Run <span class="command"><strong>pbuilder-user-mode-linux <code class="option">create --distribution sid</code></strong></span> to create the image.</p></li><li class="listitem"><p>Try running <span class="command"><strong>pbuilder-user-mode-linux build</strong></span>.</p></li></ul></div><p>
- </p></div><div class="sect1" title="4.?Considerations for running pbuilder-user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="consideruml"></a>4.?Considerations for running pbuilder-user-mode-linux</h2></div></div></div><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> emulates most of <span class="command"><strong>pbuilder</strong></span>, but there
- are some differences.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> does not support all options of <span class="command"><strong>pbuilder</strong></span>
- properly yet. This is a problem, and will be addressed as
- specific areas are discovered.
- </p></li><li class="listitem"><p>
- /tmp is handled differently inside
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span>. In
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span>,
- <code class="filename">/tmp</code> is mounted as tmpfs inside UML,
- so accessing files under <code class="filename">/tmp</code> from
- outside user-mode-linux does not work. It affects options
- like <span class="command"><strong><code class="option">--configfile</code></strong></span>, and
- when trying to build packages placed under
- <code class="filename">/tmp</code>.
- </p></li></ul></div></div><div class="sect1" title="5.?Parallel running of pbuilder-user-mode-linux"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paralleluml"></a>5.?Parallel running of pbuilder-user-mode-linux</h2></div></div></div><p>
- To run <span class="command"><strong>pbuilder-user-mode-linux</strong></span> in parallel
- on a system, there are a few things to bear in mind.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The create and update methods must not be run when
- a build is in progress, or the COW file will be invalidated.</p></li><li class="listitem"><p>
- 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 <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
- several times will result in failure to access the network.
- But something like the following will work:
- </p><pre class="screen">
-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</pre><p>
- When using slirp, this problem does not exist.
- </p></li></ul></div></div><div class="sect1" title="6.?Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlwrap"></a>6.?Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine</h2></div></div></div><p>
- It is possible to use
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> for other uses
- than just building Debian packages.
- <span class="command"><strong>pbuilder-user-mode-linux
- <code class="option">login</code></strong></span> will let a user use a shell
- inside the user-mode-linux <span class="command"><strong>pbuilder</strong></span> base
- image, and <span class="command"><strong>pbuilder-user-mode-linux
- <code class="option">execute</code></strong></span> will allow the user to
- execute a script inside the image.
- </p><p>
- 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.
- </p><p>
- Note that it is not possible to use a script from
- <code class="filename">/tmp</code> due to the way
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> mounts a tmpfs at
- <code class="filename">/tmp</code>.
- </p><p>
- The following example script may be useful in starting a sshd
- inside user-mode-linux.
- </p><pre class="screen">
-#!/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</pre></div></div><div class="chapter" title="Chapter?4.?Frequently asked questions"><div class="titlepage"><div><div><h2 class="title"><a name="faq"></a>Chapter?4.?Frequently asked questions </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. pbuilder create fails</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. Directories that cannot be bind-mounted</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. Logging in to pbuilder to investigate build failure</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. Logging in to pbuilder to modify the environment</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. Setting BUILDRESULTUID for sudo sessions</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. Notes on usage of $TMPDIR</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific distribution</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Using environmental variables for running <span class="command"><strong>pbuilder</strong></span>
- for specific distribution
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Using special apt sources lists, and local packages</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. How to get pbuilder to run apt-get update before trying to satisfy build-dependency</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. Different bash prompts inside pbuilder login</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Creating a chroot reminder</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Using /var/cache/apt/archives for the package cache</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. pbuilder back ported to stable Debian releases</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warning about LOGNAME not being defined</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Cannot Build-conflict against an essential package</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Avoiding the "ln: Invalid cross-device link" message</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Using fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Using debconf inside pbuilder sessions</a></span></dt><dt><span class="sect1"><a href="#nodev">20. nodev mount options hinder pbuilder activity</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder is slow</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Using pdebuild to sponsor package</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Why is there a source.changes file in ../?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 and i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Using tmpfs for buildplace</a></span></dt><dt><span class="sect1"><a href="#idp57743216">26. Using svn-buildpackage together with pbuilder</a></span></dt></dl></div><p>
- Here, known problems and frequently asked questions are
- documented. This portion was initially available in README.Debian
- file, but moved here.
- </p><div class="sect1" title="1.?pbuilder create fails"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuildercreatefail"></a>1.?pbuilder create fails</h2></div></div></div><p>
- It often happens that <span class="command"><strong>pbuilder</strong></span> cannot create the latest chroot.
- Try upgrading <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- There are people who occasionally back port debootstrap to stable
- versions; hunt for them.
- </p><p>
- When there are errors with the debootstrap phase,
- the debootstrap script needs to be fixed.
- <span class="command"><strong>pbuilder</strong></span> does not provide a way to work around debootstrap.
- </p></div><div class="sect1" title="2.?Directories that cannot be bind-mounted"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bindmountlimits"></a>2.?Directories that cannot be bind-mounted</h2></div></div></div><p>
- Because of the way <span class="command"><strong>pbuilder</strong></span> works, there
- are several directories which cannot be bind-mounted when
- running <span class="command"><strong>pbuilder</strong></span>. The directories include
- <code class="filename">/tmp</code>,
- <code class="filename">/var/cache/pbuilder</code>, and system
- directories such as <code class="filename">/etc</code> and
- <code class="filename">/usr</code>. The recommendation is to use
- directories under the user's home directory for bind-mounts.
- </p></div><div class="sect1" title="3.?Logging in to pbuilder to investigate build failure"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="shellafterfail"></a>3.?Logging in to pbuilder to investigate build failure</h2></div></div></div><p>
- It is possible to invoke a shell session after a build
- failure. Example hook scripts are provided as
- <code class="filename">C10shell</code> and
- <code class="filename">C11screen</code> scripts. C10shell script will
- start bash inside chroot, and C11screen script will start GNU
- screen inside the chroot.
- </p></div><div class="sect1" title="4.?Logging in to pbuilder to modify the environment"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modifyupdate"></a>4.?Logging in to pbuilder to modify the environment</h2></div></div></div><p>
- It is sometimes necessary to modify the chroot environment.
- <span class="command"><strong>login</strong></span> will remove the contents of the chroot after logout.
- It is possible to invoke a shell using hook scripts.
- <span class="command"><strong>pbuilder update</strong></span> executes 'E' scripts,
- and a sample for invoking a shell
- is provided as <code class="filename">C10shell</code>.
- </p><pre class="screen">
-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell</pre><p>
- It is also possible to add <code class="option">--save-after-exec</code>
- and/or <code class="option">--save-after-login</code> options
- to the <span class="command"><strong>pbuilder login</strong></span> session
- to accomplish the goal.
- It is possible to add the <code class="option">--uml-login-nocow</code> option
- to <span class="command"><strong>pbuilder-user-mode-linux <code class="option">login</code></strong></span> session
- as well.
- </p></div><div class="sect1" title="5.?Setting BUILDRESULTUID for sudo sessions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="BUILDRESULTUID"></a>5.?Setting BUILDRESULTUID for sudo sessions</h2></div></div></div><p>
- It is possible to set
- </p><pre class="screen">BUILDRESULTUID=$SUDO_UID</pre><p> in pbuilderrc to set
- the proper BUILDRESULTUID when using <span class="command"><strong>sudo</strong></span>.
- </p></div><div class="sect1" title="6.?Notes on usage of $TMPDIR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpdir"></a>6.?Notes on usage of $TMPDIR</h2></div></div></div><p>
- If you are setting $TMPDIR to an unusual value, of other than
- <code class="filename">/tmp</code>, you will find that some errors may occur inside the chroot,
- such as <span class="command"><strong>dpkg-source</strong></span> failing.
- </p><p>There are two options, you may install a hook to create that
- directory, or set
- </p><pre class="screen">export TMPDIR=/tmp</pre><p>
- in pbuilderrc. Take your pick.
- </p><p>
- An example script is provided as
- <code class="filename">examples/D10tmp</code> with <span class="command"><strong>pbuilder</strong></span>.
- </p></div><div class="sect1" title="7.?Creating a shortcut for running pbuilder with a specific distribution"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="DISTRIBUTIONSWITCH"></a>7.?Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific distribution</h2></div></div></div><p>
- When working with multiple chroots, it would be nice to work
- with scripts that reduce the amount of typing. An example
- script <code class="filename">pbuilder-distribution.sh</code> is
- provided as an example. Invoking the script as
- <code class="filename">pbuilder-squeeze</code> will invoke
- <span class="command"><strong>pbuilder</strong></span> with a squeeze chroot.
- </p></div><div class="sect1" title="8.?Using environmental variables for running pbuilder for specific distribution"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ENVVARDISTRIBUTIONSWITCH"></a>8.?Using environmental variables for running <span class="command"><strong>pbuilder</strong></span>
- for specific distribution
- </h2></div></div></div><p> This section<sup>[<a name="idp57650688" href="#ftn.idp57650688" class="footnote">6</a>]</sup>
- describes briefly a way to setup and use multiple pbuilder setups
- by creating a pbuilderrc configuration in your home path (<code class="filename">$HOME/.pbuilderrc</code>)
- and using the variable "DIST" when running pbuilder or pdebuild.
-</p><p> First, setup <code class="filename">$HOME/.pbuilderrc</code> to look like:</p><p>
- </p><pre class="screen">
-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
-</pre><p>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).
- </p><p>Here's some examples on running pbuilder or pdebuild:
-</p><pre class="screen">
-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
-</pre></div><div class="sect1" title="9.?Using special apt sources lists, and local packages"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="usingspecialaptsources"></a>9.?Using special apt sources lists, and local packages</h2></div></div></div><p>
- If you have some very specialized requirements on your
- apt setup inside <span class="command"><strong>pbuilder</strong></span>,
- it is possible to specify that through
- the <span class="command"><strong><code class="option">--othermirror</code></strong></span>
- option.
- Try something like:
- <span class="command"><strong><code class="option">--othermirror "deb http://local/mirror stable main|deb-src http://local/source/repository ./"</code></strong></span>
- </p><p>
- To use the local file system instead of HTTP, it is necessary to do
- bind-mounting.
- <span class="command"><strong><code class="option">--bindmounts</code></strong></span>
- is a command-line option useful for such cases.
- </p><p>
- 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.
- </p><p>
- </p><pre class="screen">BINDMOUNTS="/var/cache/pbuilder/result"</pre><p>
- </p><p>
- Then, add the following hook
- </p><p>
- </p><pre class="screen">
-# 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</pre><p>
- </p><p>
- This way, you can use <code class="filename">deb file:/var/cache/pbuilder/result</code>
- </p><p>
- To add new apt-key inside chroot:
-
- </p><p>
- </p><pre class="screen">
-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-</pre></div><div class="sect1" title="10.?How to get pbuilder to run apt-get update before trying to satisfy build-dependency"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="apt-getupdateonbuild-depend"></a>10.?How to get pbuilder to run apt-get update before trying to satisfy build-dependency</h2></div></div></div><p>
- You can use hook scripts for this.
- D scripts are run before satisfying build-dependency.
- </p><p>
- <a class="ulink" href="http://lists.debian.org/debian-devel/2006/05/msg00550.html" target="_top">
- This snippet comes from Ondrej Sury.
- </a>
- </p></div><div class="sect1" title="11.?Different bash prompts inside pbuilder login"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bashprompt"></a>11.?Different bash prompts inside pbuilder login</h2></div></div></div><p>
- To make distinguishing bash prompts inside
- <span class="command"><strong>pbuilder</strong></span> easier, it is possible to set
- environment variables such as PS1 inside
- <code class="filename">pbuilderrc</code>
- </p><p>
- 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,<sup>[<a name="idp57674928" href="#ftn.idp57674928" class="footnote">7</a>]</sup>
- setting PS1 in pbuilderrc worked.
- </p><p>example of debian_chroot</p><pre class="screen">
- export debian_chroot="pbuild$$"</pre><p>example of PS1</p><pre class="screen">
- export PS1="pbuild chroot 32165 # "</pre></div><div class="sect1" title="12.?Creating a chroot reminder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chrootmemo"></a>12.?Creating a chroot reminder</h2></div></div></div><p>
- 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
- <code class="filename">examples/F90chrootmemo</code> hook script. It
- will create a file called <code class="filename">/CHROOT</code> inside
- your chroot.
- </p></div><div class="sect1" title="13.?Using /var/cache/apt/archives for the package cache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="packagecachearchives"></a>13.?Using /var/cache/apt/archives for the package cache</h2></div></div></div><p>
- For the help of low-bandwidth systems, it is possible to use
- <code class="filename">/var/cache/apt/archives</code> as the package
- cache. Just specify it instead of the default
- <code class="filename">/var/cache/pbuilder/aptcache</code>.
- </p><p>
- It is however not possible to do so currently with the
- user-mode-linux version of <span class="command"><strong>pbuilder</strong></span>,
- because <code class="filename">/var/cache/apt/archives</code> is
- usually only writable by root.
- </p><p>
- Use of dedicated tools such as apt-proxy is recommended, since
- caching of packages would benefit the system outside the scope
- of <span class="command"><strong>pbuilder</strong></span>.
- </p></div><div class="sect1" title="14.?pbuilder back ported to stable Debian releases"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="stablebackport"></a>14.?pbuilder back ported to stable Debian releases</h2></div></div></div><p>
- Currently stable back port of pbuilder is available at backports.org.
- </p></div><div class="sect1" title="15.?Warning about LOGNAME not being defined"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="LOGNAME"></a>15.?Warning about LOGNAME not being defined</h2></div></div></div><p>
- You might see a lot of warning messages when running <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- </p><pre class="screen">
- dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)</pre><p>
- </p><p>
- 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
- <span class="command"><strong>chroot</strong></span>. For example, dpkg requires getpwnam
- to succeed inside chroot, which means LOGNAME and the related
- user information have to be set up inside chroot.
- </p></div><div class="sect1" title="16.?Cannot Build-conflict against an essential package"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nobuildconflictessential"></a>16.?Cannot Build-conflict against an essential package</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
- </p></div><div class="sect1" title='17.?Avoiding the "ln: Invalid cross-device link" message'><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lninvalidcrossdevicelink"></a>17.?Avoiding the "ln: Invalid cross-device link" message</h2></div></div></div><p>
- By default, <span class="command"><strong>pbuilder</strong></span> uses hard links to
- manage the <span class="command"><strong>pbuilder</strong></span> 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 </p><pre class="screen">APTCACHEHARDLINK=no</pre><p> in your
- pbuilderrc file. Note that packages in
- <span class="command"><strong>APTCACHE</strong></span> will be copied into chroot local
- cache, so plan for enough space on
- <span class="command"><strong>BUILDPLACE</strong></span> device.
- </p></div><div class="sect1" title="18.?Using fakechroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="fakechroot"></a>18.?Using fakechroot</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>fakechroot</strong></span> instead of
- being root to run <span class="command"><strong>pbuilder</strong></span>; however,
- several things make this impractical.
- <span class="command"><strong>fakechroot</strong></span> overrides library loads and
- tries to override default libc functions when providing the
- functionality of virtual <span class="command"><strong>chroot</strong></span>. However,
- some binaries do no use libc to function, or override the
- overriding provided by <span class="command"><strong>fakechroot</strong></span>. One
- example is <span class="command"><strong>ldd</strong></span>. Inside
- <span class="command"><strong>fakechroot</strong></span>, <span class="command"><strong>ldd</strong></span> will
- check the library dependency outside of the chroot, which is
- not the expected behavior.
- </p><p>
- To work around the problem, debootstrap has a
- <code class="option">--variant fakechroot</code> option. Use that, so
- that ldd and ldconfig are overridden.
- </p><p>
- Make sure you have set your LD_PRELOAD path correctly, as described in
- the fakechroot manpage.
- </p></div><div class="sect1" title="19.?Using debconf inside pbuilder sessions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="debconfinsidepbuilder"></a>19.?Using debconf inside pbuilder sessions</h2></div></div></div><p>
- To use debconf inside <span class="command"><strong>pbuilder</strong></span>, setting DEBIAN_FRONTEND to
- <span class="quote">“<span class="quote">readline</span>”</span> in <code class="filename">pbuilderrc</code> should work.
- Setting it to <span class="quote">“<span class="quote">dialog</span>”</span> should also work, but make sure
- whiptail or dialog is installed inside the chroot.
- </p></div><div class="sect1" title="20.?nodev mount options hinder pbuilder activity"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nodev"></a>20.?nodev mount options hinder pbuilder activity</h2></div></div></div><p>
- If you see messages such as this when building a chroot, you are mounting the file system with
- the nodev option.
- </p><pre class="screen">
- /var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied</pre><p>
- 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
- <code class="filename">/var/cache/pbuilder</code> or $BUILDPLACE.
- </p><p>
- This is not a problem when using <span class="command"><strong>user-mode-linux</strong></span>.
- </p><p>
- See <a class="ulink" href="http://bugs.debian.org/316135" target="_top">
- 316135
- </a> for example.
- </p></div><div class="sect1" title="21.?pbuilder is slow"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="faqslowpbuilder"></a>21.?pbuilder is slow</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> is often slow. The slowest part of
- <span class="command"><strong>pbuilder</strong></span> is extracting the tar.gz every
- time <span class="command"><strong>pbuilder</strong></span> is invoked. That can be
- avoided by using <span class="command"><strong>pbuilder-user-mode-linux</strong></span>.
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> uses COW file
- system, and thus does not need to clean up and recreate the
- root file system.
- </p><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> is slower in
- executing the actual build system, due to the usual
- <span class="command"><strong>user-mode-linux</strong></span> overhead for system
- calls. It is more friendly to the hard drive.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> with cowdancer is also an
- alternative that improves speed of pbuilder startup.
- </p></div><div class="sect1" title="22.?Using pdebuild to sponsor package"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sponsor"></a>22.?Using pdebuild to sponsor package</h2></div></div></div><p>
- To sign a package marking for sponsorship, it is possible to
- use<span class="command"><strong><code class="option"> --auto-debsign</code></strong></span> and
- <span class="command"><strong><code class="option">--debsign-k</code></strong></span> options of
- <span class="command"><strong>pdebuild</strong></span>.
- </p><pre class="screen">
- <span class="command"><strong>pdebuild <code class="option">--auto-debsign </code> <code class="option">--debsign-k </code><em class="parameter"><code>XXXXXXXX</code></em></strong></span></pre></div><div class="sect1" title="23.?Why is there a source.changes file in ../?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sourcechanges"></a>23.?Why is there a source.changes file in ../?</h2></div></div></div><p>
- When running <span class="command"><strong>pdebuild</strong></span>, <span class="command"><strong>pbuilder</strong></span> will run dpkg-buildpackage to create a
- Debian source package to pass it on to <span class="command"><strong>pbuilder</strong></span>.
- 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.
- </p><p>
- This behavior is different when running through <code class="option">--use-pdebuild-internal</code>
- </p></div><div class="sect1" title="24.?amd64 and i386-mode"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="amd64i386"></a>24.?amd64 and i386-mode</h2></div></div></div><p>
- amd64 architectures are capable of running binaries in i386
- mode. It is possible to use <span class="command"><strong>pbuilder</strong></span> to
- run packages, using <span class="command"><strong>linux32</strong></span> and
- <span class="command"><strong>debootstrap <code class="option">--arch</code></strong></span> option.
- Specifically, a command-line option like the following will
- work.
- </p><p>
- </p><pre class="screen">
-<span class="command"><strong>pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
- --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian</strong></span>
-<span class="command"><strong>linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz</strong></span></pre><p>
- </p></div><div class="sect1" title="25.?Using tmpfs for buildplace"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpfsforpbuilder"></a>25.?Using tmpfs for buildplace</h2></div></div></div><p>
- To improve speed of operation, it is possible to use tmpfs for
- pbuilder build location. Mount tmpfs to
- <code class="filename">/var/cache/pbuilder/build</code>, and set
- </p><pre class="screen">APTCACHEHARDLINK=no</pre><p>.
- </p></div><div class="sect1" title="26.?Using svn-buildpackage together with pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp57743216"></a>26.?Using svn-buildpackage together with pbuilder</h2></div></div></div><p>
- pdebuild command can be used with svn-buildpackage
- --svn-builder command-line option.
- <sup>[<a name="idp57744464" href="#ftn.idp57744464" class="footnote">8</a>]</sup>
- </p><pre class="screen">
-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"</pre></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp57650688" href="#idp57650688" class="para">6</a>] </sup>This part of the documentation contributed by Andres Mejia</p><p>
- This example was taken from a wiki (<a class="ulink" href="https://wiki.ubuntu.com/PbuilderHowto" target="_top">https://wiki.ubuntu.com/PbuilderHowto</a>).
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp57674928" href="#idp57674928" class="para">7</a>] </sup>Versions of bash from and before Debian 3.0</p></div><div class="footnote"><p><sup>[<a id="ftn.idp57744464" href="#idp57744464" class="para">8</a>] </sup><a class="ulink" href="http://upsilon.cc/~zack/blog/posts/2007/09/svn-cowbuilder/" target="_top">
- Zack has posted an example on his blog.
- </a></p></div></div></div><div class="chapter" title="Chapter?5.?Troubleshooting and development"><div class="titlepage"><div><div><h2 class="title"><a name="develanddebug"></a>Chapter?5.?Troubleshooting and development</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#bugreport">1. Reporting bugs </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailing list</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC Channel</a></span></dt><dt><span class="sect1"><a href="#development">4. Information for pbuilder developers</a></span></dt></dl></div><div class="sect1" title="1.?Reporting bugs"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreport"></a>1.?Reporting bugs </h2></div></div></div><p>
- To report bugs, it would be important to have a log of what's
- going wrong. Most of the time, adding a
- <span class="command"><strong><code class="option">--debug</code></strong></span> 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.
- </p></div><div class="sect1" title="2.?Mailing list"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mailinglist"></a>2.?Mailing list</h2></div></div></div><p>
- There is a mailing list for <span class="command"><strong>pbuilder</strong></span> on
- alioth (pbuilder-maint at lists.alioth.debian.org). You can
- subscribe through the alioth web interface.
- <a class="ulink" href="http://alioth.debian.org/mail/?group_id=30778" target="_top">
- http://alioth.debian.org/mail/?group_id=30778</a>.
- </p></div><div class="sect1" title="3.?IRC Channel"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="IRCchannel"></a>3.?IRC Channel</h2></div></div></div><p>
- 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.
- </p></div><div class="sect1" title="4.?Information for pbuilder developers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="development"></a>4.?Information for pbuilder developers</h2></div></div></div><p>
- This section tries to document current development practices
- and how things generally operate in development.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> is co-maintained with resources
- provided by Alioth.
-
- There is an Alioth project page at
- <a class="ulink" href="http://alioth.debian.org/projects/pbuilder" target="_top">
- http://alioth.debian.org/projects/pbuilder</a>.
- Home page is also available,
- at <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
- http://alioth.debian.org/projects/pbuilder</a>
- which shows this text.
- git repository is available through http, git, or (if you have an
- account on alioth, ) ssh.
- </p><pre class="screen">
-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</pre><p>
- 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.
- </p><p>
- Test-suites are available in <code class="filename">./testsuite/</code> directory.
- Changes are expected not to break the test-suites.
- <code class="filename">./run-test.sh</code> is a basic test-suite, which puts a summary in
- <code class="filename">run-test.log</code>, and <code class="filename">run-test-cdebootstrap.log</code>.
- <code class="filename">./run-test-regression.sh</code> is a regression test-suite,
- which puts the result in <code class="filename">run-test-regression.log</code>.
- Currently, run-test.sh is ran automatically daily to ensure that pbuilder is working.
- </p><div class="table"><a name="dirtestsuites"></a><p class="title"><b>Table?5.1.?Directory structure of the testsuite</b></p><div class="table-contents"><table summary="Directory structure of the testsuite" border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Directory</th><th align="left">Meaning</th></tr></thead><tbody><tr><td align="left"><code class="filename">./testsuite/</code></td><td align="left">Directory for testsuite</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.sh</code></td><td align="left">Daily regression test to test against Debian Archive changes breaking pbuilder.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.log</code></td><td align="left">A summary of testsuite</td></tr><tr><td align="left"><code class="filename">./testsuite/normal/</code></td><td align="left">Directory for testsuite results of running pbuilder with debootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/cdebootstrap/</code></td><td align="left">Directory for testsuite results of running pbuilder with cdebootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.sh</code></td><td align="left">Regression testsuite, ran every time change is made to pbuilder to make sure there is no regression.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.log</code></td><td align="left">Summary of test result</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*.sh</code></td><td align="left">Regression tests, exit 0 for success, exit 1 for failure</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*</code></td><td align="left">Files used for the regression testsuite.</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/log/BugID-*.sh.log</code></td><td align="left">Output of the regression test, output from the script is redirected by run-regression.sh</td></tr></tbody></table></div></div><br class="table-break"><p>
- 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.
- </p><p>
- A TODO file is available in <code class="filename">debian/TODO</code>.
- 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.
- </p><p>
- When releasing a new version of <span class="command"><strong>pbuilder</strong></span>,
- the version is tagged with the git tag
- X.XXX (version number).
- This is done with <span class="command"><strong>./git-tag.sh</strong></span> script available in the source tree.
- </p></div></div><div class="chapter" title="Chapter?6.?Other uses of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="otheruse"></a>Chapter?6.?Other uses of pbuilder</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#chroot">1. Using pbuilder for small experiments</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Running little programs inside the chroot</a></span></dt></dl></div><div class="sect1" title="1.?Using pbuilder for small experiments"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chroot"></a>1.?Using pbuilder for small experiments</h2></div></div></div><p>
- 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 <span class="command"><strong>pbuilder login</strong></span> command is available.
- </p><p>
- <span class="command"><strong>pbuilder login </strong></span> is a debugging feature for
- <span class="command"><strong>pbuilder</strong></span> itself, but it also allows users to have a temporary chroot.
- </p><p>
- Note that the chroot is cleaned after logging out of the shell,
- and mounting file systems inside it is considered harmful.
- </p></div><div class="sect1" title="2.?Running little programs inside the chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="runningprograms"></a>2.?Running little programs inside the chroot</h2></div></div></div><p>
- To facilitate using <span class="command"><strong>pbuilder</strong></span> for other uses,
- <span class="command"><strong>pbuilder execute</strong></span> is available.
- <span class="command"><strong>pbuilder execute </strong></span> will take a script
- specified in the command-line argument, and
- invoke the script inside the chroot.
- </p><p>
- The script can be useful for sequences of operations such as
- installing ssh and adding a new user inside the chroot.
- </p></div></div><div class="chapter" title="Chapter?7.?Experimental or wishlist features of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="experimental"></a>Chapter?7.?Experimental or wishlist features of pbuilder</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#lvm">1. Using LVM</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. Using cowdancer</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. Using pbuilder without tar.gz</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. Using pbuilder in a vserver</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></div><p>
- There are some advanced features, above that of the
- basic feature of <span class="command"><strong>pbuilder</strong></span>, for some specific purposes.
- </p><div class="sect1" title="1.?Using LVM"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lvm"></a>1.?Using LVM</h2></div></div></div><p>
- LVM2 has a useful snapshot function that features Copy-on-write images.
- That could be used for <span class="command"><strong>pbuilder</strong></span> just as it can be used for
- the user-mode-linux <span class="command"><strong>pbuilder</strong></span> port.
- lvmpbuilder script in the examples directory implements such port.
- The scripts and documentation can be found under
- <code class="filename">/usr/share/doc/pbuilder/examples/lvmpbuilder/</code>.
- </p></div><div class="sect1" title="2.?Using cowdancer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cowdancer"></a>2.?Using cowdancer</h2></div></div></div><p>
- <span class="command"><strong>cowdancer</strong></span> allows copy-on-write semantics on
- file system using hard links and hard-link-breaking-on-write
- tricks. <span class="command"><strong>pbuilder</strong></span> using
- <span class="command"><strong>cowdancer</strong></span> seems to be much faster and it is
- one ideal point for improvement.
- <span class="command"><strong>cowbuilder</strong></span>, a wrapper for
- <span class="command"><strong>pbuilder</strong></span> for using
- <span class="command"><strong>cowdancer</strong></span> is available from
- <span class="command"><strong>cowdancer</strong></span> package since 0.14
- </p><p>
- Example command-lines for cowbuilder look like the following.
- </p><p>
- </p><pre class="screen">
-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc</pre><p>
- </p><p>
- It is also possible to use cowdancer with pdebuild command.
- Specify with command-line option <code class="option">--pbuilder</code>
- or set it in PDEBUILD_PBUILDER configuration option.
- </p><p>
- </p><pre class="screen">
-$ pdebuild --pbuilder cowbuilder</pre><p>
- </p></div><div class="sect1" title="3.?Using pbuilder without tar.gz"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="withouttargz"></a>3.?Using pbuilder without tar.gz</h2></div></div></div><p>
- The <span class="command"><strong><code class="option">--no-targz</code></strong></span>
- option of <span class="command"><strong>pbuilder</strong></span>
- will allow usage of <span class="command"><strong>pbuilder</strong></span> 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
- <span class="command"><strong>sbuild</strong></span>.
- </p><p>
- It should be possible to create base chroot images
- for <span class="command"><strong>dchroot</strong></span> with the following commands:
- </p><pre class="screen">
-# 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</pre><p>
- </p></div><div class="sect1" title="4.?Using pbuilder in a vserver"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="inavserver"></a>4.?Using pbuilder in a vserver</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- To use <span class="command"><strong>pbuilder</strong></span> in a vserver, you need to set the
- <span class="command"><strong>secure_mount</strong></span> <span class="command"><strong>CAPS</strong></span> in the
- <span class="command"><strong>ccapabilities</strong></span> of this vserver.
- </p></div><div class="sect1" title="5.?Usage of ccache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ccache"></a>5.?Usage of ccache</h2></div></div></div><p>
- It is possible to use C compiler cache
- <span class="command"><strong>ccache</strong></span> to speed up repeated builds of the same
- package (or packages that compile the same files multiple times for some
- reason). Using <span class="command"><strong>ccache</strong></span> can speed up repeated building
- of large packages dramatically, at the cost of some disk space and
- bookkeeping.
- </p><p>
- To enable usage of <span class="command"><strong>ccache</strong></span> with
- <span class="command"><strong>pbuilder</strong></span>, you should set CCACHEDIR in your
- pbuilderrc file.
- </p><p>
- 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.
- </p></div></div><div class="chapter" title="Chapter?8.?Reference materials"><div class="titlepage"><div><div><h2 class="title"><a name="refs"></a>Chapter?8.?Reference materials</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#dirstructoutside">1. Directory structure outside the chroot</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. Directory structure inside the chroot</a></span></dt></dl></div><div class="sect1" title="1.?Directory structure outside the chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructoutside"></a>1.?Directory structure outside the chroot</h2></div></div></div><div class="table"><a name="idp57833296"></a><p class="title"><b>Table?8.1.?Directory Structure outside the chroot </b></p><div class="table-contents"><table summary="Directory Structure outside the chroot " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Directory</th><th align="left">Meaning</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/pbuilderrc</code></td><td align="left">configuration file</td></tr><tr><td align="left"><code class="filename">/usr/share/pbuilder/pbuilderrc</code></td><td align="left">Default configuration</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/base.tgz</code></td><td align="left">Default location pbuilder uses for base.tgz, the tar-ball containing a basic Debian installation
- with only the build-essential packages.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/build/PID/</code></td><td align="left">Default location pbuilder uses for chroot</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/aptcache</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> will use as apt cache, to store deb packages required during <span class="command"><strong>pbuilder</strong></span> build.</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> will use as
-cache location</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/result</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> puts the deb files and other files created after build</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-umlresult</code></td><td align="left">Default location <span class="command"><strong>pbuilder-user-mode-linux</strong></span> puts the deb files and other files created after build </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-mnt</code></td><td align="left">Default location <span class="command"><strong>pbuilder-user-mode-linux</strong></span> uses for mounting the COW file system, for chrooting.</td></tr><tr><td align="left"><code class="filename">/tmp</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> will mount tmpfs for work.</td></tr><tr><td align="left"><code class="filename">${HOME}/tmp/PID.cow</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> use this directory for location of COW file system.</td></tr><tr><td align="left"><code class="filename">${HOME}/uml-image</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> use this directory for user-mode-linux full disk image.</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" title="2.?Directory structure inside the chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructinside"></a>2.?Directory structure inside the chroot</h2></div></div></div><div class="table"><a name="idp57863936"></a><p class="title"><b>Table?8.2.?Directory Structure inside the chroot </b></p><div class="table-contents"><table summary="Directory Structure inside the chroot " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">Directory</th><th align="left">Meaning</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/mtab</code></td><td align="left">
- symlink to <code class="filename">/proc/mounts</code>.
- </td></tr><tr><td align="left"><code class="filename">/tmp/buildd</code></td><td align="left">Default place used in <span class="command"><strong>pbuilder</strong></span>
- to place the Debian package to be processed.
- <code class="filename">/tmp/buildd/packagename-version/</code>
- will be the root directory of the package being
- processed. HOME environment variable is set to this
- value inside chroot by pbuilder-buildpackage.
- <code class="option">--inputfile</code> will place files here.
- </td></tr><tr><td align="left"><code class="filename">/runscript</code></td><td align="left">The
- script passed as an argument to
- <span class="command"><strong>pbuilder</strong></span> execute is passed on.
- </td></tr><tr><td align="left"><code class="filename">/tmp/hooks</code></td><td align="left">
- The location of hooks.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/apt/archives</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> copies the content of this directory to and from
- the aptcache directory of outside chroot.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> bind-mounts this directory for use
- by ccache.
- </td></tr><tr><td align="left"><code class="filename">/tmp/XXXX</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> uses
- a script in <code class="filename">/tmp</code> to bootstrap into
- user-mode-linux</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="chapter" title="Chapter?9.?Minor archaeological details"><div class="titlepage"><div><div><h2 class="title"><a name="idp57886192"></a>Chapter?9.?Minor archaeological details</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#idp57886832">1. Documentation history </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Possibly inaccurate Background History of pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp57896896">2.1. The Time Before pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. Birth of pbuilder</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. And the second year of its life</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. Fifth year of pbuilder</a></span></dt></dl></dd></dl></div><div class="sect1" title="1.?Documentation history"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp57886832"></a>1.?Documentation history </h2></div></div></div><p>
- This document was started on 28 Dec 2002 by
- Junichi Uekawa, trying to document what is known
- about <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- This documentation is available from the <span class="command"><strong>pbuilder</strong></span> source tar-ball,
- and from the git repository of <span class="command"><strong>pbuilder</strong></span> (web-based access is possible).
- A copy of this documentation can be found on the
- <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.html" target="_top">Alioth project page for pbuilder</a>.
- <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.pdf" target="_top">There is also a PDF version</a>.
- The homepage for <span class="command"><strong>pbuilder</strong></span> is
- <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
- http://pbuilder.alioth.debian.org/
- </a> hosted by alioth project.
- </p><p>
- Documentation is written using DocBook XML,
- with emacs PSGML mode, and using wysidocbookxml for live
- previewing.
- </p></div><div class="sect1" title="2.?Possibly inaccurate Background History of pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderbackgroundhistory"></a>2.?Possibly inaccurate Background History of pbuilder</h2></div></div></div><p>
- The following is a most possibly inaccurate account of how
- <span class="command"><strong>pbuilder</strong></span> came to happen, and other attempts to
- make something like <span class="command"><strong>pbuilder</strong></span> happen.
- This part of the document was originally in the AUTHORS file,
- to give credit to those who existed before <span class="command"><strong>pbuilder</strong></span>.
- </p><div class="sect2" title="2.1.?The Time Before pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="idp57896896"></a>2.1.?The Time Before pbuilder</h3></div></div></div><p>
- 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.
- </p><p>
- 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.
- </p><p>
- 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.
- </p></div><div class="sect2" title="2.2.?Birth of pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="birth"></a>2.2.?Birth of pbuilder</h3></div></div></div><p>
- 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.
- </p><p>
- Building packages from source using Build-Depends
- information within a chroot sounded trivial; and
- <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- 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 <span class="command"><strong>pbuilder</strong></span>,
- but the amount of packages which are not buildable
- is steadily decreasing (I hope).
- </p></div><div class="sect2" title="2.3.?And the second year of its life"><div class="titlepage"><div><div><h3 class="title"><a name="secondyear"></a>2.3.?And the second year of its life</h3></div></div></div><p>
- Someone wanted <span class="command"><strong>pbuilder</strong></span> to not run as
- root, and as User-mode-linux has become more useful as time
- passed, I've started experimenting with
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span>.
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> has not stayed
- functional as much as I would have liked, and bootstrapping
- <span class="command"><strong>user-mode-linux</strong></span> 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.
- </p></div><div class="sect2" title="2.4.?Fifth year of pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="fifthyear"></a>2.4.?Fifth year of pbuilder</h3></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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, <span class="command"><strong>pbuilder</strong></span> is now co-maintained with
- several people.
- </p><p>
- <span class="command"><strong>sbuild</strong></span> is now a well-maintained Debian package within
- Debian, and with <span class="command"><strong>pbuilder</strong></span> 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.
- </p></div></div></div></div></body></html>
diff -Nru pbuilder-0.215+nmu3/Documentation/pbuilder-doc.ja.html pbuilder-0.215+nmu4/Documentation/pbuilder-doc.ja.html
--- pbuilder-0.215+nmu3/Documentation/pbuilder-doc.ja.html 2013-03-02 08:37:59.000000000 +0100
+++ pbuilder-0.215+nmu4/Documentation/pbuilder-doc.ja.html 1970-01-01 01:00:00.000000000 +0100
@@ -1,894 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pbuilder 利用マニュアル</title><link rel="stylesheet" type="text/css" href="pbuilder-doc.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div lang="ja" class="book" title="pbuilder 利用マニュアル"><div class="titlepage"><div><div><h1 class="title"><a name="idp4627488"></a>pbuilder 利用マニュアル</h1></div><div><h2 class="subtitle">利用と操作方法について</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="surname">Uekawa</span> <span class="firstname">Junichi</span> [FAMILY Given]</h3></div></div></div><div><p class="releaseinfo">草稿</p></div></div><hr></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="chapter"><a href="#introduction">1. pbuilder の紹介</a></span></dt><dd><dl><dt><span class="sect1"><a href="#aim">1. pbuilder の目的</a></span></dt></dl></dd><dt><span class="chapter"><a href="#usingpbuilder">2. pbuilder を利用する</a></span></dt><dd><dl><dt><span class="sect1"><a href="#creatingbase">1. base chroot イメージの tar 玉の作成</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. base.tgz の更新</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. base.tgz を利用してパッケージをビルドする</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Debian Developer のタイピングを省略する、pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. 設定ファイル</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. chroot 内部で root 以外でパッケージをビルドする</a></span></dt><dt><span class="sect1"><a href="#backporting">7. pbuilder をバックポートに活用する</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. パッケージを大量にビルドする</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. 自動バックポートスクリプト</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. pbuilder を自動テストに利用する</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. pbuilder でその他のコンパイラでのビルドを試験する</a></span></dt></dl></dd><dt><span class="chapter"><a href="#pbuilder-uml">3. user-mode-linux を pbuilder で利用する</a></span></dt><dd><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. user-mode-linux の設定</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. rootstrap の設定</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. pbuilder-uml の設定</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. pbuilder-user-mode-linuxを実行する場合の検討項目</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. pbuilder-user-mode-linux を複数同時に実行させる</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual
-machine</a></span></dt></dl></dd><dt><span class="chapter"><a href="#faq">4. FAQ （よくある質問） </a></span></dt><dd><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. pbuilder create が失敗する</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. bind mount できないディレクトリ</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. ビルド失敗の調査のために pbuilder 環境にログインする</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. 環境を変更するために pbuilder 環境にログインする</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. BUILDRESULTUID を sudo のセッションに追加する</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. $TMPDIRの使い方について</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific
-distribution</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Using environmental variables for running <span class="command"><strong>pbuilder</strong></span> for
-specific distribution
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Using special apt sources lists, and local packages</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. How to get pbuilder to run apt-get update before trying to satisfy
-build-dependency</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. pbuilder login で bash のプロンプトを変更する</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Creating a chroot reminder</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Using /var/cache/apt/archives for the package cache</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. pbuilder back ported to stable Debian releases</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warning about LOGNAME not being defined</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Cannot Build-conflict against an essential package</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Avoiding the "ln: Invalid cross-device link" message</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Using fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Using debconf inside pbuilder sessions</a></span></dt><dt><span class="sect1"><a href="#nodev">20. nodev mount options hinder pbuilder activity</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder が遅い</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Using pdebuild to sponsor package</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Why is there a source.changes file in ../?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 and i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Using tmpfs for buildplace</a></span></dt><dt><span class="sect1"><a href="#idp5978160">26. svn-buildpackage を pbuilder で利用する</a></span></dt></dl></dd><dt><span class="chapter"><a href="#develanddebug">5. Troubleshooting and development</a></span></dt><dd><dl><dt><span class="sect1"><a href="#bugreport">1. Reporting bugs </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailing list</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC Channel</a></span></dt><dt><span class="sect1"><a href="#development">4. Information for pbuilder developers</a></span></dt></dl></dd><dt><span class="chapter"><a href="#otheruse">6. Other uses of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#chroot">1. pbuilder を小規模な実験のために活用する</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Running little programs inside the chroot</a></span></dt></dl></dd><dt><span class="chapter"><a href="#experimental">7. Experimental or wishlist features of pbuilder</a></span></dt><dd><dl><dt><span class="sect1"><a href="#lvm">1. LVMの活用</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. cowdancer の活用</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. tar.gz を利用しないで pbuilder を利用する</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. pbuilder を vserver で利用する</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></dd><dt><span class="chapter"><a href="#refs">8. 参考文献</a></span></dt><dd><dl><dt><span class="sect1"><a href="#dirstructoutside">1. chroot 外部のディレクトリ構造</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. chroot 内部のディレクトリ構造</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp6122272">9. 些細な過去の経緯の詳細</a></span></dt><dd><dl><dt><span class="sect1"><a href="#idp6122912">1. マニュアルの履歴 </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Possibly inaccurate Background History of pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp6132976">2.1. The Time Before pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. pbuilder の誕生</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. そして二年目の人生</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. pbuilder の5年目</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>表の一覧</b></p><dl><dt>5.1. <a href="#dirtestsuites">テストスイートのディレクトリ構造</a></dt><dt>8.1. <a href="#idp6068544">chroot 内部のディレクトリ構造 </a></dt><dt>8.2. <a href="#idp6099504">chroot 内部のディレクトリ構造 </a></dt></dl></div><div class="chapter" title="第1章 pbuilder の紹介"><div class="titlepage"><div><div><h2 class="title"><a name="introduction"></a>第1章 pbuilder の紹介</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#aim">1. pbuilder の目的</a></span></dt></dl></div><div class="sect1" title="1. pbuilder の目的"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="aim"></a>1. pbuilder の目的</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> は Personal Builder
-の略です。個人的なワークステーションなどの開発環境で、Debianパッケージをビルドするためのシステムです。<span class="command"><strong>pbuilder</strong></span>
-はパッケージが Debian
-のインストール環境のほとんどでビルドできることを確認するため、Debianパッケージをクリーンルーム内部で自動にビルドするシステムとして簡単に利用できるようになることを目指しています。クリーンルーム環境は最小限のパッケージを
-chroot にインストールすることで実現しています。
- </p><p>
- Debian
-ディストリビューションはソースコードつきのフリーソフトウェアにより構成されています。Debianの「main」セクションにあるソフトウェアは、Build-depend
-（ビルド時依存関係）として指定されたDebianの「main」セクションにあるパッケージのみがインストールされている状態でビルドできなければなりません。
- </p><p>
- 主なる <span class="command"><strong>pbuilder</strong></span>
-の目的は、他の自動ビルドシステムとは違います。それは、パッケージをできるだけビルドできるようなことを目的としていないところです。パッケージが何を必要としているのかを想像しようとはしません。また選択が可能であれば、最悪な選択をする場合もあります。
- </p><p>
- この方針を採用することで、 <span class="command"><strong>pbuilder</strong></span> は、 <span class="command"><strong>pbuilder</strong></span>
-で試験したパッケージはほとんどのDebianがインストールされた環境でビルドできるように確認することができます。これによってDebian全体としてのソースコードのビルドしやすさの向上を目指しています。
- </p><p>
- Debian をソースからビルドできるようにするという目標はほぼ完了し、よく進捗しています。Debian
-3.0の時代ではソースからビルドするのに問題が多数ありましたが、最近のリリースではましになってきています。
- </p></div></div><div class="chapter" title="第2章 pbuilder を利用する"><div class="titlepage"><div><div><h2 class="title"><a name="usingpbuilder"></a>第2章 pbuilder を利用する</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#creatingbase">1. base chroot イメージの tar 玉の作成</a></span></dt><dt><span class="sect1"><a href="#basechroot">2. base.tgz の更新</a></span></dt><dt><span class="sect1"><a href="#buildpackagechroot">3. base.tgz を利用してパッケージをビルドする</a></span></dt><dt><span class="sect1"><a href="#pdebuild">4. Debian Developer のタイピングを省略する、pdebuild</a></span></dt><dt><span class="sect1"><a href="#configfile">5. 設定ファイル</a></span></dt><dt><span class="sect1"><a href="#nonrootchroot">6. chroot 内部で root 以外でパッケージをビルドする</a></span></dt><dt><span class="sect1"><a href="#backporting">7. pbuilder をバックポートに活用する</a></span></dt><dt><span class="sect1"><a href="#massbuild">8. パッケージを大量にビルドする</a></span></dt><dt><span class="sect1"><a href="#autobackport">9. 自動バックポートスクリプト</a></span></dt><dt><span class="sect1"><a href="#autotesting">10. pbuilder を自動テストに利用する</a></span></dt><dt><span class="sect1"><a href="#altcompiler">11. pbuilder でその他のコンパイラでのビルドを試験する</a></span></dt></dl></div><p>
- 操作には、いくつかの簡単なコマンドがあります。<span class="command"><strong>pbuilder create</strong></span>、 <span class="command"><strong>pbuilder
-update</strong></span>、そして <span class="command"><strong>pbuilder build</strong></span>
-コマンドがよく使われます。ひとつづつ見ていきましょう。
- </p><div class="sect1" title="1. base chroot イメージの tar 玉の作成"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creatingbase"></a>1. base chroot イメージの tar 玉の作成</h2></div></div></div><p>
- <span class="command"><strong>pbuilder create</strong></span> 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 <span class="command"><strong><code class="option">--distribution</code></strong></span> command-line
-option.
- </p><p>
- <span class="command"><strong>debootstrap</strong></span> <sup>[<a name="idp472544" href="#ftn.idp472544" class="footnote">1</a>]</sup> is used
-to create the bare minimum Debian installation, and then build-essential
-packages are installed on top of the minimum installation using
-<span class="command"><strong>apt-get</strong></span> inside the chroot.
- </p><p>
- For fuller documentation of command-line options, see the pbuilder.8 manual
-page. Some configuration will be required for
-<code class="filename">/etc/pbuilderrc</code> for the mirror site <sup>[<a name="idp297792" href="#ftn.idp297792" class="footnote">2</a>]</sup> to use, and proxy configuration may be required to
-allow access through HTTP. See the pbuilderrc.5 manual page for details.
- </p></div><div class="sect1" title="2. base.tgz の更新"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="basechroot"></a>2. base.tgz の更新</h2></div></div></div><p><span class="command"><strong>pbuilder update</strong></span> will update the base.tgz. It will
-extract the chroot, invoke <span class="command"><strong>apt-get update</strong></span> and
-<span class="command"><strong>apt-get dist-upgrade</strong></span> inside the chroot, and then recreate
-the base.tgz (the base tar-ball).
- </p><p>
- It is possible to switch the distribution which the base.tgz is targeted at
-at this point. Specify <span class="command"><strong><code class="option">--distribution
-<em class="parameter"><code>sid</code></em></code>
-<code class="option">--override-config</code></strong></span> to change the distribution to
-sid. <sup>[<a name="idp304960" href="#ftn.idp304960" class="footnote">3</a>]</sup>
- </p><p>
- コマンドラインオプションの詳細なドキュメントについては、pbuilder.8 マニュアルを参照
- </p></div><div class="sect1" title="3. base.tgz を利用してパッケージをビルドする"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="buildpackagechroot"></a>3. base.tgz を利用してパッケージをビルドする</h2></div></div></div><p>
- To build a package inside the chroot, invoke <span class="command"><strong>pbuilder build
-<code class="option">whatever.dsc</code></strong></span>. <span class="command"><strong>pbuilder</strong></span> 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
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> command-line option.
- </p><p>
- The <span class="command"><strong><code class="option">--basetgz</code></strong></span> option can be used to
-specify which base.tgz to use.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> は base.tgz から新しい
-chroot イメージを展開します。（base.tgz は <span class="command"><strong>pbuilder create</strong></span> で作成され、
-<span class="command"><strong>pbuilder update</strong></span> で更新されます)。 chroot には Build-Depend関係のパッケージが
-debian/control を解析して <span class="command"><strong>apt-get</strong></span> を実行することで追加されます。
- </p><p>
- コマンドラインオプションの詳細なドキュメントについては、pbuilder.8 マニュアルを参照
- </p></div><div class="sect1" title="4. Debian Developer のタイピングを省略する、pdebuild"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pdebuild"></a>4. Debian Developer のタイピングを省略する、pdebuild</h2></div></div></div><p>
- <span class="command"><strong>pdebuild</strong></span>
-は、あらゆる操作の中でももっとも頻繁に行われるだろう作業を簡略化するためのラッパースクリプトです。Debian Developerは Debian
-パッケージのソースディレクトリで <span class="command"><strong>debuild</strong></span> コマンドをうつことでパッケージをビルドします。
-<span class="command"><strong>pdebuild</strong></span> は同様の操作をすることで、パッケージを chroot 内部でビルドし、
-現在のツリーが chroot 内部でもビルドすることを確認します。
- </p><p>
- <span class="command"><strong>pdebuild</strong></span> calls <span class="command"><strong>dpkg-source</strong></span> to build
-the source packages, and then invokes <span class="command"><strong>pbuilder</strong></span> on the
-resulting source package. However, unlike debuild, the resulting deb files
-will be found in the <span class="command"><strong><code class="option">--buildresult</code></strong></span>
-directory.
- </p><p>
- 詳細は pdebuild.1 マニュアルページを参照してください。
- </p><p>
- There is a slightly different mode of operation available in
-<span class="command"><strong>pdebuild</strong></span> since version 0.97. <span class="command"><strong>pdebuild</strong></span>
-usually runs <span class="command"><strong>debian/rules clean</strong></span> outside of the chroot;
-however, it is possible to change the behavior to run it inside the chroot
-with the <span class="command"><strong><code class="option">--use-pdebuild-internal</code></strong></span>. It
-will try to bind mount the working directory inside chroot, and run
-<span class="command"><strong>dpkg-buildpackage</strong></span> inside. It has the following
-characteristics, and is not yet the default mode of operation.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- ソースパッケージを作成する際に、Build-Depend を chroot 内部で満たします。
-(以前の <span class="command"><strong>pdebuild</strong></span> でできなかったよい点です)。
- </p></li><li class="listitem"><p>作業ディレクトリに chroot 内部から変更を加えられます。</p></li><li class="listitem"><p><span class="command"><strong>pdebuild</strong></span> でビルドできることは <span class="command"><strong>pbuilder</strong></span>
-で必ず動くということが保証されるわけではないです。</p></li><li class="listitem"><p>ソースパッケージを作るステップ自体が失敗した場合に、その chroot を利用するセッションは無駄に終わります（chroot
-の作成には時間がかかる、cowdancer 等で改善します。)</p></li><li class="listitem"><p>Does not work in the same manner as it used to; for example,
-<span class="command"><strong><code class="option">--buildresult</code></strong></span> does not have any effect.</p></li><li class="listitem"><p>chroot 内部でのビルドは chroot 外部での現在のユーザで実行される。
- </p></li></ul></div></div><div class="sect1" title="5. 設定ファイル"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configfile"></a>5. 設定ファイル</h2></div></div></div><p>
- 設定をすべてコマンドラインで指定することも可能です。しかし、入力を簡便にするために、設定ファイルを利用することもできます。
- </p><p>
- <code class="filename">/etc/pbuilderrc</code> と
-<code class="filename">${HOME}/.pbuilderrc</code> が <span class="command"><strong>pbuilder</strong></span>
-を実行すると読み込まれます。可能なオプションについては、 pbuilderrc.5 に解説されています。
- </p><p>
- It is useful to use <code class="option">--configfile</code> option to load up a preset
-configuration file when switching between configuration files for different
-distributions.
- </p><p>
- Please note <code class="filename">${HOME}/.pbuilderrc</code> 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.
- </p></div><div class="sect1" title="6. chroot 内部で root 以外でパッケージをビルドする"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonrootchroot"></a>6. chroot 内部で root 以外でパッケージをビルドする</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
-<span class="command"><strong>pbuilder</strong></span> can create a user which is only used inside
-<span class="command"><strong>pbuilder</strong></span> and use that user id when building, and use the
-<span class="command"><strong>fakeroot</strong></span> command when root privilege is required.
- </p><p>
- BUILDUSERID 設定オプションは既存のユーザIDと異なるIDに設定しておきましょう。そうするとパッケージが
-<span class="command"><strong>pbuilder</strong></span>
-内部でビルドしている際に、chroot 外部の環境に影響をあたえにくくなります。BUILDUSERNAME が設定されている場合、その名前を
-<span class="command"><strong>pbuilder</strong></span> は利用し、 chroot 内部でroot権限で動作する代わりに、fakeroot
-を利用してパッケージをビルドします。
- </p><p>
- fakeroot の方法を利用している場合でも、<span class="command"><strong>pbuilder</strong></span> は root 権限が必要な場面では root
-権限で稼働します。例えば、chroot内部にパッケージをインストールする時には<span class="command"><strong>pbuilder</strong></span> は root
-権限で稼働します。
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> を root 権限を必要としないで利用する方法については、 user-mode-linux
-の利用が必要です。 <a class="xref" href="#pbuilder-uml" title="第3章 user-mode-linux を pbuilder で利用する">3章<i>user-mode-linux を pbuilder で利用する</i></a> で説明しています。
- </p></div><div class="sect1" title="7. pbuilder をバックポートに活用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="backporting"></a>7. pbuilder をバックポートに活用する</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> は古いディストリビューションのchroot
-を作成し、そこでパッケージをビルドすることで、Debian
-の最新版のディストリビューションからソフトウエアをバックポートするのに利用することが可能です。いくつかの点を検討する必要があり、次の理由により全自動でバックポートすることは現実的では無く、手動での作業も必要になるでしょう:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>unstableのパッケージが unstable にしかないパッケージや、unstable
-にしかないバージョンのパッケージに依存している場合がある。つまり、stable では Build-Depends:
-を充足することができない(さらなるバックポートが必要になる)。</p></li><li class="listitem"><p>stable ディストリビューションには unstable で修正しているバグが含まれており、ワークアラウンドが必要になる。</p></li><li class="listitem"><p>unstable のパッケージが unstable 上であってもビルドしない場合がある。</p></li></ul></div></div><div class="sect1" title="8. パッケージを大量にビルドする"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="massbuild"></a>8. パッケージを大量にビルドする</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span>
-は操作がインタラクティブではないため、自動的に動かすことができる。<span class="command"><strong>pbuilder</strong></span>
-を複数のパッケージに関して、インタラクティブじゃないように実行することができます。それをするためのスクリプトはいくつか存在します。上川は2001年からそのようなスクリプトを実行し、
-<span class="command"><strong>pbuilder</strong></span> でビルドできない場合についてバグ報告をしていました。次のような問題が発見されました:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>依存関係を充足させるためのインストールは非インタラクティブに行われる必要がありますが、一部のパッケージはインタラクティブな操作がないとインストールできないくらいに壊れているものがあります（postgresqlなど）.</p></li><li class="listitem"><p>ライブラリパッケージに問題があったり、gcc/gcj/g++ に問題がある場合、また bison もそうですが、多くのビルド失敗が報告されます。
-(gcj-3.0 に "javac" がなくなったり、bison がより厳密になったり、など）
- </p></li><li class="listitem"><p>一部の人はビルド失敗の報告に敵対的なので注意しましょう。</p></li></ul></div><p>
- 2002年ころの<span class="command"><strong>pbuilder </strong></span>
-の実行により初期のバグは洗いだされました。しかし、このように移行に関連したDebian全体に影響するような問題はときどき発生します。回帰テストには価値があるのです。
- </p><p>
- 上川が利用したスクリプトは今 <span class="command"><strong>pbuilder</strong></span>
-ディストリビューションに含まれています。<code class="filename">/usr/share/doc/pbuilder/examples/pbuildd/</code>
-にあり、設定は、 <code class="filename">/etc/pbuilder/pbuildd-config.sh</code>
-が設定ファイルです。<span class="command"><strong>pbuilder</strong></span>
-になれている人であれば簡単に設定することができるはずです。しばらく実行されていたため、自分のシステムでも実行できるでしょう。ただ、まだ新しいので問題があれば
-Debian BTS に登録してください。
- </p><p>
- pbuildd の設定について気にしておくところがいくつかあります。
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>ビルドしないパッケージの一覧ファイル <code class="filename">./avoidlist</code> が存在する必要があります。 </p></li><li class="listitem"><p>自分のアーキテクチャ向けでないものを含めて、あらゆるものをビルドしようとします。</p></li><li class="listitem"><p>任意のビルドスクリプトを実行しているため、 root 権限で実行しないために、 <span class="command"><strong>pbuilder</strong></span>
-のfakeroot オプションを利用するのがよいでしょう。</p></li><li class="listitem"><p>すべてのビルドが有限時間で完了することが保証されているわけではありません、そのためタイムアウトを準備しておくことが必要かもしれません。そうしないとpbuilddは悪いビルドでずっと待ち状態になる可能性もあります。</p></li><li class="listitem"><p>
- 一部のパッケージは大量のディスク領域を必要とします、現時点では最大のパッケージであっても2GBくらいが十分なようです。もしそうでないという状況を発見した場合はこの文書のメンテナに連絡してください。
- </p></li></ul></div></div><div class="sect1" title="9. 自動バックポートスクリプト"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autobackport"></a>9. 自動バックポートスクリプト</h2></div></div></div><p>
- 一部の人は <span class="command"><strong>pbuilder</strong></span> を一部のパッケージを自動的に stable
-ディストリビューションにバックポートするために利用しています。
- </p><p>
- どのように実際にやっているのか情報をください、フィードバックや情報や例を歓迎します。
- </p></div><div class="sect1" title="10. pbuilder を自動テストに利用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="autotesting"></a>10. pbuilder を自動テストに利用する</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> は、自動的なテストのために利用することができます。フックを配置することができ、そのフックは
-chroot 内部にパッケージをインストールしたり実行したりその他のいろいろなことを実行することができます。実行可能なテストとアイデアは次です:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Automatic install-remove-install-purge-upgrade-remove-upgrade-purge
-test-suite (distributed as an example, <code class="filename">B91dpkg-i</code>), or
-just check that everything installs somewhat
-(<code class="filename">execute_installtest.sh</code>).</p></li><li class="listitem"><p>自動的にlintianを実行する (例として
-<code class="filename">/usr/share/doc/pbuilder/examples/B90lintian</code>が配布されている)。</p></li><li class="listitem"><p>自動的にパッケージの debian-test を行う? debian-test パッケージは Debian から削除されました。
-<span class="command"><strong>pbuilder</strong></span> での代替は debian/pbuilder-test
-ディレクトリにあります。B92test-pkgスクリプトで実装されています。</p></li></ul></div><p>
- To use B92test-pkg script, first, add it to your hook directory.
-<sup>[<a name="idp5771824" href="#ftn.idp5771824" class="footnote">4</a>]</sup>. The test files are shell scripts
-placed in <code class="filename">debian/pbuilder-test/NN_name</code> (where NN is a
-number) following run-parts standard<sup>[<a name="idp5773872" href="#ftn.idp5773872" class="footnote">5</a>]</sup>
-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.
- </p><p>
- Example scripts for use with pbuilder-test can be found in
-<code class="filename">/usr/share/doc/pbuilder/examples/pbuilder-test</code>.
- </p></div><div class="sect1" title="11. pbuilder でその他のコンパイラでのビルドを試験する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altcompiler"></a>11. pbuilder でその他のコンパイラでのビルドを試験する</h2></div></div></div><p>
- Most packages are compiled with <span class="command"><strong>gcc</strong></span> or
-<span class="command"><strong>g++</strong></span> 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 <span class="command"><strong>gcc-3.2</strong></span>
-for gcc compiler version 3.2. It was therefore possible to try compiling
-packages against different compiler versions.
-<span class="command"><strong>pentium-builder</strong></span> 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
-<span class="command"><strong>pentium-builder</strong></span> in <span class="command"><strong>pbuilder</strong></span>, it is
-possible to set up the following in the configuration: </p><pre class="screen">
-EXTRAPACKAGES="pentium-builder gcc-3.2 g++-3.2"
-export DEBIAN_BUILDARCH=athlon
-export DEBIAN_BUILDGCCVER=3.2</pre><p>
- </p><p>
- It will instruct <span class="command"><strong>pbuilder</strong></span> to install the
-<span class="command"><strong>pentium-builder</strong></span> package and also the GCC 3.2 compiler
-packages inside the chroot, and set the environment variables required for
-<span class="command"><strong>pentium-builder</strong></span> to function.
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp472544" href="#idp472544" class="para">1</a>] </sup>debootstrap か cdebootstrap か選択することができます</p></div><div class="footnote"><p><sup>[<a id="ftn.idp297792" href="#idp297792" class="para">2</a>] </sup>
- 公開ミラーに多数のアクセス負荷をかけないため、ミラーはローカルミラーであることが望ましいです。apt-proxy などのツールの活用を推奨します。
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp304960" href="#idp304960" class="para">3</a>] </sup>アップグレードしかサポートされていません。Debianはダウングレードをサポートしていません（現時点では？）。</p></div><div class="footnote"><p><sup>[<a id="ftn.idp5771824" href="#idp5771824" class="para">4</a>] </sup><span class="command"><strong>--hookdir /usr/share/doc/pbuilder/examples</strong></span>
-コマンドラインオプションを指定することですべてのサンプルフックを利用することが可能です。</p></div><div class="footnote"><p><sup>[<a id="ftn.idp5773872" href="#idp5773872" class="para">5</a>] </sup> run-parts(8) を参照してください。例えば、ファイル名に '.' はふくめられません。
- </p></div></div></div><div class="chapter" title="第3章 user-mode-linux を pbuilder で利用する"><div class="titlepage"><div><div><h2 class="title"><a name="pbuilder-uml"></a>第3章 user-mode-linux を pbuilder で利用する</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#user-mode-linux-config">1. user-mode-linux の設定</a></span></dt><dt><span class="sect1"><a href="#rootstrap">2. rootstrap の設定</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlconfig">3. pbuilder-uml の設定</a></span></dt><dt><span class="sect1"><a href="#consideruml">4. pbuilder-user-mode-linuxを実行する場合の検討項目</a></span></dt><dt><span class="sect1"><a href="#paralleluml">5. pbuilder-user-mode-linux を複数同時に実行させる</a></span></dt><dt><span class="sect1"><a href="#pbuilderumlwrap">6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual
-machine</a></span></dt></dl></div><p>
- It is possible to use user-mode-linux by invoking
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> instead of
-<span class="command"><strong>pbuilder</strong></span>. <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-doesn't require root privileges, and it uses the copy-on-write (COW) disk
-access method of <span class="command"><strong>User-mode-linux</strong></span> which typically makes it
-much faster than the traditional <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- <span class="command"><strong>User-mode-linux</strong></span> is a somewhat less proven platform than
-the standard Unix tools which <span class="command"><strong>pbuilder</strong></span> relies on
-(<span class="command"><strong>chroot</strong></span>, <span class="command"><strong>tar</strong></span>, and
-<span class="command"><strong>gzip</strong></span>) but mature enough to support
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> since its version 0.59. And
-since then, <span class="command"><strong>pbuilder-user-mode-linux</strong></span> has seen a rapid
-evolution.
- </p><p>
- The configuration of <span class="command"><strong>pbuilder-user-mode-linux</strong></span> goes in
-three steps:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>user-mode-linux の設定</p></li><li class="listitem"><p>rootstrap の設定</p></li><li class="listitem"><p>pbuilder-uml の設定</p></li></ul></div><p>
- </p><div class="sect1" title="1. user-mode-linux の設定"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="user-mode-linux-config"></a>1. user-mode-linux の設定</h2></div></div></div><p>
- 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
-<span class="command"><strong>rootstrap</strong></span> or
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>. For details, read
-<code class="filename">/usr/share/doc/uml-utilities/README.Debian</code> and the
-<span class="command"><strong>user-mode-linux</strong></span> documentation. (It's in a separate
-package, user-mode-linux-doc.)
- </p><p>
- <span class="command"><strong>user-mode-linux</strong></span> requires the user to be in the uml-net
-group in order to configure the network unless you are using slirp.
- </p><p>
- 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.
- </p></div><div class="sect1" title="2. rootstrap の設定"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="rootstrap"></a>2. rootstrap の設定</h2></div></div></div><p>
- <span class="command"><strong>rootstrap</strong></span> is a wrapper around debootstrap. It creates a
-Debian disk image for use with UML. To configure rootstrap, there are
-several requirements.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>rootstrap パッケージをインストールします。</p></li><li class="listitem"><p>
- TUN/TAP only: add the user to the uml-net group to allow access to the
-network </p><pre class="screen">adduser dancer uml-net</pre><p>
- </p></li><li class="listitem"><p>TUN/TAPを利用している場合: カーネルが TUN/TAP
-インタフェースをサポートしていることを確認してください。必要であればカーネルをリビルドしてください。
- </p></li><li class="listitem"><p>Set up <code class="filename">/etc/rootstrap/rootstrap.conf</code>. For example, if
-the current host is 192.168.1.2, changing following entries to something
-like this seems to work. </p><pre class="screen">
-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</pre><p> Some
-experimentation with configuration and running <span class="command"><strong>rootstrap
-~/test.uml</strong></span> to actually test it would be handy.
- </p><p>
- Using slirp requires less configuration. The default configuration comes
-with a working example.
- </p></li></ul></div></div><div class="sect1" title="3. pbuilder-uml の設定"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlconfig"></a>3. pbuilder-uml の設定</h2></div></div></div><p>
- 以下の設定が必要です:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>pbuilder-uml をインストールする</p></li><li class="listitem"><p>
- Set up the configuration file
-<code class="filename">/etc/pbuilder/pbuilder-uml.conf</code> in the following
-manner. It will be different for slirp. </p><pre class="screen">
-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"</pre><p>
-Also, it needs to match the rootstrap configuration.
- </p></li><li class="listitem"><p>
- Make sure BUILDPLACE is writable by the user. Change BUILDPLACE in the
-configuration file to a place where the user has access.
- </p></li><li class="listitem"><p>Run <span class="command"><strong>pbuilder-user-mode-linux <code class="option">create --distribution
-sid</code></strong></span> to create the image.</p></li><li class="listitem"><p>Try running <span class="command"><strong>pbuilder-user-mode-linux build</strong></span>.</p></li></ul></div><p>
- </p></div><div class="sect1" title="4. pbuilder-user-mode-linuxを実行する場合の検討項目"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="consideruml"></a>4. pbuilder-user-mode-linuxを実行する場合の検討項目</h2></div></div></div><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> emulates most of
-<span class="command"><strong>pbuilder</strong></span>, but there are some differences.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> does not support all options of
-<span class="command"><strong>pbuilder</strong></span> properly yet. This is a problem, and will be
-addressed as specific areas are discovered.
- </p></li><li class="listitem"><p>
- /tmp is handled differently inside
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>. In
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>, <code class="filename">/tmp</code> is
-mounted as tmpfs inside UML, so accessing files under
-<code class="filename">/tmp</code> from outside user-mode-linux does not work. It
-affects options like <span class="command"><strong><code class="option">--configfile</code></strong></span>, and
-when trying to build packages placed under <code class="filename">/tmp</code>.
- </p></li></ul></div></div><div class="sect1" title="5. pbuilder-user-mode-linux を複数同時に実行させる"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paralleluml"></a>5. pbuilder-user-mode-linux を複数同時に実行させる</h2></div></div></div><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span>
-を同一システム上で同時に複数実行させるにはいくつか注意するべき点があります。
-
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The create and update methods must not be run when a build is in progress,
-or the COW file will be invalidated.</p></li><li class="listitem"><p>
- 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
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> several times will result in
-failure to access the network. But something like the following will work:
-</p><pre class="screen">
-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</pre><p> When using slirp, this problem does not
-exist.
- </p></li></ul></div></div><div class="sect1" title="6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual machine"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderumlwrap"></a>6. Using pbuilder-user-mode-linux as a wrapper script to start up a virtual
-machine</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>pbuilder-user-mode-linux</strong></span> for other
-uses than just building Debian packages. <span class="command"><strong>pbuilder-user-mode-linux
-<code class="option">login</code></strong></span> will let a user use a shell inside the
-user-mode-linux <span class="command"><strong>pbuilder</strong></span> base image, and
-<span class="command"><strong>pbuilder-user-mode-linux <code class="option">execute</code></strong></span> will
-allow the user to execute a script inside the image.
- </p><p>
- 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.
- </p><p>
- Note that it is not possible to use a script from <code class="filename">/tmp</code>
-due to the way <span class="command"><strong>pbuilder-user-mode-linux</strong></span> mounts a tmpfs at
-<code class="filename">/tmp</code>.
- </p><p>
- The following example script may be useful in starting a sshd inside
-user-mode-linux.
- </p><pre class="screen">
-#!/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</pre></div></div><div class="chapter" title="第4章 FAQ （よくある質問）"><div class="titlepage"><div><div><h2 class="title"><a name="faq"></a>第4章 FAQ （よくある質問） </h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#pbuildercreatefail">1. pbuilder create が失敗する</a></span></dt><dt><span class="sect1"><a href="#bindmountlimits">2. bind mount できないディレクトリ</a></span></dt><dt><span class="sect1"><a href="#shellafterfail">3. ビルド失敗の調査のために pbuilder 環境にログインする</a></span></dt><dt><span class="sect1"><a href="#modifyupdate">4. 環境を変更するために pbuilder 環境にログインする</a></span></dt><dt><span class="sect1"><a href="#BUILDRESULTUID">5. BUILDRESULTUID を sudo のセッションに追加する</a></span></dt><dt><span class="sect1"><a href="#tmpdir">6. $TMPDIRの使い方について</a></span></dt><dt><span class="sect1"><a href="#DISTRIBUTIONSWITCH">7. Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific
-distribution</a></span></dt><dt><span class="sect1"><a href="#ENVVARDISTRIBUTIONSWITCH">8. Using environmental variables for running <span class="command"><strong>pbuilder</strong></span> for
-specific distribution
- </a></span></dt><dt><span class="sect1"><a href="#usingspecialaptsources">9. Using special apt sources lists, and local packages</a></span></dt><dt><span class="sect1"><a href="#apt-getupdateonbuild-depend">10. How to get pbuilder to run apt-get update before trying to satisfy
-build-dependency</a></span></dt><dt><span class="sect1"><a href="#bashprompt">11. pbuilder login で bash のプロンプトを変更する</a></span></dt><dt><span class="sect1"><a href="#chrootmemo">12. Creating a chroot reminder</a></span></dt><dt><span class="sect1"><a href="#packagecachearchives">13. Using /var/cache/apt/archives for the package cache</a></span></dt><dt><span class="sect1"><a href="#stablebackport">14. pbuilder back ported to stable Debian releases</a></span></dt><dt><span class="sect1"><a href="#LOGNAME">15. Warning about LOGNAME not being defined</a></span></dt><dt><span class="sect1"><a href="#nobuildconflictessential">16. Cannot Build-conflict against an essential package</a></span></dt><dt><span class="sect1"><a href="#lninvalidcrossdevicelink">17. Avoiding the "ln: Invalid cross-device link" message</a></span></dt><dt><span class="sect1"><a href="#fakechroot">18. Using fakechroot</a></span></dt><dt><span class="sect1"><a href="#debconfinsidepbuilder">19. Using debconf inside pbuilder sessions</a></span></dt><dt><span class="sect1"><a href="#nodev">20. nodev mount options hinder pbuilder activity</a></span></dt><dt><span class="sect1"><a href="#faqslowpbuilder">21. pbuilder が遅い</a></span></dt><dt><span class="sect1"><a href="#sponsor">22. Using pdebuild to sponsor package</a></span></dt><dt><span class="sect1"><a href="#sourcechanges">23. Why is there a source.changes file in ../?</a></span></dt><dt><span class="sect1"><a href="#amd64i386">24. amd64 and i386-mode</a></span></dt><dt><span class="sect1"><a href="#tmpfsforpbuilder">25. Using tmpfs for buildplace</a></span></dt><dt><span class="sect1"><a href="#idp5978160">26. svn-buildpackage を pbuilder で利用する</a></span></dt></dl></div><p>
- Here, known problems and frequently asked questions are documented. This
-portion was initially available in README.Debian file, but moved here.
- </p><div class="sect1" title="1. pbuilder create が失敗する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuildercreatefail"></a>1. pbuilder create が失敗する</h2></div></div></div><p>
- It often happens that <span class="command"><strong>pbuilder</strong></span> cannot create the latest
-chroot. Try upgrading <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- There are people who occasionally back port debootstrap to stable versions;
-hunt for them.
- </p><p>
- When there are errors with the debootstrap phase, the debootstrap script
-needs to be fixed. <span class="command"><strong>pbuilder</strong></span> does not provide a way to
-work around debootstrap.
- </p></div><div class="sect1" title="2. bind mount できないディレクトリ"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bindmountlimits"></a>2. bind mount できないディレクトリ</h2></div></div></div><p>
- Because of the way <span class="command"><strong>pbuilder</strong></span> works, there are several
-directories which cannot be bind-mounted when running
-<span class="command"><strong>pbuilder</strong></span>. The directories include
-<code class="filename">/tmp</code>, <code class="filename">/var/cache/pbuilder</code>, and
-system directories such as <code class="filename">/etc</code> and
-<code class="filename">/usr</code>. The recommendation is to use directories under
-the user's home directory for bind-mounts.
- </p></div><div class="sect1" title="3. ビルド失敗の調査のために pbuilder 環境にログインする"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="shellafterfail"></a>3. ビルド失敗の調査のために pbuilder 環境にログインする</h2></div></div></div><p>
- It is possible to invoke a shell session after a build failure. Example
-hook scripts are provided as <code class="filename">C10shell</code> and
-<code class="filename">C11screen</code> scripts. C10shell script will start bash
-inside chroot, and C11screen script will start GNU screen inside the chroot.
- </p></div><div class="sect1" title="4. 環境を変更するために pbuilder 環境にログインする"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modifyupdate"></a>4. 環境を変更するために pbuilder 環境にログインする</h2></div></div></div><p>
- It is sometimes necessary to modify the chroot environment.
-<span class="command"><strong>login</strong></span> will remove the contents of the chroot after
-logout. It is possible to invoke a shell using hook scripts.
-<span class="command"><strong>pbuilder update</strong></span> executes 'E' scripts, and a sample for
-invoking a shell is provided as <code class="filename">C10shell</code>.
- </p><pre class="screen">
-$ mkdir ~/loginhooks
-$ cp C10shell ~/loginhooks/E10shell
-$ sudo pbuilder update --hookdir ~/loginhooks/E10shell</pre><p>
- It is also possible to add <code class="option">--save-after-exec</code> and/or
-<code class="option">--save-after-login</code> options to the <span class="command"><strong>pbuilder
-login</strong></span> session to accomplish the goal. It is possible to add the
-<code class="option">--uml-login-nocow</code> option to
-<span class="command"><strong>pbuilder-user-mode-linux <code class="option">login</code></strong></span> session
-as well.
- </p></div><div class="sect1" title="5. BUILDRESULTUID を sudo のセッションに追加する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="BUILDRESULTUID"></a>5. BUILDRESULTUID を sudo のセッションに追加する</h2></div></div></div><p>
- It is possible to set </p><pre class="screen">BUILDRESULTUID=$SUDO_UID</pre><p> in pbuilderrc to
-set the proper BUILDRESULTUID when using <span class="command"><strong>sudo</strong></span>.
- </p></div><div class="sect1" title="6. $TMPDIRの使い方について"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpdir"></a>6. $TMPDIRの使い方について</h2></div></div></div><p>
- If you are setting $TMPDIR to an unusual value, of other than
-<code class="filename">/tmp</code>, you will find that some errors may occur inside
-the chroot, such as <span class="command"><strong>dpkg-source</strong></span> failing.
- </p><p>There are two options, you may install a hook to create that directory, or
-set </p><pre class="screen">export TMPDIR=/tmp</pre><p> in pbuilderrc. Take your pick.
- </p><p>
- An example script is provided as <code class="filename">examples/D10tmp</code> with
-<span class="command"><strong>pbuilder</strong></span>.
- </p></div><div class="sect1" title="7. Creating a shortcut for running pbuilder with a specific distribution"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="DISTRIBUTIONSWITCH"></a>7. Creating a shortcut for running <span class="command"><strong>pbuilder</strong></span> with a specific
-distribution</h2></div></div></div><p>
- When working with multiple chroots, it would be nice to work with scripts
-that reduce the amount of typing. An example script
-<code class="filename">pbuilder-distribution.sh</code> is provided as an example.
-Invoking the script as <code class="filename">pbuilder-squeeze</code> will invoke
-<span class="command"><strong>pbuilder</strong></span> with a squeeze chroot.
- </p></div><div class="sect1" title="8. Using environmental variables for running pbuilder for specific distribution"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ENVVARDISTRIBUTIONSWITCH"></a>8. Using environmental variables for running <span class="command"><strong>pbuilder</strong></span> for
-specific distribution
- </h2></div></div></div><p> This section<sup>[<a name="idp5885632" href="#ftn.idp5885632" class="footnote">6</a>]</sup> describes briefly a way to
-setup and use multiple pbuilder setups by creating a pbuilderrc
-configuration in your home path (<code class="filename">$HOME/.pbuilderrc</code>)
-and using the variable "DIST" when running pbuilder or pdebuild.
-</p><p> First, setup <code class="filename">$HOME/.pbuilderrc</code> to look like:</p><p>
- </p><pre class="screen">
-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
-</pre><p>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).
- </p><p>Here's some examples on running pbuilder or pdebuild:
-</p><pre class="screen">
-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
-</pre></div><div class="sect1" title="9. Using special apt sources lists, and local packages"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="usingspecialaptsources"></a>9. Using special apt sources lists, and local packages</h2></div></div></div><p>
- If you have some very specialized requirements on your apt setup inside
-<span class="command"><strong>pbuilder</strong></span>, it is possible to specify that through the
-<span class="command"><strong><code class="option">--othermirror</code></strong></span> option. Try something
-like: <span class="command"><strong><code class="option">--othermirror "deb http://local/mirror stable
-main|deb-src http://local/source/repository ./"</code></strong></span>
- </p><p>
- To use the local file system instead of HTTP, it is necessary to do
-bind-mounting. <span class="command"><strong><code class="option">--bindmounts</code></strong></span> is a
-command-line option useful for such cases.
- </p><p>
- 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.
- </p><p>
- </p><pre class="screen">BINDMOUNTS="/var/cache/pbuilder/result"</pre><p>
- </p><p>
- Then, add the following hook
- </p><p>
- </p><pre class="screen">
-# 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</pre><p>
- </p><p>
- This way, you can use <code class="filename">deb
-file:/var/cache/pbuilder/result</code>
- </p><p>
-
-To add new apt-key inside chroot:
-
- </p><p>
- </p><pre class="screen">
-sudo pbuilder --login --save-after-login
-# apt-key add - <<EOF
-...public key goes here...
-EOF
-# logout
-</pre></div><div class="sect1" title="10. How to get pbuilder to run apt-get update before trying to satisfy build-dependency"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="apt-getupdateonbuild-depend"></a>10. How to get pbuilder to run apt-get update before trying to satisfy
-build-dependency</h2></div></div></div><p>
- You can use hook scripts for this. D scripts are run before satisfying
-build-dependency.
- </p><p>
- <a class="ulink" href="http://lists.debian.org/debian-devel/2006/05/msg00550.html" target="_top">
-This snippet comes from Ondrej Sury. </a>
- </p></div><div class="sect1" title="11. pbuilder login で bash のプロンプトを変更する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bashprompt"></a>11. pbuilder login で bash のプロンプトを変更する</h2></div></div></div><p>
- To make distinguishing bash prompts inside <span class="command"><strong>pbuilder</strong></span>
-easier, it is possible to set environment variables such as PS1 inside
-<code class="filename">pbuilderrc</code>
- </p><p>
- 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,<sup>[<a name="idp5909904" href="#ftn.idp5909904" class="footnote">7</a>]</sup> setting PS1 in pbuilderrc worked.
- </p><p>example of debian_chroot</p><pre class="screen">
- export debian_chroot="pbuild$$"</pre><p>example of PS1</p><pre class="screen">
- export PS1="pbuild chroot 32165 # "</pre></div><div class="sect1" title="12. Creating a chroot reminder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chrootmemo"></a>12. Creating a chroot reminder</h2></div></div></div><p>
- 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 <code class="filename">examples/F90chrootmemo</code> hook script. It will
-create a file called <code class="filename">/CHROOT</code> inside your chroot.
- </p></div><div class="sect1" title="13. Using /var/cache/apt/archives for the package cache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="packagecachearchives"></a>13. Using /var/cache/apt/archives for the package cache</h2></div></div></div><p>
- For the help of low-bandwidth systems, it is possible to use
-<code class="filename">/var/cache/apt/archives</code> as the package cache. Just
-specify it instead of the default
-<code class="filename">/var/cache/pbuilder/aptcache</code>.
- </p><p>
- It is however not possible to do so currently with the user-mode-linux
-version of <span class="command"><strong>pbuilder</strong></span>, because
-<code class="filename">/var/cache/apt/archives</code> is usually only writable by
-root.
- </p><p>
- Use of dedicated tools such as apt-proxy is recommended, since caching of
-packages would benefit the system outside the scope of
-<span class="command"><strong>pbuilder</strong></span>.
- </p></div><div class="sect1" title="14. pbuilder back ported to stable Debian releases"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="stablebackport"></a>14. pbuilder back ported to stable Debian releases</h2></div></div></div><p>
- Currently stable back port of pbuilder is available at backports.org.
- </p></div><div class="sect1" title="15. Warning about LOGNAME not being defined"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="LOGNAME"></a>15. Warning about LOGNAME not being defined</h2></div></div></div><p>
- You might see a lot of warning messages when running
-<span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- </p><pre class="screen">
- dpkg-genchanges: warning: no utmp entry available and LOGNAME not defined; using uid of process (1234)</pre><p>
- </p><p>
- 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 <span class="command"><strong>chroot</strong></span>. For example, dpkg
-requires getpwnam to succeed inside chroot, which means LOGNAME and the
-related user information have to be set up inside chroot.
- </p></div><div class="sect1" title="16. Cannot Build-conflict against an essential package"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nobuildconflictessential"></a>16. Cannot Build-conflict against an essential package</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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.
- </p></div><div class="sect1" title='17. Avoiding the "ln: Invalid cross-device link" message'><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lninvalidcrossdevicelink"></a>17. Avoiding the "ln: Invalid cross-device link" message</h2></div></div></div><p>
- By default, <span class="command"><strong>pbuilder</strong></span> uses hard links to manage the
-<span class="command"><strong>pbuilder</strong></span> 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 </p><pre class="screen">APTCACHEHARDLINK=no</pre><p> in
-your pbuilderrc file. Note that packages in <span class="command"><strong>APTCACHE</strong></span> will
-be copied into chroot local cache, so plan for enough space on
-<span class="command"><strong>BUILDPLACE</strong></span> device.
- </p></div><div class="sect1" title="18. Using fakechroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="fakechroot"></a>18. Using fakechroot</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>fakechroot</strong></span> instead of being root to
-run <span class="command"><strong>pbuilder</strong></span>; however, several things make this
-impractical. <span class="command"><strong>fakechroot</strong></span> overrides library loads and
-tries to override default libc functions when providing the functionality of
-virtual <span class="command"><strong>chroot</strong></span>. However, some binaries do no use libc to
-function, or override the overriding provided by
-<span class="command"><strong>fakechroot</strong></span>. One example is <span class="command"><strong>ldd</strong></span>.
-Inside <span class="command"><strong>fakechroot</strong></span>, <span class="command"><strong>ldd</strong></span> will check the
-library dependency outside of the chroot, which is not the expected
-behavior.
- </p><p>
- To work around the problem, debootstrap has a <code class="option">--variant
-fakechroot</code> option. Use that, so that ldd and ldconfig are
-overridden.
- </p><p>
- Make sure you have set your LD_PRELOAD path correctly, as described in the
-fakechroot manpage.
- </p></div><div class="sect1" title="19. Using debconf inside pbuilder sessions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="debconfinsidepbuilder"></a>19. Using debconf inside pbuilder sessions</h2></div></div></div><p>
- To use debconf inside <span class="command"><strong>pbuilder</strong></span>, setting DEBIAN_FRONTEND
-to <span class="quote">「<span class="quote">readline</span>」</span> in <code class="filename">pbuilderrc</code> should work.
-Setting it to <span class="quote">「<span class="quote">dialog</span>」</span> should also work, but make sure whiptail
-or dialog is installed inside the chroot.
- </p></div><div class="sect1" title="20. nodev mount options hinder pbuilder activity"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nodev"></a>20. nodev mount options hinder pbuilder activity</h2></div></div></div><p>
- If you see messages such as this when building a chroot, you are mounting
-the file system with the nodev option.
- </p><pre class="screen">
- /var/lib/dpkg/info/base-files.postinst: /dev/null: Permission denied</pre><p>
- 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 <code class="filename">/var/cache/pbuilder</code> or $BUILDPLACE.
- </p><p>
- This is not a problem when using <span class="command"><strong>user-mode-linux</strong></span>.
- </p><p>
- See <a class="ulink" href="http://bugs.debian.org/316135" target="_top"> 316135 </a> for example.
- </p></div><div class="sect1" title="21. pbuilder が遅い"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="faqslowpbuilder"></a>21. pbuilder が遅い</h2></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> is often slow. The slowest part of
-<span class="command"><strong>pbuilder</strong></span> is extracting the tar.gz every time
-<span class="command"><strong>pbuilder</strong></span> is invoked. That can be avoided by using
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span>.
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> uses COW file system, and thus
-does not need to clean up and recreate the root file system.
- </p><p>
- <span class="command"><strong>pbuilder-user-mode-linux</strong></span> is slower in executing the
-actual build system, due to the usual <span class="command"><strong>user-mode-linux</strong></span>
-overhead for system calls. It is more friendly to the hard drive.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> with cowdancer is also an alternative that
-improves speed of pbuilder startup.
- </p></div><div class="sect1" title="22. Using pdebuild to sponsor package"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sponsor"></a>22. Using pdebuild to sponsor package</h2></div></div></div><p>
- To sign a package marking for sponsorship, it is possible to
-use<span class="command"><strong><code class="option"> --auto-debsign</code></strong></span> and
-<span class="command"><strong><code class="option">--debsign-k</code></strong></span> options of
-<span class="command"><strong>pdebuild</strong></span>.
- </p><pre class="screen">
- <span class="command"><strong>pdebuild <code class="option">--auto-debsign </code> <code class="option">--debsign-k </code><em class="parameter"><code>XXXXXXXX</code></em></strong></span></pre></div><div class="sect1" title="23. Why is there a source.changes file in ../?"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sourcechanges"></a>23. Why is there a source.changes file in ../?</h2></div></div></div><p>
- When running <span class="command"><strong>pdebuild</strong></span>, <span class="command"><strong>pbuilder</strong></span> will
-run dpkg-buildpackage to create a Debian source package to pass it on to
-<span class="command"><strong>pbuilder</strong></span>. 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.
- </p><p>
- This behavior is different when running through
-<code class="option">--use-pdebuild-internal</code>
- </p></div><div class="sect1" title="24. amd64 and i386-mode"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="amd64i386"></a>24. amd64 and i386-mode</h2></div></div></div><p>
- amd64 architectures are capable of running binaries in i386 mode. It is
-possible to use <span class="command"><strong>pbuilder</strong></span> to run packages, using
-<span class="command"><strong>linux32</strong></span> and <span class="command"><strong>debootstrap
-<code class="option">--arch</code></strong></span> option. Specifically, a command-line
-option like the following will work.
- </p><p>
- </p><pre class="screen">
-<span class="command"><strong>pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \
- --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian</strong></span>
-<span class="command"><strong>linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz</strong></span></pre><p>
- </p></div><div class="sect1" title="25. Using tmpfs for buildplace"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tmpfsforpbuilder"></a>25. Using tmpfs for buildplace</h2></div></div></div><p>
- To improve speed of operation, it is possible to use tmpfs for pbuilder
-build location. Mount tmpfs to
-<code class="filename">/var/cache/pbuilder/build</code>, and set </p><pre class="screen">APTCACHEHARDLINK=no</pre><p>.
- </p></div><div class="sect1" title="26. svn-buildpackage を pbuilder で利用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5978160"></a>26. svn-buildpackage を pbuilder で利用する</h2></div></div></div><p>
- pdebuild command can be used with svn-buildpackage --svn-builder
-command-line option. <sup>[<a name="idp5979520" href="#ftn.idp5979520" class="footnote">8</a>]</sup>
- </p><pre class="screen">
-alias svn-cowbuilder="svn-buildpackage --svn-builder='pdebuild --pbuilder cowbuilder"</pre></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.idp5885632" href="#idp5885632" class="para">6</a>] </sup>This part of the documentation contributed by Andres Mejia</p><p>
- This example was taken from a wiki (<a class="ulink" href="https://wiki.ubuntu.com/PbuilderHowto" target="_top">https://wiki.ubuntu.com/PbuilderHowto</a>).
- </p></div><div class="footnote"><p><sup>[<a id="ftn.idp5909904" href="#idp5909904" class="para">7</a>] </sup>Debian 3.0 以前のbash </p></div><div class="footnote"><p><sup>[<a id="ftn.idp5979520" href="#idp5979520" class="para">8</a>] </sup><a class="ulink" href="http://upsilon.cc/~zack/blog/posts/2007/09/svn-cowbuilder/" target="_top">
-Zack has posted an example on his blog. </a></p></div></div></div><div class="chapter" title="第5章 Troubleshooting and development"><div class="titlepage"><div><div><h2 class="title"><a name="develanddebug"></a>第5章 Troubleshooting and development</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#bugreport">1. Reporting bugs </a></span></dt><dt><span class="sect1"><a href="#mailinglist">2. Mailing list</a></span></dt><dt><span class="sect1"><a href="#IRCchannel">3. IRC Channel</a></span></dt><dt><span class="sect1"><a href="#development">4. Information for pbuilder developers</a></span></dt></dl></div><div class="sect1" title="1. Reporting bugs"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreport"></a>1. Reporting bugs </h2></div></div></div><p>
- To report bugs, it would be important to have a log of what's going wrong.
-Most of the time, adding a <span class="command"><strong><code class="option">--debug</code></strong></span>
-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.
- </p></div><div class="sect1" title="2. Mailing list"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mailinglist"></a>2. Mailing list</h2></div></div></div><p>
- There is a mailing list for <span class="command"><strong>pbuilder</strong></span> on alioth
-(pbuilder-maint at lists.alioth.debian.org). You can subscribe through the
-alioth web interface. <a class="ulink" href="http://alioth.debian.org/mail/?group_id=30778" target="_top">
-http://alioth.debian.org/mail/?group_id=30778</a>.
- </p></div><div class="sect1" title="3. IRC Channel"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="IRCchannel"></a>3. IRC Channel</h2></div></div></div><p>
- 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.
- </p></div><div class="sect1" title="4. Information for pbuilder developers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="development"></a>4. Information for pbuilder developers</h2></div></div></div><p>
- This section tries to document current development practices and how things
-generally operate in development.
- </p><p>
- <span class="command"><strong>pbuilder</strong></span> is co-maintained with resources provided by
-Alioth. There is an Alioth project page at <a class="ulink" href="http://alioth.debian.org/projects/pbuilder" target="_top">
-http://alioth.debian.org/projects/pbuilder</a>. Home page is also
-available, at <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top">
-http://alioth.debian.org/projects/pbuilder</a> which shows this text.
-git repository is available through http, git, or (if you have an account on
-alioth, ) ssh.
- </p><pre class="screen">
-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</pre><p>
- 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.
- </p><p>
- Test-suites are available in <code class="filename">./testsuite/</code> directory.
-Changes are expected not to break the test-suites.
-<code class="filename">./run-test.sh</code> is a basic test-suite, which puts a
-summary in <code class="filename">run-test.log</code>, and
-<code class="filename">run-test-cdebootstrap.log</code>.
-<code class="filename">./run-test-regression.sh</code> is a regression test-suite,
-which puts the result in <code class="filename">run-test-regression.log</code>.
-Currently, run-test.sh is ran automatically daily to ensure that pbuilder is
-working.
- </p><div class="table"><a name="dirtestsuites"></a><p class="title"><b>表5.1 テストスイートのディレクトリ構造</b></p><div class="table-contents"><table summary="テストスイートのディレクトリ構造" border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">ディレクトリ</th><th align="left">意味</th></tr></thead><tbody><tr><td align="left"><code class="filename">./testsuite/</code></td><td align="left">テストスイートへのディレクトリ</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.sh</code></td><td align="left">Daily regression test to test against Debian Archive changes breaking
-pbuilder.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-test.log</code></td><td align="left">A summary of testsuite</td></tr><tr><td align="left"><code class="filename">./testsuite/normal/</code></td><td align="left">Directory for testsuite results of running pbuilder with debootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/cdebootstrap/</code></td><td align="left">Directory for testsuite results of running pbuilder with cdebootstrap</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.sh</code></td><td align="left">Regression testsuite, ran every time change is made to pbuilder to make sure
-there is no regression.</td></tr><tr><td align="left"><code class="filename">./testsuite/run-regression.log</code></td><td align="left">Summary of test result</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*.sh</code></td><td align="left">Regression tests, exit 0 for success, exit 1 for failure</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/BugID-*</code></td><td align="left">回帰テストスイートに利用されるファイル</td></tr><tr><td align="left"><code class="filename">./testsuite/regression/log/BugID-*.sh.log</code></td><td align="left">回帰テストの出力、 run-regression.sh によりスクリプトの出力がリダイレクトされる</td></tr></tbody></table></div></div><br class="table-break"><p>
- 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.
- </p><p>
- A TODO file is available in <code class="filename">debian/TODO</code>. 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.
- </p><p>
- When releasing a new version of <span class="command"><strong>pbuilder</strong></span>, the version is
-tagged with the git tag X.XXX (version number). This is done with
-<span class="command"><strong>./git-tag.sh</strong></span> script available in the source tree.
- </p></div></div><div class="chapter" title="第6章 Other uses of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="otheruse"></a>第6章 Other uses of pbuilder</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#chroot">1. pbuilder を小規模な実験のために活用する</a></span></dt><dt><span class="sect1"><a href="#runningprograms">2. Running little programs inside the chroot</a></span></dt></dl></div><div class="sect1" title="1. pbuilder を小規模な実験のために活用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chroot"></a>1. pbuilder を小規模な実験のために活用する</h2></div></div></div><p>
- 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
-<span class="command"><strong>pbuilder login</strong></span> command is available.
- </p><p>
- <span class="command"><strong>pbuilder login </strong></span> is a debugging feature for
-<span class="command"><strong>pbuilder</strong></span> itself, but it also allows users to have a
-temporary chroot.
- </p><p>
- Note that the chroot is cleaned after logging out of the shell, and mounting
-file systems inside it is considered harmful.
- </p></div><div class="sect1" title="2. Running little programs inside the chroot"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="runningprograms"></a>2. Running little programs inside the chroot</h2></div></div></div><p>
- To facilitate using <span class="command"><strong>pbuilder</strong></span> for other uses,
-<span class="command"><strong>pbuilder execute</strong></span> is available. <span class="command"><strong>pbuilder execute
-</strong></span> will take a script specified in the command-line argument, and
-invoke the script inside the chroot.
- </p><p>
- The script can be useful for sequences of operations such as installing ssh
-and adding a new user inside the chroot.
- </p></div></div><div class="chapter" title="第7章 Experimental or wishlist features of pbuilder"><div class="titlepage"><div><div><h2 class="title"><a name="experimental"></a>第7章 Experimental or wishlist features of pbuilder</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#lvm">1. LVMの活用</a></span></dt><dt><span class="sect1"><a href="#cowdancer">2. cowdancer の活用</a></span></dt><dt><span class="sect1"><a href="#withouttargz">3. tar.gz を利用しないで pbuilder を利用する</a></span></dt><dt><span class="sect1"><a href="#inavserver">4. pbuilder を vserver で利用する</a></span></dt><dt><span class="sect1"><a href="#ccache">5. Usage of ccache</a></span></dt></dl></div><p>
- There are some advanced features, above that of the basic feature of
-<span class="command"><strong>pbuilder</strong></span>, for some specific purposes.
- </p><div class="sect1" title="1. LVMの活用"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lvm"></a>1. LVMの活用</h2></div></div></div><p>
- LVM2 has a useful snapshot function that features Copy-on-write images.
-That could be used for <span class="command"><strong>pbuilder</strong></span> just as it can be used
-for the user-mode-linux <span class="command"><strong>pbuilder</strong></span> port. lvmpbuilder
-script in the examples directory implements such port. The scripts and
-documentation can be found under
-<code class="filename">/usr/share/doc/pbuilder/examples/lvmpbuilder/</code>.
- </p></div><div class="sect1" title="2. cowdancer の活用"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cowdancer"></a>2. cowdancer の活用</h2></div></div></div><p>
- <span class="command"><strong>cowdancer</strong></span> allows copy-on-write semantics on file system
-using hard links and hard-link-breaking-on-write tricks.
-<span class="command"><strong>pbuilder</strong></span> using <span class="command"><strong>cowdancer</strong></span> seems to be
-much faster and it is one ideal point for improvement.
-<span class="command"><strong>cowbuilder</strong></span>, a wrapper for <span class="command"><strong>pbuilder</strong></span> for
-using <span class="command"><strong>cowdancer</strong></span> is available from
-<span class="command"><strong>cowdancer</strong></span> package since 0.14
- </p><p>
- Example command-lines for cowbuilder look like the following.
- </p><p>
- </p><pre class="screen">
-# cowbuilder --create --distribution sid
-# cowbuilder --update --distribution sid
-# cowbuilder --build XXX.dsc</pre><p>
- </p><p>
- It is also possible to use cowdancer with pdebuild command. Specify with
-command-line option <code class="option">--pbuilder</code> or set it in
-PDEBUILD_PBUILDER configuration option.
- </p><p>
- </p><pre class="screen">
-$ pdebuild --pbuilder cowbuilder</pre><p>
- </p></div><div class="sect1" title="3. tar.gz を利用しないで pbuilder を利用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="withouttargz"></a>3. tar.gz を利用しないで pbuilder を利用する</h2></div></div></div><p>
- The <span class="command"><strong><code class="option">--no-targz</code></strong></span> option of
-<span class="command"><strong>pbuilder</strong></span> will allow usage of <span class="command"><strong>pbuilder</strong></span>
-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 <span class="command"><strong>sbuild</strong></span>.
- </p><p>
- It should be possible to create base chroot images for
-<span class="command"><strong>dchroot</strong></span> with the following commands: </p><pre class="screen">
-# 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</pre><p>
- </p></div><div class="sect1" title="4. pbuilder を vserver で利用する"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="inavserver"></a>4. pbuilder を vserver で利用する</h2></div></div></div><p>
- It is possible to use <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- To use <span class="command"><strong>pbuilder</strong></span> in a vserver, you need to set the
-<span class="command"><strong>secure_mount</strong></span> <span class="command"><strong>CAPS</strong></span> in the
-<span class="command"><strong>ccapabilities</strong></span> of this vserver.
- </p></div><div class="sect1" title="5. Usage of ccache"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ccache"></a>5. Usage of ccache</h2></div></div></div><p>
- It is possible to use C compiler cache <span class="command"><strong>ccache</strong></span> to speed up
-repeated builds of the same package (or packages that compile the same files
-multiple times for some reason). Using <span class="command"><strong>ccache</strong></span> can speed
-up repeated building of large packages dramatically, at the cost of some
-disk space and bookkeeping.
- </p><p>
- To enable usage of <span class="command"><strong>ccache</strong></span> with
-<span class="command"><strong>pbuilder</strong></span>, you should set CCACHEDIR in your pbuilderrc
-file.
- </p><p>
- 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.
- </p></div></div><div class="chapter" title="第8章 参考文献"><div class="titlepage"><div><div><h2 class="title"><a name="refs"></a>第8章 参考文献</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#dirstructoutside">1. chroot 外部のディレクトリ構造</a></span></dt><dt><span class="sect1"><a href="#dirstructinside">2. chroot 内部のディレクトリ構造</a></span></dt></dl></div><div class="sect1" title="1. chroot 外部のディレクトリ構造"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructoutside"></a>1. chroot 外部のディレクトリ構造</h2></div></div></div><div class="table"><a name="idp6068544"></a><p class="title"><b>表8.1 chroot 内部のディレクトリ構造 </b></p><div class="table-contents"><table summary="chroot 内部のディレクトリ構造 " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">ディレクトリ</th><th align="left">意味</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/pbuilderrc</code></td><td align="left">設定ファイル</td></tr><tr><td align="left"><code class="filename">/usr/share/pbuilder/pbuilderrc</code></td><td align="left">デフォルト設定</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/base.tgz</code></td><td align="left">Default location pbuilder uses for base.tgz, the tar-ball containing a basic
-Debian installation with only the build-essential packages.
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/build/PID/</code></td><td align="left">pbuilder がデフォルトでchroot のために利用する場所</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/aptcache</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> will use as apt cache, to store
-deb packages required during <span class="command"><strong>pbuilder</strong></span> build.</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> will use as cache location</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/result</code></td><td align="left">Default location <span class="command"><strong>pbuilder</strong></span> puts the deb files and other
-files created after build</td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-umlresult</code></td><td align="left">Default location <span class="command"><strong>pbuilder-user-mode-linux</strong></span> puts the deb
-files and other files created after build </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/pbuilder-mnt</code></td><td align="left">Default location <span class="command"><strong>pbuilder-user-mode-linux</strong></span> uses for
-mounting the COW file system, for chrooting.</td></tr><tr><td align="left"><code class="filename">/tmp</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> will mount tmpfs for work.</td></tr><tr><td align="left"><code class="filename">${HOME}/tmp/PID.cow</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> use this directory for location
-of COW file system.</td></tr><tr><td align="left"><code class="filename">${HOME}/uml-image</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> use this directory for
-user-mode-linux full disk image.</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect1" title="2. chroot 内部のディレクトリ構造"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dirstructinside"></a>2. chroot 内部のディレクトリ構造</h2></div></div></div><div class="table"><a name="idp6099504"></a><p class="title"><b>表8.2 chroot 内部のディレクトリ構造 </b></p><div class="table-contents"><table summary="chroot 内部のディレクトリ構造 " border="1"><colgroup><col align="left" class="c1"><col align="left" class="c2"></colgroup><thead><tr><th align="left">ディレクトリ</th><th align="left">意味</th></tr></thead><tbody><tr><td align="left"><code class="filename">/etc/mtab</code></td><td align="left">
- <code class="filename">/proc/mounts</code>へのシンボリックリンク。
- </td></tr><tr><td align="left"><code class="filename">/tmp/buildd</code></td><td align="left">Default place used in <span class="command"><strong>pbuilder</strong></span> to place the Debian
-package to be processed.
-<code class="filename">/tmp/buildd/packagename-version/</code> will be the root
-directory of the package being processed. HOME environment variable is set
-to this value inside chroot by pbuilder-buildpackage.
-<code class="option">--inputfile</code> will place files here.
- </td></tr><tr><td align="left"><code class="filename">/runscript</code></td><td align="left">The script passed as an argument to <span class="command"><strong>pbuilder</strong></span> execute is
-passed on.
- </td></tr><tr><td align="left"><code class="filename">/tmp/hooks</code></td><td align="left">
- フックの場所。
- </td></tr><tr><td align="left"><code class="filename">/var/cache/apt/archives</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> は chroot 外部の aptcache ディレクトリからコピーしてきたり、chroot
-外部の aptcache ディレクトリへコピーしたりします。
- </td></tr><tr><td align="left"><code class="filename">/var/cache/pbuilder/ccache</code></td><td align="left">
- <span class="command"><strong>pbuilder</strong></span> bind-mounts this directory for use by ccache.
- </td></tr><tr><td align="left"><code class="filename">/tmp/XXXX</code></td><td align="left"><span class="command"><strong>pbuilder-user-mode-linux</strong></span> は <code class="filename">/tmp</code>
-のスクリプトを利用して user-mode-linux にブートストラップします。</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="chapter" title="第9章 些細な過去の経緯の詳細"><div class="titlepage"><div><div><h2 class="title"><a name="idp6122272"></a>第9章 些細な過去の経緯の詳細</h2></div></div></div><div class="toc"><p><b>目次</b></p><dl><dt><span class="sect1"><a href="#idp6122912">1. マニュアルの履歴 </a></span></dt><dt><span class="sect1"><a href="#pbuilderbackgroundhistory">2. Possibly inaccurate Background History of pbuilder</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp6132976">2.1. The Time Before pbuilder</a></span></dt><dt><span class="sect2"><a href="#birth">2.2. pbuilder の誕生</a></span></dt><dt><span class="sect2"><a href="#secondyear">2.3. そして二年目の人生</a></span></dt><dt><span class="sect2"><a href="#fifthyear">2.4. pbuilder の5年目</a></span></dt></dl></dd></dl></div><div class="sect1" title="1. マニュアルの履歴"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp6122912"></a>1. マニュアルの履歴 </h2></div></div></div><p>
- This document was started on 28 Dec 2002 by Junichi Uekawa, trying to
-document what is known about <span class="command"><strong>pbuilder</strong></span>.
- </p><p>
- This documentation is available from the <span class="command"><strong>pbuilder</strong></span> source
-tar-ball, and from the git repository of <span class="command"><strong>pbuilder</strong></span>
-(web-based access is possible). A copy of this documentation can be found
-on the <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.html" target="_top">Alioth project
-page for pbuilder</a>. <a class="ulink" href="http://pbuilder.alioth.debian.org/pbuilder-doc.pdf" target="_top">There is also a PDF
-version</a>. The homepage for <span class="command"><strong>pbuilder</strong></span> is <a class="ulink" href="http://pbuilder.alioth.debian.org/" target="_top"> http://pbuilder.alioth.debian.org/
-</a> hosted by alioth project.
- </p><p>
- Documentation is written using DocBook XML, with emacs PSGML mode, and using
-wysidocbookxml for live previewing.
- </p></div><div class="sect1" title="2. Possibly inaccurate Background History of pbuilder"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="pbuilderbackgroundhistory"></a>2. Possibly inaccurate Background History of pbuilder</h2></div></div></div><p>
- The following is a most possibly inaccurate account of how
-<span class="command"><strong>pbuilder</strong></span> came to happen, and other attempts to make
-something like <span class="command"><strong>pbuilder</strong></span> happen. This part of the
-document was originally in the AUTHORS file, to give credit to those who
-existed before <span class="command"><strong>pbuilder</strong></span>.
- </p><div class="sect2" title="2.1. The Time Before pbuilder"><div class="titlepage"><div><div><h3 class="title"><a name="idp6132976"></a>2.1. The Time Before pbuilder</h3></div></div></div><p>
- 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.
- </p><p>
- 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.
- </p><p>
- 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.
- </p></div><div class="sect2" title="2.2. pbuilder の誕生"><div class="titlepage"><div><div><h3 class="title"><a name="birth"></a>2.2. pbuilder の誕生</h3></div></div></div><p>
- 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.
- </p><p>
- Building packages from source using Build-Depends information within a
-chroot sounded trivial; and <span class="command"><strong>pbuilder</strong></span> 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.
- </p><p>
- 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 <span class="command"><strong>pbuilder</strong></span>, but the amount of
-packages which are not buildable is steadily decreasing (I hope).
- </p></div><div class="sect2" title="2.3. そして二年目の人生"><div class="titlepage"><div><div><h3 class="title"><a name="secondyear"></a>2.3. そして二年目の人生</h3></div></div></div><p>
- Someone wanted <span class="command"><strong>pbuilder</strong></span> to not run as root, and as
-User-mode-linux has become more useful as time passed, I've started
-experimenting with <span class="command"><strong>pbuilder-user-mode-linux</strong></span>.
-<span class="command"><strong>pbuilder-user-mode-linux</strong></span> has not stayed functional as
-much as I would have liked, and bootstrapping
-<span class="command"><strong>user-mode-linux</strong></span> 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.
- </p></div><div class="sect2" title="2.4. pbuilder の5年目"><div class="titlepage"><div><div><h3 class="title"><a name="fifthyear"></a>2.4. pbuilder の5年目</h3></div></div></div><p>
- <span class="command"><strong>pbuilder</strong></span> 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, <span class="command"><strong>pbuilder</strong></span>
-is now co-maintained with several people.
- </p><p>
- <span class="command"><strong>sbuild</strong></span> is now a well-maintained Debian package within
-Debian, and with <span class="command"><strong>pbuilder</strong></span> 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.
- </p></div></div></div></div></body></html>
diff -Nru pbuilder-0.215+nmu3/examples/D65various-compiler-support pbuilder-0.215+nmu4/examples/D65various-compiler-support
--- pbuilder-0.215+nmu3/examples/D65various-compiler-support 2013-03-26 10:11:53.000000000 +0100
+++ pbuilder-0.215+nmu4/examples/D65various-compiler-support 2015-06-22 10:05:23.000000000 +0200
@@ -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.215+nmu3/Makefile pbuilder-0.215+nmu4/Makefile
--- pbuilder-0.215+nmu3/Makefile 2014-07-11 19:58:44.000000000 +0200
+++ pbuilder-0.215+nmu4/Makefile 2015-06-22 18:04:04.000000000 +0200
@@ -19,7 +19,7 @@
NULL :=
ALLDIRS += BASHCOMPLETION
-BASHCOMPLETIONDIR := $(SYSCONFDIR)/bash_completion.d
+BASHCOMPLETIONDIR := $(PKGDATADIR)/../bash-completion/completions/
BASHCOMPLETION_DATA += \
bash_completion.d/pbuilder \
$(NULL)
@@ -190,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.215+nmu3/patches/hoge.diff pbuilder-0.215+nmu4/patches/hoge.diff
--- pbuilder-0.215+nmu3/patches/hoge.diff 2011-06-24 12:42:26.000000000 +0200
+++ pbuilder-0.215+nmu4/patches/hoge.diff 1970-01-01 01:00:00.000000000 +0100
@@ -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 <dktrkranz at debian.org> 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.215+nmu3/patches/nmu4 pbuilder-0.215+nmu4/patches/nmu4
--- pbuilder-0.215+nmu3/patches/nmu4 2011-06-24 12:36:05.000000000 +0200
+++ pbuilder-0.215+nmu4/patches/nmu4 1970-01-01 01:00:00.000000000 +0100
@@ -1,466 +0,0 @@
-From pbuilder-maint-bounces+dancer=netfort.gr.jp at lists.alioth.debian.org Thu May 26 21:12:27 2011
-Return-Path: <pbuilder-maint-bounces+dancer=netfort.gr.jp at lists.alioth.debian.org>
-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 at 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 <pbuilder-maint-bounces+dancer=netfort.gr.jp at lists.alioth.debian.org>)
- id 1QPhrD-000289-9H
- for dancer at 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 <debbugs at busoni.debian.org>) id 1QPhrA-000281-IV
- for pbuilder-maint at 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 <debbugs at busoni.debian.org>)
- id 1QPhqe-0000py-Jl; Thu, 26 May 2011 21:12:04 +0000
-X-Loop: owner at bugs.debian.org
-Subject: Bug#400848: pbuilder: diff for NMU version 0.199+nmu4
-Resent-From: Thorsten Glaser <tg at mirbsd.de>
-Resent-To: debian-bugs-dist at lists.debian.org
-Resent-CC: Debian pbuilder maintenance team
- <pbuilder-maint at lists.alioth.debian.org>
-X-Loop: owner at bugs.debian.org
-Resent-Date: Thu, 26 May 2011 21:12:02 +0000
-Resent-Message-ID: <handler.400848.B400848.13064441782813 at bugs.debian.org>
-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 at 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 <tg at herc.mirbsd.org>)
- id 1QPho6-0000is-1B; Thu, 26 May 2011 21:09:31 +0000
-Received: from herc.mirbsd.org (tg at 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 at 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 <tg at mirbsd.de>
-X-X-Sender: tg at herc.mirbsd.org
-To: 620730 at bugs.debian.org, 626431 at bugs.debian.org, 627086 at bugs.debian.org,
- 603420 at bugs.debian.org, 601250 at bugs.debian.org, 603881 at bugs.debian.org,
- 400848 at bugs.debian.org, 622624 at bugs.debian.org
-Message-ID: <Pine.BSM.4.64L.1105262100390.6597 at herc.mirbsd.org>
-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 <debbugs at busoni.debian.org>
-x-debian-approved: yes
-Cc: control at bugs.debian.org
-X-BeenThere: pbuilder-maint at lists.alioth.debian.org
-X-Mailman-Version: 2.1.13
-Precedence: list
-Reply-To: Thorsten Glaser <tg at mirbsd.de>, 400848 at bugs.debian.org
-List-Id: Development mailing list for pbuilder
- <pbuilder-maint.lists.alioth.debian.org>
-List-Unsubscribe: <http://lists.alioth.debian.org/cgi-bin/mailman/options/pbuilder-maint>,
- <mailto:pbuilder-maint-request at lists.alioth.debian.org?subject=unsubscribe>
-List-Archive: <http://lists.alioth.debian.org/pipermail/pbuilder-maint>
-List-Post: <mailto:pbuilder-maint at lists.alioth.debian.org>
-List-Help: <mailto:pbuilder-maint-request at lists.alioth.debian.org?subject=help>
-List-Subscribe: <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint>,
- <mailto:pbuilder-maint-request at lists.alioth.debian.org?subject=subscribe>
-Sender: pbuilder-maint-bounces+dancer=netfort.gr.jp at lists.alioth.debian.org
-Errors-To: pbuilder-maint-bounces+dancer=netfort.gr.jp at lists.alioth.debian.org
-X-SA-Exim-Connect-IP: ::1
-X-SA-Exim-Mail-From: pbuilder-maint-bounces+dancer=netfort.gr.jp at 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: <Pine.BSM.4.64L.1105262108370.6597 at herc.mirbsd.org>
-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: <Pine.BSM.4.64L.1105262108371.6597 at herc.mirbsd.org>
-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: <Pine.BSM.4.64L.1105262108372.6597 at herc.mirbsd.org>
-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 at lists.alioth.debian.org
-http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
---0-422438018-1306444141=:6597--
-
-
-
diff -Nru pbuilder-0.215+nmu3/pbuilder-buildpackage pbuilder-0.215+nmu4/pbuilder-buildpackage
--- pbuilder-0.215+nmu3/pbuilder-buildpackage 2014-07-11 19:51:28.000000000 +0200
+++ pbuilder-0.215+nmu4/pbuilder-buildpackage 2015-06-22 10:05:23.000000000 +0200
@@ -36,8 +36,8 @@
# 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.
- SUTOUSER="LD_PRELOAD= LOGNAME=$BUILDUSERNAME /sbin/start-stop-daemon --start --pidfile /dev/null --chuid $BUILDUSERNAME --startas /bin/sh"
+ # 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."
diff -Nru pbuilder-0.215+nmu3/pbuilder-modules pbuilder-0.215+nmu4/pbuilder-modules
--- pbuilder-0.215+nmu3/pbuilder-modules 2013-03-26 09:49:36.000000000 +0100
+++ pbuilder-0.215+nmu4/pbuilder-modules 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/pbuilder-satisfydepends-aptitude pbuilder-0.215+nmu4/pbuilder-satisfydepends-aptitude
--- pbuilder-0.215+nmu3/pbuilder-satisfydepends-aptitude 2012-03-09 00:07:29.000000000 +0100
+++ pbuilder-0.215+nmu4/pbuilder-satisfydepends-aptitude 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/pbuilder-satisfydepends-classic pbuilder-0.215+nmu4/pbuilder-satisfydepends-classic
--- pbuilder-0.215+nmu3/pbuilder-satisfydepends-classic 2011-06-25 01:06:40.000000000 +0200
+++ pbuilder-0.215+nmu4/pbuilder-satisfydepends-classic 2015-06-22 18:04:04.000000000 +0200
@@ -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.215+nmu3/pbuilder-satisfydepends-funcs pbuilder-0.215+nmu4/pbuilder-satisfydepends-funcs
--- pbuilder-0.215+nmu3/pbuilder-satisfydepends-funcs 2012-03-09 00:11:32.000000000 +0100
+++ pbuilder-0.215+nmu4/pbuilder-satisfydepends-funcs 2015-06-22 18:04:04.000000000 +0200
@@ -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\+</;/g')"
+ local PKG="$(echo "$INSTALLPKG" | cut -d ' ' -f 1)"
+ local SEEN_PROFILE
+ local PROFILE
+ local NEGATED
+ local FOUND
+ IFS=';' read -ra RESTRLISTS <<< "$DEP_RESTRICTIONS"
+ for restrlist in "${RESTRLISTS[@]}"; do
+ SEEN_PROFILE="yes"
+ for restr in $restrlist; do
+ if [[ "$restr" == '!'* ]]; then
+ NEGATED="yes"
+ PROFILE=${restr#!}
+ else
+ NEGATED="no"
+ PROFILE=${restr}
+ fi
+ FOUND="no"
+ for p in $PROFILES; do
+ if [ "$p" = "$PROFILE" ]; then
+ FOUND="yes"
+ break
+ fi
+ done
+ if [ "$FOUND" = "$NEGATED" ]; then
+ SEEN_PROFILE="no"
+ break
+ fi
+ done
+
+ if [ "$SEEN_PROFILE" = "yes" ]; then
+ return 1
+ fi
+ done
+ return 0
+}
+
checkbuilddep_provides() {
local PACKAGENAME="$1"
# PROVIDED needs to be used outside of this function.
diff -Nru pbuilder-0.215+nmu3/test_pbuilder-satisfydepends-funcs pbuilder-0.215+nmu4/test_pbuilder-satisfydepends-funcs
--- pbuilder-0.215+nmu3/test_pbuilder-satisfydepends-funcs 2010-06-20 05:49:52.000000000 +0200
+++ pbuilder-0.215+nmu4/test_pbuilder-satisfydepends-funcs 2015-06-22 18:04:04.000000000 +0200
@@ -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 <!stage1>" ""
+expect_success checkbuilddep_restrictiondeps "foo <!stage1>" "stage1"
+expect_fail checkbuilddep_restrictiondeps "foo <!stage1>" "notest"
+expect_success checkbuilddep_restrictiondeps "foo <!stage1>" "stage1 notest"
+
+expect_success checkbuilddep_restrictiondeps "foo <stage1>" ""
+expect_fail checkbuilddep_restrictiondeps "foo <stage1>" "stage1"
+expect_success checkbuilddep_restrictiondeps "foo <stage1>" "notest"
+expect_fail checkbuilddep_restrictiondeps "foo <stage1>" "stage1 notest"
+
+expect_fail checkbuilddep_restrictiondeps "foo <!stage1 !notest>" ""
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 !notest>" "stage1"
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 !notest>" "notest"
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 !notest>" "stage1 notest"
+
+expect_success checkbuilddep_restrictiondeps "foo <stage1 notest>" ""
+expect_success checkbuilddep_restrictiondeps "foo <stage1 notest>" "stage1"
+expect_success checkbuilddep_restrictiondeps "foo <stage1 notest>" "notest"
+expect_fail checkbuilddep_restrictiondeps "foo <stage1 notest>" "stage1 notest"
+
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 notest>" ""
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 notest>" "stage1"
+expect_fail checkbuilddep_restrictiondeps "foo <!stage1 notest>" "notest"
+expect_success checkbuilddep_restrictiondeps "foo <!stage1 notest>" "stage1 notest"
+
+expect_success checkbuilddep_restrictiondeps "foo <stage1 !notest>" ""
+expect_fail checkbuilddep_restrictiondeps "foo <stage1 !notest>" "stage1"
+expect_success checkbuilddep_restrictiondeps "foo <stage1 !notest>" "notest"
+expect_success checkbuilddep_restrictiondeps "foo <stage1 !notest>" "stage1 notest"
+
+test_filter_restriction_deps() {
+ echo "$1" | filter_restriction_deps "$2"
+}
+
+expect_output "foo" test_filter_restriction_deps "foo <!stage1>" ""
+expect_output "" test_filter_restriction_deps "foo <!stage1>" "stage1"
+expect_output "foo" test_filter_restriction_deps "foo <stage1>" "stage1"
+expect_output "bar, foo" test_filter_restriction_deps "bar, foo <stage1>" "stage1"
+expect_output "bar | foo" test_filter_restriction_deps "bar | foo <stage1>" "stage1"
+expect_output "bar" test_filter_restriction_deps "bar | foo <!stage1>" "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] <!stage1>" "amd64" ""
+expect_output "" test_filter_arch_restriction_deps "foo [amd64] <stage1>" "amd64" ""
+expect_output "foo" test_filter_arch_restriction_deps "foo [amd64] <!stage1>" "amd64" ""
+expect_output "" test_filter_arch_restriction_deps "foo [i386] <stage1>" "amd64" "stage1"
+
expect_output "debhelper (>= 7)" test_get_build_deps_dsc
testlib_summary
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control 2011-07-13 14:34:16.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/control 1970-01-01 01:00:00.000000000 +0100
@@ -1,10 +0,0 @@
-Package: buildindeppkg
-Source: buildarchpkg
-Version: 0.1
-Architecture: all
-Maintainer: Junichi Uekawa <dancer at debian.org>
-Installed-Size: 28
-Section: unknown
-Priority: extra
-Description: <insert up to 60 chars description>
- <insert long description, indented with spaces>
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums 2011-07-13 14:34:18.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/DEBIAN/md5sums 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-bf5ff4686f2c9e13e9f495c99541b535 usr/share/doc/buildindeppkg/changelog.gz
Binary files /tmp/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/usr/share/doc/buildindeppkg/changelog.gz and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg/usr/share/doc/buildindeppkg/changelog.gz differ
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log 2011-07-13 14:34:18.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.debhelper.log 1970-01-01 01:00:00.000000000 +0100
@@ -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.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars 2011-07-13 14:34:11.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/buildindeppkg.substvars 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-misc:Depends=
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog 2011-07-13 14:33:33.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/changelog 1970-01-01 01:00:00.000000000 +0100
@@ -1,6 +0,0 @@
-buildarchpkg (0.1) unstable; urgency=low
-
- * a package that has both arch dep and indep parts.
-
- -- Junichi Uekawa <dancer at debian.org> Wed, 13 Jul 2011 21:33:33 +0900
-
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control 2011-07-13 14:31:07.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/control 1970-01-01 01:00:00.000000000 +0100
@@ -1,19 +0,0 @@
-Source: buildarchpkg
-Section: unknown
-Priority: extra
-Maintainer: Junichi Uekawa <dancer at debian.org>
-Build-Depends: debhelper (>= 5)
-Build-Depends-Indep: ghostscript
-Standards-Version: 3.7.2
-
-Package: buildarchpkg
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: <insert up to 60 chars description>
- <insert long description, indented with spaces>
-
-Package: buildindeppkg
-Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: <insert up to 60 chars description>
- <insert long description, indented with spaces>
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log 2011-07-13 14:34:18.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/debhelper.log 1970-01-01 01:00:00.000000000 +0100
@@ -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.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files 2011-07-13 14:34:16.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/files 1970-01-01 01:00:00.000000000 +0100
@@ -1,2 +0,0 @@
-buildarchpkg_0.1_i386.deb unknown extra
-buildindeppkg_0.1_all.deb unknown extra
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules 2011-07-13 14:26:47.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/rules 1970-01-01 01:00:00.000000000 +0100
@@ -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.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars 2011-07-13 14:34:05.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/substvars 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-misc:Depends=
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control 2011-07-13 14:34:11.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/control 1970-01-01 01:00:00.000000000 +0100
@@ -1,9 +0,0 @@
-Package: buildarchpkg
-Version: 0.1
-Architecture: i386
-Maintainer: Junichi Uekawa <dancer at debian.org>
-Installed-Size: 28
-Section: unknown
-Priority: extra
-Description: <insert up to 60 chars description>
- <insert long description, indented with spaces>
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums 2011-07-13 14:34:17.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/DEBIAN/md5sums 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-bf5ff4686f2c9e13e9f495c99541b535 usr/share/doc/buildarchpkg/changelog.gz
Binary files /tmp/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/usr/share/doc/buildarchpkg/changelog.gz and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/debian/tmp/usr/share/doc/buildarchpkg/changelog.gz differ
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README 2011-07-13 14:28:53.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg-0.1/README 1970-01-01 01:00:00.000000000 +0100
@@ -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.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build 2011-07-13 14:35:20.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.build 1970-01-01 01:00:00.000000000 +0100
@@ -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 <dancer at debian.org>
- 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.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes 2011-07-13 14:34:26.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.changes 1970-01-01 01:00:00.000000000 +0100
@@ -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 <dancer at debian.org>
-Changed-By: Junichi Uekawa <dancer at debian.org>
-Description:
- buildarchpkg - <insert up to 60 chars description>
- buildindeppkg - <insert up to 60 chars description>
-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/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.deb and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildarchpkg_0.1_i386.deb differ
Binary files /tmp/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/buildindeppkg_0.1_all.deb and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/buildindeppkg_0.1_all.deb differ
diff -Nru pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build
--- pbuilder-0.215+nmu3/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build 2011-07-13 14:31:23.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/random-manual-test-material/buildarchpkg/successpkg_0.1_i386.build 1970-01-01 01:00:00.000000000 +0100
@@ -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 <dancer at debian.org>
- 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.215+nmu3/testsuite/regression/work/526471/526471.log pbuilder-0.215+nmu4/testsuite/regression/work/526471/526471.log
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/526471.log 2009-11-29 09:21:19.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/526471.log 1970-01-01 01:00:00.000000000 +0100
@@ -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 <pbuilder-maint at lists.alioth.debian.org>
-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 <dancer at debian.org>
-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.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/changelog pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/changelog
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/changelog 2009-11-29 09:20:27.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/changelog 1970-01-01 01:00:00.000000000 +0100
@@ -1,6 +0,0 @@
-failpkg (0.1) unstable; urgency=low
-
- * a package that fails
-
- -- Junichi Uekawa <dancer at debian.org> Sun, 27 May 2007 14:27:53 +0900
-
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/control pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/control
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/control 2009-11-29 09:20:27.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/control 1970-01-01 01:00:00.000000000 +0100
@@ -1,12 +0,0 @@
-Source: failpkg
-Section: unknown
-Priority: extra
-Maintainer: Junichi Uekawa <dancer at debian.org>
-Build-Depends: debhelper (>= 5)
-Standards-Version: 3.7.2
-
-Package: failpkg
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: <insert up to 60 chars description>
- <insert long description, indented with spaces>
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/rules pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/rules
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/debian/rules 2009-11-29 09:20:27.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/debian/rules 1970-01-01 01:00:00.000000000 +0100
@@ -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.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/README pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/README
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg-0.1/README 2007-05-27 07:27:11.000000000 +0200
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg-0.1/README 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-This is an example package that simply fails to build.
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1_amd64.build pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1_amd64.build
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1_amd64.build 2009-11-29 09:21:19.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1_amd64.build 1970-01-01 01:00:00.000000000 +0100
@@ -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 <pbuilder-maint at lists.alioth.debian.org>
-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 <dancer at debian.org>
-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/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1.diff.gz and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1.diff.gz differ
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1.dsc pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1.dsc
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1.dsc 2009-11-29 09:21:19.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1.dsc 1970-01-01 01:00:00.000000000 +0100
@@ -1,17 +0,0 @@
-Format: 1.0
-Source: failpkg
-Binary: failpkg
-Architecture: any
-Version: 0.1
-Maintainer: Junichi Uekawa <dancer at debian.org>
-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/8GM7rypJet/pbuilder-0.215+nmu3/testsuite/regression/work/526471/failpkg_0.1.orig.tar.gz and /tmp/bhYREV2VCg/pbuilder-0.215+nmu4/testsuite/regression/work/526471/failpkg_0.1.orig.tar.gz differ
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/A01_hook pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/A01_hook
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/A01_hook 2009-11-29 09:20:26.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/A01_hook 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-echo failpkg-A-hook-executed
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/C01_failhook pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/C01_failhook
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/C01_failhook 2009-11-29 09:20:26.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/C01_failhook 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-echo failpkg-hook-executed
diff -Nru pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/F01_hook pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/F01_hook
--- pbuilder-0.215+nmu3/testsuite/regression/work/526471-hook/F01_hook 2009-11-29 09:20:26.000000000 +0100
+++ pbuilder-0.215+nmu4/testsuite/regression/work/526471-hook/F01_hook 1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-echo failpkg-F-hook-executed
More information about the Pbuilder-maint
mailing list