Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=master 2017-07-12T09:09:00Z 2017-07-12T09:09:00Z Apollon Oikonomopoulos apoikos@debian.org 2017-07-12T07:41:58Z urn:sha1:5caf6ee2db1ebf294fb0412fddf7d187840cce70 Commit d7c92411dc1f4c6be098d1425f9c1c075e0c2154 parses the Components section of (In)Release and attempts to detect the distribution's supported components. While doing so, it handles component names with slashes in a special manner, assuming that the actual component is only the part after the final slash. This is done to handle security.debian.org, which usually appears in sources.list as follows: deb http://s.d.o/debian-security stretch/updates main contrib non-free while the actual release file has: Codename: stretch Components: updates/main updates/contrib updates/non-free While this special handing on APTs part indeed works for debian-security, it emits spurious warnings on repositories that actually use slashes in the component names *and* appear so in sources.list. We fix this by adding both component versions (whole and final part) to the SupportedComponents array. Closes: #868127 2017-06-26T21:31:15Z David Kalnischkies david@kalnischkies.de 2017-05-28T17:18:30Z urn:sha1:d7c92411dc1f4c6be098d1425f9c1c075e0c2154 If we couldn't find an entry for a Sources file we would generate an error while for a Packages file we would silently skip it due to assuming it is missing because it is empty. We can do better by checking if the repository declares that it supports a component we want to get the file from and if not say so and hint at the user making a typo. An example were this helps is mozilla.debian.net which dropped the firefox-aurora component (as upstream did) meaning no upgrades until the user notices manually that the repository doesn't provide packages anymore. With this commit warnings are raised hopefully causing the user to investigate what is wrong (sooner).