> > Fixing a couple of nasty bugs discovered late,
> Yes, due to handling of a new binary package that you had migrated into
> bullseye the day before that wasn't allowed anymore exactly to avoid
> this class of bugs.
Agreed, this was something that several users had asked for and that we, the
screen team, agreed on making, but nobody had the time till I was able to do
it, yes, it was late on the cycle, but I think we can get it right before
releasing.
> > Loss of config and logs and service deactivated when switching squid flavour
> > and purging the old one.
> And now you don't purge the configuration and logs at all. Policy isn't
> totally clear on this (the text is lightly ambiguous), but *I* expect
> purging to remove my configuration and logs, what else is the delta
> between removal and purging? However, I'm wondering if I want you to fix
The package has traditionally left, the cache (something that is probably
not usefull at all) without being removed from the disk just because it
would take a lot of time to remove it (reading the comments on postrm
script)
# We do not remove /var/spool/squid because that might
# take a lot of time. Most of the time it is on a seperate
# disk anyway and it is faster to do a mkfs on it..
I thought that leaving the logs which can be even legally needed, wouldn't
hurt, in my case when I found this it was a problem as I lost all the logs I
had on the system (luckily I had a backup).
> that at this moment at the risk of not getting it right. However, I
You are right.
> think you're current message is confusing though and needs improvement:
> 1) it doesn't mention the configuration file(s)
The configuration file (which was forcebly removed by postrm before) is
removed by dpkg if squid and squid-openssl are both purged, so as far as
config goes, it still does what you would spect.
> 2) it doesn't mention that the log is shared with that other
> (potentially installed) package. There's context missing here for
> sysadmins of why you're not doing it in the package. What happens if
> somebody just did exactly as told and deleted the log directory?
Agreed, I can try to get a better message on a -9 version of it.
> -#DEBHELPER#
> +# Automatically added by dh_installinit/13.3.4
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Highly confusing, don't you think, for something that's not at all
> automatically added.
Sure, I didn't remove this to minimize the changes between the binary
packages, and given that this was a temporary fix, I thougt it would be
better to leave it like that, but I'll remove it on -9.
Regards...
--
Manty/BestiaTester -> http://manty.net
