apt/apt-private, branch 2.9.33Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.332025-03-09T12:55:23ZPrint --solver 3.0 explanation if both internal and it failed2025-03-09T12:55:23ZJulian Andres Klodejulian.klode@canonical.com2025-03-09T12:55:23Zurn:sha1:6c112f9860c1730237029f4e23d40bf658d73704
This can provide useful additional context.
To avoid updating the whole test suite for it, introduce a new
option `quiet::NoSolver3Explanation` and set it by default. All
the other tests that assert output will already have matching
tests for --solver 3.0 with the correct messages asserted, it
makes no sense to duplicate them.
Evaluate and fall back to the 3.0 solver2025-03-09T12:33:53ZJulian Andres Klodejulian.klode@canonical.com2025-02-18T12:06:32Zurn:sha1:935a9ab334e55a29363f45e7de6338c47337e806
Always run the 3.0 solver after the internal solver. If the internal
solver failed, and the 3.0 solver did not, use the 3.0 result.
If 3.0 solver failed or produced a worse result than the internal
solver, write an apport crash dump.
We exclude situations which we now the solver can't handle, i.e.
removals are forbidden and you requested removals, and stuff like
that.
string{=> _view} flNotDir(string{=> _view}). Configuration::{Cnd,}Set(Value: string{=> _view})2025-02-14T18:45:12Zнабnabijaczleweli@nabijaczleweli.xyz2025-01-23T19:50:39Zurn:sha1:729a5c8f4fb8c841497d26170e1a47c41617ecd9edit-sources: don't force .list2025-02-07T19:57:10ZChristopher Bockchristopher@bocki.com2025-02-06T18:08:38Zurn:sha1:1df0230b388441245e96ce7b58bd2cad59d53511modernize-sources: Avoid opening /dev/stdout for simulate2025-02-04T15:15:17ZJulian Andres Klodejulian.klode@canonical.com2025-02-04T15:14:13Zurn:sha1:ddfb32fe72ec38f27e0fa2f012c43ade421bdbd8
/dev/stdout may not exist, so let's instead just reference
the std::cout stream.
Reported-by: h01ger on IRC
Measure BootSize as integer2025-02-03T12:40:37ZJulian Andres Klodejulian.klode@canonical.com2025-02-03T12:19:12Zurn:sha1:452586e84ad54ca23dee399bf9809c49e7171f36
I don't know why I used a double here this is awkward.
Also support debian-ports modernization2025-02-02T00:41:21ZSamuel Thibaultsthibault@debian.org2025-02-02T00:37:55Zurn:sha1:f9ff99d699209aa97ba788bad86a15313751c230
That just needs using '-' to replace spaces in Origin to get the keyring file name.
Make notices about .list sources without signed-by less obnoxious2025-01-28T18:48:47ZJulian Andres Klodejulian.klode@canonical.com2025-01-27T16:34:45Zurn:sha1:4059a1544323b945a81e5ef0faea4a3b109f36bfapt: Introduce the modernize-sources command2025-01-28T18:47:00ZJulian Andres Klodejulian.klode@canonical.com2025-01-27T14:51:24Zurn:sha1:9d7a660611e9e134cd6d74a594bde59cad77c8d8
This handles rewriting .list entries to .sources ones; the
only options handled are
- signed-by => Signed-By
- trusted => Trusted
The options to specify architectures, check-valid-until, etc.
are not supported as they are not exposed in the code. We
probably should refactor the parser at some point so we can
actually read the parsed entry rather than the abstract objects
we create from it.
This can be improved further:
- Keyrings from /etc/apt/trusted.gpg.d should be moved to
/etc/apt/keyrings.
- automatic detection by trying to verify using each keyring
in trusted.gpg.d until we find the right one and then using
that for Signed-By rather than leave some sources empty.
apt-secure manual page is in manual section 82025-01-28T18:45:23ZAndreas Rönnquistgusnan@debian.org2025-01-23T14:33:55Zurn:sha1:a725a4af76fed9c4f06188f022f9a8f28ff333bd