Hi Ricardo,
Ricardo Fraile wrote:
> I tested an upgrade from 3.4.0 to 3.4.1 on a fresh install of Sid
> and it doesn't report any issue.
JFTR: uptimed is also installed. Not sure if that makes a difference
as tuptime seems to be able to import uptimed's database.
> What is the output of "ls -al /var/lib/tuptime"?
total 12
drwxr-xr-x 2 root root 4096 Sep 25 02:00 .
drwxr-xr-x 113 root root 4096 Nov 22 00:48 ..
-rw-r--r-- 1 root root 2048 Sep 25 02:00 tuptime.db
> Did you reboot the computer between the 3.4.0 installation and the
> upgrade?
Yes. tuptime 3.4.0 was uploaded to unstable on 2018-09-23 and I last
rebooted on 2018-09-30.
# zfgrep tuptime /var/log/dpkg.log.2.gz
2018-09-25 02:01:37 upgrade tuptime:amd64 3.3.3 3.4.0
2018-09-25 02:01:37 status half-configured tuptime:amd64 3.3.3
2018-09-25 02:01:37 status unpacked tuptime:amd64 3.3.3
2018-09-25 02:01:37 status half-installed tuptime:amd64 3.3.3
2018-09-25 02:01:37 status half-installed tuptime:amd64 3.3.3
2018-09-25 02:01:38 status unpacked tuptime:amd64 3.4.0
2018-09-25 02:01:38 status unpacked tuptime:amd64 3.4.0
2018-09-25 02:01:55 configure tuptime:amd64 3.4.0 <none>
2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0
2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0
2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0
2018-09-25 02:01:55 status half-configured tuptime:amd64 3.4.0
2018-09-25 02:01:56 status installed tuptime:amd64 3.4.0
> Please, can you add here the output of 'su -s /bin/sh tuptime -c
> "tuptime -x"'?
# su -s /bin/sh tuptime -c "tuptime -x"
ERROR:root:After system restart, the values must be saved into db. Please,
execute tuptime with a privileged user.
HTH.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
