Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: ralul on 2015/05/30, 09:39:22

Title: systemd-220 in unstable
Post by: ralul on 2015/05/30, 09:39:22
Caution!
Achtung Baby!
Quote
systemd (220-2) unstable; urgency=low
  * 220-1 was meant to go to experimental, but was accidentally uploaded to
    unstable. This was planned for next week anyway, just not on a Friday;     
    we don't revert, but keep an RC bug open for a few days to get broader   
    testing. Reupload 220-1 with its changelog actually pointing to unstable   
    and with all versions in the .changes.                                                                 
 -- Martin Pitt <mpitt@debian.org>  Fri, 29 May 2015 18:54:09 +0200
Title: Re: systemd-220 in unstable
Post by: ralul on 2015/05/30, 09:57:46
Just reading the systemd-220 ChangeLogs further before I consider any upgrade:
Quote
Remove our update-rc.d patches, replace them with upstream patches for
    /lib/systemd/systemd-sysv-install abstraction, and provide one for 
    update-rc.d. Also implement "is-enabled" command by directly checking for
    the presence of rcS or rc5 symlinks. (Closes: #760616)
Now, this sounds brave: Removing some of the downstream Debian hackery ...
Title: Re: systemd-220 in unstable
Post by: domicius on 2015/05/30, 13:12:39
While caution is definitely advised, here's the word from Martin Pitt, the uploader: https://plus.google.com/+MartinPitti/posts/YQrLh2nZfhs (https://plus.google.com/+MartinPitti/posts/YQrLh2nZfhs)
Title: Re: systemd-220 in unstable
Post by: dibl on 2015/05/30, 15:01:49
I have just updated two very different siduction/systemd systems and see no problems whatsoever.
Title: Re: systemd-220 in unstable
Post by: Millie on 2015/05/30, 15:25:57
What impact does this have on the system?  I followed the link, but can't find any info about how this impacts the system.

I have 215-18 on this computer and 220-2 on my other Siduction computer. As dibl said above, I haven't experienced any problem with the 220-2 machine.
Title: Re: systemd-220 in unstable
Post by: bluelupo on 2015/05/30, 15:45:27
It works fine here!
Title: Re: systemd-220 in unstable
Post by: melmarker on 2015/05/30, 15:58:37
if it works fine - fine - don't do anything :P. In case some services behave strange one have eventually do some cleanup. Will post some things later.
Title: Re: systemd-220 in unstable
Post by: ralul on 2015/05/30, 16:31:36
It works fine here!
Everybody who reads the Debian bugs must admit
systemd is maintained in an unbeatable diligent fashion.
Quote from: Martin Pitt
There are no known regressions;the issues that we found in 220 are patched,
... and coordinated work with Ubuntu splendidly happens.
Title: Re: systemd-220 in unstable
Post by: musca on 2015/05/31, 13:40:29
hello,

udev (part of systemd) has an issue which breaks network for "allow-hotplug" devices configured in /etc/network/interfaces.
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263

This will affect users of our former tool ceni which uses allow-hotplug for wired interfaces.

Users should switch to either systemd-networkd or connman or network-manager.
I think we should have a new thread on each subtopic.

greetings
musca
Title: Re: systemd-220 in unstable
Post by: ralul on 2015/05/31, 18:04:19
Users using the initrd tool dracut instead of Debian official tools
will not be able to mount, because sysinit/rootfs...fsck.service fails.

My observation:
Since systemd-220 all of files /lib/systemd/system/dracut....service
are wiped out, despite I have done a re-install of dracut.
There is no Debian bug about the issue. Obviously nobody uses dracut :(

I did begin using dracut since I switched to systemd before Debian officially did.
Thought a good idea. But I am not hit as much as I can use my self compiled kernels
which are not in need of any initrd: "make localyesconfig" did that trick.
Title: Re: systemd-220 in unstable
Post by: DeepDayze on 2015/05/31, 20:03:27
hello,

udev (part of systemd) has an issue which breaks network for "allow-hotplug" devices configured in /etc/network/interfaces.
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263)

This will affect users of our former tool ceni which uses allow-hotplug for wired interfaces.

Users should switch to either systemd-networkd or connman or network-manager.
I think we should have a new thread on each subtopic.

greetings
musca
Looks like there's a fix coming for that bug...hang tight :)
Title: Re: systemd-220 in unstable
Post by: graviton on 2015/06/01, 08:01:24
udev (part of systemd) has an issue which breaks network for "allow-hotplug" devices configured in /etc/network/interfaces.
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263)

This will affect users of our former tool ceni which uses allow-hotplug for wired interfaces.

I can confirm this problem as it occurs on two of my computers with aptosid-systemd systems. Ceni takes no interfaces (for example: eth0 on the PC and Notebook with wlan0).  A manual start with "ifup eth0" or "ifup wlan0" works, but does not solve the real problem.

Users should switch to either systemd-networkd or connman or network-manager.
I think we should have a new thread on each subtopic.

A change seems to make sense, a thread for systemd-networkd would be useful!

graviton
Title: Re: systemd-220 in unstable
Post by: reddark on 2015/06/01, 11:29:57
So, jetzt bitte ne kleine Kurzfassung auf Deutsch .. ;)
Google-Übersetzung und meine schwachen Englischkenntnisse erwecken bei mir nicht das Vertrauen, das ich alles richtig verstehe .... ;)

Danke ....  8)
Title: systemd-220-3 is in incoming ...
Post by: musca on 2015/06/01, 14:30:40
Hello,

... and it will bring the fixed version of udev 220-3, see changelog:
  * sd-device: fix device_get_properties_strv(). Fixes environment for
    processes spawned by udev, in particular "allow-hoplug" ifupdown
    interfaces via ifup@.service. (Closes: #787263)


so just wait 3 or 4 hours more before you dist-upgrade.

greetings
musca

Hallo reddark,
durch einen Bug in udev funktioniert die klassische Netzwerkkonfiguration momentan nicht, so dass Anwender von Ceni betroffen sind.
Mit dem nächsten Repo-Sync in etwa 3-4 Stunden kommt der Fix.

Grüße
musca
Title: Re: systemd-220 in unstable
Post by: reddark on 2015/06/01, 14:34:13
@musca

danke .... gut das ich gewartet hab ... ;)
Title: Re: systemd-220 in unstable
Post by: jure on 2015/06/01, 19:01:55
Quote
apt-cache policy systemd
systemd:
  Installiert:           215-18
  Installationskandidat: 220-3
  Versionstabelle:
     220-3 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
Quote from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787263
Source: systemd
Source-Version: 220-3

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.
........
Changes:
 systemd (220-3) unstable; urgency=medium
 .
   * Fix ProtectSystem=yes to actually protect /usr, not /home.
     (Closes: #787343)
   * sd-device: fix device_get_properties_strv(). Fixes environment for
     processes spawned by udev, in particular "allow-hoplug" ifupdown
     interfaces via ifup@.service. (Closes: #787263)
   * Ignore test failures on mipsel; the three failures are not reproducible on
     the porter box (different kernel?). (See #787258)
   * Add ifupdown-hotplug autopkgtest. Reproduces #787263.
   * udev: Bring back persistant storage symlinks for bcache. Thanks David
     Mohr! (Closes: #787367)
   * sd-device: Fix invalid property strv pointers. This unbreaks the
     environment of udev callouts.
Title: Re: systemd-220 in unstable
Post by: Jörg on 2015/06/03, 08:11:06
udev and systemd DU-ed to most recent version 220-4, but still no wireless-internet connection. Is there still any hope for ceni-users (like me) by waiting a few more days? or will systemd-networkd, connman, or network-manager be the future alternatives?

Greetings,
Jörg
Title: Re: systemd-220 in unstable
Post by: melmarker on 2015/06/03, 11:41:14
@Jörg: Good question, for LXDE and LXQt i think i will prefer connman and cmst as frontend
Title: Re: systemd-220 in unstable
Post by: Jörg on 2015/06/03, 11:54:48
@melmarker: and your advice for KDE?
Title: Re: systemd-220 in unstable
Post by: devil on 2015/06/03, 14:39:31
On a dist-upgraded 64-bit wired  KDE install ceni works just fine, no idea why :)


greetz
devil
Title: Re: systemd-220 in unstable
Post by: Jörg on 2015/06/03, 16:19:35
On my system ceni gives ... Hardware devices: no values!
Title: Re: systemd-220 in unstable
Post by: melmarker on 2015/06/03, 16:59:24
@Jörg: hmm - i will have a look at ceni, maybe the upstream changes solve it.
Title: Re: systemd-220 in unstable
Post by: Jörg on 2015/06/20, 09:11:41
After two weeks of "waiting & thinking" the only way of setting up a wireless internet connection is:

Code: [Select]
[08:11:36] root@thinkpad-s540:/home/jorg# ifup wlan0
wpa_supplicant: wpa_action is managing ifup/ifdown state of wlan0
wpa_supplicant: execute `ifdown --force wlan0' to stop wpa_action
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Failed to bring up wlan0.
[08:11:46] root@thinkpad-s540:/home/jorg#

Nevertheless the message "Failed to bring up wlan0", the wireless internet connection works until shutdown of the computer. After every new start I have to type in the root-console "ifup wlan0" again. Any explanation and help is welcome - thank you in advance.

Greetings,
Jörg
Title: Re: systemd-220 in unstable
Post by: bluelupo on 2015/06/20, 12:25:00
Hi Jörg,

have you switched to the new "systemd-networkd"? Perhaps this helps to get around your problem with the WLAN.

More info here (only in german):
http://forum.siduction.org/index.php?topic=5571.0
http://forum.siduction.org/index.php?topic=5580.0
Title: Re: systemd-220 in unstable
Post by: melmarker on 2015/06/20, 12:29:30
connman and cmst work too