apt/test/integration/test-kernel-helper-autoremove, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2024-04-24T13:16:21ZDrop sudo-related envvars in testing framework2024-04-24T13:16:21ZDavid Kalnischkiesdavid@kalnischkies.de2024-04-23T16:13:46Zurn:sha1:9c06578c37ff77b70b9d978d48528df13e13530f
Our autoremoval-advertisment is modified by SUDO_USER as if the current
apt call was made with sudo it seems a good idea to show the ad with
sudo as well. That is annoying for our tests through as normally the
tests are run locally or by autopkgtest without sudo, but in Gitlab CI
we use it (to run our tests as user… as we are already root) and so
individual tests had to deal with this.
That is annoying and really not needed as we can have our autoremove
test check that this ad gets displayed the right way and ignore it the
rest of the time.
Only protect two kernels, not last installed one2022-04-07T11:19:52ZJulian Andres Klodejulian.klode@canonical.com2022-04-06T11:51:08Zurn:sha1:824651ded0bcf8603e9b508860b8fe5a68fc53ff
The kernel autoremoval algorithm was written to accomodate
for Ubuntu's boot partition sizing, which was written to
accomodate 3 kernels - 2 installed ones + a new one being
unpacked.
It seems that when the algorithm was designed, it was overlooked
that it actually kept 3 kernels.
LP: #1968154
Determine autoremovable kernels at run-time2021-01-04T09:46:48ZJulian Andres Klodejulian.klode@canonical.com2020-12-17T12:24:56Zurn:sha1:04085f46dea9a95dd86123ac00187a63cc4ba2c0
Our kernel autoremoval helper script protects the currently booted
kernel, but it only runs whenever we install or remove a kernel,
causing it to protect the kernel that was booted at that point in time,
which is not necessarily the same kernel as the one that is running
right now.
Reimplement the logic in C++ such that we can calculate it at run-time:
Provide a function to produce a regular expression that matches all
kernels that need protecting, and by changing the default root set
function in the DepCache to make use of that expression.
Note that the code groups the kernels by versions as before, and then
marks all kernel packages with the same version.
This optimized version inserts a virtual package $kernel into the cache
when building it to avoid having to iterate over all packages in the
cache to find the installed ones, significantly improving performance at
a minor cost when building the cache.
LP: #1615381
Widen regular expressions for versioned kernel packages2020-01-30T15:58:23ZJulian Andres Klodejulian.klode@canonical.com2019-04-15T07:40:20Zurn:sha1:4f9c58d25ff52fbb69cd3439fc1484bea47e1566
Since we append a concrete kernel version to each pattern, and then
anchor the pattern, let's just pick any package starting with a
kernel name (linux-, kfreebsd-, gnumach-), and not worry about
linux-headers, linux-tools, etc specifically, as they'll be caught
by the generic pattern.
LP: #1607845
support COLUMNS environment variable in apt tools2017-11-19T17:26:19ZDavid Kalnischkiesdavid@kalnischkies.de2017-11-18T02:48:59Zurn:sha1:3f8664036e63d2a2d58120ab6c1e8a0a09937c71
apt usually gets the width of the window from the terminal or failing
that has a default value, but especially for testing it can be handy
to control the size as you can't be sure that variable sized content
will always be linebreaked as expected in the testcases.
Lower-case uname -r output in kernel autoremove helper2016-08-26T20:24:24ZJulian Andres Klodejak@debian.org2016-08-24T14:28:47Zurn:sha1:15134a8e5458fc634482386f1fd2acbccc3ac892
This is needed on FreeBSD which has versions like 11.0-RC1,
otherwise the tests would fail.
Add kernels with "+" in the package name to APT::NeverAutoRemove2016-07-08T06:44:05ZAndrew Pattersonandrew.patterson@hpe.com2016-07-06T19:40:16Zurn:sha1:130176bcb6ce65c98d5692196c55cc18b4c210e0
Escape "+" in kernel package names when generating APT::NeverAutoRemove
list so it is not treated as a regular expression meta-character.
[Changed by David Kalnischkies: let test actually test the change]
Closes: #830159
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
suggest 'apt autoremove' to get right of unneeded packages2015-11-04T17:04:01ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-16T10:54:14Zurn:sha1:73fe49f9b4748eddb5a2dad4f0abb51a8f63564c
The bugreport is more conservative in asking for a conditional, but
given that this is a message intended to be read by users to be run by
users we should suggest using a command intended to be used by users.
And while we are at, add sudo to the message – conditional of course.
Closes: 801571
tests: try to support spaces in TMPDIR2015-09-14T13:22:19ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-14T00:26:13Zurn:sha1:63c7141275c8c5c0f6e60f5242785e50cabaf2a0
Not all tests work yet, most notable the cdrom tests, but those require
changes in libapt itself to have a proper fix and what we have fixed so
far is good enough progress for now.
Git-Dch: Ignore