systemd-220 in unstable

[ralul]

Caution!
Achtung Baby!

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

[ralul]

Just reading the systemd-220 ChangeLogs further before I consider any upgrade:

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 ...

[domicius]

While caution is definitely advised, here's the word from Martin Pitt, the uploader: https://plus.google.com/+MartinPitti/posts/YQrLh2nZfhs

[dibl]

I have just updated two very different siduction/systemd systems and see no problems whatsoever.

[Millie]

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.

[bluelupo]

It works fine here!

[melmarker]

if it works fine - fine - don't do anything . In case some services behave strange one have eventually do some cleanup. Will post some things later.

[ralul]

It works fine here!

Everybody who reads the Debian bugs must admit
systemd is maintained in an unbeatable diligent fashion.

There are no known regressions;the issues that we found in 220 are patched,

... and coordinated work with Ubuntu splendidly happens.

[musca]

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

[ralul]

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.

[DeepDayze]

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

Looks like there's a fix coming for that bug...hang tight

[graviton]

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.

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

[reddark]

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 .... 

[musca]

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

[reddark]

@musca

danke .... gut das ich gewartet hab ...