All translations have been updated for the Debian Bookworm version of the Debian Administrator's Handbook. Due to Debian Trixie being released soon, we hope to release the Trixie version of the book soon as well. Thus, there might only be a brief period to translate the Bookworm version of the book this time. We thank everybody who has contributed so far and hope that you continue your great work.

Translation status

322 Strings 93%
Browse Translate
7,350 Words 80%
65,713 Characters 80%

Strings status

Strings Words Characters
322 7,350 65,713
All strings Browse Translate Zen
301 5,948 53,062
Translated strings Browse Translate Zen
21 1,402 12,651
Unfinished strings Browse Translate Zen
1 30 221
Untranslated strings Browse Translate Zen
20 1,372 12,430
Strings marked for edit Browse Translate Zen
30 119 2,428
Translated strings with dismissed checks Browse Translate Zen

Overview

Project website debian-handbook.info
Instructions for translators

https://debian-handbook.info/contribute/ Mailing list for translators: <debian-handbook-translators@lists.alioth.debian.org
Project maintainers User avatar rhertzogUser avatar pereUser avatar dleidert
Translation license GNU General Public License v2.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://salsa.debian.org/hertzog/debian-handbook.git
Repository branch bookworm/main
Last remote commit Update PO files c274c239
User avatar dleidert authored yesterday
Last commit in Weblate sv-SE: Translated using Weblate. e847ba88
User avatar hanklank authored 3 hours ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
File mask */15_debian-packaging.po
Translation file Download pt-BR/15_debian-packaging.po
Last change April 22, 2025, 2:05 a.m.
Last change made by None
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 322 7,350 65,713
Translated 93% 301 80% 5,948 80% 53,062
Needs editing 6% 20 18% 1,372 18% 12,430
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 1 1% 30 1% 221
Last 12 months Previous

Activity in last 12 months

2 changes 0 changes 2 changes 0 changes 29 changes 0 changes 2 changes 128 changes 155 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

7,350
Hosted words
322
Hosted strings
93%
Translated
12
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−6%
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “pt-BR/15_debian-packaging.po” file was changed. yesterday
User avatar None

String added in the repository
Building the package is then as easy as running <command>gbp buildpackage</command> in the Git tree. It will start a package build in a Debian <emphasis role="distribution">Bookworm</emphasis> chroot using <command>sbuild</command>. When the build succeeds, the created files are checked running the <command>autopkgtest</command>-testsuite (if defined). All the various options are explained in <citerefentry><refentrytitle>gbp.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> and <filename>/etc/git-buildpackage/gbp.conf</filename>.
Construir o pacote é tão fácil quanto executar <command>gbp buildpackage</command> na árvore do Git. Ele iniciará a construção de um pacote em um chroot do Debian <emphasis role="distribution">Bullseye</emphasis> usando <command>sbuild</command>. Quando a construção é bem-sucedida, os arquivos criados são verificados executando o <command>autopkgtest</command>-testsuite (se definido). Todas as várias opções são explicadas em <citerefentry><refentrytitle>gbp.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> e <filename>/etc/git-buildpackage/gbp.conf</filename> .
yesterday
User avatar None

Source string changed
Building the package is then as easy as running <command>gbp buildpackage</command> in the Git tree. It will start a package build in a Debian <emphasis role="distribution">Bullseyeookworm</emphasis> chroot using <command>sbuild</command>. When the build succeeds, the created files are checked running the <command>autopkgtest</command>-testsuite (if defined). All the various options are explained in <citerefentry><refentrytitle>gbp.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> and <filename>/etc/git-buildpackage/gbp.conf</filename>.
yesterday
User avatar None

String added in the repository
<![CDATA[[DEFAULT]
builder = sbuild -d bookworm --build-dep-resolver=aptitude -s --source-only-changes --build-failed-commands "%SBUILD_SHELL"
pristine-tar = true

[buildpackage]
sign-tags = true
keyid = XXXX
postbuild = autopkgtest --user debci --apt-upgrade -s "$GBP_CHANGES_FILE" -- lxc --sudo autopkgtest-bookworm-amd64
export-dir = /tmp/build-area/
notify = off

[import-orig]
filter-pristine-tar = true
sign-tags = true

[pq]
drop = true
]]>
<![CDATA[[DEFAULT]
builder = sbuild -d bullseye --build-dep-resolver=aptitude -s --source-only-changes --build-failed-commands "%SBUILD_SHELL"
pristine-tar = true

[buildpackage]
sign-tags = true
keyid = XXXX
postbuild = autopkgtest --user debci --apt-upgrade -s "$GBP_CHANGES_FILE" -- lxc --sudo autopkgtest-bullseye-amd64
export-dir = /tmp/build-area/
notify = off

[import-orig]
filter-pristine-tar = true
sign-tags = true

[pq]
drop = true
]]>
yesterday
User avatar None

Source string changed
<![CDATA[[DEFAULT]
builder = sbuild -d bullseyeookworm --build-dep-resolver=aptitude -s --source-only-changes --build-failed-commands "%SBUILD_SHELL"
pristine-tar = true

[buildpackage]
sign-tags = true
keyid = XXXX
postbuild = autopkgtest --user debci --apt-upgrade -s "$GBP_CHANGES_FILE" -- lxc --sudo autopkgtest-bullseyeookworm-amd64
export-dir = /tmp/build-area/
notify = off

[import-orig]
filter-pristine-tar = true
sign-tags = true

[pq]
drop = true
]]>
yesterday
User avatar None

String added in the repository
Creating a quality Debian package is not always a simple task. And becoming a package maintainer takes some learning, both with theory and practice in technical and legal matters. It is not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available.
Criar um pacote Debian de qualidade não é sempre uma tarefa simples, e se tornar um mantenedor de pacote requer aprendizado, tanto na teoria quanto na prática em questões técnicas e legais. Não é simplesmente uma questão de construir ou instalar programas; em vez disso, a maior parte da complexidade vem do entendimento de problemas e conflitos, e mais geralmente as interações, com a miríade de outros pacotes disponíveis.
yesterday
User avatar None

Source string changed
Creating a quality Debian package is not always a simple task, a. And becoming a package maintainer takes some learning, both with theory and practice in technical and legal matters. It is not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available.
yesterday
User avatar None

String added in the repository
As mentioned earlier, tools like <command>aptly</command> and <command>reprepro</command> come with built-in support for creating a signed archive and are often the better choice for larger or more complex archive setups.
 
yesterday
User avatar None

String added in the repository
Falcot Corp gradually started maintaining a number of Debian packages, either locally modified from existing packages or created from scratch to distribute internal data and programs.
A Falcot Corp gradualmente começou a manter alguns pacotes Debian modificados localmente a partir de pacotes existentes ou criados do zero para distribuir dados e programas internos.
yesterday
User avatar None

Source string changed
Falcot Corp gradually started maintaining a number of Debian packages, either locally modified from existing packages or created from scratch to distribute internal data and programs.
yesterday
Browse all translation changes