From doerges@pre-sense.de Tue Mar 31 15:32:50 2020 From: Till =?utf-8?q?D=C3=B6rges?= To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] DoD not working for Leap 15.2 Date: Tue, 31 Mar 2020 17:32:13 +0200 Message-ID: <429e8e77-f480-da5f-0973-a94bcccdfe49@pre-sense.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1704843995197430485==" --===============1704843995197430485== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello all, we're running a private OBS instance (2.9 on x86_64). As openSUSE Leap 15.2 is getting closer to release we of course want to make = sure our software works with it. I therefore tried adding a simple DoD repository which I configured as follow= s: --- snip --- openSUSE Leap 15.2 OSS (DoD) [...] {} {} x86_64 --- snap --- I also copied the PRJCONF for openSUSE:Leap:15.2 from https://api.opensuse.or= g into the local project. It's basically a 1:1 copy from the 15.1 case where it works just fine. But if I enable this new repo for a basic project OBS tells me "nothing provi= des rpm-build, nothing provides gcc-PIE". This obviously isn't true because there is http://download.opensuse.org/distribution/leap/15.2/repo/oss/x86_64/rpm-build= -4.14.1-lp152.15.23.x86_64.rpm I started looking through the logs in /srv/obs/log (and /srv/www/obs/api/log)= but couldn't find a clue. What am I missing or where could I continue to debug this? Thanks a lot and regards -- Till --=20 Dipl.-Inform. Till D=C3=B6rges doerges(a)pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Gesch=C3=A4ftsf=C3=BChrer/Managing Directors AG Hamburg, HRB 107844 Till D=C3=B6rges, J=C3=BCrgen Sander USt-IdNr.: DE263765024 --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============1704843995197430485==-- From adrian@suse.de Tue Mar 31 15:37:53 2020 From: Adrian =?utf-8?q?Schr=C3=B6ter?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] DoD not working for Leap 15.2 Date: Tue, 31 Mar 2020 17:37:51 +0200 Message-ID: <1987672.OBFZWjSADL@linux-izwb.site> In-Reply-To: <429e8e77-f480-da5f-0973-a94bcccdfe49@pre-sense.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5232607838727953386==" --===============5232607838727953386== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Dienstag, 31. M=C3=A4rz 2020, 17:32:13 CEST wrote Till D=C3=B6rges: > Hello all, >=20 > we're running a private OBS instance (2.9 on x86_64). >=20 > As openSUSE Leap 15.2 is getting closer to release we of course want to mak= e sure our > software works with it. >=20 > I therefore tried adding a simple DoD repository which I configured as foll= ows: >=20 > --- snip --- > > openSUSE Leap 15.2 OSS (DoD) > [...] > > > > > > > > > > > url=3D"http://download.opensuse.org/distribution/leap/15.2/repo/oss/" repot= ype=3D"rpmmd"> > {} > {} this looks broken. Either remove it or place a valid gpg key. > > x86_64 > > > --- snap --- >=20 > I also copied the PRJCONF for openSUSE:Leap:15.2 from https://api.opensuse.= org into > the local project. >=20 >=20 > It's basically a 1:1 copy from the 15.1 case where it works just fine. >=20 >=20 >=20 > But if I enable this new repo for a basic project OBS tells me "nothing pro= vides > rpm-build, nothing provides gcc-PIE". because it does not accept the repo, because the gpg validation fails most li= kely > This obviously isn't true because there is > http://download.opensuse.org/distribution/leap/15.2/repo/oss/x86_64/rpm-bui= ld-4.14.1-lp152.15.23.x86_64.rpm >=20 >=20 > I started looking through the logs in /srv/obs/log (and /srv/www/obs/api/lo= g) but > couldn't find a clue. >=20 >=20 > What am I missing or where could I continue to debug this? >=20 >=20 > Thanks a lot and regards -- Till >=20 --=20 Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton, HR= B 21284 (AG N=C3=BCrnberg)=20 =20 Maxfeldstra=C3=9Fe 5 =20 90409 N=C3=BCrnberg=20 Germany=20 --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============5232607838727953386==-- From stefan.seyfried@googlemail.com Tue Mar 31 20:22:08 2020 From: Stefan Seyfried To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] DoD not working for Leap 15.2 Date: Tue, 31 Mar 2020 19:56:48 +0200 Message-ID: In-Reply-To: <429e8e77-f480-da5f-0973-a94bcccdfe49@pre-sense.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1362065453159856642==" --===============1362065453159856642== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 31.03.20 um 17:32 schrieb Till D=C3=B6rges: > Hello all, >=20 > we're running a private OBS instance (2.9 on x86_64). >=20 > As openSUSE Leap 15.2 is getting closer to release we of course want to mak= e sure our > software works with it. >=20 > I therefore tried adding a simple DoD repository which I configured as foll= ows: >=20 > --- snip --- > Does your buildservice have an interconnect to build.opensuse.org? if yes, what's its name/prefix? If the interconnect is named "openSUSE.org" (which is the default...), then I could imagine that this causes some trouble. --=20 Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============1362065453159856642==-- From doerges@pre-sense.de Tue Mar 31 21:00:04 2020 From: Till =?utf-8?q?D=C3=B6rges?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] DoD not working for Leap 15.2 Date: Tue, 31 Mar 2020 18:02:07 +0200 Message-ID: In-Reply-To: <1987672.OBFZWjSADL@linux-izwb.site> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6385073619363021638==" --===============6385073619363021638== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Am 31.03.20 um 17:37 schrieb Adrian Schröter: >> {} >> {} > this looks broken. Either remove it or place a valid gpg key. Removing these two lines did the trick. (I'm a bit curious as to why the problem did not occur for our 15.1 setup.) Thanks for the really quick and helpful answer! :-) Regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6385073619363021638==--