| Language | Translated | Untranslated | Untranslated words | Checks | Suggestions | Comments | |
|---|---|---|---|---|---|---|---|
Arabic (Morocco)
GPL-2.0
|
68% | 111 | 4,436 | 73 | |||
|
|
|||||||
|
Catalan
GPL-2.0
|
|||||||
|
|
|||||||
|
Chinese (Simplified)
GPL-2.0
|
|||||||
|
|
|||||||
|
Chinese (Traditional)
GPL-2.0
|
67% | 115 | 4,516 | 46 | |||
|
|
|||||||
|
Croatian
GPL-2.0
|
15% | 295 | 9,394 | 41 | |||
|
|
|||||||
|
Czech
GPL-2.0
|
67% | 115 | 4,516 | 63 | |||
|
|
|||||||
|
Danish
GPL-2.0
|
0% | 350 | 9,774 | ||||
|
|
|||||||
|
Dutch
GPL-2.0
|
82% | 62 | 3,165 | 54 | |||
|
|
|||||||
English
GPL-2.0
|
192 | ||||||
|
|
|||||||
|
French
GPL-2.0
|
68% | 110 | 4,425 | 67 | 1 | ||
|
|
|||||||
|
German
GPL-2.0
|
|||||||
|
|
|||||||
|
Greek
GPL-2.0
|
0% | 347 | 9,769 | 1 | |||
|
|
|||||||
|
Indonesian
GPL-2.0
|
|||||||
|
|
|||||||
|
Italian
GPL-2.0
|
75% | 86 | 3,443 | 34 | |||
|
|
|||||||
|
Japanese
GPL-2.0
|
68% | 109 | 4,056 | 153 | |||
|
|
|||||||
|
Korean
GPL-2.0
|
0% | 348 | 9,771 | 14 | |||
|
|
|||||||
|
Norwegian Bokmål
GPL-2.0
|
|||||||
|
|
|||||||
|
Persian
GPL-2.0
|
67% | 115 | 4,516 | 79 | |||
|
|
|||||||
|
Polish
GPL-2.0
|
44% | 194 | 7,654 | 32 | |||
|
|
|||||||
|
Portuguese (Brazil)
GPL-2.0
|
|||||||
|
|
|||||||
|
Romanian
GPL-2.0
|
0% | 349 | 9,772 | 14 | |||
|
|
|||||||
|
Russian
GPL-2.0
|
67% | 115 | 4,516 | 58 | 9 | 3 | |
|
|
|||||||
|
Spanish
GPL-2.0
|
1 | ||||||
|
|
|||||||
|
Swedish
GPL-2.0
|
19% | 281 | 9,361 | 19 | |||
|
|
|||||||
|
Turkish
GPL-2.0
|
0% | 350 | 9,774 | ||||
|
|
|||||||
|
Vietnamese
GPL-2.0
|
67% | 115 | 4,516 | 122 | |||
|
|
|||||||
Please sign in to see the alerts.
| 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 |
 rhertzog
 pere
|
| Translation process |
|
| Translation license | GNU General Public License v2.0 or later |
| Source code repository |
https://salsa.debian.org/hertzog/debian-handbook.git
|
| Repository branch | buster/master |
| Last remote commit |
Merge branch 'buster/master' into 'buster/master'
ee675503
rhertzog authored 4 weeks ago |
| Weblate repository |
https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
|
| Filemask | */05_packaging-system.po |
| Languages | 26 |
| Source strings | 350 |
| Source words | 9,774 |
| Source characters | 87,118 |
| Hosted strings | 9,100 |
| Hosted words | 254,124 |
| Hosted characters | 2,265,068 |
GilB
fred_maranhao<computeroutput>$ </computeroutput><userinput>fakeroot alien --to-deb phpMyAdmin-4.7.5-2.fc28.noarch.rpm</userinput>
<computeroutput>phpmyadmin_4.7.5-3_all.deb generated
$ </computeroutput><userinput>ls -s phpmyadmin_4.7.5-3_all.deb</userinput>
<computeroutput> 4356 phpmyadmin_4.7.5-3_all.deb</computeroutput>
<computeroutput>$ </computeroutput><userinput>fakeroot alien --to-deb phpMyAdmin-
<computeroutput>phpmyadmin_
$ </computeroutput><userinput>ls -s phpmyadmin_
<computeroutput>
If you regularly use the <command>alien</command> program to install RPM packages coming from one of your providers, do not hesitate to write to them and amicably express your strong preference for the <filename>.deb</filename> format. Note that the format of the package is not everything: a <filename>.deb</filename> package built with <command>alien</command> or prepared for a version of Debian different than that which you use, or even for a derivative distribution like Ubuntu, would probably not offer the same level of quality and integration as a package specifically developed for Debian <emphasis role="distribution">Buster</emphasis>.
Se você usa regularmente o programa <command>alien</command> para instalar pacotes RPM dos seus fornecedores, não hesite em escrever para eles e amigavelmente expressar sua forte preferência pelo formato <filename>.deb</filename>. Observe que o formato do pacote não é tudo: um pacote <filename>.deb</filename> construído com o <command>alien</command> ou preparado para uma versão do Debian diferente da que você usa, ou mesmo sendo uma derivada como o ubuntu, provavelmente não vai oferecer o mesmo nível de qualidade e integração que um pacote feito especificamente para o Debian <emphasis role="distribution">JessieBuster</emphasis>.
<computeroutput>$ </computeroutput><userinput>dpkg -s gcc-8-base
</userinput><computeroutput>dpkg-query: error: --status needs a valid package name but 'gcc-8-base' is not: ambiguous package name 'gcc-8-base' with more than one installed instance
Use --help for help about querying packages.
$ </computeroutput><userinput>dpkg -s gcc-8-base:amd64 gcc-8-base:armhf | grep ^Multi
</userinput><computeroutput>Multi-Arch: same
Multi-Arch: same
$ </computeroutput><userinput>dpkg -L libgcc1:amd64 |grep .so
</userinput><computeroutput>/lib/x86_64-linux-gnu/libgcc_s.so.1
$ </computeroutput><userinput>dpkg -S /usr/share/doc/gcc-8-base/copyright
</userinput><computeroutput>gcc-8-base:amd64, gcc-8-base:armhf: /usr/share/doc/gcc-8-base/copyright
</computeroutput>
</userinput><computeroutput>dpkg-query: error: --status needs a valid package name but 'gcc-8-base' is not: ambiguous package name 'gcc-8-base' with more than one installed instance
Use --help for help about querying packages.
$ </computeroutput><userinput>dpkg -s gcc-8-base:amd64 gcc-8-base:armhf | grep ^Multi
</userinput><computeroutput>Multi-Arch: same
Multi-Arch: same
$ </computeroutput><userinput>dpkg -L libgcc1:amd64 |grep .so
</userinput><computeroutput>/lib/x86_64-linux-gnu/libgcc_s.so.1
$ </computeroutput><userinput>dpkg -S /usr/share/doc/gcc-8-base/copyright
</userinput><computeroutput>gcc-8-base:amd64, gcc-8-base:armhf: /usr/share/doc/gcc-8-base/copyright
</computeroutput>
<computeroutput>$ </computeroutput><userinput>dpkg -s gcc-4.98-base
</userinput><computeroutput>dpkg-query: error: --status needs a valid package name but 'gcc-4.98-base' is not: ambiguous package name 'gcc-4.98-base' with more than one installed instance
Use --help for help about querying packages.
$ </computeroutput><userinput>dpkg -s gcc-4.98-base:amd64 gcc-4.98-base:armhf | grep ^Multi
</userinput><computeroutput>Multi-Arch: same
Multi-Arch: same
$ </computeroutput><userinput>dpkg -L libgcc1:amd64 |grep .so
</userinput><computeroutput>/lib/x86_64-linux-gnu/libgcc_s.so.1
$ </computeroutput><userinput>dpkg -S /usr/share/doc/gcc-4.98-base/copyright
</userinput><computeroutput>gcc-4.98-base:amd64, gcc-4.98-base:armhf: /usr/share/doc/gcc-4.98-base/copyright
</computeroutput>
</userinput><computeroutput>dpkg-query: error: --status needs a valid package name but 'gcc-
Use --help for help about querying packages.
$ </computeroutput><userinput>dpkg -s gcc-
</userinput><computeroutput>Multi-Arch: same
Multi-Arch: same
$ </computeroutput><userinput>dpkg -L libgcc1:amd64 |grep .so
</userinput><computeroutput>/lib/x86_64-linux-gnu/libgcc_s.so.1
$ </computeroutput><userinput>dpkg -S /usr/share/doc/gcc-
</userinput><computeroutput>gcc-
</computeroutput>
To make multi-arch actually useful and usable, libraries had to be repackaged and moved to an architecture-specific directory so that multiple copies (targeting different architectures) can be installed alongside. Such updated packages contain the “<literal>Multi-Arch: same</literal>” header field to tell the packaging system that the various architectures of the package can be safely co-installed (and that those packages can only satisfy dependencies of packages of the same architecture). The most important libraries have been converted since the introduction of multi-arch in Debian 7 <emphasis role="distribution">Wheezy</emphasis>, but there are many libraries that will likely never be converted unless someone specifically requests it (through a bug report for example).
Para fazer multi-arqu realmente útil e utilizável, as bibliotecas tiveram de ser reembalpacotadas e movidas para um diretório de uma arquitetura específica, de modo que várias cópias (segmentações deapontando para diferentes arquiteturas) podudessem ser instaladas lado ao lado. Tais pacotes atualizados conteém o campo de cabeçalho “<literal>Multi-Arqu: same</literal>” para dizer ao sistema de embalagempacotamento que as várias arquiteturas do pacote podem ser seguramente co-instaladas (e que os pacotes só podem satisfazer as dependências de pacotes da mesma arquitectura). Desde que o multi-arqu fez sua estréiaAs bibliotecas mais importantes foram convertidas desde a introdução do multi-arch no Debian 7 <emphasis role="distribution">Wheezy</emphasis>, nem todas as bibliotecas foram convertidas aindamas existem muitas bibliotecas que provavelmente nunca serão convertidas a menos que alguém peça especificamente por elas (através de um bugreport, por exemplo).
There are multiple use cases for multi-arch, but the most popular ones are the possibility to execute (sometimes proprietary) 32 bit binaries (i386) on 64 bit systems (amd64), and the possibility to cross-compile software for a platform or an architecture different from the host one.
Existem vários casos de uso para multi-arquch, mas os mais popular ées são a possibilidade de executar binários (algumas vezes proprietários) de 32 bits (i386) em sistemas de 64 bits (AMDamd64), em particular, uma vez que vários aplicativos populares proprietários (como o Skype) são fornecidos apenas em versões 32 bit a possibilidade de fazer compilação cruzada de programas para uma plataforma ou arquitetura diferentes da máquina.
APT will automatically detect when dpkg has been configured to support foreign architectures and will start downloading the corresponding <filename>Packages</filename> files during its update process.
O APT irá detectar automaticamente quando o dpkg foi configurado para suportar arquiteturas estrangeiras e vai começar a fazer o download dbaixar os arquivos <filename>pPacotkages</filename> correspondentes durante seu processo de atualização.
postrm/usr</filename></primary>