apt/debian, branch 3.1.7 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=3.1.7 2025-10-02T14:50:16Z Release 3.1.7 2025-10-02T14:50:16Z Julian Andres Klode jak@debian.org 2025-10-02T14:50:16Z urn:sha1:be54b990682a16e0add08c3468e5114ec4e4f844 Release 3.1.6 2025-09-26T17:06:16Z Julian Andres Klode jak@debian.org 2025-09-26T17:05:46Z urn:sha1:ddfd20559b66e2878cc256d7da068d5058453a53 Release 3.1.5 2025-08-26T19:03:09Z Julian Andres Klode jak@debian.org 2025-08-26T19:03:09Z urn:sha1:23af056d0dd21acaeae14d02e416a8696ebd69af Release 3.1.4 2025-08-11T15:28:12Z Julian Andres Klode jak@debian.org 2025-08-11T15:28:12Z urn:sha1:8d9ea25bc7e908f25baee2448e80f6bbd820173f Release 3.1.3 2025-06-24T17:32:09Z Julian Andres Klode jak@debian.org 2025-06-24T17:32:09Z urn:sha1:95ff30f3976d73b3dcfd60ab7518130252efbb79 Release 3.1.2 2025-06-10T19:16:43Z Julian Andres Klode jak@debian.org 2025-06-10T19:16:43Z urn:sha1:63919b628a9bf386136f708f06c1a8a7d4f09fca Release 3.1.1 2025-06-10T16:06:26Z Julian Andres Klode jak@debian.org 2025-06-10T16:05:29Z urn:sha1:f9b5f49fe6030fc028bc93debf856d1ae75ca7ab Release 3.1.0 2025-05-19T17:14:52Z Julian Andres Klode jak@debian.org 2025-05-19T17:14:11Z urn:sha1:5bfea97d7b3c6f4fcaa56c24d6f3591b1862b86b Include everything in our pkg-config autopkgtest 2025-05-19T17:06:31Z David Kalnischkies david@kalnischkies.de 2022-12-30T17:56:19Z urn:sha1:aea3d9cf573a17400d4c1d399f410cb87ec58c6d GCC defaults to C++17 currently, but our library users could be on other (newer/older) standard still e.g. by explicit request, so to avoid accidentally breaking them the pkg-config-test is adapted to include all of our public headers as a smoke test for if you can build an application against our library in a certain C++ standard. The test script is also adapted to be runnable outside of autopkgtest like in our CI or manually. Introduce apt why, apt why-not 2025-05-19T15:20:09Z Julian Andres Klode jak@debian.org 2025-05-19T12:17:23Z urn:sha1:7724d170751b3dc1717ba7a08881437cf7151996 These are implemented somewhat differently from aptitudes why and why-not commands: They produce the actual solver trace for why a particular decision has been taken. For the why-not case, we need to explicitly discover our specified package, as if nothing else depends on it in our graph, it would otherwise always be undiscovered and conflicts not detected (see e.g. level-3 in the test).