Bug#476126: Bug:#476126 hplip: postrm attempts to remove group scanner unconditionally
On Tue, 15 Apr 2008, Julien BLACHE wrote: When purged, the hplip postrm attempts to remove the scanner group, and this in an unconditional manner. Please do not do this and let libsane handle the scanner group. Julien, Sorry about the delay, yes I agree this would be good to resolve before lenny. hplip also checks for the scanner group and adds it if necessary. But hplip also depends on libsane. Is hplip able to rely on libsane to add and remove the scanner group as required? Looking through launchpad[1] I see that they are now using HAL rather than the scanner group for access. Is that relevant to debian? Till. Can you comment at all? Mark [1] https://bugs.launchpad.net/ubuntu/+source/hal/+bug/195782 signature.asc Description: This is a digitally signed message part.
Bug#476126: Bug:#476126 hplip: postrm attempts to remove group scanner unconditionally
Mark Purcell wrote: Sorry about the delay, yes I agree this would be good to resolve before lenny. hplip also checks for the scanner group and adds it if necessary. But hplip also depends on libsane. Is hplip able to rely on libsane to add and remove the scanner group as required? If libsane manages completely that the scanner group exists throughout the whole presence of libsane, HPLIP does not need to take care of the group. If libsane does so only from a given version on, then make the dependency in HPLIP versioned. Looking through launchpad[1] I see that they are now using HAL rather than the scanner group for access. Is that relevant to debian? I do not know whether Debian switched to HAL, too. If so, one could drop the scanner group even in libsane. In general I would keep the scanner group, so that the admin can add (trusted) users to the group scanner if they want to scan from an ssh login or if the machine provides desktops to remote machines through tools like VNC or NX. Till -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476126: Bug:#476126 hplip: postrm attempts to remove group scanner unconditionally
Mark Purcell [EMAIL PROTECTED] wrote: Hi, Is hplip able to rely on libsane to add and remove the scanner group as required? Yes, absolutely. libsane has been using (and creating) the scanner group for years now. Also, when you create users and/or groups, you never ever remove them with the package. Users and groups must remain on the system even after the package has been purged. Looking through launchpad[1] I see that they are now using HAL rather than the scanner group for access. Is that relevant to debian? I provide the HAL fdi file in Debian too, but HAL is not mandatory and libsane still ships udev rules and will continue to do so. JB. -- Julien BLACHE [EMAIL PROTECTED] | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476126: Bug:#476126 hplip: postrm attempts to remove group scanner unconditionally
On Tue, 3 Jun 2008, Julien BLACHE wrote:
Is hplip able to rely on libsane to add and remove the scanner group as
required?
Yes, absolutely. libsane has been using (and creating) the scanner
group for years now.
Great, I'll remove all hplip touching the scanner group from post{inst,rm}
then and defer all actions to libsane.
Mark
signature.asc
Description: This is a digitally signed message part.
