1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207
|
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2020-05-17 17:54+0200\n"
"PO-Revision-Date: 2014-07-13 15:49+0200\n"
"Last-Translator: Dag Velovic <dag.velovic@gmail.com>\n"
"Language-Team: Croatian <https://debian.weblate.org/projects/debian-handbook/06_apt/hr/>\n"
"Language: hr-HR\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
"X-Generator: Weblate 1.10-dev\n"
msgid "apt"
msgstr ""
msgid "apt-get"
msgstr ""
msgid "apt-cache"
msgstr ""
msgid "aptitude"
msgstr ""
msgid "synaptic"
msgstr ""
msgid "sources.list"
msgstr ""
msgid "apt-cdrom"
msgstr ""
msgid "Maintenance and Updates: The APT Tools"
msgstr ""
msgid "What makes Debian so popular with administrators is how easily software can be installed and how easily the whole system can be updated. This unique advantage is largely due to the <emphasis>APT</emphasis> program, which Falcot Corp administrators studied with enthusiasm."
msgstr ""
msgid "<primary>APT</primary>"
msgstr ""
msgid "<primary>Advanced Package Tool</primary><seealso>APT</seealso>"
msgstr ""
msgid "<acronym>APT</acronym> is the abbreviation for Advanced Package Tool. What makes this program “advanced” is its approach to packages. It doesn't simply evaluate them individually, but it considers them as a whole and produces the best possible combination of packages depending on what is available and compatible according to dependencies."
msgstr ""
msgid "<emphasis>VOCABULARY</emphasis> Package source and source package"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>source package</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary>package source</primary><seealso>repository</seealso>"
msgstr ""
msgid "The word <emphasis>source</emphasis> can be ambiguous. A \"source package\" — a package containing the source code of a program — should not be confused with a \"package source\" — a repository (website, FTP server, CD-ROM, local directory, etc.) which contains packages."
msgstr ""
msgid "APT needs to be given a “list of package sources (repositories)”: the file <filename>/etc/apt/sources.list</filename> will list the different repositories that publish Debian packages. APT will then import the list of packages published by each of these sources. This operation is achieved by downloading <filename>Packages.xz</filename> files or a variant such as <filename>Packages.gz</filename> or <filename>.bz2</filename> (using a different compression method) in case of a source of binary packages and by analyzing their contents. In case of a source of source packages, APT downloads <filename>Sources.xz</filename> files or a variant using a different compression method. When an old copy of these files is already present, APT can update it by only downloading the differences (see sidebar <xref linkend=\"sidebar.apt-pdiff\" />)."
msgstr ""
msgid "<primary><filename>Packages.xz</filename></primary>"
msgstr ""
msgid "<primary><filename>Packages.gz</filename></primary>"
msgstr ""
msgid "<primary><filename>Packages.bz2</filename></primary>"
msgstr ""
msgid "<primary><filename>Sources.xz</filename></primary>"
msgstr ""
msgid "<primary><filename>Sources.gz</filename></primary>"
msgstr ""
msgid "<primary><filename>Sources.bz2</filename></primary>"
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> <command>gzip</command>, <command>bzip2</command>, <command>LZMA</command> and <command>XZ</command> Compression"
msgstr ""
msgid "<primary><command>gzip</command></primary>"
msgstr ""
msgid "<primary><command>bzip2</command></primary>"
msgstr ""
msgid "<primary><command>lzma</command></primary>"
msgstr ""
msgid "<primary><command>xz</command></primary>"
msgstr ""
msgid "A <filename>.gz</filename> extension refers to a file compressed with the <command>gzip</command> utility. <command>gzip</command> is the fast and efficient traditional Unix utility to compress files. Newer tools achieve better rates of compression but require more resources (computation time and memory) to compress and uncompress a file. Among them, and by order of appearance, there are <command>bzip2</command> (generating files with a <filename>.bz2</filename> extension), <command>lzma</command> (generating <filename>.lzma</filename> files) and <command>xz</command> (generating <filename>.xz</filename> files)."
msgstr ""
msgid "Filling in the <filename>sources.list</filename> File"
msgstr ""
msgid "<primary><filename>sources.list</filename></primary>"
msgstr ""
msgid "<primary>source</primary><secondary>of packages</secondary>"
msgstr ""
msgid "<primary>package</primary><secondary>source of</secondary>"
msgstr ""
msgid "<primary><filename>/etc/apt/sources.list</filename></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/etc/apt/sources.list</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Syntax"
msgstr ""
msgid "Each active line in the <filename>/etc/apt/sources.list</filename> file represents a package source (repository) and is made of at least three parts separated by spaces. For a complete description of the file format and the accepted entry compositions see <citerefentry><refentrytitle>sources.list</refentrytitle><manvolnum>5</manvolnum></citerefentry>."
msgstr ""
msgid "Example entry format in <filename>/etc/apt/sources.list</filename>"
msgstr ""
msgid ""
"deb url distribution component1 component2 component3 [..] componentX\n"
"deb-src url distribution component1 component2 component3 [..] componentX\n"
" "
msgstr ""
msgid "The first field indicates the source type:"
msgstr ""
msgid "<literal>deb</literal>"
msgstr ""
msgid "package source (repository) of binary packages"
msgstr ""
msgid "<literal>deb-src</literal>"
msgstr ""
msgid "package source (repository) of source packages"
msgstr ""
msgid "The second field gives the base URL of the source. Combined with the filenames listed in the <filename>Packages.xz</filename> files, it must give a full and valid URL. This can consist in a Debian mirror or in any other package archive set up by a third party. The URL can start with <literal>file://</literal> to indicate a local source installed in the system's file hierarchy, with <literal>http://</literal> or <literal>https://</literal> to indicate a source accessible from a web server server, or with <literal>ftp://</literal> or <literal>ftps://</literal> for a source available on an FTP server. The URL can also start with <literal>cdrom:</literal> for CD-ROM/DVD/Blu-ray disc based installations, although this is less frequent, since network-based installation methods are eventually more common."
msgstr ""
msgid "The syntax of the last field depends on the structure of the repository. In the simplest case, you can simply indicate a subdirectory (with a required trailing slash) of the desired source. This is often a simple “<filename>./</filename>” which refers to the absence of a subdirectory. The packages are then directly at the specified URL. But in the most common case, the repositories will be structured like a Debian mirror, with multiple distributions, each having multiple components. In those cases, name the chosen distribution by its “codename” — see the list in sidebar <xref linkend=\"sidebar.bruce-perens\" /> — or by the corresponding “suite” <literal>oldstable</literal>, <literal>stable</literal>, <literal>testing</literal>, <literal>unstable</literal>) and then the components to enable. A typical Debian mirror provides the components <literal>main</literal>, <literal>contrib</literal>, and <literal>non-free</literal>."
msgstr ""
msgid "<emphasis>VOCABULARY</emphasis> The <literal>main</literal>, <literal>contrib</literal> and <literal>non-free</literal> archives"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>component</primary><secondary><literal>main</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary><literal>main</literal>, component</primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>component</primary><secondary><literal>contrib</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary><literal>contrib</literal>, component</primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>component</primary><secondary><literal>non-free</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary><literal>non-free</literal>, component</primary>"
msgstr ""
msgid "<primary>component (of a repository)</primary>"
msgstr ""
msgid "Debian uses three components to differentiate packages according to the licenses chosen by the authors of each work. <literal>Main</literal> gathers all packages which fully comply with the <ulink url=\"https://www.debian.org/social_contract.html#guidelines\">Debian Free Software Guidelines</ulink>."
msgstr ""
msgid "The <literal>non-free</literal> component is different because it contains software which does not (entirely) conform to these principles but which can, nevertheless, be distributed without restrictions. This archive, which is not officially part of Debian, is a service for users who could need some of those programs and, nowadays, also require the firmware for their hardware. However, Debian always recommends giving priority to free software. The existence of this component represents a considerable problem for Richard M. Stallman and keeps the Free Software Foundation from recommending Debian to users."
msgstr ""
msgid "<literal>Contrib</literal> (contributions) is a set of open source software which cannot function without some non-free elements — these elements can be software from the <literal>non-free</literal> section, or non-free files such as game ROMs, BIOS of consoles, etc. — or some elements, not available from the Debian <literal>main</literal> archive at all. The <literal>contrib</literal> component also includes free software whose compilation requires proprietary elements. This was initially the case for the OpenOffice.org office suite, which used to require a proprietary Java environment."
msgstr ""
msgid "<emphasis>TIP</emphasis> <filename>/etc/apt/sources.list.d/*.list</filename> files"
msgstr ""
msgid "<primary><filename>/etc/apt/sources.list.d</filename></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/etc/apt/sources.list.d</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "If many package sources are referenced, it can be useful to split them in multiple files. Each part is then stored in <filename>/etc/apt/sources.list.d/<replaceable>filename</replaceable>.list</filename> (see sidebar <xref linkend=\"sidebar.directory.d\" />)."
msgstr ""
msgid "<primary><command>apt-cdrom</command></primary>"
msgstr ""
msgid "The <literal>cdrom</literal> entries describe the CD/DVD-ROMs you have. Contrary to other entries, a CD-ROM is not always available since it has to be inserted into the drive and since only one disc can be read at a time. For those reasons, these sources are managed in a slightly different way, and need to be added with the <command>apt-cdrom</command> program, usually executed with the <literal>add</literal> parameter. The latter will then request the disc to be inserted in the drive and will browse its contents looking for <filename>Packages</filename> files. It will use these files to update its database of available packages (this operation is usually done by the <command>apt update</command> command). From then on, APT can require the disc to be inserted if it needs one of its packages."
msgstr ""
msgid "Repositories for <emphasis role=\"distribution\">Stable</emphasis> Users"
msgstr ""
msgid "Here is a standard <filename>sources.list</filename> for a system running the <emphasis role=\"distribution\">Stable</emphasis> version of Debian:"
msgstr ""
msgid "<filename>/etc/apt/sources.list</filename> file for users of Debian Stable"
msgstr ""
msgid "<primary><filename>/etc/apt/sources.list</filename></primary><secondary>Example</secondary><tertiary><literal>stable</literal></tertiary>"
msgstr ""
msgid ""
"# Security updates\n"
"deb http://security.debian.org/ buster/updates main contrib non-free\n"
"deb-src http://security.debian.org/ buster/updates main contrib non-free\n"
"\n"
"## Debian mirror\n"
"\n"
"# Base repository\n"
"deb https://deb.debian.org/debian buster main contrib non-free\n"
"deb-src https://deb.debian.org/debian buster main contrib non-free\n"
"\n"
"# Stable updates\n"
"deb https://deb.debian.org/debian buster-updates main contrib non-free\n"
"deb-src https://deb.debian.org/debian buster-updates main contrib non-free\n"
"\n"
"# Stable backports\n"
"deb https://deb.debian.org/debian buster-backports main contrib non-free\n"
"deb-src https://deb.debian.org/debian buster-backports main contrib non-free"
msgstr ""
msgid "This file lists all sources of packages associated with the <emphasis role=\"distribution\">Buster</emphasis> version of Debian (the current <emphasis role=\"distribution\">Stable</emphasis> suite as of this writing). In the example above, we opted to name “buster” explicitly instead of using the corresponding “stable“ aliases (<literal>stable</literal>, <literal>stable-updates</literal>, <literal>stable-backports</literal>) because we don't want to have the underlying distribution changed outside of our control when the next stable release comes out."
msgstr ""
msgid "Most packages will come from the “base repository” which contains all packages but is seldom updated (about once every 2 months for a “point release”). The other repositories are partial (they do not contain all packages) and can host updates (packages with newer version) that APT might install. The following sections will explain the purpose and the rules governing each of those repositories."
msgstr ""
msgid "Note that when the desired version of a package is available on several repositories, the first one listed in the <filename>sources.list</filename> file will be used. For this reason, non-official sources are usually added at the end of the file."
msgstr ""
msgid "As a side note, most of what this section says about <emphasis role=\"distribution\">Stable</emphasis> applies equally well to <emphasis role=\"distribution\">Oldstable</emphasis> since the latter is just an older <emphasis role=\"distribution\">Stable</emphasis> that is maintained in parallel."
msgstr ""
msgid "Security Updates"
msgstr ""
msgid "<primary><literal>security.debian.org</literal></primary>"
msgstr ""
msgid "<primary>security updates</primary>"
msgstr ""
msgid "<primary>updates</primary><secondary>security updates</secondary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>CVE</primary><secondary>Common Vulnerabilities and Exposures</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>DSA</primary><secondary>Debian Security Advisory</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary>Common Vulnerabilities and Exposures</primary><seealso>CVE</seealso>"
msgstr ""
msgid "<primary>Debian Security Advisory</primary><seealso>DSA</seealso>"
msgstr ""
msgid "<primary>debian-security-announce</primary>"
msgstr ""
msgid "Debian takes security seriously. Known software vulnerabilities in Debian are tracked in the <ulink url=\"https://security-tracker.debian.org\">Security Bug Tracker</ulink> and usually get fixed in a reasonable timeframe. The security updates are not hosted on the usual network of Debian mirrors but on <literal>security.debian.org</literal>, a small set of machines maintained by the <link linkend=\"dsa-team\">Debian System Administrators</link>. This archive contains security updates prepared by the Debian Security Team and/or by package maintainers for the <emphasis role=\"distribution\">Stable</emphasis> and <emphasis role=\"distribution\">Oldstable</emphasis> distribution."
msgstr ""
msgid "The server can also host security updates for <emphasis role=\"distribution\">Testing</emphasis> but this doesn't happen very often since those updates tend to reach the <emphasis role=\"distribution\">Testing</emphasis> suite via the regular flow of updates coming from <emphasis role=\"distribution\">Unstable</emphasis>."
msgstr ""
msgid "For serious issues, the security team issues a <literal>Debian Security Advisory</literal> (<acronym>DSA</acronym>) and announces it together with the security update on the <email>debian-security-announce@lists.debian.org</email> mailing list (<ulink url=\"https://lists.debian.org/debian-security-announce/\">archive</ulink>)."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-security-announce@lists.debian.org</email></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Stable Updates"
msgstr ""
msgid "<primary>stable updates</primary>"
msgstr ""
msgid "<primary><literal>stable-updates</literal></primary>"
msgstr ""
msgid "<primary><literal>buster-updates</literal></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary>buster</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary>stable</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Stable updates are not security sensitive but are deemed important enough to be pushed to users before the next stable point release."
msgstr ""
msgid "This repository will typically contain fixes for critical and serious bugs which could not be fixed before release or which have been introduced by subsequent updates. Depending on the urgency, it can also contain updates for packages that have to evolve over time, like <emphasis role=\"pkg\">spamassassin</emphasis>'s spam detection rules, <emphasis role=\"pkg\">clamav</emphasis>'s virus database, the daylight-saving time rules of all timezones (<emphasis role=\"pkg\">tzdata</emphasis>), the <acronym>ESR</acronym> version of Firefox (<emphasis role=\"pkg\">firefox-esr</emphasis>) or cryptographic keyrings like <emphasis role=\"pkg\">debian-archive-keyring</emphasis>."
msgstr ""
msgid "In practice, this repository is a subset of the <literal>proposed-updates</literal> repository, carefully selected by the <link linkend=\"srm-team\">Stable Release Managers</link>. All updates are announced on the <email>debian-stable-announce@lists.debian.org</email> mailing list (<ulink url=\"https://lists.debian.org/debian-stable-announce/\">archive</ulink>) and will be included in the next <emphasis role=\"distribution\">Stable</emphasis> point release anyway."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-stable-announce@lists.debian.org</email></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "deb https://deb.debian.org/debian buster-updates main contrib non-free"
msgstr ""
msgid "Proposed Updates"
msgstr ""
msgid "<primary><literal>proposed-updates</literal></primary>"
msgstr ""
msgid "<primary><literal>stable-proposed-updates</literal></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary>proposed</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary><literal>stable-proposed</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary><literal>stable</literal>, proposed</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Once published, the <emphasis role=\"distribution\">Stable</emphasis> distribution is only updated about once every 2 months. The <literal>proposed-updates</literal> repository is where the expected updates are prepared (under the supervision of the Stable Release Managers)."
msgstr ""
msgid "The security and stable updates documented in the former sections are always included in this repository, but there is more too, because package maintainers also have the opportunity to fix important bugs that do not deserve an immediate release."
msgstr ""
msgid "Anyone can use this repository to test those updates before their official publication. The extract below uses the <literal>buster-proposed-updates</literal> alias which is both more explicit and more consistent since <literal>stretch-proposed-updates</literal> also exists (for the <emphasis role=\"distribution\">Oldstable</emphasis> updates):"
msgstr ""
msgid "deb https://deb.debian.org/debian buster-proposed-updates main contrib non-free"
msgstr ""
msgid "Stable Backports"
msgstr ""
msgid "<primary><literal>stable-backports</literal></primary>"
msgstr ""
msgid "<primary>backport</primary>"
msgstr ""
msgid "<primary>updates</primary><secondary>backports</secondary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary><literal>stable-backports</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>updates</primary><secondary><literal>stable</literal>, backports</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "The <literal>stable-backports</literal> repository hosts “package backports”. The term refers to a package of some recent software which has been recompiled for an older distribution, generally for <emphasis role=\"distribution\">Stable</emphasis>."
msgstr ""
msgid "When the distribution becomes a little dated, numerous software projects have released new versions that are not integrated into the current <emphasis role=\"distribution\">Stable</emphasis> suite, which is only modified to address the most critical problems, such as security issues. Since the <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis> suites can be more risky, package maintainers sometimes voluntarily offer recompilations of recent software applications for <emphasis role=\"distribution\">Stable</emphasis>, which has the advantage to users and system administrators to limit potential instability to a small number of chosen packages. The page <ulink url=\"https://backports.debian.org\" /> provides more information."
msgstr ""
msgid "<primary><literal>backports.debian.org</literal></primary><seealso>backports</seealso>"
msgstr ""
msgid "Backports from <literal>stable-backports</literal> are only created from packages available in <emphasis role=\"distribution\">Testing</emphasis>. This ensures that all installed backports will be upgradable to the corresponding stable version once the next stable release of Debian is available."
msgstr ""
msgid "Even though this repository provides newer versions of packages, <literal>APT</literal> will not install them unless you give explicit instructions to do so (or unless you have already done so with a former version of the given backport):"
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>sudo apt-get install <replaceable>package</replaceable>/buster-backports\n"
"</userinput><computeroutput>$ </computeroutput><userinput>sudo apt-get install -t buster-backports <replaceable>package</replaceable>\n"
"</userinput>"
msgstr ""
msgid "Repositories for <emphasis role=\"distribution\">Testing</emphasis>/<emphasis role=\"distribution\">Unstable</emphasis> Users"
msgstr ""
msgid "Here is a standard <filename>sources.list</filename> for a system running the <emphasis role=\"distribution\">Testing</emphasis> or <emphasis role=\"distribution\">Unstable</emphasis> version of Debian:"
msgstr ""
msgid "<filename>/etc/apt/sources.list</filename> file for users of Debian <emphasis role=\"distribution\">Testing</emphasis>/<emphasis role=\"distribution\">Unstable</emphasis>"
msgstr ""
msgid "<primary><filename>/etc/apt/sources.list</filename></primary><secondary>Example</secondary><tertiary><literal>unstable</literal></tertiary>"
msgstr ""
msgid ""
"\n"
"# Unstable\n"
"deb https://deb.debian.org/debian unstable main contrib non-free\n"
"deb-src https://deb.debian.org/debian unstable main contrib non-free\n"
"\n"
"# Testing\n"
"deb https://deb.debian.org/debian testing main contrib non-free\n"
"deb-src https://deb.debian.org/debian testing main contrib non-free\n"
"\n"
"# Testing security updates\n"
"deb http://security.debian.org/ testing-security main contrib non-free\n"
"deb-src http://security.debian.org/ testing-security main contrib non-free\n"
"\n"
"# Stable\n"
"deb https://deb.debian.org/debian stable main contrib non-free\n"
"deb-src https://deb.debian.org/debian stable main contrib non-free\n"
"\n"
"# Stable security updates\n"
"deb http://security.debian.org/ stable/updates main contrib non-free\n"
"deb-src http://security.debian.org/ stable/updates main contrib non-free"
msgstr ""
msgid "<emphasis>NOTE</emphasis> Layout of security repositories"
msgstr ""
msgid "Starting with Debian 11 <emphasis role=\"distribution\">Bullseye</emphasis>, the codename of the repository providing security updates has been renamed from <literal><replaceable>codename</replaceable>/updates</literal> into <literal><replaceable>codename</replaceable>-security</literal> to avoid the confusion with <literal><replaceable>codename</replaceable>-updates</literal> (see <xref linkend=\"sect.apt-sources.list.stable.updates\" />)."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>APT::Default-Release</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "With this <filename>sources.list</filename> file APT will install packages from the <emphasis role=\"distribution\">Unstable</emphasis> suite. If that is not desired, use the <literal>APT::Default-Release</literal> setting (see <xref linkend=\"sect.apt-upgrade\" />) to instruct APT to pick packages from another suite (most likely <emphasis role=\"distribution\">Testing</emphasis> in this case)."
msgstr ""
msgid "There are good reasons to include all those repositories, even though a single one should be enough. <emphasis role=\"distribution\">Testing</emphasis> users will appreciate the possibility to cherry-pick a fixed package from <emphasis role=\"distribution\">Unstable</emphasis> when the version in <emphasis role=\"distribution\">Testing</emphasis> is affected by an annoying bug. On the opposite, <emphasis role=\"distribution\">Unstable</emphasis> users bitten by unexpected regressions have the possibility to downgrade packages to their (supposedly working) <emphasis role=\"distribution\">Testing</emphasis> version."
msgstr ""
msgid "The inclusion of <emphasis role=\"distribution\">Stable</emphasis> is more debatable but it often gives access to some packages, which have been removed from the development versions. It also ensures that you get the latest updates for packages, which have not been modified since the last stable release."
msgstr ""
msgid "The <emphasis role=\"distribution\">Experimental</emphasis> Repository"
msgstr ""
msgid "<primary><emphasis role=\"distribution\">experimental</emphasis></primary>"
msgstr ""
msgid "The archive of <emphasis role=\"distribution\">Experimental</emphasis> packages is present on all Debian mirrors, and contains packages which are not in the <emphasis role=\"distribution\">Unstable</emphasis> version yet because of their substandard quality — they are often software development versions or pre-versions (alpha, beta, release candidate…). A package can also be sent there after undergoing subsequent changes which can generate problems. The maintainer then tries to uncover them with help from advanced users who can handle important issues. After this first stage, the package is moved into <emphasis role=\"distribution\">Unstable</emphasis>, where it reaches a much larger audience and where it will be tested in much more detail."
msgstr ""
msgid "<emphasis role=\"distribution\">Experimental</emphasis> is generally used by users who do not mind breaking their system and then repairing it. This distribution gives the possibility to import a package which a user wants to try or use as the need arises. That is exactly how Debian approaches it, since adding it in APT's <filename>sources.list</filename> file does not lead to the systematic use of its packages. The line to be added is:"
msgstr ""
msgid "deb https://deb.debian.org/debian experimental main contrib non-free"
msgstr ""
msgid "Using Alternate Mirrors"
msgstr ""
msgid "<primary><literal>deb.debian.org</literal></primary><see>mirrors</see>"
msgstr ""
msgid "<primary>mirrors</primary>"
msgstr ""
msgid "<primary>CDN</primary><see>Content Delivery Networks</see>"
msgstr ""
msgid "<primary>Content Delivery Networks</primary>"
msgstr ""
msgid "The <filename>sources.list</filename> examples in this chapter refer to package repositories hosted on <ulink url=\"https://deb.debian.org/\"><literal>deb.debian.org</literal></ulink>. Those URLs will redirect you to servers which are close to you and which are managed by Content Delivery Networks (<acronym>CDN</acronym>) whose main role is to store multiple copies of the files across the world, and to deliver them as fast as possible to users. The CDN companies that Debian is working with are Debian partners who are offering their services freely to Debian. While none of those servers are under direct control of Debian, the fact that the whole archive is sealed by GPG signatures makes it a non-issue."
msgstr ""
msgid "<primary>mirror list</primary><seealso>mirrors</seealso>"
msgstr ""
msgid "<primary>list of mirrors</primary><seealso>mirrors</seealso>"
msgstr ""
msgid "Picky users who are not satisfied with the performance of <literal>deb.debian.org</literal> can try to find a better mirror in the official mirror list: <ulink type=\"block\" url=\"https://www.debian.org/mirror/list\" />"
msgstr ""
msgid "But when you don't know which mirror is best for you, this list is of not much use. Fortunately for you, Debian maintains DNS entries of the form <literal>ftp.<replaceable>country-code</replaceable>.debian.org</literal> (e.g. <literal>ftp.us.debian.org</literal> for the USA, <literal>ftp.fr.debian.org</literal> for France, etc.) which are covering many countries and which are pointing to one (or more) of the best mirrors available within that country."
msgstr ""
msgid "<primary><literal>httpredir.debian.org</literal></primary><see>mirrors</see>"
msgstr ""
msgid "As an alternative to <literal>deb.debian.org</literal>, there used to be <literal>httpredir.debian.org</literal>. This service would identify a mirror close to you (among the list of official mirrors, using GeoIP mainly) and would redirect APT's requests to that mirror. This service has been deprecated due to reliability concerns and now <literal>httpredir.debian.org</literal> provides the same CDN-based service as <literal>deb.debian.org</literal>."
msgstr ""
msgid "Non-Official Resources: <literal>mentors.debian.net</literal>"
msgstr ""
msgid "<primary><literal>mentors.debian.net</literal></primary>"
msgstr ""
msgid "There are numerous non-official sources of Debian packages set up by advanced users who have recompiled some software (Ubuntu made this popular with their Personal Package Archive (<acronym>PPA</acronym>) service, by programmers who make their creation available to all, and even by Debian developers who offer pre-versions of their package online."
msgstr ""
msgid "The <ulink url=\"https://mentors.debian.net\"><literal>mentors.debian.net</literal></ulink> site is interesting (although it only provides source packages), since it gathers packages created by candidates to the status of official Debian developer or by volunteers who wish to create Debian packages without going through that process of integration. These packages are made available without any guarantee regarding their quality; make sure that you check their origin and integrity and then test them before you consider using them in production."
msgstr ""
msgid "<emphasis>COMMUNITY</emphasis> The <literal>debian.net</literal> sites"
msgstr ""
msgid "<primary><emphasis>debian.net</emphasis></primary>"
msgstr ""
msgid "The <emphasis>debian.net</emphasis> domain is not an official resource of the Debian project. Each Debian developer may use that domain name for their own use. These websites can contain unofficial services (sometimes personal sites) hosted on a machine which does not belong to the project and set up by Debian developers, or even prototypes about to be moved on to <emphasis>debian.org</emphasis>. Two reasons can explain why some of these prototypes remain on <emphasis>debian.net</emphasis>: either no one has made the necessary effort to transform it into an official service (hosted on the <emphasis>debian.org</emphasis> domain, and with a certain guarantee of maintenance), or the service is too controversial to be officialized."
msgstr ""
msgid "Installing a package means giving root rights to its creator, because they decide on the contents of the initialization scripts which are run under that identity. Official Debian packages are created by volunteers who have been co-opted and reviewed and who can seal their packages so that their origin and integrity can be checked."
msgstr ""
msgid "In general, be wary of a package whose origin you don't know and which isn't hosted on one of the official Debian servers: evaluate the degree to which you can trust the creator, and check the integrity of the package."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> Old package versions: <literal>snapshot.debian.org</literal>"
msgstr ""
msgid "<primary><literal>snapshot.debian.org</literal></primary>"
msgstr ""
msgid "The <ulink url=\"https://snapshot.debian.org\"><literal>snapshot.debian.org</literal></ulink> service, introduced in April 2010, can be used to “go backwards in time” and to find an old version of a package not longer contained in the Debian archives. It can be used, for example, to identify which version of a package introduced a regression, and more concretely, to come back to the former version while waiting for the regression fix."
msgstr ""
msgid "Caching Proxy for Debian Packages"
msgstr ""
msgid "<primary>proxy cache</primary>"
msgstr ""
msgid "<primary>cache, proxy</primary>"
msgstr ""
msgid "When an entire network of machines is configured to use the same remote server to download the same updated packages, any administrator knows that it would be beneficial to have an intermediate proxy acting as a network-local cache (see sidebar <xref linkend=\"sidebar.cache\" />)."
msgstr ""
msgid "You can configure APT to use a \"standard\" proxy (see <xref linkend=\"sect.apt-config\" /> for the APT side, and <xref linkend=\"sect.http-ftp-proxy\" /> for the proxy side), but the Debian ecosystem offers better options to solve this problem. The dedicated software presented in this section are smarter than a plain proxy cache because they can rely on the specific structure of APT repositories (for instance they know when individual files are obsolete or not, and thus adjust the time during which they are kept)."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">apt-cacher</emphasis></primary>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">apt-cacher-ng</emphasis></primary>"
msgstr ""
msgid "<emphasis role=\"pkg\">apt-cacher</emphasis> and <emphasis role=\"pkg\">apt-cacher-ng</emphasis> work like usual proxy cache servers. APT's <filename>sources.list</filename> is left unchanged, but APT is configured to use them as proxy for outgoing requests."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">approx</emphasis></primary>"
msgstr ""
msgid "<emphasis role=\"pkg\">approx</emphasis>, on the other hand, acts like an HTTP server that “mirrors” any number of remote repositories in its top-level URLs. The mapping between those top-level directories and the remote URLs of the repositories is stored in <filename>/etc/approx/approx.conf</filename>:"
msgstr ""
msgid ""
"# <name> <repository-base-url>\n"
"debian https://deb.debian.org/debian\n"
"security http://security.debian.org\n"
" "
msgstr ""
msgid "<emphasis role=\"pkg\">approx</emphasis> runs by default on port 9999 via a systemd socket and requires the users to adjust their <filename>sources.list</filename> file to point to the approx server:"
msgstr ""
msgid ""
"# Sample sources.list pointing to a local approx server\n"
"deb http://localhost:9999/security buster/updates main contrib non-free\n"
"deb http://localhost:9999/debian buster main contrib non-free\n"
" "
msgstr ""
msgid "<command>aptitude</command>, <command>apt-get</command>, and <command>apt</command> Commands"
msgstr ""
msgid "<primary><command>apt</command></primary>"
msgstr ""
msgid "<primary><command>apt-get</command></primary>"
msgstr ""
msgid "<primary><command>aptitude</command></primary>"
msgstr ""
msgid "<acronym>APT</acronym> is a vast project, whose original plans included a graphical interface. It is based on a library which contains the core application, and <command>apt-get</command> is the first front end — command-line based — which was developed within the project. <command>apt</command> is a second command-line based front end provided by APT which overcomes some design mistakes of <command>apt-get</command>."
msgstr ""
msgid "Both tools are built on top of the same library and are thus very close, but the default behavior of <command>apt</command> has been improved for interactive use and to actually do what most users expect. The APT developers reserve the right to change the public interface of this tool to further improve it. On the opposite, the public interface of <command>apt-get</command> is well defined and will not change in any backwards incompatible way. It is thus the tool that you want to use when you need to script package installation requests."
msgstr ""
msgid "Numerous other graphical interfaces then appeared as external projects: <command>synaptic</command>, <command>aptitude</command> (which includes both a text mode interface and a graphical one — even if not complete yet), <command>wajig</command>, etc. The most recommended interface, <command>apt</command>, is the one that we will use in the examples given in this section. Note, however, that <command>apt-get</command> and <command>aptitude</command> have a very similar command line syntax. When there are major differences between these three commands, these will be detailed."
msgstr ""
msgid "Initialization"
msgstr ""
msgid "For any work with APT, the list of available packages needs to be updated; this can be done simply through <command>apt update</command>. Depending on the speed of your connection and configuration, the operation can take a while, since it involves downloading a certain number of (usually compressed) files (<filename>Packages</filename>, <filename>Sources</filename>, <filename>Translation-<replaceable>language-code</replaceable></filename>), which have gradually become bigger and bigger as Debian has developed (at least 10 MB of data for the <literal>main</literal> section). Of course, installing from a CD-ROM/DVD set does not require any downloading — in this case, the operation is very fast."
msgstr ""
msgid "<primary><command>apt update</command></primary>"
msgstr ""
msgid "<primary><command>apt-get update</command></primary>"
msgstr ""
msgid "<primary><command>aptitude update</command></primary>"
msgstr ""
msgid "<emphasis>TIP</emphasis> Incremental updates"
msgstr ""
msgid "The aim of the <command>apt update</command> command is to download for each package source the corresponding <filename>Packages</filename> (or <filename>Sources</filename>) file. However, even after a <command>xz</command> compression, these files can remain rather large (the <filename>Packages.xz</filename> for the <foreignphrase>main</foreignphrase> section of <emphasis role=\"distribution\">Buster</emphasis> takes more than 7 MB). If you wish to update regularly, these downloads can take up a lot of time."
msgstr ""
msgid "To speed up the process APT can download “diff” files containing the changes since the previous update, as opposed to the entire file. To achieve this, official Debian mirrors distribute different files which list the differences between one version of the <filename>Packages</filename> file and the following version. They are generated at each update of the archives and a history of one week is kept. Each of these “diff” files only takes a few dozen kilobytes for <emphasis role=\"distribution\">Unstable</emphasis>, so that the amount of data downloaded by a weekly <command>apt update</command> is often divided by 10. For <emphasis role=\"distribution\">Stable</emphasis> and <emphasis role=\"distribution\">Testing</emphasis>, which change less, the gain is even more noticeable."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>Acquire::PDiffs</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "However, it can sometimes be of interest to force the download of the entire <filename>Packages</filename> file, especially when the last upgrade is very old and when the mechanism of incremental differences would not contribute much. This can also be interesting when network access is very fast but when the processor of the machine to upgrade is rather slow, since the time saved on the download is more than lost when the computer calculates the new versions of these files (starting with the older versions and applying the downloaded differences). To do that, you can use the APT configuration parameter <literal>Acquire::PDiffs</literal> and set it to <literal>false</literal>."
msgstr ""
msgid "<computeroutput>$ </computeroutput><userinput>sudo apt -o \"Acquire::PDiffs=false\" update</userinput>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>Acquire::Languages</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "The <literal>Acquire::*</literal> options also control other aspects of the download, and even the download methods. <literal>Acquire::Languages</literal> can limit or disable the download of <filename>Translation-<replaceable>language-code</replaceable></filename> files and save even more time. For a complete reference see <citerefentry><refentrytitle>apt.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>."
msgstr ""
msgid "Installing and Removing"
msgstr ""
msgid "<primary>package</primary><secondary>installation</secondary>"
msgstr ""
msgid "<primary>package</primary><secondary>removal</secondary>"
msgstr ""
msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary>removal of a package</primary>"
msgstr ""
msgid "With APT, packages can be added or removed from the system, respectively with <command>apt install <replaceable>package</replaceable></command> and <command>apt remove <replaceable>package</replaceable></command>. In both cases, APT will automatically install the necessary dependencies or delete the packages which depend on the package that is being removed. The <command>apt purge <replaceable>package</replaceable></command> command involves a complete uninstallation by deleting the configuration files as well."
msgstr ""
msgid "<primary><command>apt install</command></primary>"
msgstr ""
msgid "<primary><command>apt remove</command></primary>"
msgstr ""
msgid "<primary><command>apt purge</command></primary>"
msgstr ""
msgid "<primary><command>apt-get install</command></primary>"
msgstr ""
msgid "<primary><command>apt-get remove</command></primary>"
msgstr ""
msgid "<primary><command>apt-get purge</command></primary>"
msgstr ""
msgid "<primary><command>aptitude install</command></primary>"
msgstr ""
msgid "<primary><command>aptitude remove</command></primary>"
msgstr ""
msgid "<primary><command>aptitude purge</command></primary>"
msgstr ""
msgid "<emphasis>TIP</emphasis> Installing the same selection of packages several times"
msgstr ""
msgid "It can be useful to systematically install the same list of packages on several computers. This can be done quite easily."
msgstr ""
msgid "First, retrieve the list of packages installed on the computer which will serve as the “model” to copy."
msgstr ""
msgid "<computeroutput>$ </computeroutput><userinput>dpkg --get-selections >pkg-list</userinput>"
msgstr ""
msgid "The <filename>pkg-list</filename> file then contains the list of installed packages. Next, transfer the <filename>pkg-list</filename> file onto the computers you want to update and use the following commands:"
msgstr ""
msgid ""
"## Update dpkg's database of known packages\n"
"# <userinput>avail=`mktemp`</userinput>\n"
"# <userinput>apt-cache dumpavail > \"$avail\"</userinput>\n"
"# <userinput>dpkg --merge-avail \"$avail\"</userinput>\n"
"# <userinput>rm -f \"$avail\"</userinput>\n"
"## Update dpkg's selections\n"
"# <userinput>dpkg --set-selections < pkg-list</userinput>\n"
"## Ask apt-get to install the selected packages\n"
"# <userinput>apt-get dselect-upgrade</userinput>"
msgstr ""
msgid "The first commands record the list of available packages in the dpkg database. Then <command>dpkg --set-selections</command> restores the selection of packages that you wish to install, and the <command>apt-get</command> invocation executes the required operations! <command>aptitude</command> does not have this command."
msgstr ""
msgid "<emphasis>TIP</emphasis> Removing and installing at the same time"
msgstr ""
msgid "It is possible to ask <command>apt</command> (or <command>apt-get</command>, or <command>aptitude</command>) to install certain packages and remove others on the same command line by adding a suffix. With an <command>apt install</command> command, add “<literal>-</literal>” to the names of the packages you wish to remove. With an <command>apt remove</command> command, add “<literal>+</literal>” to the names of the packages you wish to install."
msgstr ""
msgid "The next example shows two different ways to install <replaceable>package1</replaceable> and to remove <replaceable>package2</replaceable>."
msgstr ""
msgid "# <userinput>apt install <replaceable>package1</replaceable> <replaceable>package2</replaceable>-</userinput>"
msgstr ""
msgid "# <userinput>apt remove <replaceable>package1</replaceable>+ <replaceable>package2</replaceable></userinput>"
msgstr ""
msgid "This can also be used to exclude packages which would otherwise be installed, for example, due to an automatic installation of <literal>Recommends</literal>. In general, the dependency solver will use that information as a hint to look for alternative solutions."
msgstr ""
msgid "<emphasis>TIP</emphasis> <command>apt --reinstall</command> and <command>aptitude reinstall</command>"
msgstr ""
msgid "<primary>reinstallation</primary>"
msgstr ""
msgid "<primary><command>apt install --reinstall</command></primary>"
msgstr ""
msgid "<primary><command>apt-get install --reinstall</command></primary>"
msgstr ""
msgid "<primary><command>aptitude install --reinstall</command></primary>"
msgstr ""
msgid "The system can sometimes be damaged after the removal or modification of files in a package. The easiest way to retrieve these files is to reinstall the affected package. Unfortunately, the packaging system finds that the latter is already installed and politely refuses to reinstall it; to avoid this, use the <literal>--reinstall</literal> option of the <command>apt</command> and <command>apt-get</command> commands. The following command reinstalls <emphasis role=\"pkg\">postfix</emphasis> even if it is already present:"
msgstr ""
msgid "<computeroutput># </computeroutput><userinput>apt --reinstall install postfix</userinput>"
msgstr ""
msgid "The <command>aptitude</command> command line is slightly different, but achieves the same result with <command>aptitude reinstall postfix</command>."
msgstr ""
msgid "The problem does not arise with <command>dpkg</command>, but the administrator rarely uses it directly."
msgstr ""
msgid "Be careful! Using <command>apt --reinstall</command> to restore packages modified during an attack will certainly not recover the system as it was. <xref linkend=\"sect.dealing-with-compromised-machine\" /> details the necessary steps to take with a compromised system."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>dpkg</command></primary><secondary><command>--force-confask</command></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary><command>dpkg</command></primary><secondary><command>--force-confmiss</command></secondary>"
msgstr ""
msgid "These commands will not restore the configuration files. But as you have learned in <xref linkend=\"sect.conffiles\" /> (see also sidebar <xref linkend=\"sidebar.questions-conffiles-bis\" />), you can use the following command to be asked to install the unmodified version and even restore any deleted configuration file as well."
msgstr ""
msgid "<computeroutput># </computeroutput><userinput>apt --reinstall -o Dpkg::Options::=\"--force-confask,confmiss\" install <replaceable>package</replaceable></userinput>"
msgstr ""
msgid "Some packages don't ship the configuration file found in <filename>/etc</filename> with the package. Instead they create it during installation by either copying a skeleton or writing it by a script. The file <filename>/etc/inputrc</filename>, for example, is a copy of <filename>/usr/share/readline/inputrc</filename>. In such cases the commands shown above won't work."
msgstr ""
msgid "If the file <filename>sources.list</filename> mentions several distributions, it is possible to give the version of the package to install. A specific version number can be requested with <command>apt install <replaceable>package</replaceable>=<replaceable>version</replaceable></command>, but indicating its distribution of origin (<emphasis role=\"distribution\">Stable</emphasis>, <emphasis role=\"distribution\">Testing</emphasis> or <emphasis role=\"distribution\">Unstable</emphasis>) — with <command>apt install <replaceable>package</replaceable>/<replaceable>distribution</replaceable></command> — is usually preferred. With this command, it is possible to go back to an older version of a package (if, for instance, you know that it works well), provided that it is still available in one of the sources referenced by the <filename>sources.list</filename> file. Otherwise the <literal>snapshot.debian.org</literal> archive can come to the rescue (see sidebar <xref linkend=\"sidebar.snapshot.debian.org\" />)."
msgstr ""
msgid "Installation of the <emphasis role=\"distribution\">Unstable</emphasis> version of <emphasis role=\"pkg\">spamassassin</emphasis>"
msgstr ""
msgid "<computeroutput># </computeroutput><userinput>apt install spamassassin/unstable</userinput>"
msgstr ""
msgid "If the package to install has been made available to you under the form of a simple <filename>.deb</filename> file without any associated package repository, it is still possible to use APT to install it together with its dependencies (provided that the dependencies are available in the configured repositories) with a simple command: <command>apt install ./<replaceable>path-to-the-package.deb</replaceable></command>. The leading <literal>./</literal> is important to make it clear that we are referring to a filename and not to the name of a package available in one of the repositories."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> The cache of <filename>.deb</filename> files"
msgstr ""
msgid "<primary><filename>/var/cache/apt/archives/</filename></primary>"
msgstr ""
msgid "<primary><command>apt-get clean</command></primary>"
msgstr ""
msgid "<primary><command>apt-get autoclean</command></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/var/cache/apt/archives/</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>APT::Clean-Installed</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "APT keeps a copy of each downloaded <filename>.deb</filename> file in the directory <filename>/var/cache/apt/archives/</filename>. In case of frequent updates, this directory can quickly take a lot of disk space with several versions of each package; you should regularly sort through them. Two commands can be used: <command>apt-get clean</command> entirely empties the directory; <command>apt-get autoclean</command> only removes packages which can no longer be downloaded (because they have disappeared from the Debian mirror) and are therefore clearly useless (the configuration parameter <literal>APT::Clean-Installed</literal> can prevent the removal of <filename>.deb</filename> files that are currently installed)."
msgstr ""
msgid "System Upgrade"
msgstr ""
msgid "<primary>upgrade</primary><secondary>system upgrade</secondary>"
msgstr ""
msgid "<primary><command>apt upgrade</command></primary>"
msgstr ""
msgid "<primary><command>apt-get upgrade</command></primary>"
msgstr ""
msgid "<primary><command>aptitude safe-upgrade</command></primary>"
msgstr ""
msgid "Regular upgrades are recommended, because they include the latest security updates. To upgrade, use <command>apt upgrade</command>, <command>apt-get upgrade</command> or <command>aptitude safe-upgrade</command> (of course after <command>apt update</command>). This command looks for installed packages which can be upgraded without removing any packages. In other words, the goal is to ensure the least intrusive upgrade possible. <command>apt-get</command> is slightly more demanding than <command>aptitude</command> or <command>apt</command> because it will refuse to install packages which were not installed beforehand."
msgstr ""
msgid "<command>apt</command> will generally select the most recent version number (except for packages from <emphasis role=\"distribution\">Experimental</emphasis> and <emphasis role=\"distribution\">stable-backports</emphasis>, which are ignored by default whatever their version number). If you specified <emphasis role=\"distribution\">Testing</emphasis> or <emphasis role=\"distribution\">Unstable</emphasis> in your <filename>sources.list</filename>, <command>apt upgrade</command> will switch most of your <emphasis role=\"distribution\">Stable</emphasis> system to <emphasis role=\"distribution\">Testing</emphasis> or <emphasis role=\"distribution\">Unstable</emphasis>, which might not be what you intended."
msgstr ""
msgid "To tell <command>apt</command> to use a specific distribution when searching for upgraded packages, you need to use the <literal>-t</literal> or <literal>--target-release</literal> option, followed by the name of the distribution you want (for example, <command>apt -t stable upgrade</command>). To avoid specifying this option every time you use <command>apt</command>, you can add <literal>APT::Default-Release \"stable\";</literal> in the file <filename>/etc/apt/apt.conf.d/local</filename>."
msgstr ""
msgid "<primary><command>apt full-upgrade</command></primary>"
msgstr ""
msgid "<primary><command>apt dist-upgrade</command></primary>"
msgstr ""
msgid "<primary><command>apt-get dist-upgrade</command></primary>"
msgstr ""
msgid "<primary><command>aptitude dist-upgrade</command></primary>"
msgstr ""
msgid "<primary><command>aptitude full-upgrade</command></primary>"
msgstr ""
msgid "For more important upgrades, such as the change from one major Debian version to the next, you need to use <command>apt full-upgrade</command>. With this instruction, <command>apt</command> will complete the upgrade even if it has to remove some obsolete packages or install new dependencies. This is also the command used by users who work daily with the Debian <emphasis role=\"distribution\">Unstable</emphasis> release and follow its evolution day by day. It is so simple that it hardly needs explanation: APT's reputation is based on this great functionality."
msgstr ""
msgid "Unlike <command>apt</command> and <command>aptitude</command>, <command>apt-get</command> doesn't know the <command>full-upgrade</command> command. Instead, you should use <command>apt-get dist-upgrade</command> (”distribution upgrade”), the historical and well-known command that <command>apt</command> and <command>aptitude</command> also accept for the convenience of users who got used to it."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/var/log/apt/history.log</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/var/log/apt/term.log</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/var/log/apt/eipp.log.xz</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>dpkg</primary><secondary><filename>/var/log/dpkg.log</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "The results of these operations are logged into <filename>/var/log/apt/history.log</filename> and <filename>/var/log/apt/term.log</filename>, whereas <command>dpkg</command> keeps its log in a file called <filename>/var/log/dpkg.log</filename>."
msgstr ""
msgid "Configuration Options"
msgstr ""
msgid "<primary>APT</primary><secondary>configuration</secondary>"
msgstr ""
msgid "<primary><filename>apt.conf</filename></primary>"
msgstr ""
msgid "<primary><filename>apt.conf.d/</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/apt.conf</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/apt.conf.d/</filename></primary>"
msgstr ""
msgid "<primary><citerefentry><refentrytitle>apt.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/etc/apt/apt.conf</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/etc/apt/apt.conf.d/</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>DPkg::options</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>Acquire::http::proxy</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>Acquire::ftp::proxy</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Besides the configuration elements already mentioned, it is possible to configure certain aspects of APT by adding directives in a file of the <filename>/etc/apt/apt.conf.d/</filename> directory or <filename>/etc/apt/apt.conf</filename> itself. Remember, for instance, that it is possible for APT to tell <command>dpkg</command> to ignore file conflict errors by specifying <literal>DPkg::options { \"--force-overwrite\"; }</literal>."
msgstr ""
msgid "If the Web can only be accessed through a proxy, add a line like <literal>Acquire::http::proxy \"http://<replaceable>yourproxy</replaceable>:3128\"</literal>. For an FTP proxy, write <literal>Acquire::ftp::proxy \"ftp://<replaceable>yourproxy</replaceable>\"</literal>. To discover more configuration options, read the <citerefentry><refentrytitle>apt.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> manual page with the <command>man apt.conf</command> command (for details on manual pages, see <xref linkend=\"sect.manual-pages\" />)."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Directories ending in <filename>.d</filename>"
msgstr ""
msgid "<primary><filename>.d</filename></primary>"
msgstr ""
msgid "Directories with a <filename>.d</filename> suffix are used more and more often. Each directory represents a configuration file which is split over multiple files. In this sense, all of the files in <filename>/etc/apt/apt.conf.d/</filename> are instructions for the configuration of APT. APT includes them in alphabetical order, so that the last ones can modify a configuration element defined in one of the first ones."
msgstr ""
msgid "This structure brings some flexibility to the machine administrator and to the package maintainers. Indeed, the administrator can easily modify the configuration of the software by adding a ready-made file in the directory in question without having to change an existing file. Package maintainers use the same approach when they need to adapt the configuration of another software to ensure that it perfectly co-exists with theirs. The Debian policy explicitly forbids modifying configuration files of other packages — only users are allowed to do this. Remember that during a package upgrade, the user gets to choose the version of the configuration file that should be kept when a modification has been detected. Any external modification of the file would trigger that request, which would disturb the administrator, who is sure not to have changed anything."
msgstr ""
msgid "Without a <filename>.d</filename> directory, it is impossible for an external package to change the settings of a program without modifying its configuration file. Instead it must invite the user to do it themselves and lists the operations to be done in the file <filename>/usr/share/doc/<replaceable>package</replaceable>/README.Debian</filename>."
msgstr ""
msgid "Depending on the application, the <filename>.d</filename> directory is used directly or managed by an external script which will concatenate all the files to create the configuration file itself. It is important to execute the script after any change in that directory so that the most recent modifications are taken into account. In the same way, it is important not to work directly in the configuration file created automatically, since everything would be lost at the next execution of the script. The chosen method (<filename>.d</filename> directory used directly or a file generated from that directory) is usually dictated by implementation constraints, but in both cases the gains in terms of configuration flexibility more than make up for the small complications that they entail. The Exim 4 mail server is an example of the generated file method: it can be configured through several files (<filename>/etc/exim4/conf.d/*</filename>) which are concatenated into <filename>/var/lib/exim4/config.autogenerated</filename> by the <command>update-exim4.conf</command> command."
msgstr ""
msgid "Managing Package Priorities"
msgstr ""
msgid "One of the most important aspects in the configuration of APT is the management of the priorities associated with each package source. For instance, you might want to extend one distribution with one or two newer packages from <emphasis role=\"distribution\">Testing</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis> or <emphasis role=\"distribution\">Experimental</emphasis>. It is possible to assign a priority to each available package (the same package can have several priorities depending on its version or the distribution providing it). These priorities will influence APT's behavior: for each package, it will always select the version with the highest priority (except if this version is older than the installed one and if its priority is less than 1000)."
msgstr ""
msgid "<primary>APT</primary><secondary><foreignphrase>pinning</foreignphrase></secondary>"
msgstr ""
msgid "<primary>pinning, APT pinning</primary>"
msgstr ""
msgid "<primary>package</primary><secondary>priority</secondary>"
msgstr ""
msgid "<primary>priority</primary><secondary>package priority</secondary>"
msgstr ""
msgid "<primary>APT</primary><secondary>preferences</secondary>"
msgstr ""
msgid "<primary><filename>preferences</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/preferences</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/preferences.d/</filename></primary>"
msgstr ""
msgid "<primary><citerefentry><refentrytitle>apt_preferences</refentrytitle><manvolnum>5</manvolnum></citerefentry></primary>"
msgstr ""
msgid "APT defines several default priorities. Each installed package version has a priority of 100. A non-installed version has a priority of 500 by default, but it can jump to 990 if it is part of the target release (defined with the <literal>-t</literal> command-line option or the <literal>APT::Default-Release</literal> configuration directive)."
msgstr ""
msgid "You can modify the priorities by adding entries in a file in <filename>/etc/apt/preferences.d/</filename> or the <filename>/etc/apt/preferences</filename> file with the names of the affected packages, their version, their origin and their new priority."
msgstr ""
msgid "APT will never install an older version of a package (that is, a package whose version number is lower than the one of the currently installed package) except if its priority is higher than 1000 (or it is explicitely requested by the user, see <xref linkend=\"sect.apt.install\" />). APT will always install the highest priority package which follows this constraint. If two packages have the same priority, APT installs the newest one (whose version number is the highest). If two packages of same version have the same priority but differ in their content, APT installs the version that is not installed (this rule has been created to cover the case of a package update without the increment of the revision number, which is usually required)."
msgstr ""
msgid "In more concrete terms, a package whose priority is"
msgstr ""
msgid "< 0"
msgstr ""
msgid "will never be installed,"
msgstr ""
msgid "1..99"
msgstr ""
msgid "will only be installed if no other version of the package is already installed,"
msgstr ""
msgid "100..499"
msgstr ""
msgid "will only be installed if there is no other newer version installed or available in another distribution,"
msgstr ""
msgid "500....989"
msgstr ""
msgid "will only be installed if there is no newer version installed or available in the target distribution,"
msgstr ""
msgid "990..1000"
msgstr ""
msgid "will be installed except if the installed version is newer,"
msgstr ""
msgid "> 1000"
msgstr ""
msgid "will always be installed, even if it forces APT to downgrade to an older version."
msgstr ""
msgid "When APT checks <filename>/etc/apt/preferences</filename> and <filename>/etc/apt/preferences.d/</filename>, it first takes into account the most specific entries (often those specifying the concerned package), then the more generic ones (including, for example, all the packages of a distribution). If several generic entries exist, the first match is used. The available selection criteria include the package's name and the source providing it. Every package source is identified by the information contained in a <filename>Release</filename> file that APT downloads together with the <filename>Packages</filename> files. It specifies the origin (usually “Debian” for the packages of official mirrors, but it can also be a person's or an organization's name for third-party repositories). It also gives the name of the distribution (usually <emphasis role=\"distribution\">Stable</emphasis>, <emphasis role=\"distribution\">Testing</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis> or <emphasis role=\"distribution\">Experimental</emphasis> for the standard distributions provided by Debian) together with its version (for example, 10 for Debian <emphasis role=\"distribution\">Buster</emphasis>). Let's have a look at its syntax through some realistic case studies of this mechanism."
msgstr ""
msgid "<emphasis>SPECIFIC CASE</emphasis> Priority of <emphasis role=\"distribution\">experimental</emphasis>"
msgstr ""
msgid "<primary><emphasis role=\"distribution\">Experimental</emphasis></primary>"
msgstr ""
msgid "If you listed <emphasis role=\"distribution\">Experimental</emphasis> in your <filename>sources.list</filename> file, the corresponding packages will almost never be installed because their default APT priority is 1. This is of course a specific case, designed to keep users from installing <emphasis role=\"distribution\">Experimental</emphasis> packages by mistake. The packages can only be installed by typing <command>aptitude install <replaceable>package</replaceable>/experimental</command> — users typing this command can only be aware of the risks that they take. It is still possible (though <emphasis>not</emphasis> recommended) to treat packages of <emphasis role=\"distribution\">Experimental</emphasis> like those of other distributions by giving them a priority of 500. This is done with a specific entry in <filename>/etc/apt/preferences</filename>:"
msgstr ""
msgid ""
"Package: *\n"
"Pin: release a=experimental\n"
"Pin-Priority: 500"
msgstr ""
msgid "Let's suppose that you only want to use packages from the stable version of Debian. Those provided in other versions should not be installed except if explicitly requested. You could write the following entries in the <filename>/etc/apt/preferences</filename> file:"
msgstr ""
msgid ""
"Package: *\n"
"Pin: release a=stable\n"
"Pin-Priority: 900\n"
"\n"
"Package: *\n"
"Pin: release o=Debian\n"
"Pin-Priority: -10"
msgstr ""
msgid "<literal>a=stable</literal> defines the name of the selected distribution. <literal>o=Debian</literal> limits the scope to packages whose origin is “Debian”."
msgstr ""
msgid "Let's now assume that you have a server with several local programs depending on the version 5.24 of Perl and that you want to ensure that upgrades will not install another version of it. You could use this entry:"
msgstr ""
msgid ""
"Package: perl\n"
"Pin: version 5.24*\n"
"Pin-Priority: 1001"
msgstr ""
msgid "To gain a better understanding of the mechanisms of priority and distribution or repository properties to pin do not hesitate to execute <command>apt-cache policy</command> to display the default priority associated with each package source, or <command>apt-cache policy <replaceable>package</replaceable></command> to display the default priority for each available version and source of a package as explained in <xref linkend=\"sidebar.apt-cache-policy\" />."
msgstr ""
msgid "The reference documentation for the files <filename>/etc/apt/preferences</filename> and <filename>/etc/apt/preferences.d/</filename> is available in the manual page <citerefentry><refentrytitle>apt_preferences</refentrytitle><manvolnum>5</manvolnum></citerefentry>, which you can display with <command>man apt_preferences</command>."
msgstr ""
msgid "<emphasis>TIP</emphasis> Comments in <filename>/etc/apt/preferences</filename>"
msgstr ""
msgid "<primary><literal>Explanation</literal></primary>"
msgstr ""
msgid "<primary><literal>Pin</literal></primary>"
msgstr ""
msgid "<primary><literal>Pin-Priority</literal></primary>"
msgstr ""
msgid "There is no official syntax to put comments in the <filename>/etc/apt/preferences</filename> file, but some textual descriptions can be provided by putting one or more “<literal>Explanation</literal>” fields at the start of each entry:"
msgstr ""
msgid ""
"Explanation: The package xserver-xorg-video-intel provided\n"
"Explanation: in experimental can be used safely\n"
"Package: xserver-xorg-video-intel\n"
"Pin: release a=experimental\n"
"Pin-Priority: 500"
msgstr ""
msgid "Working with Several Distributions"
msgstr ""
msgid "<command>apt</command> being such a marvelous tool, it is tempting to pick packages coming from other distributions. For example, after having installed a <emphasis role=\"distribution\">Stable</emphasis> system, you might want to try out a software package available in <emphasis role=\"distribution\">Testing</emphasis> or <emphasis role=\"distribution\">Unstable</emphasis> without diverging too much from the system's initial state."
msgstr ""
msgid "Even if you will occasionally encounter problems while mixing packages from different distributions, <command>apt</command> manages such coexistence very well and limits risks very effectively. The best way to proceed is to list all distributions used in <filename>/etc/apt/sources.list</filename> (some people always put the three distributions, but remember that <emphasis role=\"distribution\">Unstable</emphasis> is reserved for experienced users) and to define your reference distribution with the <literal>APT::Default-Release</literal> parameter (see <xref linkend=\"sect.apt-upgrade\" />)."
msgstr ""
msgid "Let's suppose that <emphasis role=\"distribution\">Stable</emphasis> is your reference distribution but that <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis> are also listed in your <filename>sources.list</filename> file. In this case, you can use <command>apt install <replaceable>package</replaceable>/testing</command> to install a package from <emphasis role=\"distribution\">Testing</emphasis>. If the installation fails due to some unsatisfiable dependencies, let it solve those dependencies within <emphasis role=\"distribution\">Testing</emphasis> by adding the <literal>-t testing</literal> parameter. The same obviously applies to <emphasis role=\"distribution\">Unstable</emphasis>."
msgstr ""
msgid "In this situation, upgrades (<command>upgrade</command> and <command>full-upgrade</command>) are done within <emphasis role=\"distribution\">Stable</emphasis> except for packages already upgraded to another distribution: those will follow updates available in the other distributions. We will explain this behavior with the help of the default priorities set by APT below. Do not hesitate to use <command>apt-cache policy</command> (see sidebar <xref linkend=\"sidebar.apt-cache-policy\" />) to verify the given priorities."
msgstr ""
msgid "Everything centers around the fact that APT only considers packages of higher or equal version than the installed one (assuming that <filename>/etc/apt/preferences</filename> has not been used to force priorities higher than 1000 for some packages)."
msgstr ""
msgid "Let's assume that you have installed version 1 of a first package from <emphasis role=\"distribution\">Stable</emphasis> and that version 2 and 3 are available respectively in <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis>. The installed version has a priority of 100 but the version available in <emphasis role=\"distribution\">Stable</emphasis> (the very same) has a priority of 990 (because it is part of the target release). Packages in <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis> have a priority of 500 (the default priority of a non-installed version). The winner is thus version 1 with a priority of 990. The package “stays in <emphasis role=\"distribution\">Stable</emphasis>”."
msgstr ""
msgid "Let's take the example of another package whose version 2 has been installed from <emphasis role=\"distribution\">Testing</emphasis>. Version 1 is available in <emphasis role=\"distribution\">Stable</emphasis> and version 3 in <emphasis role=\"distribution\">Unstable</emphasis>. Version 1 (of priority 990 — thus lower than 1000) is discarded because it is lower than the installed version. This only leaves version 2 and 3, both of priority 500. Faced with this alternative, APT selects the newest version, the one from <emphasis role=\"distribution\">Unstable</emphasis>. If you don't want a package installed from <emphasis role=\"distribution\">Testing</emphasis> to migrate to <emphasis role=\"distribution\">Unstable</emphasis>, you have to assign a priority lower than 500 (490 for example) to packages coming from <emphasis role=\"distribution\">Unstable</emphasis>. You can modify <filename>/etc/apt/preferences</filename> to this effect:"
msgstr ""
msgid ""
"Package: *\n"
"Pin: release a=unstable\n"
"Pin-Priority: 490"
msgstr ""
msgid "Tracking Automatically Installed Packages"
msgstr ""
msgid "One of the essential functionalities of <command>apt</command> is the tracking of packages installed only through dependencies. These packages are called “automatic”, and often include libraries."
msgstr ""
msgid "<primary><command>apt autoremove</command></primary>"
msgstr ""
msgid "<primary><command>apt-get autoremove</command></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary>automatic removal</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>automatic removal</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "With this information, when packages are removed, the package managers can compute a list of automatic packages that are no longer needed (because there is no “manually installed” packages depending on them). <command>apt-get autoremove</command> or <command>apt autoremove</command> will get rid of those packages. <command>aptitude</command> does not have this command because it removes them automatically as soon as they are identified. In all cases, the tools display a clear message listing the affected packages."
msgstr ""
msgid "<primary><command>apt-mark auto</command></primary>"
msgstr ""
msgid "<primary><command>apt-mark manual</command></primary>"
msgstr ""
msgid "<primary><command>aptitude markauto</command></primary>"
msgstr ""
msgid "<primary><command>aptitude unmarkauto</command></primary>"
msgstr ""
msgid "It is a good habit to mark as automatic any package that you don't need directly so that they are automatically removed when they aren't necessary anymore. <command>apt-mark auto <replaceable>package</replaceable></command> will mark the given package as automatic whereas <command>apt-mark manual <replaceable>package</replaceable></command> does the opposite. <command>aptitude markauto</command> and <command>aptitude unmarkauto</command> work in the same way although they offer more features for marking many packages at once (see <xref linkend=\"sect.aptitude\" />). The console-based interactive interface of <command>aptitude</command> also makes it easy to review the “automatic flag” on many packages."
msgstr ""
msgid "<primary><command>aptitude why</command></primary>"
msgstr ""
msgid "People might want to know why an automatically installed package is present on the system. To get this information from the command line, you can use <command>aptitude why <replaceable>package</replaceable></command> (<command>apt</command> and <command>apt-get</command> have no similar feature):"
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>aptitude why python-debian\n"
"</userinput><computeroutput>i aptitude Suggests apt-xapian-index\n"
"p apt-xapian-index Depends python-debian (>= 0.1.14)\n"
"</computeroutput>"
msgstr ""
msgid "<emphasis>ALTERNATIVE</emphasis> <command>deborphan</command> and <command>debfoster</command>"
msgstr ""
msgid "<primary><command>deborphan</command></primary>"
msgstr ""
msgid "<primary><command>debfoster</command></primary>"
msgstr ""
msgid "In days where <command>apt</command>, <command>apt-get</command> and <command>aptitude</command> were not able to track automatic packages, there were two utilities producing lists of unnecessary packages: <command>deborphan</command> and <command>debfoster</command>. Both can still be useful."
msgstr ""
msgid "<command>deborphan</command> scans the <literal>libs</literal> and <literal>oldlibs</literal> sections (in the absence of supplementary instructions) by default looking for the packages that are currently installed and that no other package depends on. The resulting list can then serve as a basis to remove unneeded packages."
msgstr ""
msgid "<command>debfoster</command> has a more elaborate approach, very similar to APT's one: it maintains a list of packages that have been explicitly installed, and remembers what packages are really required between each invocation. If new packages appear on the system and if <command>debfoster</command> doesn't know them as required packages, they will be shown on the screen together with a list of their dependencies. The program then offers a choice: remove the package (possibly together with those that depend on it), mark it as explicitly required, or ignore it temporarily."
msgstr ""
msgid "The <command>apt-cache</command> Command"
msgstr ""
msgid "<primary><command>apt-cache</command></primary>"
msgstr ""
msgid "<primary>APT</primary><secondary>package search</secondary>"
msgstr ""
msgid "<primary>APT</primary><secondary>header display</secondary>"
msgstr ""
msgid "<primary>search of packages</primary>"
msgstr ""
msgid "<primary>package</primary><secondary>search</secondary>"
msgstr ""
msgid "The <command>apt-cache</command> command can display much of the information stored in APT's internal database. This information is a sort of cache since it is gathered from the different sources listed in the <filename>sources.list</filename> file. This happens during the <command>apt update</command> operation."
msgstr ""
msgid "<emphasis>VOCABULARY</emphasis> Cache"
msgstr ""
msgid "<primary>cache</primary>"
msgstr ""
msgid "A cache is a temporary storage system used to speed up frequent data access when the usual access method is expensive (performance-wise). This concept can be applied in numerous situations and at different scales, from the core of microprocessors up to high-end storage systems."
msgstr ""
msgid "In the case of APT, the reference <filename>Packages</filename> files are those located on Debian mirrors. That said, it would be very ineffective to go through the network for every search that we might want to do in the database of available packages. That is why APT stores a copy of those files (in <filename>/var/lib/apt/lists/</filename>) and searches are done within those local files. Similarly, <filename>/var/cache/apt/archives/</filename> contains a cache of already downloaded packages to avoid downloading them again if you need to reinstall them after a removal."
msgstr ""
msgid "On the other hand, it is mandatory to run <command>apt update</command> regularly to update the cache. Otherwise your package search results will always miss the latest updates distributed by the Debian mirrors."
msgstr ""
msgid "<primary><command>apt show</command></primary>"
msgstr ""
msgid "<primary><command>apt search</command></primary>"
msgstr ""
msgid "<primary><command>apt-cache show</command></primary>"
msgstr ""
msgid "<primary><command>apt-cache search</command></primary>"
msgstr ""
msgid "<primary><command>aptitude show</command></primary>"
msgstr ""
msgid "<primary><command>aptitude search</command></primary>"
msgstr ""
msgid "The <command>apt-cache</command> command can do keyword-based package searches with <command>apt-cache search <replaceable>keyword</replaceable></command>. It can also display the headers of the package's available versions with <command>apt-cache show <replaceable>package</replaceable></command>. This command provides the package's description, its dependencies, the name of its maintainer, etc. Note that <command>apt search</command>, <command>apt show</command>, <command>aptitude search</command>, <command>aptitude show</command> work in the same way."
msgstr ""
msgid "<emphasis>ALTERNATIVE</emphasis> <command>axi-cache</command>"
msgstr ""
msgid "<primary><command>axi-cache</command></primary>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">apt-xapian-index</emphasis></primary>"
msgstr ""
msgid "<command>apt-cache search</command> is a very rudimentary tool, basically implementing <command>grep</command> on package's descriptions. It often returns too many results or none at all when you include too many keywords."
msgstr ""
msgid "<command>axi-cache search <replaceable>term</replaceable></command>, on the other hand, provides better results, sorted by relevancy. It uses the <emphasis>Xapian</emphasis> search engine and is part of the <emphasis role=\"pkg\">apt-xapian-index</emphasis> package which indexes all package information (and more, like the <filename>.desktop</filename> files from all Debian packages). It knows about tags (see sidebar <xref linkend=\"sidebar.debtags\" />) and returns results in a matter of milliseconds."
msgstr ""
msgid ""
"$ <userinput>axi-cache search package use::searching</userinput>\n"
"<![CDATA[\n"
"100 results found.\n"
"Results 1-20:\n"
"100% packagesearch - GUI for searching packages and viewing package information\n"
"99% apt-utils - package management related utility programs\n"
"98% whohas - query multiple distributions' package archives\n"
"98% dpkg-awk - Gawk script to parse /var/lib/dpkg/{status,available} and Packages\n"
"97% apt-file - search for files within Debian packages (command-line interface)\n"
"[..]\n"
"90% wajig - unified package management front-end for Debian\n"
"More terms: debtags debian paket dpkg search pakete tools\n"
"More tags: role::program interface::commandline works-with::software:package suite::debian admin::package-management scope::utility network::client\n"
"`axi-cache more' will give more results\n"
"]]>"
msgstr ""
msgid "<primary><command>apt-cache policy</command></primary>"
msgstr ""
msgid "<primary><command>apt-cache dumpavail</command></primary>"
msgstr ""
msgid "<primary><command>apt-cache pkgnames</command></primary>"
msgstr ""
msgid "Some features are more rarely used. For instance, <command>apt-cache policy</command> displays the priorities of package sources as well as those of individual packages. Another example is <command>apt-cache dumpavail</command> which displays the headers of all available versions of all packages. <command>apt-cache pkgnames</command> displays the list of all the packages which appear at least once in the cache."
msgstr ""
msgid "<emphasis>TIP</emphasis> <command>apt-cache policy</command>"
msgstr ""
msgid "The <command>apt-cache policy</command> command displays the pinning priorities and distribution properties of each package source as explained in <xref linkend=\"sect.apt.priorities\" />. It can also show the pinning priorities for all available versions and sources of a package. For the <filename>sources.list</filename> example used in <xref linkend=\"example.stable-sources-list\" /> and <literal>APT::Default-Release</literal> set to <literal>\"buster\"</literal>, the output will look like this:"
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>apt-cache policy</userinput>\n"
"<computeroutput>Package files:\n"
" 100 /var/lib/dpkg/status\n"
" release a=now\n"
" 100 https://deb.debian.org/debian buster-backports/contrib amd64 Packages\n"
" release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=contrib,b=amd64\n"
" origin deb.debian.org\n"
" 100 https://deb.debian.org/debian buster-backports/main amd64 Packages\n"
" release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=main,b=amd64\n"
" origin deb.debian.org\n"
" 990 https://deb.debian.org/debian buster/non-free amd64 Packages\n"
" release v=10.0,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64\n"
" origin deb.debian.org\n"
" 990 https://deb.debian.org/debian buster/contrib amd64 Packages\n"
" release v=10.0,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64\n"
" origin deb.debian.org\n"
" 990 https://deb.debian.org/debian buster/main amd64 Packages\n"
" release v=10.0,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64\n"
" origin deb.debian.org\n"
" 990 http://security.debian.org buster/updates/main amd64 Packages\n"
" release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64\n"
" origin security.debian.org</computeroutput>"
msgstr ""
msgid "<command>apt-cache policy</command> can also show the pinning priorities for all available versions and sources of a given package."
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>apt-cache policy iptables</userinput>\n"
"<computeroutput>iptables:\n"
" Installed: 1.8.2-4\n"
" Candidate: 1.8.2-4\n"
" Version table:\n"
" 1.8.3-2~bpo10+1 100\n"
" 100 https://deb.debian.org/debian buster-backports/main amd64 Packages\n"
" *** 1.8.2-4 990\n"
" 990 https://deb.debian.org/debian buster/main amd64 Packages\n"
" 100 /var/lib/dpkg/status</computeroutput>"
msgstr ""
msgid "Although there is a newer version of <emphasis role=\"pkg\">iptables</emphasis> in the <literal>buster-backports</literal> repository, APT will not install it automatically based on the priority. One would have to use <command>apt install iptables/buster-backports</command> or add a higher pinning priority to <filename>/etc/apt/preferences.d/iptables</filename>:"
msgstr ""
msgid ""
"Package: iptables\n"
"Pin: release o=Debian Backports, a=buster-backports\n"
"Pin-Priority: 1001"
msgstr ""
msgid "The <command>apt-file</command> Command"
msgstr ""
msgid "<primary><command>apt-file</command></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary>file search</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary>search of files</primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>search files</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Sometimes we refer to a file or a command and you might wonder, in which package it will be found. Fortunately the Debian repositories not only contain information about all the binary packages provided, but also all the files shipped with them. This information is stored in files named <filename>Contents-<replaceable>arch</replaceable>.gz</filename> and <filename>Contents-udeb-<replaceable>arch</replaceable>.gz</filename>. This information is not automatically downloaded by APT. Instead it needs the <command>apt-file update</command> command (from the similar named package) to retrieve the contents of all package sources mentioned in <filename>/etc/apt/sources.list</filename>. To update the database on a weekly base, the following entry can be added to <filename>/etc/crontab</filename> if convenient."
msgstr ""
msgid "<![CDATA[@weekly root test -x /usr/bin/apt-file && /usr/bin/apt-file update >> /dev/null 2>&1]]>"
msgstr ""
msgid "After the database has been updated, the command <command>apt-file search <replaceable>pattern</replaceable></command> will list all packages, which contain a filename or path containing the pattern."
msgstr ""
msgid ""
"<computeroutput>$ </computeroutput><userinput>apt-file search bin/axi-cache</userinput>\n"
"apt-xapian-index: /usr/bin/axi-cache"
msgstr ""
msgid "The command <command>apt-file list <replaceable>package</replaceable></command> will list all files shipped with the package instead."
msgstr ""
msgid "<emphasis>TIP</emphasis> Listing a package contents and finding a file's package"
msgstr ""
msgid "Similar to <command>apt-file list</command> the command <command>dpkg -L <replaceable>package</replaceable></command> lists all files, but only for an installed package. To find the package, a local file belongs to, use <command>dpkg -S <replaceable>file</replaceable></command> (see <xref linkend=\"sect.dpkg-list\" />). To list all local files not belonging to any installed package, you might want to take a look at the <emphasis role=\"pkg\">cruft</emphasis> or the <emphasis role=\"pkg\">cruft-ng</emphasis> package."
msgstr ""
msgid "Frontends: <command>aptitude</command>, <command>synaptic</command>"
msgstr ""
msgid "<primary><command>synaptic</command></primary>"
msgstr ""
msgid "<primary>APT</primary><secondary>interfaces</secondary>"
msgstr ""
msgid "APT is a C++ program whose code mainly resides in the <literal>libapt-pkg</literal> shared library. Using a shared library facilitates the creation of user interfaces (front-ends), since the code contained in the library can easily be reused. Historically, <command>apt-get</command> was only designed as a test front-end for <literal>libapt-pkg</literal> but its success tends to obscure this fact."
msgstr ""
msgid "<command>aptitude</command>"
msgstr ""
msgid "<primary>APT</primary><secondary>interfaces</secondary><tertiary><command>aptitude</command></tertiary><see><command>aptitude</command></see>"
msgstr ""
msgid "<command>aptitude</command> is an interactive program that can be used in semi-graphical mode on the console. You can browse the list of installed and available packages, look up all the available information, and select packages to install or remove. The program is designed specifically to be used by administrators, so that its default behaviors are designed to be much more intelligent than <command>apt-get</command>'s, and its interface much easier to understand."
msgstr ""
msgid "The <command>aptitude</command> package manager"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>basic usage</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "When it starts, <command>aptitude</command> shows a list of packages sorted by state (installed, non-installed, or installed but not available on the mirrors — other sections display tasks, virtual packages, and new packages that appeared recently on mirrors). To facilitate thematic browsing, other views are available. In all cases, <command>aptitude</command> displays a list combining categories and packages on the screen. Categories are organized through a tree structure, whose branches can respectively be unfolded or closed with the <keycombo><keycap>Enter</keycap></keycombo>, <keycombo><keycap>[</keycap></keycombo> and <keycombo><keycap>]</keycap></keycombo> keys. <keycombo><keycap>+</keycap></keycombo> should be used to mark a package for installation, <keycombo><keycap>-</keycap></keycombo> to mark it for removal and <keycombo><keycap>_</keycap></keycombo> to purge it (note that these keys can also be used for categories, in which case the corresponding actions will be applied to all the packages of the category). <keycombo><keycap>u</keycap></keycombo> updates the lists of available packages and <keycombo action=\"simul\"><keycap>Shift</keycap><keycap>u</keycap></keycombo> prepares a global system upgrade. <keycombo><keycap>g</keycap></keycombo> switches to a summary view of the requested changes (and typing <keycombo><keycap>g</keycap></keycombo> again will apply the changes), and <keycombo><keycap>q</keycap></keycombo> quits the current view. If you are in the initial view, this will effectively close <command>aptitude</command>."
msgstr ""
msgid "<emphasis>DOCUMENTATION</emphasis> <command>aptitude</command>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>documentation</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "This section does not cover the finer details of using <command>aptitude</command>. It rather focuses on giving you a survival kit to use it. But it is well documented and we advise you to use its complete manual available in the <emphasis role=\"pkg\">aptitude-doc-en</emphasis> package (see <filename>/usr/share/doc/aptitude/html/en/index.html</filename>) or at <ulink url=\"https://www.debian.org/doc/manuals/aptitude/\" />)."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>package search</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "To search for a package, you can type <keycombo><keycap>/</keycap></keycombo> followed by a search pattern. This pattern matches the name of the package, but can also be applied to the description (if preceded by <literal>~d</literal>), to the section (with <literal>~s</literal>) or to other characteristics detailed in the documentation. The same patterns can filter the list of displayed packages: type the <keycombo><keycap>l</keycap></keycombo> key (as in <foreignphrase>limit</foreignphrase>) and enter the pattern."
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>automatic flag</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary><literal>markauto</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Managing the “automatic flag” of Debian packages (see <xref linkend=\"sect.automatic-tracking\" />) is a breeze with <command>aptitude</command>. It is possible to browse the list of installed packages and mark packages as automatic with <keycombo action=\"simul\"><keycap>Shift</keycap> <keycap>m</keycap></keycombo> or to remove the mark with the <keycombo><keycap>m</keycap></keycombo> key. “Automatic packages” are displayed with an “A” in the list of packages. This feature also offers a simple way to visualize the packages in use on a machine, without all the libraries and dependencies that you don't really care about. The related pattern that can be used with <keycombo><keycap>l</keycap></keycombo> (to activate the filter mode) is <literal>~i!~M</literal>. It specifies that you only want to see installed packages (<literal>~i</literal>) not marked as automatic (<literal>!~M</literal>)."
msgstr ""
msgid "<emphasis>TOOL</emphasis> Using <command>aptitude</command> on the command-line interface"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>command line</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Most of <command>aptitude</command>'s features are accessible via the interactive interface as well as via command-lines. These command-lines will seem familiar to regular users of <command>apt-get</command> and <command>apt-cache</command>."
msgstr ""
msgid "The advanced features of <command>aptitude</command> are also available on the command-line. You can use the same package search patterns as in the interactive version. For example, if you want to cleanup the list of “manually installed” packages, and if you know that none of the locally installed programs require any particular libraries or Perl modules, you can mark the corresponding packages as automatic with a single command:"
msgstr ""
msgid "<computeroutput># </computeroutput><userinput>aptitude markauto '~slibs|~sperl'</userinput>"
msgstr ""
msgid "Here, you can clearly see the power of the search pattern system of <command>aptitude</command>, which enables the instant selection of all the packages in the <literal>libs</literal> and <literal>perl</literal> sections."
msgstr ""
msgid "Beware, if some packages are marked as automatic and if no other package depends on them, they will be removed immediately (after a confirmation request)."
msgstr ""
msgid "Managing Recommendations, Suggestions and Tasks"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>tasks</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Another interesting feature of <command>aptitude</command> is the fact that it respects recommendations between packages while still giving users the choice not to install them on a case by case basis. For example, the <emphasis role=\"pkg\">gnome</emphasis> package recommends <emphasis role=\"pkg\">transmission-gtk</emphasis> (among others). When you select the former for installation, the latter will also be selected (and marked as automatic if not already installed on the system). Typing <keycombo><keycap>g</keycap></keycombo> will make it obvious: <emphasis role=\"pkg\">transmission-gtk</emphasis> appears on the summary screen of pending actions in the list of packages installed automatically to satisfy dependencies. However, you can decide not to install it by deselecting it before confirming the operations."
msgstr ""
msgid "Note that this recommendation tracking feature does not apply to upgrades. For instance, if a new version of <emphasis role=\"pkg\">gnome</emphasis> recommends a package that it did not recommend formerly, the package won't be marked for installation. However, it will be listed on the upgrade screen so that the administrator can still select it for installation."
msgstr ""
msgid "Suggestions between packages are also taken into account, but in a manner adapted to their specific status. For example, since <emphasis role=\"pkg\">gnome</emphasis> suggests <emphasis role=\"pkg\">empathy</emphasis>, the latter will be displayed on the summary screen of pending actions (in the section of packages suggested by other packages). This way, it is visible and the administrator can decide whether to take the suggestion into account or not. Since it is only a suggestion and not a dependency or a recommendation, the package will not be selected automatically — its selection requires a manual intervention from the user (thus, the package will not be marked as automatic)."
msgstr ""
msgid "In the same spirit, remember that <command>aptitude</command> makes intelligent use of the concept of task. Since tasks are displayed as categories in the screens of packages lists, you can either select a full task for installation or removal, or browse the list of packages included in the task to select a smaller subset."
msgstr ""
msgid "Better Solver Algorithms"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>solver</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "To conclude this section, let's note that <command>aptitude</command> has more elaborate algorithms compared to <command>apt-get</command> when it comes to resolving difficult situations. When a set of actions is requested and when these combined actions would lead to an incoherent system, <command>aptitude</command> evaluates several possible scenarios and presents them in order of decreasing relevance. However, these algorithms are not failproof. Fortunately there is always the possibility to manually select the actions to perform. When the currently selected actions lead to contradictions, the upper part of the screen indicates a number of “broken” packages (and you can directly navigate to those packages by pressing <keycombo><keycap>b</keycap></keycombo>). It is then possible to manually build a solution for the problems found. In particular, you can get access to the different available versions by simply selecting the package with <keycombo><keycap>Enter</keycap></keycombo>. If the selection of one of these versions solves the problem, you should not hesitate to use the function. When the number of broken packages gets down to zero, you can safely go to the summary screen of pending actions for a last check before you apply them."
msgstr ""
msgid "<emphasis>NOTE</emphasis> <command>aptitude</command>'s log"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary>log</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary><command>aptitude</command></primary><secondary><filename>/var/log/aptitude</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Like <command>dpkg</command>, <command>aptitude</command> keeps a trace of executed actions in its logfile (<filename>/var/log/aptitude</filename>). However, since both commands work at a very different level, you cannot find the same information in their respective logfiles. While <command>dpkg</command> logs all the operations executed on individual packages step by step, <command>aptitude</command> gives a broader view of high-level operations like a system-wide upgrade."
msgstr ""
msgid "Beware, this logfile only contains a summary of operations performed by <command>aptitude</command>. If other front-ends (or even <command>dpkg</command> itself) are occasionally used, then <command>aptitude</command>'s log will only contain a partial view of the operations, so you can't rely on it to build a trustworthy history of the system."
msgstr ""
msgid "<command>synaptic</command>"
msgstr ""
msgid "<primary>APT</primary><secondary>interfaces</secondary><tertiary><command>synaptic</command></tertiary><see><command>synaptic</command></see>"
msgstr ""
msgid "<command>synaptic</command> is a graphical package manager for Debian which features a clean and efficient graphical interface based on GTK+/GNOME. Its many ready-to-use filters give fast access to newly available packages, installed packages, upgradable packages, obsolete packages and so on. If you browse through these lists, you can select the operations to be done on the packages (install, upgrade, remove, purge); these operations are not performed immediately, but put into a task list. A single click on a button then validates the operations, and they are performed in one go."
msgstr ""
msgid "<command>synaptic</command> package manager"
msgstr ""
msgid "Checking Package Authenticity"
msgstr ""
msgid "<primary>package</primary><secondary>authenticity check</secondary>"
msgstr ""
msgid "<primary>package</primary><secondary>seal</secondary>"
msgstr ""
msgid "<primary>package</primary><secondary>signature</secondary>"
msgstr ""
msgid "<primary>signature</primary><secondary>package signature</secondary>"
msgstr ""
msgid "<primary>authentication</primary><secondary>package authentication</secondary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>Release</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>Release.gpg</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>InRelease</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><filename>/etc/apt/trusted.gpg</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><literal>apt-secure</literal></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary>archive authentification</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Security is very important for Falcot Corp administrators. Accordingly, they need to ensure that they only install packages which are guaranteed to come from Debian with no tampering on the way. A computer cracker could try to add malicious code to an otherwise legitimate package. Such a package, if installed, could do anything the cracker designed it to do, including for instance disclosing passwords or confidential information. To circumvent this risk, Debian provides a tamper-proof seal to guarantee — at install time — that a package really comes from its official maintainer and hasn't been modified by a third party."
msgstr ""
msgid "The seal works with a chain of cryptographical hashes and a signature and is explained in detail in <citerefentry><refentrytitle>apt-secure</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Starting with Debian 10 <emphasis role=\"distribution\">Buster</emphasis> the signed file is the <filename>InRelease</filename> file, provided by the Debian mirrors. There is also a legacy file called <filename>Release</filename>. Both contain a list of the <filename>Packages</filename> files (including their compressed forms, <filename>Packages.gz</filename> and <filename>Packages.xz</filename>, and the incremental versions), along with their SHA256 hashes, which ensures that the files haven't been tampered with. These <filename>Packages</filename> files contain a list of the Debian packages available on the mirror, along with their hashes, which ensures in turn that the contents of the packages themselves haven't been altered either. The difference between <filename>InRelease</filename> and <filename>Release</filename> is, that the former are cryptographically signed in-line, whereas the latter provide a detached signature in the form of the file <filename>Release.gpg</filename>."
msgstr ""
msgid "<emphasis>NOTE</emphasis> The future of <filename>Release</filename> and <filename>Release.gpg</filename>"
msgstr ""
msgid "Probably with the release of Debian 11 <emphasis role=\"distribution\">Bullseye</emphasis> APT will remove support for the legacy files <filename>Release</filename> and <filename>Release.gpg</filename>, used since APT 0.6, which introduced support for an archive authentication."
msgstr ""
msgid "<primary><command>apt-key</command></primary>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">debian-archive-keyring</emphasis></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/trusted.gpg.d/</filename></primary>"
msgstr ""
msgid "<primary><filename>/etc/apt/trusted.gpg</filename></primary>"
msgstr ""
msgid "<primary><filename>Release.gpg</filename></primary>"
msgstr ""
msgid "<primary><filename>InRelease</filename></primary>"
msgstr ""
msgid "APT needs a set of trusted GnuPG public keys to verify signatures in the <filename>InRelease</filename> and <filename>Release.gpg</filename> files available on the mirrors. It gets them from files in <filename>/etc/apt/trusted.gpg.d/</filename> and from the <filename>/etc/apt/trusted.gpg</filename> keyring (managed by the <command>apt-key</command> command). The official Debian keys are provided and kept up-to-date by the <emphasis role=\"pkg\">debian-archive-keyring</emphasis> package which puts them in <filename>/etc/apt/trusted.gpg.d/</filename>. Note, however, that the first installation of this particular package requires caution: even if the package is signed like any other, the signature cannot be verified externally. Cautious administrators should therefore check the fingerprints of imported keys before trusting them to install new packages:"
msgstr ""
msgid ""
"<computeroutput># </computeroutput><userinput>apt-key fingerprint\n"
"</userinput><![CDATA[/etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg\n"
"----------------------------------------------------------\n"
"pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]\n"
" 80D1 5823 B7FD 1561 F9F7 BCDD DC30 D7C2 3CBB ABEE\n"
"uid [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>\n"
"sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg\n"
"-------------------------------------------------------------------\n"
"pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]\n"
" 5E61 B217 265D A980 7A23 C5FF 4DFA B270 CAA9 6DFA\n"
"uid [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>\n"
"sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg\n"
"-------------------------------------------------------\n"
"pub rsa4096 2019-02-05 [SC] [expires: 2027-02-03]\n"
" 6D33 866E DD8F FA41 C014 3AED DCC9 EFBF 77E1 1517\n"
"uid [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org>\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg\n"
"----------------------------------------------------------\n"
"pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]\n"
" 126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010\n"
"uid [ unknown] Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg\n"
"-------------------------------------------------------------------\n"
"pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]\n"
" D211 6914 1CEC D440 F2EB 8DDA 9D6D 8F6B C857 C906\n"
"uid [ unknown] Debian Security Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg\n"
"-------------------------------------------------------\n"
"pub rsa4096 2013-08-17 [SC] [expires: 2021-08-15]\n"
" 75DD C3C4 A499 F1A1 8CB5 F3C8 CBF8 D6FD 518E 17E1\n"
"uid [ unknown] Jessie Stable Release Key <debian-release@lists.debian.org>\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg\n"
"-----------------------------------------------------------\n"
"pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]\n"
" E1CF 20DD FFE4 B89E 8026 58F1 E0B1 1894 F66A EC98\n"
"uid [ unknown] Debian Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>\n"
"sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg\n"
"--------------------------------------------------------------------\n"
"pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]\n"
" 6ED6 F5CB 5FA6 FB2F 460A E88E EDA0 D238 8AE2 2BA9\n"
"uid [ unknown] Debian Security Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>\n"
"sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]\n"
"\n"
"/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg\n"
"--------------------------------------------------------\n"
"pub rsa4096 2017-05-20 [SC] [expires: 2025-05-18]\n"
" 067E 3C45 6BAE 240A CEE8 8F6F EF0F 382A 1A7B 6500\n"
"uid [ unknown] Debian Stable Release Key (9/stretch) <debian-release@lists.debian.org>\n"
"\n"
"]]>"
msgstr ""
msgid "<emphasis>IN PRACTICE</emphasis> Adding trusted keys"
msgstr ""
msgid "<primary>trusted key</primary>"
msgstr ""
msgid "<primary>key</primary><secondary>APT's authentication keys</secondary>"
msgstr ""
msgid "When a third-party package source is added to the <filename>sources.list</filename> file, APT needs to be told to trust the corresponding GPG authentication key (otherwise it will keep complaining that it can't ensure the authenticity of the packages coming from that repository). The first step is of course to get the public key. More often than not, the key will be provided as a small text file, which we will call <filename>key.asc</filename> in the following examples."
msgstr ""
msgid "To add the key to the trusted keyring, the administrator can just put it in a <filename>*.asc</filename> file in <filename>/etc/apt/trusted.gpg.d/</filename>. This is supported since Debian <emphasis role=\"distribution\">Stretch</emphasis>. With older releases, you had to run <command>apt-key add < key.asc</command>."
msgstr ""
msgid "Once the appropriate keys are in the keyring, APT will check the signatures before any risky operation, so that front-ends will display a warning if asked to install a package whose authenticity can't be ascertained."
msgstr ""
msgid "Upgrading from One Stable Distribution to the Next"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>system</primary><secondary><foreignphrase>dist-upgrade</foreignphrase></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "<primary><foreignphrase>dist-upgrade</foreignphrase></primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>APT</primary><secondary><foreignphrase>dist-upgrade</foreignphrase></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "One of the best-known features of Debian is its ability to upgrade an installed system from one stable release to the next: <foreignphrase>dist-upgrade</foreignphrase> — a well-known phrase — has largely contributed to the project's reputation. With a few precautions, upgrading a computer can take as little as a few minutes, or a few dozen minutes, depending on the download speed from the package repositories."
msgstr ""
msgid "Recommended Procedure"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>system</primary><secondary><foreignphrase>release notes</foreignphrase></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Since Debian has quite some time to evolve in-between stable releases, you should read the release notes before upgrading."
msgstr ""
msgid "<emphasis>BACK TO BASICS</emphasis> Release notes"
msgstr ""
msgid "<primary>release notes</primary>"
msgstr ""
msgid "The release notes for an operating system (and, more generally, for any software) are a document giving an overview of the software, with some details concerning the particularities of one version. These documents are generally short compared to the complete documentation, and they usually list the features which have been introduced since the previous version. They also give details on upgrading procedures, warnings for users of previous versions, and sometimes errata."
msgstr ""
msgid "Release notes are available online: the release notes for the current stable release have a dedicated URL, while older release notes can be found with their codenames: <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/releasenotes\" /> <ulink type=\"block\" url=\"https://www.debian.org/releases/stretch/releasenotes\" />"
msgstr ""
msgid "In this section, we will focus on upgrading a <emphasis role=\"distribution\">Stretch</emphasis> system to <emphasis role=\"distribution\">Buster</emphasis>. This is a major operation on a system; as such, it is never 100% risk-free, and should not be attempted before all important data has been backed up."
msgstr ""
msgid "Another good habit which makes the upgrade easier (and shorter) is to tidy your installed packages and keep only the ones that are really needed. Helpful tools to do that include <command>aptitude</command>, <command>deborphan</command> and <command>debfoster</command> (see <xref linkend=\"sect.automatic-tracking\" />). For example, you can use the following command, and then use <command>aptitude</command>'s interactive mode to double check and fine-tune the scheduled removals:"
msgstr ""
msgid "# <userinput>deborphan | xargs aptitude --schedule-only remove</userinput>"
msgstr ""
msgid "<emphasis>TIP</emphasis> Finding changed files"
msgstr ""
msgid "<primary><command>debsums</command></primary>"
msgstr ""
msgid "The <command>debsums</command> command can check if files on the local system, which are part of an installed package, have been altered. It uses a simple hashsum algorithm and the information in <filename>/var/lib/dpkg/info/<replaceable>package</replaceable>.md5sums</filename> (see <xref linkend=\"sect.conffiles\" />). To find all altered configuration files use <command>debsums -ec</command>. To check the whole system, use <command>debsums -c</command>."
msgstr ""
msgid "Now for the upgrading itself. First, you need to change the <filename>/etc/apt/sources.list</filename> file to tell APT to get its packages from <emphasis role=\"distribution\">Buster</emphasis> instead of <emphasis role=\"distribution\">Stretch</emphasis>. If the file only contains references to <emphasis role=\"distribution\">Stable</emphasis> rather than explicit codenames, the change isn't even required, since <emphasis role=\"distribution\">Stable</emphasis> always refers to the latest released version of Debian. In both cases, the database of available packages must be refreshed (with the <command>apt update</command> command or the refresh button in <command>synaptic</command>)."
msgstr ""
msgid "<emphasis>NOTE</emphasis> Repository information changes"
msgstr ""
msgid "When a new stable version of Debian is released, some fields in the <filename>Release</filename> and <filename>InRelease</filename> files of a repository change, like the <literal>Suite</literal> field. When this happens, downloading data from the repository is declined until the change is confirmed to ensure the user is prepared for it. To confirm the change use the <literal>--allow-releaseinfo-change</literal> or <literal>--allow-releaseinfo-change-<replaceable>field</replaceable></literal> options for <command>apt-get</command> or the <literal>Acquire::AllowReleaseInfoChange</literal> configuration option."
msgstr ""
msgid "Once these new package sources are registered, you should first do a minimal upgrade with <command>apt upgrade</command>. By doing the upgrade in two steps, we ease the job of the package management tools and often ensure that we have the latest versions of those, which might have accumulated bugfixes and improvements required to complete the full distribution upgrade."
msgstr ""
msgid "Once this first upgrade is done, it is time to handle the upgrade itself, either with <command>apt full-upgrade</command>, <command>aptitude</command>, or <command>synaptic</command>. You should carefully check the suggested actions before applying them: you might want to add suggested packages or deselect packages which are only recommended and known not to be useful. In any case, the front-end should come up with a scenario ending in a coherent and up-to-date <emphasis role=\"distribution\">Buster</emphasis> system. Then, all you need is to do is wait while the required packages are downloaded, answer the debconf questions and possibly those about locally modified configuration files, and sit back while APT does its magic."
msgstr ""
msgid "Handling Problems after an Upgrade"
msgstr ""
msgid "In spite of the Debian maintainers' best efforts, a major system upgrade isn't always as smooth as you could wish. New software versions may be incompatible with previous ones (for instance, their default behavior or their data format may have changed). Also, some bugs may slip through the cracks despite the testing phase which always precedes a Debian release."
msgstr ""
msgid "To anticipate some of these problems, you can install the <emphasis role=\"pkg\">apt-listchanges</emphasis> package, which displays information about possible problems at the beginning of a package upgrade. This information is compiled by the package maintainers and put in <filename>/usr/share/doc/<replaceable>package</replaceable>/NEWS.Debian</filename> files for the benefit of users. Reading these files (possibly through <emphasis role=\"pkg\">apt-listchanges</emphasis>) should help you avoid bad surprises."
msgstr ""
msgid "You might sometimes find that the new version of a software doesn't work at all. This generally happens if the application isn't particularly popular and hasn't been tested enough; a last-minute update can also introduce regressions which are only found after the stable release. In both cases, the first thing to do is to have a look at the bug tracking system at <ulink url=\"https://bugs.debian.org\"><literal>https://bugs.debian.org/<replaceable>package</replaceable></literal></ulink>, and check whether the problem has already been reported. If this is case it will be also listed before the upgrade begins, if you have <emphasis role=\"pkg\">apt-listbugs</emphasis> installed. If it hasn't, you should report it yourself with <command>reportbug</command>. If it is already known, the bug report and the associated messages are usually an excellent source of information related to the bug:"
msgstr ""
msgid "sometimes a patch already exists, and it is available on the bug report; you can then recompile a fixed version of the broken package locally (see <xref linkend=\"sect.rebuilding-package\" />);"
msgstr ""
msgid "in other cases, users may have found a workaround for the problem and shared their insights about it in their replies to the report;"
msgstr ""
msgid "in yet other cases, a fixed package may have already been prepared and made public by the maintainer."
msgstr ""
msgid "Depending on the severity of the bug, a new version of the package may be prepared specifically for a new revision of the stable release. When this happens, the fixed package is made available in the <literal>proposed-updates</literal> section of the Debian mirrors (see <xref linkend=\"sect.apt-sources.list.stable.proposed-updates\" />). The corresponding entry can then be temporarily added to the <filename>sources.list</filename> file, and updated packages can be installed with <command>apt</command> or <command>aptitude</command>."
msgstr ""
msgid "Sometimes the fixed package isn't available in this section yet because it is pending a validation by the Stable Release Managers. You can verify if that is the case on their web page. Packages listed there aren't available yet, but at least you know that the publication process is ongoing. <ulink type=\"block\" url=\"https://release.debian.org/proposed-updates/stable.html\" />"
msgstr ""
msgid "Cleaning Up after an Upgrade"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>upgrade</primary><secondary>cleaning</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "APT usually ensures a clean upgrade, pulling in new and updated dependencies, or removing conflicting packages. But even being such a great tool, it cannot cover all tasks users and administrators will face after an upgrade, because they require a human decision."
msgstr ""
msgid "Packages removed from the Debian Archive"
msgstr ""
msgid "<primary><command>apt-show-versions</command></primary>"
msgstr ""
msgid "Sometimes the Debian FTP Masters remove packages from the Debian archive, because they contain release critical bugs, were abandoned by their upstream author or their package maintainer, or simply reached their end of life. In this case a newer Debian release does not ship the package anymore. To find all packages, which do not have a package source, use the <command>apt-show-versions</command> command:"
msgstr ""
msgid "<computeroutput>$ </computeroutput><userinput>apt-show-versions | grep \"No available version\"</userinput>"
msgstr ""
msgid "A similar result can be achieved by <command>aptitude search ~o</command>. If the packages found are not required anymore, they should be purged from the system, because they will not face any updates for critical or security related bugs anymore."
msgstr ""
msgid "Dummy and Transitional Packages"
msgstr ""
msgid "<primary>dummy package</primary>"
msgstr ""
msgid "<primary>transitional package</primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>transitional</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>dummy</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Sometimes, it might be necessary for a package to get a new name. In this case often the old package is kept as an (almost) empty package, depending on the new one and installing only the mandatory files in <filename>/usr/share/doc/<replaceable>package</replaceable>/</filename>. Such packages are called \"dummy\" or \"transitional\" packages. If the package maintainer in charge also changed the section of this package to <literal>oldlibs</literal>, then tools like <command>aptitude</command>, <command>deboprhan</command>, or <command>debfoster</command> (see sidebar <xref linkend=\"sidebar.deborphan-debfoster\" />) can pickup these packages to suggest their removal."
msgstr ""
msgid "Unfortunately there is currently no foolproof way of making sure that these packages are automatically removed or picked by the tools mentioned above. One way to check if the system still has some of these packages installed, is to look through the package descriptions of installed packages and then check the results. Be careful not to schedule the results for automatic removal, because this method can lead to false positives:"
msgstr ""
msgid "<computeroutput>$ </computeroutput><userinput>dpkg -l | grep ^ii | grep -i -E \"(transition|dummy)\"</userinput>"
msgstr ""
msgid "Because the new package is pulled in as a dependency of the transitional package, it is usually marked as automatically installed and might be scheduled for removal if you try to purge the transitional package from your system. In this case you can use either of the approaches described in sidebar <xref linkend=\"sidebar.apt-install-and-remove\" /> and <xref linkend=\"sect.automatic-tracking\" /> to selectively remove the transitional package."
msgstr ""
msgid "Old or Unused Configuration Files"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>configuration files</primary><secondary><filename>.dpkg-dist</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>configuration files</primary><secondary><filename>.dpkg-old</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>configuration files</primary><secondary><filename>.ucf-old</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>configuration files</primary><secondary><filename>.ucf-new</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>configuration files</primary><secondary><filename>.ucf-dist</filename></secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "If the upgrade was successful there might be some configuration file cruft, either from dpkg (see <xref linkend=\"sect.conffiles\" />), ucf or from removed packages. The latter can be <link linkend=\"sidebar.purge\">purged</link> by using <command>apt autoremove --purge</command>. The configuration files, that were handled by <emphasis role=\"pkg\">dpkg</emphasis> or <emphasis role=\"pkg\">ucf</emphasis> during the upgrade process, have left some counterparts with a dedicated suffix (e.g. <filename>.dpkg-dist</filename>, <filename>.dpkg-old</filename>, <filename>.ucf-old</filename>). Using the <command>find</command> or <command>locate</command> command can help to track them down. If they are no longer of any use, they can be deleted."
msgstr ""
msgid "Files not owned by any Package"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">cruft</emphasis></primary>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">cruft-ng</emphasis></primary>"
msgstr ""
msgid "The Debian policy enforces that packages don't leave files behind when they are purged. Violating this principle is a serious bug and you will rarely encounter it. If you do, report it; and if you are curious though, you can use the <emphasis role=\"pkg\">cruft</emphasis> or <emphasis role=\"pkg\">cruft-ng</emphasis> package to check your system for files not owned by any package."
msgstr ""
msgid "Keeping a System Up to Date"
msgstr ""
msgid "The Debian distribution is dynamic and changes continually. Most of the changes are in the <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis> versions, but even <emphasis role=\"distribution\">Stable</emphasis> is updated from time to time, mostly for security-related fixes. Whatever version of Debian a system runs, it is generally a good idea to keep it up to date, so that you can get the benefit of recent evolution and bug fixes."
msgstr ""
msgid "While it is of course possible to periodically run a tool to check for available updates and run the upgrades, such a repetitive task is tedious, especially when it needs to be performed on several machines. Fortunately, like many repetitive tasks, it can be partly automated, and a set of tools have already been developed to that effect."
msgstr ""
msgid "The first of these tools is <command>apticron</command>, in the package of the same name. Its main effect is to run a script daily (via <command>cron</command>). The script updates the list of available packages, and, if some installed packages are not in the latest available version, it sends an email with a list of these packages along with the changes that have been made in the new versions. Obviously, this package mostly targets users of Debian <emphasis role=\"distribution\">Stable</emphasis>, since the daily emails would be very long for the faster paced versions of Debian. When updates are available, <command>apticron</command> automatically downloads them. It does not install them — the administrator will still do it — but having the packages already downloaded and available locally (in APT's cache) makes the job faster."
msgstr ""
msgid "Administrators in charge of several computers will no doubt appreciate being informed of pending upgrades, but the upgrades themselves are still as tedious as they used to be. Periodic upgrades can be enabled: it uses a <command>systemd</command> timer unit or <command>cron</command>. If <emphasis role=\"pkg\">systemd</emphasis> is not installed, the <filename>/etc/cron.daily/apt-compat</filename> script (in the <emphasis role=\"pkg\">apt</emphasis> package) comes in handy. This script is run daily (and non-interactively) by <command>cron</command>. To control the behavior, use APT configuration variables (which are therefore stored in a file <filename>/etc/apt/apt.conf.d/10periodic</filename>). The main variables are:"
msgstr ""
msgid "<indexterm><primary>APT</primary><secondary><literal>APT::Periodic::Update-Package-Lists</literal></secondary></indexterm> <literal>APT::Periodic::Update-Package-Lists</literal>"
msgstr ""
msgid "This option allows you to specify the frequency (in days) at which the package lists are refreshed. <command>apticron</command> users can do without this variable, since <command>apticron</command> already does this task."
msgstr ""
msgid "<indexterm><primary>APT</primary><secondary><literal>APT::Periodic::Download-Upgradeable-Packages</literal></secondary></indexterm> <literal>APT::Periodic::Download-Upgradeable-Packages</literal>"
msgstr ""
msgid "Again, this option indicates a frequency (in days), this time for the downloading of the actual packages. Again, <command>apticron</command> users won't need it."
msgstr ""
msgid "<indexterm><primary>APT</primary><secondary><literal>APT::Periodic::AutocleanInterval</literal></secondary></indexterm> <literal>APT::Periodic::AutocleanInterval</literal>"
msgstr ""
msgid "This option covers a feature that <command>apticron</command> doesn't have. It controls how often obsolete packages (those not referenced by any distribution anymore) are removed from the APT cache. This keeps the APT cache at a reasonable size and means that you don't need to worry about that task."
msgstr ""
msgid "<indexterm><primary>APT</primary><secondary><literal>APT::Periodic::Unattended-Upgrade</literal></secondary></indexterm> <literal>APT::Periodic::Unattended-Upgrade</literal>"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">unattended-upgrades</emphasis></primary><secondary><filename>/etc/apt/apt.conf.d/50unattended-upgrades</filename></secondary>"
msgstr ""
msgid "<primary><filename>/etc/apt/apt.conf.d/50unattended-upgrades</filename></primary>"
msgstr ""
msgid "When this option is enabled, the daily script will execute <command>unattended-upgrade</command> (from the <emphasis role=\"pkg\">unattended-upgrades</emphasis> package) which — as its name suggest — can automatize the upgrade process for some packages (by default it only takes care of security updates, but this can be customized in <filename>/etc/apt/apt.conf.d/50unattended-upgrades</filename>). Note that this option can be set with the help of debconf by running <command>dpkg-reconfigure -plow unattended-upgrades</command>. If <emphasis role=\"pkg\">apt-listbugs</emphasis> is installed it will prevent an automatic upgrade of packages which are affected by an already reported serious or grave bug."
msgstr ""
msgid "Other options can allow you to control the cache cleaning behavior with more precision. They are not listed here, but they are described in the <filename>/usr/lib/apt/apt.systemd.daily</filename> script."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">gnome-packagekit</emphasis></primary>"
msgstr ""
msgid "These tools work very well for servers, but desktop users generally prefer a more interactive system. The package <emphasis role=\"pkg\">gnome-software</emphasis> provides an icon in the notification area of desktop environments when updates are available; clicking on this icon then runs an interface to perform updates. You can browse through available updates, read the short description of the relevant packages and the corresponding <filename>changelog</filename> entries, and select whether to apply the update or not on a case-by-case basis."
msgstr ""
msgid "Upgrading with <command>gpk-update-viewer</command>"
msgstr ""
msgid "This tool is no longer installed in the default GNOME desktop. The new philosophy is that security updates should be automatically installed, either in the background or, preferably, when you shutdown your computer so as to not confuse any running application."
msgstr ""
msgid "Automatic Upgrades"
msgstr ""
msgid "<primary>upgrade</primary><secondary>automatic system upgrade</secondary>"
msgstr ""
msgid "<primary>automatic upgrade</primary>"
msgstr ""
msgid "Since Falcot Corp has many computers but only limited manpower, its administrators try to make upgrades as automatic as possible. The programs in charge of these processes must therefore run with no human intervention."
msgstr ""
msgid "Configuring <command>dpkg</command>"
msgstr ""
msgid "As we have already mentioned (see sidebar <xref linkend=\"sidebar.questions-conffiles\" />), <command>dpkg</command> can be instructed not to ask for confirmation when replacing a configuration file (with the <literal>--force-confdef --force-confold</literal> options). Interactions can, however, have three other sources: some come from APT itself, some are handled by <command>debconf</command>, and some happen on the command line due to package configuration scripts (sometimes handled by <emphasis role=\"pkg\">ucf</emphasis>)."
msgstr ""
msgid "Configuring APT"
msgstr ""
msgid "The case of APT is simple: the <literal>-y</literal> option (or <literal>--assume-yes</literal>) tells APT to consider the answer to all its questions to be “yes”."
msgstr ""
msgid "Configuring <command>debconf</command>"
msgstr ""
msgid "The case of <command>debconf</command> deserves more details. This program was, from its inception, designed to control the relevance and volume of questions displayed to the user, as well as the way they are shown. That is why its configuration requests a minimal priority for questions; only questions above the minimal priority are displayed. <command>debconf</command> assumes the default answer (defined by the package maintainer) for questions which it decided to skip."
msgstr ""
msgid "The other relevant configuration element is the interface used by the front-end. If you choose <literal>noninteractive</literal> out of the choices, all user interaction is disabled. If a package tries to display an informative note, it will be sent to the administrator by email."
msgstr ""
msgid "To reconfigure <command>debconf</command>, use the <command>dpkg-reconfigure</command> tool from the <emphasis role=\"pkg\">debconf</emphasis> package; the relevant command is <command>dpkg-reconfigure debconf</command>. Note that the configured values can be temporarily overridden with environment variables when needed (for instance, <varname>DEBIAN_FRONTEND</varname> controls the interface, as documented in the <citerefentry><refentrytitle>debconf</refentrytitle><manvolnum>7</manvolnum></citerefentry> manual page)."
msgstr ""
msgid "Handling Command Line Interactions"
msgstr ""
msgid "The last source of interactions, and the hardest to get rid of, is the configuration scripts run by <command>dpkg</command>. There is unfortunately no standard solution, and no answer is overwhelmingly better than another."
msgstr ""
msgid "The common approach is to suppress the standard input by redirecting the empty content of <filename>/dev/null</filename> into it with <command><replaceable>command</replaceable> </dev/null</command>, or to feed it with an endless stream of newlines. None of these methods is 100 % reliable, but they generally lead to the default answers being used, since most scripts consider a lack of reply as an acceptance of the default value."
msgstr ""
msgid "The Miracle Combination"
msgstr ""
msgid "By combining the previous elements, it is possible to design a small but rather reliable script which can handle automatic upgrades."
msgstr ""
msgid "Non-interactive upgrade script"
msgstr ""
msgid ""
"export DEBIAN_FRONTEND=noninteractive\n"
"yes '' | apt-get -y -o DPkg::options::=\"--force-confdef\" -o DPkg::options::=\"--force-confold\" dist-upgrade"
msgstr ""
msgid "<emphasis>IN PRACTICE</emphasis> The Falcot Corp case"
msgstr ""
msgid "Falcot computers are a heterogeneous system, with machines having various functions. Administrators will therefore pick the most relevant solution for each computer."
msgstr ""
msgid "In practice, the servers running <emphasis role=\"distribution\">Buster</emphasis> are configured with the “miracle combination” above, and are kept up to date automatically. Only the most critical servers (the firewalls, for instances) are set up with <command>apticron</command>, so that upgrades always happen under the supervision of an administrator."
msgstr ""
msgid "The office workstations in the administrative services also run <emphasis role=\"distribution\">Buster</emphasis>, but they are equipped with <emphasis role=\"pkg\">gnome-packagekit</emphasis>, so that users trigger the upgrades themselves. The rationale for this decision is that if upgrades happen without an explicit action, the behavior of the computer might change unexpectedly, which could cause confusion for the main users."
msgstr ""
msgid "In the lab, the few computers using <emphasis role=\"distribution\">Testing</emphasis> — to take advantage of the latest software versions — are not upgraded automatically either. Administrators only configure APT to prepare the upgrades but not enact them; when they decide to upgrade (manually), the tedious parts of refreshing package lists and downloading packages will be avoided, and administrators can focus on the really useful part."
msgstr ""
msgid "Searching for Packages"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>search package</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "With the large and ever-growing amount of software in Debian, there emerges a paradox: Debian usually has a tool for most tasks, but that tool can be very difficult to find amongst the myriad other packages. The lack of appropriate ways to search for (and to find) the right tool has long been a problem. Fortunately, this problem has almost entirely been solved."
msgstr ""
msgid "The most trivial search possible is looking up an exact package name. If <command>apt show <replaceable>package</replaceable></command> returns a result, then the package exists. Unfortunately, this requires knowing or even guessing the package name, which isn't always possible."
msgstr ""
msgid "<emphasis>TIP</emphasis> Package naming conventions"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>naming conventions</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Some categories of packages are named according to a conventional naming scheme; knowing the scheme can sometimes allow you to guess exact package names. For instance, for Perl modules, the convention says that a module called <literal>XML::Handler::Composer</literal> upstream should be packaged as <emphasis role=\"pkg\">libxml-handler-composer-perl</emphasis>. The library enabling the use of the <command>gconf</command> system from Python is packaged as <emphasis role=\"pkg\">python-gconf</emphasis>. It is unfortunately not possible to define a fully general naming scheme for all packages, even though package maintainers usually try to follow the choice of the upstream developers."
msgstr ""
msgid "A slightly more successful searching pattern is a plain-text search in package names, but it remains very limited. You can generally find results by searching package descriptions: since each package has a more or less detailed description in addition to its package name, a keyword search in these descriptions will often be useful. <command>apt-cache</command> and <command>axi-cache</command> are the tools of choice for this kind of search (see <xref linkend=\"sidebar.apt-axi-cache\" />); for instance, <command>apt-cache search video</command> will return a list of all packages whose name or description contains the keyword “video”."
msgstr ""
msgid "For more complex searches, a more powerful tool such as <command>aptitude</command> is required. <command>aptitude</command> allows you to search according to a logical expression based on the package's meta-data fields. For instance, the following command searches for packages whose name contains <literal>kino</literal>, whose description contains <literal>video</literal> and whose maintainer's name contains <literal>paul</literal>:"
msgstr ""
msgid ""
"$ <userinput>aptitude search kino~dvideo~mpaul</userinput>\n"
"p kino - Non-linear editor for Digital Video data\n"
"$ <userinput>aptitude show kino</userinput>\n"
"<![CDATA[Package: kino \n"
"Version: 1.3.4+dfsg0-1\n"
"State: not installed\n"
"Priority: optional\n"
"Section: video\n"
"Maintainer: Paul Brossier <piem@debian.org>\n"
"Architecture: amd64\n"
"Uncompressed Size: 8,304 k\n"
"Depends: libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4), libavc1394-0 (>= 0.5.3), libavcodec58 (>=\n"
" 7:4.0) | libavcodec-extra58 (>= 7:4.0), libavformat58 (>= 7:4.0), libavutil56 (>= 7:4.0),\n"
" libc6 (>= 2.14), libcairo2 (>= 1.2.4), libdv4 (>= 1.0.0), libfontconfig1 (>= 2.12.6),\n"
" libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglade2-0\n"
" (>= 1:2.6.4-2~), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.24.32), libice6 (>= 1:1.0.0),\n"
" libiec61883-0 (>= 1.2.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0),\n"
" libpangoft2-1.0-0 (>= 1.14.0), libquicktime2 (>= 2:1.2.2), libraw1394-11, libsamplerate0\n"
" (>= 0.1.7), libsm6, libstdc++6 (>= 5.2), libswscale5 (>= 7:4.0), libx11-6, libxext6,\n"
" libxml2 (>= 2.7.4), libxv1, zlib1g (>= 1:1.1.4)\n"
"Recommends: ffmpeg, curl\n"
"Suggests: udev | hotplug, vorbis-tools, sox, mjpegtools, lame, ffmpeg2theora\n"
"Conflicts: kino-dvtitler, kino-timfx, kinoplus\n"
"Replaces: kino-dvtitler, kino-timfx, kinoplus\n"
"Provides: kino-dvtitler, kino-timfx, kinoplus\n"
"Description: Non-linear editor for Digital Video data\n"
" Kino allows you to record, create, edit, and play movies recorded with DV camcorders. This program\n"
" uses many keyboard commands for fast navigating and editing inside the movie.\n"
"\n"
" The kino-timfx, kino-dvtitler and kinoplus sets of plugins, formerly distributed as separate\n"
" packages, are now provided with Kino.\n"
"Homepage: http://www.kinodv.org/\n"
"Tags: field::arts, hardware::camera, implemented-in::c, implemented-in::c++, interface::graphical,\n"
" interface::x11, role::program, scope::application, suite::gnome, uitoolkit::gtk,\n"
" use::editing, use::learning, works-with::video, x11::application\n"
"]]>"
msgstr ""
msgid "The search only returns one package, <emphasis role=\"pkg\">kino</emphasis>, which satisfies all three criteria."
msgstr ""
msgid "Even these multi-criteria searches are rather unwieldy, which explains why they are not used as much as they could. A new tagging system has therefore been developed, and it provides a new approach to searching. Packages are given tags that provide a thematical classification along several strands, known as a “facet-based classification”. In the case of <emphasis role=\"pkg\">kino</emphasis> above, the package's tags indicate that Kino is a Gnome-based software that works on video data and whose main purpose is editing."
msgstr ""
msgid "Browsing this classification can help you to search for a package which corresponds to known needs; even if it returns a (moderate) number of hits, the rest of the search can be done manually. To do that, you can use the <literal>~G</literal> search pattern in <command>aptitude</command>, but it is probably easier to simply navigate the site where tags are managed: <ulink type=\"block\" url=\"https://debtags.debian.org/\" />"
msgstr ""
msgid "<primary><emphasis role=\"pkg\">debtags</emphasis></primary>"
msgstr ""
msgid "<primary>tag</primary>"
msgstr ""
#, fuzzy
#| msgid "<primary>installation</primary><secondary>package installation</secondary>"
msgid "<primary>package</primary><secondary>tags</secondary>"
msgstr "<primary>instalacija</primary><secondary>instalacija paketa</secondary>"
msgid "Selecting the <literal>works-with::video</literal> and <literal>use::editing</literal> tags yields a handful of packages, including the <emphasis role=\"pkg\">kino</emphasis> and <emphasis role=\"pkg\">pitivi</emphasis> video editors. This system of classification is bound to be used more and more as time goes on, and package managers will gradually provide efficient search interfaces based on it."
msgstr ""
msgid "To sum up, the best tool for the job depends on the complexity of the search that you wish to do:"
msgstr ""
msgid "<command>apt-cache</command> only allows searching in package names and descriptions, which is very convenient when looking for a particular package that matches a few target keywords;"
msgstr ""
msgid "when the search criteria also include relationships between packages or other meta-data such as the name of the maintainer, <command>synaptic</command> will be more useful;"
msgstr ""
msgid "when a tag-based search is needed, a good tool is <command>packagesearch</command>, a graphical interface dedicated to searching available packages along several criteria (including the names of the files that they contain). For usage on the command-line, <command>axi-cache</command> will fit the bill."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">packagesearch</emphasis></primary>"
msgstr ""
msgid "finally, when the searches involve complex expressions with logic operations, the tool of choice will be <command>aptitude</command>'s search pattern syntax, which is quite powerful despite being somewhat obscure; it works in both the command-line and the interactive modes."
msgstr ""
|