Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Dominik George
Hi, > > I said that I cannot access CUPS from the local network, not from loopback. > > The title of this bug is "Default ServerName wrong/not in sync with manual". > I'm not sure I understand whether you think the documentation should be > changed, or whether the _code_ should be changed. Coul

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Didier 'OdyX' Raboud
Le jeudi, 12 octobre 2017, 16.34:48 h CEST Dominik George a écrit : > I said that I cannot access CUPS from the local network, not from loopback. The title of this bug is "Default ServerName wrong/not in sync with manual". I'm not sure I understand whether you think the documentation should be c

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Brian Potkin
On Thu 12 Oct 2017 at 16:34:48 +0200, Dominik George wrote: > >CUPS' behaviour is intentional. It rejects requests addressed to the > >system's FQDN host which are received over the local loopback > >interface. > >127.0.1.1 uses the loopback interface. > > Good thing I do not route 127.0.0.0/8 in

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Dominik George
>CUPS' behaviour is intentional. It rejects requests addressed to the >system's FQDN host which are received over the local loopback >interface. >127.0.1.1 uses the loopback interface. Good thing I do not route 127.0.0.0/8 in my network - that wouldn't work anyway. I said that I cannot access CUP

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Brian Potkin
On Thu 12 Oct 2017 at 14:50:20 +0200, Dominik George wrote: > > Does either 127.0.0.1 or 127.0.1.1 in /etc/hosts map to your FQDN? > > The base host name of the system is resolvable to its FQDN and > `hostname -f` returns the correct FQDN. > > Yet, as reported, CUPS only accepts the base name as

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Dominik George
> Does either 127.0.0.1 or 127.0.1.1 in /etc/hosts map to your FQDN? The base host name of the system is resolvable to its FQDN and `hostname -f` returns the correct FQDN. Yet, as reported, CUPS only accepts the base name as reported by `hostname`. -nik

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Brian Potkin
On Thu 12 Oct 2017 at 12:18:51 +0200, Dominik George wrote: > Hi, > > >> What I report - and what is a fact - is that CUPS as installed from > >> the Debian package does NOT WORK under normal network conditions, > >> because it REFUSES to accept requests under its own FQDN. > >> > >> That the do

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Dominik George
Hi, >> What I report - and what is a fact - is that CUPS as installed from >> the Debian package does NOT WORK under normal network conditions, >> because it REFUSES to accept requests under its own FQDN. >> >> That the docs tell it should accept those requests is another part of >> the bug. > >P

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-12 Thread Brian Potkin
On Wed 11 Oct 2017 at 23:25:48 +0200, Dominik George wrote: > >If you feel there is an upstream issue in the documentation there is > > > > https://github.com/apple/cups/issues/new > > Have you read devref? It's your responsibility as package maintainer > to forward bugs upstream. I am not a mai

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-11 Thread Dominik George
Hi, >If you feel there is an upstream issue in the documentation there is > > https://github.com/apple/cups/issues/new Have you read devref? It's your responsibility as package maintainer to forward bugs upstream. https://www.debian.org/doc/manuals/developers-reference/ch03.en.html#upstream-coo

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-11 Thread Brian Potkin
On Wed 11 Oct 2017 at 20:59:24 +0200, Dominik George wrote: > Control: reopen -1 > > On Wed, Oct 11, 2017 at 07:35:25PM +0100, Brian Potkin wrote: > > It is common to use manualpage(x) as a shorthand to instruct a user to > > run the command 'man x manualpage'. Following the advice in hostname(1)

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-11 Thread Dominik George
Control: reopen -1 On Wed, Oct 11, 2017 at 07:35:25PM +0100, Brian Potkin wrote: > It is common to use manualpage(x) as a shorthand to instruct a user to > run the command 'man x manualpage'. Following the advice in hostname(1) > does result in the fully-qualified hostname being displayed when the

Processed: Re: Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-11 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #878148 {Done: Brian Potkin } [cups] cups: Default ServerName wrong/not in sync with manual Bug reopened Ignoring request to alter fixed versions of bug #878148 to the same values previously set -- 878148: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#878148: cups: Default ServerName wrong/not in sync with manual

2017-10-10 Thread Dominik George
Package: cups Version: 2.2.4-7 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - From cups.d(5): ServerName hostname Specifies the fully-qualified hostname of the server. The default is the value reported by the hostname(1) command. This is plain wrong in i