Am 09.10.2015 um 19:33 schrieb Michael Biebl:
> if dpkg --compare-versions "$2" lt "218-11~"; then
> systemctl enable systemd-timesyncd.service || true
> fi
>
> The latter should only be run from upgrades older then 218-11 or on new
> installs.
>
>
> So for some reason "$2" (the old
On 09/10/15 19:33, Michael Biebl wrote:
> The complete log dpkg log from the upgrade.
I didn't have time to try and replicate the issue with the
downgrade/upgrade again yet.
Attached there's the dpkg.log of the previous update (227-1 -> 227-2).
2015-10-09 16:54:56 startup packages configure
On 09/10/15 16:57, Yuri D'Elia wrote:
>> If you do the steps I posted, is the service re-enabled for you?
>
> No it's not, as expected.
Ok, just updated from 227-1 to 227-2 using aptitude:
Performing actions...
Preconfiguring packages ...
(Reading database ... 35322 files and directories
On 09/10/15 15:23, Martin Pitt wrote:
> i. e. it only gets enabled once on a fresh install, or when you
> upgrade from jessie. But not e. g. from 226-1 to 227-1. Which version
> did you upgrade from?
I'm following unstable on a KVM instance where I explicitly do not want
time sync, so I'm unsure
Am 09.10.2015 um 15:56 schrieb Yuri D'Elia:
> On 09/10/15 15:23, Martin Pitt wrote:
>> i. e. it only gets enabled once on a fresh install, or when you
>> upgrade from jessie. But not e. g. from 226-1 to 227-1. Which version
>> did you upgrade from?
>
> I'm following unstable on a KVM instance
Am 09.10.2015 um 19:25 schrieb Yuri D'Elia:
> On 09/10/15 19:15, Michael Biebl wrote:
>>> # systemctl is-enabled systemd-timesyncd.service
>>> enabled
>>
>> Can you provide the full log?
>
> I closed the terminal already [heh], but there was nothing interesting
> in replacing the other systemd
Am 09.10.2015 um 18:27 schrieb Yuri D'Elia:
> On 09/10/15 16:57, Yuri D'Elia wrote:
>>> If you do the steps I posted, is the service re-enabled for you?
>>
>> No it's not, as expected.
>
> Ok, just updated from 227-1 to 227-2 using aptitude:
>
> Performing actions...
> Preconfiguring packages
On 09/10/15 19:15, Michael Biebl wrote:
>> # systemctl is-enabled systemd-timesyncd.service
>> enabled
>
> Can you provide the full log?
I closed the terminal already [heh], but there was nothing interesting
in replacing the other systemd packages. I pasted the entire contents of
the
Package: systemd
Version: 227-1
Severity: normal
I'm trying to disable time syncronization, but I've found two issues happening
during upgrades:
- Disabling systemd-timesyncd.service is not enough.
systemd-timesyncd.service gets automatically re-enabled on upgrade.
Is this intended? I would
Control: tags -1 moreinfo unreproducible
Am 09.10.2015 um 15:11 schrieb Yuri D'Elia:
> Package: systemd
> Version: 227-1
> Severity: normal
>
> I'm trying to disable time syncronization, but I've found two issues happening
> during upgrades:
>
> - Disabling systemd-timesyncd.service is not
Control: tag -1 moreinfo
Hello Yuri,
Yuri D'Elia [2015-10-09 15:11 +0200]:
> Version: 227-1
>
> I'm trying to disable time syncronization, but I've found two issues happening
> during upgrades:
>
> - Disabling systemd-timesyncd.service is not enough.
> systemd-timesyncd.service gets
On 09/10/15 16:08, Michael Biebl wrote:
>> I'm following unstable on a KVM instance where I explicitly do not want
>> time sync, so I'm unsure on which version this got re-enabled.
>>
>> I noticed this issue some months ago, where I disabled the service on
>> two occasions, then tried using
12 matches
Mail list logo
