[debhelper-devel] Bug#697362: debhelper: [dh_installudev] please automatically generate `udevadm trigger` calls

Niels Thykier niels at thykier.net
Mon Feb 22 19:37:39 UTC 2016


On Fri, 04 Jan 2013 12:38:31 +0100 Luca Capello <luca at pca.it> wrote:
> 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
> 
> [...]

Hi systemd/udev maintainers,

Is this something we can solve by using dpkg file triggers (or an
activate-noawait trigger)?

Thanks,
~Niels



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debhelper-devel/attachments/20160222/ca0c0d89/attachment-0003.sig>


More information about the debhelper-devel mailing list