Please review the SRU process here.
https://wiki.ubuntu.com/StableReleaseUpdates
When it lands in -proposed, your help in the verification process is most
welcomed.
On Thu, May 4, 2017 at 10:46 AM, Алексей wrote:
> okay, is there any ETA for SRU process to be finished?
> We can fix this by han
It's not been released. I've just started the SRU process for getting it
into xenial-updates.
If you want to test, you can try out the package from the PPA:
ppa:raharper/bugfixes
On Thu, May 4, 2017 at 4:27 AM, Алексей wrote:
> Ryan, but I couldnt find this version in repos:
> # cat /etc/apt
On Tue, Jun 28, 2016 at 1:01 PM, Alexander E. Patrakov <
1448...@bugs.launchpad.net> wrote:
> The proposed modification of the service file works. It works both with
> default.target and with multi-user.target.
>
Thanks for testing.
The target selection was based on what's upstream in the debian
On Mon, Jun 13, 2016 at 8:18 PM, David Kowis wrote:
> Sorry for the noise on this bug! It turns out I'm simply not waiting
> long enough for it to come up. It is being started on boot, and
> everything is working like I expect, just isn't showing up.
>
>
> I do still have the question about when
On Mon, Jun 13, 2016 at 8:10 PM, David Kowis wrote:
> Also, I've grabbed and installed the 5.15-1 .dpkg. systemctl reports
> that it's enabled, but it never starts on boot. Checking right after
> boot yields this:
>
> ```
> root@hylden:~# systemctl status watchdog
> ● watchdog.service - watchdog
On Mon, Apr 18, 2016 at 4:05 PM, Paul Crawford <1448...@bugs.launchpad.net>
wrote:
> I will try to look tomorrow or so at the proposed fix.
> Have you checked if it is still loaded OK following a reboot?
>
Yes, it continues to work after reboot.
It's best if you configure /etc/default/watchdog a