How shall I report a bug in the .deb packaging itself?
Alexandre Detiste
alexandre.detiste at gmail.com
Tue Dec 22 08:37:08 UTC 2015
Le mardi 22 décembre 2015, 00:35:25 Robie Basak a écrit :
> I had always assumed that this is the risk you take by using autoremove
> and thus you need to pay attention to what you autoremove, which is for
> example why unattended-upgrades is sensible by not doing it by default.
Excepted that unattended-upgrades is changeing this behaviour right
now because some users got their /boot filled with many differents kernel images
over the time.
https://github.com/mvo5/unattended-upgrades/commit/25ff94915a9fc99058839d16761cf029896cbe05
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093
*) "apt-get autoremove" should always be safe;
one can use apt-mark manual to pin pakcages
*) "apt-get remove $(deborphan)" is more dangerous; and should be done manually;
and then one can also build fake empty packages with equivs to register some
-libs or -devel packages as needed by a local application.
Greets,
Alexandre
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20151222/41c89450/attachment.sig>
More information about the Ubuntu-devel-discuss
mailing list