Your message dated Sat, 16 May 2020 15:08:46 +0200
with message-id <[email protected]>
and subject line Re: Bug#956577: virtualbox: Please decide whether to add
C/R/P: time-daemon
has caused the Debian Bug report #956577,
regarding Please decide whether to add C/R/P: time-daemon
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
956577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956577
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-timesyncd
Version: 245.4-3
Severity: normal
# apt-get -V dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libnotify-bin (0.7.9-1)
libqpdf26 (9.1.1-1)
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
virtualbox-guest-utils (6.1.4-dfsg-4)
virtualbox-guest-x11 (6.1.4-dfsg-4)
The following NEW packages will be installed:
libqpdf28 (10.0.1-2)
linux-image-5.5.0-1-amd64 (5.5.13-2)
systemd-timesyncd (245.4-3)
The following packages will be upgraded:
cups-filters (1.27.3-1 => 1.27.4-1)
cups-filters-core-drivers (1.27.3-1 => 1.27.4-1)
libnss-systemd (245.4-1 => 245.4-3)
libpam-systemd (245.4-1 => 245.4-3)
libsystemd0 (245.4-1 => 245.4-3)
linux-image-amd64 (5.4.19-1 => 5.5.13-2)
python3-pikepdf (1.10.3+dfsg-1 => 1.10.3+dfsg-1+b1)
systemd (245.4-1 => 245.4-3)
8 upgraded, 3 newly installed, 2 to remove and 0 not upgraded.
Need to get 56.8 MB of archives.
After this operation, 276 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd-timesyncd depends on:
ii adduser 3.118
ii libc6 2.30-4
ii systemd 245.4-1
systemd-timesyncd recommends no packages.
systemd-timesyncd suggests no packages.
--- End Message ---
--- Begin Message ---
On Tue, 14 Apr 2020 13:48:08 +0200 Guillem Jover <[email protected]> wrote:
> Hi!
>
> On Tue, 2020-04-14 at 11:58:57 +0100, Dimitri John Ledkov wrote:
> > IMHO virtualbox-guest-utils portion that does settimeofday() to host's
> > time should be split into a separate subpackage, and make that one
> > provide/conflicts/replaces time-daemon.
>
> I don't think this is possible. The part that does that is VBoxService
> which is a multi-service daemon that takes care of many other things.
>
> > This way, people can use virtualbox-guest-utils always, and choose if
> > they want timesyncd / ntp / etc or virtualbox-guest-utils-time-daemon
> > to provide the time.
>
> The timesync support in VBoxService can always be disabled by passing
> --disable-timesync on when starting it, or from the host either
> permanently or at run-time time with VBoxManage. So neither the presence
> of the file on the file system nor of the process running means its is
> handling time sync.
>
Unfortunately I agree, there is currently no way to understand if VBoxService
is doing or not the timesync.
I might create a new binary that does only autosync and put into a separate
binary,
but this won't help people using the iso as guest tool and other distro.
We need in case to ask upstream to do something related to this and eventually
adapt it to Debian.
E.g. We can disable it by compiling with VBOX_WITH_VBOXSERVICE_TIMESYNC but
this is a no-go of course.
Majority of people still wants it to work, not being disabled or decoupled by
default.
please reopen if you have a patch or a better overview of the problem, I admit
I don't like kmk too much, and a patch to create
a standalone binary just made of
src/VBox/Additions/common/VBoxService/VBoxServiceTimeSync.cpp might be easier
than my thought
thanks
Gianfranco
Gianfranco
--- End Message ---
