Bug#747073: [cups-daemon] Doesn't work with systemd

[Brian Potkin]

On Sun 03 Aug 2014 at 14:06:10 +0200, Didier 'OdyX' Raboud wrote:

> Le dimanche, 3 août 2014, 12.11:58 Marco d'Itri a écrit :
> > > systemd maintainers: I think Listen*=[::1]:$port stanzas shouldn't
> > > make the .socket-file loading fail if the ipv6 module is not
> > > loaded. It should certainly spit out a warning though.
> > 
> > There is no magic "we do not care if it does not work" address family:
> > if a unit is configured to open a socket but this fails then the unit
> > must fail.
> 
> Fair enough.
> 
> Assuming there's no good way to make this work within systemd, I see 
> three ways forward to fix this in cups:
> 
> a) declare that ipv6 is mandatory these days, document this in
>    README.Debian, let users cope with it.
>    Pros: it works for most, ipv6 is coming anyway
>    Cons: changes done through cups would break the user override every
>          time.

[Snip]
 
> The current setup took quite some intensive iterations to work as it 
> currently does; it's only drawback is that it fails to give proper 
> feedback to users who have disabled ipv6 for some reason.
> 
> I'm currently leaning towards either leaving this bug as a documentation 
> trace (+wontfix) or tackling the c)-idea above but would welcome 
> feedback from systemd maintainers on whether this has a chance to 
> actually work.

Debian set the goal of supporting IPv6 across the distribution and I
believe it is now mainly complete, so it seems to me that regarding it
as an integral part or default for the distribution is fair and not out
of place. Users who for whatever reason turn it off should not have an
expectation of significant work being done to meet their situation.

I would suggest your documentation idea is the path to take.

Proof-reading is available on request. :)

Regards,

Brian.