Am 07.02.2016 um 18:41 schrieb Manfred Hollstein: > Hi there, > > On Wed, 03 Feb 2016, 17:27:06 +0100, Olaf Hering wrote: >> On Wed, Feb 03, Marcus Meissner wrote: >> >>> Please check if this helps. >> >> Thanks. At least the i586 part of 13.1 is in "blocked/scheduled" state >> again. I think the x86_64 part will catch up soon. > > this is not related with any _build_ problems, but rather _using_ the > systemd-210 update. Before (using systemd-208) my systems started > without any issue, but since systemd-210 named doesn't start anymore. > Here is a message from /var/log/messages indicating that there is a > dependency cycle: > > systemd: Job remote-fs.target/stop deleted to break ordering cycle > starting with named.service/stop > > Normally I would expect that named will start up as a result of this > decision, but it does not - which is horrible because all my local names > do not get resolved anymore. Yeah, I could add all those names to > /etc/hosts, but there are way too many systems and using named for it > used to work since years. FWIW, I have now downgraded to 208 again and > locked all relevant packages, and everything is smooth again... > > How and where shall I report this bug? Still openSUSE bugzilla?
I think openSUSE bugzilla makes sense in any case. For systemd I'm not sure who can pick it up for 13.1 though. The update itself was not released yet from the Evergreen maintenance project so I'm not exactly sure what changed etc. Wolfgang
Description: OpenPGP digital signature
_______________________________________________ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen