summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2017-07-15 12:14:01 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2017-07-15 12:14:01 +0200
commit109c82b997fde38310cd35dd54c140ef048a49b1 (patch)
tree58026a2ddbb4fb5d25df70c6d3b251769b570deb
parent03996ab25c50b9f2c8a872aacba3287dad5a29f5 (diff)
Replace libsane.udev with libsane1.udev at TROUBLESHOOTING.Debian and libsane1.README.Debian
-rw-r--r--debian/TROUBLESHOOTING.Debian4
-rw-r--r--debian/changelog6
-rw-r--r--debian/libsane1.README.Debian10
3 files changed, 11 insertions, 9 deletions
diff --git a/debian/TROUBLESHOOTING.Debian b/debian/TROUBLESHOOTING.Debian
index 397626f..f9a9a76 100644
--- a/debian/TROUBLESHOOTING.Debian
+++ b/debian/TROUBLESHOOTING.Debian
@@ -18,7 +18,7 @@ REMARK: Sometimes usblp is used to access your printer.
From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789593
-The file /lib/udev/rules.d/60-libsane.rules uses the command "/bin/setfacl -m g:scanner:rw
+The file /lib/udev/rules.d/60-libsane1.rules uses the command "/bin/setfacl -m g:scanner:rw
$env{DEVNAME}" to add the "scanner" group with rw access to the device permissions.
In my case, with /dev on an ext4 filesystem with no ACL support enabled in the kernel, setfacl
@@ -26,4 +26,4 @@ returns "Operation not supported". I assume this is because it's trying to add a
possible in its fallback mode of traditional Unix-style file permissions.
As a workaround, I have substituted "/bin/chown root:scanner $env{DEVNAME}" as the command at the
-end of 60-libsane.rules (an alternative would be to use a UDEV rule element to change the ownership).
+end of 60-libsane1.rules (an alternative would be to use a UDEV rule element to change the ownership).
diff --git a/debian/changelog b/debian/changelog
index 0b5751e..67186d2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
sane-backends (1.0.27-1~experimental2) UNRELEASED; urgency=medium
* debian/rules:
- - Rename libsane.udev to libsane1.udev to get missing
- 60-libsane1.rules.
+ - Rename libsane.udev to libsane1.udev to get missing
+ 60-libsane1.rules (Closes: #868312).
+ * Replace libsane.udev with libsane1.udev at TROUBLESHOOTING.Debian
+ and libsane1.README.Debian.
-- Jörg Frings-Fürst <debian@jff-webhosting.net> Sat, 15 Jul 2017 11:31:34 +0200
diff --git a/debian/libsane1.README.Debian b/debian/libsane1.README.Debian
index a9ae566..ae0cca2 100644
--- a/debian/libsane1.README.Debian
+++ b/debian/libsane1.README.Debian
@@ -79,7 +79,7 @@ make sure the appropriate device files (eg. /dev/sg0, ...) are owned by root
and the scanner group, with permissions set to 0660.
For USB and SCSI scanners, the permissions will be automatically set by udev;
-the /lib/udev/rules.d/60-libsane.rules file contains a list of USB and SCSI
+the /lib/udev/rules.d/60-libsane1.rules file contains a list of USB and SCSI
scanners supported by SANE.
The udev rules now use ACLs instead of standard UNIX permissions; the scanner
@@ -88,9 +88,9 @@ permissions.
If your scanner is missing from the list, do NOT modify this file; it is not
a configuration file, which means your changes WILL be overwritten upon
-upgrade. Instead, create /etc/udev/rules.d/60-libsane.rules and add the udev
-rule for your scanner in this file. /lib/udev/rules.d/60-libsane.rules will
-then be ignored by udev and /etc/udev/rules.d/60-libsane.rules will be used
+upgrade. Instead, create /etc/udev/rules.d/60-libsane1.rules and add the udev
+rule for your scanner in this file. /lib/udev/rules.d/60-libsane1.rules will
+then be ignored by udev and /etc/udev/rules.d/60-libsane1.rules will be used
instead.
Feel free to file a bug report (severity wishlist) against the libsane package
@@ -104,7 +104,7 @@ the scanner is supported (basic, good, ...).
udev will automatically set up the permissions and ownership on the device
node corresponding to your scanner according to the rules defined in the
-libsane.rules file (default is root:scanner, 0664). If you want to execute
+libsane1.rules file (default is root:scanner, 0664). If you want to execute
a script when your scanner is plugged in, add RUN+="/path/to/script" to the
rule matching your scanner.