Bug#711169: cups-daemon: ipp printer browsing support removed
Sorry for the delay on this urgent issue. On Wed, Jun 05, 2013 at 01:09:28PM +0200, Till Kamppeter wrote: Your patch is a first step to inform users about the need of cups-browsed. Suggestion to improve it: Explicitly mention that the configuration settings have to be done in /etc/cups/cups-browsed.conf. I attached an updated patch. It also mentions that the values are space separated and that cups browse should be avoided if possible. I am also thinking about letting cups-browsed at least listen to the old IPP broadcasts (BrowseRemoteProtocols cups), so that new clients work with old servers out of the box but the network does not get flooded with broadcasts of an obsolete format by cups-browsed. WDYT? Yes, that would be a good idea. In that case the NEWS file should be changed to reflect this. I was also wondering whether we can somehow pull in cups-browsed on upgrades by default. Not sure whether this is possible without introducing a hard dependency. May I suggest to raise this bug to RCness to avoid cups transitioning to testing before a NEWS entry is there? As you also pointed out the current upgrade path is less than optimal. Having the NEWS file could avoid a pile of headache. Helmut diff -Nru cups-1.6.2/debian/changelog cups-1.6.2/debian/changelog --- cups-1.6.2/debian/changelog 2013-06-04 14:19:17.0 +0200 +++ cups-1.6.2/debian/changelog 2013-06-06 18:59:02.0 +0200 @@ -1,3 +1,10 @@ +cups (1.6.2-8.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Explain browsing transition in cups.NEWS (Closes: #711169). + + -- Helmut Grohne hel...@subdivi.de Wed, 05 Jun 2013 11:16:33 +0200 + cups (1.6.2-8) unstable; urgency=low * Upload to unstable. diff -Nru cups-1.6.2/debian/cups.NEWS cups-1.6.2/debian/cups.NEWS --- cups-1.6.2/debian/cups.NEWS 2013-03-19 11:05:13.0 +0100 +++ cups-1.6.2/debian/cups.NEWS 2013-06-06 19:03:45.0 +0200 @@ -1,3 +1,18 @@ +cups (1.6.2-8) unstable; urgency=low + + * The support for browsing printers on the local network has been moved to +the cups-browsed package. If you need to access a wheezy cups server, you +need to install this package and add cups to the BrowseRemoteProtocols +configuration entry. Similarly if a wheezy client is to discover a 1.6 or +newer cups server, the cups server also needs this package and has to +list cups to the BrowseLocalProtocols configuration entry. The values in +both fields are to be separated and they are both located in +/etc/cups/cups-browsed.conf. You are encouraged to transition to the dnssd +browse protocol, because the cups protocol support is to be dropped in a +future upstream release. + + -- Helmut Grohne hel...@subdivi.de Wed, 05 Jun 2013 11:13:16 +0200 + cups (1.5.3-2.7) unstable; urgency=low In order to mitigate a privilege escalation from the lpadmin to root
Bug#711169: cups-daemon: ipp printer browsing support removed
Package: cups-daemon Version: 1.6.2-8 Severity: normal Somewhere between 1.5.3-5 and 1.6.2-8 the support for IPP printer browsing was removed. This was a decision of cups upstream (i.e. some big fruit company). Still it breaks a legitimate use case: Having printers on a network just work. For what it is worth I have neither avahi-daemon nor cups-browsed installed, so maybe this is just my fault. This bug report is *not* asking for getting IPP printer browsing back, but on getting a smoother transition. To me the two core problems appear to be: How to get a jessie/sid cups client talk to a wheezy cups server without the need to configure each individual printer on the client? (my case) How to get a wheezy cups client talk to a jessie/sid cups server without ...? As a first step I ask for an entry in NEWS.Debian, telling users about the issue. This helps users not finding their printing setup being broken for no obvious reason. This might also reduce the amount of bug reports for this issue (assuming users install apt-listchanges). Then I would like to see some documentation on how to transition systems. I looked at wiki.d.o only finding an outdated http://wiki.debian.org/Teams/CUPS not even knowing about odyx. I briefly looked at /usr/share/doc/cups without finding anything obvious. Is there another place I should check? It is a bit unclear to me how to get a transition at all. Apparently the cups-browsed package is not part of wheezy. So as far as I can see wheezy is not going to talk bonjour. On the other hand jessie/sid is not going to talk IPP browsing. How are they supposed to interact? So this is probably a non-coding issue. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711169: cups-daemon: ipp printer browsing support removed
On Wed, Jun 05, 2013 at 10:14:20AM +0200, Helmut Grohne wrote: As a first step I ask for an entry in NEWS.Debian, telling users about the issue. This helps users not finding their printing setup being broken for no obvious reason. This might also reduce the amount of bug reports for this issue (assuming users install apt-listchanges). I am proposing the attached patch to address this. Feel free use it as a base for further expansion or to include it as is. It is a bit unclear to me how to get a transition at all. Apparently the cups-browsed package is not part of wheezy. So as far as I can see wheezy is not going to talk bonjour. On the other hand jessie/sid is not going to talk IPP browsing. How are they supposed to interact? The observation about cups-browsed not supporting the old browse protocol was wrong. Thanks to Didier for pointing out. The default configuration of the package is not sufficient though. To interact with wheezy cups systems the value cups needs to be added to BrowseRemoteProtocols and BrowseLocalProtocols (for either direction). This is not difficult once you know what to do. Helmut diff -Nru cups-1.6.2/debian/changelog cups-1.6.2/debian/changelog --- cups-1.6.2/debian/changelog 2013-06-04 14:19:17.0 +0200 +++ cups-1.6.2/debian/changelog 2013-06-05 11:18:16.0 +0200 @@ -1,3 +1,10 @@ +cups (1.6.2-8.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Explain browsing transition in cups.NEWS (Closes: #711169). + + -- Helmut Grohne hel...@subdivi.de Wed, 05 Jun 2013 11:16:33 +0200 + cups (1.6.2-8) unstable; urgency=low * Upload to unstable. diff -Nru cups-1.6.2/debian/cups.NEWS cups-1.6.2/debian/cups.NEWS --- cups-1.6.2/debian/cups.NEWS 2013-03-19 11:05:13.0 +0100 +++ cups-1.6.2/debian/cups.NEWS 2013-06-05 11:19:36.0 +0200 @@ -1,3 +1,14 @@ +cups (1.6.2-8) unstable; urgency=low + + * The support for browsing printers on the local network has been moved to +the cups-browsed package. If you need to access a wheezy cups server, you +need to install this package and add cups to the BrowseRemoteProtocols +configuration entry. Similarly if a wheezy client is to discover a newer +cups server, the cups server also needs this package and has to list +cups to the BrowseLocalProtocols configuration entry. + + -- Helmut Grohne hel...@subdivi.de Wed, 05 Jun 2013 11:13:16 +0200 + cups (1.5.3-2.7) unstable; urgency=low In order to mitigate a privilege escalation from the lpadmin to root
Bug#711169: cups-daemon: ipp printer browsing support removed
Thank you very much for the bug report and the patch. The hard switchover from IPP-only broadcasting to Bonjour-only broadcasting on the transition from CUPS 1.5.x to 1.6.x is really bad. cups-browsed is indeed the only solution to get Bonjour browsing to conserve the configuration-less client feature in CUPS 1.6.x environment and CUPS broadcasting/browsing to get compatibility between CUPS 1.5.x and 1.6.x. Your patch is a first step to inform users about the need of cups-browsed. Suggestion to improve it: Explicitly mention that the configuration settings have to be done in /etc/cups/cups-browsed.conf. I am also thinking about letting cups-browsed at least listen to the old IPP broadcasts (BrowseRemoteProtocols cups), so that new clients work with old servers out of the box but the network does not get flooded with broadcasts of an obsolete format by cups-browsed. WDYT? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
