Bug#854041: systemd: dpkg fails for systemd package when upgrading from jessie to stretch
Package: systemd Version: 215-17+deb8u6 Severity: normal Dear Maintainer, while upgrading from jessie to stretch I encounter the following error with dpkg trying to upgrade systemd package: # apt-get dist-upgrade ... dpkg: systemd: Abhängigkeitsprobleme, wird aber wie gefordert dennoch entfernt: dbus-user-session hängt ab von systemd; aber: Paket systemd soll entfernt werden. systemd-sysv hängt ab von systemd (= 215-17+deb8u6). systemd-sysv hängt ab von systemd. systemd-sysv hängt ab von systemd (= 215-17+deb8u6). systemd-sysv hängt ab von systemd. libpam-systemd:amd64 hängt ab von systemd (= 215-17+deb8u6). (Lese Datenbank ... 307696 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von systemd (215-17+deb8u6) ... systemd is the active init system, please switch to another before removing systemd. dpkg: Fehler beim Bearbeiten des Paketes systemd (--remove): Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück Failed to stop lib-init-rw.mount: Unit lib-init-rw.mount not loaded. addgroup: Die Gruppe »systemd-journal« existiert bereits als Systemgruppe. Programmende. Fehler traten auf beim Bearbeiten von: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) The full output can be found at the following URL: https://gist.github.com/cebe/67c135b990d5c7a92149e4e7113c555c For the upgrade I removed the jessie-backports repository from source.list and replaced "jessie" with "stretch" the apt sources.list file is also included in the URL above. Please let me know if you need further information. best regards, Carsten Brandt -- Package-specific info: -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59.8 ii libacl1 2.2.52-2 ii libaudit1 1:2.6.7-1 ii libblkid1 2.29.1-1 ii libc6 2.24-9 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.7.5-3 ii libkmod218-3 ii liblzma55.2.2-1.2 ii libpam0g1.1.8-3.5 ii libselinux1 2.6-3 iu libsystemd0 232-14 ii mount 2.29.1-1 ii sysv-rc 2.88dsf-59.8 ii udev215-17+deb8u6 ii util-linux 2.29.1-1 Versions of packages systemd recommends: iu dbus1.10.14-1 ii libpam-systemd 215-17+deb8u6 Versions of packages systemd suggests: pn systemd-ui -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: Acknowledgement (systemd: dpkg fails for systemd package when upgrading from jessie to stretch)
I was unsure about the severtiy setting so the bugreport tool changed severty to "normal". Dependent on whether this affects only a small amount of systems or is reproduceable in general, the severty might be much higher. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#853940: systemd: RestrictAddressFamilies causes services to fail to start on powerpc
On 02/02/17 22:37, Phil Armstrong wrote: On 02/02/17 21:50, Michael Biebl wrote: Are you absolutely sure? We had another bug report who said that downgrading systemd+udev to 232-1 did fix the problem on ppc(64). This is a ppc32 system, so maybe that makes the difference? I’ll test it again over the weekend. I must have made an error before: After carefully binary chopping the systemd package versions from snapshot.debian.org, I can report that the last version to work correctly is systemd 232-10. 232-11 fails. Looking at the changelog & the service files, this is kind of unsurprising: the service files for 232-10 don’t contain any RestrictAddressFamilies entries on my system, whereas the ones for 232-11 do & the changelog for 232-11 contains this entry: * Fix RestrictAddressFamilies= Backport upstream fix for setting up seccomp filters to fix RestrictAddressFamilies= on non-amd64 architectures. Drop the hack from debian/rules to remove this property from unit files. See #843160 So either the upstream fix doesn’t work on powerpc32 or the backport is broken somehow. I appreciate that ppc32 is a minority platform at this point. cheers, Phil ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: Info received (Bug#854041: Acknowledgement (systemd: dpkg fails for systemd package when upgrading from jessie to stretch))
I have tried to reproduce this on a clean installation of jessie inside of an LXC container but that went fine. So it seems to be something specific to my system. # on a debian system as root: # on stretch apt-get install lxc # or if you are on jessie you need lxc from the backports to have proper network config out of the box #apt-get install -t jessie-backports lxc # set up lxc networking as described in # https://wiki.debian.org/LXC#Minimal_changes_to_set_up_networking_for_LXC_for_Debian_.2BIBw-stretch.2BIB0_.28testing.29 lxc-create -n test-upgrade -t debian -- -r jessie lxc-start -n test-upgrade -d lxc-attach -n test-upgrade # in the container run the following: sed -i s/jessie/stretch/ /etc/apt/sources.list apt-get update apt-get dist-upgrade ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: Info received (Bug#854041: Info received (Bug#854041: Acknowledgement (systemd: dpkg fails for systemd package when upgrading from jessie to stretch)))
Here is the output of LANG=C apt-get -f install after the failure of apt-get dist-upgrade. https://gist.github.com/cebe/8ddd41ebb40c555dc1d6b276a4283eec There is also this output directly after accepting the upgrade: Traceback (most recent call last): File "/usr/bin/apt-listchanges", line 250, in main() File "/usr/bin/apt-listchanges", line 48, in main debs = apt_listchanges.read_apt_pipeline(config) File "/usr/share/apt-listchanges/apt_listchanges.py", line 98, in read_apt_pipeline del filenames[pkg] KeyError: 'texlive-latex-extra' Not sure it is systemd related anymore. Where else would I report this? ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: systemd: dpkg fails for systemd package when upgrading from jessie to stretch
On 3 February 2017 at 08:03, Carsten Brandt wrote: > > Package: systemd > Version: 215-17+deb8u6 > Severity: normal > > Dear Maintainer, > > while upgrading from jessie to stretch I encounter the following error with > dpkg trying to upgrade systemd package: > > # apt-get dist-upgrade > ... > dpkg: systemd: Abhängigkeitsprobleme, wird aber wie gefordert > dennoch entfernt: > dbus-user-session hängt ab von systemd; aber: > Paket systemd soll entfernt werden. > systemd-sysv hängt ab von systemd (= 215-17+deb8u6). > systemd-sysv hängt ab von systemd. > systemd-sysv hängt ab von systemd (= 215-17+deb8u6). > systemd-sysv hängt ab von systemd. > libpam-systemd:amd64 hängt ab von systemd (= 215-17+deb8u6). > > (Lese Datenbank ... 307696 Dateien und Verzeichnisse sind > derzeit installiert.) > Entfernen von systemd (215-17+deb8u6) ... > systemd is the active init system, please switch to another > before removing systemd. > dpkg: Fehler beim Bearbeiten des Paketes systemd (--remove): > Unterprozess installiertes pre-removal-Skript gab den > Fehlerwert 1 zurück > Failed to stop lib-init-rw.mount: Unit lib-init-rw.mount not > loaded. > addgroup: Die Gruppe »systemd-journal« existiert bereits als > Systemgruppe. Programmende. > Fehler traten auf beim Bearbeiten von: > systemd > E: Sub-process /usr/bin/dpkg returned an error code (1) > > The full output can be found at the following URL: > https://gist.github.com/cebe/67c135b990d5c7a92149e4e7113c555c > Init: systemd (via /run/systemd/system) So, apt decided it needed to temporarily remove systemd for some reason, and systemd errors out because removing systemd while running under it is a bad idea[1]. Dear apt maintainers, any idea on what conditions could result in apt deciding to temporarily remove systemd? [1] https://sources.debian.net/src/systemd/232-15/debian/systemd.prerm/#L10 -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: systemd: dpkg fails for systemd package when upgrading from jessie to stretch
Am 03.02.2017 um 14:04 schrieb Felipe Sateler: > So, apt decided it needed to temporarily remove systemd for some > reason, and systemd errors out because removing systemd while running > under it is a bad idea[1]. > > Dear apt maintainers, any idea on what conditions could result in apt > deciding to temporarily remove systemd? Carsten, can you attach /var/lib/dpkg/status from before the upgrade. This should give us an opportunity to reproduce the problem. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854041: systemd: dpkg fails for systemd package when upgrading from jessie to stretch
Am 03.02.2017 um 14:15 schrieb Michael Biebl: > Carsten, can you attach /var/lib/dpkg/status from before the upgrade. > This should give us an opportunity to reproduce the problem. You can download it from here: https://cloud.cebe.cc/s/D5snvzhWpsLdtyg It is the last version from /var/backups/dpkg.status.0 Btw, the upgrade succeeded after running apt-get -f install and then apt-get dist-upgrade again. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#843251: udev i386 232-15 . .
Not a smooth upgrade but better than udev i386 232-1[3,4]. Both left my test system unbootable Cut from the upgrade terminal. Setting up udev (232-15) ... addgroup: The group `input' already exists as a system group. Exiting. Job for systemd-udevd.service failed because a timeout was exceeded. See "systemctl status systemd-udevd.service" and "journalctl -xe" for details. invoke-rc.d: initscript udev, action "restart" failed. ● systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled) Active: activating (start) since Fri 2017-02-03 14:32:57 UTC; 18ms ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 26844 (systemd-udevd) Tasks: 1 CGroup: /system.slice/systemd-udevd.service └─26844 /lib/systemd/systemd-udevd Feb 03 14:32:57 unassigned-hostname systemd[1]: Starting udev Kernel Device …... Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 To get it right I had to root@unassigned-hostname:/home/datb# dpkg -i udev_232-15_i386.deb (Reading database ... 170141 files and directories currently installed.) Preparing to unpack udev_232-15_i386.deb ... Unpacking udev (232-15) over (232-15) ... Setting up udev (232-15) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (232-15) ... Processing triggers for man-db (2.7.6.1-2) ... Processing triggers for initramfs-tools (0.120) ... update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc4-generic ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#854102: systemd-logind fails to update session's Display property after `startx` from VT
Package: systemd
Version: 232-14
Severity: normal
i start my login on this system on a text-mode console (a "VT") and
then do "exec startx" to transition to a graphical X11 session.
>From within this graphical session, if i query logind about the
Display for the login session, it is the empty string, instead of what
it should be (":0").
logind knows that i'm on "/dev/tty1", according to its TTY property,
which is correct, but it should know the Display as well, since startx
just reuses the same VT for the graphical console.
here's me debugging it:
dkg@test:~$ SESSION_OBJ_PATH=$(busctl call org.freedesktop.login1
/org/freedesktop/login1 org.freedesktop.login1.Manager GetSessionByPID u $$ |
awk '-F"' '/o/{ print $2 }')
dkg@test:~$ busctl get-property org.freedesktop.login1 "$SESSION_OBJ_PATH"
org.freedesktop.login1.Session Display
s ""
$ busctl get-property org.freedesktop.login1 "$SESSION_OBJ_PATH"
org.freedesktop.login1.Session TTY
s "/dev/tty1"
dkg@test:~$
logind should be aware when startx triggers the change and update its
conception of the use of the tty accordingly, though i'm not sure how
that would be done.
I'm looking into this because it would be nice to have anything that's
associated with the user session be able to know what the Display is
for that particular session (i care about this for gpg-agent and
pinentry, as discussed on #debian-systemd, but i'm sure there are
other use cases as well).
Thanks for maintaining systemd in debian!
--dkg
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (200,
'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor12.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcrypt20 1.7.5-3
ii libgpg-error0 1.26-2
ii libidn111.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod223-2
ii liblz4-10.0~r131-2
ii liblzma55.2.2-1.2
ii libmount1 2.29.1-1
ii libpam0g1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3
ii libsystemd0 232-14
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus1.10.14-1
ii libpam-systemd 232-14
Versions of packages systemd suggests:
ii policykit-10.105-17
ii systemd-container 232-14
pn systemd-ui
Versions of packages systemd is related to:
ii dracut 044+189-2
pn initramfs-tools
ii udev 232-14
-- no debconf information
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
