[pkg-squid-devel] squid-3.5.4 package

[Amos Jeffries]

On 7/05/2015 6:21 p.m., Mathieu Parent (Debian) wrote:
> Hello,
> 
> 2015-05-07 7:58 GMT+02:00 Amos Jeffries <squid3 at treenet.co.nz>:
>> As mentioned earlier I've got the packaging updating squid3 to 3.5.4
>> applied and pushed.
>>
>> The transition to package name "squid" has got a bit confusing. Using
>> dpkg-maintscript-helper it copes nicely with with all cases of any
>> pre-existing squid (2.7) package, or both pre-existing squid and squid3
>> packages.
>>
>> Except for one case permutation:
>>  With only a pre-existing squid3 package which has also been edited by
>> the admin it seems to discard the old /etc/squid3/squid.conf file and
>> use the new packaged one. So the one case we most want to preserve the
>> config it is being discarded.
>>
>> Any ideas how to fix?
>>  I've applied and pushed the progress so far for y'all to see the context.
> 
> I think this can't be solved without a remaining "squid3" package
> which previously owns /etc/squid3 files.This is because currently, the
> "squid" postrm script is not run on upgrade (as this is an install).
> 

It seems so. And only with a bit of trickery even then.
 I had to have the squid package explicitly check for /etc/squid3
existence and copy the file over before squid package upgrade AND have a
squid3 dummy package ready to install to suppress errors about
conflicting man8 files etc.

The squid3 dummy package seems to require a Pre-Depends on the new squid
package to avoid erasing the wanted old squid3 files.
 But then the squid package needs a conflicts on pre-3.5 squid3 package
versions to enforce the dummy package upgrade happens at the same time
(due to man8 file collision errors).

Using manual calls to dpkg --install I still cant seem to find any
combination of package ordering that lets me install the upgrade and
dummy packages cleanly at the same time.

The best I can get is "dpkg --install squid-common squid squid3". It
unpacks but squid3 setup fails citing some error about squid pre-dep
package being unpacked but not yet installed, which disappears on a
repeat attempt to install squid3.

I'm hoping that apt is able to suppress either the man8 or pre-dep the
errors since it knows the squid3 package will be upgrading.



>> To be done:
>> * fix the above squid3 issue
>> * migrate any other user custom config files that exist in /etc/squid3/

Decided to leave this to admin. Since they could be using /etc/squid3
for anything sub-included off squid.conf and the folder is left in place
by the upgrade if its non-empty.

>> * edit squid.conf for helper renaming since Lenny.

Testing now a function which scans like grepconf for usage of any of the
Lenny packaged helper names and squid3 paths in cache_dir etc. then
creates symlinks only for the ones actively used.

Amos