Thank you for the work, could give a bit more context why a reboot is
needed in those cases? Isn't restarting the service enough?
Having hardcoded addresses in the script seems a bit fragile. And is
that the sort of change we could try to upstream to Debian to not
increase our delta?
Also the description states 'In the case of upgrading bluez', is that
specific to some version? if the issue is with upgrade the postinst code
should check that we are in the upgrade case and not a new install no?
** Changed in: bluez (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
Status in bluez package in Ubuntu:
Incomplete
Bug description:
In the case of upgrading bluez on certain raspberry pi devices, a
reboot may be required to apply the changes. We should add a check for
this scenario in the postinst script.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
