Package: aptitude Version: 0.8.10-1 Severity: normal Steps to reproduce:
- Have an apt source for "deb http://repo.steampowered.com/steam/ precise steam" (plus some way to mark it as trusted) - Observe how the steam-launcher package offered by that repository is presented in the TUI (It has Section: games, is in a component/archive area named steam, and comes from Origin: Valve Software LLC, Label: Steam) (Any other archive with similar structure can probably reproduce this, that's just the first one I thought of) Expected result: - The package is presented as though it was in no particular archive component, because aptitude presumably doesn't know what policies the origin "Valve Software LLC" uses when marking packages with a Section and putting them in a component Actual result: --\ New Packages (1) --\ games Games, toys, and fun programs (1) --\ main The main Debian archive (1) p steam-launcher <none> 1.0.0.54 I assume this is because aptitude sees the unadorned Section: games (as opposed to Section: steam/games or similar) and bases its UI on that. Compare with how aptitude presents the packages in Section: local/games generated by game-data-packager, which seems fine: --\ games Games, toys, and fun programs (77) --- non-free Programs which are not free software (15) --\ local (62) i blakestone-v30-data 54 <none> (This does not make any particular statement about the status of 'local'). synaptic has (or used to have) some mechanism for recognising Debian 'main' packages when run on Debian, and supported Ubuntu packages (for some definition, perhaps main or main + restricted) when run on Ubuntu. Ideally aptitude would behave similarly, perhaps by knowing which Origin can be (or at least claims to be) the Debian main archive. I suspect that if aptitude had the requested behaviour, it would have to present packages that are no longer available via apt (Obsolete and Locally Created) as having an unknown status, rather than being from "The main Debian archive". This seems more correct - if I built a package locally, it might be Free Software (or not) but is certainly not from "The main Debian archive". Regards, smcv -- Package-specific info: Terminal: xterm-256color $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.8.10 Compiler: g++ 7.2.0 Compiled against: apt version 5.0.2 NCurses version 6.0 libsigc++ version: 2.10.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20171125 cwidget version: 0.5.17 Apt version: 5.0.2 aptitude linkage: linux-vdso.so.1 (0x00007ffc1ee90000) libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 (0x00007f48f4147000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007f48f3f17000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f48f3ced000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x00007f48f3ae6000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x00007f48f37eb000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f48f34e3000) libboost_iostreams.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x00007f48f32cb000) libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x00007f48f30b2000) libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x00007f48f2eae000) libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 (0x00007f48f2aa3000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f48f2885000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f48f2506000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f48f21f3000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f48f1fdc000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f48f1c39000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f48f1a23000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f48f1809000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f48f15f9000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f48f13d3000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f48f11c1000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f48f0fa3000) /lib64/ld-linux-x86-64.so.2 (0x00007f48f4b05000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f48f0d9f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f48f0b97000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f48f0992000) -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.8.10-1 ii libapt-pkg5.0 1.6~alpha5 ii libboost-filesystem1.62.0 1.62.0+dfsg-4+b2 ii libboost-iostreams1.62.0 1.62.0+dfsg-4+b2 ii libboost-system1.62.0 1.62.0+dfsg-4+b2 ii libc6 2.25-2 ii libcwidget3v5 0.5.17-6 ii libgcc1 1:7.2.0-16 ii libncursesw5 6.0+20171125-1 ii libsigc++-2.0-0v5 2.10.0-1 ii libsqlite3-0 3.21.0-1 ii libstdc++6 7.2.0-16 ii libtinfo5 6.0+20171125-1 ii libxapian30 1.4.5-1 Versions of packages aptitude recommends: ii libparse-debianchangelog-perl 1.2.0-12 ii sensible-utils 0.0.11 Versions of packages aptitude suggests: ii apt-xapian-index 0.49 ii aptitude-doc-en [aptitude-doc] 0.8.10-1 pn debtags <none> ii tasksel 3.42 -- no debconf information
