ubuntu-packaging-guide-team team mailing list archive
-
ubuntu-packaging-guide-team team
-
Mailing list archive
-
Message #01849
[Bug 1646557] Re: /bin/udevadm should be exit 0 instead of exit 1
Solution change udevadm or change packages if xenial change udevadm -
rfkill is just an example there are more packages, which call
/bin/udevadm at dpkg configure ... if you change udevadm, then
cat udevadm
#!/bin/sh
if [ "$1" = "trigger" ]; then
echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
exit 0
fi
if [ "$1" = "settle" ]; then
echo "udevadm settle is not permitted while udev is unconfigured." 1>&2
exit 0
fi
exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0"
"$@"
then
dpkg --configure -a
rfkill (0.5-1ubuntu3) wird eingerichtet ...
udevadm trigger is not permitted while udev is unconfigured.
but get configured, because the package didn't get a sigkill
--
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/1646557
Title:
/bin/udevadm should be exit 0 instead of exit 1
Status in Ubuntu Packaging Guide:
Invalid
Bug description:
if [ "$1" = "trigger" ]; then
echo "some text halt was sinnvolle oder unsinniges zum Abruch
exit 1
fi
apt-get install rfkill
for example fails to configure
why not in /bin/udevadm end with exit 0 in case of trigger
or settle?
then apt-get install rfkill and 28 other packages can configure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1646557/+subscriptions
References