Package: apt-listchanges Version: 4.6 Dear developer,
A couple of days ago I noticed that the service to initialize apt-listchanges database seemed to hang (the service wouldn't stop).
I tried to remove the database and initialize it again properly, but again it seemed to run for hours.
Running it with --debug showed that as soon as the load average exceeds 1, it waits for 10 seconds. After killing most of my desktop apps, it still waited most of the time, itself increasing load average and entering some kind of loop.
After disabling the culprit block (lines 42-46) it did its job in about 3 minutes.
I think this safeguard is counter-productive, since as I described, the script itself increases load average and can easily create a loop and lock itself in it.
If you don't wish to remove it, another idea is to make MAX_LOAD_AVG equal to the number of CPUs, which would be a lot more realistic (a 12-core CPU is far from being overloaded when the load average reaches 1).
Regards, -- Raphaël Halimi
