Re: one package altering other package's postrm
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Guillem Jover writes ("Re: one package altering other package's postrm"):
>> As mentioned before, just add a versioned Breaks against the cron
>> package not supporting that, do not mangle its maintainer scripts.
> ...
>> If using current apt with APT::Get::Purge=true or --purge, or the
>> aptitude TUI and marking cron for purge, the conflicting package will
>> get purged before the other package is even in the picture.
> Isn't this combination rather dangerous ? The result would appear to
> be that switching to systemd-cron would first purge the cron package,
> discarding any local changes to /etc/crontab (and other config files
> owned by cron).
I think Apt::Get::Purge=true or --purge during upgrades is rather
dangerous inherently. One is basically telling apt "full steam ahead, and
destroy anything too slow to keep up, no looking back!" I much prefer a
multi-step process of apt upgrade, apt-get autoremove, and then purging
removed packages some time (days) later after I've had some time to notice
broken things.
If you use --purge during upgrades, I think you should expect some things
to break and for your local configurations to occasionally get wiped out.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: