Your message dated Sat, 10 Sep 2022 19:17:54 +0100
with message-id
<5b2514e5ca0c6a9656f7489407f1f7318ee5be3f.ca...@adam-barratt.org.uk>
and subject line Re: Bug#977028: buster-pu: package sane-backends/1.0.27-3.2
has caused the Debian Bug report #977028,
regarding buster-pu: package sane-backends/1.0.27-3.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
977028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian....@packages.debian.org
Usertags: pu
[ Reason ]
The udev rule to change the owner/group of usb scanners are not included.
[ Impact ]
Scanner working only as root
[ Risks ]
Trivial. The same rule are included in older sane-backends releases.
The same rule is working in bullseye
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in stable
[X] the issue is verified as fixed in unstable
[ Changes ]
* Fix missing udev rules (Closes: #941038)
- New debian/99-libsane.rules.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-4-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
diff -Nru sane-backends-1.0.27/debian/99-libsane.rules
sane-backends-1.0.27/debian/99-libsane.rules
--- sane-backends-1.0.27/debian/99-libsane.rules 1970-01-01
01:00:00.000000000 +0100
+++ sane-backends-1.0.27/debian/99-libsane.rules 2019-04-27
17:25:19.000000000 +0200
@@ -0,0 +1,2 @@
+
+ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"
diff -Nru sane-backends-1.0.27/debian/changelog
sane-backends-1.0.27/debian/changelog
--- sane-backends-1.0.27/debian/changelog 2019-03-23 17:38:37.000000000
+0100
+++ sane-backends-1.0.27/debian/changelog 2020-12-09 18:53:35.000000000
+0100
@@ -1,3 +1,10 @@
+sane-backends (1.0.27-3.2+deb10u1) buster; urgency=medium
+
+ * Fix missing udev rules (Closes: #941038)
+ - New debian/99-libsane.rules.
+
+ -- Jörg Frings-Fürst <debian@jff.email> Wed, 09 Dec 2020 18:53:35 +0100
+
sane-backends (1.0.27-3.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru sane-backends-1.0.27/debian/libsane.install
sane-backends-1.0.27/debian/libsane.install
--- sane-backends-1.0.27/debian/libsane.install 2018-11-02 18:13:02.000000000
+0100
+++ sane-backends-1.0.27/debian/libsane.install 2019-10-02 08:15:37.000000000
+0200
@@ -1,2 +1,3 @@
usr/lib/*/*.so.*
usr/lib/*/sane/*.so.*
+debian/99-libsane.rules /lib/udev/rules.d/
--- End Message ---
--- Begin Message ---
On Fri, 2022-08-05 at 20:31 +0100, Adam D. Barratt wrote:
> On Sat, 2021-01-16 at 18:08 +0000, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> >
> > On Thu, 2020-12-10 at 09:44 +0100, Jörg Frings-Fürst wrote:
> > > The udev rule to change the owner/group of usb scanners are not
> > > included.
> > >
> > > [ Impact ]
> > > Scanner working only as root
> > >
> > > [ Risks ]
> > > Trivial. The same rule are included in older sane-backends
> > > releases.
> > > The same rule is working in bullseye
> > [...]
> > > * Fix missing udev rules (Closes: #941038)
> > > - New debian/99-libsane.rules.
> >
> > The metadata for that bug does not include a fixed version, and
> > implies
> > that it affects the package in unstable. That seems to be in direct
> > contradiction to your comment in the "risks" section above.
> >
> > Assuming that this is simply an oversight, please add an
> > appropriate
> > fixed version to #941038 and go ahead.
> >
>
> Ping? We're in the process of organising the final point release for
> buster, as support for it transitions over to the LTS team, so if you
> would still like to fix it via pu then the upload needs to happen
> soon.
>
It didn't happen, and the final point release was earlier today. I'm
therefore going to close this request now.
Regards,
Adam
--- End Message ---
