[SCM] live-manual branch, debian, updated. debian/2.0.0-1-55-gfd6e353
Ben Armstrong
synrg at debian.org
Thu Dec 23 11:39:08 UTC 2010
The following commit has been merged in the debian branch:
commit fd6e353830e9a292ced0ba2c6b6bec9403e81581
Author: Ben Armstrong <synrg at debian.org>
Date: Thu Dec 23 07:38:55 2010 -0400
Expanding and correcting Reporting bugs chapter.
diff --git a/manual/de/project_bugs.ssi b/manual/de/project_bugs.ssi
index 685bead..7eaaaea 100644
--- a/manual/de/project_bugs.ssi
+++ b/manual/de/project_bugs.ssi
@@ -21,42 +21,44 @@ used and the distribution of the live system you are building.
2~ Known issues
-Due to the nature of Debian *{testing}* and Debian *{unstable}*
-distributions being a moving target, building a live system may not always
-be possible.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a
+moving target, when you specify either as the target system distribution, a
+successful build may not always be possible.
-If this is a problem, do not build a system based on *{testing}* or
-*{unstable}*, but go with *{stable}*. live-build does always default to the
-current *{stable}* release.
+% FIXME:
+
+If this causes too much difficulty for you, do not build a system based on
+*{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does
+always default to the *{stable}* release.
Currently known issues are listed under the section 'status' on our homepage
-at http://live.debian.net/
+at http://live.debian.net/.
-It is out of the scope of this manual to train you in correctly identifying
-and fixing problems in packages of the development distributions, however,
-there are two things you can always try: When not succeeding to build
-*{testing}*, try if *{unstable}* works. If *{unstable}* does not work
-either, revert to *{testing}* and pinning the newer version of the failing
-package from *{unstable}*.
+It is out of the scope of this manual to train you to correctly identify and
+fix problems in packages of the development distributions, however, there
+are two things you can always try: If a build fails when the target
+distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work
+either, revert to *{testing}* and pin the newer version of the failing
+package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Rebuild from scratch
-To ensure that a particular bug is not caused by an unclean built system,
+To ensure that a particular bug is not caused by an uncleanly built system,
please always rebuild the whole live system from scratch to see if the bug
is reproducible.
2~ Use up-to-date packages
Using outdated packages can cause significant problems when trying to
-reproduce (and ultimately fix) your problem.
+reproduce (and ultimately fix) your problem. Make sure your build system is
+up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Collect information
-Please provide enough information with your report. At a minimum, it should
-contain the exact version of live-build version where the bug is
-encountered, and steps to reproduce it. Please use common sense and include
-other relevant information if you think that it might help in solving the
-problem.
+Please provide enough information with your report. At least include the
+exact version of live-build version where the bug is encountered and steps
+to reproduce it. Please use common sense and include other relevant
+information if you think that it might help in solving the problem.
To make the most out of your bug report, we require at least the following
information:
@@ -69,7 +71,7 @@ _* Version of live-boot on the live system
_* Version of live-config on the live system
-_* Version of debootstrap and/or cdebootstrap on the host system
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architecture of the live system
@@ -77,7 +79,9 @@ _* Distribution of the live system
_* Version of the kernel on the live system
-You can generate a log of the build process by using the tee command:
+You can generate a log of the build process by using the #{tee}# command. We
+recommend doing this automatically with an #{auto/build}# script; see
+{Managing a configuration}#managing-a-configuration for details).
code{
@@ -85,18 +89,33 @@ code{
}code
-For runtime log, live-boot stores a log in #{/var/log/live.log}# (or
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or
#{/var/log/live-boot.log}#).
Additionally, to rule out other errors, it is always a good idea to tar up
-your config directory and upload it somewhere (do *{not}* send it as an
-attachment to the mailinglist), so that we can try to reproduce the errors
-you encountered.
+your #{config/}# directory and upload it somewhere (do *{not}* send it as an
+attachment to the mailing list), so that we can try to reproduce the errors
+you encountered. If this is difficult (e.g. due to size) you can use the
+output of #{lb config --dump}# which produces a summary of your config tree
+(i.e. lists files in subdirectories of #{config/}# but does not include
+them).
Remember to send in any logs that were produced with English locale
settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or
#{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that
+breaks. It is not always easy to do this, so if you can't manage it for your
+report, don't worry. However, if you plan your development cycle well, using
+small enough change sets per iteration, you may be able to isolate the
+problem by constructing a simpler 'base' configuration that closely matches
+your actual configuration plus just the broken change set added to it. If
+you have a hard time sorting out which of your changes broke, it may be that
+you are including too much in each change set and should develop in smaller
+increments.
+
2~ Use the correct package to report the bug against
Where does the bug appear?
@@ -121,9 +140,9 @@ can fail. If a bug appears here, check if the error is also reproducible on
a normal system.
If this is the case, this is not a bug in Debian Live, but rather in Debian
-- please report it against the failing package. Running debootstrap
-seperately from the Live system build or running lb bootstrap with
-#{--debug}# will give you more information.
+- please report it against the failing package. Running #{debootstrap}#
+separately from the Live system build or running #{lb bootstrap --debug}#
+will give you more information.
Also, if you are using a local mirror and/or any of sort of proxy and you
are experiencing a problem, please always reproduce it first by
@@ -134,10 +153,10 @@ bootstrapping from an official mirror.
If your image does not boot, please report it to the mailing list together
with the information requested in {Collect
information}#collect-information. Do not forget to mention, how/when the
-image failed, in Qemu, VMWare or real hardware. If you are using a
-virtualization technology of any kind, please always run it on real hardware
-before reporting a bug. Providing a screenshot of the failure is also very
-helpful.
+image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using
+a virtualization technology of any kind, please always run it on real
+hardware before reporting a bug. Providing a screenshot of the failure is
+also very helpful.
3~ At run time
diff --git a/manual/en/project_bugs.ssi b/manual/en/project_bugs.ssi
index 7512d4f..e0cf633 100644
--- a/manual/en/project_bugs.ssi
+++ b/manual/en/project_bugs.ssi
@@ -14,25 +14,27 @@ _* Try to give *{as specific information as possible}* about the bug. This inclu
2~ Known issues
-Due to the nature of Debian *{testing}* and Debian *{unstable}* distributions being a moving target, building a live system may not always be possible.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a moving target, when you specify either as the target system distribution, a successful build may not always be possible.
-If this is a problem, do not build a system based on *{testing}* or *{unstable}*, but go with *{stable}*. live-build does always default to the current *{stable}* release.
+% FIXME:
-Currently known issues are listed under the section 'status' on our homepage at http://live.debian.net/
+If this causes too much difficulty for you, do not build a system based on *{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does always default to the *{stable}* release.
-It is out of the scope of this manual to train you in correctly identifying and fixing problems in packages of the development distributions, however, there are two things you can always try: When not succeeding to build *{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, revert to *{testing}* and pinning the newer version of the failing package from *{unstable}*.
+Currently known issues are listed under the section 'status' on our homepage at http://live.debian.net/.
+
+It is out of the scope of this manual to train you to correctly identify and fix problems in packages of the development distributions, however, there are two things you can always try: If a build fails when the target distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work either, revert to *{testing}* and pin the newer version of the failing package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Rebuild from scratch
-To ensure that a particular bug is not caused by an unclean built system, please always rebuild the whole live system from scratch to see if the bug is reproducible.
+To ensure that a particular bug is not caused by an uncleanly built system, please always rebuild the whole live system from scratch to see if the bug is reproducible.
2~ Use up-to-date packages
-Using outdated packages can cause significant problems when trying to reproduce (and ultimately fix) your problem.
+Using outdated packages can cause significant problems when trying to reproduce (and ultimately fix) your problem. Make sure your build system is up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Collect information
-Please provide enough information with your report. At a minimum, it should contain the exact version of live-build version where the bug is encountered, and steps to reproduce it. Please use common sense and include other relevant information if you think that it might help in solving the problem.
+Please provide enough information with your report. At least include the exact version of live-build version where the bug is encountered and steps to reproduce it. Please use common sense and include other relevant information if you think that it might help in solving the problem.
To make the most out of your bug report, we require at least the following information:
@@ -44,7 +46,7 @@ _* Version of live-boot on the live system
_* Version of live-config on the live system
-_* Version of debootstrap and/or cdebootstrap on the host system
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architecture of the live system
@@ -52,7 +54,7 @@ _* Distribution of the live system
_* Version of the kernel on the live system
-You can generate a log of the build process by using the tee command:
+You can generate a log of the build process by using the #{tee}# command. We recommend doing this automatically with an #{auto/build}# script; see {Managing a configuration}#managing-a-configuration for details).
code{
@@ -60,12 +62,16 @@ code{
}code
-For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/live-boot.log}#).
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/live-boot.log}#).
-Additionally, to rule out other errors, it is always a good idea to tar up your config directory and upload it somewhere (do *{not}* send it as an attachment to the mailinglist), so that we can try to reproduce the errors you encountered.
+Additionally, to rule out other errors, it is always a good idea to tar up your #{config/}# directory and upload it somewhere (do *{not}* send it as an attachment to the mailing list), so that we can try to reproduce the errors you encountered. If this is difficult (e.g. due to size) you can use the output of #{lb config --dump}# which produces a summary of your config tree (i.e. lists files in subdirectories of #{config/}# but does not include them).
Remember to send in any logs that were produced with English locale settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that breaks. It is not always easy to do this, so if you can't manage it for your report, don't worry. However, if you plan your development cycle well, using small enough change sets per iteration, you may be able to isolate the problem by constructing a simpler 'base' configuration that closely matches your actual configuration plus just the broken change set added to it. If you have a hard time sorting out which of your changes broke, it may be that you are including too much in each change set and should develop in smaller increments.
+
2~ Use the correct package to report the bug against
Where does the bug appear?
@@ -80,13 +86,13 @@ In both cases, this is not a bug in Debian Live, but rather in Debian itself whi
live-build installs additional packages from the Debian archive and depending on the Debian distribution used and the daily archive state, it can fail. If a bug appears here, check if the error is also reproducible on a normal system.
-If this is the case, this is not a bug in Debian Live, but rather in Debian - please report it against the failing package. Running debootstrap seperately from the Live system build or running lb bootstrap with #{--debug}# will give you more information.
+If this is the case, this is not a bug in Debian Live, but rather in Debian - please report it against the failing package. Running #{debootstrap}# separately from the Live system build or running #{lb bootstrap --debug}# will give you more information.
Also, if you are using a local mirror and/or any of sort of proxy and you are experiencing a problem, please always reproduce it first by bootstrapping from an official mirror.
3~ At boot time
-If your image does not boot, please report it to the mailing list together with the information requested in {Collect information}#collect-information. Do not forget to mention, how/when the image failed, in Qemu, VMWare or real hardware. If you are using a virtualization technology of any kind, please always run it on real hardware before reporting a bug. Providing a screenshot of the failure is also very helpful.
+If your image does not boot, please report it to the mailing list together with the information requested in {Collect information}#collect-information. Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using a virtualization technology of any kind, please always run it on real hardware before reporting a bug. Providing a screenshot of the failure is also very helpful.
3~ At run time
diff --git a/manual/fr/project_bugs.ssi b/manual/fr/project_bugs.ssi
index 685bead..7eaaaea 100644
--- a/manual/fr/project_bugs.ssi
+++ b/manual/fr/project_bugs.ssi
@@ -21,42 +21,44 @@ used and the distribution of the live system you are building.
2~ Known issues
-Due to the nature of Debian *{testing}* and Debian *{unstable}*
-distributions being a moving target, building a live system may not always
-be possible.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a
+moving target, when you specify either as the target system distribution, a
+successful build may not always be possible.
-If this is a problem, do not build a system based on *{testing}* or
-*{unstable}*, but go with *{stable}*. live-build does always default to the
-current *{stable}* release.
+% FIXME:
+
+If this causes too much difficulty for you, do not build a system based on
+*{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does
+always default to the *{stable}* release.
Currently known issues are listed under the section 'status' on our homepage
-at http://live.debian.net/
+at http://live.debian.net/.
-It is out of the scope of this manual to train you in correctly identifying
-and fixing problems in packages of the development distributions, however,
-there are two things you can always try: When not succeeding to build
-*{testing}*, try if *{unstable}* works. If *{unstable}* does not work
-either, revert to *{testing}* and pinning the newer version of the failing
-package from *{unstable}*.
+It is out of the scope of this manual to train you to correctly identify and
+fix problems in packages of the development distributions, however, there
+are two things you can always try: If a build fails when the target
+distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work
+either, revert to *{testing}* and pin the newer version of the failing
+package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Rebuild from scratch
-To ensure that a particular bug is not caused by an unclean built system,
+To ensure that a particular bug is not caused by an uncleanly built system,
please always rebuild the whole live system from scratch to see if the bug
is reproducible.
2~ Use up-to-date packages
Using outdated packages can cause significant problems when trying to
-reproduce (and ultimately fix) your problem.
+reproduce (and ultimately fix) your problem. Make sure your build system is
+up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Collect information
-Please provide enough information with your report. At a minimum, it should
-contain the exact version of live-build version where the bug is
-encountered, and steps to reproduce it. Please use common sense and include
-other relevant information if you think that it might help in solving the
-problem.
+Please provide enough information with your report. At least include the
+exact version of live-build version where the bug is encountered and steps
+to reproduce it. Please use common sense and include other relevant
+information if you think that it might help in solving the problem.
To make the most out of your bug report, we require at least the following
information:
@@ -69,7 +71,7 @@ _* Version of live-boot on the live system
_* Version of live-config on the live system
-_* Version of debootstrap and/or cdebootstrap on the host system
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architecture of the live system
@@ -77,7 +79,9 @@ _* Distribution of the live system
_* Version of the kernel on the live system
-You can generate a log of the build process by using the tee command:
+You can generate a log of the build process by using the #{tee}# command. We
+recommend doing this automatically with an #{auto/build}# script; see
+{Managing a configuration}#managing-a-configuration for details).
code{
@@ -85,18 +89,33 @@ code{
}code
-For runtime log, live-boot stores a log in #{/var/log/live.log}# (or
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or
#{/var/log/live-boot.log}#).
Additionally, to rule out other errors, it is always a good idea to tar up
-your config directory and upload it somewhere (do *{not}* send it as an
-attachment to the mailinglist), so that we can try to reproduce the errors
-you encountered.
+your #{config/}# directory and upload it somewhere (do *{not}* send it as an
+attachment to the mailing list), so that we can try to reproduce the errors
+you encountered. If this is difficult (e.g. due to size) you can use the
+output of #{lb config --dump}# which produces a summary of your config tree
+(i.e. lists files in subdirectories of #{config/}# but does not include
+them).
Remember to send in any logs that were produced with English locale
settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or
#{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that
+breaks. It is not always easy to do this, so if you can't manage it for your
+report, don't worry. However, if you plan your development cycle well, using
+small enough change sets per iteration, you may be able to isolate the
+problem by constructing a simpler 'base' configuration that closely matches
+your actual configuration plus just the broken change set added to it. If
+you have a hard time sorting out which of your changes broke, it may be that
+you are including too much in each change set and should develop in smaller
+increments.
+
2~ Use the correct package to report the bug against
Where does the bug appear?
@@ -121,9 +140,9 @@ can fail. If a bug appears here, check if the error is also reproducible on
a normal system.
If this is the case, this is not a bug in Debian Live, but rather in Debian
-- please report it against the failing package. Running debootstrap
-seperately from the Live system build or running lb bootstrap with
-#{--debug}# will give you more information.
+- please report it against the failing package. Running #{debootstrap}#
+separately from the Live system build or running #{lb bootstrap --debug}#
+will give you more information.
Also, if you are using a local mirror and/or any of sort of proxy and you
are experiencing a problem, please always reproduce it first by
@@ -134,10 +153,10 @@ bootstrapping from an official mirror.
If your image does not boot, please report it to the mailing list together
with the information requested in {Collect
information}#collect-information. Do not forget to mention, how/when the
-image failed, in Qemu, VMWare or real hardware. If you are using a
-virtualization technology of any kind, please always run it on real hardware
-before reporting a bug. Providing a screenshot of the failure is also very
-helpful.
+image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using
+a virtualization technology of any kind, please always run it on real
+hardware before reporting a bug. Providing a screenshot of the failure is
+also very helpful.
3~ At run time
diff --git a/manual/it/project_bugs.ssi b/manual/it/project_bugs.ssi
index 6e7ef77..ec6bf14 100644
--- a/manual/it/project_bugs.ssi
+++ b/manual/it/project_bugs.ssi
@@ -22,42 +22,44 @@ si sta costruendo.
2~ Problemi noti
-A causa della natura di Debian *{testing}* e Debian *{unstable}* di subire
-cambiamenti continui, la costruzione di un sistema live può non essere
-sempre possibile.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a
+moving target, when you specify either as the target system distribution, a
+successful build may not always be possible.
-Se questo è un problema, non creare un sistema basato su *{testing}* o
-*{unstable}* ma usare piuttosto *{stable}*. live-build si basa sull'attuale
-rilascio di *{stable}* in modo predefinito.
+% FIXME:
-I problemi noti al momento sono elencati sotto la sezione "status" della
-nostra pagina iniziale http://live.debian.net/
+If this causes too much difficulty for you, do not build a system based on
+*{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does
+always default to the *{stable}* release.
-Questo manuale non intende insegnare come identificare e risolvere
-correttamente i problemi dei pacchetti delle distribuzioni di sviluppo,
-tuttavia ci sono un paio di cose da provare: se la creazione di *{testing}*
-non va a buon fine provare con *{unstable}*; se non funziona nemmeno
-*{unstable}* tornare a *{testing}* ed effettuare il pinning da *{unstable}*
-alla nuova versione del pacchetto corrotto.
+Currently known issues are listed under the section 'status' on our homepage
+at http://live.debian.net/.
+
+It is out of the scope of this manual to train you to correctly identify and
+fix problems in packages of the development distributions, however, there
+are two things you can always try: If a build fails when the target
+distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work
+either, revert to *{testing}* and pin the newer version of the failing
+package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Ricostruire da zero
-Per essere certi che un particolare bug non sia causato dalla creazione di
-un sistema non pulito, ricostruire sempre l'intero sistema da zero per
-vedere se il bug sia riproducibile.
+To ensure that a particular bug is not caused by an uncleanly built system,
+please always rebuild the whole live system from scratch to see if the bug
+is reproducible.
2~ Usare pacchetti aggiornati
-L'utilizzo di pacchetti datati può causare notevoli complicazioni nel
-tentativo di riprodurre (e alla fine risolvere) il problema.
+Using outdated packages can cause significant problems when trying to
+reproduce (and ultimately fix) your problem. Make sure your build system is
+up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Raccogliere informazioni
-Nella segnalazione si invita a fornire informazioni sufficienti. Dovrebbe
-almeno contenere l'esatta versione di live-build nella quale si è trovato il
-bug e i passi per riprodurlo. Con un po' di buon senso si può includere
-qualsiasi altro dettaglio rilevante che si ritiene utile per la risoluzione
-del problema.
+Please provide enough information with your report. At least include the
+exact version of live-build version where the bug is encountered and steps
+to reproduce it. Please use common sense and include other relevant
+information if you think that it might help in solving the problem.
Affinché la segnalazione del bug sia migliore possibile, si richiedono
almeno le seguenti informazioni:
@@ -70,7 +72,7 @@ _* Versione di live-boot sul sistema ospitante
_* Versione di live-config sul sistema live
-_* Versione di debootstrap o cdebootstrap sul sistema ospitante
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architettura del sistema live
@@ -78,8 +80,9 @@ _* Distribuzione del sistema live
_* Versione del kernel sul sistema live
-È possibile generare un registro del processo di compilazione usando il
-comando tee:
+You can generate a log of the build process by using the #{tee}# command. We
+recommend doing this automatically with an #{auto/build}# script; see
+{Managing a configuration}#managing-a-configuration for details).
code{
@@ -87,18 +90,33 @@ code{
}code
-Durante la sua esecuzione live-boot conserva una registrazione in
-#{/var/log/live.log}# (or #{/var/log/live-boot.log}#).
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or
+#{/var/log/live-boot.log}#).
-Inoltre, per escludere altri errori, è sempre una buona idea creare un tar
-della propria directory di configurazione e caricarlo da qualche parte
-(*{non}* inviarlo come allegato alla mailing list), in modo che sia per noi
-possibile riprodurre gli errori incontrati.
+Additionally, to rule out other errors, it is always a good idea to tar up
+your #{config/}# directory and upload it somewhere (do *{not}* send it as an
+attachment to the mailing list), so that we can try to reproduce the errors
+you encountered. If this is difficult (e.g. due to size) you can use the
+output of #{lb config --dump}# which produces a summary of your config tree
+(i.e. lists files in subdirectories of #{config/}# but does not include
+them).
Ricordarsi che i file di registro da inviare vanno creati con l'impostazione
della lingua inglese, ad esempio eseguendo il comando live-build preponendo
#{LC_ALL=C}# oppure #{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that
+breaks. It is not always easy to do this, so if you can't manage it for your
+report, don't worry. However, if you plan your development cycle well, using
+small enough change sets per iteration, you may be able to isolate the
+problem by constructing a simpler 'base' configuration that closely matches
+your actual configuration plus just the broken change set added to it. If
+you have a hard time sorting out which of your changes broke, it may be that
+you are including too much in each change set and should develop in smaller
+increments.
+
2~ Segnalare il bug del pacchetto giusto
Dove appare il bug?
@@ -123,22 +141,23 @@ a seconda della distribuzione Debian e lo stato dell'archivio giornaliero.Se
il bug appare a questo punto, controllare che l'errore sia riproducibile su
un sistema normale.
-In questo caso non è un bug in Debian Live, ma piuttosto in Debian, inviare
-una segnalazione sul pacchetto che ha fallito. Si otterranno maggiori
-informazioni eseguendo debootstrap separatamente dal sistema live o
-eseguendo lb bootstrap con l'opzione #{--debug}#.
+If this is the case, this is not a bug in Debian Live, but rather in Debian
+- please report it against the failing package. Running #{debootstrap}#
+separately from the Live system build or running #{lb bootstrap --debug}#
+will give you more information.
Se si verifica un problema utilizzando un mirror locale o un qualsiasi tipo
di proxy è bene riprodurlo avviando da un mirror ufficiale.
3~ In fase di avvio
-Se l'immagine non si avvia segnalarlo alla mailing list con le informazioni
-richieste in {Raccogliere informazioni}#collect-information. Non dimenticare
-di menzionare come e quando l'immagine fallisce, in Qemu, VMWare o hardware
-reale. Se si utilizza un qualsiasi sistema di virtualizzazione provare
-sempre su hardware reale prima di segnalare un bug; anche fornire
-un'istantanea dello schermo può essere molto utile.
+If your image does not boot, please report it to the mailing list together
+with the information requested in {Collect
+information}#collect-information. Do not forget to mention, how/when the
+image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using
+a virtualization technology of any kind, please always run it on real
+hardware before reporting a bug. Providing a screenshot of the failure is
+also very helpful.
3~ In fase di esecuzione
diff --git a/manual/po/de/project_bugs.ssi.po b/manual/po/de/project_bugs.ssi.po
index 3e2811c..dfcae8b 100644
--- a/manual/po/de/project_bugs.ssi.po
+++ b/manual/po/de/project_bugs.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: 2010-10-25 23:27+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,7 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -84,7 +84,7 @@ msgstr ""
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -198,153 +198,165 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:18
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
-msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+msgid "% FIXME:"
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:22
msgid ""
-"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:24
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"Currently known issues are listed under the section 'status' on our homepage "
+"at http://live.debian.net/."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:26
-msgid "2~ Rebuild from scratch"
+msgid ""
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:28
+msgid "2~ Rebuild from scratch"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:30
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -352,22 +364,41 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -377,7 +408,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -385,12 +416,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -399,16 +430,16 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -416,40 +447,40 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -459,7 +490,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -468,7 +499,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -476,12 +507,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -490,7 +521,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -500,7 +531,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/po/fr/project_bugs.ssi.po b/manual/po/fr/project_bugs.ssi.po
index 320a78d..38444ce 100644
--- a/manual/po/fr/project_bugs.ssi.po
+++ b/manual/po/fr/project_bugs.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: 2010-10-25 23:27+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,7 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -84,7 +84,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -198,153 +198,165 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:18
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
-msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+msgid "% FIXME:"
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:22
msgid ""
-"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:24
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"Currently known issues are listed under the section 'status' on our homepage "
+"at http://live.debian.net/."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:26
-msgid "2~ Rebuild from scratch"
+msgid ""
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:28
+msgid "2~ Rebuild from scratch"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:30
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -352,22 +364,41 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -377,7 +408,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -385,12 +416,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -399,16 +430,16 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -416,40 +447,40 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -459,7 +490,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -468,7 +499,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -476,12 +507,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -490,7 +521,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -500,7 +531,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/po/it/live-manual.ssm.po b/manual/po/it/live-manual.ssm.po
index 6d827bd..819caff 100644
--- a/manual/po/it/live-manual.ssm.po
+++ b/manual/po/it/live-manual.ssm.po
@@ -45,6 +45,7 @@ msgstr ""
#. type: Plain text
#: en/live-manual.ssm:13
+#, no-wrap
msgid ""
"@date:\n"
" :published: 2010-12-23\n"
diff --git a/manual/po/it/project_bugs.ssi.po b/manual/po/it/project_bugs.ssi.po
index 204bbe3..5ed3df3 100644
--- a/manual/po/it/project_bugs.ssi.po
+++ b/manual/po/it/project_bugs.ssi.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: 2010-12-15 23:11+0100\n"
"Last-Translator: skizzhg <skizzhg at gmx.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -21,7 +21,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -85,7 +85,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -210,10 +210,15 @@ msgstr "2~ Problemi noti"
#. type: Plain text
#: en/project_bugs.ssi:18
+#, fuzzy
+#| msgid ""
+#| "Due to the nature of Debian *{testing}* and Debian *{unstable}* "
+#| "distributions being a moving target, building a live system may not "
+#| "always be possible."
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
"A causa della natura di Debian *{testing}* e Debian *{unstable}* di subire "
"cambiamenti continui, la costruzione di un sistema live può non essere "
@@ -221,33 +226,55 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
+msgid "% FIXME:"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:22
+#, fuzzy
+#| msgid ""
+#| "If this is a problem, do not build a system based on *{testing}* or *"
+#| "{unstable}*, but go with *{stable}*. live-build does always default to "
+#| "the current *{stable}* release."
msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
"Se questo è un problema, non creare un sistema basato su *{testing}* o *"
"{unstable}* ma usare piuttosto *{stable}*. live-build si basa sull'attuale "
"rilascio di *{stable}* in modo predefinito."
#. type: Plain text
-#: en/project_bugs.ssi:22
+#: en/project_bugs.ssi:24
+#, fuzzy
+#| msgid ""
+#| "Currently known issues are listed under the section 'status' on our "
+#| "homepage at http://live.debian.net/"
msgid ""
"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"at http://live.debian.net/."
msgstr ""
"I problemi noti al momento sono elencati sotto la sezione \"status\" della "
"nostra pagina iniziale http://live.debian.net/"
#. type: Plain text
-#: en/project_bugs.ssi:24
+#: en/project_bugs.ssi:26
+#, fuzzy
+#| msgid ""
+#| "It is out of the scope of this manual to train you in correctly "
+#| "identifying and fixing problems in packages of the development "
+#| "distributions, however, there are two things you can always try: When not "
+#| "succeeding to build *{testing}*, try if *{unstable}* works. If *{unstable}"
+#| "* does not work either, revert to *{testing}* and pinning the newer "
+#| "version of the failing package from *{unstable}*."
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
"Questo manuale non intende insegnare come identificare e risolvere "
"correttamente i problemi dei pacchetti delle distribuzioni di sviluppo, "
@@ -257,14 +284,19 @@ msgstr ""
"alla nuova versione del pacchetto corrotto."
#. type: Plain text
-#: en/project_bugs.ssi:26
+#: en/project_bugs.ssi:28
msgid "2~ Rebuild from scratch"
msgstr "2~ Ricostruire da zero"
#. type: Plain text
-#: en/project_bugs.ssi:28
+#: en/project_bugs.ssi:30
+#, fuzzy
+#| msgid ""
+#| "To ensure that a particular bug is not caused by an unclean built system, "
+#| "please always rebuild the whole live system from scratch to see if the "
+#| "bug is reproducible."
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
@@ -273,32 +305,43 @@ msgstr ""
"vedere se il bug sia riproducibile."
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr "2~ Usare pacchetti aggiornati"
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
+#, fuzzy
+#| msgid ""
+#| "Using outdated packages can cause significant problems when trying to "
+#| "reproduce (and ultimately fix) your problem."
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
"L'utilizzo di pacchetti datati può causare notevoli complicazioni nel "
"tentativo di riprodurre (e alla fine risolvere) il problema."
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr "2~collect-information Raccogliere informazioni"
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
+#, fuzzy
+#| msgid ""
+#| "Please provide enough information with your report. At a minimum, it "
+#| "should contain the exact version of live-build version where the bug is "
+#| "encountered, and steps to reproduce it. Please use common sense and "
+#| "include other relevant information if you think that it might help in "
+#| "solving the problem."
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
"Nella segnalazione si invita a fornire informazioni sufficienti. Dovrebbe "
"almeno contenere l'esatta versione di live-build nella quale si è trovato il "
@@ -307,7 +350,7 @@ msgstr ""
"del problema."
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
@@ -316,74 +359,91 @@ msgstr ""
"almeno le seguenti informazioni:"
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr "_* Architettura del sistema ospitante"
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr "_* Versione di live-build sul sistema ospitante"
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr "_* Versione di live-boot sul sistema ospitante"
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr "_* Versione di live-config sul sistema live"
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+#, fuzzy
+#| msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr "_* Versione di debootstrap o cdebootstrap sul sistema ospitante"
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr "_* Architettura del sistema live"
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr "_* Distribuzione del sistema live"
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr "_* Versione del kernel sul sistema live"
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
-"È possibile generare un registro del processo di compilazione usando il "
-"comando tee:"
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
+#, fuzzy
+#| msgid ""
+#| "For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/"
+#| "var/log/live-boot.log}#)."
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
"Durante la sua esecuzione live-boot conserva una registrazione in #{/var/log/"
"live.log}# (or #{/var/log/live-boot.log}#)."
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
+#, fuzzy
+#| msgid ""
+#| "Additionally, to rule out other errors, it is always a good idea to tar "
+#| "up your config directory and upload it somewhere (do *{not}* send it as "
+#| "an attachment to the mailinglist), so that we can try to reproduce the "
+#| "errors you encountered."
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
"Inoltre, per escludere altri errori, è sempre una buona idea creare un tar "
"della propria directory di configurazione e caricarlo da qualche parte (*"
@@ -391,7 +451,7 @@ msgstr ""
"possibile riprodurre gli errori incontrati."
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -402,22 +462,41 @@ msgstr ""
"{LC_ALL=C}# oppure #{LC_ALL=en_US}#."
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr "2~ Segnalare il bug del pacchetto giusto"
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr "Dove appare il bug?"
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr "3~ Durante la compilazione mentre esegue il bootstrap"
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -432,7 +511,7 @@ msgstr ""
"probabile) o allo strumento di avvio stesso."
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -444,12 +523,12 @@ msgstr ""
"fallito."
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr "3~ Durante la compilazione mentre installa i pacchetti"
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -462,12 +541,18 @@ msgstr ""
"un sistema normale."
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
+#, fuzzy
+#| msgid ""
+#| "If this is the case, this is not a bug in Debian Live, but rather in "
+#| "Debian - please report it against the failing package. Running "
+#| "debootstrap seperately from the Live system build or running lb bootstrap "
+#| "with #{--debug}# will give you more information."
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
"In questo caso non è un bug in Debian Live, ma piuttosto in Debian, inviare "
"una segnalazione sul pacchetto che ha fallito. Si otterranno maggiori "
@@ -475,7 +560,7 @@ msgstr ""
"eseguendo lb bootstrap con l'opzione #{--debug}#."
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -485,19 +570,28 @@ msgstr ""
"di proxy è bene riprodurlo avviando da un mirror ufficiale."
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr "3~ In fase di avvio"
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
+#, fuzzy
+#| msgid ""
+#| "If your image does not boot, please report it to the mailing list "
+#| "together with the information requested in {Collect information}#collect-"
+#| "information. Do not forget to mention, how/when the image failed, in "
+#| "Qemu, VMWare or real hardware. If you are using a virtualization "
+#| "technology of any kind, please always run it on real hardware before "
+#| "reporting a bug. Providing a screenshot of the failure is also very "
+#| "helpful."
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
"Se l'immagine non si avvia segnalarlo alla mailing list con le informazioni "
"richieste in {Raccogliere informazioni}#collect-information. Non dimenticare "
@@ -507,12 +601,12 @@ msgstr ""
"un'istantanea dello schermo può essere molto utile."
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr "3~ In fase di esecuzione"
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
@@ -522,12 +616,12 @@ msgstr ""
"Live. Tuttavia,"
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr "2~ Fare la ricerca"
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -542,7 +636,7 @@ msgstr ""
"soluzione temporanea."
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -555,7 +649,7 @@ msgstr ""
"nella segnalazione del bug."
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -566,12 +660,12 @@ msgstr ""
"qualcosa di simile."
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr "2~ Dove segnalare i bug"
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -584,7 +678,7 @@ msgstr ""
"il comando #{reportbug}# dall'omonimo pacchetto."
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -599,7 +693,7 @@ msgstr ""
"messaggio in mailing list e vi aiuteremo a capire."
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/po/pt_BR/project_bugs.ssi.po b/manual/po/pt_BR/project_bugs.ssi.po
index 010d47f..c370f2b 100644
--- a/manual/po/pt_BR/project_bugs.ssi.po
+++ b/manual/po/pt_BR/project_bugs.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: 2010-10-25 23:27+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,7 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -84,7 +84,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -198,153 +198,165 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:18
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
-msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+msgid "% FIXME:"
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:22
msgid ""
-"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:24
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"Currently known issues are listed under the section 'status' on our homepage "
+"at http://live.debian.net/."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:26
-msgid "2~ Rebuild from scratch"
+msgid ""
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:28
+msgid "2~ Rebuild from scratch"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:30
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -352,22 +364,41 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -377,7 +408,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -385,12 +416,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -399,16 +430,16 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -416,40 +447,40 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -459,7 +490,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -468,7 +499,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -476,12 +507,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -490,7 +521,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -500,7 +531,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/po/ro/project_bugs.ssi.po b/manual/po/ro/project_bugs.ssi.po
index 88c31d5..47680e4 100644
--- a/manual/po/ro/project_bugs.ssi.po
+++ b/manual/po/ro/project_bugs.ssi.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: 2010-10-27 22:56+0200\n"
"Last-Translator: Creak <romain.failliot at foolstep.com>\n"
"Language-Team: Français <debian-live at lists.debian.org>\n"
@@ -21,7 +21,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -85,7 +85,7 @@ msgstr "code{"
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -199,153 +199,165 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:18
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
-msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+msgid "% FIXME:"
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:22
msgid ""
-"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:24
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"Currently known issues are listed under the section 'status' on our homepage "
+"at http://live.debian.net/."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:26
-msgid "2~ Rebuild from scratch"
+msgid ""
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:28
+msgid "2~ Rebuild from scratch"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:30
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -353,22 +365,41 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -378,7 +409,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -386,12 +417,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -400,16 +431,16 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -417,40 +448,40 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -460,7 +491,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -469,7 +500,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -477,12 +508,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -491,7 +522,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -501,7 +532,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/pot/project_bugs.ssi.pot b/manual/pot/project_bugs.ssi.pot
index c7b5a88..040f2dd 100644
--- a/manual/pot/project_bugs.ssi.pot
+++ b/manual/pot/project_bugs.ssi.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2010-12-19 20:37-0400\n"
+"POT-Creation-Date: 2010-12-23 07:37-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -20,7 +20,7 @@ msgstr ""
#: en/about_manual.ssi:84 en/about_manual.ssi:92 en/about_manual.ssi:100
#: en/about_manual.ssi:108 en/about_manual.ssi:120 en/about_manual.ssi:133
#: en/about_manual.ssi:146 en/about_manual.ssi:154 en/about_manual.ssi:162
-#: en/about_manual.ssi:170 en/project_bugs.ssi:58
+#: en/about_manual.ssi:170 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:28 en/project_coding-style.ssi:38
#: en/project_coding-style.ssi:51 en/project_coding-style.ssi:61
#: en/project_coding-style.ssi:92 en/project_coding-style.ssi:100
@@ -84,7 +84,7 @@ msgstr ""
#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
#: en/about_manual.ssi:112 en/about_manual.ssi:129 en/about_manual.ssi:142
#: en/about_manual.ssi:150 en/about_manual.ssi:158 en/about_manual.ssi:166
-#: en/about_manual.ssi:174 en/project_bugs.ssi:62
+#: en/about_manual.ssi:174 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:34 en/project_coding-style.ssi:45
#: en/project_coding-style.ssi:57 en/project_coding-style.ssi:68
#: en/project_coding-style.ssi:96 en/project_coding-style.ssi:104
@@ -198,153 +198,165 @@ msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:18
msgid ""
-"Due to the nature of Debian *{testing}* and Debian *{unstable}* "
-"distributions being a moving target, building a live system may not always "
-"be possible."
+"Because Debian *{testing}* and Debian *{unstable}* distributions are a "
+"moving target, when you specify either as the target system distribution, a "
+"successful build may not always be possible."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:20
-msgid ""
-"If this is a problem, do not build a system based on *{testing}* or *"
-"{unstable}*, but go with *{stable}*. live-build does always default to the "
-"current *{stable}* release."
+msgid "% FIXME:"
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:22
msgid ""
-"Currently known issues are listed under the section 'status' on our homepage "
-"at http://live.debian.net/"
+"If this causes too much difficulty for you, do not build a system based on *"
+"{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does "
+"always default to the *{stable}* release."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:24
msgid ""
-"It is out of the scope of this manual to train you in correctly identifying "
-"and fixing problems in packages of the development distributions, however, "
-"there are two things you can always try: When not succeeding to build *"
-"{testing}*, try if *{unstable}* works. If *{unstable}* does not work either, "
-"revert to *{testing}* and pinning the newer version of the failing package "
-"from *{unstable}*."
+"Currently known issues are listed under the section 'status' on our homepage "
+"at http://live.debian.net/."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:26
-msgid "2~ Rebuild from scratch"
+msgid ""
+"It is out of the scope of this manual to train you to correctly identify and "
+"fix problems in packages of the development distributions, however, there "
+"are two things you can always try: If a build fails when the target "
+"distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work "
+"either, revert to *{testing}* and pin the newer version of the failing "
+"package from *{unstable}* (see {APT pinning}#apt-pinning for details)."
msgstr ""
#. type: Plain text
#: en/project_bugs.ssi:28
+msgid "2~ Rebuild from scratch"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:30
msgid ""
-"To ensure that a particular bug is not caused by an unclean built system, "
+"To ensure that a particular bug is not caused by an uncleanly built system, "
"please always rebuild the whole live system from scratch to see if the bug "
"is reproducible."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:30
+#: en/project_bugs.ssi:32
msgid "2~ Use up-to-date packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:32
+#: en/project_bugs.ssi:34
msgid ""
"Using outdated packages can cause significant problems when trying to "
-"reproduce (and ultimately fix) your problem."
+"reproduce (and ultimately fix) your problem. Make sure your build system is "
+"up-to-date and any packages included in your image are up-to-date as well."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:34
+#: en/project_bugs.ssi:36
msgid "2~collect-information Collect information"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:36
+#: en/project_bugs.ssi:38
msgid ""
-"Please provide enough information with your report. At a minimum, it should "
-"contain the exact version of live-build version where the bug is "
-"encountered, and steps to reproduce it. Please use common sense and include "
-"other relevant information if you think that it might help in solving the "
-"problem."
+"Please provide enough information with your report. At least include the "
+"exact version of live-build version where the bug is encountered and steps "
+"to reproduce it. Please use common sense and include other relevant "
+"information if you think that it might help in solving the problem."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:38
+#: en/project_bugs.ssi:40
msgid ""
"To make the most out of your bug report, we require at least the following "
"information:"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:40
+#: en/project_bugs.ssi:42
msgid "_* Architecture of the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:42
+#: en/project_bugs.ssi:44
msgid "_* Version of live-build on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:44
+#: en/project_bugs.ssi:46
msgid "_* Version of live-boot on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:46
+#: en/project_bugs.ssi:48
msgid "_* Version of live-config on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:48
-msgid "_* Version of debootstrap and/or cdebootstrap on the host system"
+#: en/project_bugs.ssi:50
+msgid ""
+"_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:50
+#: en/project_bugs.ssi:52
msgid "_* Architecture of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:52
+#: en/project_bugs.ssi:54
msgid "_* Distribution of the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:54
+#: en/project_bugs.ssi:56
msgid "_* Version of the kernel on the live system"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:56
-msgid "You can generate a log of the build process by using the tee command:"
+#: en/project_bugs.ssi:58
+msgid ""
+"You can generate a log of the build process by using the #{tee}# command. We "
+"recommend doing this automatically with an #{auto/build}# script; see "
+"{Managing a configuration}#managing-a-configuration for details)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:60
+#: en/project_bugs.ssi:62
#, no-wrap
msgid " # lb build 2>&1 | tee build.log\n"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:64
+#: en/project_bugs.ssi:66
msgid ""
-"For runtime log, live-boot stores a log in #{/var/log/live.log}# (or #{/var/"
-"log/live-boot.log}#)."
+"At boot time, live-boot stores a log in #{/var/log/live.log}# (or #{/var/log/"
+"live-boot.log}#)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:66
+#: en/project_bugs.ssi:68
msgid ""
"Additionally, to rule out other errors, it is always a good idea to tar up "
-"your config directory and upload it somewhere (do *{not}* send it as an "
-"attachment to the mailinglist), so that we can try to reproduce the errors "
-"you encountered."
+"your #{config/}# directory and upload it somewhere (do *{not}* send it as an "
+"attachment to the mailing list), so that we can try to reproduce the errors "
+"you encountered. If this is difficult (e.g. due to size) you can use the "
+"output of #{lb config --dump}# which produces a summary of your config tree "
+"(i.e. lists files in subdirectories of #{config/}# but does not include "
+"them)."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:68
+#: en/project_bugs.ssi:70
msgid ""
"Remember to send in any logs that were produced with English locale "
"settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or #"
@@ -352,22 +364,41 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:70
+#: en/project_bugs.ssi:72
+msgid "2~ Isolate the failing case if possible"
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:74
+msgid ""
+"If possible, isolate the failing case to the smallest possible change that "
+"breaks. It is not always easy to do this, so if you can't manage it for your "
+"report, don't worry. However, if you plan your development cycle well, using "
+"small enough change sets per iteration, you may be able to isolate the "
+"problem by constructing a simpler 'base' configuration that closely matches "
+"your actual configuration plus just the broken change set added to it. If "
+"you have a hard time sorting out which of your changes broke, it may be that "
+"you are including too much in each change set and should develop in smaller "
+"increments."
+msgstr ""
+
+#. type: Plain text
+#: en/project_bugs.ssi:76
msgid "2~ Use the correct package to report the bug against"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:72
+#: en/project_bugs.ssi:78
msgid "Where does the bug appear?"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:74
+#: en/project_bugs.ssi:80
msgid "3~ At build time whilst bootstrapping"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:76
+#: en/project_bugs.ssi:82
msgid ""
"live-build first bootstraps a basic Debian system with #{debootstrap}# or #"
"{cdebootstrap}#. Depending on the bootstrapping tool used and the Debian "
@@ -377,7 +408,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:78
+#: en/project_bugs.ssi:84
msgid ""
"In both cases, this is not a bug in Debian Live, but rather in Debian itself "
"which we can not fix this directly. Please report such a bug against the "
@@ -385,12 +416,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:80
+#: en/project_bugs.ssi:86
msgid "3~ At build time whilst installing packages"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:82
+#: en/project_bugs.ssi:88
msgid ""
"live-build installs additional packages from the Debian archive and "
"depending on the Debian distribution used and the daily archive state, it "
@@ -399,16 +430,16 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:84
+#: en/project_bugs.ssi:90
msgid ""
"If this is the case, this is not a bug in Debian Live, but rather in Debian "
-"- please report it against the failing package. Running debootstrap "
-"seperately from the Live system build or running lb bootstrap with #{--debug}"
-"# will give you more information."
+"- please report it against the failing package. Running #{debootstrap}# "
+"separately from the Live system build or running #{lb bootstrap --debug}# "
+"will give you more information."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:86
+#: en/project_bugs.ssi:92
msgid ""
"Also, if you are using a local mirror and/or any of sort of proxy and you "
"are experiencing a problem, please always reproduce it first by "
@@ -416,40 +447,40 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:88
+#: en/project_bugs.ssi:94
msgid "3~ At boot time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:90
+#: en/project_bugs.ssi:96
msgid ""
"If your image does not boot, please report it to the mailing list together "
"with the information requested in {Collect information}#collect-information. "
-"Do not forget to mention, how/when the image failed, in Qemu, VMWare or real "
-"hardware. If you are using a virtualization technology of any kind, please "
-"always run it on real hardware before reporting a bug. Providing a "
-"screenshot of the failure is also very helpful."
+"Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, "
+"VMWare or real hardware. If you are using a virtualization technology of any "
+"kind, please always run it on real hardware before reporting a bug. "
+"Providing a screenshot of the failure is also very helpful."
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:92
+#: en/project_bugs.ssi:98
msgid "3~ At run time"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:94
+#: en/project_bugs.ssi:100
msgid ""
"If a package was successfully installed, but fails while actually running "
"the Live system, this is probably a bug in Debian Live. However,"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:96
+#: en/project_bugs.ssi:102
msgid "2~ Do the research"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:98
+#: en/project_bugs.ssi:104
msgid ""
"Before filing the bug, please search the web for the particular error "
"message or symptom you are getting. As it is highly unlikely that you are "
@@ -459,7 +490,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:100
+#: en/project_bugs.ssi:106
msgid ""
"You should pay particular attention to the Debian Live mailing list, as well "
"as the homepage, as these are likely to contain the most up-to-date "
@@ -468,7 +499,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:102
+#: en/project_bugs.ssi:108
msgid ""
"In addition, you should check the current bug lists for live-build, live-"
"boot, and live-config to see whether something similar has been reported "
@@ -476,12 +507,12 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:104
+#: en/project_bugs.ssi:110
msgid "2~ Where to report bugs"
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:106
+#: en/project_bugs.ssi:112
msgid ""
"The Debian Live project keeps track of all bugs in the Debian Bug Tracking "
"System (BTS). For information on how to use the system, please see http://"
@@ -490,7 +521,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:108
+#: en/project_bugs.ssi:114
msgid ""
"In general, you should report build time errors against the live-build "
"package, boot time errors against live-boot, and run time errors against "
@@ -500,7 +531,7 @@ msgid ""
msgstr ""
#. type: Plain text
-#: en/project_bugs.ssi:109
+#: en/project_bugs.ssi:115
msgid ""
"Please note that bugs found in distributions derived from Debian (such as "
"Ubuntu and others) should *{not}* be reported to the Debian BTS unless they "
diff --git a/manual/pt_BR/project_bugs.ssi b/manual/pt_BR/project_bugs.ssi
index 685bead..7eaaaea 100644
--- a/manual/pt_BR/project_bugs.ssi
+++ b/manual/pt_BR/project_bugs.ssi
@@ -21,42 +21,44 @@ used and the distribution of the live system you are building.
2~ Known issues
-Due to the nature of Debian *{testing}* and Debian *{unstable}*
-distributions being a moving target, building a live system may not always
-be possible.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a
+moving target, when you specify either as the target system distribution, a
+successful build may not always be possible.
-If this is a problem, do not build a system based on *{testing}* or
-*{unstable}*, but go with *{stable}*. live-build does always default to the
-current *{stable}* release.
+% FIXME:
+
+If this causes too much difficulty for you, do not build a system based on
+*{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does
+always default to the *{stable}* release.
Currently known issues are listed under the section 'status' on our homepage
-at http://live.debian.net/
+at http://live.debian.net/.
-It is out of the scope of this manual to train you in correctly identifying
-and fixing problems in packages of the development distributions, however,
-there are two things you can always try: When not succeeding to build
-*{testing}*, try if *{unstable}* works. If *{unstable}* does not work
-either, revert to *{testing}* and pinning the newer version of the failing
-package from *{unstable}*.
+It is out of the scope of this manual to train you to correctly identify and
+fix problems in packages of the development distributions, however, there
+are two things you can always try: If a build fails when the target
+distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work
+either, revert to *{testing}* and pin the newer version of the failing
+package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Rebuild from scratch
-To ensure that a particular bug is not caused by an unclean built system,
+To ensure that a particular bug is not caused by an uncleanly built system,
please always rebuild the whole live system from scratch to see if the bug
is reproducible.
2~ Use up-to-date packages
Using outdated packages can cause significant problems when trying to
-reproduce (and ultimately fix) your problem.
+reproduce (and ultimately fix) your problem. Make sure your build system is
+up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Collect information
-Please provide enough information with your report. At a minimum, it should
-contain the exact version of live-build version where the bug is
-encountered, and steps to reproduce it. Please use common sense and include
-other relevant information if you think that it might help in solving the
-problem.
+Please provide enough information with your report. At least include the
+exact version of live-build version where the bug is encountered and steps
+to reproduce it. Please use common sense and include other relevant
+information if you think that it might help in solving the problem.
To make the most out of your bug report, we require at least the following
information:
@@ -69,7 +71,7 @@ _* Version of live-boot on the live system
_* Version of live-config on the live system
-_* Version of debootstrap and/or cdebootstrap on the host system
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architecture of the live system
@@ -77,7 +79,9 @@ _* Distribution of the live system
_* Version of the kernel on the live system
-You can generate a log of the build process by using the tee command:
+You can generate a log of the build process by using the #{tee}# command. We
+recommend doing this automatically with an #{auto/build}# script; see
+{Managing a configuration}#managing-a-configuration for details).
code{
@@ -85,18 +89,33 @@ code{
}code
-For runtime log, live-boot stores a log in #{/var/log/live.log}# (or
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or
#{/var/log/live-boot.log}#).
Additionally, to rule out other errors, it is always a good idea to tar up
-your config directory and upload it somewhere (do *{not}* send it as an
-attachment to the mailinglist), so that we can try to reproduce the errors
-you encountered.
+your #{config/}# directory and upload it somewhere (do *{not}* send it as an
+attachment to the mailing list), so that we can try to reproduce the errors
+you encountered. If this is difficult (e.g. due to size) you can use the
+output of #{lb config --dump}# which produces a summary of your config tree
+(i.e. lists files in subdirectories of #{config/}# but does not include
+them).
Remember to send in any logs that were produced with English locale
settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or
#{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that
+breaks. It is not always easy to do this, so if you can't manage it for your
+report, don't worry. However, if you plan your development cycle well, using
+small enough change sets per iteration, you may be able to isolate the
+problem by constructing a simpler 'base' configuration that closely matches
+your actual configuration plus just the broken change set added to it. If
+you have a hard time sorting out which of your changes broke, it may be that
+you are including too much in each change set and should develop in smaller
+increments.
+
2~ Use the correct package to report the bug against
Where does the bug appear?
@@ -121,9 +140,9 @@ can fail. If a bug appears here, check if the error is also reproducible on
a normal system.
If this is the case, this is not a bug in Debian Live, but rather in Debian
-- please report it against the failing package. Running debootstrap
-seperately from the Live system build or running lb bootstrap with
-#{--debug}# will give you more information.
+- please report it against the failing package. Running #{debootstrap}#
+separately from the Live system build or running #{lb bootstrap --debug}#
+will give you more information.
Also, if you are using a local mirror and/or any of sort of proxy and you
are experiencing a problem, please always reproduce it first by
@@ -134,10 +153,10 @@ bootstrapping from an official mirror.
If your image does not boot, please report it to the mailing list together
with the information requested in {Collect
information}#collect-information. Do not forget to mention, how/when the
-image failed, in Qemu, VMWare or real hardware. If you are using a
-virtualization technology of any kind, please always run it on real hardware
-before reporting a bug. Providing a screenshot of the failure is also very
-helpful.
+image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using
+a virtualization technology of any kind, please always run it on real
+hardware before reporting a bug. Providing a screenshot of the failure is
+also very helpful.
3~ At run time
diff --git a/manual/ro/project_bugs.ssi b/manual/ro/project_bugs.ssi
index 685bead..7eaaaea 100644
--- a/manual/ro/project_bugs.ssi
+++ b/manual/ro/project_bugs.ssi
@@ -21,42 +21,44 @@ used and the distribution of the live system you are building.
2~ Known issues
-Due to the nature of Debian *{testing}* and Debian *{unstable}*
-distributions being a moving target, building a live system may not always
-be possible.
+Because Debian *{testing}* and Debian *{unstable}* distributions are a
+moving target, when you specify either as the target system distribution, a
+successful build may not always be possible.
-If this is a problem, do not build a system based on *{testing}* or
-*{unstable}*, but go with *{stable}*. live-build does always default to the
-current *{stable}* release.
+% FIXME:
+
+If this causes too much difficulty for you, do not build a system based on
+*{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does
+always default to the *{stable}* release.
Currently known issues are listed under the section 'status' on our homepage
-at http://live.debian.net/
+at http://live.debian.net/.
-It is out of the scope of this manual to train you in correctly identifying
-and fixing problems in packages of the development distributions, however,
-there are two things you can always try: When not succeeding to build
-*{testing}*, try if *{unstable}* works. If *{unstable}* does not work
-either, revert to *{testing}* and pinning the newer version of the failing
-package from *{unstable}*.
+It is out of the scope of this manual to train you to correctly identify and
+fix problems in packages of the development distributions, however, there
+are two things you can always try: If a build fails when the target
+distribution is *{testing}*, try *{unstable}*. If *{unstable}* does not work
+either, revert to *{testing}* and pin the newer version of the failing
+package from *{unstable}* (see {APT pinning}#apt-pinning for details).
2~ Rebuild from scratch
-To ensure that a particular bug is not caused by an unclean built system,
+To ensure that a particular bug is not caused by an uncleanly built system,
please always rebuild the whole live system from scratch to see if the bug
is reproducible.
2~ Use up-to-date packages
Using outdated packages can cause significant problems when trying to
-reproduce (and ultimately fix) your problem.
+reproduce (and ultimately fix) your problem. Make sure your build system is
+up-to-date and any packages included in your image are up-to-date as well.
2~collect-information Collect information
-Please provide enough information with your report. At a minimum, it should
-contain the exact version of live-build version where the bug is
-encountered, and steps to reproduce it. Please use common sense and include
-other relevant information if you think that it might help in solving the
-problem.
+Please provide enough information with your report. At least include the
+exact version of live-build version where the bug is encountered and steps
+to reproduce it. Please use common sense and include other relevant
+information if you think that it might help in solving the problem.
To make the most out of your bug report, we require at least the following
information:
@@ -69,7 +71,7 @@ _* Version of live-boot on the live system
_* Version of live-config on the live system
-_* Version of debootstrap and/or cdebootstrap on the host system
+_* Version of #{debootstrap}# and/or #{cdebootstrap}# on the host system
_* Architecture of the live system
@@ -77,7 +79,9 @@ _* Distribution of the live system
_* Version of the kernel on the live system
-You can generate a log of the build process by using the tee command:
+You can generate a log of the build process by using the #{tee}# command. We
+recommend doing this automatically with an #{auto/build}# script; see
+{Managing a configuration}#managing-a-configuration for details).
code{
@@ -85,18 +89,33 @@ code{
}code
-For runtime log, live-boot stores a log in #{/var/log/live.log}# (or
+At boot time, live-boot stores a log in #{/var/log/live.log}# (or
#{/var/log/live-boot.log}#).
Additionally, to rule out other errors, it is always a good idea to tar up
-your config directory and upload it somewhere (do *{not}* send it as an
-attachment to the mailinglist), so that we can try to reproduce the errors
-you encountered.
+your #{config/}# directory and upload it somewhere (do *{not}* send it as an
+attachment to the mailing list), so that we can try to reproduce the errors
+you encountered. If this is difficult (e.g. due to size) you can use the
+output of #{lb config --dump}# which produces a summary of your config tree
+(i.e. lists files in subdirectories of #{config/}# but does not include
+them).
Remember to send in any logs that were produced with English locale
settings, e.g. run your live-build commands with a leading #{LC_ALL=C}# or
#{LC_ALL=en_US}#.
+2~ Isolate the failing case if possible
+
+If possible, isolate the failing case to the smallest possible change that
+breaks. It is not always easy to do this, so if you can't manage it for your
+report, don't worry. However, if you plan your development cycle well, using
+small enough change sets per iteration, you may be able to isolate the
+problem by constructing a simpler 'base' configuration that closely matches
+your actual configuration plus just the broken change set added to it. If
+you have a hard time sorting out which of your changes broke, it may be that
+you are including too much in each change set and should develop in smaller
+increments.
+
2~ Use the correct package to report the bug against
Where does the bug appear?
@@ -121,9 +140,9 @@ can fail. If a bug appears here, check if the error is also reproducible on
a normal system.
If this is the case, this is not a bug in Debian Live, but rather in Debian
-- please report it against the failing package. Running debootstrap
-seperately from the Live system build or running lb bootstrap with
-#{--debug}# will give you more information.
+- please report it against the failing package. Running #{debootstrap}#
+separately from the Live system build or running #{lb bootstrap --debug}#
+will give you more information.
Also, if you are using a local mirror and/or any of sort of proxy and you
are experiencing a problem, please always reproduce it first by
@@ -134,10 +153,10 @@ bootstrapping from an official mirror.
If your image does not boot, please report it to the mailing list together
with the information requested in {Collect
information}#collect-information. Do not forget to mention, how/when the
-image failed, in Qemu, VMWare or real hardware. If you are using a
-virtualization technology of any kind, please always run it on real hardware
-before reporting a bug. Providing a screenshot of the failure is also very
-helpful.
+image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using
+a virtualization technology of any kind, please always run it on real
+hardware before reporting a bug. Providing a screenshot of the failure is
+also very helpful.
3~ At run time
--
live-manual
More information about the debian-live-changes
mailing list