This bug was fixed in the package unattended-upgrades - 0.50ubuntu1
---
unattended-upgrades (0.50ubuntu1) karmic; urgency=low
* fix crash in ouput, thanks to Joerg Schuetter, closes: #535347
* when running in --debug mode, also print debug output to stderr
* add --dry-run option
** Branch linked: lp:unattended-upgrades
--
Still not obvious how to configure unattended-upgrades
https://bugs.launchpad.net/bugs/311052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I see you added a manual page, too. Looking good. Thanks!
--
Still not obvious how to configure unattended-upgrades
https://bugs.launchpad.net/bugs/311052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Branch linked: lp:~mvo/unattended-upgrades/mvo
--
Still not obvious how to configure unattended-upgrades
https://bugs.launchpad.net/bugs/311052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Thanks for your bugreport and your suggestions.
I added them to the README file now and I hope they are clearer now.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Fix Committed
** Changed in: unattended-upgrades (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
> Most users enable it via the Update Manager, which has a simple
> checkbox in the UI for enabling unattended upgrades
Sorry, this should be Software Sources, and the widget is actually a
radio button. (The default is to just notify about new security
updates.)
Bug #84918 has details about how
