/usr/share/aptitude/README is in aptitude-common 0.8.10-6ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 | <?xml version="1.0" encoding="UTF-8"?>
aptitude user's manual
Version 0.8.10
Daniel Burrows
Main author of the document. <dburrows@debian.org>
Manuel A. Fernandez Montecelo
Main maintainer after Daniel Burrows, documentation about new features,
corrections and formatting. <mafm@debian.org>
Copyright © 2004-2011, 2012-2016 Daniel Burrows, Manuel A. Fernandez Montecelo
This manual is free software; you can redistribute it and/or modify it under the
terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version.
This manual is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with
this manual; if not, write to the Free Software Foundation, Inc., 51 Franklin
St, Fifth Floor, Boston, MA 02110-1301 USA
--------------------------------------------------------------------------------
Table of Contents
Introduction
What is this aptitude thing, anyway?
What is a package manager?
What is the apt system?
How can I get aptitude?
Pre-built aptitude packages, or, “what 99% of users should do”
Building aptitude from source code
Tracking and participating in aptitude development
1. Getting started
Using aptitude
aptitude basics
Navigating the aptitude package list
Finding packages by name
Managing packages
Updating the package list and installing packages
Using aptitude from the command line
2. aptitude reference guide
The aptitude terminal user interface
Using the menus
Menu commands
Working with multiple views
Becoming root
Managing packages
Managing the package list
Accessing package information
Modifying package states
Downloading, installing, and removing packages
Understanding and managing package trust
Managing automatically installed packages
Resolving package dependencies
Dependency resolution in aptitude
Immediate dependency resolution
Resolving Dependencies Interactively
Costs in the interactive dependency resolver
Configuring the interactive dependency resolver
Search patterns
Searching for strings
Shorthand for search terms
Searches and versions
Explicit search targets
Search term reference
Customizing aptitude
Customizing the package list
Customizing keybindings
Customizing text colors and styles
Customizing the display layout
Configuration file reference
Themes
Playing Minesweeper
3. aptitude frequently asked questions
4. Credits
I. Command-line reference
aptitude — high-level interface to the package manager
aptitude-create-state-bundle — bundle the current aptitude state
aptitude-run-state-bundle — unpack an aptitude state bundle and invoke
aptitude on it
List of Figures
2.1. Commands available in the Actions menu
2.2. Commands available in the Undo menu
2.3. Commands available in the Package menu
2.4. Commands available in the Resolver menu
2.5. Commands available in the Search menu
2.6. Commands available in the Options menu
2.7. Commands available in the Views menu
2.8. Commands available in the Help menu
2.9. Values of the “current state” flag
2.10. Values of the “action” flag
2.11. Syntax of compound cost components
2.12. Safety cost levels
2.13. Syntax of the ?for term
2.14. Customizable styles in aptitude
List of Tables
2.1. Basic cost components
2.2. Default safety cost levels
2.3. Quick guide to search terms
List of Examples
2.1. Sample resolver costs
2.2. Use of the ?= term.
2.3. Use of the ?bind term
2.4. Use of the ?exact-name term
2.5. Use of the ?for term
2.6. Use of the ?term-prefix term
2.7. Grouping policy firstchar or firstchar(binary)
2.8. Grouping policy firstchar(source)
2.9. Use of pattern to group packages by their maintainer
2.10. Use of pattern with some packages placed at the top level
2.11. Use of the pattern grouping policy with sub-policies
12. Usage of --show-summary
Introduction
Table of Contents
What is this aptitude thing, anyway?
What is a package manager?
What is the apt system?
How can I get aptitude?
Pre-built aptitude packages, or, “what 99% of users should do”
Building aptitude from source code
Tracking and participating in aptitude development
“Master, does Emacs possess the Buddha nature?” the novice asked.
“I don't see why not,” replied the master. “It's got bloody well everything
else.” Several years later, the novice suddenly achieved enlightenment.
-- John Fouhy
Hello, and welcome to the aptitude user's manual! This introductory section
explains what aptitude is and how to get your hands on it; for information on
actually using it, please proceed to Chapter 1, Getting started.
What is this aptitude thing, anyway?
aptitude is a featureful package manager for Debian GNU/Linux systems, based on
the renowned apt package management infrastructure. aptitude provides the
functionality of dselect and apt-get, as well as many additional features not
found in either program.
What is a package manager?
A package manager keeps track of what software is installed on your computer,
and allows you to easily install new software, upgrade software to newer
versions, or remove software that you previously installed. As the name
suggests, package managers deal with packages: collections of files that are
bundled together and can be installed and removed as a group.
Often, a package is just a particular program. For instance, the instant
messaging client gaim is contained in the Debian package of the same name. On
the other hand, it is common for programs to consist of several interrelated
packages. For instance, the gimp image editor consists not only of the gimp
package, but also of the gimp-data package; in addition, several optional add-on
packages (containing esoteric data, documentation, and so on) are also
available. It is also possible for several small, related programs to be
contained in a single package: for instance, the fileutils package contains
several common Unix commands, such as ls, cp, etc.
Some packages require other packages in order to function. In Debian, packages
can depend upon, recommend, suggest, break, or conflict with other packages.
* If a package A depends upon another package B, then B is required for A to
operate properly. For instance, the gimp package depends upon the gimp-data
package in order to ensure that the GIMP graphics editor can access its
critical data files.
* If a package A recommends another package B, then B provides important
additional functionality to A that will be desired in most circumstances. For
instance, the mozilla-browser package recommends the mozilla-psm package,
which adds support for secure data transfers to the Mozilla Web browser. While
mozilla-psm is not strictly required for Mozilla to function, most users will
want Mozilla to support the secure transmission of confidential data (such as
credit card numbers).
* If a package A suggests another package B, then package B provides
functionality that may enhance A, but is not needed in most cases. For
instance, the kmail package suggests the gnupg package, which contains
encryption software that can be used by KMail.
* If a package A conflicts with another package B, then the two packages cannot
be installed at the same time. For instance, fb-music-hi conflicts with fb-
music-low because they provide alternate sets of music for the game Frozen
Bubble.
The job of a package manager is to present an interface which assists the user
in managing the collection of packages installed on his or her system. aptitude
provides such an interface by building on the apt package management system.
What is the apt system?
Being able to install and remove packages is great, but the basic software for
doing this (known as dpkg) does exactly that and nothing more. This is fine if
you download one or two packages by hand, but quickly becomes cumbersome when
you are trying to manage a large number of packages. Furthermore, if your shiny
new package requires software you haven't yet installed, you have to download
the newly required software by hand. And if you later decide to remove the no-
longer-shiny package, these extra packages will linger on your system, consuming
hard drive space, unless you manually remove them.
Obviously, all of this manual labor is a tedious chore, and so most package
management systems come with software which takes care of some or all of it for
you. apt is a common base on which to build these programs: in addition to
aptitude, programs such as synaptic and apt-watch make use of apt.
apt works by keeping a list of the packages that can be downloaded from Debian
on your computer. This list is used to find packages that need to be upgraded
and to install new packages. apt can also solve many dependency problems
automatically: for instance, when you choose to install a package, it will find
any additional required packages and install those as well.
When working with a package manager based on apt, such as aptitude, you will
typically perform three basic tasks: you will update the list of packages that
are available by downloading new lists from the Debian servers, you will select
which packages should be installed, upgraded, or removed, and finally, you will
commit your selections by actually performing the installations, removals, etc.
apt-based package managers read the list of “sources” -- repositories of Debian
packages -- from the file /etc/apt/sources.list. The format and contents of this
file are beyond the scope of this document, but are described in the manual page
sources.list(5).
How can I get aptitude?
In case you are reading this manual but aptitude is not yet installed on your
system, this section explains how to correct this unfortunate situation. Most
people should head straight for the section on binary packages.
Pre-built aptitude packages, or, “what 99% of users should do”
Pre-built, or “binary” packages are the easiest and most common way to install
aptitude. You should only attempt a source install if binary packages are not
available for some reason, or if you have unusual needs that are not met by
binary packages.
If you are using a Debian system, execute the following command as root: apt-get
install aptitude. If you are not using a Debian system, your system provider
might have created a pre-built package of aptitude; if you are not sure, you can
contact them for further suggestions.
Building aptitude from source code
You also can build aptitude from source; however, this is probably not a useful
exercise unless apt is already available on your system. If it is, you can
install aptitude from source with the following steps:
1. Install the following pieces of software:
o A C++ compiler, such as g++.
o The development files for apt, typically available in a package with a
name like libapt-pkg-dev.
o The libsigc++-2.0 library, available in the package libsigc++-2.0-dev or
from http://libsigc.sourceforge.net.
o The cwidget library, available in the package libcwidget-dev or from
http://cwidget.alioth.debian.org.
o The gettext program, which should be included with your Linux
distribution.
o A make tool, such as GNU make.
2. Last but not least, download the most recent aptitude source code,
available from http://packages.debian.org/unstable/admin/aptitude. (scroll
to the bottom of the page and download the “.orig.tar.gz” file)
Once all the required components are available, open a terminal and execute the
command tar zxf aptitude-0.8.10.tar.gz to unpack the source code. Once the
source code is unpacked, type cd aptitude-0.8.10 && ./configure && make to
compile aptitude. If this succeeds, make sure you are the root user (by using
su, for instance), then type make install to install aptitude on your computer.
Once aptitude is successfully installed, typing aptitude at a command prompt
should start the program.
Tracking and participating in aptitude development
Getting the aptitude development source tree
If you want to test the latest bleeding-edge source code for aptitude, you can
download unreleased aptitude source code using Git. Install Git (available from
http://git-scm.com/) and execute the command git clone git://anonscm.debian.org/
aptitude/aptitude.git to retrieve the most recent source code.
IMG.alt.suffix = \[Warning]] Warning
The aptitude Git repository is an active
development tree; it will change as bugs are fixed
and features are added, and there is absolutely no
guarantee that it will even compile, let alone run
properly! Bug reports are welcome, but be aware
that you use development code entirely at your own
risk![1]
Mailing list
The primary mailing list for aptitude development is <aptitude-
devel@lists.alioth.debian.org>. Archives of the list are located at http://
lists.alioth.debian.org/pipermail/aptitude-devel/. To subscribe, visit the Web
page http://lists.alioth.debian.org/mailman/listinfo/aptitude-devel.
Submitting patches
Ideally, patches should be submitted to the aptitude mailing list, <aptitude-
devel@lists.alioth.debian.org>. But if you prefer sending them by private email,
you may email them to <aptitude@packages.debian.org> or <dburrows@debian.org>. A
brief description of the motivation behind your patch, and an explanation of how
it works, are greatly appreciated.
Tracking changes to the aptitude source tree
The aptitude source tree is regularly updated with new features, bugfixes, and
new bugs. Once the source code is available on your computer (see the previous
section), you can cd into it and type git pull to update it with any changes
made to the main repository.
To automatically receive notifications when changes are made to the aptitude
codebase, subscribe to the Atom feed available at http://anonscm.debian.org/
gitweb/?p=aptitude/aptitude.git;a=atom or RSS feed available at http://
anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=rss.
Building aptitude from the development tree
To build aptitude from the Git repository, you must have the programs autoconf
and automake installed. Type sh ./autogen.sh && ./configure to generate the
files needed to compile aptitude, then execute make and make install.
--------------------------------------------------------------------------------
[1]Of course, all free software is used at your own risk, but the risk involved
in using an active development tree is much higher.
Chapter 1. Getting started
Table of Contents
Using aptitude
aptitude basics
Navigating the aptitude package list
Finding packages by name
Managing packages
Updating the package list and installing packages
Using aptitude from the command line
A journey of a thousand miles must begin with a single step.
-- Lao Tsu
aptitude is a sizeable program with many features, and it can be a bit
overwhelming for new users to get acquainted with it. This chapter does not
exhaustively describe the features of aptitude (see Chapter 2, aptitude
reference guide for that), but it does provide a walk-through of the basic and
most commonly used features of the program.
Using aptitude
This section describes how to use the visual interface of aptitude. For
information on using aptitude's command-line interface, see the section called
“Using aptitude from the command line”.
aptitude basics
To run aptitude, open your favorite text terminal, and at the command line,
type:
foobar$ aptitude
Once the cache is loaded (this may take some time on slower machines), the main
aptitude screen should appear:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--- Installed Packages
--- Not Installed Packages
--- Obsolete and Locally Created Packages
--- Virtual Packages
--- Tasks
These packages are currently installed on your computer.
As you can see, the main screen of aptitude is divided into several regions. The
blue line at the top of the terminal is the menu bar, and the blue lines below
it are informational messages describing some important commands. The black
space that follows is the list of all available packages, in which some groups
of packages are listed. The currently selected group (“Installed Packages”) is
highlighted, and its description is shown in the lower black space.
As the top line of the screen suggests, you can access aptitude's menus by
pressing Control+t (also valid: Control+Space and F10); you can also click the
mouse on a menu title if your system supports it. Pressing Control+t will open
the Actions menu:
Actions Undo Package Search Options Views Help
+-------------------------+ u: Update g: Download/Install/Remove Pkgs
|Install/remove packages g|
|Update package list u|
|Forget new packages f|
|Clean package cache |eated Packages
|Clean obsolete files |
|Mark Upgradable U|
|Play Minesweeper |
|Become root |
+-------------------------+
|Quit Q|
+-------------------------+
These packages are currently installed on your computer.
Perform all pending installs and removals
Use the arrow keys and Enter to select menu items (or, if your system supports
it, click on them with a mouse); to close the menu without selecting anything,
press Control+t again. The currently highlighted menu item is explained at the
bottom of the screen. If a menu item can be activated using a keyboard shortcut,
the shortcut is displayed in the menu: for instance, the command “Update package
list” can be activated by pressing u.
At any time, you can press ? to display an on-line reference to the available
keyboard shortcuts.
Navigating the aptitude package list
The list of packages is the primary interface to aptitude. When aptitude starts,
the list is organized into a number of groups, as can be seen in the following
screen shot:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--- Installed Packages
--- Not Installed Packages
--- Obsolete and Locally Created Packages
--- Virtual Packages
--- Tasks
These packages are currently installed on your computer.
IMG.alt.suffix = \[Note]] Note
Empty groups of packages are automatically hidden by
aptitude, so you may see more or less groups than
appear in this screen shot.
In the screen shot above, the first group (“Installed Packages”) is highlighted
to indicate that it is currently selected. You can move the selection up and
down with the arrow keys; note that the description below the package list
changes as you do so. To “expand” a group, press Enter while the group is
selected:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--\ Installed Packages
--- admin - Administrative utilities (install software, manage users, etc)
--- base - The Debian base system
--- devel - Utilities and programs for software development
--- doc - Documentation and specialized programs for viewing documentation
--- editors - Text editors and word processors
--- electronics - Programs for working with circuits and electronics
--- games - Games, toys, and fun programs
--- gnome - The GNOME Desktop System
--- graphics - Utilities to create, view, and edit graphics files
These packages are currently installed on your computer.
As you can see, the “Installed Packages” group has been expanded to reveal its
contents: it contains a number of subgroups, loosely defined by what types of
software they contain. Expanding the “admin” section by selecting it and
pressing Enter, we see:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--\ Installed Packages
--\ admin - Administrative utilities (install software, manage users, etc)
--- main - The main Debian archive
--- base - The Debian base system
--- devel - Utilities and programs for software development
--- doc - Documentation and specialized programs for viewing documentation
--- editors - Text editors and word processors
--- electronics - Programs for working with circuits and electronics
--- games - Games, toys, and fun programs
--- gnome - The GNOME Desktop System
Packages in the 'admin' section allow you to perform administrative tasks such
as installing software, managing users, configuring and monitoring your system,
examining network traffic, and so on.
The “admin” group contains a single subgroup, the “main” Debian archive.
Expanding this group reveals some packages!
IMG.alt.suffix Tip
= \[Tip]]
To save time, you can use the [ key to expand all the subgroups of a group at
once. Selecting “Installed Packages” and pressing [ would have immediately
revealed the packages in the screenshot below.
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--\ Installed Packages
--\ admin - Administrative utilities (install software, manage users, etc)
--\ main - The main Debian archive
i acpid 1.0.3-19 1.0.3-19
i alien 8.44 8.44
i anacron 2.3-9 2.3-9
i apt-show-versions 0.07 0.07
i A apt-utils 0.5.25 0.5.25
i apt-watch 0.3.2-2 0.3.2-2
i aptitude 0.2.14.1-2 0.2.14.1-2
The Debian distribution consists of packages from the 'main' section. Every
package in 'main' is Free Software.
For more information about what Debian considers to be Free Software, see
http://www.debian.org/social_contract#guidelines
In addition to the arrow keys, you can move the selection through the package
list by a page of information at a time using the Page Up and Page Down keys.
IMG.alt.suffix = \[Tip]] Tip
When there is more information in the lower half of the
display than fits into the available space, the a and z
keys can be used to scroll through it.
Finding packages by name
To quickly find a package whose name you know, press / to open a search dialog:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
i frozen-bubble 1.0.0-5 1.0.0-5
i A frozen-bubble-data 1.0.0-5 1.0.0-5
i geekcode 1.7.3-1 1.7.3-1
i gfpoken 0.25-3 0.25-3
i ggz-gnome-client 0.0.7-2 0.0.7-2
i ggz-gtk-client 0.0.7-1 0.0.7-1
i ggz-gtk-game-data 0.0.7-2 0.0.7-2
i +--------------------------------------------------------------------------+
i |Search for: |
i |froz |
Po| [ Ok ] [ Cancel ]|
Fr+--------------------------------------------------------------------------+
attempt to shoot bubbles into groups of the same color to cause them to pop. It
features 100 single-player levels, a two-player mode, music and striking
graphics.
This game is widely rumored to be responsible for delaying the Woody release.
URL: http://www.frozen-bubble.org/
As you can see in the above screen shot, a search for froz finds the frozen-
bubble package. Using aptitude's powerful search language, described in the
section called “Search patterns”, it is possible to find packages based on many
complex criteria.
IMG.alt.suffix = \[Tip]] Tip
You can search backwards in the package list by
pressing \, and you can repeat the last search by
pressing n after closing the search window.
Sometimes it is useful to hide all packages except those which meet some
particular criterion. To do this, press l:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--- Installed Packages
--- Not Installed Packages
--- Obsolete and Locally Created Packages
--- Virtual Packages
--- Tasks
+--------------------------------------------------------------------------+
|Enter the new package tree limit: |
|apti |
| [ Ok ] [ Cancel ]|
Th+--------------------------------------------------------------------------+ a
This dialog works exactly like the search dialog, except that instead of
highlighting the next package that matches what you typed into the dialog box,
it hides all packages which don't match. For instance, typing apti into this
dialog box and pressing Enter will hide all packages except those whose names
contain “apti”:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--\ Installed Packages
--\ admin - Administrative utilities (install software, manage users, etc)
--\ main - The main Debian archive
i aptitude 0.2.14.1-2 0.2.14.1-2
i A synaptic 0.51-1 0.51-1
--\ x11 - The X window system and related software
--\ main - The main Debian archive
i xfree86-driver-synaptics 0.13.3-1 0.13.3-1
--- Not Installed Packages
--- Virtual Packages
These packages are currently installed on your computer.
Managing packages
Now that you can move about the list of packages, it's time to start using
aptitude to install and remove packages. In this section you will learn how to
flag packages for installation, deletion, and upgrade.
IMG.alt.suffix = \[Tip]] Tip
You can only change your system's setup as the root
user. If you want to experiment with aptitude, you can
safely run it as any user other than root without
damaging your system in any way. aptitude will tell you
when you try to do something that only root can do, and
if you want to continue, you must type root's password.
All changes to a package are performed by first highlighting it in the package
list, then pressing a key corresponding to the action which should be performed.
The basic action keys [2] are + to install or upgrade a package, - to remove a
package, and = to prevent a package from being automatically upgraded (this is
known as holding the package). These actions are not performed immediately;
aptitude will simply update the package list to show the change that has been
requested.
For instance, in the screen shot below, the kaffeine-mozilla package was
selected and + was pushed. The package is now highlighted in green and the
letter “i” has appeared to the left of its name, to indicate that it will be
installed; in addition, an estimate of the amount of space that the package will
use is displayed.
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1 Will use 2925kB of disk space DL Size:
1375kB
--\ kde - The KDE Desktop System
--\ main - The main Debian archive
p bibletime-i18n <none> 1.4.1-1
p education-desktop-kde <none> 0.771
p junior-kde <none> 1.4
piA kaffeine +2843kB <none> 0.4.3-1
pi kaffeine-mozilla +81.9kB <none> 0.4.3-1
p karamba <none> 0.17-5
p kde-devel <none> 4:3.1.2
p kde-devel-extras <none> 4:3.1.2
The K Desktop Environment (development files)
A metapackage containing dependencies for the core development suite of KDE
including kdesdk, qt3-designer, and all core KDE -dev packages.
IMG.alt.suffix Tip
= \[Tip]]
At any time, you can use Undo → Undo (Control+u) to “undo” any change to one or more
packages. This is very useful if an action has unforeseen consequences and you want
to “take it back”.
In addition to actions that affect individual packages, another important action
is available: typing U will attempt to upgrade any packages that can be
upgraded. You should use this command on a regular basis to keep your system up-
to-date.
Managing broken packages
Sometimes, changing a package's state will cause dependency relationships to
become unfulfilled; packages with unfulfilled dependencies are said to be
broken. aptitude will warn you when this happens, and explain why it occured.
For instance, here is what happens if I attempt to remove sound-juicer:
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.3.3 #Broken: 1 Will free 48.6MB of disk space
i A nautilus 2.10.1-4 2.10.1-4
i nautilus-cd-burner 2.10.2-1.1 2.10.2-1.1
i A nautilus-data 2.10.1-4 2.10.1-4
i netspeed 0.12.1-1 0.12.1-1
i A oaf 0.6.10-3 0.6.10-3
i pybliographer 1.2.6.2-1 1.2.6.2-1
i rhythmbox 0.8.8-13 0.8.8-13
i shermans-aquarium 3.0.1-1 3.0.1-1
idA sound-juicer -1733kB 2.10.1-3 2.10.1-3
GNOME 2 CD Ripper
sound-juicer will be removed.
The following packages depend on sound-juicer and will be broken by its
removal:
* gnome-desktop-environment depends on sound-juicer
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
As you can see, aptitude displays three indicators that something has gone
wrong: first, the number of broken packages is displayed in the upper blue area;
second, the lower half of the display changes to describe broken packages that
are related to the currently highlighted package; third, a bar appears at the
bottom of the screen with a suggestion on how to solve the problem. To quickly
find broken packages in the package list, you can press b or search for ?broken.
IMG.alt.suffix Note
= \[Note]]
The text [1(1)/...] indicates the progress of aptitude's dependency resolver.
The first number is the solution that you have currently selected, and the
second one is the number of solutions that aptitude has already generated. The
presence of the text “...” indicates that there may be additional solutions
beyond the ones generated; if aptitude knew for certain that it had generated
the only possible solution, this indicator would read [1/1].
To see more information about how aptitude thinks you can solve this problem,
press e. A screen similar to the following will appear:
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
gstreamer0.8-cdparanoia [0.8.10-1 (unstable, now)]
sound-juicer [2.10.1-2 (now)]
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
From here, you can see more solutions by pressing . or return to solutions that
you previously examined by pressing ,. To apply the current solution and return
to the package list, press !. For instance, pressing . while the above screen is
displayed results in the following solution being presented:
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
sound-juicer [2.10.1-3 (unstable, now)]
--\ Downgrade the following packages:
gstreamer0.8-cdparanoia [0.8.11-1 unstable, now -> 0.8.8-3 testing]
[2(2)/...] Suggest 1 keep,1 downgrade
e: Examine !: Apply .: Next ,: Previous
In addition to the basic solution navigation commands, you can press r to
“reject” actions of which you disapprove. For instance, the first solution will
cancel the removal of sound-juicer -- the very action we were trying to perform!
By pressing r on the item corresponding to this action, we can tell aptitude
that it should not cancel the removal of sound-juicer in this way.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
gstreamer0.8-cdparanoia [0.8.11-1 (unstable, now)]
R sound-juicer [2.10.1-3 (unstable, now)]
GNOME 2 CD Ripper
gnome-desktop-environment depends upon sound-juicer
--\ The following actions will resolve this dependency:
-> Remove gnome-desktop-environment [1:2.10.2.3 (unstable, testing, now)]
R -> Cancel the removal of sound-juicer
-> Downgrade sound-juicer [2.10.1-3 (unstable, now) -> 0.6.1-2 (testing)]
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
As you can see, the list item corresponding to keeping sound-juicer at its
current version has turned red and been marked with an “R”, indicating that it
has been rejected. Solutions that you generate in the future (that is, any
solution that you have not yet viewed) will not include this action, although
solutions that were already generated and contain this action will be available.
IMG.alt.suffix = \[Note]] Note
In the above screen image, a description of sound-
juicer is displayed in the middle of the screen; below
it, you can see the dependency that caused sound-
juicer to be kept at its current version, along with
all the ways to resolve this dependency that aptitude
knows about.
For instance, if this rejection is imposed immediately after attempting to
remove sound-juicer, pressing . retrieves the following solution, skipping the
solution that cancels the installation of sound-juicer and downgrades
gstreamer0.8-cdparanoia.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Remove the following packages:
gnome-desktop-environment [1:2.10.2.3 (unstable, testing, now)]
[2(2)/...] Suggest 1 removal
e: Examine !: Apply .: Next ,: Previous
Rejections are only applied to newly generated solutions: that is, solutions
that are generated when you press . while viewing the last generated solution.
Previously generated solutions can still contain rejections. You can cancel a
rejection at any time by once again selecting the rejected action and pressing
r; this will permit solutions containing the action to be generated again,
including any solutions that were previously “skipped”.
The opposite of rejecting an action is approving it. To approve an action, just
select it and press a; this forces the problem resolver to choose the action
whenever possible[3]. Approved actions will turn green and will be marked with
“A”, as in the following screenshot:
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Remove the following packages:
A gnome-desktop-environment [1:2.10.2.3 (unstable, testing, now)]
[2(2)/...] Suggest 1 removal
e: Examine !: Apply .: Next ,: Previous
IMG.alt.suffix = \[Important]] Important
If you do not resolve any broken dependencies,
aptitude will automatically implement its current
suggestion when you commit your selections by
pressing g. However, it is hard to automatically
solve dependency problems, and you may not be
happy with the results, so it is generally better
to look at what aptitude plans to do before
committing your selections.
Updating the package list and installing packages
At this point, you know enough about aptitude to actually make modifications to
your system.
You should periodically update your list of available packages from the Debian
servers, to keep track of new packages and new versions of packages. To do this,
press u. At any time during the download, you can press q to abort it.
Once you have fresh lists of packages, you can choose the packages to upgrade,
install, or remove as described in the previous section. To review the actions
you have requested, press g once. When installing the kaffeine-mozilla package
(from the previous example), the following screen appears:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1 Will use 2925kB of disk space DL Size:
1375kB
--\ Packages being automatically installed to satisfy dependencies
piA kaffeine +2843kB <none> 0.4.3-1
--\ Packages to be installed
pi kaffeine-mozilla +81.9kB <none> 0.4.3-1
These packages are being installed because they are required by another package
you have chosen for installation.
If you select a package, an explanation of its current state will appear in this
space.
As you can see, aptitude automatically decided to install kaffeine for me
because kaffeine-mozilla requires it. At this point, I have the choice of either
continuing with the installation by pressing g, or aborting it by pressing q.
Using aptitude from the command line
In addition to its “visual” interface described in the previous section,
aptitude can be used to manage packages directly from the command-line in the
same way that you would use apt-get. This section covers the most common
aptitude command-line actions; for more information, see the aptitude command-
line reference.
In general, a command-line invocation of aptitude will look like this:
aptitude action [arguments...]
action tells aptitude what action it is to take; the remaining arguments are
used in an option-specific fashion. Typically they will consist of package names
and command-line switches[4].
The most important actions are:
aptitude update
This command updates the package lists, as if you had entered the visual
interface and pressed u.
aptitude safe-upgrade
This command will upgrade as many packages as it can upgrade without
removing existing packages.
It is sometimes necessary to remove one package in order to upgrade
another; this command is not able to upgrade packages in such situations.
Use the full-upgrade command to upgrade those packages as well.
aptitude full-upgrade
Like safe-upgrade, this command will attempt to upgrade packages, but it
is more aggressive about solving dependency problems: it will install and
remove packages until all dependencies are satisfied. Because of the
nature of this command, it is possible that it will do undesirable things,
and so you should be careful when using it.
IMG.alt.suffix = \[Note]] Note
For historical reasons, this command was
originally named dist-upgrade, and that name is
still recognized by aptitude.
aptitude [ install | remove | purge ] pkg1 [pkg2...]
These commands install, remove, or purge[5] the specified packages.
“Installing” a package which is already installed but can be upgraded will
cause it to be upgraded.
aptitude search pattern1 [pattern2...]
This command searches for packages whose name contains any of the given
patterns, printing the result to the terminal. In addition to just being a
string of text, each pattern can be a search pattern as described in the
section called “Search patterns”. [6] For instance, “aptitude search gnome
kde” will list all packages whose name contains either “gnome” or “kde”.
aptitude show pkg1 [pkg2...]
Prints information about each pkg to the terminal.
The commands that install, upgrade, and remove packages all accept the parameter
-s, which stands for “simulate”. When -s is passed on the command line, the
program performs all the actions it would normally perform, but does not
actually download or install/remove any files.
aptitude will sometimes present a prompt like this:
The following NEW packages will be automatically installed:
space-orbit-common
The following NEW packages will be installed:
space-orbit space-orbit-common
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 3200kB of archives. After unpacking 8413kB will be used.
Do you want to continue? [Y/n/?]
In addition to the obvious options of “Yes” and “No”, a number of commands are
available which can be used to change the information displayed at the prompt,
or to specify further actions. For instance, typing s will display or hide
information about how much space each package will use:
Do you want to continue? [Y/n/?] s
Size changes will be shown.
The following NEW packages will be automatically installed:
space-orbit-common <+8020kB>
The following NEW packages will be installed:
space-orbit <+393kB> space-orbit-common <+8020kB>
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 3200kB of archives. After unpacking 8413kB will be used.
Do you want to continue? [Y/n/?]
Similarly, typing d will display information about automatically installed or
removed packages:
The following NEW packages will be automatically installed:
space-orbit-common (D: space-orbit)
The following NEW packages will be installed:
space-orbit space-orbit-common
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 3200kB of archives. After unpacking 8413kB will be used.
This shows that space-orbit-common is being installed because space-orbit
depends on it. You can see the entire list of possible entries by entering ? at
the prompt.
If your request violates dependencies in a way that cannot be trivially
resolved, aptitude will ask you what to do:
The following packages are BROKEN:
libsdl1.2debian
The following packages will be REMOVED:
libsdl1.2debian-alsa
.
.
.
The following actions will resolve these dependencies:
Install the following packages:
libsdl1.2debian-all [1.2.12-1 (unstable)]
Score is 41
Accept this solution? [Y/n/q/?]
Typing y (or simply pressing enter) will accept the proposed solution. Typing n
will display the “next best” solution:
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Install the following packages:
libsdl1.2debian-esd [1.2.12-1 (unstable)]
Score is 19
Accept this solution? [Y/n/q/?]
As with the main command-line prompt, you can perform a number of additional
actions, including manually altering the states of packages, from the dependency
resolution prompt. Type ? to see a complete list.
Typing q will abort the automatic resolver and allow you to resolve the
dependencies manually:
Accept this solution? [Y/n/q/?] q
aptitude failed to find a solution to these dependencies. You can solve them
yourself by hand or type 'n' to quit.
The following packages have unmet dependencies:
libsdl1.2debian: Depends: libsdl1.2debian-alsa (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-all (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-esd (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-arts (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-oss (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-nas (= 1.2.12-1) but it is not
installable or
libsdl1.2debian-pulseaudio (= 1.2.12-1) but it is
not installable
Resolve these dependencies by hand? [N/+/-/_/:/?]
You can use any of the package manipulation commands to resolve the broken
dependencies (type ? for a full list of the available commands). Type n or press
enter to quit aptitude:
Resolve these dependencies by hand? [N/+/-/_/:/?] n
Abort.
For complete documentation of the command-line features of aptitude, see
Command-line reference.
--------------------------------------------------------------------------------
[2] You can also change packages using the Package menu; see the section called
“The Package menu” for details.
[3] Approving an action is slightly different from requiring all solutions to
contain the action; what it means is that given a choice between an approved
action and a non-approved action, the resolver will always pick the approved
action. If there are several possible approved actions, all of them will be
candidates to be placed into the solution.
[4]A “switch” is a letter preceded by a hyphen: for instance, “-a”, “-v”, etc.
[5]Purging a package removes the package, as well as all its configuration
files.
[6] In fact, the same is true of the commands that take packages as arguments,
such as install or show.
Chapter 2. aptitude reference guide
Table of Contents
The aptitude terminal user interface
Using the menus
Menu commands
Working with multiple views
Becoming root
Managing packages
Managing the package list
Accessing package information
Modifying package states
Downloading, installing, and removing packages
Understanding and managing package trust
Managing automatically installed packages
Resolving package dependencies
Dependency resolution in aptitude
Immediate dependency resolution
Resolving Dependencies Interactively
Costs in the interactive dependency resolver
Configuring the interactive dependency resolver
Search patterns
Searching for strings
Shorthand for search terms
Searches and versions
Explicit search targets
Search term reference
Customizing aptitude
Customizing the package list
Customizing keybindings
Customizing text colors and styles
Customizing the display layout
Configuration file reference
Themes
Playing Minesweeper
The White Rabbit put on his spectacles. 'Where shall I begin, please your
Majesty?' he asked.
'Begin at the beginning,' the King said gravely, 'and go on till you come
to the end: then stop.'
-- Lewis Carrol, Alice in Wonderland
aptitude is a large program with many features, and it is sometimes difficult to
remember how to do something, or even to remember whether that something is even
possible. Indeed, many feature requests received by the author describe features
which are already present but are difficult to find.[7]
In an attempt to combat this obscurity, this reference guide describes every
feature and configuration parameter of aptitude. For a more gentle guide to the
important features of aptitude, see Chapter 1, Getting started.
IMG.alt.suffix Note
= \[Note]]
aptitude's behavior and appearance can be configured in a number of
ways. This manual describes how the program works with the default
settings; descriptions of how various settings affect behavior are
given in the section called “Customizing aptitude”.
The aptitude terminal user interface
This section describes the parts of the terminal-based user interface of
aptitude that do not deal with managing packages.
Using the menus
The menu bar at the top of the screen lists the most important commands in
aptitude. To activate the menu bar, press Control+t (also valid: Control+Space
and F10); you can then navigate it using the arrow keys and select a menu item
using Enter.
Some menu items also have “hotkeys”: letters or numbers that can be used to
select the item while the menu is active. These hotkeys are displayed in a
brighter shade of white than the rest of the menu.
In addition, some menu items have “shortcuts”: keystrokes that perform the same
action as the menu item while the menu is not active. These keystrokes are
listed on the right-hand side of the menu.
In the remainder of the manual, menu commands will be written like this: Menu →
Item (key). This indicates that you should choose Item from the Menu menu, and
that key is the shortcut for this command.
Menu commands
The Actions menu
Figure 2.1. Commands available in the Actions menu
______________________________________________________________________________________________________________________
|Command |Description |
|_______________________________________|______________________________________________________________________________|
| |If an installation preview is not visible, display one; otherwise, perform an |
|Actions → Install/remove packages (g)|install run as described in the section called “Downloading, installing, and|
| |removing packages”. |
|_______________________________________|______________________________________________________________________________|
|Actions → Update package list (u) |Bring the package list up-to-date. |
|_______________________________________|______________________________________________________________________________|
|Actions → Mark Upgradable (U) |Flag all upgradable packages, except those which are held or forbidden from |
| |upgrading, for upgrade. |
|_______________________________________|______________________________________________________________________________|
|Actions → Forget new packages (f) |Discard all information about what packages are “new” (empty the “New |
| |Packages” tree). |
|_______________________________________|______________________________________________________________________________|
| |Cancel all pending actions from this session (including installations, |
|Actions → Cancel pending actions |removals, upgrades, holds, marking as automatically installed...). This is |
| |roughly equivalent to restart the program. |
|_______________________________________|______________________________________________________________________________|
|Actions → Clean package cache |Delete all the compressed packages that were downloaded by aptitude [a]. |
|_______________________________________|______________________________________________________________________________|
| |Delete any compressed packages that were downloaded by aptitude [a] and are no|
|Actions → Clean obsolete files |longer available. These are presumed to be packages which are obsolete, and |
| |can be deleted to save disk space without requiring an otherwise unnecessary |
| |download. |
|_______________________________________|______________________________________________________________________________|
|Actions → Play Minesweeper |Play a game of Minesweeper, as described in the section called “Playing |
| |Minesweeper”. |
|_______________________________________|______________________________________________________________________________|
|Actions → Become root |Continue working as the root user; see the section called “Becoming root”.|
|_______________________________________|______________________________________________________________________________|
|Actions → Quit (Q) |Quit aptitude, saving any changes to package states. |
|_______________________________________|______________________________________________________________________________|
|[a] Or any other apt utility. |
|______________________________________________________________________________________________________________________|
The Undo menu
Figure 2.2. Commands available in the Undo menu
______________________________________________________________________________
|Command |Description |
|_________________________|____________________________________________________|
| |Cancel the effect of the last change to a package's |
|Undo → Undo (Control+u)|state, up to the last time aptitude was started, the|
| |package list was updated, or an install run was |
| |performed. |
|_________________________|____________________________________________________|
The Package menu
Figure 2.3. Commands available in the Package menu
__________________________________________________________________________________________________________________
|Command |Description |
|_________________________________|________________________________________________________________________________|
|Package → Install (+) |Flag the currently selected package for installation. |
|_________________________________|________________________________________________________________________________|
|Package → Reinstall (L) |Flag the currently selected package for reinstallation. |
|_________________________________|________________________________________________________________________________|
|Package → Remove (-) |Flag the currently selected package for removal. |
|_________________________________|________________________________________________________________________________|
|Package → Purge (_) |Flag the currently selected package to be purged. |
|_________________________________|________________________________________________________________________________|
|Package → Keep (:) |Cancel any pending installation, upgrade, or removal of the currently selected |
| |package, and remove any hold that was set on the package. |
|_________________________________|________________________________________________________________________________|
|Package → Hold (=) |Hold the currently selected package back. |
|_________________________________|________________________________________________________________________________|
| |Mark the currently selected package as an “automatically installed” package.|For
|Package → Mark Auto (M) |more information on manually and automatically installed packages, see the |
| |section called “Managing automatically installed packages”. |
|_________________________________|________________________________________________________________________________|
| |Mark the currently selected package as a “manually installed” package. For m|re
|Package → Mark Manual (m) |information on manually and automatically installed packages, see the section |
| |called “Managing automatically installed packages”. |
|_________________________________|________________________________________________________________________________|
| |If a package that can be upgraded is selected, forbid it from being upgraded to |
|Package → Forbid Version (F) |the currently available version. If a version of a package is selected, forbid |
| |the package from being upgraded to that version. |
|_________________________________|________________________________________________________________________________|
| |Display a screen containing information about the currently selected package, |
|Package → Information (enter) |such as the packages it depends upon, the packages which depend upon it, and its|
| |available versions. |
|_________________________________|________________________________________________________________________________|
| |When browsing the package list, cycles through the information that can be |
| |displayed in the information area (the lower half of the display). The |
|Package → Cycle Information (i)|information area can display the long description of the selected package (its |
| |default behavior), a summary of the dependencies related to the package, or an |
| |analysis of which other packages require or suggest the selected package. |
|_________________________________|________________________________________________________________________________|
|package → Changelog (C) |Display the currently selected package's Debian changelog. To see the changelog |
| |of a particular version, select that version and execute this command. |
|_________________________________|________________________________________________________________________________|
The Resolver menu
Figure 2.4. Commands available in the Resolver menu
______________________________________________________________________________________________________________
|Command |Description |
|__________________________________|___________________________________________________________________________|
|Resolver → Examine Solution (e) |Display a detailed description of the problem resolver's current suggestion|
| |(see the section called “Resolving Dependencies Interactively”). |
|__________________________________|___________________________________________________________________________|
|Resolver → Apply Solution (!) |Carry out the actions that the problem resolver is currently suggesting. |
|__________________________________|___________________________________________________________________________|
|Resolver → Next Solution (.) |Select the problem resolver's next suggestion. |
|__________________________________|___________________________________________________________________________|
|Resolver → Previous Solution (,)|Select the problem resolver's previous suggestion. |
|__________________________________|___________________________________________________________________________|
|Resolver → First Solution (<) |Select the problem resolver's first suggestion. |
|__________________________________|___________________________________________________________________________|
|Resolver → Last Solution (>) |Select the problem resolver's most recently generated solution (see the |
| |section called “Resolving Dependencies Interactively”). |
|__________________________________|___________________________________________________________________________|
| |When examining a solution, toggle whether the currently selected action is |
|Resolver → Toggle Rejected (r) |rejected and move to the next action (see the section called “Resolving |
| |Dependencies Interactively”). If the action is currently approved, its |
| |approval will be cancelled. |
|__________________________________|___________________________________________________________________________|
| |When examining a solution, toggle whether the currently selected action is |
|Resolver → Toggle Approved (a) |approved and move to the next action (see the section called “Resolving |
| |Dependencies Interactively”). If the action is currently rejected, its |
| |rejection will be cancelled. |
|__________________________________|___________________________________________________________________________|
| |When examining a solution, view detailed information about the package |
|Resolver → View Target (Enter) |which is affected by the currently selected action (see the section called |
| |“Resolving Dependencies Interactively”). |
|__________________________________|___________________________________________________________________________|
| |Reject (as if with Resolver → Toggle Rejected (r)) all actions that would|
| |break a hold on a package or install a forbidden version. These actions are|
|Resolver → Reject Breaking Holds|rejected by default unless Aptitude::ProblemResolver::Allow-Break-Holds is |
| |set to true, but this menu item allows you to reject them manually at any |
| |time. |
|__________________________________|___________________________________________________________________________|
The Search menu
Figure 2.5. Commands available in the Search menu
__________________________________________________________________________________________________________
|Command |Description |
|___________________________________|______________________________________________________________________|
|Search → Find (/) |Find the next package in the package list that matches a search |
| |pattern (see the section called “Search patterns”). |
|___________________________________|______________________________________________________________________|
|Search → Find Backwards (\) |Find the previous package in the package list that matches a search |
| |pattern (see the section called “Search patterns”). |
|___________________________________|______________________________________________________________________|
|Search → Find Again (n) |Repeat the last Find command. |
|___________________________________|______________________________________________________________________|
| |Repeat the last Find command, but in the opposite direction. If the |
|Search → Find Again Backwards (N)|last Find command was Find Backwards, this will perform a forwards |
| |search, and vice versa. |
|___________________________________|______________________________________________________________________|
|Search → Limit Display (l) |Filter the current package list by removing any packages which do not |
| |match a search pattern (see the section called “Search patterns”).|
|___________________________________|______________________________________________________________________|
|Search → Un-Limit Display |Un-filter the current package list (all packages will be shown). |
|___________________________________|______________________________________________________________________|
|Search → Find Broken (b) |Find the next broken package. This is equivalent to searching for |
| |?broken. |
|___________________________________|______________________________________________________________________|
The Options menu
Figure 2.6. Commands available in the Options menu
______________________________________________________________________________
|Command |Description |
|__________________________|___________________________________________________|
| |Open a new top-level view in which you can modify |
| |aptitude's settings. Configuration options are |
| |displayed in a tree similar to the tree of |
|Options → Preferences |packages; to enable or disable an option, select it|
| |and press Space or Enter. Configuration options are|
| |saved to ~/.aptitude/config immediately upon being |
| |selected. |
|__________________________|___________________________________________________|
|Options → Revert options|Reset all options to their default values. |
|__________________________|___________________________________________________|
The Views menu
IMG.alt.suffix Note
= \[Note]]
For an overview of how views work, see the section called “Working with
multiple views”.
Figure 2.7. Commands available in the Views menu
______________________________________________________________________________
|Command |Description |
|_______________________________|______________________________________________|
|Views → Next (F6) |Change to the next active view. |
|_______________________________|______________________________________________|
|Views → Prev (F7) |Change to the previous active view. |
|_______________________________|______________________________________________|
|Views → Close (q) |Close the current view. |
|_______________________________|______________________________________________|
|Views → New Package View |Create a new view of the package list. |
|_______________________________|______________________________________________|
| |Create a view that displays packages which are|
|Views → Audit Recommendations|not installed, and which a package installed |
| |on your system Recommends. |
|_______________________________|______________________________________________|
|Views → New Flat Package List|Create a new view of the package list in which|
| |packages are not categorized. |
|_______________________________|______________________________________________|
| |Create a new view of the package list in which|
|Views → New Debtags Browser |packages are categorized according to their |
| |debtags entries. |
|_______________________________|______________________________________________|
| |A number of additional menu items appear; |
|Additional items |these correspond to the currently active |
| |views. To switch directly to a view, select it|
| |from the menu. |
|_______________________________|______________________________________________|
The Help menu
Figure 2.8. Commands available in the Help menu
______________________________________________________________________________
|Command |Description |
|______________________|_______________________________________________________|
|Help → About |Display some copyright information. |
|______________________|_______________________________________________________|
|Help → Help (?) |Display the on-line help page. |
|______________________|_______________________________________________________|
|Help → User's Manual|Display the User's Manual (this document). |
|______________________|_______________________________________________________|
|Help → FAQ |Display the aptitude FAQ. |
|______________________|_______________________________________________________|
|Help → ChangeLog |Display a history of the major changes made to |
| |aptitude. |
|______________________|_______________________________________________________|
|Help → License |Display the terms under which you may copy, modify, and|
| |distribute aptitude. |
|______________________|_______________________________________________________|
Working with multiple views
aptitude allows you to work with several “views” at once. A “view” (sometimes
called a “screen”) is simply something that can appear in the area of the screen
below the menu bar. The most common view is the package list, but download views
are also common.
When several views are open at once, a bar listing all the active views will
appear at the top of the screen. For instance, if I examine apt by pressing
Enter, then examine libc6, the screen will look something like this:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages apt info libc6 info
aptitude 0.3.1
i A --\ libc6 2.3.2.ds1- 2.3.2.ds1-
Description: GNU C Library: Shared libraries and Timezone data
Contains the standard libraries that are used by nearly all programs on the
system. This package includes shared versions of the standard C library and
the standard math library, as well as many others. Timezone data is also
included.
Priority: required
Section: base
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Compressed size: 4901k
Uncompressed size: 15.9M
Source Package: glibc
--\ Depends
--- libdb1-compat
--\ Suggests
--- locales
--- glibc-doc
--\ Conflicts
GNU C Library: Shared libraries and Timezone data
You can close the current view using Views → Close (q). To switch to the next or
previous view, use Views → Next (F6) and Views → Prev (F7), or click on the
view's name at the top of the screen; you can also find a list of all active
views in the Views menu.
As shown above, some commands (for instance, viewing information about a
package) will create new views automatically; you can also explicitly create a
new view using Views → New Package View.
Becoming root
Some actions, such as updating the package lists, can only be performed as root.
If you are not root and you try to update the package lists, aptitude will ask
if you want to become root:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--- Installed Packages
--- Not Installed Packages
--- Obsolete and Locally Created Packages
--- Virtual Packages
--- Tasks
+-------------------------------------------------------------------------+
|Updating the package lists requires administrative privileges, which |
|you currently do not have. Would you like to change to the root account?|
| |
| [ Become root ] [ Don't become root ] |
Th+-------------------------------------------------------------------------+
If you select “Become root”, aptitude will prompt you for root's password; when
you have correctly entered it, aptitude will perform the action that required
root privileges. You will still be root after the action completes.
You can switch to the root account at any time using the command Actions →
Become root. Any changes you have made to package states will be preserved (but
will not be saved until you quit aptitude).
By default, aptitude will use the command su to gain root privileges. If you
would like it to use some other command (such as sudo), set the configuration
option Aptitude::Get-Root-Command.
Managing packages
This section describes how to manipulate the list of packages, how to install
new packages on your system, and how to remove old packages.
Managing the package list
To keep the list of packages up-to-date, it is recommended that you periodically
update it. You can do this using the Actions → Update package list (u) command.
Accessing package information
Information about packages is presented in several locations in aptitude: the
package list gives a quick overview of the state of each package, and additional
views providing detailed information about a package are also available.
The package list
The package list displays an “at-a-glance” synopsis of a package's state. For
instance, the package webmin might have the following synopsis:
piAU webmin +5837kB <none> 1.160-2
The four characters on the left-hand side of the synopsis show that the package
is not installed (“p”), that it is going to be installed (“i”), that it was
automatically chosen to be installed (“A”), and that it is untrusted (“U”). On
the right-hand side of the synopsis, the current version and the most recent
available version are displayed, along with an indication of how much space will
be used by the upgrade.
IMG.alt.suffix Tip
= \[Tip]]
You can customize how package synopses are displayed; see the section
called “Customizing how packages are displayed” for details.
The four status flags on the left-hand side of the screen give the basic
information about a package's state. The first character is the package's
current state. The second character is the action which will be taken on the
package. The third character indicates whether the package was automatically
installed (see the section called “Managing automatically installed packages”),
and the fourth character indicates whether the package is trusted (see the
section called “Understanding and managing package trust”).
The possible values of the “current state” flag are given in Figure 2.9, “Values
of the “current state” flag” and the possible values of the “action” flag are
given in Figure 2.10, “Values of the “action” flag”.
Figure 2.9. Values of the “current state” flag
i - the package is installed and all its dependencies are satisfied.
c - the package was removed, but its configuration files are still present.
p - the package and all its configuration files were removed, or the package was
never installed.
v - the package is virtual.
B - the package has broken dependencies.
u - the package has been unpacked but not configured.
C - half-configured: the package's configuration was interrupted.
H - half-installed: the package's installation was interrupted.
W - triggers-awaited: the package awaits trigger processing by another package.
T - triggers-pending: The package has had an update triggered due to changes in
another package.
Figure 2.10. Values of the “action” flag
i - the package will be installed.
u - the package will be upgraded.
w - the package will be downgraded.
d - the package will be deleted: it will be removed, but its configuration files
will remain on the system.
p - the package will be purged: it and its configuration files will be removed.
h - the package will be held back: it will be kept at its current version, even
if a newer version becomes available, until the hold is cancelled.
F - An upgrade of the package has been forbidden.
r - the package will be reinstalled.
the package is “broken”: some of its dependencies will not be satisfied.
B - aptitude will not allow you to install, remove, or upgrade anything while
you have broken packages.
In addition, aptitude will use colors to indicate package state if your terminal
supports it. State distinctions are mainly displayed using the background color:
Black
The package cannot be upgraded (or is not going to be installed), and it
has no dependency problems. If the package is installed, its name will be
highlighted.
Green
The package is going to be installed.
Blue
The package is currently installed, and it will be upgraded.
Brown
The package is currently installed, and it will be downgraded.
Magenta
The package is currently installed, but it will be removed.
White
The package is currently installed, and it is “held” at its current
version: automatic upgrades will ignore it.
Red
This package is broken: some of its dependencies will not be satisfied.
Finally, the lower half of the screen displays the long description. aptitude
will attempt to detect whether the package is involved in a dependency problem;
if so, information regarding the dependency problem will be displayed here. To
cycle between dependency information and the package description, press i.
Detailed package information
Pressing Enter while a package is highlighted will display the package
information screen:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
i A --\ apt 0.5.25 0.5.25
Description: Advanced front-end for dpkg
This is Debian's next generation front-end for the dpkg package manager. It
provides the apt-get utility and APT dselect method that provides a simpler,
safer way to install and upgrade packages.
APT features complete installation ordering, multiple source capability and
several other unique features, see the Users Guide in apt-doc.
Essential: yes
Priority: important
Section: base
Maintainer: APT Development Team <deity@lists.debian.org>
Compressed size: 970k
Uncompressed size: 2961k
Source Package: apt
--\ Depends
--- libc6 (>= 2.3.2.ds1-4)
--- libgcc1 (>= 1:3.3.3-1)
--- libstdc++5 (>= 1:3.3.3-1)
--\ Suggests
--- aptitude | synaptic | gnome-apt | wajig
--- dpkg-dev
--\ apt-doc (UNSATISFIED)
p 0.6.25
p 0.5.25
--\ Replaces
--- libapt-pkg-doc (< 0.3.7)
--- libapt-pkg-dev (< 0.3.7)
--- Package names provided by apt
--- Packages which depend on apt
--\ Versions
p A 0.6.25
i A 0.5.25
This display can be navigated in a manner similar to the package list: for
instance, in the screenshot above, I expanded the dependency on apt-doc,
revealing the available versions of apt-doc which will fulfill the dependency.
These versions can be manipulated in the same way that packages can: for
instance, to install version 0.5.25 of apt-doc, you would highlight it and press
+.
IMG.alt.suffix = \[Tip]] Tip
To quickly satisfy a dependency, select the dependency
and press +; aptitude will attempt to automatically
satisfy it.
In addition to the dependencies of a package, you can view the package names
that it Provides, the packages which depend upon it, and the available versions
of the package (including any other packages that Provide it).
As usual, you can dismiss this screen and return to the main view by pressing q.
For convenience, a few other information screens (which only display some
commonly-used information, hiding the rest) are available: press v to view the
versions of a package, d to view the dependencies of a package, and r to view
the “reverse dependencies” of a package (packages which depend upon it).
Modifying package states
The following commands are available to modify the states of packages. Commands
take effect the next time you perform an install run; until you do, all of these
commands can be reversed using Undo → Undo (Control+u).
To apply a command to a package, simply select the package in a package list and
issue the command. These commands can also be applied to groups of packages by
selecting the group header (for instance, “Upgradable Packages”) and issuing the
command.
_____________________________________________________________________________________________________________________________________
|Command |Description |
|______________________________________________________|______________________________________________________________________________|
| |Flag the current package for installation. |
| | |
|Install: Package → Install (+) |If the package is not installed, it will be installed. If it is already |
| |installed, it will be upgraded if possible and any sticky upgrade prevention |
| |that is in effect (eg, Hold) will be cancelled. |
|______________________________________________________|______________________________________________________________________________|
| |Flag the currently selected package for removal. |
|Remove: Package → Remove (-) | |
| |If the package is installed, it will be removed. |
|______________________________________________________|______________________________________________________________________________|
| |Flag the current package to be purged. |
| | |
|Purge: Package → Purge (_) |If the package is installed, it will be removed. Furthermore, even if it is |
| |removed, any remaining files (such as configuration files) related to the |
| |package will be removed from the system. |
|______________________________________________________|______________________________________________________________________________|
| |Flag the current package to be kept at its current version. |
| | |
|Keep: Package → Keep (:) |Any action that was to be performed on the package -- installation, removal, |
| |or upgrade -- is cancelled, and any persistent hold that was set on the |
| |package is removed. |
|______________________________________________________|______________________________________________________________________________|
| |Set a persistent hold on the package. |
| | |
|Hold: Package → Hold (=) |As with Keep, any action that was to be performed on the package is cancelled.|
| |In addition, the package will not be automatically upgraded [a] until the hold|
| |is removed. You may cancel a hold by issuing the Install command. |
|______________________________________________________|______________________________________________________________________________|
| |The package will not be automatically upgraded[a] to the version it would |
| |currently be upgraded to. If it was going to be upgraded, the upgrade will be |
| |cancelled. |
| | |
|Package → Forbid Version (F) |If you issue this command on a particular version of a package, the package |
| |will not be upgraded to the selected version. Note that only one version can |
| |be forbidden at once. |
| | |
| |This functionality is largely provided as a convenience for users of the |
| |“unstable” distribution, so they can avoid known-bad versions of packages.|
|______________________________________________________|______________________________________________________________________________|
| |Flag the current package for reinstallation. |
| | |
|Reinstall: Package → Reinstall (L) |Note that the reinstallation will not be saved when you quit aptitude or |
| |perform an install run, for technical reasons (essentially, the underlying |
| |software layers (dpkg and apt) do not provide any way to find out whether a |
| |reinstallation was successful or not). |
|______________________________________________________|______________________________________________________________________________|
| |Sets whether the package is treated as having been automatically installed; |
|Package → Mark Auto (M), Package → Mark Manual (m)|automatically installed packages will be removed when no other package |
| |requires them. For more information, see the section called “Managing |
| |automatically installed packages”. |
|______________________________________________________|______________________________________________________________________________|
|[a] That is, it will be unaffected by Actions → Mark Upgradable (U) or the full-upgrade or safe-upgrade command-line actions. |
|_____________________________________________________________________________________________________________________________________|
In addition to these commands that affect the selected package, there are two
commands that affect large numbers of packages at once regardless of what is
selected. Actions → Forget new packages (f) clears the “new” status of all
packages in the package list, and Actions → Mark Upgradable (U) flags every
package which can be upgraded for upgrade, except for packages that are held
back or would be upgraded to a forbidden version.
IMG.alt.suffix = \[Note]] Note
All changes to package states are saved when you quit
aptitude, update the package list, or perform an
install run. If you do not wish to save your changes,
you can always abort aptitude by pressing Ctrl-C.
Downloading, installing, and removing packages
Changing package states as described in the previous section does not actually
affect what is installed on your system. Thus, you can adjust the state of
packages without affecting your system until you are happy with what you see;
once you are, you can “commit” the changes by actually installing and removing
packages.[8]
To commit your changes, use the Actions → Install/remove packages (g) command.
Selecting this command will display a preview screen describing the changes that
will be performed. This screen is just a package list, and you can manipulate
the packages (for instance, cancelling unwanted removals) in the same way that
you could in the main list.
When you are done, use Views → Close (q) to cancel the installation, or use
Actions → Install/remove packages (g) to proceed. aptitude will download any
files that need to be downloaded, then prompt you to continue with the
installation. When you select “Continue”, the installations and removals will
commence.
Packages that are downloaded by aptitude are placed in a cache directory
(typically /var/cache/apt/archives). Normally, they are just left in this
directory ad infinitum. To delete all the files in this directory, use Actions →
Clean package cache; to delete only files which cannot be downloaded again (ie,
obsolete packages), use Actions → Clean obsolete files.
Understanding and managing package trust
apt's ability to access multiple package sources leads to a potential security
vulnerability. Suppose you add an archive of packages published by Joe Random
Hacker to your sources.list file in order to install Joe's gargleblast package.
It is possible, however, that -- unbeknownst to you -- Joe's archive also
contains his own “customized” versions of packages such as libc6 and
ssh...versions that steal your private information or open backdoors on your
system! If these packages have higher version numbers than the legitimate Debian
packages, apt will blithely install them on your system during your next
upgrade, allowing Joe to do his dirty work undetected. Joe could also break into
your mirror of the Debian archives and replace the legitimate software with his
doctored version.
Luckily, newer versions of apt and aptitude, such as the version documented in
this manual, have built-in safeguards to help defeat this type of attack. apt
uses strong security mechanisms based on the popular GPG encryption software to
verify that the packages being distributed from the official Debian mirrors are
the same packages that were uploaded by the Debian developers. aptitude will
then warn you if you attempt to install a package from a non-Debian source, or
if you attempt to upgrade a package that was installed from a Debian source to a
version that came from a non-Debian source.
IMG.alt.suffix = \[Warning]] Warning
The security mechanisms in apt provide a near-
perfect guarantee that the contents of your archive
mirror are identical to the contents of the master
Debian archive. However, they are not a panacea:
for instance, there are many ways that a tampered
package could theoretically find its way into the
master Debian archive.
Ensuring that you only install software from a
trusted source will give you an important degree of
protection against malicious packages, but it
cannot eliminate all the risks inherent in
installing software.
Understanding trust
apt allows the administrator of an archive to provide a signature of the
archive's index. This signature, which (for all practical purposes) cannot be
forged, indicates that the package files listed in the index are the same files
that the administrator intended to place in the archive: ie, that the contents
of the archive have not been tampered with since it was created.[9] The
signature can be validated by checking that it corresponds to the
administrator's public key. The public key of the Debian archive is distributed
with apt, typically on your Debian CD.
When aptitude downloads an archive index, it will check whether the index is
properly signed. If it is unsigned, aptitude will not trust package files from
that archive. (see below for information on what this means) If it has a
signature but the signature is incorrect or cannot be verified, a warning will
be printed and aptitude will refuse to trust packages from that archive.
Later, when you perform an install run, aptitude will check whether the packages
are from trusted sources. If an untrusted package is being installed, or a
package is being upgraded from a trusted to an untrusted version, a warning will
be displayed and you will have the opportunity to abort the download:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.3.0 Will use 831kB of disk space DL Size: 30.4MB
--\ Packages to be upgraded
iu U wesnoth -98.3kB 0.8.7-1 0.8.8-1.0w
iuAU wesnoth-data +930kB 0.8.7-1 0.8.8-1.0w
+------------------------------------------------------------------------------+
|WARNING: untrusted versions of the following packages will be installed! #|
| #|
|Untrusted packages could compromise your system's security. You should only #|
|proceed with the installation if you are certain that this is what you want #|
|to do. #|
| #|
| * wesnoth [version 0.8.8-1.0wesnoth.org] #|
| * wesnoth-data [version 0.8.8-1.0wesnoth.org] #|
| * wesnoth-music [version 0.8.8-1.0wesnoth.org] #|
| [ Really Continue ] [ Abort Installation ] |
+------------------------------------------------------------------------------+
#
#
#
#
#
#
Trusting additional keys
You might find it useful to allow apt to trust additional archives, besides the
main Debian archive. For each archive that you want to trust, you will have to
acquire the public key that is used to sign the archive's package index. This is
typically a text file whose name ends in .asc; it might be provided by the site
administrator or downloadable from a public keyserver. For more information on
what public keys are and how to get them, see the GPG web page.
The list of keys that apt will trust is stored in the keyring file /etc/apt/
trusted.gpg. Once you have the GPG key, you can add it to this file by executing
the command gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --import
newkey.asc. aptitude will then trust any archive that is signed with the key
contained in newkey.asc.
IMG.alt.suffix = \[Warning]] Warning
Once an archive's key has been added to the APT
keyring, it will be trusted just as much as the
main Debian mirrors themselves! You should only do
this if you are very confident that the key you are
adding is correct and that the person who holds the
key is trustworthy and competent.
Managing automatically installed packages
To install one package, it is often necessary to install several others (to
fulfill its dependencies). For instance, if you wish to install the clanbomber
package, you must also install the package libclanlib2. If you remove clanbomber
again, you probably no longer need the libclanlib2 package; aptitude will
attempt to detect this and automatically remove the libclanlib2 package.
It works like this: when you install a package, aptitude will automatically
install any other packages on which it depends. These packages are marked as
having been “automatically installed”; aptitude will monitor them and remove
them when they are no longer depended upon by any manually installed package
[10] . They will appear in the preview as “packages being removed because they
are no longer used.”
As with any automatic process, there is a potential for things to go haywire.
For instance, even if a package was automatically installed to start with, it
might turn out to be useful in its own right. You can cancel the “automatic”
flag at any time by pressing m; if the package is already being removed, you can
use Package → Install (+) to cancel the removal and clear the “automatic” flag.
Resolving package dependencies
Dependency resolution in aptitude
There are two main dependency resolution algorithms in aptitude.
The first is an algorithm that is also used by programs such as apt-get and
synaptic; I will call it “immediate resolution”. It is invoked whenever you
select a package for installation interactively, and immediately after one or
more packages are marked for installation at the command-line. Immediate
resolution is fast and will solve most dependency problems, but it is sometimes
unable to find any solution.
The second algorithm, which I will call “interactive resolution”, is invoked
when packages have broken dependencies even after immediate resolution[11]. It
can resolve more dependencies, it allows you to review a solution before
applying it, and it allows you to provide feedback to the resolver, guiding it
towards a better solution.
Immediate dependency resolution
Whenever you choose to install or upgrade a package in aptitude, aptitude makes
an immediate attempt to resolve any of its dependencies that are not fulfilled.
For each unsatisfied dependency (either a “Depends”, a “Recommends”, or a
“Conflicts”), it performs the following steps:
1. If the dependency is a recommendation, aptitude tries to guess whether it
is a “new” recommendation or a “previously satisfied” recommendation.
aptitude considers a recommendation to be “new” if the package declaring
the recommendation is not currently installed, or if its installed version
does not recommend a package of the same name. On the other hand, a
recommendation is “previously satisfied” if the package declaring the
recommendation is installed, the currently installed version recommends a
package of the same name, and that recommendation is currently fulfilled.
For example: suppose that version 1.0 of prog recommends version 4.0 of
libcool1, but version 2.0 of prog recommends version 5.0 of libcool1, and
also recommends apache. If you choose to upgrade prog from version 1.0 to
version 2.0, the recommendation of apache will be considered to be “new”
because version 1.0 of prog did not recommend apache. On the other hand,
the recommendation of libcool1 is not “new”, because version 1.0 of prog
recommended libcool1, even though it recommended a different version.
However, if libcool1 is installed, then that recommendation will be
considered to be “previously satisfied”.
If the configuration option APT::Install-Recommends is true, aptitude will
always attempt to fulfill “new” and “previously satisfied” recommendations;
all others will be ignored by immediate resolution. If that option is
false, immediate dependency resolution will ignore all recommendations.
2. If the dependency is on several packages combined with OR, examine each of
the alternatives in the order that they are given. For instance, if a
package depends on “exim | mail-transport-agent”, aptitude will first
process exim, then mail-transport-agent.
3. For each alternative, attempt to resolve it. If the dependency is a
conflict, remove the current alternative if it is installed (and for an
unversioned conflict, also remove any package providing the target of the
conflict). Otherwise, install the candidate version of the current
alternative if it satisfies the dependency. If not, or if there is no
candidate version (for instance, because the current alternative is a
virtual package), and if the dependency is unversioned, attempt to install
the highest-priority package[12] whose candidate version provides the
target of the current alternative.
For instance, say we are attempting to resolve “Depends: exim | mail-
transport-agent”. aptitude will first attempt to install the package exim.
If exim is not available, aptitude will then attempt to install the
highest-priority package whose candidate version provides exim. If there is
no such package, aptitude will install the highest-priority package whose
candidate version provides the virtual package mail-transport-agent. On the
other hand, suppose that the dependency is “Depends: exim (>= 2.0.0) |
mail-transport-agent”, but only version 1.0 of exim is available. In this
case, aptitude will not install exim (because the version does not match),
nor will it attempt to install packages providing exim (because virtual
packages cannot match a dependency with a version restriction). Thus,
aptitude will fall back to installing the highest-priority package whose
candidate version provides mail-transport-agent.
4. If a package was installed by the previous step, resolve its dependencies
using this algorithm, then stop.
While this technique very often solves all the outstanding package dependencies,
it can fail in a number of common circumstances.
* Conflicts are resolved by removing the package that is the target of the
conflict. But now other packages that depend on this package have unresolved
dependencies; the immediate resolver makes no attempt to fix them.
* A dependency might not be satisfiable due to version restrictions and due to
the limitation that only candidate versions are considered. For instance, say
that versions 1.0 and 2.0 of fileutils are available, that the candidate
version is 1.0, and that the package octopus declares a dependency “Depends:
fileutils (>= 2.0)”. Immediate resolution is unable to resolve this
dependency: it will never consider version 2.0 of the package, since that is
not the candidate version.
The interactive dependency resolver can solve these situations and more. When
there are broken dependencies left over, or when immediate dependency resolution
is disabled, the interactive resolver will automatically start searching for a
solution. The next section describes how to use the interactive dependency
resolver.
Resolving Dependencies Interactively
If a dependency problem arises that cannot be handled using the immediate
dependency resolver, aptitude can assist you in resolving it. As soon as a
problem occurs, a red bar will appear at the bottom of the screen with a summary
of aptitude's suggestion about how to fix it. For instance, in the following
screenshot, aptitude is indicating that it can resolve the situation by keeping
two packages at their current versions.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.3.3 #Broken: 1 Will free 48.6MB of disk space
i A nautilus 2.10.1-4 2.10.1-4
i nautilus-cd-burner 2.10.2-1.1 2.10.2-1.1
i A nautilus-data 2.10.1-4 2.10.1-4
i netspeed 0.12.1-1 0.12.1-1
i A oaf 0.6.10-3 0.6.10-3
i pybliographer 1.2.6.2-1 1.2.6.2-1
i rhythmbox 0.8.8-13 0.8.8-13
i shermans-aquarium 3.0.1-1 3.0.1-1
idA sound-juicer -1733kB 2.10.1-3 2.10.1-3
GNOME 2 CD Ripper
sound-juicer will be removed.
The following packages depend on sound-juicer and will be broken by its
removal:
* gnome-desktop-environment depends on sound-juicer
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
As indicated at the bottom of the screen, you can view additional solutions by
pressing . and ,, apply the current solution by pressing !, and examine the
solution in more detail by pressing e. When you examine the current solution, a
screen similar to the following will appear:
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
gstreamer0.8-cdparanoia [0.8.10-1 (unstable, now)]
sound-juicer [2.10.1-2 (now)]
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
You can access information about the package affected by an action by simply
pressing Enter while the package is highlighted. For a more detailed explanation
of why aptitude made a particular decision, you can highlight the element in the
list. When you do so, the lower half of the screen will display the dependency
which was resolved by aptitude's choice, along with every way in which this
dependency could have been resolved.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
gstreamer0.8-cdparanoia [0.8.11-1 (unstable, now)]
sound-juicer [2.10.1-3 (unstable, now)]
cdparanoia plugin for GStreamer
sound-juicer depends upon gstreamer0.8-cdparanoia
--\ The following actions will resolve this dependency:
-> Downgrade sound-juicer [2.10.1-3 (unstable, now) -> 0.6.1-2 (testing)]
-> Remove sound-juicer [2.10.1-3 (unstable, now)]
-> Cancel the removal of gstreamer0.8-cdparanoia
-> Downgrade gstreamer0.8-cdparanoia [0.8.11-1 (unstable, now) -> 0.8.8-3 (tes
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
You can guide the dependency resolver to a solution of which you approve by
approving or rejecting the individual actions of a solution. If you approve an
action, the resolver will choose it whenever possible, ignoring alternatives
(when there are several approved alternatives, any one of them could be chosen).
On the other hand, if you reject an action, the resolver will never choose that
action.
To reject an action, highlight it and press r; the rejection can be cancelled by
pressing r again. Similarly, select an action and press a to approve it; press a
again to restore its original state. You can undo either action by using Undo →
Undo (Control+u) while the resolver screen is active. If you cancel a rejection
or an approval, any solutions that were ignored will be available the next time
that you generate a new solution.
IMG.alt.suffix = \[Note]] Note
By default, the resolver rejects actions that change
the state of held packages, or that install forbidden
versions of packages. You can override these
rejections, thus allowing the hold or forbidding to be
automatically overridden, in the same way that you
would override any other rejection. Setting the
configuration option Aptitude::ProblemResolver::Allow-
Break-Holds to true will disable this behavior,
meaning that the resolver will always break holds
(albeit at a penalty, see Aptitude::ProblemResolver::
BreakHoldScore).
Rejected actions are colored red and marked with an “R”, while approved actions
are colored green and marked with an “A”. You can see this in the following
screenshot, where the action “keep gstreamer0.8-cdparanoia at its current
version” has been rejected, and the action “keep sound-juicer at its current
version” has been approved.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ Keep the following packages at their current version:
R gstreamer0.8-cdparanoia [0.8.11-1 (unstable, now)]
A sound-juicer [2.10.1-3 (unstable, now)]
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
Rejections and approvals only affect newly generated solutions. You can tell
when a new solution will be generated by examining the indicator in the lower
left hand corner of the screen: if there is a number in parentheses, it is the
number of solutions that have been generated. Thus, when the number outside the
parentheses and the number inside are identical (as above), pressing . will
generate a new solution. If there is no number in parentheses (for instance, the
indicator reads [1/5]), then there are no more solutions to generate. At any
time, you can select the last generated solution by pressing >, and the first
generated solution by pressing <.
IMG.alt.suffix = \[Important]] Important
The state of the problem resolver is discarded
when you modify the state of any package. If you
mark a package for installation, for upgrade, for
removal, etc, the resolver will forget all of
your rejections and approvals, as well as all the
solutions that have been generated so far.
In addition to selecting actions in the list at the top of the screen, you can
also select them using the list in the bottom half. To access this list, either
click in it using the mouse or press Tab. Finally, to see the decisions that the
problem resolver took arranged in order, press o. This will give a list of the
dependencies that were resolved and the action taken to resolve them, as in the
following screenshot.
Actions Undo Package Resolver Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Packages Resolve Dependencies
--\ gnome-desktop-environment depends upon sound-juicer
-> Cancel the removal of sound-juicer
--\ sound-juicer depends upon gstreamer0.8-cdparanoia
-> Cancel the removal of gstreamer0.8-cdparanoia
GNOME 2 CD Ripper
gnome-desktop-environment depends upon sound-juicer
--\ The following actions will resolve this dependency:
-> Remove gnome-desktop-environment [1:2.10.2.3 (unstable, testing, now)]
-> Cancel the removal of sound-juicer
-> Downgrade sound-juicer [2.10.1-3 (unstable, now) -> 0.6.1-2 (testing)]
[1(1)/...] Suggest 2 keeps
e: Examine !: Apply .: Next ,: Previous
You can leave this display mode by pressing o again.
Costs in the interactive dependency resolver
Costs and cost components
The cost of a solution produced by the interactive dependency resolver is a
value that aptitude uses to determine how “bad” that solution is. Solutions that
are “better” are always displayed before solutions that are “worse”. The cost of
solutions is defined in the configuration option Aptitude::ProblemResolver::
SolutionCost.
Some typical costs are shown in Example 2.1, “Sample resolver costs”.
Example 2.1. Sample resolver costs
The default cost, sorting solutions by their safety cost, then by their apt pin
priority:
safety, priority
Remove as few packages as possible, then cancel as few actions as possible:
removals, canceled-actions
Sort solutions by the number of packages they remove plus twice the number of
actions they cancel.
removals + 2 * canceled-actions
As can be seen from the above examples, a cost is not necessarily a single
number. In fact, a cost consists of one or more cost components, each of which
is a number associated with the solution. When sorting solutions, the resolver
examines cost components in order, proceeding to later components only if the
earlier ones are equal. For instance, in the cost “removals, canceled-actions”,
solutions with fewer removals always appear before solutions with more removals,
regardless of how many canceled actions they have. However, solutions with the
same number of removals are sorted so that solutions with fewer canceled actions
appear first.
Cost components come in two flavors: basic cost components and compound cost
components.
Basic components simply name some property of the solution, such as “upgrades”
or “removals”. A list of built-in basic components provided by aptitude can be
found in Table 2.1, “Basic cost components”. You can also create your own cost
components using the add-to-cost-component and raise-cost-component hints; see
the section called “Configuring resolver hints” for details.
Each basic component is either a counter or a level. Counters count how many of
a solution's actions meet some condition (such as removing packages or
installing new packages), while levels associate a number with each action and
compute the highest number associated with any action in the solution.
Table 2.1. Basic cost components
_____________________________________________________________________________________________
|Name |Type |Description |
|_________|_______|___________________________________________________________________________|
|broken- |Counter|Counts the number of holds that the solution breaks, if the resolver is |
|holds | |allowed to break holds (Aptitude::ProblemResolver::Allow-Break-Holds). |
|_________|_______|___________________________________________________________________________|
|canceled-|Counter|Counts the number of pending actions that the solution cancels (keeping |
|actions | |packages at their current version). |
|_________|_______|___________________________________________________________________________|
|installs |Counter|Counts the number of packages that the solution installs. |
|_________|_______|___________________________________________________________________________|
|non- | |Counts the number of versions that the solution installs or upgrades from |
|default- |Counter|non-default sources. |
|versions | | |
|_________|_______|___________________________________________________________________________|
| | |A value that increases as the apt pin priority of a version decreases. |
|priority |Level |Specifically, this is computed by negating the pin priority (so, e.g., if |
| | |the pin priority is 500, this component will compute -500). |
|_________|_______|___________________________________________________________________________|
|removals |Counter|Counts the number of packages that the solution removes. |
|_________|_______|___________________________________________________________________________|
|removals-|Counter|Counts the number of manually installed packages that the solution removes.|
|of-manual| | |
|_________|_______|___________________________________________________________________________|
|safety |Level |A broad heuristic that increases as actions become less “safe”; see the|
| | |section called “Safety costs” for details. |
|_________|_______|___________________________________________________________________________|
|upgrades |Counter|Counts the number of packages that the solution upgrades. |
|_________|_______|___________________________________________________________________________|
Compound components are built by combining the values of basic components. For
instance, removals + canceled-actions adds the components removal and canceled-
actions, resulting in a component that counts the number of removals and
canceled actions. Compound components combine counters by adding them together
and levels by taking their maximum value, as shown in Figure 2.11, “Syntax of
compound cost components”.
IMG.alt.suffix = \[Note]] Note
It is an error to add two levels, or to take the
maximum of two counters, or to combine levels and
counters in any way. For instance, the costs removals
+ safety and max(upgrades, installs) will be treated
as errors and ignored by the resolver.[13]
Figure 2.11. Syntax of compound cost components
Add two or more basic costs:
[scale1]*cost1 + [scale2]*cost2 + ...
Take the maximum value of two or more basic costs:
max([scale1]*cost1, [scale2]*cost2, ...)
Note that each individual basic component can be multiplied by a scaling factor
before it is combined with other components. This can be used to control the
trade-offs that the resolver makes between costs. For instance, a cost of
2*removals + 3*upgrades says that three removals are exactly as “bad” as two
upgrades. Solutions that contain four removals and one upgrade will be
considered equivalent to solutions containing one removal and three upgrades,
since both have a cost of eleven.
Safety costs
Figure 2.12. Safety cost levels
IMG.alt.suffix = \Safety cost levels]
[Safety cost levels diagram]
The safety cost component is a heuristic estimate of how “safe” or “unsafe” a
solution is. Safety costs can be thought of as a way of dividing solutions into
several numbered “levels”, where “less safe” levels are given higher numbers.
Figure 2.12, “Safety cost levels” shows how this works with aptitude's default
settings.
IMG.alt.suffix Tip
= \[Tip]]
Safety cost levels are just one way to control the order in which dependency
solutions are returned. See the section called “Costs in the interactive
dependency resolver” for a full description of how to change the order in which
aptitude sorts solutions.
By default, aptitude initializes the resolver with a “reasonable” set of safety
cost levels. They are:
Table 2.2. Default safety cost levels
______________________________________________________________________________________________________
|Cost |Description |Configuration |
|level | |option |
|______|_____________________________________________________________________________|_________________|
| | |Aptitude:: |
| | |ProblemResolver::|
|10,000|Solutions that include only “safe” actions (installing the default target|Safe-Level, |
| |a package or keeping a package at its current version) and package removals. |Aptitude:: |
| | |ProblemResolver::|
| | |Remove-Level |
|______|_____________________________________________________________________________|_________________|
| |The solution that cancels all the user's actions. It used to be higher than |Aptitude:: |
|10,000|Aptitude::ProblemResolver::Remove-Level, but removing packages was ranked |ProblemResolver::|
| |higher than keeping the same packages, even if the package was to be |Keep-All-Level |
| |upgraded. | |
|______|_____________________________________________________________________________|_________________|
| | |Aptitude:: |
|40,000|Solutions that break holds set by the user or install forbidden versions. |ProblemResolver::|
| | |Break-Hold-Level |
|______|_____________________________________________________________________________|_________________|
| |Solutions that install packages from non-default versions (such as |Aptitude:: |
|50,000|“experimental”, for instance). |ProblemResolver::|
| | |Non-Default-Level|
|______|_____________________________________________________________________________|_________________|
| | |Aptitude:: |
|60,000|Solutions that remove Essential packages. |ProblemResolver::|
| | |Remove-Essential-|
| | |Level |
|______|_____________________________________________________________________________|_________________|
If a solution qualifies for several safety cost levels, it will be placed in the
highest one, that is, the one that appears last. For example, a solution that
upgrades one package to its default version and breaks a hold on a second
package will be placed at level 40,000. You can adjust the levels of individual
versions using resolver hints; see the section called “Configuring resolver
hints” for details. The default levels are illustrated in Figure 2.12, “Safety
cost levels”.
Besides numbers you can also use the keywords “maximum” and “minimum” for cost
levels. They refer to the maximal respective minimal integer value possible on
the hardware architecture of your system.
Configuring the interactive dependency resolver
Configuring resolver hints
To improve the quality of the dependency solutions that you receive, you can
provide hints to the interactive dependency resolver. These hints can alter the
priorities of the resolver, biasing it more strongly in favor of one version or
package, or they can be used to “pre-load” the resolver with rejections and
approvals, as if you had entered the resolver and manually rejected or approved
various versions.
Hints are stored in the apt configuration file, /etc/apt/apt.conf, in the
configuration group “Aptitude::ProblemResolver::Hints” (see the section called
“Configuration file reference” for details on the configuration file).
Each resolver hint consists of an action, a target, and an optional version. A
hint is written like this: "action target [version]". To apply a resolver hint,
aptitude locates one or more packages using the value of target, chooses one or
more versions of those packages using the value of version, and finally performs
the given action.
The action field of a resolver hint may be one of the following:
1. “approve”: Approve the version, as if the command Resolver → Toggle
Approved (a) had been invoked on it.
2. “reject”: Reject the version, as if the command Resolver → Toggle Rejected
(r) had been invoked on it.
3. “discard”: Discard every solution containing the version. Differs from
“reject” in that it is not visible to the user and cannot be modified
interactively.
4. “increase-safety-cost-to number”: increase the safety cost of any solution
that contains the version to number; if its safety cost is already higher
than number, this hint has no effect. The safety cost can be used (and is
used by default) to control the order in which solutions appear; see the
section called “Costs and cost components” and the section called “Safety
costs” for details.
Several special cost levels can be chosen by name:
a. conflict, discard: instead of changing the safety cost, discard
solutions containing the version as if the “discard” hint had been
applied.
b. maximum: the highest safety cost.
c. minimum: the lowest safety cost. All searches start at this cost, so
“increasing” a version to this cost has no effect. However, this value
can also be used when adjusting the predefined cost levels: for
instance, setting Aptitude::ProblemResolver::Remove-Level to “minimum”
will cause removed packages to have no effect on the safety cost of a
solution.
IMG.alt.suffix Note
= \[Note]]
The increase-safety-cost-to hint is applied in addition to any default
safety cost that is due to the selected action. For instance, a hint that
increases the safety cost of “install hal from experimental” to 15,000
will have no effect, because that action already has a safety cost of
50,000 (assuming that this version of hal is not the default candidate
version).
5. “number”: add the given number to the version's score, biasing the resolver
in favor of it or (with a negative number) away from it. For instance, the
hint 200 emacs adds 200 to the score of emacs, whereas the hint -10 emacs
subtracts 10 from its score.
If target field of a resolver hint contains a question mark (“?”) or tilde
(“~”), it is considered to be a search pattern and all matching package versions
are considered. Otherwise, it is considered to be the name of a package to
select. So the target “g++” will select only the g++ package, but the target
“?section(non-free)” will select any package in the non-free section. See the
section called “Search patterns” for more information on search patterns.
If the version field is not present, then all versions of the package are
affected by the hint. Otherwise, it may have any of the following forms:
1. “/archive”: the hint only affects versions that are available in the given
archive.
2. “<version”: the hint only affects versions whose version number is less
than version.
3. “<=version”: the hint only affects versions whose version number is less
than or equal to version.
4. “=version”: the hint only affects versions whose version number is version.
5. “<>version”: the hint only affects versions whose version number is not
version.
6. “>=version”: the hint only affects versions whose version number is greater
than or equal to version.
7. “>version”: the hint only affects versions whose version number is greater
than version.
8. “:UNINST”: instead of affecting any of the versions of target, the hint
affects the decision to remove target. For instance, “Aptitude::
ProblemResolver::Hints { "reject aptitude :UNINST"; };” will prevent the
resolver from attempting to remove aptitude.
9. “version”: the hint only affects versions whose version number is version.
Search patterns
When you search for a package or set a display limit in aptitude, the string you
enter is known as a “search pattern”. While the most basic usage of search
patterns is to match packages by name, aptitude allows you to create much more
complex searches. In addition to the visual interface, some command-line
operations can use search patterns; see Command-line reference for details.
A search pattern consists of one or more conditions (sometimes known as
“terms”); packages match the pattern if they match all of its terms. Terms
generally start with a question mark (“?”), followed by the name of the match
term, which describes the search that the term performs: for instance, the term
?name matches package names, while the term ?version matches package versions.
Finally, any additional parameters to the search term are placed in parentheses
(see the documentation of individual terms for details of what each term's
parameters mean).
IMG.alt.suffix Note
= \[Note]]
Text with no leading “?” also forms a search pattern: aptitude will treat each
word (or quoted string) as the argument to a ?name pattern, which searches for a
package whose name matches the text when the text is interpreted as a regular
expression.
IMG.alt.suffix Warning
= \[Warning]]
The behavior of aptitude when given a search pattern without a leading “?” (or “~”)
is provided as a convenience for interactive use and will change in future
releases; scripts that invoke aptitude should explicitly name the search strategy
they want to use. That is, scripts should search for “?name(coq)” rather than
“coq”).
Searching for strings
Many search terms take a string as a parameter and match it against one or more
fields of a package. Strings can be entered either with or without double quotes
(“"”), so “?name(scorch)” and “?name("scorch")” will perform the same search. If
you enter a search string using double quotes, you can include a literal double-
quote in the search string by placing a backslash (“\”) immediately before it:
for instance, “?description("\"easy\"")” will match any package whose
description contains the string “"easy"”.
If you enter a “bare” string, one not surrounded by double quotes, then aptitude
will consider the string to have “ended” when it encounters the closing
parenthesis or the comma before a second argument to the search term. [14] To
remove the special meaning of these characters, place a tilde (“~”) directly
before them. For instance, “?description(etc))” is a syntax error, because the
first “)” ends the ?description term, and the second “)” does not correspond to
any “(”. In contrast, “?description(etc~))” matches any package whose
description contains the text “etc)”. There are additional considerations if you
are using the shorthand notation for a term; see the section called “Shorthand
for search terms” for details.
Most textual searches (for package names, descriptions, etc) are performed using
case-insensitive regular expressions. A regular expression will match against a
field if any portion of the field matches the expression; for instance, “ogg[0-
9]” will match “libogg5”, “ogg123”, and “theogg4u”. Some characters have a
special meaning within regular expressions [15] , so if you want to match them
in searches you need to backslash-escape them: for instance, to find “g++”, you
should use the pattern “g\+\+”.
The characters “!” and “|” have special meanings within search patterns. In
order to include these characters in an unquoted string, you can place a tilde
(“~”) directly before them. For instance, to match packages whose description
contains either “grand” or “oblique”, use the pattern “?description
(grand~|oblique)”. However, you will probably find it more convenient to simply
use a quoted string in these cases: “?description("grand|oblique")”.
Shorthand for search terms
Some search terms can be written using “short” forms, which consist of a tilde
(“~”) followed by a single character that identifies the term, and finally the
arguments (if any) to the term. For instance, the short form of ?name(aptitude)
is ~n aptitude.
When writing a term using its short form, tilde characters and “whitespace” -
- that is, space characters, tabs, and so on -- will break the term off and
start a new term. For instance, “~mDaniel Burrows” will match any package whose
maintainer field contains “Daniel” and whose name contains “Burrows”, while
“~i~napt” matches installed packages whose name contains apt. To include
whitespace characters in the search expression, you can either place a tilde in
front of it (as in Daniel~ Burrows) or place quotation marks around it (as in
"Debian Project" or even Debian" "Project). Inside a quoted string, the
backslash character (“\”) can be used to cancel the special meaning of the
quotation mark: for instance, ~d"\"email" will match any package whose
description contains a quotation mark followed immediately by email. [16]
IMG.alt.suffix Note
= \[Note]]
Question marks (“?”) will not end the short form of a term, even if they are
followed by the name of a search term. For instance, “~napt?priority(required)”
will match all packages whose name matches the regular expression “apt?priority
(required)”. To combine a short query term with a search term specified by name,
add one or more spaces between the two terms, as in “~napt ?priority(required)”, or
place quotation marks around the text (if any) following the short form of a term,
as in “~n"apt"?priority(required)”.
Table 2.3, “Quick guide to search terms” lists the short form of each search
term.
Searches and versions
By default, a pattern matches a package if any version of the package matches
the pattern. However, some patterns will restrict their sub-patterns to only
match against some versions of a package. For instance, the search term ?depends
(pattern) will select any package that depends on a package matching pattern.
However, pattern will only be checked against the versions of the package that
actually satisfy a dependency. This means that if foo depends on bar (>= 3.0)
and versions 2.0, 3.0, and 4.0 of bar are available, then in the search pattern
?depends(?version(2\.0)), only versions 3.0 and 4.0 will be tested against
?version(2\.0), and hence foo will not be found by this search.
It matters which versions are checked because, as in the example above, some
patterns will match one version but not another. For instance, the pattern
?installed will only match the version of the package (if any) that is currently
installed. Similarly, the pattern ?maintainer(maintainer) will only match
versions that have the given maintainer. Normally all versions of a package have
the same maintainer, but this is not always the case; in fact, any search
pattern that examines the fields of a package (other than its name, of course)
will behave this way, because all the fields of a package can change between
versions.
To test a pattern against all the versions of a package, even if the pattern
would normally be tested against only some of the versions, use the ?widen term.
For instance, ?depends(?widen(?version(2\.0))) will match any package A that
depends on a package B, where B has a version matching 2.0, regardless of
whether that version actually satisfies A's dependency. On the other hand, the
?narrow term restricts the versions that its sub-pattern is matched against:
?narrow(?installed, ?depends(?version(ubuntu))) will match any package whose
installed version has a dependency that can be satisfied by a package whose
version string contains “ubuntu”.
IMG.alt.suffix = \[Note]] Note
There is a subtle, but important, distinction between
matching a pattern against a package, and matching it
against all the versions of that package. When a
pattern is matched against a package, each of its
terms is matched against the package, and so each term
will match if any version of the package matches. In
contrast, when a pattern is matched against each
version of a package, it will successfully match if it
matches when all its terms are matched against the
same version of the package.
For example: suppose that version 3.0-1 of the package
aardvark is installed, but that version 4.0-1 is
available. Then the search expression ?version(4\.0-
1)?installed matches aardvark, because ?version(4\.0-
1) matches against version 4.0-1 of aardvark, while
?installed matches against version 3.0-1. On the other
hand, this expression does not match against all the
versions of aardvark, because no single version is
installed and also has a version number of 4.0-1.
Explicit search targets
Some particularly complex searches can be expressed in aptitude using explicit
targets. In normal search expressions, there is no way to refer to the package
or version that is currently being tested. For instance, suppose that you want
to search for all packages P that depend on a second package Q such that Q
recommends P. Clearly you need to start out with a ?depends(...) term. But the
term filling in the ... needs to somehow select packages that are identical to
the one being matched against ?depends. When describing the goal above, I dealt
with this by giving the packages names, calling them P and Q; terms with
explicit targets do exactly the same thing. [17]
An explicit target is introduced by the ?for term:
Figure 2.13. Syntax of the ?for term
?for variable: pattern
This behaves exactly like pattern, but variable can be used within pattern to
refer to the package or version that pattern is being matched against. You can
use variable in two ways:
1. The term ?= will match exactly the package or version indicated by the
given variable. Specifically: if the corresponding ?for term is limited to
a particular version, then ?= will match either that version (if ?= is
limited) or the whole package; otherwise it will match any version of the
package.
See Example 2.2, “ Use of the ?= term. ” for an example of how to use ?=.
2. The term ?bind(variable, pattern) will match any package or version if the
value of variable matches against pattern.
For ?-style terms, a shorthand form is available. The expression ?bind
(variable, ?term[(args)]) can be replaced by ?variable:term(args).
See Example 2.3, “Use of the ?bind term” for an example of how to use
?bind.
Search term reference
Table 2.3, “Quick guide to search terms” provides a brief summary of all the
search terms provided by aptitude. A full description of each term can be found
below.
Table 2.3. Quick guide to search terms
_____________________________________________________________________________________________________________
|Long form |Short form |Description |
|______________|______________|_______________________________________________________________________________|
|?=variable | |Select the package bound to variable; see the section called “Explicit search|
| | |targets”. |
|______________|______________|_______________________________________________________________________________|
|?not(pattern) |!pattern |Select any package that does not match pattern. |
|______________|______________|_______________________________________________________________________________|
|?action |~aaction |Select packages that have been marked for the given action (e.g., “install”|or
|(action) | |“upgrade”). |
|______________|______________|_______________________________________________________________________________|
|?all-versions | |Select packages whose versions all match pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?and(pattern1,|pattern1 |Select any package that matches both pattern1 and pattern2. |
|pattern2) |pattern2 | |
|______________|______________|_______________________________________________________________________________|
|?any-version | |Select packages for which at least one version matches pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?architecture |~rarchitecture|Select packages for the given architecture (such as “amd64”, or “all”).|Special
|(architecture)| |values: native and foreign. |
|______________|______________|_______________________________________________________________________________|
|?archive |~Aarchive |Select packages from the given archive (such as “unstable”). |
|(archive) | | |
|______________|______________|_______________________________________________________________________________|
|?automatic |~M |Select packages that were automatically installed. |
|______________|______________|_______________________________________________________________________________|
|?bind |?variable: |Selects anything if variable matches pattern; see the section called “Explici|
|(variable, |term-name[ |search targets”. |
|pattern) |(args)] | |
|______________|______________|_______________________________________________________________________________|
|?broken |~b |Select packages that have a broken dependency. |
|______________|______________|_______________________________________________________________________________|
|?broken- |~BdepType |Select package that have a broken dependency of the given depType. |
|depType | | |
|______________|______________|_______________________________________________________________________________|
|?broken- |~DB[depType: |Select packages that have a broken dependency of the given depType matching |
|depType |]pattern |pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?broken- | | |
|reverse- |~RBdepType: |Select packages that a package matching pattern declares a broken dependency of|
|depType |pattern |type depType. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?conflicts |~Cpattern |Select packages that conflict with a package matching pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?config-files |~c |Select packages that were removed but not purged. |
|______________|______________|_______________________________________________________________________________|
|?depType |~D[depType: |Match packages that declare a dependency of type depType on a package matching |
|(pattern) |]pattern |pattern. |
|______________|______________|_______________________________________________________________________________|
|?description |~ddescription |Select packages whose description matches description. |
|(description) | | |
|______________|______________|_______________________________________________________________________________|
|?essential |~E |Select essential packages, those with Essential: yes in their control files. |
|______________|______________|_______________________________________________________________________________|
|?exact-name | |Select packages named name. |
|(name) | | |
|______________|______________|_______________________________________________________________________________|
|?false |~F |Select no packages. |
|______________|______________|_______________________________________________________________________________|
|?for variable:| |Select packages that match pattern with variable bound to the package being |
|pattern | |matched; see the section called “Explicit search targets”. |
|______________|______________|_______________________________________________________________________________|
|?garbage |~g |Select packages that are not required by any manually installed package. |
|______________|______________|_______________________________________________________________________________|
|?installed |~i |Select installed packages. |
|______________|______________|_______________________________________________________________________________|
|?maintainer |~mmaintainer |Select packages maintained by maintainer. |
|(maintainer) | | |
|______________|______________|_______________________________________________________________________________|
|?multiarch | |Select packages with a multi-arch capability of multiarch (that is, either |
|(multiarch) | |“foreign”, “same”, “allowed”, or “none”). |
|______________|______________|_______________________________________________________________________________|
|?narrow |~S filter | |
|(filter, |pattern |Select packages for which a single version matches both filter and pattern. |
|pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?name(name) |~nname, name |Select packages with the given name. |
|______________|______________|_______________________________________________________________________________|
|?new |~N |Select new packages. |
|______________|______________|_______________________________________________________________________________|
|?obsolete |~o |Match installed packages that cannot be downloaded. |
|______________|______________|_______________________________________________________________________________|
|?or(pattern1, |pattern1 | |Select packages that match pattern1, pattern2, or both. |
|pattern2) |pattern2 | |
|______________|______________|_______________________________________________________________________________|
|?origin |~Oorigin |Select packages with the given origin. |
|(origin) | | |
|______________|______________|_______________________________________________________________________________|
|?provides |~Ppattern |Select packages that provide a package matching pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?priority |~ppriority |Select packages with the given priority. |
|(priority) | | |
|______________|______________|_______________________________________________________________________________|
|?reverse- |~R[depType: |Select packages that are the targets of a dependency of type depType declared |
|depType |]pattern |by a package matching pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?reverse- |~RBdepType: |Select packages that are the targets of a broken dependency of type depType |
|broken-depType|pattern |declared by a package matching pattern. |
|(pattern) | | |
|______________|______________|_______________________________________________________________________________|
|?section |~ssection |Select packages in the given section. |
|(section) | | |
|______________|______________|_______________________________________________________________________________|
|?source- |~ename |Select packages whose source package name matches the regular expression name. |
|package(name) | | |
|______________|______________|_______________________________________________________________________________|
|?source- | | |
|version | |Select packages whose source version matches the regular expression version. |
|(version) | | |
|______________|______________|_______________________________________________________________________________|
|?tag(tag) |~Gtag |Select packages that have the given debtags tag. |
|______________|______________|_______________________________________________________________________________|
|?term(keyword)| |Full-text search for packages that contain the given keyword. |
|______________|______________|_______________________________________________________________________________|
|?term-prefix | |Full-text search for packages that contain a keyword that begins with the given|
|(keyword) | |keyword. |
|______________|______________|_______________________________________________________________________________|
|?true |~T |Select all packages. |
|______________|______________|_______________________________________________________________________________|
|?task(task) |~ttask |Select packages that are in the given task. |
|______________|______________|_______________________________________________________________________________|
|?upgradable |~U |Select packages that are installed and can be upgraded. |
|______________|______________|_______________________________________________________________________________|
|?user-tag | |Select packages that are marked with a user-tag matching the regular expression|
| | |user-tag. |
|______________|______________|_______________________________________________________________________________|
|?version |~Vversion |Select packages whose version matches version (special values: CURRENT, |
|(version) | |CANDIDATE, and TARGET). |
|______________|______________|_______________________________________________________________________________|
|?virtual |~v |Select virtual packages. |
|______________|______________|_______________________________________________________________________________|
|?widen |~Wpattern |Select versions for which pattern matches any version of the corresponding |
|(pattern) | |package, discarding local version restrictions. |
|______________|______________|_______________________________________________________________________________|
name
Matches packages whose names match the regular expression name. This is
the “default” search mode and is used for patterns that don't start with
~.
IMG.alt.suffix Note
= \[Note]]
To match packages whose names contain several different substrings, use the
?name term (described below); for instance, “?name(apti)?name(tude)” will
match any package whose name contains both “apti” and “tude”.
?=variable
Matches packages that correspond to the value of variable, which must be
bound by an enclosing ?for. For instance, ?for x: ?depends( ?recommends
( ?=x ) ) will match any package x that depends on a package which
recommends x.
For instance, the following search expression matches packages that
conflict with themselves:
Example 2.2. Use of the ?= term.
?for x: ?conflicts(?=x)
See the section called “Explicit search targets” for more information.
?not(pattern), !pattern
Matches packages which do not match the pattern pattern. For instance,
“?not(?broken)” selects packages that are not “broken”.
IMG.alt.suffix Note
= \[Note]]
To include a “!” in a search string, it must be “escaped” by placing a tilde
(“~”) in front of it; otherwise, aptitude will consider it to be part of a
?not term. For instance, to select packages whose description contains
“extra!”, use “?description(extra~!)”.
?and(pattern1, pattern2), pattern1 pattern2
Matches packages that match both pattern1 and pattern2.
?or(pattern1, pattern2), pattern1 | pattern2
Matches packages that match either pattern1 or pattern2.
IMG.alt.suffix Note
= \[Note]]
To use the character “|” in a regular expression, it must be “escaped” to prevent
aptitude from creating an OR term from it: “~|”.
(pattern)
Matches pattern. For instance, “opengl (perl|python)” matches any package
whose name contains opengl, and also contains either perl or python.
?action(action), ~aaction
Matches packages upon which the given action is going to be performed.
action can be “install”, “upgrade”, “downgrade”, “remove”, “purge”, “hold”
(tests whether a package has been placed on hold), or “keep” (tests
whether a package will be unchanged).
IMG.alt.suffix = \[Note]] Note
Note that this only tests whether an action is
actually queued up to be performed on a package,
not whether it could be performed. Thus, for
instance, ?action(upgrade) matches exactly those
packages that you have already decided to
upgrade, not packages which could be upgraded in
the future (for that, use ?upgradable).
?all-versions(pattern)
Matches any package whose versions all match the given expression. Each
version of a package will be separately tested against pattern, and the
package will match if all of its versions match. Packages without
versions, such as virtual packages, will always be matched by this search
term.
This term may not be used in a context in which the versions to match
against have already been narrowed, such as within ?depends or ?narrow.
However, it may always be used within ?widen.
?any-version(pattern)
Matches a package if any one of its versions matches the enclosed pattern.
This is the dual to ?all-versions.
This term may not be used in a context in which the versions to match
against have already been narrowed, such as within ?depends or ?narrow.
However, it may always be used within ?widen.
IMG.alt.suffix = \[Note]] Note
This term is closely related to ?narrow. In
fact, ?any-version(pattern1 pattern2) is exactly
the same as ?narrow(pattern1, pattern2).
IMG.alt.suffix Note
= \[Note]]
To be precise, as with any other pattern, it is not packages but versions of
the packages which are matched. For “aptitude search” and other uses it does
not make much difference, but “aptitude versions” will only show the
versions that match, not all versions of the package for which any version
matches. For that, use an enclosing ?widen.
?architecture(architecture-spec), ~rarchitecture-spec
Matches package versions for the given architecture-spec. For instance,
“?architecture(amd64)” matches amd64 packages, while “?architecture(all)”
matches arch-independent packages.
It also accepts the special values native and foreign, and architecture
wildcards (e.g. linux-any or any-amd64), as specified in Policy (“11.1
Architecture specification strings”).
?archive(archive), ~Aarchive
Matches package versions which are available from an archive that matches
the regular expression archive. For instance, “?archive(testing)” matches
any package available from the testing archive.
?automatic, ~M
Matches packages which were automatically installed.
?bind(variable, pattern), ?variable:term-name[(args)]
Matches any package or version if the given pattern matches the package or
version bound to variable, which must be defined in an enclosing ?for.
Example 2.3. Use of the ?bind term
?for x: ?depends(?depends(?for z: ?bind(x, ?depends(?=z))))
?for x: ?depends(?depends(?for z: ?x:depends(?=z)))
The two search patterns in the above example both match any package x such
that x depends on a package y which in turn depends on a package z such
that x also depends directly on z. The first pattern uses ?bind directly,
while the second one uses an equivalent shorthand syntax.
See the section called “Explicit search targets” for more information.
?broken, ~b
Matches packages that are “broken”: they have an unfulfilled dependency,
predependency, breaks, or conflict.
?broken-depType, ~BdepType
Matches packages which have an unfulfilled (“broken”) dependency of the
given depType. depType can be “depends”, “predepends”, “recommends”,
“suggests”, “breaks”, “conflicts”, or “replaces”.
?broken-depType(pattern), ~DB[depType:]pattern
Matches packages with an unsatisfied dependency of type depType on a
package matching pattern. depType may be any one of the dependency types
listed in the documentation of ?broken-depType.
?conflicts(pattern), ~Cpattern
Matches packages which conflict with a package matching the given pattern.
For instance, “?conflicts(?maintainer(dburrows@debian.org))” matches any
package which conflicts with a package I maintain.
?config-files, ~c
Matches packages which have been removed, but whose configuration files
remain on the system (ie, they were removed but not purged).
?depType(pattern), ~D[depType:]pattern
depType may be any one of the dependency types given in the documentation
of ?broken-depType, as well as provides: for instance, ?depends(libpng3)
will match any package that depends on libpng3. If the short form (~D) is
used and depType is not present, it defaults to depends.
If depType is “provides”, matches packages that provide a package matching
pattern (the equivalent of ?provides). Otherwise, matches packages which
declare a dependency of type depType upon a package version which matches
pattern.
?description(description), ~ddescription
Matches packages whose description matches the regular expression
description.
?essential, ~E
Matches Essential packages.
?exact-name(name)
Matches packages named name. This is similar to ?name, but the name must
match exactly. For instance, the following pattern will match only the
package apt; with ?name, it would also match aptitude, uvccapture, etc.
Example 2.4. Use of the ?exact-name term
?exact-name(apt)
?false, ~F
This term does not match any package. [18]
?for variable: pattern
Matches pattern, but the given variable may be used inside pattern to
refer to the package or package version this term to.
You can use variable in two ways. To apply a ?-style term to the variable,
write ?variable:term-name(args); for instance, ?x:depends(apt). In
addition, the term ?=variable will select any package or version that
matches the value of the given variable.
For instance, the following term will match any package x that both
depends and recommends a second package y.
Example 2.5. Use of the ?for term
?for x: ?depends( ?for y: ?x:recommends( ?=y ) )
See the section called “Explicit search targets” for more information.
?garbage, ~g
Matches packages which are not installed, or which were automatically
installed and are not depended upon by any installed package.
?installed, ~i
Matches package versions which are currently installed.
Since all versions are tested by default, this normally matches packages
which are currently installed.
?maintainer(maintainer), ~mmaintainer
Matches packages whose Maintainer field matches the regular expression
maintainer. For instance, “?maintainer(joeyh)” will find all packages
maintained by Joey Hess.
?multiarch(multiarch)
Matches packages with the multi-arch capability specified by multiarch.
For instance, “?multiarch(foreign)” will find all packages which can
satisfy dependencies of packages for another architecture. “?multiarch
(none)” will select packages with no multi-arch capability.
?narrow(filter, pattern), ~S filter pattern
This term “narrows” the search to package versions matching filter. In
particular, it matches any package version which matches both filter and
pattern. The string value of the match is the string value of pattern.
?name(name), ~nname
Matches packages whose name matches the regular expression name. For
instance, most of the packages that match “?name(^lib)” are libraries of
one sort or another.
?new, ~N
Matches packages which are “new”: that is, they have been added to the
archive since the last time the list of packages was cleared using Actions
→ Forget new packages (f) or the command-line action forget-new.
?obsolete, ~o
This term matches any installed package which is not available in any
version from any archive. These packages appear as “Obsolete or Locally
Installed” in the visual interface.
?origin(origin), ~Oorigin
Matches package versions whose origin matches the regular expression
origin. For instance, “!?origin(debian)” will find any unofficial packages
on your system (packages not from the Debian archive).
?provides(pattern), ~Ppattern
Matches package versions which provide a package that matches the pattern.
For instance, “?provides(mail-transport-agent)” will match all the
packages that provide “mail-transport-agent”.
?priority(priority), ~ppriority
Matches packages whose priority is priority; priority must be extra,
important, optional, required, or standard. For instance, “?priority
(required)” matches packages whose priority is “required”.
?reverse-depType(pattern), ~R[depType:]pattern
depType may be either “provides” or one of the dependency types given in
the documentation of ?broken-depType. If depType is not present, it
defaults to depends.
If depType is “provides”, matches packages whose name is provided by a
package version matching pattern. Otherwise, matches packages which a
package version matching pattern declares a dependency of type depType
upon.
?reverse-broken-depType(pattern), ?broken-reverse-depType(pattern), ~RB
[depType:]pattern
depType may be either “provides” or one of the dependency types given in
the documentation of ?broken-depType. If depType is not present, it
defaults to depends.
Matches packages which a package version matching pattern declares an
unsatisfied dependency of type depType upon.
?section(section), ~ssection
Matches packages whose section matches the regular expression section.
?source-package(name), ~ename
Matches packages whose source package name matches the regular expression
name.
?source-version(version)
Matches packages whose source version matches the regular expression
version.
?tag(tag), ~Gtag
Matches packages whose Tag field matches the regular expression tag. For
instance, the pattern ?tag(game::strategy) would match strategy games.
For more information on tags and debtags, see http://
debtags.alioth.debian.org.
?task(task), ~ttask
Matches packages that appear in a task whose name matches the regular
expression task.
?term(keyword)
This term performs a full-text search for keyword in the apt package
cache. When used with “aptitude search”, Search → Limit Display (l) in the
curses front-end, or typed into a package search box in the GTK+ front-
end, this term will allow aptitude to accelerate the search using a Xapian
index.
?term-prefix(keyword)
This term performs a full-text search for any keyword beginning with
keyword in the apt package cache. When used with “aptitude search”, Search
→ Limit Display (l) in the curses front-end, or typed into a package
search box in the GTK+ front-end, this term will allow aptitude to
accelerate the search using a Xapian index.
This is similar to ?term, but matches extensions of the keyword. For
instance, the following search pattern will match any package indexed
under the keywords hour, hourglass, hourly, and so on:
Example 2.6. Use of the ?term-prefix term
?term-prefix(hour)
?true, ~T
This term matches any package. For instance, “?installed?provides(?true)”
matches installed packages which provide any package.
?upgradable, ~U
This term matches any installed package which can be upgraded.
IMG.alt.suffix = \[Note]] Note
Note that this only tests whether there are
upgrades available for a package, not whether an
upgrade could be performed (with actions such as
safe-upgrade or full-upgrade).
For instance, there can be upgrades available
for several packages, but maybe the upgraded
versions of a subset conflict with each other,
so they cannot be co-installed or not all of
them upgraded at the same time.
?user-tag(tag)
This term matches any package that is marked with a user-tag matching the
regular expression tag.
?version(version), ~Vversion
Matches any package version whose version number matches the regular
expression version, with the exceptions noted below. For instance,
“?version(debian)” matches packages whose version contains “debian”.
The following values of version are treated specially. To search for
version numbers containing these values, preface the value with a
backslash; for instance, to find packages whose version number contains
CURRENT, search for \CURRENT.
* CURRENT matches the currently installed version of a package, if any.
* CANDIDATE matches the version, if any, of the package that will be
installed if you press + on the package or run aptitude install on it.
* TARGET matches the version of a package that is currently targeted for
installation, if any.
?virtual, ~v
Matches any package which is purely virtual: that is, its name is provided
by a package, but no package of that name exists. For instance,
“?virtual?reverse-provides(?installed)” matches virtual packages which are
provided by any installed package.
?widen(pattern), ~Wpattern
“Widens” the match: if the versions to match against have been limited by
an enclosing term (such as ?depends), these limits are dropped. Thus,
?widen(pattern) matches a package version if pattern matches any version
of that package.
Customizing aptitude
Customizing the package list
The package list can be heavily customized: how packages are displayed, how the
package hierarchy is formed, how packages are sorted, and even how the display
is organized are all open to change.
Customizing how packages are displayed
This section describes how to configure the contents and format of the package
list, status line, and header line, as well as the output of aptitude search.
The format of each of these locations is defined by a “format string”. A format
string is a string of text containing %-escapes such as %p, %S, and so on. The
resulting output is created by taking the text and replacing the %-escapes
according to their meanings (given below).
A %-escape can either have a fixed size, in which case it is always replaced by
the same amount of text (with extra space characters added to fill it out as
necessary), or it can be “expandable”, meaning that it takes up the space that
is not claimed by fixed-size columns. If there are several expandable columns,
the extra space is divided evenly between them.
All %-escapes come with a default size and/or expandability. The size of a %-
escape can be changed by writing it between the % and the character identifying
the escape; for instance, %20V generates the candidate version of the package,
20 characters wide. Placing a question mark (?) between the % and the character
identifying the escape causes the column's “basic” width to vary depending on
its content. Note that the resulting columns might not line up vertically!
If you want a particular %-escape to be expandable, even though it normally has
a fixed width, place a pound sign (ie, “#”) immediately after it. For instance,
to display the candidate version of a package, no matter how long it is, use the
format string %V#. You can also place # after something that is not a %-escape;
aptitude will “expand” the text preceding the # by inserting extra spaces after
it.
In summary, the syntax of a %-escape is:
%[width][?]code[#]
The configuration variables Aptitude::UI::Package-Display-Format, Aptitude::UI::
Package-Header-Format, and Aptitude::UI::Package-Status-Format define the
default formats the package list, the header at the top of the package list, and
the status line below the package list respectively. To change how the results
of an aptitude search command are displayed, use the -F option.
The following %-escapes are available in format strings:
IMG.alt.suffix Note
= \[Note]]
Some of the descriptions below refer to “the package”. In the GUI, this is
either the package being displayed or the currently selected package; in the
command-line search, this is the package being displayed.
Escape Name Default size Expandable Description
%% Literal % 1 No This is not really an escape; it simply inserts a percent sign into the output at
the point at which it occurs.
In some circumstances, a display format string will have “parameters”: for
%#number Parameter Variable No instance, in the command-line search, the groups matched by the search are used
Replacement as parameters when displaying the result. This format code will be replaced by
the parameter indicated by number.
%a Action Flag 1 No A single-character flag summarizing any action to be performed on the package, as
described in Figure 2.10, “Values of the “action” flag”.
%A Action 10 No A somewhat more verbose description of the action to be performed on the package.
%B Broken Count 12 No If there are no broken packages, produces nothing. Otherwise, produces a string
such as “Broken: 10” describing the number of broken packages.
%c Current 1 No A single-character flag summarizing the current state of the package, as
State Flag described in Figure 2.9, “Values of the “current state” flag”.
%C Current 11 No A more verbose description of the current state of the package.
State
%d Description 40 Yes The package's short description.
%D Package Size 8 No The size of the package file containing the package.
%E Architecture 10 No Outputs the string of the architecture, for example “amd64”.
%e Source 30 No Outputs the source package, for example “aptitude” for “aptitude-doc-en”.
%H Hostname 15 No The name of the computer on which aptitude is running.
Displays the highest priority assigned to a package version; for packages,
%i Pin priority 4 No displays the priority of the version which will be forced to be installed (if
any).
%I Installed 8 No The (estimated) amount of space the package takes up on disk.
Size
%m Maintainer 30 Yes The maintainer of the package.
%M Automatic 1 No If the package is automatically installed, outputs “A”; otherwise, outputs
Flag nothing.
%n Program The length of “0.8.10”. No Outputs the version of aptitude that is running, currently “0.8.10”.
Version
%N Program Name The length of the name. No Outputs the name of the program; usually “aptitude”.
Download If no packages are going to be installed, outputs nothing. Otherwise, outputs a
%o Size 17 No string describing the total size of all the package files which will be installed
(an estimate of how much needs to be downloaded); for instance, “DL size: 1000B”.
%O Origin 30 No Outputs a string of the origin of the package, for example “Debian:unstable
[amd64]”.
Outputs the name of the package. When a package is displayed in a tree context,
%p Package Name 30 Yes the name of the package will be indented, if possible, according to its depth in
the tree.
%P Priority 9 No Outputs the priority of the package.
Reverse Outputs the approximate number of installed packages which depend upon the
%r Depends 2 No package.
Count
%R Abbreviated 3 No Outputs an abbreviated description of the package's priority: for instance,
Priority “Important” becomes “Imp”.
%s Section 10 No Outputs the section of the package.
%S Trust Status 1 No If the package is untrusted, displays the letter "U".
%t Archive 10 Yes The archive in which the package is found.
Tagged (and Outputs “*” if the package is tagged, nothing otherwise.[19]
%T user-tags) 30 No
This field also includes user-tags.
Disk Usage If the scheduled actions will alter the amount of space used on the disk, outputs
%u Change 30 No a description of the change in disk space; for instance, “Will use 100MB of disk
space.”
%v Current 14 No Outputs the currently installed version of the package, or <none> if the package
Version is not currently installed.
Candidate Outputs the version of the package which would be installed if Package → Install
%V Version 14 No (+) were issued on the package, or <none> if the package is not currently
available.
%Z Size Change 9 No Outputs how much additional space will be used or how much space will be freed by
installing, upgrading, or removing a package.
Customizing the package hierarchy
The package hierarchy is generated by a grouping policy: rules describing how
the hierarchy should be built. The grouping policy describes a “pipeline” of
rules; each rule can discard packages, create sub-hierarchies in which packages
reside, or otherwise manipulate the tree. The configuration items Aptitude::UI::
Default-Grouping and Aptitude::UI::Default-Preview-Grouping set the grouping
policies for newly created package lists and preview screens, respectively. You
can set the grouping policy for the current package list by pressing G.
The grouping policy is described by a comma-separated list of rules:
rule1,rule2,.... Each rule consists of the name of the rule, possibly followed
by arguments: for instance, versions or section(subdir). Whether arguments are
required and how many arguments are required (or allowed) depends on the type of
rule.
Rules can be non-terminal or terminal. A non-terminal rule will process a
package by generating some part of the hierarchy, then passing the package on to
a later rule. A terminal rule, on the other hand, will also generate part of the
tree (typically items corresponding to the package), but does not pass its
package to a later rule. If no terminal rule is specified, aptitude will use the
default rule, which is to create the standard “package items”.
action
Groups packages according to the action scheduled on them; packages that
are not upgradable and will be unchanged are ignored. This is the grouping
that is used in preview trees.
architecture
Groups packages according to their architecture.
deps
This is a terminal rule.
Creates standard package items which can be expanded to reveal the
dependencies of the package.
filter(pattern)
Include only packages for which at least one version matches pattern.
If pattern is “missing”, no packages are discarded. This is a backwards
compatibility feature and may be removed in the future.
firstchar[(mode)]
Groups packages based on the first character of their name.
To be precise, it is not always the first letter -- for packages starting
with lib* the name of the group is liba, libb, ... like in Debian FTPs.
mode can be one of the following:
binary
Group based on the binary package name. This is the default if no
mode is specified.
Example 2.7. Grouping policy firstchar or firstchar(binary)
With the source package dpkg as an example, the binary packages
dselect, dpkg and dpkg-dev would be grouped under d, while libdpkg-
dev and libdpkg-perl would be added to the libd group.
source
Group based on the source package name.
This is useful for example when browsing packages coming from the
same source package (source grouping policy) within large
collections (examples: all installed packages, all upgradable
packages, all packages from "main" section), to add an intermediate
grouping step. In this way, one can for example emulate the
hierarchy of FTPs (try grouping: "section(topdir),firstchar
(source),source").
Example 2.8. Grouping policy firstchar(source)
Again, with the source package dpkg as an example, all the binary
packages dselect, dpkg, dpkg-dev, libdpkg-dev and libdpkg-perl would
be grouped under d.
pattern(pattern [=> title] [{ policy }] [, ...])
A customizable grouping policy. Each version of every package is matched
against the given patterns. The first match found is used to assign a
title to the package; packages are then grouped by their title. Strings of
the form \N that occur in title will be replaced by the Nth result of the
match. If title is not present, it is assumed to be \1. Note that packages
which do not match any patterns will not appear in the tree at all.
Example 2.9. Use of pattern to group packages by their maintainer
pattern(?maintainer() => \1)
The example above will group packages according to their Maintainer field.
The policy pattern(?maintainer()) will do the same thing, as the absent
title defaults to \1.
Instead of => title, an entry may end with ||. This indicates that
packages matching the corresponding pattern will be inserted into the tree
at the same level as the pattern grouping, rather than being placed in
subtrees.
Example 2.10. Use of pattern with some packages placed at the top level
pattern(?action(remove) => Packages Being Removed, ?true ||)
The example above will place packages that are being removed into a
subtree, and place all the other packages at the current level, grouped
according to the policies that follow pattern.
By default, all the packages that match each pattern are grouped according
to the rules that follow the pattern policy. To specify a different policy
for some packages, write the policy in braces ({}) after the title of the
group, after the ||, or after the pattern if neither is present. For
instance:
Example 2.11. Use of the pattern grouping policy with sub-policies
pattern(?action(remove) => Packages Being Removed {}, ?action(install) =>
Packages Being Installed, ?true || {status})
The policy in the above example has the following effects:
* Packages that are being removed are placed into a subtree labeled
“Packages Being Removed”; the grouping policy for this subtree is empty,
so the packages are placed into a flat list.
* Packages that are being installed are placed into a subtree labeled
Packages Being Installed and grouped according to the policies that
follow pattern.
* All remaining packages are placed at the top level of the tree, grouped
according to their status.
See the section called “Search patterns” for more information on the
format of pattern.
priority
Groups packages according to their priority.
section[(mode[,passthrough])]
Groups packages according to their Section field.
mode can be one of the following:
none
Group based on the whole Section field, so categories like “non-
free/games” will be created. This is the default if no mode is
specified.
topdir
Group based on the part of the Section field before the first /
character; if this part of the Section is not recognized, or if
there is no /, the first entry in the list Aptitude::Sections::Top-
Sections will be used instead.
subdir
Group based on the part of the Section field after the first /
character, if it is contained in the list Aptitude::Sections::Top-
Sections. If not, or if there is no /, group based on the entire
Section field instead.
subdirs
Group based on the part of the Section field after the first /
character, if the portion of the field preceding it is contained in
the list Aptitude::Sections::Top-Sections; if not, or if there is no
/, the entire field will be used. If there are multiple / characters
in the portion of the field that is used, a hierarchy of groups will
be formed. For instance, if “games” is not a member of Aptitude::
Sections::Top-Sections, then a package with a section of “games/
arcade” will be placed under the top-level heading “games”, in a
sub-tree named “arcade”.
If passthrough is present, packages which for some reason lack a true
Section (for instance, virtual packages) will be passed directly to the
next level of grouping without first being placed in sub-categories.
status
Groups packages into the following categories:
* Security Updates
* Upgradable
* New
* Installed
* Not Installed
* Obsolete and Locally Created
* Virtual
source
Groups packages according to their source package name.
tag[(facet)]
Groups packages according to the Tag information stored in the Debian
package files. If facet is provided, then only tags corresponding to that
facet will be displayed, and packages lacking this facet will be hidden;
otherwise, all packages will be displayed at least once (with tagless
packages listed separately from packages that have tags).
For more information on debtags, see http://debtags.alioth.debian.org.
task
Creates a tree called “Tasks” which contains the available tasks
(information on tasks is read from debian-tasks.desc in the package
tasksel). The rule following task will create its categories as siblings
of Tasks.
versions
This is a terminal rule.
Creates standard package items which can be expanded to reveal the
versions of the package.
Customizing how packages are sorted
By default, packages in the package list or in the output of aptitude search are
sorted by name. However, it is often useful to sort them according to different
criteria (for instance, package size), and aptitude allows you to do just that
by modifying the sorting policy.
Like the grouping policy described in the previous section, the sorting policy
is a comma-separated list. Each item in the list is the name of a sorting rule;
if packages are “equal” according to the first rule, the second rule is used to
sort them, and so on. Placing a tilde character (~) in front of a rule reverses
the usual meaning of that rule. For instance, priority,~name will sort packages
by priority, but packages with the same priority will be placed in reverse order
according to name.
To change the sorting policy for an active package list, press S. To change the
default sorting for all package lists, set the configuration option Aptitude::
UI::Default-Sorting. To change the sorting policy for aptitude search, use the -
-sort command-line option.
The available rules are:
installsize
Sorts packages by the estimated amount of size they require when
installed.
installsizechange
Sorts packages by the change in the installed size (estimated amount of
size required when installed), comparing the current version (if
installed) and the candidate version to be installed, upgraded or removed.
debsize
Sorts packages by the size of the package.
name
Sorts packages by name.
priority
Sorts packages by priority.
version
Sorts packages according to their version number.
Customizing keybindings
The keys used to activate commands in aptitude can be customized in the
configuration file. Every command has an associated configuration variable under
Aptitude::UI::Keybindings; to change the keystroke bound to a command, just set
the corresponding variable to the keystroke. For instance, to make the key s
perform a search, set Aptitude::UI::Keybindings::Search to “s”. You can require
the Control key to be pressed by placing “C-” in front of the key: for instance,
using “C-s” instead of “s” would bind Search to Control+s instead of s. Finally,
you can bind a command to several keys at once using a comma-separated list: for
instance, using “s,C-s” would cause both s and Control+s to perform a search.
The following commands can be bound to keys by setting the variable Aptitude::
UI::Keybindings::command, where command is the name of the command to be bound:
___________________________________________________________________________________________________________________
|Command |Default |Description |
|______________________|____________|_______________________________________________________________________________|
|ApplySolution |! |If packages are broken and aptitude has suggested a solution to the problem, |
| | |immediately apply the solution. |
|______________________|____________|_______________________________________________________________________________|
|Begin |home,C-a |Move to the beginning of the current display: to the top of a list, or to the |
| | |left of a text entry field. |
|______________________|____________|_______________________________________________________________________________|
|Cancel |C- |Cancels the current interaction: for instance, discards a dialog box or |
| |g,escape,C-[|deactivates the menu. |
|______________________|____________|_______________________________________________________________________________|
|Changelog |C |Displays the changelog.Debian of the currently selected package or package |
| | |version. |
|______________________|____________|_______________________________________________________________________________|
|ChangePkgTreeGrouping |G |Changes the grouping policy of the currently active package list. |
|______________________|____________|_______________________________________________________________________________|
|ChangePkgTreeLimit |l |Changes the limit of the currently active package list. |
|______________________|____________|_______________________________________________________________________________|
|ChangePkgTreeSorting |S |Changes the sorting policy of the currently active package list. |
|______________________|____________|_______________________________________________________________________________|
|ClearAuto |m |Marks the currently selected package as having been manually installed. |
|______________________|____________|_______________________________________________________________________________|
|CollapseAll |] |Collapses the selected tree and all its children in a hierarchical list. |
|______________________|____________|_______________________________________________________________________________|
|CollapseTree |left |Collapses the selected tree in a hierarchical list. |
|______________________|____________|_______________________________________________________________________________|
|Confirm |enter |In dialog boxes, this is equivalent to pressing “Ok”; when interacting with|a
| | |status-line multiple choice question, it chooses the default option. |
|______________________|____________|_______________________________________________________________________________|
|Cycle |tab |Switches the keyboard focus to the next “widget”. |
|______________________|____________|_______________________________________________________________________________|
|CycleNext |f6 |Switches to the next active view. |
|______________________|____________|_______________________________________________________________________________|
|CycleOrder |o |Cycles through predefined arrangements of the display. |
|______________________|____________|_______________________________________________________________________________|
|CyclePrev |f7 |Switches to the previous active view. |
|______________________|____________|_______________________________________________________________________________|
|DelBOL |C-u |Deletes all text between the cursor and the beginning of the line. |
|______________________|____________|_______________________________________________________________________________|
|DelBack |backspace,C-|Deletes the previous character when entering text. |
| |h | |
|______________________|____________|_______________________________________________________________________________|
|DelEOL |C-k |Deletes all text from the cursor to the end of the line. |
|______________________|____________|_______________________________________________________________________________|
|DelForward |delete,C-d |Deletes the character under the cursor when entering text. |
|______________________|____________|_______________________________________________________________________________|
|Dependencies |d |Displays the dependencies of the currently selected package. |
|______________________|____________|_______________________________________________________________________________|
|DescriptionCycle |i |When browsing the package list, cycles through the available views in the |
| | |information area. |
|______________________|____________|_______________________________________________________________________________|
|DescriptionDown |z |When browsing the package list, scrolls the information area down one line. |
|______________________|____________|_______________________________________________________________________________|
|DescriptionUp |a |When browsing the package list, scrolls the information area up one line. |
|______________________|____________|_______________________________________________________________________________|
|DoInstallRun |g |If not in a preview screen, display the preview screen [a]; if in a preview |
| | |screen, perform an install run. |
|______________________|____________|_______________________________________________________________________________|
|Down |down,j |Moves down: for instance, scrolls a text display down or selects the next item |
| | |in a list. |
|______________________|____________|_______________________________________________________________________________|
|DumpResolver |* |If packages are broken, writes the current state of the problem-resolver to a |
| | |file (for debugging purposes). |
|______________________|____________|_______________________________________________________________________________|
|End |end,C-e |Move to the end of the current display: to the bottom of a list, or to the |
| | |right of a text entry field. |
|______________________|____________|_______________________________________________________________________________|
|ExamineSolution |e |If some packages are broken and aptitude has suggested a solution, display a |
| | |dialog box with a detailed description of the proposed solution. |
|______________________|____________|_______________________________________________________________________________|
|ExpandAll |[ |Expands the selected tree and all its children in a hierarchical list. |
|______________________|____________|_______________________________________________________________________________|
|ExpandTree |right |Expands the selected tree in a hierarchical list. |
|______________________|____________|_______________________________________________________________________________|
|FirstSolution |< |Select the first solution produced by the problem resolver. |
|______________________|____________|_______________________________________________________________________________|
|ForbidUpgrade |F |Forbids a package from being upgraded to the currently available version (or a |
| | |particular version). |
|______________________|____________|_______________________________________________________________________________|
|ForgetNewPackages |f |Discards all information about which packages are “new” (causes the list of|
| | |“new” packages to become empty). |
|______________________|____________|_______________________________________________________________________________|
|Help |? |Displays the on-line help screen. |
|______________________|____________|_______________________________________________________________________________|
|HistoryNext |down,C-n |In a line editor with history, moves forwards in the history. |
|______________________|____________|_______________________________________________________________________________|
|HistoryPrev |up,C-p |In a line editor with history, moves backwards in the history. |
|______________________|____________|_______________________________________________________________________________|
|Hold |= |Places a package on hold. |
|______________________|____________|_______________________________________________________________________________|
|Install |+ |Flags a package for installation. |
|______________________|____________|_______________________________________________________________________________|
|InstallSingle |I |Marks a single package for installation; all other packages are kept at their |
| | |current version. |
|______________________|____________|_______________________________________________________________________________|
|Keep |: |Cancels all installation or removal requests and all holds for a package. |
|______________________|____________|_______________________________________________________________________________|
|LastSolution |< |Select the last solution produced by the problem resolver. |
|______________________|____________|_______________________________________________________________________________|
|Left |left,h |Moves left: for instance, moves one menu to the left in the menu bar, or moves |
| | |the cursor to the left when editing text. |
|______________________|____________|_______________________________________________________________________________|
|LevelDown |J |In a hierarchical list, selects the next sibling of the currently selected item|
| | |(the next item at the same level with the same parent). |
|______________________|____________|_______________________________________________________________________________|
|LevelUp |K |In a hierarchical list, selects the previous sibling of the currently selected |
| | |item (the previous item at the same level with the same parent). |
|______________________|____________|_______________________________________________________________________________|
|MarkUpgradable |U |Attempts to upgrade all packages which are not held back or forbidden from |
| | |upgrading. It also installs new Essential or Required packages. |
|______________________|____________|_______________________________________________________________________________|
|MineFlagSquare |f |In Minesweeper, places or removes a flag on a square. |
|______________________|____________|_______________________________________________________________________________|
|MineLoadGame |L |Loads a Minesweeper game. |
|______________________|____________|_______________________________________________________________________________|
|MineSaveGame |S |Saves a Minesweeper game. |
|______________________|____________|_______________________________________________________________________________|
|MineSweepSquare |No binding |Sweeps around the current square in Minesweeper. |
|______________________|____________|_______________________________________________________________________________|
|MineUncoverSquare |No binding |Uncovers the current square in Minesweeper |
|______________________|____________|_______________________________________________________________________________|
|MineUncoverSweepSquare|enter |Uncovers the current square in Minesweeper if it is covered; otherwise, sweeps |
| | |around it. |
|______________________|____________|_______________________________________________________________________________|
|NextPage |pagedown,C-f|Moves the current display one page forward. |
|______________________|____________|_______________________________________________________________________________|
|NextSolution |. |Advance the dependency resolver to the next solution. |
|______________________|____________|_______________________________________________________________________________|
|No |n[b] |This key will select the “no” button in yes/no dialog boxes. |
|______________________|____________|_______________________________________________________________________________|
| |^, left (in |Selects the parent of the selected item in a hierarchical list. left is used |
|Parent |package |only in package items (rows) when showing trees of packages. |
| |items) | |
|______________________|____________|_______________________________________________________________________________|
|PrevPage |pageup,C-b |Moves the current display one page backward. |
|______________________|____________|_______________________________________________________________________________|
|PrevSolution |, |Return the dependency resolver to the previous solution. |
|______________________|____________|_______________________________________________________________________________|
|Purge |_ |Flags the currently selected package to be purged. |
|______________________|____________|_______________________________________________________________________________|
|PushButton |space,enter |Activates the currently selected button, or toggles a checkbox. |
|______________________|____________|_______________________________________________________________________________|
|Quit |q |Close the current view. |
|______________________|____________|_______________________________________________________________________________|
|QuitProgram |Q |Quit the entire program. |
|______________________|____________|_______________________________________________________________________________|
|RejectBreakHolds | |Reject all resolver actions that would break a hold; equivalent to Resolver →|
| | |Reject Breaking Holds. |
|______________________|____________|_______________________________________________________________________________|
|Refresh |C-l |Redraws the screen from scratch. |
|______________________|____________|_______________________________________________________________________________|
|Remove |- |Flags a package for removal. |
|______________________|____________|_______________________________________________________________________________|
|ReInstall |L |Flags the currently selected package to be reinstalled. |
|______________________|____________|_______________________________________________________________________________|
|RepeatSearchBack |N |Repeats the last search, but searches in the opposite direction. |
|______________________|____________|_______________________________________________________________________________|
|ReSearch |n |Repeats the last search. |
|______________________|____________|_______________________________________________________________________________|
|ReverseDependencies |r |Displays packages which depend upon the currently selected package. |
|______________________|____________|_______________________________________________________________________________|
|Right |right,l |Moves right: for instance, moves one menu to the right in the menu bar, or |
| | |moves the cursor to the right when editing text. |
|______________________|____________|_______________________________________________________________________________|
|Search |/ |Activate the “search” function of the currently active interface element. |
|______________________|____________|_______________________________________________________________________________|
|SearchBack |\ |Activate the “search backwards” function of the currently active interface |
| | |element. |
|______________________|____________|_______________________________________________________________________________|
|SearchBroken |b |In a package tree, search for the next broken package. |
|______________________|____________|_______________________________________________________________________________|
|SetAuto |M |Marks the current package as having been automatically installed. |
|______________________|____________|_______________________________________________________________________________|
|ShowHideDescription |D |In a package list, toggles whether the information area is visible. |
|______________________|____________|_______________________________________________________________________________|
|SolutionActionApprove |a |When viewing a solution, marks the currently selected action as "approved" (it |
| | |will be included in future solutions whenever possible). |
|______________________|____________|_______________________________________________________________________________|
|SolutionActionReject |r |When viewing a solution, marks the currently selected action as "rejected" |
| | |(future solutions will not contain it). |
|______________________|____________|_______________________________________________________________________________|
|ToggleExpanded |enter |Expands or collapses the currently selected tree in a hierarchical list. |
|______________________|____________|_______________________________________________________________________________|
|ToggleMenuActive |C-m,f10,C- |Activates or deactivates the main menu. |
| |space | |
|______________________|____________|_______________________________________________________________________________|
|Undo |C-_,C-u |Cancels the last action, up to when aptitude was started OR the last time you |
| | |update the package lists or installed packages. |
|______________________|____________|_______________________________________________________________________________|
|Up |up,k |Moves up: for instance, scrolls a text display up or selects the previous item |
| | |in a list. |
|______________________|____________|_______________________________________________________________________________|
|UpdatePackageList |u |Updates the list of packages by fetching new lists from the Internet if |
| | |necessary. |
|______________________|____________|_______________________________________________________________________________|
|Versions |v |Displays the available versions of the currently selected package. |
|______________________|____________|_______________________________________________________________________________|
|Yes |y [b] |This key will select the “Yes” button in yes/no dialog boxes. |
|______________________|____________|_______________________________________________________________________________|
|[a] unless Aptitude::Display-Planned-Action is false. |
| |
|[b] This default may be different in different locales. |
|___________________________________________________________________________________________________________________|
In addition to letter keys, number keys, and punctuation, the following
“special” keys can be bound:
_____________________________________________________________________________
|Key name |Description |
|________________|____________________________________________________________|
|a1 |The A1 key. |
|________________|____________________________________________________________|
|a3 |The A3 key. |
|________________|____________________________________________________________|
|b2 |The B2 key. |
|________________|____________________________________________________________|
|backspace |The Backspace key. |
|________________|____________________________________________________________|
|backtab |The back-tab key |
|________________|____________________________________________________________|
|begin |The Begin key (not Home) |
|________________|____________________________________________________________|
|break |The “break” key. |
|________________|____________________________________________________________|
|c1 |The C1 key. |
|________________|____________________________________________________________|
|c3 |The C3 key. |
|________________|____________________________________________________________|
|cancel |The Cancel key. |
|________________|____________________________________________________________|
|create |The Create key. |
|________________|____________________________________________________________|
|comma |Comma (,) -- note that because commas are used to list keys,|
| |this is the only way to bind to a comma. |
|________________|____________________________________________________________|
|command |The Command key. |
|________________|____________________________________________________________|
|copy |The Copy key. |
|________________|____________________________________________________________|
|delete |The Delete key. |
|________________|____________________________________________________________|
|delete_line |The “delete line” key. |
|________________|____________________________________________________________|
|down |The “down” arrow key. |
|________________|____________________________________________________________|
|end |The End key. |
|________________|____________________________________________________________|
|entry |The Enter key. |
|________________|____________________________________________________________|
|exit |The Exit key. |
|________________|____________________________________________________________|
|f1, f2, ..., f10|The F1 through F10 keys. |
|________________|____________________________________________________________|
|find |The Find key. |
|________________|____________________________________________________________|
|home |The Home key. |
|________________|____________________________________________________________|
|insert |The Insert key. |
|________________|____________________________________________________________|
|insert_exit |The “insert exit” key. |
|________________|____________________________________________________________|
|clear |The “clear” key. |
|________________|____________________________________________________________|
|clear_eol |The “clear to end of line” key. |
|________________|____________________________________________________________|
|clear_eos |The “clear to end of screen” key. |
|________________|____________________________________________________________|
|insert_line |The “insert line” key. |
|________________|____________________________________________________________|
|left |The “left” arrow key. |
|________________|____________________________________________________________|
|mark |The Mark key. |
|________________|____________________________________________________________|
|message |The Message key. |
|________________|____________________________________________________________|
|move |The Move key. |
|________________|____________________________________________________________|
|next |The Next key. |
|________________|____________________________________________________________|
|open |The Open key. |
|________________|____________________________________________________________|
|previous |The Previous key. |
|________________|____________________________________________________________|
|print |The Print key. |
|________________|____________________________________________________________|
|redo |The Redo key. |
|________________|____________________________________________________________|
|reference |The Reference key. |
|________________|____________________________________________________________|
|refresh |The Refresh key. |
|________________|____________________________________________________________|
|replace |The Replace key. |
|________________|____________________________________________________________|
|restart |The Restart key. |
|________________|____________________________________________________________|
|resume |The Resume key. |
|________________|____________________________________________________________|
|return |The Return key. |
|________________|____________________________________________________________|
|right |The “right” arrow key. |
|________________|____________________________________________________________|
|save |The Save key. |
|________________|____________________________________________________________|
|scrollf |The “scroll forward” key. |
|________________|____________________________________________________________|
|scrollr |The “scroll backwards” key. |
|________________|____________________________________________________________|
|select |The Select key. |
|________________|____________________________________________________________|
|suspend |The Suspend key. |
|________________|____________________________________________________________|
|pagedown |The “Page Down” key. |
|________________|____________________________________________________________|
|pageup |The “Page Up” key. |
|________________|____________________________________________________________|
|space |The Space key |
|________________|____________________________________________________________|
|tab |The Tab key |
|________________|____________________________________________________________|
|undo |The Undo key. |
|________________|____________________________________________________________|
|up |The “up” arrow key. |
|________________|____________________________________________________________|
In addition to binding keys globally, it is possible to change key bindings for
one particular part (or domain) of aptitude: for instance, to make Tab the
equivalent of the right arrow key in menu bars, set Aptitude::UI::Keybindings::
Menubar::Right to “tab,right”. The following domains are available:
_____________________________________________________________________________________________
|Domain |Description |
|_____________|_______________________________________________________________________________|
|EditLine |Used by line-editing widgets, such as the entry field in a “search” dialog.|
|_____________|_______________________________________________________________________________|
|Menu |Used by drop-down menus. |
|_____________|_______________________________________________________________________________|
|Menubar |Used by the menu bar at the top of the screen. |
|_____________|_______________________________________________________________________________|
|Minesweeper |Used by the Minesweeper mode. |
|_____________|_______________________________________________________________________________|
|MinibufChoice|Used by the multiple-choice prompts that appear if you have chosen to have some|
| |prompts appear in the status line. |
|_____________|_______________________________________________________________________________|
|Pager |Used when displaying a file on disk (for instance, the help text). |
|_____________|_______________________________________________________________________________|
|PkgNode |Used by packages, trees of packages, package versions, and package dependencies|
| |when they appear in package lists. |
|_____________|_______________________________________________________________________________|
|PkgTree |Used by package lists. |
|_____________|_______________________________________________________________________________|
|Table |Used by tables of widgets (for instance, dialog boxes). |
|_____________|_______________________________________________________________________________|
|TextLayout |Used by formatted text displays, such as package descriptions. |
|_____________|_______________________________________________________________________________|
|Tree |Used by all tree displays (including package lists, for which it can be |
| |overridden by PkgTree). |
|_____________|_______________________________________________________________________________|
Customizing text colors and styles
The colors and visual styles used by aptitude to display text can be extensively
customized. Each visual element has an associated “style”, which describes the
particular colors and visual attributes that will be used to display that
element. Styles take the form of a list of color and attribute settings. This
list is not necessarily exhaustive; if some colors or attributes are not
explicitly specified, their values will be taken from the surrounding visual
context. In fact, most visual elements have an “empty” style by default.
You can change the contents of a style by creating a configuration group of the
same name in the apt or aptitude configuration file. For instance, the
“MenuBorder” style is used to draw the visual border around drop-down menus. By
default, this border is drawn bold and white-on-blue. Placing the following text
in the configuration file would change it to white-on-cyan:
Aptitude::UI::Styles {
MenuBorder {fg white; bg cyan; set bold;};
};
As you can see, a style's configuration group consists of a sequence of
instructions. The general classes of instructions are:
fg color
Sets the text foreground to the given color. See below for a list of the
colors known to aptitude.
bg color
Sets the text background to the given color. See below for a list of the
colors known to aptitude.
set attribute
Enables the given text attribute. See below for a list of the text
attributes known to aptitude.
clear attribute
Disables the given text attribute. See below for a list of the text
attributes known to aptitude.
flip attribute
Toggles the given text attribute: if it is enabled in the surrounding
element, it will be disabled, and vice versa. See below for a list of the
text attributes known to aptitude.
The colors that aptitude recognizes are black, blue, cyan, green, magenta, red,
white, and yellow [20]. In addition, you may specify default in place of a
background color to use the default terminal background (this could be the
default color, an image file, or even “transparent”). The styles that aptitude
recognizes are:
blink
Enables blinking text.
bold
Makes the foreground color of the text (or the background if reverse video
is enabled) brighter.
dim
May cause text to be extra-dim on some terminals. No effect has been
observed on common Linux terminals.
reverse
Swaps the foreground and background colors. Many visual elements flip this
attribute to perform common highlighting tasks.
standout
This enables “the best highlighting mode of the terminal”. In xterms it is
similar, but not idential to, reverse video; behavior on other terminals
may vary.
underline
Enables underlined text.
You can select several attributes at once by separating them with commas; for
instance, set bold,standout;.
IMG.alt.suffix = \[Note]] Note
As hinted at above, the interpretation of both styles
and text attributes is highly terminal-dependent. You
may need to experiment a bit to find out exactly what
some settings do on your terminal.
The following styles can be customized in aptitude:
Figure 2.14. Customizable styles in aptitude
________________________________________________________________________________________________________________________
|Style |Default |Description |
|__________________________|_____________|_______________________________________________________________________________|
|Bullet |fg yellow; |The style of the bullets in bulleted lists. |
| |set bold; | |
|__________________________|_____________|_______________________________________________________________________________|
| | |The style of newer versions of the package in the changelog view. Note that |
|ChangelogNewerVersion |set bold; |aptitude will only highlight newer versions of the package if you have the |
| | |package libparse-debianchangelog-perl installed. |
|__________________________|_____________|_______________________________________________________________________________|
|Default |fg white; bg |The basic style of the screen. |
| |black; | |
|__________________________|_____________|_______________________________________________________________________________|
|DepBroken |fg black; bg |The style of unfulfilled dependencies. |
| |red; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg black; bg | |
|DisabledMenuEntry |blue; set |The style of menu entries that are disabled and cannot be used. |
| |dim; | |
|__________________________|_____________|_______________________________________________________________________________|
|DownloadHit |fg black; bg |The style used to indicate that a file was “hit”: i.e., it has not changed |
| |green; |since the last time it was downloaded. |
|__________________________|_____________|_______________________________________________________________________________|
|DownloadProgress |fg blue; bg |The style of the progress indicator for a download. |
| |yellow; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|EditLine |black; clear |The style of line editors (for instance, the entry in the “Search” dialog).|
| |reverse; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|Error |red; set |The style of error messages. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|Header |blue; set |The style of screen headers. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|HighlightedMenuBar |blue; set |The style of the currently selected menu name in the menu bar. |
| |bold,reverse;| |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|HighlightedMenuEntry |blue; set |The style of the currently selected choice in a menu. |
| |bold,reverse;| |
|__________________________|_____________|_______________________________________________________________________________|
| |fg yellow; bg| |
|MediaChange |red; set |The style of the dialog used to ask the user to insert a new CD. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|MenuBar |blue; set |The style of the menu bar. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|MenuBorder |blue; set |The style of the borders that surround a drop-down menu. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
|MenuEntry |fg white; bg |The style of each entry in a drop-down menu. |
| |blue; | |
|__________________________|_____________|_______________________________________________________________________________|
|MineBomb |fg red; set |The style of bombs in Minesweeper. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
|MineBorder |set bold; |The style of the border drawn around a Minesweeper board. |
|__________________________|_____________|_______________________________________________________________________________|
|MineFlag |fg red; set |The style of flags in Minesweeper. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
|MineNumberN |Various |The style of the number N in Minesweeper; N may range from 0 to 8. |
|__________________________|_____________|_______________________________________________________________________________|
|MultiplexTab |fg white; bg |The color used to display “tabs” other than the currently selected one. |
| |blue; | |
|__________________________|_____________|_______________________________________________________________________________|
|MultiplexTabHighlighted |fg blue; bg |The color used to display the currently selected “tab”. |
| |white; | |
|__________________________|_____________|_______________________________________________________________________________|
|PkgBroken |fg red; flip |The style of packages in the package list which have unfulfilled dependencies. |
| |reverse; | |
|__________________________|_____________|_______________________________________________________________________________|
|PkgBrokenHighlighted |fg red; |The style of highlighted packages in the package list which have unfulfilled |
| | |dependencies. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgNotInstalled | |The style of packages which are not currently installed and will not be |
| | |installed. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgNotInstalledHighlighted| |The style of highlighted packages which are not currently installed and will |
| | |not be installed. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgIsInstalled |set bold; |The style of packages which are currently installed and for which no actions |
| | |are scheduled. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgIsInstalledHighlighted |set bold; |The style of highlighted packages which are currently installed and for which |
| |flip reverse;|no actions are scheduled. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToDowngrade |set bold; |The style of packages in the package list which will be downgraded. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToDowngradeHighlighted |set bold; |The style of highlighted packages in the package list which will be downgraded.|
| |flip reverse | |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToHold |fg white; |The style of packages in the package list which are on hold. |
| |flip reverse;| |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToHoldHighlighted |fg white; |The style of highlighted packages in the package list which are on hold. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToInstall |fg green; |The style of packages in the package list which are being installed (not |
| |flip reverse;|upgraded) or reinstalled. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToInstallHighlighted |fg green; |The style of highlighted packages in the package list which are being installed|
| | |(not upgraded) or reinstalled. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToRemove |fg magenta; |The style of packages in the package list which will be removed or purged. |
| |flip reverse;| |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToRemoveHighlighted |fg magenta; |The style of highlighted packages in the package list which will be removed or |
| | |purged. |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToUpgrade |fg cyan; flip|The style of packages in the package list which will be upgraded. |
| |reverse; | |
|__________________________|_____________|_______________________________________________________________________________|
|PkgToUpgradeHighlighted |fg cyan; |The style of highlighted packages in the package list which will be upgraded. |
|__________________________|_____________|_______________________________________________________________________________|
|Progress |fg blue; bg |The style of progress indicators such as the one that appears while the package|
| |yellow; |cache is being loaded. |
|__________________________|_____________|_______________________________________________________________________________|
|SolutionActionApproved |bg green; |The style of approved actions in a solution. |
|__________________________|_____________|_______________________________________________________________________________|
|SolutionActionRejected |bg red; |The style of rejected actions in a solution. |
|__________________________|_____________|_______________________________________________________________________________|
| |fg white; bg | |
|Status |blue; set |The style of status lines at the bottom of the screen. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
|TreeBackground | |The basic color of all visual lists and trees. |
|__________________________|_____________|_______________________________________________________________________________|
| |fg red; bg | |
|TrustWarning |black; set |The color used to display warnings about package trust. |
| |bold; | |
|__________________________|_____________|_______________________________________________________________________________|
Customizing the display layout
It is possible to rearrange the aptitude package list by making suitable
modifications to the configuration file.
Display elements
The layout is stored in the configuration group Aptitude::UI::Default-Package-
View, and consists of a list of display elements:
Name Type {
Row row;
Column column;
Width width;
Height height;
additional options...
};
This creates a display element named Name; the type of element created is
determined by Type. The Row, Column, Width, and Height options must be present;
they determine where the display element is placed. (see below for a detailed
explanation of how display elements are arranged)
For examples of how to change the display layout, see the theme definitions in
the file /usr/share/aptitude/aptitude-defaults.
The following types of display elements are available:
Description
This display element will contain the “information area” (typically a
description of the currently selected package).
The option PopUpDownKey gives the name of a keyboard command which will
cause the display element to be shown or hidden. For instance, setting
this to ShowHideDescription will give the current display element the same
behavior as the default information area. The option PopUpDownLinked gives
the name of another display element; the current element will be shown or
hidden whenever the other element is.
MainWidget
This is a placeholder for the “main” display element: typically this is
the list of packages. A display layout must contain exactly one MainWidget
element: no more, no less.
Static
A region of the screen which displays some text, possibly containing
formatting codes as described in the section called “Customizing how
packages are displayed”. The text to display can be given in the Columns
option, or it can be stored in another configuration variable specified by
the ColumnsCfg option. The color of the text is determined by the color
named by the Color option.
Static items can be displayed and hidden in the same way as Description
items, using the PopUpDownKey and PopUpDownLinked options.
Placement of display elements
The display elements are arranged in a “table”. The upper-left corner of an
element is in the cell given by its Row and Column options (typically starting
from row 0 and column 0, but this is not required). The width of an element in
cells is given by its Width option, and its height is given by its Height
option.
Once the display elements are arranged and have been given an initial amount of
space on the screen, there is likely to be space left over. If there is extra
vertical space, each row containing a display element whose RowExpand option is
true will be allocated a share of the extra space; similarly, if there is extra
horizontal space, each column containing a display element whose ColExpand
option is true will be allocated a share of the extra space.
In the event that there is not enough space, every row and column whose widgets
all have their RowShrink or ColShrink options set to true will be shrunk. If
this is not enough, all rows and columns are shrunk to fit into the available
space.
If a display element is not expanded, but its row or column is, its alignment is
determined by the RowAlign and ColAlign options. Setting them to Left, Right,
Top, Bottom, or Center will tell aptitude where to place the element within the
row or column.
For instance, the following configuration group creates a static element named
“Header”, which is three cells wide and will expand horizontally but not
vertically. It has the same color as other header lines and uses the standard
display format for header lines:
Header Static {
Row 0;
Column 0;
Width 3;
Height 1;
ColExpand true;
ColAlign Center;
RowAlign Center;
Color ScreenHeaderColor;
ColumnsCfg HEADER;
};
Display layout option reference
The following options are available for display elements:
ColAlign alignment;
alignment must be either Left, Right, or Center. If the row containing the
current display element is wider than the element itself and ColExpand is
false, the element will be placed within the row according to the value of
alignment.
If this option is not present, it defaults to Left.
ColExpand true|false;
If this option is set to true, the column containing this display element
will be allocated a share of any extra horizontal space that is available.
If this option is not present, it defaults to false.
Color colorname;
This option applies to Static elements. colorname is the name of a color
(for instance, ScreenStatusColor) which should be used as the “default”
color for this display element.
If this option is not present, it defaults to DefaultWidgetBackground.
ColShrink true|false;
If this option is set to true on each element in a column and there is not
enough horizontal space, the column will be shrunk as necessary to fit the
available space. Note that a column may be shrunk even if ColShrink is
false; it simply indicates that aptitude should try shrinking a particular
column before shrinking other columns.
If this option is not present, it defaults to false.
Column column;
Specifies the leftmost column containing this display element.
Columns format;
This option applies to Static display elements for which the ColumnsCfg
option is not set. It sets the displayed contents of the status item; it
is a format string as described in the section called “Customizing how
packages are displayed”.
ColumnsCfg HEADER|STATUS|name;
This option applies to Static display elements. It sets the display format
of the current element to the value of another configuration variable: if
it is HEADER or STATUS, the options Aptitude::UI::Package-Header-Format
and Aptitude::UI::Package-Status-Format, repectively, are used; otherwise,
the option name is used.
If this option is not present, the value of the Columns option is used to
control the contents of the static item.
Height height;
Specifies the height of the current display element.
PopUpDownKey command;
This option applies to Description and Static display elements.
command is the name of a keyboard command (for instance,
ShowHideDescription). When this key is pressed, the display element will
be hidden if it is visible, and displayed if it is hidden.
PopUpDownLinked element;
This option applies to Description and Static display elements.
element is the name of a display element. When element is displayed, the
current element will also be displayed; when element is hidden, the
current element will also be hidden.
Row row;
Specifies the uppermost row containing this display element.
RowAlign alignment;
alignment must be either Top, Bottom, or Center. If the row containing the
current display element is taller than the element itself and RowExpand is
false, the element will be placed within the row according to the value of
alignment.
If this option is not present, it defaults to Top.
RowExpand true|false;
If this option is set to true, the row containing this display element
will be allocated a share of any extra vertical space that is available.
If this option is not present, it defaults to false.
RowShrink true|false;
If this option is set to true on each element in a row and there is not
enough vertical space, the row will be shrunk as necessary to fit the
available space. Note that a row may be shrunk even if RowShrink is false;
it simply indicates that aptitude should try shrinking a particular row
before shrinking other rows.
If this option is not present, it defaults to false.
Visible true|false;
If set to false, this display element will initially be hidden. Presumably
only useful in conjunction with PopUpDownKey and/or PopUpDownLinked.
If this option is not present, it defaults to true.
Width width;
Specifies the width of the current display element.
Configuration file reference
Configuration file format
In its basic form, aptitude's configuration file is a list of options and their
values. Each line of the file should have the form “Option Value;”: for
instance, the following line in the configuration file sets the option
Aptitude::Theme to “Dselect”.
Aptitude::Theme "Dselect";
An option can “contain” other options if they are written in curly braces
between the option and the semicolon following it, like this:
Aptitude::UI {
Package-Status-Format "";
Package-Display-Format "";
};
An option that contains other options is sometimes called a group. In fact, the
double colons that appear in option names are actually a shorthand way of
indicating containment: the option Aptitude::UI::Default-Grouping is contained
in the group Aptitude::UI, which itself is contained in the group Aptitude.
Thus, if you wanted to, you could set this option to "" as follows:
Aptitude {
UI {
Default-Grouping "";
};
};
For more information on the format of the configuration file, see the manual
page apt.conf(5).
Locations of configuration files
aptitude's configuration is read from the following sources, in order:
1. Configuration file options specified on the command-line.
2. The user's configuration file, ~/.aptitude/config. This file is overwritten
when the user modifies settings in the Options menu.
3. The system configuration file, /etc/apt/apt.conf.
4. The system configuration fragment files, /etc/apt/apt.conf.d/*.
5. The file specified by the APT_CONFIG environment variable (if any).
6. Default values stored in /usr/share/aptitude/aptitude-defaults.
7. Default values built into aptitude.
When an option is being checked, these sources are searched in order, and the
first one that provides a value for the option is used. For instance, setting an
option in /etc/apt/apt.conf will override aptitude's defaults for that option,
but will not override user settings in ~/.aptitude/config.
Available configuration options
The following configuration options are used by aptitude. Note that these are
not the only available configuration options; options used by the underlying apt
system are not listed here. See the manual pages apt(8) and apt.conf(5) for
information on apt options.
Option:APT::AutoRemove::RecommendsImportant
Default:true
Description: If this option is true, then aptitude will not consider packages to
be unused (and thus will not automatically remove them) as long as any installed
package recommends them, even if APT::Install-Recommends is false. For more
information, see the section called “Managing automatically installed packages”.
Option:APT::AutoRemove::SuggestsImportant
Default:true
Description: If this option is true, then aptitude will not consider packages to
be unused (and thus will not automatically remove them) as long as any installed
package suggests them. For more information, see the section called “Managing
automatically installed packages”.
Option:APT::Get::List-Cleanup
Default:true
Description: A synonym for APT::List-Cleanup. If either of these options is set
to false, aptitude will not delete old package list files after downloading a
new set of package lists.
Option:APT::List-Cleanup
Default:true
Description: A synonym for APT::Get::List-Cleanup. If either of these options is
set to false, aptitude will not delete old package list files after downloading
a new set of package lists.
Option:APT::Install-Recommends
Default:true
Description: If this option is true and Aptitude::Auto-Install is true, then
whenever you mark a package for installation, aptitude will also mark the
packages it recommends for installation. Furthermore, if this option is true,
aptitude will not consider packages to be unused (and thus will not
automatically remove them) as long as any installed package reommends them. For
more information, see the section called “Managing automatically installed
packages” and the section called “Immediate dependency resolution”.
Option:Aptitude::Allow-Null-Upgrade
Default:false
Description: Normally, if you try to start an install run when no actions will
be performed, aptitude will print a warning and return to the package list. If
this option is true, aptitude will continue to the preview screen whenever there
are upgradable packages, rather than displaying a reminder about the Actions →
Mark Upgradable (U) command.
Option:Aptitude::Always-Use-Safe-Resolver
Default:false
Description: If this option is true, aptitude's command-line actions will always
use a “safe” dependency resolver, as if --safe-resolver had been passed on the
command line.
Option:Aptitude::Autoclean-After-Update
Default:false
Description: If this option is true, aptitude will clean up obsolete files (see
Actions → Clean obsolete files) every time you update the package list. This
option is similar to Aptitude::Clean-After-Install.
Option:Aptitude::Auto-Fix-Broken
Default:true
Description: If this option is false, aptitude will ask for permission before
attempting to fix any broken packages.
Option:Aptitude::Auto-Install
Default:true
Description: If this option is true, aptitude will automatically attempt to
fulfill the dependencies of a package when you mark a package to be installed or
upgraded.
Option:Aptitude::Auto-Install-Remove-Ok
Default:false
Description: If this option is true, aptitude will automatically remove
conflicting packages when you mark a package to be installed or upgraded.
Normally these conflicts are flagged and you must handle them manually.
Option:Aptitude::Auto-Upgrade
Default:false
Description: If this option is true, aptitude will automatically flag all
upgradable packages for upgrade when the program starts, as if you had issued
the command Actions → Mark Upgradable (U).
Option:Aptitude::Clean-After-Install
Default:false
Description: If this option is true, aptitude will clean up all files in the
package cache directory (see Actions → Clean package cache) after successful
installation of packages (or similar operations). This option is similar to
Aptitude::Autoclean-After-Update.
Option:Aptitude::CmdLine::Always-Prompt
Default:false
Description: In command-line mode, if this is set, aptitude will always prompt
before starting to install or remove packages, even if the prompt would normally
be skipped. This is equivalent to the -P command-line option.
Option:Aptitude::CmdLine::Assume-Yes
Default:false
Description: In command-line mode, if this option is true, aptitude will act as
if the user had answered “yes” to every prompt, causing most prompts to be
skipped. This is equivalent to the -y command-line option.
Option:Aptitude::CmdLine::Disable-Columns
Default:false
Description: If this option is enabled, the results of command-line searches
(performed via aptitude search) will not be formatted into fixed-width columns
or truncated to the screen width. This is equivalent to the --disable-columns
command-line option.
Option:Aptitude::CmdLine::Download-Only
Default:false
Description: In command-line mode, if this option is true, aptitude will
download package files but not install them. This is equivalent to the -
d command-line option.
Option:Aptitude::CmdLine::Fix-Broken
Default:false
Description: In command-line mode, if this option is true, aptitude will be more
aggressive when attempting to fix the dependencies of broken packages. This is
equivalent to the -f command-line option.
Option:Aptitude::CmdLine::Versions-Group-By
Default: Set to auto, none, package, or source-package to control whether and
how the output of aptitude versions is grouped. Equivalent to the command-line
option --group-by (see its documentation for more description of what the values
mean).
Option:Aptitude::CmdLine::Ignore-Trust-Violations
Default:false
Description: In command-line mode, causes aptitude to ignore the installation of
untrusted packages. This is a synonym for APT::Get::AllowUnauthenticated.
Option:Aptitude::CmdLine::Package-Display-Format
Default:%c%a%M %p# - %d#
Description: This is a format string, as described in the section called
“Customizing how packages are displayed”, which is used to display the results
of a command-line search. This is equivalent to the -F command-line option.
Option:Aptitude::CmdLine::Package-Display-Width
Default:
Description: This option gives the width in characters for which command-line
search results should be formatted. If it is empty (the default; ie, ""), search
results will be formatted for the current terminal size, or for an 80-column
display if the terminal size cannot be determined.
Option:Aptitude::CmdLine::Progress::Percent-On-Right
Default:false
Description: This option controls whether command-line progress indicators
display the percentage on the left-hand side of the screen, in the same style as
apt-get, or on the right-hand side (the default). This option does not affect
download progress indicators.
Option:Aptitude::CmdLine::Progress::Retain-Completed
Default:false
Description: If this value is false, then command-line progress indicators will
be deleted and overwritten once the task they represent is completed. If it is
true, then they will be left on the terminal. This option does not affect
download progress indicators.
Option:Aptitude::CmdLine::Request-Strictness
Default:10000
Description: When run in command-line mode, if dependency problems are
encountered, aptitude will add this value to the problem resolver score of each
action that you explicitly request.
Option:Aptitude::CmdLine::Resolver-Debug
Default:false
Description: In command-line mode, if this option is true, aptitude will print
extremely verbose information while attempting to resolve broken dependencies.
As the name suggests, this option is primarily meant to aid in debugging the
problem resolver.
Option:Aptitude::CmdLine::Resolver-Dump
Default:
Description: In command-line mode, if it is necessary to resolve broken
dependencies and this option is set to the name of a writable file, the resolver
state will be dumped to this file before any calculations are undertaken.
Option:Aptitude::CmdLine::Resolver-Show-Steps
Default:false
Description: If this option is true, then a dependency solution will be
displayed as a sequence of resolutions of individual dependencies; for instance,
“wesnoth depends upon wesnoth-data (= 1.2.4-1) -> installing wesnoth-data 1.2.4-
1 (unstable)”. To toggle between the two display modes, press o at the prompt
“Accept this solution?”.
Option:Aptitude::CmdLine::Show-Deps
Default:false
Description: In command-line mode, if this option is true, aptitude will display
a brief summary of the dependencies (if any) relating to a package's state. This
is equivalent to the -D command-line option.
Option:Aptitude::CmdLine::Show-Size-Changes
Default:false
Description: In command-line mode, if this option is true, aptitude will display
the expected change in the amount of space used by each package. This is
equivalent to the -Z command-line option.
Option:Aptitude::CmdLine::Show-Summary
Default:no-summary
Description: This option sets the default value of the command-line argument --
show-summary. See the documentation of --show-summary for a list of the allowed
values of this option and their meanings.
Option:Aptitude::CmdLine::Show-Versions
Default:false
Description: In command-line mode, if this option is true, aptitude will display
the version of a package that is being installed or removed. This is equivalent
to the -V command-line option.
Option:Aptitude::CmdLine::Show-Why
Default:false
Description: In command-line mode, if this option is true, aptitude will display
the manually installed packages that require each automatically installed
package, or the manually installed packages that cause a conflict with each
automatically removed package. This is equivalent to the -W command-line option
and displays the same information you can access via aptitude why or by pressing
i in a package list.
Option:Aptitude::CmdLine::Version-Display-Format
Default:%c%a%M %p# %t %i
Description: This is a format string, as described in the section called
“Customizing how packages are displayed”, which is used to display the output of
aptitude versions. This is equivalent to the -F command-line option.
Option:Aptitude::CmdLine::Versions-Show-Package-Names
Default: Set to always, auto, or never to control when package names are
displayed in the output of aptitude versions. Equivalent to the command-line
option --show-package-names (see its documentation for more description of what
the values mean).
Option:Aptitude::Safe-Resolver::Show-Resolver-Actions
Default:false
Description: If this option is enabled, then when the “safe” dependency resolver
has been activated via --safe-resolver or because the command-line action is
safe-upgrade, it will display a summary of the actions taken by the resolver
before showing the installation preview. Equivalent to the command-line option -
-show-resolver-actions.
Option:Aptitude::Screenshot::IncrementalLoadLimit
Default:16384
Description: The minimum size in bytes at which aptitude will begin to display
screenshots incrementally. Below this size, screenshots will not appear until
they are fully downloaded.
Option:Aptitude::Screenshot::Cache-Max
Default:4194304
Description: The maximum number of bytes of screenshot data that aptitude will
store in memory for screenshots that are not currently being displayed. The
default is four megabytes.
Option:Aptitude::CmdLine::Simulate
Default:false
Description: This option is deprecated; use Aptitude::Simulate instead. In
command-line mode, causes aptitude to just display the actions that would be
performed (rather than actually performing them); in the visual interface,
causes aptitude to start in read-only mode regardless of whether you are root or
not. This is equivalent to the -s command-line option.
Option:Aptitude::CmdLine::Verbose
Default:0
Description: This controls how verbose the command-line mode of aptitude is.
Every occurrence of the -v command-line option adds 1 to this value.
Option:Aptitude::CmdLine::Visual-Preview
Default:false
Description: If this option is true, aptitude will enter its visual interface to
display the preview of an installation run and to download packages.
Option:Aptitude::Delete-Unused
Default:true
Description: If this option is true, automatically installed packages which are
no longer required will be automatically removed. For more information, see the
section called “Managing automatically installed packages”.
Option:Aptitude::Delete-Unused-Pattern
Default:
Description: Deprecated alias for Aptitude::Keep-Unused-Pattern. If Aptitude::
Keep-Unused-Pattern is unset or set to an empty string, the value of this
configuration option will override it. Otherwise, Aptitude::Delete-Unused-
Pattern is ignored.
Option:Aptitude::Display-Planned-Action
Default:true
Description: If this option is true, aptitude will display a preview screen
before actually carrying out the actions you have requested.
Option:Aptitude::Forget-New-On-Install
Default:false
Description: If this option is true, aptitude will clear the list of new
packages whenever you install, upgrade, or remove packages, as if you had issued
the command Actions → Forget new packages (f).
Option:Aptitude::Forget-New-On-Update
Default:false
Description: If this option is true, aptitude will clear the list of new
packages whenever the package list is updated, as if you had issued the command
Actions → Forget new packages (f).
Option:Aptitude::Get-Root-Command
Default:su:/bin/su
Description: This option sets the external command that aptitude will use to
switch to the root user (see the section called “Becoming root”). It has the
form protocol:command. protocol must be either su or sudo; it determines how
aptitude invokes the program when it wants to gain root privileges. If protocol
is su, then “command -c arguments” is used to become root; otherwise, aptitude
uses “command arguments”. The first word in command is the name of the program
that should be invoked; remaining words are treated as arguments to that
program.
Option:Aptitude::Ignore-Old-Tmp
Default:false
Description: Old versions of aptitude created a directory ~/.aptitude/.tmp which
is no longer necessary. If the directory exists and Aptitude::Ignore-Old-Tmp is
true, aptitude will ask you whether to remove this directory. This option is
automatically set to true after you reply. On the other hand, if the directory
does not exist, this option is set to false so that you will be notified if it
reappears.
Option:Aptitude::Ignore-Recommends-Important
Default:false
Description: In previous versions of aptitude, the setting Aptitude::Recommends-
Important caused recommendations to be installed automatically, the same way
that APT::Install-Recommends does today. If this option is set to false and
Aptitude::Recommends-Important is also set to false, aptitude will set APT::
Install-Recommends to false and set Aptitude::Ignore-Recommends-Important to
true on startup.
Option:Aptitude::Keep-Recommends
Default:false
Description: This is an obsolete option; use APT::AutoRemove::
RecommendsImportant instead. Setting this option to true has the same effect as
setting APT::AutoRemove::RecommendsImportant to true.
Option:Aptitude::Keep-Suggests
Default:false
Description: This is an obsolete option; use APT::AutoRemove::SuggestsImportant
instead. Setting this option to true has the same effect as setting APT::
AutoRemove::SuggestsImportant to true.
Option:Aptitude::Keep-Unused-Pattern
Default:
Description: If Aptitude::Delete-Unused is true, only unused packages which do
not match this pattern (see the section called “Search patterns”) will be
removed. If this option is set to an empty string (the default), all unused
packages will be removed.
Option:Aptitude::LockFile
Default:/var/lock/aptitude
Description: A file that will be fcntl-locked to ensure that at most one
aptitude process can modify the cache at once. In normal circumstances, you
should never need to modify this; it may be useful for debugging. Note: if
aptitude complains that it cannot acquire a lock, this is not because the lock
file needs to be deleted. fcntl locks are managed by the kernel and will be
destroyed when the program holding them terminates; failure to acquire the lock
means that another running program is using it!
Option:Aptitude::Localize-Log
Default:false
Description: If this option is enabled, aptitude will use the user's locale for
messages and dates in the log file; otherwise it is written in the "classic"
locale, to avoid having the log file written in different languages (depending
on the locales of the users running the program).
Option:Aptitude::Log
Default:/var/log/aptitude
Description: If this is set to a nonempty string, aptitude will log the package
installations, removals, and upgrades that it performs. If the value of
Aptitude::Log begins with a pipe character (ie, “|”), the remainder of its value
is used as the name of a command into which the log will be piped: for instance,
|mail -s 'Aptitude install run' root will cause the log to be emailed to root.
To log to multiple files or commands, you may set this option to a list of log
targets.
Option:Aptitude::Logging::File
Default:
Description: If this is set to a nonempty string, aptitude will write logging
messages to it; setting it to “-” causes logging messages to be printed to
standard output. This differs from the setting Aptitude::Log: that file is used
to log installations and removals, whereas this file is used to log program
events, errors, and debugging messages (if enabled). This option is equivalent
to the command-line argument --log-file. See also Aptitude::Logging::Levels.
Option:Aptitude::Logging::Levels
Default:(empty)
Description: This option is a group whose members control which log messages are
written. Each entry is either “level”, to set the global log level (the log
level of the root logger) to the given level, or “category:level”, where
category is the category of messages to modify (such as
aptitude.resolver.hints.match) and level is the lowest log level of messages in
that category that should be displayed. Valid log levels are “fatal”, “error”,
“warn”, “info”, “debug”, and “trace”. The command-line option --log-level can be
used to set or override any log level.
Option:Aptitude::Parse-Description-Bullets
Default:true
Description: If this option is enabled, aptitude will attempt to automatically
detect bulleted lists in package descriptions. This will generally improve how
descriptions are displayed, but it is not entirely backwards-compatible; some
descriptions might be formatted less attractively when this option is true than
when it is false.
Option:Aptitude::Pkg-Display-Limit
Default:
Description: The default filter applied to the package list; see the section
called “Search patterns” for details about its format.
Option:Aptitude::ProblemResolver::Allow-Break-Holds
Default:false
Description: If this option is set to true, the problem resolver will consider
breaking package holds or installing forbidden versions in order to resolve a
dependency. If it is set to false, these actions will be rejected by default,
although you can always enable them manually (see the section called “Resolving
Dependencies Interactively”).
Option:Aptitude::ProblemResolver::BreakHoldScore
Default:-300
Description: How much to reward or penalize solutions that change the state of a
held package or install a forbidden version. Note that unless Aptitude::
ProblemResolver::Allow-Break-Holds is set to true, the resolver will never break
a hold or install a forbidden version unless it has explicit permission from the
user.
Option:Aptitude::ProblemResolver::Break-Hold-Level
Default:50000
Description: The safety cost assigned to actions that break a hold set by the
user (by upgrading a held package or by installing a forbidden version of a
package). See the section called “Safety costs” for a description of safety
costs.
Option:Aptitude::ProblemResolver::BrokenScore
Default:-100
Description: How much to reward or penalize prospective solutions based on the
number of dependencies they break. For each dependency broken by a possible
solution, this many points are added to its score; typically this should be a
negative value.
Option:Aptitude::ProblemResolver::CancelRemovalScore
Default:-300
Description: How much weight the problem resolver should give to not remove or
purge a package requested to be removed or purged.
Option:Aptitude::ProblemResolver::DefaultResolutionScore
Default:400
Description: How much to reward or penalize prospective solutions based on how
many “default” resolutions for currently unsatisfied dependencies they install.
The default resolution is the resolution that “apt-get install” or the
“immediate dependency resolver” would pick. The score is only applied for
dependencies and recommendations whose targets are not currently installed.
Option:Aptitude::ProblemResolver::Discard-Null-Solution
Default:true
Description: If this option is true, aptitude will never suggest cancelling all
of your proposed actions in order to resolve a dependency problem.
Option:Aptitude::ProblemResolver::EssentialRemoveScore
Default:-100000
Description: How much to reward or penalize solutions that remove an Essential
package.
Option:Aptitude::ProblemResolver::Remove-Essential-Level
Default:60000
Description: The safety cost assigned to actions that remove an Essential
package. See the section called “Safety costs” for a description of safety
costs.
Option:Aptitude::ProblemResolver::ExtraScore
Default:0
Description: Any version of a package whose Priority is “extra” will have this
many points added to its score.
Option:Aptitude::ProblemResolver::FullReplacementScore
Default:500
Description: Removing a package and installing another package that fully
replaces it (i.e., conflicts with it, replaces it, and provides it) is assigned
this score.
Option:Aptitude::ProblemResolver::FutureHorizon
Default:50
Description: How many “steps” the resolver should run after finding the first
solution. Although aptitude attempts to generate better solutions before worse
solutions, sometimes it is unable to do so; this setting causes the resolver to
briefly continue searching for a better solution before displaying its results,
rather than stopping immediately after it finds the first solution.
Option:Aptitude::ProblemResolver::Hints
Default:(empty)
Description: This option is a group whose members are used to configure the
problem resolver. Each item in the group is a string describing an action that
should be applied to one or more packages. The syntax for each hint, and the
effect that hints have, may be found in the section called “Configuring resolver
hints”.
Option:Aptitude::ProblemResolver::ImportantScore
Default:4
Description: Any version of a package whose Priority is “important” will have
this many points added to its score.
Option:Aptitude::ProblemResolver::Infinity
Default:1000000
Description: A “maximum” score for potential solutions. If a set of actions has
a score worse than -Infinity, it will be discarded immediately.
Option:Aptitude::ProblemResolver::InstallScore
Default:-20
Description: How much weight the problem resolver should give to installing a
package, if the package is not already going to be installed.
Option:Aptitude::ProblemResolver::Keep-All-Level
Default:10000
Description: The safety cost assigned to the single solution that cancels all of
the actions selected by the user. See the section called “Safety costs” for a
description of safety costs.
Option:Aptitude::ProblemResolver::KeepScore
Default:0
Description: How much weight the problem resolver should give to keeping a
package in its current state, if that package is not already going to be kept in
its current state.
Option:Aptitude::ProblemResolver::NonDefaultScore
Default:-40
Description: How much weight the problem resolver should give to installing a
non-default version of the package (one that is not the current version and not
the “candidate version”).
Option:Aptitude::ProblemResolver::Non-Default-Level
Default:50000
Description: The safety cost assigned to actions that install non-default
versions of a package. For instance, if version 5 of a package is installed,
versions 6, 7, and 8 are available, and version 7 is the default version, then
versions 6 and 8 will be given a safety cost that is at least this high. See the
section called “Safety costs” for a description of safety costs.
Option:Aptitude::ProblemResolver::OptionalScore
Default:1
Description: Any version of a package whose Priority is “optional” will have
this many points added to its score.
Option:Aptitude::ProblemResolver::PreserveAutoScore
Default:0
Description: How much weight the problem resolver should give to preserving
automatic installations or removals.
Option:Aptitude::ProblemResolver::PreserveManualScore
Default:20
Description: How much weight the problem resolver should give to preserving
explicit user selections.
Option:Aptitude::ProblemResolver::RemoveObsoleteScore
Default:310
Description: How much weight the problem resolver should give to removing an
obsolete package (if it is not already marked for removal). It should at least
counter RemoveScore, because it will still be applied.
Option:Aptitude::ProblemResolver::RemoveScore
Default:-300
Description: How much weight the problem resolver should give to removing a
package (if it is not already marked for removal).
Option:Aptitude::ProblemResolver::Remove-Level
Default:10000
Description: The safety cost assigned to actions that remove a package. See the
section called “Safety costs” for a description of safety costs.
Option:Aptitude::ProblemResolver::RequiredScore
Default:8
Description: Any version of a package whose Priority is “required” will have
this many points added to its score.
Option:Aptitude::ProblemResolver::ResolutionScore
Default:50
Description: In addition to all other scoring factors, proposed solutions that
actually resolve all unsatisfied dependencies are awarded this many extra
points.
Option:Aptitude::ProblemResolver::Safe-Level
Default:10000
Description: The safety cost assigned to actions that install the default
version of a package, upgrade a package to its default version, or cancel
installing or upgrading a package. Solutions assigned this cost could be
generated by aptitude safe-upgrade. See the section called “Safety costs” for a
description of safety costs.
Option:Aptitude::ProblemResolver::SolutionCost
Default:safety,priority
Description: Describes how to determine the cost of a solution. See the section
called “Costs in the interactive dependency resolver” for a description of what
solution costs are, what they do, and the syntax used to specify them. If the
cost cannot be parsed, an error is issued and the default cost is used instead.
Option:Aptitude::ProblemResolver::StandardScore
Default:2
Description: Any version of a package whose Priority is “standard” will have
this many points added to its score.
Option:Aptitude::ProblemResolver::StepLimit
Default:5000
Description: The maximum number of “steps” which should be performed by the
problem resolver on each attempt to find a solution to a dependency problem.
Decreasing this number will make aptitude “give up” sooner; increasing it will
permit the search for a solution to consume much more time and memory before it
is aborted. Setting StepLimit to 0 will disable the problem resolver entirely.
The default value is large enough to accomodate commonly encountered situations,
while preventing aptitude from “blowing up” if an overly complicated problem is
encountered. (note: this applies only to command-line searches; in the visual
interface, the resolver will continue working until it reaches a solution)
Option:Aptitude::ProblemResolver::StepScore
Default:-10
Description: How much to reward or penalize prospective solutions based on their
length. For each action performed by a solution, these many points are added to
its score. The larger this value is, the more the resolver tends to stick with
its first choice rather than considering alternatives; this will cause it to
produce a solution more quickly, but the solution might be of slightly lower
quality than it would otherwise be.
Option:Aptitude::ProblemResolver::Trace-Directory
Default:
Description: If this value is set, then each time the problem resolver produces
a solution, a stripped-down version of the package state sufficient to reproduce
that solution is written to the given file. If Aptitude::ProblemResolver::Trace-
File is also set, the same information will also be written to the trace file.
Trace directories are more transparent than trace files, and are more suitable
for, e.g., including in source trees as test cases.
Option:Aptitude::ProblemResolver::Trace-File
Default:
Description: If this value is set, then each time the problem resolver produces
a solution, a stripped-down version of the package state sufficient to reproduce
that solution is written to the given file. If Aptitude::ProblemResolver::Trace-
Directory is also set, the same information will also be written to the trace
directory. A trace file is simply a compressed archive of a trace directory; it
will take less space than the trace directory and is suitable for transmission
over a network.
Option:Aptitude::ProblemResolver::UndoFullReplacementScore
Default:-500
Description: Installing a package and removing another package that fully
replaces it (i.e., conflicts with it, replaces it, and provides it) is assigned
this score.
Option:Aptitude::ProblemResolver::UnfixedSoftScore
Default:-200
Description: How much to reward or penalize leaving a Recommends relationship
unresolved. This should typically be less than RemoveScore, or aptitude will
tend to remove packages rather than leaving their Recommendations unfixed. See
the section called “Resolving Dependencies Interactively” for details.
Option:Aptitude::ProblemResolver::UpgradeScore
Default:30
Description: How much weight the problem resolver should give to upgrading (or
downgrading) a package to its candidate version, if the package was not already
going to be upgraded.
Option:Aptitude::Purge-Unused
Default:false
Description: If this option is true and Aptitude::Delete-Unused is also true,
then packages which are unused will be purged from the system, removing their
configuration files and perhaps other important data. For more information about
which packages are considered to be “unused”, see the section called “Managing
automatically installed packages”. THIS OPTION CAN CAUSE DATA LOSS! DO NOT
ENABLE IT UNLESS YOU KNOW WHAT YOU ARE DOING!
Option:Aptitude::Recommends-Important
Default:true
Description: This is an obsolete configuration option that has been superseded
by APT::Install-Recommends. On startup, aptitude will copy Aptitude::Recommends-
Important (if it exists) to APT::Install-Recommends and then clear Aptitude::
Recommends-Important in your user configuration file.
Option:Aptitude::Safe-Resolver::No-New-Installs
Default:false
Description: If this option is true, then when the “safe” dependency resolver
has been activated via --safe-resolver or by using the safe-upgrade command-line
action, the resolver will not be allowed to install packages that are not
currently installed.
Option:Aptitude::Safe-Resolver::No-New-Upgrades
Default:false
Description: If this option is enabled, then when the “safe” dependency resolver
has been activated via --safe-resolver or by using the safe-upgrade command-line
action, the resolver will not be allowed to resolve dependencies by upgrading
packages.
Option:Aptitude::Sections::Descriptions
Default:See $prefix/share/aptitude/section-descriptions
Description: This option is a group whose members define the descriptions
displayed for each section when using the “section” package hierarchy grouping
policy. Descriptions are assigned to section trees based on the last component
of the name: for instance, a member of this group named “games” will be used to
describe the Sections “games”, “non-free/games”, and “non-free/desktop/games”.
Within the text of section descriptions, the string “\n” will be replaced by a
line-break, and the string “''” will be replaced by a double-quote character.
Option:Aptitude::Sections::Top-Sections
Default:"main"; "contrib"; "non-free"; "non-US";
Description: A configuration group whose elements are the names of the top-level
archive sections. The “topdir”, “subdir”, and “subdirs” grouping policies use
this list to interpret Section fields: if the first path element of a package's
Section is not contained in this list, or if its Section has only one element,
then the package will be grouped using the first member of this list as its
first path element. For example, if the first member of Top-Sections is “main”,
then a package whose Section is “games/arcade” will be treated as if its Section
field were “main/games/arcade”.
Option:Aptitude::Simulate
Default:false
Description: In command-line mode, causes aptitude to just display the actions
that would be performed (rather than actually performing them); in the visual
interface, causes aptitude to start in read-only mode regardless of whether you
are root or not. This is equivalent to the -s command-line option.
Option:Aptitude::Spin-Interval
Default:500
Description: The number of milliseconds to delay in between updating the
“spinner” that appears while the problem resolver is running.
Option:Aptitude::Suggests-Important
Default:false
Description: This is an obsolete option; use APT::AutoRemove::SuggestsImportant
instead. Setting this option to true has the same effect as setting APT::
AutoRemove::SuggestsImportant to true.
Option:Aptitude::Suppress-Read-Only-Warning
Default:false
Description: If this option is false, aptitude will display a warning the first
time that you attempt to modify package states while aptitude is in read-only
mode.
Option:Aptitude::Theme
Default:
Description: The theme that aptitude should use; see the section called “Themes”
for more information.
Option:Aptitude::Track-Dselect-State
Default:true
Description: If this option is set to true, aptitude will attempt to detect when
a change to a package's state has been made using dselect or dpkg: for instance,
if you remove a package using dpkg, aptitude will not try to reinstall it. Note
that this may be somewhat buggy.
Option:Aptitude::UI::Advance-On-Action
Default:false
Description: If this option is set to true, changing a package's state (for
instance, marking it for installation) will cause aptitude to advance the
highlight to the next package in the current group.
Option:Aptitude::UI::Auto-Show-Reasons
Default:true
Description: If this option is set to true, selecting a package which is broken
or which appears to be causing other packages to be broken will cause the
information area to automatically display some reasons why the breakage might be
occuring.
Option:Aptitude::UI::Default-Grouping
Default:filter(missing),status,section(subdirs,passthrough),section(topdir)
Description: Sets the default grouping policy used for package lists. See the
section called “Customizing the package hierarchy” for additional information on
grouping policies.
Option:Aptitude::UI::Default-Package-View
Default:
Description: This option is a group whose members define the default layout of
aptitude's display. See the section called “Customizing the display layout” for
more information.
Option:Aptitude::UI::Default-Preview-Grouping
Default:action
Description: Sets the default grouping policy used for preview screens. See the
section called “Customizing the package hierarchy” for additional information on
grouping policies.
Option:Aptitude::UI::Default-Sorting
Default:name
Description: The default sorting policy of package views. See the section called
“Customizing how packages are sorted” for more information.
Option:Aptitude::UI::Description-Visible-By-Default
Default:true
Description: When a package list is first displayed, the information area (which
typically contains the long description of the current package) will be visible
if this option is true and hidden if it is false.
Option:Aptitude::UI::Exit-On-Last-Close
Default:true
Description: If this option is true, closing all the active views will quit
aptitude; otherwise, aptitude will not exit until you issue the command Actions
→ Quit (Q). See the section called “Working with multiple views” for more
information.
Option:Aptitude::UI::Fill-Text
Default:false
Description: If this option is true, aptitude will format descriptions so that
each line is exactly the width of the screen.
Option:Aptitude::UI::Flat-View-As-First-View
Default:false
Description: If this option is true, aptitude will display a flat view on
startup instead of the default view.
Option:Aptitude::UI::HelpBar
Default:true
Description: If this option is true, a line of information about important
keystrokes will be displayed at the top of the screen.
Option:Aptitude::UI::Incremental-Search
Default:true
Description: If this option is true, aptitude will perform “incremental”
searches: as you type the search pattern, it will search for the next package
matching what you have typed so far.
Option:Aptitude::UI::InfoAreaTabs
Default:false
Description: If this option is true, aptitude will display tabs at the top of
the information area (the pane at the bottom of the screen) describing the
different modes the area can be set to.
Option:Aptitude::UI::Keybindings
Default:
Description: This is a group whose members define the connections between
keystrokes and commands in aptitude. For more information, see the section
called “Customizing keybindings”.
Option:Aptitude::UI::Menubar-Autohide
Default:false
Description: If this option is set to true, the menu bar will be hidden while it
is not in use.
Option:Aptitude::UI::Minibuf-Download-Bar
Default:false
Description: If this option is set to true, aptitude will use a less obtrusive
mechanism to display the progress of downloads: a bar at the bottom of the
screen will appear which displays the current download status. While the
download is active, pressing q will abort it.
Option:Aptitude::UI::Minibuf-Prompts
Default:false
Description: If this option is true, some prompts (such as yes/no and multiple-
choice prompts) will be displayed at the bottom of the screen instead of in
dialog boxes.
Option:Aptitude::UI::New-Package-Commands
Default:true
Description: If this option is set to false, commands such as Package → Install
(+) will have the same deprecated behavior that they did in antique versions of
aptitude.
Option:Aptitude::UI::Package-Display-Format
Default:%c%a%M %p %Z %v %V
Description: This option controls the format string used to display packages in
package lists. For more information on format strings, see the section called
“Customizing how packages are displayed”.
Option:Aptitude::UI::Package-Header-Format
Default:%N %n @ %H #%B %u %o
Description: This option controls the format string used to display the header
line of package lists (ie, the line that appears between the package list and
the menu bar). For more information on format strings, see the section called
“Customizing how packages are displayed”.
Option:Aptitude::UI::Package-Status-Format
Default:%d
Description: This option controls the format string used to display the status
line of package lists (ie, the line that appears between the package list and
the information area). For more information on format strings, see the section
called “Customizing how packages are displayed”.
Option:Aptitude::UI::Pause-After-Download
Default:OnlyIfError
Description: If this option is true, aptitude will display a message after it
finishes downloading packages, asking you if you want to continue with the
installation. If it is OnlyIfError, a message will only be displayed if a
download failed. Otherwise, if the option is set to false, aptitude will
immediately proceed to the next screen after completing a download.
Option:Aptitude::UI::Preview-Limit
Default:
Description: The default filter applied to the preview screen; see the section
called “Search patterns” for details about its format.
Option:Aptitude::UI::Prompt-On-Exit
Default:true
Description: If this option is true, aptitude will display a confirmation prompt
before shutting down.
Option:Aptitude::UI::Styles
Default:
Description: This is a configuration group whose contents define what textual
styles aptitude uses to display information. For more information, see the
section called “Customizing text colors and styles”.
Option:Aptitude::UI::ViewTabs
Default:true
Description: If this option is set to false, aptitude will not display “tabs”
describing the currently active views at the top of the screen.
Option:Aptitude::Warn-Not-Root
Default:true
Description: If this option is true, aptitude will detect when you need root
privileges to do something, and ask you whether you want to switch to the root
account if you aren't root already. See the section called “Becoming root” for
more information.
Option:DebTags::Vocabulary
Default:/usr/share/debtags/vocabulary
Description: The location of the debtags vocabulary file; used to load in the
package tag metadata.
Option:Dir::Aptitude::state
Default:/var/lib/aptitude
Description: The directory in which aptitude's persistent state information is
stored.
Option:Quiet
Default:0
Description: This controls the quietness of the command-line mode. Setting it to
a higher value will disable more progress indicators.
Themes
A theme in aptitude is simply a collection of settings that “go together”.
Themes work by overriding the default values of options: if an option is not set
in the system configuration file or in your personal configuration file,
aptitude will use the setting from the current theme, if one is available,
before using the standard default value.
A theme is simply a named group under Aptitude::Themes; each configuration
option contained in the group will override the corresponding option in the
global configuration. For instance, if the Dselect theme is selected, the option
Aptitude::Themes::Dselect::Aptitude::UI::Package-Display-Format will override
the default value of the option Aptitude::UI::Package-Display-Format.
To select a theme, set the configuration option Aptitude::Theme to the name of
the theme; for instance,
Aptitude::Theme Vertical-Split;
The following themes are shipped with aptitude in /usr/share/aptitude/aptitude-
defaults:
Dselect
This theme makes aptitude look and behave more like the legacy dselect
package manager:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
--\ Installed Packages
--\ Priority required
--\ base - The Debian base system
c base base-file 3.0.16 3.0.16 Debian base system
miscellaneous fil
c base base-pass 3.5.7 3.5.7 Debian base system master
password a
c base bash 2.05b-15 2.05b-15 The GNU Bourne Again SHell
c base bsdutils 1:2.12-7 1:2.12-7 Basic utilities from 4.4BSD-
Lite
c base coreutils 5.0.91-2 5.0.91-2 The GNU core utilities
c base debianuti 2.8.3 2.8.3 Miscellaneous utilities
specific to
c base diff 2.8.1-6 2.8.1-6 File comparison utilities
base-files installed ; none
required
This package contains the basic filesystem hierarchy of a Debian system,
and
several important miscellaneous files, such as /etc/debian_version,
/etc/host.conf, /etc/issue, /etc/motd, /etc/profile, /etc/nsswitch.conf,
and
others, and the text of several common licenses in use on Debian systems.
Vertical-Split
This theme rearranges the display: instead of the current package's
description appearing underneath the package list, it is displayed to the
right of the package list. This theme is useful with very wide terminals,
and perhaps also when editing the built-in hierarchy of packages.
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
aptitude 0.2.14.1
--\ Installed Packages Modern computers support the
Advanced #
--\ admin - Administrative utilities Configuration and Power Interface
--\ main - The main Debian archive (ACPI) to allow intelligent power
i acpid 1.0.3-19 1.0.3-19 management on your system and to
query
i alien 8.44 8.44 battery and configuration status.
i anacron 2.3-9 2.3-9
i apt-show-vers 0.07 0.07 ACPID is a completely flexible,
totally
i A apt-utils 0.5.25 0.5.25 extensible daemon for delivering
ACPI
i apt-watch 0.3.2-2 0.3.2-2 events. It listens on a file
i aptitude 0.2.14.1-2 0.2.14.1-2 (/proc/acpi/event) and when an
event
i at 3.1.8-11 3.1.8-11 occurs, executes programs to
handle the
i auto-apt 0.3.20 0.3.20 event. The programs it executes
are
i cron 3.0pl1-83 3.0pl1-83 configured through a set of
i debconf 1.4.29 1.4.29 configuration files, which can be
i debconf-i18n 1.4.29 1.4.29 dropped into place by packages or
by
i A debootstrap 0.2.39 0.2.39 the admin.
i A deborphan 1.7.3 1.7.3
i debtags 0.16 0.16 In order to use this package you
need a
i A defoma 0.11.8 0.11.8 recent Kernel (=>2.4.7). This can
be
i discover 2.0.4-5 2.0.4-5 one including the patches on
Utilities for using ACPI power management
Playing Minesweeper
In case you get tired of installing and removing packages, aptitude includes a
version of the classic game “Minesweeper”. To start it, select Actions → Play
Minesweeper; the initial Minesweeper board will appear:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Minesweeper 10/10 mines 13 seconds
+--------+
| |
| |
| |
| |
| |
| |
| |
| |
+--------+
Within the rectangle that appears on the screen are hidden ten mines. Your goal
is to determine, through intuition, logic, and luck, where those mines are,
without setting any of them off! To do this, you must uncover all the squares
that do not contain mines; in doing so, you will learn important information
regarding which squares do contain mines. Beware, however: uncovering a square
that contains a mine will set it off, ending your game immediately!
To uncover a square (and find out whether a mine is hidden there), select the
square with the arrow keys and press Enter:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Minesweeper 10/10 mines 387 seconds
+--------+
| 2......|
| 2111...|
| 1...|
| 1111...|
|11...111|
|...113 |
|1122 |
| |
+--------+
As you can see, some of the hidden (blank) parts of the board have been revealed
in this screenshot. The squares containing a . are squares which are not next to
any mines; the numbers in the remaining squares indicate how many mines they are
next to.
If you think you know where a mine is, you can place a “flag” on it. To do this,
select the suspected square and press f. For instance, in the screenshot below,
I decided that the square on the left-hand side of the board looked
suspicious...
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Minesweeper 9/10 mines 961 seconds
+--------+
| 2......|
| 2111...|
| 1...|
|F1111...|
|11...111|
|...113 |
|1122 |
| |
+--------+
As you can see, an F appeared in the selected square. It is no longer possible
to uncover this square, even accidentally, until the flag is removed (by
pressing f again). Once you have placed flags on all the mines that are next to
a square (for instance, the squares labelled 1 next to the flag above), you can
“sweep” around the square. This is just a convenient shortcut to uncover all the
squares next to it (except those containing a flag, of course). For instance,
sweeping around the 1 above:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Minesweeper 9/10 mines 2290
seconds
+--------+
| 2......|
| 2111...|
|221 1...|
|F1111...|
|11...111|
|...113 |
|1122 |
| |
+--------+
Luckily (or was it luck?), my guess about the location of that mine was correct.
If I had been wrong, I would have lost immediately:
Actions Undo Package Search Options Views Help
f10: Menu ?: Help q: Quit u: Update g: Download/Install/Remove Pkgs
Minesweeper Minesweeper Lost in 2388
seconds
+--------+
|^2......|
|^2111...|
|221^1...|
|^1111...|
|11...111|
|...113^ |
|1122* ^ |
| ^ ^ ^|
+--------+
When you lose, the locations of all the mines are revealed: unexploded mines are
indicated by a caret symbol (^), and the one you “stepped on” is indicated by an
asterisk (*).
--------------------------------------------------------------------------------
[7]I am pleased to say that the number of requests of this sort fell off
precipitously following the initial publication of this Guide. It would be a
happy occurrence if there was a connection between the two events.
[8]This is sometimes referred to as an “install run”, even though you might be
upgrading or removing packages in addition to installing them.
[9]As noted above, it does not indicate that the packages in the archive are
secure, or even non-malicious; it merely shows that they are genuine.
[10] More precisely: they will be removed when there is no path via Depends,
PreDepends, or Recommends to them from a manually installed package. If APT::
AutoRemove::SuggestsImportant is true, a Suggests relationship is also enough to
keep a package installed.
[11]Or when immediate resolution is disabled.
[12]The package with the highest dpkg priority, not the package with the highest
apt pin priority.
[13]This limit was imposed because more complex cost structures could make it
difficult to optimize the resolver. Future versions of the program might remove
some of the restrictions if they turn out to be unnecessary.
[14] aptitude will only treat the comma as special if there is a second
argument, so (for instance) “?name(apt,itude)” searches for the string
“apt,itude” in the Name field of packages.
While this behavior is well-defined, it may be surprising; I recommend using
quoted strings for any pattern that contains characters that could have a
special meaning.
[15] Characters with a special meaning include: “+”, “-”, “.”, “(”, “)”, “|”, “
[”, “]”, “^”, “$”, and “?”. Note that some of these are also aptitude
metacharacters, so if you want to type (for instance) a literal “|”, it must be
double-escaped: “?description(\~|)” will match packages whose description
contains a vertical bar character (“|”).
[16] The backslash escapes \\, \n, and \t are also available.
[17] Astute readers will note that this is essentially a way to explicitly name
the variable in the λ-terms corresponding to the term. A typical term would have
the form “λ x . name-equals(x, pattern)”; giving this an explicit target makes x
visible in the search language.
[18] This is provided largely for symmetry with ?true.
[19]Currently tagging is not supported; this escape is for future use.
[20] On some terminals, a “yellow” background will actually come out brown.
Chapter 3. aptitude frequently asked questions
“What ... is your name?”
“I am Arthur, King of the Britons.”
“What ... is your quest?”
“I seek the Holy Grail!”
“What ... is the airspeed velocity of an unladen swallow?”
“What do you mean? An African or a European swallow?”
“Huh? I ... I don't kn---AAAAAUUUGGGHH!”
-- Monty Python and the Holy Grail
3.1. How can I find exactly one package by name?
3.2. How can I find broken packages?
3.3. I want to select text, why doesn't aptitude let me disable the mouse?
3.1. How can I find exactly one package by name?
As mentioned in the section called “Search patterns”, when you search for a
package by name, the text you enter is actually a regular expression. Thus, the
search pattern “^name$” will match only a package named name.
For instance, you can find apt (but not aptitude or synaptic) by entering
^apt$; you can find g++ (but not g++-2.95 or g++-3.0) by entering ^g\+\+$.
3.2. How can I find broken packages?
Use the command Search → Find Broken (b).
3.3. I want to select text, why doesn't aptitude let me disable the mouse?
Normally, you cannot select text in an xterm while a program running in that
terminal (such as aptitude) is using the mouse. However, you can override this
behavior and perform a selection by holding the Shift key down while you click
on the terminal.
Chapter 4. Credits
No-one remembers the singer. The song remains.
-- Terry Pratchett, The Last Hero
This section commemorates some of the people who have contributed to aptitude
over its lifetime.
IMG.alt.suffix = \[Note]] Note
This section is presently rather incomplete and will
likely be updated and expanded as time goes on (in
particular, there are many missing translation credits
due to the huge number of sources of translations
[21]). If you think you should be on this list, please
email <dburrows@debian.org> with an explanation of why
you think so.
Translations and internationalization
Brazilian translation
Andre Luis Lopes, Gustavo Silva
Chinese translation
Carlos Z.F. Liu
Czech translation
Miroslav Kure
Danish translation
Morten Brix Pedersen, Morten Bo Johansen
Dutch translation
Luk Claes
Finnish translation
Jaakko Kangasharju
French translation
Martin Quinson, Jean-Luc Coulon
German translation
Sebastian Schaffert, Erich Schubert, Sebastian Kapfer, Jens Seidel
Italian translation
Danilo Piazzalunga
Japanese translation
Yasuo Eto, Noritada Kobayashi
Lithuanian translation
Darius ?itkevicius
Polish translation
Michal Politowski
Portuguese translation
Nuno Sénica, Miguel Figueiredo
Norwegian translation
Håvard Korsvoll
Spanish translation
Jordi Malloch, Ruben Porras
Swedish translation
Daniel Nylander
Initial i18n patch
Masato Taruishi
i18n triaging and maintainence
Christian Perrier
Documentation
User's Manual
Daniel Burrows
Programming
Program design and implementation
Daniel Burrows
Support for the dpkg Breaks field
Ian Jackson, Michael Vogt
--------------------------------------------------------------------------------
[21] It should be possible to compile a fairly complete list of i18n
contributors based on the ChangeLog, its references to the Debian bug tracking
system, and the revision history of aptitude, but doing so will require a large
investment of time that is not currently available.
Command-line reference
--------------------------------------------------------------------------------
Table of Contents
aptitude — high-level interface to the package manager
aptitude-create-state-bundle — bundle the current aptitude state
aptitude-run-state-bundle — unpack an aptitude state bundle and invoke
aptitude on it
Name
aptitude — high-level interface to the package manager
Synopsis
aptitude [options...] { autoclean | clean | forget-new | keep-all | update }
aptitude [options...] { full-upgrade | safe-upgrade } [packages...]
aptitude [options...] { build-dep | build-depends | changelog | download |
forbid-version | hold | install | markauto | purge | reinstall | remove | show |
showsrc | source | unhold | unmarkauto | versions } packages...
aptitude extract-cache-subset output-directory packages...
aptitude [options...] search patterns...
aptitude [options...] { add-user-tag | remove-user-tag } tag packages...
aptitude [options...] { why | why-not } [patterns...] package
aptitude [-S fname] [ --autoclean-on-startup | --clean-on-startup | -i | -u ]
aptitude help
Description
aptitude is a text-based interface to the Debian GNU/Linux package system.
It allows the user to view the list of packages and to perform package
management tasks such as installing, upgrading, and removing packages. Actions
may be performed from a visual interface or from the command-line.
Command-line actions
The first argument which does not begin with a hyphen (“-”) is considered to be
an action that the program should perform. If an action is not specified on the
command-line, aptitude will start up in visual mode.
The following actions are available:
install
Install one or more packages. The packages should be listed after the
“install” command; if a package name contains a tilde character (“~”) or a
question mark (“?”), it will be treated as a search pattern and every
package matching the pattern will be installed (see the section “Search
Patterns” in the aptitude reference manual).
To select a particular version of the package, append “=version” to the
package name: for instance, “aptitude install apt=0.3.1”. Similarly, to
select a package from a particular archive, append “/archive” to the
package name: for instance, “aptitude install apt/experimental”. You
cannot specify both an archive and a version for a package.
Not every package listed on the command line has to be installed; you can
tell aptitude to do something different with a package by appending an
“override specifier” to the name of the package. For example, aptitude
remove wesnoth+ will install wesnoth, not remove it. The following
override specifiers are available:
package+
Install package.
If the package was not installed, it is marked as manually
installed, and the dependencies newly installed are marked with the
automatic flag. If the package or the dependencies were already
installed, the automatic flag is preserved. See the section about
automatic installations in the documentation for more information.
package+M
Install package and immediately mark it as automatically installed
(note that if nothing depends on package, this will cause it to be
immediately removed).
package-
Remove package.
package_
Purge package: remove it and all its associated configuration and
data files.
package=
Place package on hold: cancel any active installation, upgrade, or
removal, and prevent this package from being automatically upgraded
in the future.
package:
Keep package at its current version: cancel any installation,
removal, or upgrade. Unlike “hold” (above) this does not prevent
automatic upgrades in the future.
package&M
Mark package as having been automatically installed.
package&m
Mark package as having been manually installed.
package&BD
Install the build-dependencies of a package.
As a special case, “install” with no arguments will act on any stored/
pending actions.
IMG.alt.suffix Note
= \[Note]]
Once you enter Y at the final confirmation prompt, the “install” command
will modify aptitude's stored information about what actions to perform.
Therefore, if you issue (e.g.) the command “aptitude install foo bar” on
packages previously uninstalled, and then the installation fails once
aptitude has started downloading and installing packages, you will need to
run “aptitude remove foo bar” to go back to the previous state (and possibly
undo installations or upgrades to other packages that were affected by the
“install” action).
remove, purge, reinstall
These commands are the same as “install”, but apply the named action to
all packages given on the command line for which it is not overridden.
For instance, “aptitude remove '~ndeity'” will remove all packages whose
name contains “deity”.
build-depends, build-dep
Satisfy the build-dependencies of a package. Each package name may be a
source package, in which case the build dependencies of that source
package are installed; otherwise, binary packages are found in the same
way as for the “install” command, and the build-dependencies of the source
packages that build those binary packages are satisfied.
If the command-line parameter --arch-only is present, only architecture-
dependent build dependencies (i.e., not Build-Depends-Indep or Build-
Conflicts-Indep) will be obeyed.
markauto, unmarkauto
Mark packages as automatically installed or manually installed,
respectively. Packages are specified in exactly the same way as for the
“install” command. For instance, “aptitude markauto '~slibs'” will mark
all packages in the “libs” section as having been automatically installed.
For more information on automatically installed packages, see the section
“Managing Automatically Installed Packages” in the aptitude reference
manual.
hold, unhold, keep
Mark packages to be on hold, remove this property, or set to keep in the
current state. Packages are specified in exactly the same way as for the
“install” command. For instance, “aptitude hold '~e^dpkg$'” will mark all
packages coming from the source package “dpkg” to be on hold.
The difference between hold and keep is that hold will cause a package to
be ignored by future safe-upgrade or full-upgrade commands, while keep
merely cancels any scheduled actions on the package. unhold will allow a
package to be upgraded by future safe-upgrade or full-upgrade commands,
without otherwise altering its state.
keep-all
Cancels all scheduled actions on all packages; any packages whose sticky
state indicates an installation, removal, or upgrade will have this sticky
state cleared.
forget-new
Forgets all internal information about what packages are “new” (equivalent
to pressing “f” when in visual mode).
This command accepts package names or patterns as arguments. If the string
contains a tilde character (“~”) or a question mark (“?”), it will be
treated as a search pattern and every package matching the pattern will be
considered (see the section “Search Patterns” in the aptitude reference
manual).
forbid-version
Forbid a package from being upgraded to a particular version, while
allowing automatic upgrades to future versions. This is useful for example
to avoid a known broken version of a package, without having to set and
clear manual holds.
By default, aptitude will select the forbidden version to be the one which
the package would normally be upgraded (the candidate version). This may
be overridden by appending “=version” to the package name: for instance,
“aptitude forbid-version vim=1.2.3.broken-4”.
To revert the action, “aptitude install package” will remove the ban. To
remove the forbidden version without installing the candidate version, the
current version should be appended: “install package=version”.
update
Updates the list of available packages from the apt sources (this is
equivalent to “apt-get update”)
safe-upgrade
Upgrades installed packages to their most recent version. Installed
packages will not be removed unless they are unused (see the section
“Managing Automatically Installed Packages” in the aptitude reference
manual). Packages which are not currently installed may be installed to
resolve dependencies unless the --no-new-installs command-line option is
supplied.
If no packages are listed on the command line, aptitude will attempt to
upgrade every package that can be upgraded. Otherwise, aptitude will
attempt to upgrade only the packages which it is instructed to upgrade.
The packages can be extended with suffixes in the same manner as arguments
to aptitude install, so you can also give additional instructions to
aptitude here; for instance, aptitude safe-upgrade bash dash- will attempt
to upgrade the bash package and remove the dash package.
It is sometimes necessary to remove one package in order to upgrade
another; this command is not able to upgrade packages in such situations.
Use the full-upgrade command to upgrade as many packages as possible.
full-upgrade
Upgrades installed packages to their most recent version, removing or
installing packages as necessary. It also installs new Essential or
Required packages. This command is less conservative than safe-upgrade and
thus more likely to perform unwanted actions. However, it is capable of
upgrading packages that safe-upgrade cannot upgrade.
If no packages are listed on the command line, aptitude will attempt to
upgrade every package that can be upgraded. Otherwise, aptitude will
attempt to upgrade only the packages which it is instructed to upgrade.
The packages can be extended with suffixes in the same manner as arguments
to aptitude install, so you can also give additional instructions to
aptitude here; for instance, aptitude full-upgrade bash dash- will attempt
to upgrade the bash package and remove the dash package.
IMG.alt.suffix = \[Note]] Note
This command was originally named dist-upgrade
for historical reasons, and aptitude still
recognizes dist-upgrade as a synonym for full-
upgrade.
search
Searches for packages matching one of the patterns supplied on the command
line. All packages which match any of the given patterns will be
displayed; for instance, “aptitude search '~N' edit” will list all “new”
packages and all packages whose name contains “edit”. For more information
on search patterns, see the section “Search Patterns” in the aptitude
reference manual.
IMG.alt.suffix Note
= \[Note]]
In the example above, “aptitude search '~N' edit” has two arguments after
search and thus is searching for two patterns: “~N” and “edit”. As described
in the search pattern reference, a single pattern composed of two sub-
patterns separated by a space (such as “~N edit”) matches only if both
patterns match. Thus, the command “aptitude search '~N edit'” will only show
“new” packages whose name contains “edit”.
Unless you pass the -F option, the output of aptitude search will look
something like this:
i apt - Advanced front-end for dpkg
pi apt-build - frontend to apt to build, optimize
and in
cp apt-file - APT package searching utility -
- command-
ihA raptor-utils - Raptor RDF Parser utilities
Each search result is listed on a separate line. The first character of
each line indicates the current state of the package: the most common
states are p, meaning that no trace of the package exists on the system,
c, meaning that the package was deleted but its configuration files remain
on the system, i, meaning that the package is installed, and v, meaning
that the package is virtual. The second character indicates the stored
action (if any; otherwise a blank space is displayed) to be performed on
the package, with the most common actions being i, meaning that the
package will be installed, d, meaning that the package will be deleted,
and p, meaning that the package and its configuration files will be
removed. If the third character is A, the package was automatically
installed.
For a complete list of the possible state and action flags, see the
section “Accessing Package Information” in the aptitude reference guide.
To customize the output of search, see the command-line options -F and --
sort.
show
Displays detailed information about one or more packages. If a package
name contains a tilde character (“~”) or a question mark (“?”), it will be
treated as a search pattern and all matching packages will be displayed
(see the section “Search Patterns” in the aptitude reference manual).
If the verbosity level is 1 or greater (i.e., at least one -v is present
on the command-line), information about all versions of the package is
displayed. Otherwise, information about the “candidate version” (the
version that “aptitude install” would download) is displayed.
You can display information about a different version of the package by
appending =version to the package name; you can display the version from a
particular archive or release by appending /archive or /release to the
package name: for instance, /unstable or /sid. If either of these is
present, then only the version you request will be displayed, regardless
of the verbosity level.
If the verbosity level is 1 or greater, the package's architecture,
compressed size, filename, and md5sum fields will be displayed. If the
verbosity level is 2 or greater, the select version or versions will be
displayed once for each archive in which they are found.
showsrc
Displays detailed information about one or more source packages.
This is a thin wrapper over apt(8).
source
Downloads one or more source packages.
This is a thin wrapper over apt(8).
versions
Displays the versions of the packages listed on the command-line.
$ aptitude versions wesnoth
p 1:1.4.5-
1 100
p 1:1.6.5-1 unstable
500
p 1:1.7.14-1 experimental
1
Each version is listed on a separate line. The leftmost three characters
indicate the current state, planned state (if any), and whether the
package was automatically installed; for more information on their
meanings, see the documentation of aptitude search. To the right of the
version number you can find the releases from which the version is
available, and the pin priority of the version.
If a package name contains a tilde character (“~”) or a question mark
(“?”), it will be treated as a search pattern and all matching versions
will be displayed (see the section “Search Patterns” in the aptitude
reference manual). This means that, for instance, aptitude versions '~i'
will display all the versions that are currently installed on the system
and nothing else, not even other versions of the same packages.
$ aptitude versions '~nexim4-daemon-light'
Package exim4-daemon-light:
i 4.71-
3 100
p 4.71-4 unstable
500
Package exim4-daemon-light-dbg:
p 4.71-4 unstable
500
If the input is a search pattern, or if more than one package's versions
are to be displayed, aptitude will automatically group the output by
package, as shown above. You can disable this via --group-by=none, in
which case aptitude will display a single list of all the versions that
were found and automatically include the package name in each output line:
$ aptitude versions --group-by=none '~nexim4-daemon-light'
i exim4-daemon-light 4.71-
3 100
p exim4-daemon-light 4.71-4 unstable
500
p exim4-daemon-light-dbg 4.71-4 unstable
500
To disable the package name, pass --show-package-names=never:
$ aptitude versions --show-package-names=never --group-by=none '~nexim4-
daemon-light'
i 4.71-
3 100
p 4.71-4 unstable
500
p 4.71-4 unstable
500
In addition to the above options, the information printed for each version
can be controlled by the command-line option -F. The order in which
versions are displayed can be controlled by the command-line option --
sort. To prevent aptitude from formatting the output into columns, use --
disable-columns.
add-user-tag, remove-user-tag
Adds a user tag to or removes a user tag from the selected group of
packages. If a package name contains a tilde (“~”) or question mark (“?”),
it is treated as a search pattern and the tag is added to or removed from
all the packages that match the pattern (see the section “Search Patterns”
in the aptitude reference manual).
User tags are arbitrary strings associated with a package. They can be
used with the ?user-tag(tag) search term, which will select all the
packages that have a user tag matching tag.
why, why-not
Explains the reason that a particular package should or cannot be
installed on the system.
This command searches for packages that require or conflict with the given
package. It displays a sequence of dependencies leading to the target
package, along with a note indicating the installed state of each package
in the dependency chain:
$ aptitude why kdepim
i nautilus-data Recommends nautilus
i A nautilus Recommends desktop-base (>= 0.2)
i A desktop-base Suggests gnome | kde | xfce4 | wmaker
p kde Depends kdepim (>= 4:3.4.3)
The command why finds a dependency chain that installs the package named
on the command line, as above. Note that the dependency that aptitude
produced in this case is only a suggestion. This is because no package
currently installed on this computer depends on or recommends the kdepim
package; if a stronger dependency were available, aptitude would have
displayed it.
In contrast, why-not finds a dependency chain leading to a conflict with
the target package:
$ aptitude why-not textopo
i ocaml-core Depends ocamlweb
i A ocamlweb Depends tetex-extra | texlive-latex-extra
i A texlive-latex-extra Conflicts textopo
If one or more patterns are present (in addition to the mandatory last
argument, which should be a valid package name), then aptitude will begin
its search at these patterns. That is, the first package in the chain it
prints to explain why package is or is not installed, will be a package
matching the pattern in question. The patterns are considered to be
package names unless they contain a tilde character (“~”) or a question
mark (“?”), in which case they are treated as search patterns (see the
section “Search Patterns” in the aptitude reference manual).
If no patterns are present, then aptitude will search for dependency
chains beginning at manually installed packages. This effectively shows
the packages that have caused or would cause a given package to be
installed.
IMG.alt.suffix Note
= \[Note]]
aptitude why does not perform full dependency resolution; it only displays
direct relationships between packages. For instance, if A requires B, C
requires D, and B and C conflict, “aptitude why-not D” will not produce the
answer “A depends on B, B conflicts with C, and D depends on C”.
By default aptitude outputs only the “most installed, strongest, tightest,
shortest” dependency chain. That is, it looks for a chain that only
contains packages which are installed or will be installed; it looks for
the strongest possible dependencies under that restriction; it looks for
chains that avoid ORed dependencies and Provides; and it looks for the
shortest dependency chain meeting those criteria. These rules are
progressively weakened until a match is found.
If the verbosity level is 1 or more, then all the explanations aptitude
can find will be displayed, in inverse order of relevance. If the
verbosity level is 2 or more, a truly excessive amount of debugging
information will be printed to standard output.
This command returns 0 if successful, 1 if no explanation could be
constructed, and -1 if an error occurred.
clean
Removes all previously downloaded .deb files from the package cache
directory (usually /var/cache/apt/archives).
autoclean
Removes any cached packages which can no longer be downloaded. This allows
you to prevent a cache from growing out of control over time without
completely emptying it.
changelog
Downloads and displays the Debian changelog for each of the given source
or binary packages.
By default, the changelog for the version which would be installed with
“aptitude install” is downloaded. You can select a particular version of a
package by appending =version to the package name; you can select the
version from a particular archive or release by appending /archive or /
release to the package name (for instance, /unstable or /sid).
download
Downloads the .deb file for the given package to the current directory.
This is a thin wrapper over apt(8).
extract-cache-subset
Copy the apt configuration directory (/etc/apt) and a subset of the
package database to the specified directory. If no packages are listed,
the entire package database is copied; otherwise only the entries
corresponding to the named packages are copied. Each package name may be a
search pattern, and all the packages matching that pattern will be
selected (see the section “Search Patterns” in the aptitude reference
manual). Any existing package database files in the output directory will
be overwritten.
Dependencies in binary package stanzas will be rewritten to remove
references to packages not in the selected set.
help
Displays a brief summary of the available commands and options.
Options
The following options may be used to modify the behavior of the actions
described above. Note that while all options will be accepted for all commands,
some options don't apply to particular commands and will be ignored by those
commands.
--add-user-tag tag
For full-upgrade, safe-upgrade, forbid-version, hold, install, keep-all,
markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto:
add the user tag tag to all packages that are installed, removed, or
upgraded by this command as if with the add-user-tag command.
--add-user-tag-to tag,pattern
For full-upgrade, safe-upgrade, forbid-version, hold, install, keep-all,
markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto:
add the user tag tag to all packages that match pattern as if with the
add-user-tag command. The pattern is a search pattern as described in the
section “Search Patterns” in the aptitude reference manual.
For instance, aptitude safe-upgrade --add-user-tag-to "new-
installs,?action(install)" will add the tag new-installs to all the
packages installed by the safe-upgrade command.
--allow-new-upgrades
When the safe resolver is being used (i.e., --safe-resolver was passed,
the action is safe-upgrade, or Aptitude::Always-Use-Safe-Resolver is set
to true), allow the dependency resolver to install upgrades for packages
regardless of the value of Aptitude::Safe-Resolver::No-New-Upgrades.
--allow-new-installs
Allow the safe-upgrade command to install new packages; when the safe
resolver is being used (i.e., --safe-resolver was passed, the action is
safe-upgrade, or Aptitude::Always-Use-Safe-Resolver is set to true), allow
the dependency resolver to install new packages. This option takes effect
regardless of the value of Aptitude::Safe-Resolver::No-New-Installs.
--allow-untrusted
Install packages from untrusted sources without prompting. You should only
use this if you know what you are doing, as it could easily compromise
your system's security.
--disable-columns
This option causes aptitude search and aptitude versions to output their
results without any special formatting. In particular: normally aptitude
will add whitespace or truncate search results in an attempt to fit its
results into vertical “columns”. With this flag, each line will be formed
by replacing any format escapes in the format string with the
corresponding text; column widths will be ignored.
For instance, the first few lines of output from “aptitude search -F '%p
%V' --disable-columns libedataserver” might be:
disksearch 1.2.1-3
hp-search-mac 0.1.3
libbsearch-ruby 1.5-5
libbsearch-ruby1.8 1.5-5
libclass-dbi-abstractsearch-perl 0.07-2
libdbix-fulltextsearch-perl 0.73-10
As in the above example, --disable-columns is often useful in combination
with a custom display format set using the command-line option -F.
This corresponds to the configuration option Aptitude::CmdLine::Disable-
Columns.
-D, --show-deps
For commands that will install or remove packages (install, full-upgrade,
etc), show brief explanations of automatic installations and removals.
This corresponds to the configuration option Aptitude::CmdLine::Show-Deps.
-d, --download-only
Download packages to the package cache as necessary, but do not install or
remove anything. By default, the package cache is stored in /var/cache/
apt/archives.
This corresponds to the configuration option Aptitude::CmdLine::Download-
Only.
-F format, --display-format format
Specify the format which should be used to display output from the search
and versions commands. For instance, passing “%p %v %V” for format will
display a package's name, followed by its currently installed version and
its candidate version (see the section “Customizing how packages are
displayed” in the aptitude reference manual for more information).
The command-line option --disable-columns is often useful in combination
with -F.
For search, this corresponds to the configuration option Aptitude::
CmdLine::Package-Display-Format; for versions, this corresponds to the
configuration option Aptitude::CmdLine::Version-Display-Format.
-f
Try hard to fix the dependencies of broken packages, even if it means
ignoring the actions requested on the command line.
This corresponds to the configuration item Aptitude::CmdLine::Fix-Broken.
--full-resolver
When package dependency problems are encountered, use the default “full”
resolver to solve them. Unlike the “safe” resolver activated by --safe-
resolver, the full resolver will happily remove packages to fulfill
dependencies. It can resolve more situations than the safe algorithm, but
its solutions are more likely to be undesirable.
This option can be used to force the use of the full resolver even when
Aptitude::Always-Use-Safe-Resolver is true.
--group-by grouping-mode
Control how the versions command groups its output. The following values
are recognized:
* archive to group packages by the archive they occur in (“stable”,
“unstable”, etc). If a package occurs in several archives, it will be
displayed in each of them.
* auto to group versions by their package unless there is exactly one
argument and it is not a search pattern.
* none to display all the versions in a single list without any grouping.
* package to group versions by their package.
* source-package to group versions by their source package.
* source-version to group versions by their source package and source
version.
This corresponds to the configuration option Aptitude::CmdLine::Versions-
Group-By.
-h, --help
Display a brief help message. Identical to the help action.
--log-file=file
If file is a nonempty string, log messages will be written to it, except
that if file is “-”, the messages will be written to standard output
instead. If this option appears multiple times, the last occurrence is the
one that will take effect.
This does not affect the log of installations that aptitude has performed
(/var/log/aptitude); the log messages written using this configuration
include internal program events, errors, and debugging messages. See the
command-line option --log-level to get more control over what gets logged.
This corresponds to the configuration option Aptitude::Logging::File.
--log-level=level, --log-level=category:level
--log-level=level causes aptitude to only log messages whose level is
level or higher. For instance, setting the log level to error will cause
only messages at the log levels error and fatal to be displayed; all
others will be hidden. Valid log levels (in descending order) are off,
fatal, error, warn, info, debug, and trace. The default log level is warn.
--log-level=category:level causes messages in category to only be logged
if their level is level or higher.
--log-level may appear multiple times on the command line; the most
specific setting is the one that takes effect, so if you pass --log-
level=aptitude.resolver:fatal and --log-
level=aptitude.resolver.hints.match:trace, then messages in
aptitude.resolver.hints.parse will only be printed if their level is
fatal, but all messages in aptitude.resolver.hints.match will be printed.
If you set the level of the same category two or more times, the last
setting is the one that will take effect.
This does not affect the log of installations that aptitude has performed
(/var/log/aptitude); the log messages written using this configuration
include internal program events, errors, and debugging messages. See the
command-line option --log-file to change where log messages go.
This corresponds to the configuration group Aptitude::Logging::Levels.
--log-resolver
Set some standard log levels related to the resolver, to produce logging
output suitable for processing with automated tools. This is equivalent to
the command-line options --log-level=aptitude.resolver.search:trace --log-
level=aptitude.resolver.search.tiers:info.
--no-new-installs
Prevent safe-upgrade from installing any new packages; when the safe
resolver is being used (i.e., --safe-resolver was passed or Aptitude::
Always-Use-Safe-Resolver is set to true), forbid the dependency resolver
from installing new packages. This option takes effect regardless of the
value of Aptitude::Safe-Resolver::No-New-Installs.
This mimics the historical behavior of apt-get upgrade.
--no-new-upgrades
When the safe resolver is being used (i.e., --safe-resolver was passed or
Aptitude::Always-Use-Safe-Resolver is set to true), forbid the dependency
resolver from installing upgrades for packages regardless of the value of
Aptitude::Safe-Resolver::No-New-Upgrades.
--no-show-resolver-actions
Do not display the actions performed by the “safe” resolver, overriding
any configuration option or earlier --show-resolver-actions.
-O order, --sort order
Specify the order in which output from the search and versions commands
should be displayed. For instance, passing “installsize” for order will
list packages in order according to their size when installed (see the
section “Customizing how packages are sorted” in the aptitude reference
manual for more information).
Prepending the order keyword with a tilde character (~) reverses the order
from ascending to descending.
The default sort order is name,version.
-o key=value
Set a configuration file option directly; for instance, use -o Aptitude::
Log=/tmp/my-log to log aptitude's actions to /tmp/my-log. For more
information on configuration file options, see the section “Configuration
file reference” in the aptitude reference manual.
-P, --prompt
Always display a prompt before downloading, installing or removing
packages, even when no actions other than those explicitly requested will
be performed.
This corresponds to the configuration option Aptitude::CmdLine::Always-
Prompt.
--purge-unused
If Aptitude::Delete-Unused is set to “true” (its default), then in
addition to removing each package that is no longer required by any
installed package, aptitude will also purge them, removing their
configuration files and perhaps other important data. For more information
about which packages are considered to be “unused”, see the section
“Managing Automatically Installed Packages” in the aptitude reference
manual. THIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS YOU KNOW
WHAT YOU ARE DOING!
This corresponds to the configuration option Aptitude::Purge-Unused.
-q[=n], --quiet[=n]
Suppress all incremental progress indicators, thus making the output
loggable. This may be supplied multiple times to make the program quieter,
but unlike apt-get, aptitude does not enable -y when -q is supplied more
than once.
The optional =n may be used to directly set the amount of quietness (for
instance, to override a setting in /etc/apt/apt.conf); it causes the
program to behave as if -q had been passed exactly n times.
-R, --without-recommends
Do not treat recommendations as dependencies when installing new packages
(this overrides settings in /etc/apt/apt.conf and ~/.aptitude/config).
Packages previously installed due to recommendations will not be removed.
This corresponds to the pair of configuration options APT::Install-
Recommends and APT::AutoRemove::RecommendsImportant.
-r, --with-recommends
Treat recommendations as dependencies when installing new packages (this
overrides settings in /etc/apt/apt.conf and ~/.aptitude/config).
This corresponds to the configuration option APT::Install-Recommends
--remove-user-tag tag
For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all,
markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto:
remove the user tag tag from all packages that are installed, removed, or
upgraded by this command as if with the add-user-tag command.
--remove-user-tag-from tag,pattern
For full-upgrade, safe-upgrade forbid-version, hold, install, keep-all,
markauto, unmarkauto, purge, reinstall, remove, unhold, and unmarkauto:
remove the user tag tag from all packages that match pattern as if with
the remove-user-tag command. The pattern is a search pattern as described
in the section “Search Patterns” in the aptitude reference manual.
For instance, aptitude safe-upgrade --remove-user-tag-from "not-
upgraded,?action(upgrade)" will remove the not-upgraded tag from all
packages that the safe-upgrade command is able to upgrade.
-s, --simulate
In command-line mode, print the actions that would normally be performed,
but don't actually perform them. This does not require root privileges. In
the visual interface, always open the cache in read-only mode regardless
of whether you are root.
This corresponds to the configuration option Aptitude::Simulate.
--safe-resolver
When package dependency problems are encountered, use a “safe” algorithm
to solve them. This resolver attempts to preserve as many of your choices
as possible; it will never remove a package or install a version of a
package other than the package's default candidate version. It is the same
algorithm used in safe-upgrade; indeed, aptitude --safe-resolver full-
upgrade is equivalent to aptitude safe-upgrade. Because safe-upgrade
always uses the safe resolver, it does not accept the --safe-resolver
flag.
This option is equivalent to setting the configuration variable Aptitude::
Always-Use-Safe-Resolver to true.
--schedule-only
For commands that modify package states, schedule operations to be
performed in the future, but don't perform them. You can execute scheduled
actions by running aptitude install with no arguments. This is equivalent
to making the corresponding selections in visual mode, then exiting the
program normally.
For instance, aptitude --schedule-only install evolution will schedule the
evolution package for later installation.
--show-package-names when
Controls when the versions command shows package names. The following
settings are allowed:
* always: display package names every time that aptitude versions runs.
* auto: display package names when aptitude versions runs if the output is
not grouped by package, and either there is a pattern-matching argument
or there is more than one argument.
* never: never display package names in the output of aptitude versions.
This option corresponds to the configuration item Aptitude::CmdLine::
Versions-Show-Package-Names.
--show-resolver-actions
Display the actions performed by the “safe” resolver and by safe-upgrade.
When executing the command safe-upgrade or when the option --safe-resolver
is present, aptitude will display a summary of the actions performed by
the resolver before printing the installation preview. This is equivalent
to the configuration option Aptitude::Safe-Resolver::Show-Resolver-
Actions.
--show-summary[=MODE]
Changes the behavior of “aptitude why” to summarize each dependency chain
that it outputs, rather than displaying it in long form. If this option is
present and MODE is not “no-summary”, chains that contain Suggests
dependencies will not be displayed: combine --show-summary with -v to see
a summary of all the reasons for the target package to be installed.
MODE can be any one of the following:
1. no-summary: don't show a summary (the default behavior if --show-
summary is not present).
2. first-package: display the first package in each chain. This is the
default value of MODE if it is not present.
3. first-package-and-type: display the first package in each chain,
along with the strength of the weakest dependency in the chain.
4. all-packages: briefly display each chain of dependencies leading to
the target package.
5. all-packages-with-dep-versions: briefly display each chain of
dependencies leading to the target package, including the target
version of each dependency.
This option corresponds to the configuration item Aptitude::CmdLine::Show-
Summary; if --show-summary is present on the command-line, it will
override Aptitude::CmdLine::Show-Summary.
Example 12. Usage of --show-summary
--show-summary used with -v to display all the reasons a package is
installed:
$ aptitude -v --show-summary why foomatic-db
Packages requiring foomatic-db:
cupsys-driver-gutenprint
foomatic-db-engine
foomatic-db-gutenprint
foomatic-db-hpijs
foomatic-filters-ppds
foomatic-gui
kde
printconf
wine
$ aptitude -v --show-summary=first-package-and-type why foomatic-db
Packages requiring foomatic-db:
[Depends] cupsys-driver-gutenprint
[Depends] foomatic-db-engine
[Depends] foomatic-db-gutenprint
[Depends] foomatic-db-hpijs
[Depends] foomatic-filters-ppds
[Depends] foomatic-gui
[Depends] kde
[Depends] printconf
[Depends] wine
$ aptitude -v --show-summary=all-packages why foomatic-db
Packages requiring foomatic-db:
cupsys-driver-gutenprint D: cups-driver-gutenprint D: cups R: foomatic-
filters R: foomatic-db-engine D: foomatic-db
foomatic-filters-ppds D: foomatic-filters R: foomatic-db-engine D:
foomatic-db
kde D: kdeadmin R: system-config-printer-kde D: system-config-printer R:
hal-cups-utils D: cups R: foomatic-filters R: foomatic-db-engine D:
foomatic-db
wine D: libwine-print D: cups-bsd R: cups R: foomatic-filters R:
foomatic-db-engine D: foomatic-db
foomatic-db-engine D: foomatic-db
foomatic-db-gutenprint D: foomatic-db
foomatic-db-hpijs D: foomatic-db
foomatic-gui D: python-foomatic D: foomatic-db-engine D: foomatic-db
printconf D: foomatic-db
$ aptitude -v --show-summary=all-packages-with-dep-versions why foomatic-
db
Packages requiring foomatic-db:
cupsys-driver-gutenprint D: cups-driver-gutenprint (>= 5.0.2-4) D: cups
(>= 1.3.0) R: foomatic-filters (>= 4.0) R: foomatic-db-engine (>= 4.0) D:
foomatic-db (>= 20090301)
foomatic-filters-ppds D: foomatic-filters R: foomatic-db-engine (>= 4.0)
D: foomatic-db (>= 20090301)
kde D: kdeadmin (>= 4:3.5.5) R: system-config-printer-kde (>= 4:4.2.2-1)
D: system-config-printer (>= 1.0.0) R: hal-cups-utils D: cups R: foomatic-
filters (>= 4.0) R: foomatic-db-engine (>= 4.0) D: foomatic-db (>=
20090301)
wine D: libwine-print (= 1.1.15-1) D: cups-bsd R: cups R: foomatic-
filters (>= 4.0) R: foomatic-db-engine (>= 4.0) D: foomatic-db (>=
20090301)
foomatic-db-engine D: foomatic-db
foomatic-db-gutenprint D: foomatic-db
foomatic-db-hpijs D: foomatic-db
foomatic-gui D: python-foomatic (>= 0.7.9.2) D: foomatic-db-engine D:
foomatic-db (>= 20090301)
printconf D: foomatic-db
--show-summary used to list a chain on one line:
$ aptitude --show-summary=all-packages why aptitude-gtk libglib2.0-data
Packages requiring libglib2.0-data:
aptitude-gtk D: libglib2.0-0 R: libglib2.0-data
-t release, --target-release release
Set the release from which packages should be installed. For instance,
“aptitude -t experimental ...” will install packages from the experimental
distribution unless you specify otherwise.
This will affect the default candidate version of packages according to
the rules described in apt_preferences(5).
This corresponds to the configuration item APT::Default-Release.
-V, --show-versions
Show which versions of packages will be installed.
This corresponds to the configuration option Aptitude::CmdLine::Show-
Versions.
-v, --verbose
Causes some commands (for instance, show) to display extra information.
This may be supplied multiple times to get more and more information.
This corresponds to the configuration option Aptitude::CmdLine::Verbose.
--version
Display the version of aptitude and some information about how it was
compiled.
--visual-preview
When installing or removing packages from the command line, instead of
displaying the usual prompt, start up the visual interface and display its
preview screen.
-W, --show-why
In the preview displayed before packages are installed or removed, show
which manually installed package requires each automatically installed
package. For instance:
$ aptitude --show-why install mediawiki
...
The following NEW packages will be installed:
libapache2-mod-php5{a} (for mediawiki) mediawiki php5{a} (for
mediawiki)
php5-cli{a} (for mediawiki) php5-common{a} (for mediawiki)
php5-mysql{a} (for mediawiki)
When combined with -v or a non-zero value for Aptitude::CmdLine::Verbose,
this displays the entire chain of dependencies that lead each package to
be installed. For instance:
$ aptitude -v --show-why install libdb4.2-dev
The following NEW packages will be installed:
libdb4.2{a} (libdb4.2-dev D: libdb4.2) libdb4.2-dev
The following packages will be REMOVED:
libdb4.4-dev{a} (libdb4.2-dev C: libdb-dev P<- libdb-dev)
This option will also describe why packages are being removed, as shown
above. In this example, libdb4.2-dev conflicts with libdb-dev, which is
provided by libdb-dev.
This argument corresponds to the configuration option Aptitude::CmdLine::
Show-Why and displays the same information that is computed by aptitude
why and aptitude why-not.
-w width, --width width
Specify the display width which should be used for output from the search
and versions commands (in the command line).
By default and when the output is seen directly in a terminal, the
terminal width is used. When the output is redirected or piped, a very
large "unlimited" line width is used, and this option is ignored.
This corresponds to the configuration option Aptitude::CmdLine::Package-
Display-Width
-y, --assume-yes
When a yes/no prompt would be presented, assume that the user entered
“yes”. In particular, suppresses the prompt that appears when installing,
upgrading, or removing packages. Prompts for “dangerous” actions, such as
removing essential packages, will still be displayed. This option
overrides -P.
This corresponds to the configuration option Aptitude::CmdLine::Assume-
Yes.
-Z
Show how much disk space will be used or freed by the individual packages
being installed, upgraded, or removed.
This corresponds to the configuration option Aptitude::CmdLine::Show-Size-
Changes.
The following options apply to the visual mode of the program, but are primarily
for internal use; you generally won't need to use them yourself.
--autoclean-on-startup
Deletes old downloaded files when the program starts (equivalent to
starting the program and immediately selecting Actions → Clean obsolete
files). You cannot use this option and “--clean-on-startup”, “-i”, or “-u”
at the same time.
--clean-on-startup
Cleans the package cache when the program starts (equivalent to starting
the program and immediately selecting Actions → Clean package cache). You
cannot use this option and “--autoclean-on-startup”, “-i”, or “-u” at the
same time.
-i
Displays a download preview when the program starts (equivalent to
starting the program and immediately pressing “g”). You cannot use this
option and “--autoclean-on-startup”, “--clean-on-startup”, or “-u” at the
same time.
-S fname
Loads the extended state information from fname instead of the standard
state file.
-u
Begins updating the package lists as soon as the program starts. You
cannot use this option and “--autoclean-on-startup”, “--clean-on-startup”,
or “-i” at the same time.
Environment
HOME
If $HOME/.aptitude exists, aptitude will store its configuration file in
$HOME/.aptitude/config. Otherwise, it will look up the current user's home
directory using getpwuid(2) and place its configuration file there.
PAGER
If this environment variable is set, aptitude will use it to display
changelogs when “aptitude changelog” is invoked. If not set, it defaults
to more.
TMP
If TMPDIR is unset, aptitude will store its temporary files in TMP if that
variable is set. Otherwise, it will store them in /tmp.
TMPDIR
aptitude will store its temporary files in the directory indicated by this
environment variable. If TMPDIR is not set, then TMP will be used; if TMP
is also unset, then aptitude will use /tmp.
Files
/var/lib/aptitude/pkgstates
The file in which stored package states and some package flags are stored.
/etc/apt/apt.conf, /etc/apt/apt.conf.d/*, ~/.aptitude/config
The configuration files for aptitude. ~/.aptitude/config overrides /etc/
apt/apt.conf. See apt.conf(5) for documentation of the format and contents
of these files.
See also
apt-get(8), apt(8), /usr/share/doc/aptitude/html/lang/index.html from the
package aptitude-doc-lang
--------------------------------------------------------------------------------
Name
aptitude-create-state-bundle — bundle the current aptitude state
Synopsis
aptitude-create-state-bundle [options...] output-file
Description
IMG.alt.suffix = \[Note]] Note
This command is mostly for internal use and bug
reporting in exceptional cases, it is not intended for
end-users under normal circumstances.
aptitude-create-state-bundle produces a compressed archive storing the files
that are required to replicate the current package archive state. The following
files and directories are included in the bundle:
* $HOME/.aptitude
* /var/lib/aptitude
* /var/lib/apt
* /var/cache/apt/*.bin
* /etc/apt
* /var/lib/dpkg/status
The output of this program can be used as an argument to aptitude-run-state-
bundle(1).
Options
--force-bzip2
Override the autodetection of which compression algorithm to use. By
default, aptitude-create-state-bundle uses bzip2(1) if it is available,
and gzip(1) otherwise. Passing this option forces the use of bzip2 even if
it doesn't appear to be available.
--force-gzip
Override the autodetection of which compression algorithm to use. By
default, aptitude-create-state-bundle uses bzip2(1) if it is available,
and gzip(1) otherwise. Passing this option forces the use of gzip even if
bzip2 is available.
--help
Print a brief usage message, then exit.
--print-inputs
Instead of creating a bundle, display a list of the files and directories
that the program would include if it generated a bundle.
File format
The bundle file is simply a tar(1) file compressed with bzip2(1) or gzip(1),
with each of the input directory trees rooted at “.”.
See also
aptitude-run-state-bundle(1), aptitude(8), apt(8)
--------------------------------------------------------------------------------
Name
aptitude-run-state-bundle — unpack an aptitude state bundle and invoke aptitude
on it
Synopsis
aptitude-run-state-bundle [options...] input-file [ program [arguments...]]
Description
IMG.alt.suffix = \[Note]] Note
This command is mostly for internal use and bug
reporting in exceptional cases, it is not intended for
end-users under normal circumstances.
aptitude-run-state-bundle unpacks the given aptitude state bundle created by
aptitude-create-state-bundle(1) to a temporary directory, invokes program on it
with the supplied arguments, and removes the temporary directory afterwards. If
program is not supplied, it defaults to aptitude(8).
Options
The following options may occur on the command-line before the input file.
Options following the input file are presumed to be arguments to aptitude.
--append-args
Place the options that give the location of the state bundle at the end of
the command line when invoking program, rather than at the beginning (the
default is to place options at the beginning).
--help
Display a brief usage summary.
--prepend-args
Place the options that give the location of the state bundle at the
beginning of the command line when invoking program, overriding any
previous --append-args (the default is to place options at the beginning).
--no-clean
Do not remove the unpacked state directory after running aptitude. You
might want to use this if, for instance, you are debugging a problem that
appears when aptitude's state file is modified. When aptitude finishes
running, the name of the state directory will be printed so that you can
access it in the future.
This option is enabled automatically by --statedir.
--really-clean
Delete the state directory after running aptitude, even if --no-clean or -
-statedir was supplied.
--statedir
Instead of treating the input file as a state bundle, treat it as an
unpacked state bundle. For instance, you can use this to access the state
directory that was created by a prior run with --no-clean.
--unpack
Unpack the input file to a temporary directory, but don't actually run
aptitude.
See also
aptitude-create-state-bundle(1), aptitude(8), apt(8)
|