[Touch-packages] [Bug 1581892] [NEW] Download fails on already athenticated site

2016-05-14 Thread Barry Kolts
Public bug reported: I have a personal website that I use Apache's AuthType Basic to authenticate. >From my phone ( Nexas 4 Mako OTA10 ) I can access the page and login OK. When >I download a file I get a HttpError: 401-Unathorized. More in depth: When I press the "GetFile" link Apache logs (in

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

2016-06-29 Thread Barry Kolts
I have noticed this too, at least with logrotate not running. I thought this was because the reboot happens right after, or during, unattended-upgrades. So I set the time to reboot to 7:30 AM in /etc/apt/apt.conf/50unattended-upgrades to give the rest of cron.daily time to run. However

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

2016-06-29 Thread Barry Kolts
Can't seem to edit my own post. Disregard the last paragraph about reboot-required, I need to look into that a little further, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1626345] [NEW] After rebooting for updates, reboot is still required.

2016-09-21 Thread Barry Kolts
Public bug reported: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Barry Kolts
Brian, File attached. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4746383/+files/history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Barry Kolts
Brian, I don't have that file as it was removed by the reboot, but I do believe it said "Linux base", same as the day before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Barry Kolts
Brian, This weekend we had updates for libssl and a libssl regression. Both required a reboot and no second reboot. In other words worked as expected. Perhaps the bug only occurs for kernel updates. I have had this happen a few times in the past. So the next time it happens I will not run

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-10-12 Thread Barry Kolts
And the after autoremove log ** Attachment added: "after_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760020/+files/after_history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-10-12 Thread Barry Kolts
Brian, Yesterday we had kernel updates. My server, which is set to automatically reboot, reboot fine and no /var/run/reboot-required. This morning there was no second reboot, so everything was as expected. The I ran autoremove to remove the stale kernel. Then I had /var/run/reboot- required and

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-22 Thread Barry Kolts
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-05 Thread Barry Kolts
Brian, On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0. On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should. Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and then rebooted which it shouldn't do. I have

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-08 Thread Barry Kolts
@tjaalton My 16.04 server doesn't have update-notifier installed but does have update-notifier-common installed. If I install update-notifier from propose it will install a slew of other packages. If I install update- notifier-common from propose it just installs the new update-notifier- common

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

2019-02-05 Thread Barry Kolts
lukasz, After a kernel update yesterday I can confirmed that the old kernel was removed and the was no reboot today. apt-cache policy unattended-upgrades unattended-upgrades: Installed: 1.1ubuntu1.18.04.7~16.04.1 Candidate: 1.1ubuntu1.18.04.7~16.04.1 Also installed from xenial-proposed: