Hello,
The debdiff that I provided contains two typos in a comment :
> 64 +# Explicitely enable and start the service.i Debian Bug #797108 for
It should read Explicitly and "start the service. Debian"
Just let me know if you want an updated debdiff or if you will be fixing it up
yourself.
Hello,
Here is the patch for this issue that I uploaded to Ubuntu. It is slightly
adapted to take into account the possibility of being install on a non-systemd
installation.
I tried to make the changelog entry as explicit as possible but here are some
details.
As outlined previously, the
On Thu, 20 Apr 2017 14:05:39 +0200 Louis Bouchard
wrote:
> Hello,
>
> Le 20/04/2017 à 12:27, Simon McVittie a écrit :
> > [...]
>
> First of all, I am sorry for not keeping up with my work in both bug reports.
> Recent events at my employer have made things a bit
Hi Louis, thanks for your work on this.
On 2017-04-20.14:05, Louis Bouchard wrote:
> > [Unit]
> >
> > Description=Unattended Upgrades Shutdown
> >
Hello,
Le 20/04/2017 à 12:27, Simon McVittie a écrit :
> On Tue, 11 Apr 2017 at 17:25:00 +, Niels Thykier wrote:
>> On Thu, 2 Mar 2017 17:59:02 +0100 Louis Bouchard
>> wrote:
>>> It now tests correctly and I am preparing an upload to our development
>>>
On Tue, 11 Apr 2017 at 17:25:00 +, Niels Thykier wrote:
> On Thu, 2 Mar 2017 17:59:02 +0100 Louis Bouchard
> wrote:
> > It now tests correctly and I am preparing an upload to our development
> > release.
>
> Any news on this? I cannot see an upload to unstable
On Thu, 2 Mar 2017 17:59:02 +0100 Louis Bouchard
wrote:
> Hello,
>
> [...]
>
> The unit was correctly installed but another issue made it show as an
> incorrect
> behavior.
>
> It now tests correctly and I am preparing an upload to our development
> release.
>
On Fri, 10 Feb 2017 at 16:31:25 +0100, Louis Bouchard wrote:
> The proposed systemd unit change would break :
>
> Unattended-Upgrade::InstallOnShutdown "true";
>
> as the network is no longer available to fetch the archive.
You might be interested in unattended-upgrades patches that I wrote for
Hello,
Le 21/02/2017 à 12:31, Scott Leggett a écrit :
> Hi Louis,
>
> On Wed, 15 Feb 2017 14:34:58 +0100 Louis Bouchard
> wrote:
>> Hello,
>>
>> I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown
>> unit starts once the target Network is
Hi Louis,
On Wed, 15 Feb 2017 14:34:58 +0100 Louis Bouchard
wrote:
> Hello,
>
> I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown
> unit starts once the target Network is being brought down :
I don't think the replacement unit I
Hello,
I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown
unit starts once the target Network is being brought down :
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target Network is
> Online.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target
On Fri, 10 Feb 2017 16:31:25 +0100 Louis Bouchard
wrote:
> Hi,
>·
> The proposed systemd unit change would break :
>·
> Unattended-Upgrade::InstallOnShutdown "true";
>·
> as the network is no longer available to fetch the archive.
>·
No, it wouldn't.
> As outlined
Hi,
The proposed systemd unit change would break :
Unattended-Upgrade::InstallOnShutdown "true";
as the network is no longer available to fetch the archive.
As outlined in the systemd documentation :
"Given two units with any ordering dependency between them, if one unit is shut
down and the
Le jeudi 9 février 2017, 17 h 14 min 44 s CET Louis Bouchard a écrit :
> The unattended-upgrade-shutdown script uses a lock in /var/run to check if an
> upgrade job is running. After /var is unmounted, /var/run is no longer present
Hi,
I thought that by now all reference to /var/run could be
Hello,
For info, this also has the potential effect of blocking shutdown (see Ubuntu's
LP: #1654600 [1]) for details.
The unattended-upgrade-shutdown script uses a lock in /var/run to check if an
upgrade job is running. After /var is unmounted, /var/run is no longer present
and
15 matches
Mail list logo