[Pkg-squid-devel] Team maintaining Squid packages

[Luigi Gangitano]

> Il giorno 19/ott/2014, alle ore 10:05, Amos Jeffries <squid3 at treenet.co.nz> ha scritto:
> 
> * The cert_tool has openssl dependency and we are explicitly not
> publishing an OpenSSL linked with Squid package [1]. While this is not
> exactly linking, IMHO the script should probably not be installed anyway.

I would pull it for know. May be we could add it back once a non-free squid3-ssl package is built and distributed (see #641944).

> * "Create run_dir ... fixes #710126 (Closes: #732183, #760400)"
> - does that not also need another (Closes: #710126) ?

#710126 is marked as fixed in 3.3.8-1 even if a later messages notes that it is not.

> * about the config file processing/checking...
> 
> - "-k check" requires an already running Squid process to exchange
> signals with. This new change will start to produce errors about no
> running process if restart/reload/force-reload is used after a Squid
> crash or other reason for none already running. Previously it would just
> start a new one.
> 
> Luigi: is that an acceptible change? if not the new "-k check"
> should become "-k parse", which validates without the existing
> process condition.

I would prefer the "-k parse” option and 

> - we are also still missing "-k parse" on start action to verify the
> config is usable without that running-process requirement.

this also. Am changing this behavior now in squid3.rc.

> FYI: Squid SMP support allows macros embeded in config file lines,
> which is a popular feature with SMP cache_dir configurations. The naive
> grepconf will not produce correct paths in the presence of these macros.
> 
> ++ I am working now on a better grepconf that fixes those unreported
> bugs, but it may take me a while to verify properly. The existing
> updates are reasonable temporary fix if you want these bugs closed ASAP.

Thanks. Would “-k parse” produce better results? I didn’t get too much into the macros details yet.

> * do we want to pull in the apparmour template? I note that someone in
> Ubuntu has once again entangled squidguard and squid3 packages. So
> the template will need pruning by someone who knows how to de-tangle them.

Will look into this too, but I see Ubuntu-specific changes low priority ATM.

> * squid-langpack could do with a refresh.

Will do now. squid-langpack will also need to be moved to pkg-squid in the near future.

Regards,

L

--
Luigi Gangitano -- <luigi at debian.org> -- <gangitano at lugroma3.org>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26
GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5  0F6D 0284 F20C 2BA9 7CED