I always enable proposed and never break my system. In this case I have
disable secure boot to time when shim-signed was published in repo. When
I write "release" I mean publishing package in repo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Proposed is *proposed*, not *released*. Packages in -proposed are not
guaranteed to be suitable for general consumption. apt dist-upgrade
with -proposed enabled is a good way to break your system. You should
disable -proposed.
--
You received this bug notification because you are a member of
No it's ok, but first was released all except shim-signed (that broke depends
and force user to uninstall shim-signed). 12 h ago was released shim-signed
that was lack at first update. Even on Launchpad is date of publish of package:
https://launchpad.net/ubuntu/+source/shim-signed/1.21.4
They
new version of shim-signed was released 3h ago. It would be better to
release all changes related to same topic (secureboot for this example)
in same time. After update shim-signed to 1.21.4 secureboot now working
with Ubuntu.
** Changed in: shim-signed (Ubuntu)
Status: New => Fix Released
