Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194405 > unrolled thread

Unknown Systemd version

Started byLaurent Lyaudet <laurent.lyaudet@gmail.com>
First post2018-04-02 18:40 +0200
Last post2018-04-04 19:50 +0200
Articles 7 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Unknown Systemd version Laurent Lyaudet <laurent.lyaudet@gmail.com> - 2018-04-02 18:40 +0200
    Re: Unknown Systemd version Sven Joachim <svenjoac@gmx.de> - 2018-04-02 19:20 +0200
    Re: Unknown Systemd version David Wright <deblis@lionunicorn.co.uk> - 2018-04-02 21:20 +0200
      Re: Unknown Systemd version Laurent Lyaudet <laurent.lyaudet@gmail.com> - 2018-04-03 20:20 +0200
        Re: Unknown Systemd version David Wright <deblis@lionunicorn.co.uk> - 2018-04-03 21:50 +0200
          Re: Unknown Systemd version Abdullah Ramazanoglu <ar018@yahoo.com> - 2018-04-03 22:40 +0200
            Re: Unknown Systemd version Laurent Lyaudet <laurent.lyaudet@gmail.com> - 2018-04-04 19:50 +0200

#194405 — Unknown Systemd version

FromLaurent Lyaudet <laurent.lyaudet@gmail.com>
Date2018-04-02 18:40 +0200
SubjectUnknown Systemd version
Message-ID<vAaEW-3NU-7@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,

I'm using Stretch. I do security updates daily.
On 29th of march, I had an update for systemd :

2018-03-29 21:53:53 startup archives unpack
2018-03-29 21:53:59 upgrade libsystemd0:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:53:59 status triggers-pending libc-bin:amd64 2.24-11+deb9u3
2018-03-29 21:53:59 status half-configured libsystemd0:amd64 232-25+deb9u2
2018-03-29 21:53:59 status unpacked libsystemd0:amd64 232-25+deb9u2
2018-03-29 21:53:59 status half-installed libsystemd0:amd64 232-25+deb9u2
2018-03-29 21:53:59 status half-installed libsystemd0:amd64 232-25+deb9u2
2018-03-29 21:54:00 status unpacked libsystemd0:amd64 232-25+deb9u3
2018-03-29 21:54:00 status unpacked libsystemd0:amd64 232-25+deb9u3
2018-03-29 21:54:00 startup packages configure
2018-03-29 21:54:00 configure libsystemd0:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:00 status unpacked libsystemd0:amd64 232-25+deb9u3
2018-03-29 21:54:00 status half-configured libsystemd0:amd64 232-25+deb9u3
2018-03-29 21:54:00 status installed libsystemd0:amd64 232-25+deb9u3
2018-03-29 21:54:00 startup archives unpack
2018-03-29 21:54:00 upgrade libnss-myhostname:amd64 232-25+deb9u2
232-25+deb9u3
2018-03-29 21:54:00 status half-configured libnss-myhostname:amd64
232-25+deb9u2
2018-03-29 21:54:01 status unpacked libnss-myhostname:amd64 232-25+deb9u2
2018-03-29 21:54:01 status half-installed libnss-myhostname:amd64
232-25+deb9u2
2018-03-29 21:54:01 status triggers-pending man-db:amd64 2.7.6.1-2
2018-03-29 21:54:01 status half-installed libnss-myhostname:amd64
232-25+deb9u2
2018-03-29 21:54:01 status unpacked libnss-myhostname:amd64 232-25+deb9u3
2018-03-29 21:54:01 status unpacked libnss-myhostname:amd64 232-25+deb9u3
2018-03-29 21:54:01 upgrade libpam-systemd:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:54:01 status half-configured libpam-systemd:amd64
232-25+deb9u2
2018-03-29 21:54:01 status unpacked libpam-systemd:amd64 232-25+deb9u2
2018-03-29 21:54:01 status half-installed libpam-systemd:amd64 232-25+deb9u2
2018-03-29 21:54:02 status half-installed libpam-systemd:amd64 232-25+deb9u2
2018-03-29 21:54:02 status unpacked libpam-systemd:amd64 232-25+deb9u3
2018-03-29 21:54:02 status unpacked libpam-systemd:amd64 232-25+deb9u3
2018-03-29 21:54:02 upgrade systemd:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:54:02 status half-configured systemd:amd64 232-25+deb9u2
2018-03-29 21:54:02 status unpacked systemd:amd64 232-25+deb9u2
2018-03-29 21:54:02 status half-installed systemd:amd64 232-25+deb9u2
2018-03-29 21:54:02 status triggers-pending dbus:amd64 1.10.26-0+deb9u1
2018-03-29 21:54:03 status triggers-pending dbus:amd64 1.10.26-0+deb9u1
2018-03-29 21:54:03 status half-installed systemd:amd64 232-25+deb9u2
2018-03-29 21:54:03 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:03 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:04 upgrade udev:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:54:04 status half-configured udev:amd64 232-25+deb9u2
2018-03-29 21:54:04 status unpacked udev:amd64 232-25+deb9u2
2018-03-29 21:54:04 status half-installed udev:amd64 232-25+deb9u2
2018-03-29 21:54:04 status half-installed udev:amd64 232-25+deb9u2
2018-03-29 21:54:05 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:05 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:05 upgrade libudev1:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:54:05 status half-configured libudev1:amd64 232-25+deb9u2
2018-03-29 21:54:06 status unpacked libudev1:amd64 232-25+deb9u2
2018-03-29 21:54:06 status half-installed libudev1:amd64 232-25+deb9u2
2018-03-29 21:54:06 status half-installed libudev1:amd64 232-25+deb9u2
2018-03-29 21:54:06 status unpacked libudev1:amd64 232-25+deb9u3
2018-03-29 21:54:06 status unpacked libudev1:amd64 232-25+deb9u3
2018-03-29 21:54:06 startup packages configure
2018-03-29 21:54:06 configure libudev1:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:06 status unpacked libudev1:amd64 232-25+deb9u3
2018-03-29 21:54:06 status half-configured libudev1:amd64 232-25+deb9u3
2018-03-29 21:54:06 status installed libudev1:amd64 232-25+deb9u3
2018-03-29 21:54:06 configure systemd:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:06 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:06 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:06 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:06 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:06 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status unpacked systemd:amd64 232-25+deb9u3
2018-03-29 21:54:07 status half-configured systemd:amd64 232-25+deb9u3
2018-03-29 21:54:08 status installed systemd:amd64 232-25+deb9u3
2018-03-29 21:54:08 startup archives unpack
2018-03-29 21:54:08 upgrade systemd-sysv:amd64 232-25+deb9u2 232-25+deb9u3
2018-03-29 21:54:08 status half-configured systemd-sysv:amd64 232-25+deb9u2
2018-03-29 21:54:08 status unpacked systemd-sysv:amd64 232-25+deb9u2
2018-03-29 21:54:08 status half-installed systemd-sysv:amd64 232-25+deb9u2
2018-03-29 21:54:09 status half-installed systemd-sysv:amd64 232-25+deb9u2
2018-03-29 21:54:09 status unpacked systemd-sysv:amd64 232-25+deb9u3
2018-03-29 21:54:09 status unpacked systemd-sysv:amd64 232-25+deb9u3
2018-03-29 21:54:09 startup packages configure
2018-03-29 21:54:09 configure libnss-myhostname:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:09 status unpacked libnss-myhostname:amd64 232-25+deb9u3
2018-03-29 21:54:09 status half-configured libnss-myhostname:amd64
232-25+deb9u3
2018-03-29 21:54:09 status installed libnss-myhostname:amd64 232-25+deb9u3
2018-03-29 21:54:09 configure systemd-sysv:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:09 status unpacked systemd-sysv:amd64 232-25+deb9u3
2018-03-29 21:54:09 status half-configured systemd-sysv:amd64 232-25+deb9u3
2018-03-29 21:54:09 status installed systemd-sysv:amd64 232-25+deb9u3
2018-03-29 21:54:09 trigproc libc-bin:amd64 2.24-11+deb9u3 <aucune>
2018-03-29 21:54:09 status half-configured libc-bin:amd64 2.24-11+deb9u3
2018-03-29 21:54:10 status installed libc-bin:amd64 2.24-11+deb9u3
2018-03-29 21:54:10 configure udev:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status unpacked udev:amd64 232-25+deb9u3
2018-03-29 21:54:10 status half-configured udev:amd64 232-25+deb9u3
2018-03-29 21:54:11 status installed udev:amd64 232-25+deb9u3
2018-03-29 21:54:11 status triggers-pending initramfs-tools:all 0.130
2018-03-29 21:54:11 trigproc man-db:amd64 2.7.6.1-2 <aucune>
2018-03-29 21:54:11 status half-configured man-db:amd64 2.7.6.1-2
2018-03-29 21:54:12 status installed man-db:amd64 2.7.6.1-2
2018-03-29 21:54:12 trigproc dbus:amd64 1.10.26-0+deb9u1 <aucune>
2018-03-29 21:54:12 status half-configured dbus:amd64 1.10.26-0+deb9u1
2018-03-29 21:54:12 status installed dbus:amd64 1.10.26-0+deb9u1
2018-03-29 21:54:12 configure libpam-systemd:amd64 232-25+deb9u3 <aucune>
2018-03-29 21:54:12 status unpacked libpam-systemd:amd64 232-25+deb9u3
2018-03-29 21:54:12 status half-configured libpam-systemd:amd64
232-25+deb9u3
2018-03-29 21:54:13 status installed libpam-systemd:amd64 232-25+deb9u3
2018-03-29 21:54:13 trigproc initramfs-tools:all 0.130 <aucune>
2018-03-29 21:54:13 status half-configured initramfs-tools:all 0.130
2018-03-29 21:54:24 status installed initramfs-tools:all 0.130

I checked that there was no security update for Systemd.
Moreover, if I look at one package in particular, let's say libsystemd0,
the update log says it is now deb9u3 version but the debian package page
says it is still deb9u2.
https://packages.debian.org/search?keywords=libsystemd0&searchon=names&suite=stretch&section=all

Today I reinstalled Debian from scratch on my laptop using my net install
CD.
It installed again libsystemd deb9u3, etc.
2018-04-02 15:19:10 upgrade libsystemd0:amd64 232-25+deb9u1 232-25+deb9u3

What is this update that is referenced nowhere ? hacking ?

Thanks, best regards,
   Laurent Lyaudet

[toc] | [next] | [standalone]

#194407

FromSven Joachim <svenjoac@gmx.de>
Date2018-04-02 19:20 +0200
Message-ID<vAbhF-4iN-37@gated-at.bofh.it>
In reply to#194405
On 2018-04-02 18:16 +0200, Laurent Lyaudet wrote:

> I'm using Stretch. I do security updates daily.
> On 29th of march, I had an update for systemd :

> I checked that there was no security update for Systemd.
> Moreover, if I look at one package in particular, let's say libsystemd0,
> the update log says it is now deb9u3 version but the debian package page
> says it is still deb9u2.
> https://packages.debian.org/search?keywords=libsystemd0&searchon=names&suite=stretch&section=all

> Today I reinstalled Debian from scratch on my laptop using my net install
> CD.
> It installed again libsystemd deb9u3, etc.
> 2018-04-02 15:19:10 upgrade libsystemd0:amd64 232-25+deb9u1 232-25+deb9u3
>
> What is this update that is referenced nowhere ? hacking ?

No, this was an upload to stretch-updates, and it has been announced on
the list dedicated for such updates:

https://lists.debian.org/debian-stable-announce/2018/03/msg00001.html

Cheers,
       Sven

[toc] | [prev] | [next] | [standalone]

#194419

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2018-04-02 21:20 +0200
Message-ID<vAd9L-5zO-1@gated-at.bofh.it>
In reply to#194405
On Mon 02 Apr 2018 at 18:16:15 (+0200), Laurent Lyaudet wrote:
> I'm using Stretch. I do security updates daily.
> On 29th of march, I had an update for systemd :
> 
> 2018-03-29 21:53:53 startup archives unpack
> 2018-03-29 21:53:59 upgrade libsystemd0:amd64 232-25+deb9u2 232-25+deb9u3
> 2018-03-29 21:53:59 status triggers-pending libc-bin:amd64 2.24-11+deb9u3
[…]
> 2018-03-29 21:54:13 status installed libpam-systemd:amd64 232-25+deb9u3
> 2018-03-29 21:54:13 trigproc initramfs-tools:all 0.130 <aucune>
> 2018-03-29 21:54:13 status half-configured initramfs-tools:all 0.130
> 2018-03-29 21:54:24 status installed initramfs-tools:all 0.130
> 
> I checked that there was no security update for Systemd.
> Moreover, if I look at one package in particular, let's say libsystemd0,
> the update log says it is now deb9u3 version but the debian package page
> says it is still deb9u2.
> https://packages.debian.org/search?keywords=libsystemd0&searchon=names&suite=stretch&section=all
> 
> Today I reinstalled Debian from scratch on my laptop using my net install
> CD.
> It installed again libsystemd deb9u3, etc.
> 2018-04-02 15:19:10 upgrade libsystemd0:amd64 232-25+deb9u1 232-25+deb9u3
> 
> What is this update that is referenced nowhere ? hacking ?

It might be more pleasant to look at /var/log/apt/history.log rather
than /var/log/dpkg.log which looks more like debug output than a log.

(Both logs should have been rotated since the above, so .1
will have been appended to the previous month's filenames.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194455

FromLaurent Lyaudet <laurent.lyaudet@gmail.com>
Date2018-04-03 20:20 +0200
Message-ID<vAyHf-33z-3@gated-at.bofh.it>
In reply to#194419
>No, this was an upload to stretch-updates, and it has been announced on
>the list dedicated for such updates:
>
>https://lists.debian.org/debian-stable-announce/2018/03/msg00001.html
>
>Cheers,
>       Sven

Thanks Sven.
I didn't knew about this list.
It's good to know that the debian page of a package may not be up to
date and that some updates are announced on another list.
I see two things to enhance :
 - have automatic updates of debian pages of packages according to
current version
 - have a webpage that lists both security updates and SUA (I checked
that the debian-stable-announce doesn't list security updates)

2018-04-02 20:58 GMT+02:00 David Wright <deblis@lionunicorn.co.uk>:
> It might be more pleasant to look at /var/log/apt/history.log rather
> than /var/log/dpkg.log which looks more like debug output than a log.
>
> (Both logs should have been rotated since the above, so .1
> will have been appended to the previous month's filenames.)
>
> Cheers,
> David.
>

Thanks David. The /var/log/apt/history.log is indeed more clearer.

Today I have this:
  Start-Date: 2018-04-03  19:29:28
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: apache2-bin:amd64 (2.4.25-3+deb9u3, 2.4.25-3+deb9u4)
  End-Date: 2018-04-03  19:29:35
but I did not install apache.
I tried this:
  root@Laurent-Portable:/home/laurent# service apache2 stop
  Failed to stop apache2.service: Unit apache2.service not loaded.
  root@Laurent-Portable:/home/laurent# service apache2 start
  Failed to start apache2.service: Unit apache2.service not found.

I don't understand why I have apache2-bin installed but apache is not there???

Thanks, best regards,
   Laurent Lyaudet

[toc] | [prev] | [next] | [standalone]

#194459

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2018-04-03 21:50 +0200
Message-ID<vAA6l-3PH-9@gated-at.bofh.it>
In reply to#194455
On Tue 03 Apr 2018 at 19:58:23 (+0200), Laurent Lyaudet wrote:
> 2018-04-02 20:58 GMT+02:00 David Wright <deblis@lionunicorn.co.uk>:
> > It might be more pleasant to look at /var/log/apt/history.log rather
> > than /var/log/dpkg.log which looks more like debug output than a log.

> Thanks David. The /var/log/apt/history.log is indeed more clearer.
> 
> Today I have this:
>   Start-Date: 2018-04-03  19:29:28
>   Commandline: /usr/bin/unattended-upgrade
>   Upgrade: apache2-bin:amd64 (2.4.25-3+deb9u3, 2.4.25-3+deb9u4)
>   End-Date: 2018-04-03  19:29:35
> but I did not install apache.
> I tried this:
>   root@Laurent-Portable:/home/laurent# service apache2 stop
>   Failed to stop apache2.service: Unit apache2.service not loaded.
>   root@Laurent-Portable:/home/laurent# service apache2 start
>   Failed to start apache2.service: Unit apache2.service not found.
> 
> I don't understand why I have apache2-bin installed but apache is not there???

$ aptitude why apache2-bin

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194462

FromAbdullah Ramazanoglu <ar018@yahoo.com>
Date2018-04-03 22:40 +0200
Message-ID<vAASJ-4pm-1@gated-at.bofh.it>
In reply to#194459
On Tue, 3 Apr 2018 14:24:54 -0500 David Wright said:

> On Tue 03 Apr 2018 at 19:58:23 (+0200), Laurent Lyaudet wrote:
> 
>> I don't understand why I have apache2-bin installed but apache is
>> not there???  
> 
> $ aptitude why apache2-bin

Or, if you have not installed aptitude,

$ apt-cache --installed rdepends apache2-bin

Regards
-- 
Abdullah Ramazanoglu

[toc] | [prev] | [next] | [standalone]

#194495

FromLaurent Lyaudet <laurent.lyaudet@gmail.com>
Date2018-04-04 19:50 +0200
Message-ID<vAUHM-17T-9@gated-at.bofh.it>
In reply to#194462
2018-04-03 22:14 GMT+02:00 Abdullah Ramazanoglu <ar018@yahoo.com>:
> On Tue, 3 Apr 2018 14:24:54 -0500 David Wright said:
>
>> On Tue 03 Apr 2018 at 19:58:23 (+0200), Laurent Lyaudet wrote:
>>
>>> I don't understand why I have apache2-bin installed but apache is
>>> not there???
>>
>> $ aptitude why apache2-bin
>
> Or, if you have not installed aptitude,
>
> $ apt-cache --installed rdepends apache2-bin
>
> Regards
> --
> Abdullah Ramazanoglu
>
>
Thanks David and Abdullah.
It's good to know that gnome-user-share requires apache2-bin.
I've seen that file sharing on the network is off by default anyway.

Best regards,
   Laurent Lyaudet

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web