Your message dated Sat, 01 Oct 2016 17:06:00 +0000
with message-id <600b9838-7b6c-a4ae-00f2-58961ec43...@thykier.net>
and subject line Re: Bug#697362: debhelper: [dh_installudev] please 
automatically generate `udevadm trigger` calls
has caused the Debian Bug report #697362,
regarding debhelper: [dh_installudev] please automatically generate `udevadm 
trigger` calls
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.)


-- 
697362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 9.20120909
Severity: wishlist
File: /usr/bin/dh_installudev
Usertags: debian-packaging

Hi there!

When a package installs udev rules, these not automatically applied if
the device is built-in (like fingerprint readers), since it is never
plugged in (obviously, except if the computer is rebooted).  Thus
package.postinst must call `udevadm trigger` according to the udev's
maintainer's explanation at:

  <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683863#27>

While `udevadm trigger` could be called without options, IMHO it is
preferable to limit its call(s) for the device(s) the package supports.
In some cases, the number of the devices can be quite a lot (e.g.
libfprint0 supports 17 of them), thus having an automatic way to
generate these calls from the udev rules would be preferable.

I would be glad to provide a patch, but I am a bit busy ATM.

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debhelper depends on:
ii  binutils    2.22-7.1
ii  dpkg        1.16.9
ii  dpkg-dev    1.16.9
ii  file        5.11-2
ii  html2text   1.3.2a-15
ii  man-db      2.6.3-3
ii  perl        5.14.2-16
ii  po-debconf  1.0.16+nmu2

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  <none>

-- no debconf information

Attachment: pgpXeB5TGAaxH.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
On Sat, 27 Feb 2016 10:19:29 +0000 Niels Thykier <ni...@thykier.net> wrote:
> Control: tags -1 moreinfo
> 
> Michael Biebl:
> > [...]
> 
> Hi Michael and Luca,
> 
> Thanks for your explanation.
> 
> @Luca: Can you elaborate on how many packages where you would need the
> "udevadm trigger" call?  From Michael's explanation I am not quite sure
> it makes sense to add this to debhelper unless it is a common thing.
> 
> Thanks,
> ~Niels
> 
> 
> 

Closing as this bug as been tagged "moreinfo" in over 6 months with no
updates.

Thanks,
~Niels

--- End Message ---

Reply via email to