Re: [Evergreen] 13.1 systemd update breaks build - and also *runtime* :(
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[1]: 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 signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build - and also *runtime* :(
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[1]: 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? TIA, cheers. l8er manfred pgpv72cK8TK93.pgp Description: PGP signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build
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. Olaf ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] 13.1 systemd update breaks build
Not sure if this is already an Evergreen or still regular update thing. openSUSE_13.1x86_64 unresolvable: nothing provides this-is-only-for-build-envs needed by libudev-mini1 nothing provides this-is-only-for-build-envs needed by udev-mini Seen in various projects, including PMBS:Essentials/ffmpeg Olaf ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build
Am 03.02.2016 um 16:46 schrieb Olaf Hering: > Not sure if this is already an Evergreen or still regular update thing. > > openSUSE_13.1x86_64 unresolvable: nothing provides > this-is-only-for-build-envs needed by libudev-mini1 > nothing provides this-is-only-for-build-envs needed by udev-mini > > Seen in various projects, including PMBS:Essentials/ffmpeg systemd was released still from the official maintenance queue. That does not mean necessarily that we do not have to do something about it from our side though. Any help is appreciated. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build
On Wed, Feb 03, 2016 at 05:03:45PM +0100, Adrian Schröter wrote: > On Mittwoch, 3. Februar 2016, 16:55:11 CET wrote Wolfgang Rosenauer: > > Am 03.02.2016 um 16:46 schrieb Olaf Hering: > > > Not sure if this is already an Evergreen or still regular update thing. > > > > > > openSUSE_13.1x86_64 unresolvable: nothing provides > > > this-is-only-for-build-envs needed by libudev-mini1 > > > nothing provides this-is-only-for-build-envs needed by udev-mini > > > > > > Seen in various projects, including PMBS:Essentials/ffmpeg > > > > systemd was released still from the official maintenance queue. > > That does not mean necessarily that we do not have to do something about it > > from > > our side though. Any help is appreciated. > > This should help: > > eosc meta prjconf openSUSE:13.2 | grep this-is-only-for-build-envs > Ignore: systemd-mini:this-is-only-for-build-envs > Ignore: udev-mini:this-is-only-for-build-envs > Ignore: libudev-mini1:this-is-only-for-build-envs > Ignore: jdk-bootstrap:this-is-only-for-build-envs I have now added Ignore: systemd-mini:this-is-only-for-build-envs Ignore: udev-mini:this-is-only-for-build-envs Ignore: libudev-mini1:this-is-only-for-build-envs to openSUSE:13.1:Update prjconf. Please check if this helps. Ciao, Marcus ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
