On Sun, Feb 07, 2016 at 06:41:30PM +0100, Manfred Hollstein wrote:
> 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?
To reach the systemd maintainers, use opensuse bugzilla.
I see already a bug opened:
Evergreen mailing list