From mhollstein@t-online.de Fri Sep 6 13:44:30 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 06 Sep 2019 15:44:04 +0200 Message-ID: <20190906134404.GC4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5070322722736024044==" --===============5070322722736024044== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi there, I've given up (I think) trying to understand why OBS sometimes behaves different than what I'd expect. Here is my (current) challenge: I'm trying to build firefox69 in my own project in home:manfred-h:mozilla. The repository metadata is set up as follows: $ osc meta prj home:manfred-h:mozilla mozilla Mozilla based projects and support packages. x86_64 x86_64 x86_64 As you can see, nothing should get build by default (this is enabled purely on a package by package case) and repositories are setup so that "rust" and related packages should be taken from - devel:languages:rust for openSUSE_Leap_15.1 - home:manfred-h:devel:languages:rust for 42.3 and 15.0 firefox69 now needs rust-cbindgen >=3D 0.9.0, so I copied that package to my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 Still OBS thinks "nothing provides rust-cbindgen >=3D 0.9.0" for 15.0 and 42.3, but the packages are there: both providing: rust-cbindgen =3D 0.9.0-1.1 =09 rust-cbindgen(x86-64) =3D 0.9.0-1.1 FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to rust-cbindgen in the home:manfred-h:devel:languages:rust project, but this did not change anything unfortunately. Can anybody tell me what I'm doing wrong here? Or is this a bug in the OBS resolver? TIA, cheers. l8er manfred PS: No complaints wrt/ 42.3, I'm not yet done with migrating all systems I maintain to 15.1 yet! Therefore I'm trying to keep those packages still building which are not services but still as close to the Internet as possible, i.e. the _bad world_ ;) --===============5070322722736024044== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxeVlxUUFDZ2tRcjNhVEx6VHIKQWVrM3FBLzdCdlgzZytTWkR2 cSt2bVZwdjJLQUhwVmJhdHMySjhTcUFzdHFXUWdNTklsZnVtenJJanlrSlIrRwpjd2NOYzF6OURj cFBNc1F5TElia1JzeUpqUXFNUHdwa0diOE1idVNROTZjREF4bDRsdUVqTnhuZnhyVDlPYmVMCk8v RDlTV2VhVFZLZWY3cGNvYWk4NHk3SmlMR2paYXFjaExPN2VNQ1lPMEs1MVZxdWVNUU9CTjgxdFdP SW5rQnoKc05aY2wzTzJKa1l4M0E2MDh3U2dmUWR0amlScUhkUkMydkxHUGVBTk5WWk1EWHhNMmpa UHBxU3ozQ05ZazFvMQoraEhFWm5YWjdrbWdBQ0YwbXRyNHFUZ095UFdNNjc5bEJuSVNoZmhTUGlu c3ZZaGxXSWtNZDlNSmRXaDZWWlNTCmVzWWE3U2xGeEE3SFk5MTFBUlZyOFR6VUlZNUhvaUxGZ1Fp V0dmTTQ2TkNtSWl5cVpuRzNLeDVPbGZFTHZXYTEKdzMrZHR1UURvNEEzbVAyZWJQUkMvamhCYlkz cXlGcFpyNk9ubzRYa3lxaXpEb3BTY21uVEVtMVBKLzJmTjNKTAp4WU02R0QySVdtdDZpejY2Y3dK ZW1IZTRIeHpaOWdock5tQW84NTJVR1VLT0hGS2pobnVhUWx0b2FXa0FwUjErClovUkp4RDQ5ZnJC VkdmR3c1cThTd01kazV6S1pnSmIyOERkcStUK3EzY0JJakNrT0lzWjdiL25wWnMyR0xqRkwKVnRt a2tpZGJzOFJIZ2VBNEFTRW5jc1c2SjNyU01Hc3lTTkY5Uk9XSlEyWk12K1BSY2dXbnFDbzJYamN4 N2kxVQpJRWVsamFlalYxWnlTZTkvY2pUZWM5L3IzR1gweXhzS1JLbFV2TUhISlZrSStIMmdHUW89 Cj11azJtCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============5070322722736024044==-- From adrian@suse.de Fri Sep 6 13:55:27 2019 From: Adrian =?utf-8?q?Schr=C3=B6ter?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 06 Sep 2019 15:54:14 +0200 Message-ID: <2060454.vZzipiRFKg@linux-ywca> In-Reply-To: <20190906134404.GC4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6725461074454859528==" --===============6725461074454859528== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Freitag, 6. September 2019, 15:44:04 CEST Manfred Hollstein wrote: > Hi there, > > I've given up (I think) trying to understand why OBS sometimes behaves > different than what I'd expect. > > Here is my (current) challenge: > > I'm trying to build firefox69 in my own project in > home:manfred-h:mozilla. The repository metadata is set up as follows: > > $ osc meta prj home:manfred-h:mozilla > > mozilla > > Mozilla based projects and support packages. > > > > > > > repository="openSUSE_Leap_42.3"/> repository="openSUSE_Leap_42.3"/> > > > x86_64 > > > > > > > x86_64 > > > repository="openSUSE_Leap_15.0"/> repository="openSUSE_Leap_15.0"/> > > > x86_64 > > > > As you can see, nothing should get build by default (this is enabled > purely on a package by package case) and repositories are setup so > that "rust" and related packages should be taken from > > - devel:languages:rust for openSUSE_Leap_15.1 > - home:manfred-h:devel:languages:rust for 42.3 and 15.0 > > firefox69 now needs rust-cbindgen >= 0.9.0, so I copied that package to > my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built > it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 > > Still OBS thinks "nothing provides rust-cbindgen >= 0.9.0" for 15.0 and > 42.3, but the packages are there: > > > ust/rust-cbindgen-0.9.0/openSUSE_Leap_15.0/x86_64/rust-cbindgen-0.9.0-lp150. > 1.1.x86_64.rpm> > ust/rust-cbindgen-0.9.0/openSUSE_Leap_42.3/x86_64/rust-cbindgen-0.9.0-1.1.x8 > 6_64.rpm> > > both providing: > > rust-cbindgen = 0.9.0-1.1 > rust-cbindgen(x86-64) = 0.9.0-1.1 > > FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to > rust-cbindgen in the home:manfred-h:devel:languages:rust project, but > this did not change anything unfortunately. > > Can anybody tell me what I'm doing wrong here? Or is this a bug in the > OBS resolver? I don't see it unresolvable in home:manfred-h:mozilla, but blocked. please note that events between repos in different projects are handled with low prio. So it might take some time to see an effect. Use "osc buildinfo" to debug a dependency issue instead, it does a current evaluation. -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6725461074454859528==-- From schwab@linux-m68k.org Fri Sep 6 13:58:58 2019 From: Andreas Schwab To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 06 Sep 2019 15:58:55 +0200 Message-ID: <87woela5ls.fsf@igel.home> In-Reply-To: <20190906134404.GC4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0320787152066277708==" --===============0320787152066277708== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Sep 06 2019, Manfred Hollstein wrote: > Still OBS thinks "nothing provides rust-cbindgen >= 0.9.0" for 15.0 and > 42.3, but the packages are there: The package is currently building, maybe you didn't wait long enough for the scheduler to pick up the newly built packages? Andreas. -- Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============0320787152066277708==-- From mhollstein@t-online.de Fri Sep 6 14:04:43 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 06 Sep 2019 16:04:39 +0200 Message-ID: <20190906140439.GD4608@saturn.hollstein.homelinux.org> In-Reply-To: <20190906134404.GC4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6187635891108873714==" --===============6187635891108873714== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Fri, 06 Sep 2019, 15:44:04 +0200, Manfred Hollstein wrote: > Hi there, >=20 > I've given up (I think) trying to understand why OBS sometimes behaves > different than what I'd expect. >=20 > Here is my (current) challenge: >=20 > I'm trying to build firefox69 in my own project in > home:manfred-h:mozilla. The repository metadata is set up as follows: >=20 > $ osc meta prj home:manfred-h:mozilla > > mozilla > > Mozilla based projects and support packages. > > > > > > > > > > > x86_64 > > > > > > > x86_64 > > > > > > > x86_64 > > >=20 > As you can see, nothing should get build by default (this is enabled > purely on a package by package case) and repositories are setup so > that "rust" and related packages should be taken from >=20 > - devel:languages:rust for openSUSE_Leap_15.1 > - home:manfred-h:devel:languages:rust for 42.3 and 15.0 >=20 > firefox69 now needs rust-cbindgen >=3D 0.9.0, so I copied that package to > my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built > it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 >=20 > Still OBS thinks "nothing provides rust-cbindgen >=3D 0.9.0" for 15.0 and > 42.3, but the packages are there: >=20 > > >=20 > both providing: >=20 > rust-cbindgen =3D 0.9.0-1.1 =09 > rust-cbindgen(x86-64) =3D 0.9.0-1.1 >=20 > FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to > rust-cbindgen in the home:manfred-h:devel:languages:rust project, but > this did not change anything unfortunately. as an update, the linked package "rust-cbindgen" is now "finished" (not yet "succeeded"), and after sending my former message, firefox69 is "blocked" because of rust-cbindgen now. At least a change... ;) > Can anybody tell me what I'm doing wrong here? Or is this a bug in the > OBS resolver? >=20 > TIA, cheers. >=20 > l8er > manfred >=20 > PS: No complaints wrt/ 42.3, I'm not yet done with migrating all systems > I maintain to 15.1 yet! Therefore I'm trying to keep those packages > still building which are not services but still as close to the > Internet as possible, i.e. the _bad world_ ;) --===============6187635891108873714== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxeVozY0FDZ2tRcjNhVEx6VHIKQWVsejhRLzhDcEJkN2NYYzI4 ZkNNdTg5MmNUOFlGQW1jL0pieGJQa3BFT0V1bHBjOFBKWW93MFV1U0E5SzkvNQpNZktsZkUzRlA5 eXZTV3RXS0V0YTFpRUhWUmt3ZzBXcnFBcUlMMDZkWGVXZWduby9aajBBMWVQek5jN1JJaVJtCnBu TWVvWm05aUtjUTBpYlhrb2FkcUVKK1N3NWIyNmNrMlc1UGhuTjFyZ05SenRCeDNpYjl5cHhLb3l1 M0tLQlUKODd0TmJ5M3VCdEhNWDc1RWZMUktYemtBcjVlbXcwVzM0OXBZTDV0bEpjMjY5YTFPZjl5 SjFyRDhSVFRXZmdaRQpqNHJQUlgzWm92MTRYVW9HaHVRck5qN3dubk1aT1hrTlhuUDUrcUlNSnhR REh0ajJUL2ZaOWh3c0RHaWhjanY3CnpXQkJaY0ZRVGhDelk1R2NudXMvVndhTWJqSHRLSnNXMis1 L0JBWXhVSUhrQWNCb2FpWU1vcVVxR1l4L3puM3kKMzl1cDJvNjJBb1hCazBwYjYvT1pVajZLRUkv NkFCZHdNdm5lSWVpbzVCUVdkMTJnS1VIOTU0NTcvWENDQUlBVQovTzZ4T2tpK0czbVdmeC9sL1Mw QUUyaUtrYTlFQVNtU045R2xNTzZRTVpRSVR5OXNWYUhTd3gzbzQ2TTNjN3JyCllpNDJEZENXaWVV bzJLS1lOWnN3UWRlekdLTjZuNGlrU0tFaXAvbHpha0p4c3FLRGwxb1BnK2JMK1BZN1lGbWsKWTdJ UXhZWWczOFkvbFRzY2ZvMGlueDgyUUU1cEdMVS9wRG9SSXpiZWxSeTRHKy9UaGxBZ1p5VmF2UjZs M3ZnNQo0SjB2MTZHRXdFSzNsTnBRMDlCaEUvVVRwUlE1ZTNKSEFxU1lRNmpUcVdMdHBxV0lWc2M9 Cj1qc2N2Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============6187635891108873714==-- From mhollstein@t-online.de Fri Sep 6 15:08:12 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 06 Sep 2019 17:08:05 +0200 Message-ID: <20190906150805.GA14791@saturn.hollstein.homelinux.org> In-Reply-To: <20190906140439.GD4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2252888344693611816==" --===============2252888344693611816== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Fri, 06 Sep 2019, 16:04:39 +0200, Manfred Hollstein wrote: > On Fri, 06 Sep 2019, 15:44:04 +0200, Manfred Hollstein wrote: > > Hi there, > >=20 > > I've given up (I think) trying to understand why OBS sometimes behaves > > different than what I'd expect. > >=20 > > Here is my (current) challenge: > >=20 > > I'm trying to build firefox69 in my own project in > > home:manfred-h:mozilla. The repository metadata is set up as follows: > >=20 > > $ osc meta prj home:manfred-h:mozilla > > > > mozilla > > > > Mozilla based projects and support packages. > > > > > > > > > > > > > > > > > > > > > > x86_64 > > > > > > > > > > > > > > x86_64 > > > > > > > > > > > > > > x86_64 > > > > > >=20 > > As you can see, nothing should get build by default (this is enabled > > purely on a package by package case) and repositories are setup so > > that "rust" and related packages should be taken from > >=20 > > - devel:languages:rust for openSUSE_Leap_15.1 > > - home:manfred-h:devel:languages:rust for 42.3 and 15.0 > >=20 > > firefox69 now needs rust-cbindgen >=3D 0.9.0, so I copied that package to > > my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built > > it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 > >=20 > > Still OBS thinks "nothing provides rust-cbindgen >=3D 0.9.0" for 15.0 and > > 42.3, but the packages are there: > >=20 > > > > > >=20 > > both providing: > >=20 > > rust-cbindgen =3D 0.9.0-1.1 =09 > > rust-cbindgen(x86-64) =3D 0.9.0-1.1 > >=20 > > FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to > > rust-cbindgen in the home:manfred-h:devel:languages:rust project, but > > this did not change anything unfortunately. >=20 > as an update, the linked package "rust-cbindgen" is now "finished" (not > yet "succeeded"), and after sending my former message, firefox69 is > "blocked" because of rust-cbindgen now. At least a change... ;) On Fri, 06 Sep 2019, 15:54:14 +0200, Adrian Schr=C3=B6ter wrote: > I don't see it unresolvable in home:manfred-h:mozilla, but blocked. > > please note that events between repos in different projects are handled with > low prio. So it might take some time to see an effect. and On Fri, 06 Sep 2019, 15:58:55 +0200, Andreas Schwab wrote: > The package is currently building, maybe you didn't wait long enough for > the scheduler to pick up the newly built packages? both of your answers go into the direction I thought I've waited long enough for... Looks like I just need to wait a little longer :) Thanks for you replies anyway! In case it doesn't resolve in the coming days, I'll be back ;) Cheers. l8er manfred --===============2252888344693611816== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxeWRsVUFDZ2tRcjNhVEx6VHIKQWVrdWVnLy9kUVFYWnNKWFNj M2lXS3pDM2hsUndMcTErQjJtejJxdFlIdDQzRW8ydVFXNDQ5aHN3UXVoT2J2bwpxTE9HWE84eUhW T1U1SDUvVDhsVlUxeXZKaUdIdHh0UkxQNDk0Y01lWURqWVowS2l5UXBacjJGei9YTUgxNWR0CnUv TGZ3RWZqY25QR1RVQlovZ0hFUGQ0YkpBdUdtT2dWNklEVVMzdUhxZHlyQ0RTUEt4Zk9iVFMzeVVJ bmFWengKZHJJcmZNalo3cjNlNHdWNFY2KzNqcUtWTjN4TCs0UzBOU2NXL1VnK1dQREs2dUVTNGlz SXRFQys2UXFXK3hkbgp6OHU2ZzlSWFcyWkpJZkZ3OXFSYjVFM2l4aTBxUlNPeWE3azZMMHl5V2Ux NmFRdGczZmgrbXE5QTgzdzJ4aXU4CmpJek83bytKaGNZWGVyOGVPdFowZXcxaFB1QzBrSmFzQmgy WUhNbUdXK2tIVXBHQm5YRzhUWlIxRWxENTdyTVcKS3JjbHJhWnlGbUNWUDlEN0pmSldxQXVGQWkr bHlMc2hiQUpkaUxmN3gzRWhJaktVcjREVnBudm83VHBES1ZCNwphektBOVlEWFR0TGVNQm5wcDEr UUJUZHpWR2hndjRoSTR3NnZDUjJaL0RUYkt1TG9SN2lTYzdRV2V1ZzZpRS80CkU5ZE5UNTJ1aVFt SGNkd2ZhZVUyZUljMmFhWGNuRUVDcmh1Ui9vNmFCYm9FRks0NWd5clhmc0xLa0pMWnRCdWQKUFpH STEvZURJNzk5SDlJT2xsVDN4VkhybnBYRDF0UWt6aXRqeUxidXBxRHNyT3hGdGVyelBTcFd4WFlo ZVEzSgorT3U3dGhVRFJLdkx5QzVlb2k0UjQ1ZXFHaU5PdXlIWWxRcjBGOHlZY05uRUs4Z3BQTEk9 Cj1pMy95Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============2252888344693611816==-- From mhollstein@t-online.de Sun Sep 8 11:32:51 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 13:32:42 +0200 Message-ID: <20190908113242.GB4145@saturn.hollstein.homelinux.org> In-Reply-To: <20190906150805.GA14791@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4972715555727491274==" --===============4972715555727491274== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi there, On Fri, 06 Sep 2019, 17:08:05 +0200, Manfred Hollstein wrote: > On Fri, 06 Sep 2019, 16:04:39 +0200, Manfred Hollstein wrote: > > On Fri, 06 Sep 2019, 15:44:04 +0200, Manfred Hollstein wrote: > > > Hi there, > > >=20 > > > I've given up (I think) trying to understand why OBS sometimes behaves > > > different than what I'd expect. > > >=20 > > > Here is my (current) challenge: > > >=20 > > > I'm trying to build firefox69 in my own project in > > > home:manfred-h:mozilla. The repository metadata is set up as follows: ... > On Fri, 06 Sep 2019, 15:54:14 +0200, Adrian Schr=C3=B6ter wrote: > > I don't see it unresolvable in home:manfred-h:mozilla, but blocked. > > > > please note that events between repos in different projects are handled w= ith > > low prio. So it might take some time to see an effect. >=20 > and >=20 > On Fri, 06 Sep 2019, 15:58:55 +0200, Andreas Schwab wrote: > > The package is currently building, maybe you didn't wait long enough for > > the scheduler to pick up the newly built packages? >=20 > both of your answers go into the direction I thought I've waited long > enough for... Looks like I just need to wait a little longer :) >=20 > Thanks for you replies anyway! >=20 > In case it doesn't resolve in the coming days, I'll be back ;) and here I am again... I have re-created the situation in a small project at . It contains four packages of which two BuildRequire the two other ones: (1) firefox68 BuildRequires rust-cbindgen >=3D 0.8.7 provided by rust-cbindgen-0.8.7 (2) firefox69 BuildRequires rust-cbindgen >=3D 0.9.0 provided by rust-cbindgen-0.9.0 Building firefox68 succeeds, although I don't understand why it doesn't pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire, too. But, firefox69 fails with "unresolvable": nothing provides rust-cbindgen >=3D= 0.9.0 Am I wrong assuming this ought to work? Worth a bugzilla? Cheers. l8er manfred --===============4972715555727491274== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMDV0b0FDZ2tRcjNhVEx6VHIKQWVrRjVnLy9YeEZ1TWZnVEFB S3BwU3NJRC84ZWVWOWF3K2NEdXVqaG5VNjBubmdNNzBDMytsZ2paVC9MNHNORAp4SDJFamptMVVU Sm5hMUNPWVl0a2ZnMU1Ed0piVXB4Wm1UenZCS0pFQk5oVVlYbFFWRElrUmRqVUJrUmpWcG5ZCjQx SmZhYlVGWUdZZUxvd2JHNm5qVUtWQkdtb1JrVnhuY0NzWERoMURyMnN1QkY0aE1OSVN0b2F0Zlhh bmxpOWUKa3IvdkZ5QVZFczR1UGNIaEU4RDhhU1JHWGtRYTBZQTR1ancyRENXUHF6elF6UHA2NStz NC9GUnVSSzRaMXdOTgpwWEhUSnZqREMrYkYzREl2Ly9tU2RLQk5GTzF4ZnAzejFmRHlBcmgxTUZt U3JoNEpUM290WUVWTkhGcytlbFM1CjdyWU8zV09uTWsyY1Z2TElnTWN6RTJVMXF2TzBxd2V0Nzc0 V3dmTGwvREZLUngrMGhJODJobzhMazN5K3ZaQ0MKQWRMdU0weFVWM3lOK3Q2cVRCUFpUU0l2aFhW NFhCcjZsRm1EdkpNTWVPeWp1M2VXeG9zcWRJQkFrbGd6VldQVQpmMXh5TW15WEV5aWZyYkVDdFRm bzdyUjhZUU4vN2RYY0p2b3BnNDBucHVLRnVqZzJjK0FhTU9CcExONmFMZ24vCnhTdUg0cTNDNVIz KzBlQmgxalFtRUN4d0tzVVlRR0VwZUtvVUYveXl3VXFpVjJ5RWNyQitkdThPZ0Y3d3ZoRzAKQ2Yz VU02NjNudjlwaEV4MWtubUc3bklRSEsrcHVjeEJtNGZIeUh5UU1kVzg1aHZncUt1SVR1TzdTeUla UjBIUApiYmovWjJZcE1mMUFzMERwYlpMM3lDc3dJSE03cVZzOGc1NURqNnRiSHIrMi93aUVrM2c9 Cj1uSjNkCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============4972715555727491274==-- From schwab@linux-m68k.org Sun Sep 8 12:12:48 2019 From: Andreas Schwab To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 14:12:45 +0200 Message-ID: <87blvvj8aq.fsf@igel.home> In-Reply-To: <20190908113242.GB4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8250106262326515838==" --===============8250106262326515838== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sep 08 2019, Manfred Hollstein wrote: > Building firefox68 succeeds, although I don't understand why it doesn't > pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire, > too. There is no rust-cbindgen-0.9.0.rpm, there is only rust-cbindgen.rpm, which has been picked up from home:manfred-h:TEST/rust-cbindgen-0.8.7, with version 0.8.7. > But, firefox69 fails with "unresolvable": nothing provides rust-cbindgen >= =3D 0.9.0 Because rust-cbindgen.rpm has version 0.8.7. > Am I wrong assuming this ought to work? Yes. A repository can only hold a single version of a binary package with a given name. If you want to provide different versions of a package, you need to build them in different repositories, and control the visibilty via the repository path. Alternatively, you can rename the binary package to make its name unique. Andreas. --=20 Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============8250106262326515838==-- From mhollstein@t-online.de Sun Sep 8 12:39:40 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 14:39:35 +0200 Message-ID: <20190908123935.GC4145@saturn.hollstein.homelinux.org> In-Reply-To: <20190908113242.GB4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5302893466677065318==" --===============5302893466677065318== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Moin, On Sun, 08 Sep 2019, 13:32:42 +0200, Manfred Hollstein wrote: > Hi there, >=20 > On Fri, 06 Sep 2019, 17:08:05 +0200, Manfred Hollstein wrote: > > On Fri, 06 Sep 2019, 16:04:39 +0200, Manfred Hollstein wrote: > > > On Fri, 06 Sep 2019, 15:44:04 +0200, Manfred Hollstein wrote: > > > > Hi there, > > > >=20 > > > > I've given up (I think) trying to understand why OBS sometimes behaves > > > > different than what I'd expect. > > > >=20 > > > > Here is my (current) challenge: > > > >=20 > > > > I'm trying to build firefox69 in my own project in > > > > home:manfred-h:mozilla. The repository metadata is set up as follows: > ... > > On Fri, 06 Sep 2019, 15:54:14 +0200, Adrian Schr=C3=B6ter wrote: > > > I don't see it unresolvable in home:manfred-h:mozilla, but blocked. > > > > > > please note that events between repos in different projects are handled= with > > > low prio. So it might take some time to see an effect. > >=20 > > and > >=20 > > On Fri, 06 Sep 2019, 15:58:55 +0200, Andreas Schwab wrote: > > > The package is currently building, maybe you didn't wait long enough for > > > the scheduler to pick up the newly built packages? > >=20 > > both of your answers go into the direction I thought I've waited long > > enough for... Looks like I just need to wait a little longer :) > >=20 > > Thanks for you replies anyway! > >=20 > > In case it doesn't resolve in the coming days, I'll be back ;) >=20 > and here I am again... >=20 > I have re-created the situation in a small project at > . > It contains four packages of which two BuildRequire the two other ones: >=20 > (1) firefox68 BuildRequires rust-cbindgen >=3D 0.8.7 > provided by rust-cbindgen-0.8.7 > (2) firefox69 BuildRequires rust-cbindgen >=3D 0.9.0 > provided by rust-cbindgen-0.9.0 >=20 > Building firefox68 succeeds, although I don't understand why it doesn't > pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire, > too. >=20 > But, firefox69 fails with "unresolvable": nothing provides rust-cbindgen >= =3D 0.9.0 >=20 > Am I wrong assuming this ought to work? Worth a bugzilla? FWIW, building it using a local build script (build-20190128-lp151.1.1.noarch) behaves exactly like I would expect: (0) Both rust-cbindgen package have been built and are available in the same RPMS subdirectory: RPMS/rust-cbindgen-0.8.7-0.x86_64.rpm RPMS/rust-cbindgen-0.9.0-0.x86_64.rpm (1) firefox68 picks up RPMS/rust-cbindgen-0.9.0-0.x86_64.rpm because of the higher version number (2) firefox69 picks up RPMS/rust-cbindgen-0.9.0-0.x86_64.rpm, too, i.e. no trouble to resolve "rust-cbindgen >=3D 0.9.0"! So, to me this looks like a bug in OBS, no?!? Cheers. l8er manfred --===============5302893466677065318== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMDlvY0FDZ2tRcjNhVEx6VHIKQWVtczBCQUFsTkNFQU52U250 dUJKWktoM0JYYU9MOGxpVjVDbjh6c040eFhIaDhtdzYwRkhmcndaRjlkN1ZJTwpBMHp4S1BYazQw aUh0MzN6c1QwTVcySUphTE1hMXZoV0hCZnoxWXJWejM2K3BZMDczL2ZzOU1BMk1Tb0JhNEZvCnFj UCtDT2FLVDkvcndPSE91YjROZnY4QzJYaUF0VHpJNS9NU2RLcWcyS0djUm40WWkvSi9hbm56ejRP Q0FabFIKcmVSOFBtU2QxYWJWQ3g3RmE3eU5Ma09ON3BZSDEvTWVQa05sak5hVnErNnVRUTZaSTFT WGI1UnM1WEtGSFROOApJRXllSjhIWkU2S1E0SFhDL3AybEtLd0J2UTdLOGZyRFRDcVZQTU5xYWhC Q2U5Qy9KZnZkS3IwUFVJWnJTRTdLCmluclU3WW9FY2UwbjZYY2VJczRmV3hjZk01N3JEcVZHK004 YmhCL1lUa2FPYXExVmtFcThqMVBrT3AyNDQ5bHIKbWVlMWZBTWlLc1JwK3hpakRlWTVIMytPQzVn OHBkS0hYZXlHN2NkNXFrbWVWYk5EYlJ5ay9xa1lXSnUwTDlXcApScXdpZkxqa3JLMGlaUXFtNGZn cUhtZWZIZ29nSnFPTTVkOUdqdnNYcSs4UGNBdkRPYmVKVHBkTVVZdFo2N1NhCmttamROdFBoNEpV NDhkS3Y5T2EzQmQ1b01QQWFSWEdUaWxhZncwRnBVT3kxdW0wY2ZMaU14V1VzeUpjdEFUNjIKZnF1 cFpTS1lZbEttZTlUcTFRZFowdkVoZjJ1U3VROWpqbVBxbmNIMy9Ubk4vaHlFMGhnY2huU2x5cXNh c3c4MQpxZ3RZUEFOaXZCejVmNTZ0K3pTU1dLK1lCc21QSEg2ZUhaYWFxdWE1MzBjYWp1MHY0TFU9 Cj1ENUwrCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============5302893466677065318==-- From schwab@linux-m68k.org Sun Sep 8 12:44:12 2019 From: Andreas Schwab To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 14:44:08 +0200 Message-ID: <877e6jj6uf.fsf@igel.home> In-Reply-To: <20190908123935.GC4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3384081772160217646==" --===============3384081772160217646== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Sep 08 2019, Manfred Hollstein wrote: > (0) Both rust-cbindgen package have been built and are available in > the same RPMS subdirectory: > RPMS/rust-cbindgen-0.8.7-0.x86_64.rpm > RPMS/rust-cbindgen-0.9.0-0.x86_64.rpm The repository can only hold rust-cbindgen.rpm. > So, to me this looks like a bug in OBS, no?!? No. Andreas. -- Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============3384081772160217646==-- From stefan.bruens@rwth-aachen.de Sun Sep 8 13:13:07 2019 From: Stefan =?utf-8?q?Br=C3=BCns?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 15:12:58 +0200 Message-ID: <1730981.4uqr5RoJSf@pebbles> In-Reply-To: <20190908113242.GB4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2143579203964470479==" --===============2143579203964470479== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sonntag, 8. September 2019 13:32:42 CEST Manfred Hollstein wrote: > Hi there, >=20 > I have re-created the situation in a small project at > . > It contains four packages of which two BuildRequire the two other ones: I am just wondering what you are trying to achieve at all. Currently you are: - building mozilla69 and mozilla68, both are unmodified copies of the package= s=20 from the mozilla OBS projects. - building each one for Leap 42.3, 15.0 and 15.1 - doing the same in your :mozilla and :TEST subprojects. These are 2 * 3 * 2 =3D 12 instances of mozilla package builds. These package= s=20 compete with the MozillaFirefox packages from Tumbleweed and its Stagings.=20 Only 4 of the OBS workers have enough resources to build Firefox, so the whol= e=20 Staging process gets slowed down considerably. Please: - disable building for the project(s) you don't work on - disable building for all but one distribution, thats sufficient for your=20 setup experiments. And as Andreas has said already - don't try to build different versions of th= e=20 same package in one project. A project can hold exactly one version of a=20 package at any time. Regards, Stefan --=20 Stefan Br=C3=BCns / Bergstra=C3=9Fe 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 --===============2143579203964470479== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlGMEVBQkVDQUIwV0lRU3dXUldJcEpibDBX NERlbU52ZjBvOWpQNnFVd1VDWFhUK1dnQUtDUkJ2ZjBvOWpQNnEKVTZhWUFKOVhQNENmT2hmbjdW THQvRU80RldSdzhWVEZKZ0NncTAvTlplV3RzYlN1TjFGd3FlVU5BeEdia2VjPQo9UmhScwotLS0t LUVORCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============2143579203964470479==-- From mhollstein@t-online.de Sun Sep 8 13:29:17 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 15:29:02 +0200 Message-ID: <20190908132902.GD4145@saturn.hollstein.homelinux.org> In-Reply-To: <87blvvj8aq.fsf@igel.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5158353651781499827==" --===============5158353651781499827== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, 08 Sep 2019, 14:12:45 +0200, Andreas Schwab wrote: > On Sep 08 2019, Manfred Hollstein wrote: >=20 > > Building firefox68 succeeds, although I don't understand why it doesn't > > pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire, > > too. >=20 > There is no rust-cbindgen-0.9.0.rpm, there is only rust-cbindgen.rpm, > which has been picked up from home:manfred-h:TEST/rust-cbindgen-0.8.7, > with version 0.8.7. then, why do both versions exist at ?? > > But, firefox69 fails with "unresolvable": nothing provides rust-cbindgen = >=3D 0.9.0 >=20 > Because rust-cbindgen.rpm has version 0.8.7. Nope: zypper ar https://download.opensuse.org/repositories/home:/manfred-h:/TEST/= openSUSE_Leap_15.1/ TEST zypper ref zypper se -s rust-cbindgen Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------+------------+-----------------+--------+----------- | rust-cbindgen | package | 0.9.0-lp151.3.1 | x86_64 | TEST =20 | rust-cbindgen | package | 0.8.7-lp151.8.1 | x86_64 | TEST =20 | rust-cbindgen | srcpackage | 0.9.0-lp151.3.1 | noarch | TEST =20 | rust-cbindgen | srcpackage | 0.8.7-lp151.8.1 | noarch | TEST =20 so it's there and would be installed in version 0.9.0-lp151.3.1 when running zypper in rust-cbindgen > > Am I wrong assuming this ought to work? >=20 > Yes. A repository can only hold a single version of a binary package > with a given name. If you want to provide different versions of a > package, you need to build them in different repositories, and control > the visibilty via the repository path. Alternatively, you can rename > the binary package to make its name unique. See above. AFAICS, the update repos work exactly like this - they just add a newer version on top of the stack, but in the same repo. > Andreas. Cheers. l8er manfred --===============5158353651781499827== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMUFoNEFDZ2tRcjNhVEx6VHIKQWVrZmhRLy9YMHpQR3oxbkR2 RWxRVCtybkQrQ2ZlVzI3VFpqdFA4OFA0UFFNZnhRTG1Nckl5MUFoR3hLK0RuVgoxa2FkOHVOL3N0 NDhzVHl1bldyZUFzWFZpRVhKdFMrb2tLQkJWOTRsd2xJWFQybVpTSXZBUUFXelFMdlR1UGZSCjJY SHhnSGlYWUY3MWdEa1YrWVBtZXdYMmhxZ3I2YlNWZnNob2ljRktpUHQvaGQrdi9RMThDYW10c0w1 V0hTazAKT3UxTk1nWXNnTUxOMVhDSHNtVlVPdDA2NVcxMGhKeklPU3FQa2tqYlV2QU1RQi8zbS9q ZnM4OVpFejRPN3VSKwpIMnVuTEFJWHhFdVR2a2hjbkErT0RBUVNBSTVCQW5GcGw5NWdLeWhLTXRU RGlMbG5KVDVzaGZ6SVh2ZWIwcEFBCldJU01YVEtFb3lDLzhEQXpsMTFvcU5zdExoc3EvdGJ2RGdn ZTJJYmo5c2ZqakZKSU4xb1BZVldDV3JyZEkwbTgKeldqWkRTZmZqRDRFZG5XcHgwazI1ZXJFbTc1 UFFVc0tjU294RXRWSmZiTGVvMDRtaFVDWEVhQVNtV0dFTEh0WQp1cURoMjN2WDN5TjJWVDBuVXNz empLQnRBVWxYNkU1UVlPQkNMa2dwV3IrclNVTS8zc3NaL2M0OXoyZnFMRnhVCkcyV3JROWc1d3BK NjZEREliSitERDEycWZ1Y2dMWHZ5cGNUanpabW1GcGxaNEhIU1p5OFN5d3BBRUM3Mnh1VS8KSlNV a2pJUjNKajl6Zi9vanJseVNKUE9TMnZHbkluTnFrdVA3S0dmVEpjYU5PVzlaZ3ppSEZ1aS8wM1hC Uk5RSApRR1NUS0VHalZJZm5GcnFuZEJ4eFRqQzAyUUhrbU93NFpNRm1YWUIrZjZzNFd5anZiVHM9 Cj1seFVJCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============5158353651781499827==-- From mhollstein@t-online.de Sun Sep 8 13:32:14 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 15:32:08 +0200 Message-ID: <20190908133208.GE4145@saturn.hollstein.homelinux.org> In-Reply-To: <877e6jj6uf.fsf@igel.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4534642431512717854==" --===============4534642431512717854== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, 08 Sep 2019, 14:44:08 +0200, Andreas Schwab wrote: > On Sep 08 2019, Manfred Hollstein wrote: >=20 > > (0) Both rust-cbindgen package have been built and are available in > > the same RPMS subdirectory: > > RPMS/rust-cbindgen-0.8.7-0.x86_64.rpm > > RPMS/rust-cbindgen-0.9.0-0.x86_64.rpm >=20 > The repository can only hold rust-cbindgen.rpm. which I honestly doubt! Here's another live example from the updates repo: zypper se -s -x kernel-default i+ | kernel-default | package | 4.12.14-lp151.28.13.1 | x86_64 | update.= local v | kernel-default | package | 4.12.14-lp151.28.10.1 | x86_64 | update.= local v | kernel-default | package | 4.12.14-lp151.28.7.1 | x86_64 | update.= local v | kernel-default | package | 4.12.14-lp151.28.4.1 | x86_64 | update.= local This looks to me as if the repo can hold more than one version. > > So, to me this looks like a bug in OBS, no?!? >=20 > No. Still not convinced. > Andreas. Cheers. l8er manfred --===============4534642431512717854== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMUF0Y0FDZ2tRcjNhVEx6VHIKQWVrREZ3Ly9aak1WZ0FIeGZR bTZCb1BnOHJlUXhQdVliYnVlL0J3Nm10cmR1UE5TOFpaNmloS2lTRDhYUXNJTwp4UjRIWlVaTnJl ZU55R0t3Sk8xMndTRVpBMVM3Skp3dEZUcVBnMVUwbE5iZGI1dzdaQjZPUWU1dlMxL0lHcHpsCkkz VVU3d2drY0p3R0RrdmZuQ1BMY1hwN1NBV0hiWnptemk5b0RPL0swdDJEVmd2aGRWb1hXWWx1dXpF N2pkVFkKSDVKQUE3MDI5a3RGOFE1SmhFN2M5SjdvN3R2Q1daTkJ3dlRaWUNsMCtPOEYvTHRRSFNz NkEwTHY5MERERGo3SQpaSHZBVklYRzNOelFBV0h3WUJMaDR5SklsS3c3M3MrM0xPaUdwRGlGZmg2 M2pTMXhRVzN0Q2E3dVk2dzdIcEo5CndiSHgxWlpLZ1VzYVlHWVVFT3JWWlhsL0txSHZiSEs2cVBZ aGtkVUxVUnZ4bkIvbnFuY3p1OWpEbUxIVzB6anAKeWlwRkdmZjdVR0JvTHlMbXIyTll5YmJZMWRv QUFVbTdOSEpzaHJ4ZU81bDdWTnBtWWNsMG5rVWRwcGJMcEFaKwpmTnoyWUtLczh6Y1pLVDh1cFZM K0hnWnAxR09xUDhxU3JsdkdTd3RYbkNGOWJ5ZndqWnQvblpoeVc3WnpvTzVICjQvaHU2VEM5Qm9u TXAvM2xNMlNvQ1hMTCtjODdLMnBiaC9mbUY5bFM0NnNPdDZ0U014ekw5bG80ZkduN3JpR2oKZ0N0 N2J6ZEhmR0M4cGR0ZE96ak01cW1JVlI5Mm9YTHhEU2N1dE01d0REQVlCQ21BZ0cxN0RUVnpxbGlh UG5mZQpzKzNXa21tQUoxUllOYW9aTDh5eTMyLzJCc2tkS0l1bFcyZDVDaU9wZ3huY05SOEtUbmc9 Cj1OOE5TCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============4534642431512717854==-- From stefan.bruens@rwth-aachen.de Sun Sep 8 13:50:38 2019 From: Stefan =?utf-8?q?Br=C3=BCns?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 15:50:27 +0200 Message-ID: <9240615.7cQ4HqM3ZH@pebbles> In-Reply-To: <20190908132902.GD4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4413686212010690284==" --===============4413686212010690284== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sonntag, 8. September 2019 15:29:02 CEST Manfred Hollstein wrote: > On Sun, 08 Sep 2019, 14:12:45 +0200, Andreas Schwab wrote: > > On Sep 08 2019, Manfred Hollstein wrote: > > > Building firefox68 succeeds, although I don't understand why it doesn't > > > pick up rust-cbindgen-0.9.0 which perfectly fulfills the BuildRequire, > > > too. > >=20 > > There is no rust-cbindgen-0.9.0.rpm, there is only rust-cbindgen.rpm, > > which has been picked up from home:manfred-h:TEST/rust-cbindgen-0.8.7, > > with version 0.8.7. >=20 > then, why do both versions exist at >=20 > =20 > Leap_15.1/x86_64/> You are confusing download directories with OBS projects. Each OBS project ca= n=20 have exactly *one* version of each package. Each update is created in a separate maintenance project and the built=20 packages are synced to the download directory. Stefan --=20 Stefan Br=C3=BCns / Bergstra=C3=9Fe 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 --===============4413686212010690284== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlGMEVBQkVDQUIwV0lRU3dXUldJcEpibDBX NERlbU52ZjBvOWpQNnFVd1VDWFhVSEl3QUtDUkJ2ZjBvOWpQNnEKVXcyTUFLQ0Q3eE5TbVVNcHFE UHFTUFdkUFZnc0htRkJ5UUNnbFVraktmWkFXU1g1MVd5TXh5MG5KSTZWRzQwPQo9Sk9BYwotLS0t LUVORCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============4413686212010690284==-- From schwab@linux-m68k.org Sun Sep 8 14:01:06 2019 From: Andreas Schwab To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 16:01:00 +0200 Message-ID: <8736h6khur.fsf@igel.home> In-Reply-To: <20190908133208.GE4145@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4771484870047017555==" --===============4771484870047017555== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sep 08 2019, Manfred Hollstein wrote: > which I honestly doubt! Here's another live example from the updates > repo: > > zypper se -s -x kernel-default > i+ | kernel-default | package | 4.12.14-lp151.28.13.1 | x86_64 | updat= e.local > v | kernel-default | package | 4.12.14-lp151.28.10.1 | x86_64 | updat= e.local > v | kernel-default | package | 4.12.14-lp151.28.7.1 | x86_64 | updat= e.local > v | kernel-default | package | 4.12.14-lp151.28.4.1 | x86_64 | updat= e.local These all come from separate repositories. A download directory is *not* a repository in the OBS sense. Andreas. --=20 Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============4771484870047017555==-- From schwab@linux-m68k.org Sun Sep 8 14:05:38 2019 From: Andreas Schwab To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 16:05:34 +0200 Message-ID: <87y2yyj32p.fsf@igel.home> In-Reply-To: <9240615.7cQ4HqM3ZH@pebbles> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5850390300794179575==" --===============5850390300794179575== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sep 08 2019, Stefan Br=C3=BCns wrote: > You are confusing download directories with OBS projects. Each OBS project = can=20 > have exactly *one* version of each package. This isn't exactly true either. A project can have more than one build repository, each one containing its own set of unversioned binary packages. But each build can only see one version of a binary package, with the visibility defined through the repository path. Andreas. --=20 Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============5850390300794179575==-- From mhollstein@t-online.de Sun Sep 8 15:08:18 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 17:08:14 +0200 Message-ID: <20190908150814.GA6930@saturn.hollstein.homelinux.org> In-Reply-To: <1730981.4uqr5RoJSf@pebbles> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0367142236330066710==" --===============0367142236330066710== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, 08 Sep 2019, 15:12:58 +0200, Stefan Br=C3=BCns wrote: > On Sonntag, 8. September 2019 13:32:42 CEST Manfred Hollstein wrote: > > Hi there, >=20 > >=20 > > I have re-created the situation in a small project at > > . > > It contains four packages of which two BuildRequire the two other ones: >=20 > I am just wondering what you are trying to achieve at all. Currently you ar= e: >=20 > - building mozilla69 and mozilla68, both are unmodified copies of the packa= ges=20 > from the mozilla OBS projects. > - building each one for Leap 42.3, 15.0 and 15.1 > - doing the same in your :mozilla and :TEST subprojects. you did not look at the projects, did you? :TEST is just a set of four packages with *no* files to be stored into the built RPMs; I created them just as a small test case to describe what I see. I now learned that I have to re-think my impression of a repository in the sense of OBS vs zypper, but that's another issue. > These are 2 * 3 * 2 =3D 12 instances of mozilla package builds. These packa= ges=20 > compete with the MozillaFirefox packages from Tumbleweed and its Stagings. = Are you saying I should not help Wolfgang, who is the maintainer for the mozilla packages and his work? The current situation that I'm back at revision 1 is just a matter of having to re-base/sync my work with Wolfgang's. > Only 4 of the OBS workers have enough resources to build Firefox, so the wh= ole=20 > Staging process gets slowed down considerably. >=20 > Please: > - disable building for the project(s) you don't work on > - disable building for all but one distribution, thats sufficient for your = > setup experiments. Please read above. If you want, I can certainly stop contributing to various packages... > And as Andreas has said already - don't try to build different versions of = the=20 > same package in one project. A project can hold exactly one version of a=20 > package at any time. Yep, *now* I know. > Regards, >=20 > Stefan Cheers. l8er manfred --===============0367142236330066710== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMUdWNEFDZ2tRcjNhVEx6VHIKQWVrZ2pRLzlIZ1hnU1hkclA0 b1lTNGRnWHdpSmU0Z2tiYWhCMWpRMUlzL1JMOHVJcXdaNWhrNzZqZUlsTFdCcwpJbGdSaURwODMx NXN2MzduTmZEY0dHZzRCMGR1NUhFSlR5TUp5RXZBVTMyQWVlY2x5VEx3OEJNTXBlVUZGSXBjCjQ5 dWx3VDMzZlhqdFJYSW95MHJVajdHam1ieFFHcUpCZnRXajYrbGZ2Q3dRbVZkbFhicnlRdUFKdlQv MktuQ2YKbDFWczFIZ1pwODJRWlVLRUxneVNvNmZaWUM2VkpuRmRJMStUNFo0T1VTajJVYkppNEto blpuQzVnU2wySUd5UQpZZkVNQlpUMkI1MHBJaUpzZmpOblFxamo1ek5MMTM2RXcxRWg2V2NVWHFW WU9aMWh2Tks5blUybXJGUnJGbCtLCnkvSkgyemVUWm85RXQ3bElCejNJcXMrWXFMTHc1clc2V2Jn TDFrTHRsNHlsWlRLa2NOTDJyWVdoNnV5VzlQOHEKcG83ZWFyekhBZ2pPdFVUeTdOOGY2OXZFbHRR UW80cGg4QktHVmMvNEtuT0V5TUR1c0Y4ZzQyRlgzYzgvTmlqQgpyUnVwdDZiNk1uRzFreDJvRlQ5 MmlBZnltMi95dGRBaUN5cnFsVEtBQk42SkVTN25qZWVROHJmN1lZV0xXZGFnCll2bmJvSktXZ3Vv SVlkSHFNVnlwa0g4U2dEQmlhbVlkeEg4NVpIc0JhYjB0MHJ1THpKSE95UGtJSkdWT255b2cKQmNT emVQeHpEYnBVRjlnVkNMVHdGWFhabXJaK010bGYxdk02Z1B3NWlJa2JtN2FiVjJWbk5jdHRtQ3N1 MHlDQworWHlHbFJ4b2FRYnBrSWQrbEtWMDRHTGhEZDJ2SDFzRFMzNUFuSXdOMDBTWm1MdTdRT1k9 Cj16MFU5Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============0367142236330066710==-- From stefan.bruens@rwth-aachen.de Sun Sep 8 16:18:42 2019 From: Stefan =?utf-8?q?Br=C3=BCns?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Sun, 08 Sep 2019 18:18:33 +0200 Message-ID: <1719830.NLvTtPdLLN@pebbles> In-Reply-To: <20190908150814.GA6930@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9218956525818937814==" --===============9218956525818937814== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sonntag, 8. September 2019 17:08:14 CEST Manfred Hollstein wrote: > On Sun, 08 Sep 2019, 15:12:58 +0200, Stefan Br=C3=BCns wrote: > > On Sonntag, 8. September 2019 13:32:42 CEST Manfred Hollstein wrote: > > These are 2 * 3 * 2 =3D 12 instances of mozilla package builds. These > > packages compete with the MozillaFirefox packages from Tumbleweed and its > > Stagings. > Are you saying I should not help Wolfgang, who is the maintainer for the > mozilla packages and his work? The current situation that I'm back at > revision 1 is just a matter of having to re-base/sync my work with > Wolfgang's. >=20 > > Only 4 of the OBS workers have enough resources to build Firefox, so the > > whole Staging process gets slowed down considerably. > >=20 > > Please: > > - disable building for the project(s) you don't work on > > - disable building for all but one distribution, thats sufficient for your > > setup experiments. >=20 > Please read above. If you want, I can certainly stop contributing to > various packages... I never said that. I just asked kindly to consider the effects of rebuilding = packages in your home project *after* submitting your work. You are=20 effectively hurting yourself - you are slowing down Factory progress, and thu= s=20 also extend the time it takes until the next Firefox or Thunderbird version i= s=20 accepted. When you start the next round, you can just start with *one* target repositor= y=20 enabled, and enable the other ones once the first one succeeds, just prior to= =20 submission. Unfortunately, powerful workers are a scarce resource in the OBS. Using only = as few resources as needed helps *all* contributors. Kind regards, Stefan --=20 Stefan Br=C3=BCns / Bergstra=C3=9Fe 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 --===============9218956525818937814== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlGMEVBQkVDQUIwV0lRU3dXUldJcEpibDBX NERlbU52ZjBvOWpQNnFVd1VDWFhVcDJRQUtDUkJ2ZjBvOWpQNnEKVS91bkFKOXFNcTl1Ykc4TFRU eUZIdnpjYlFWRGRGZjZLQUNnaDE3RDcyWXdKTk9DeHlpaHRNL3Q4dlVBc1lzPQo9M0ZBVQotLS0t LUVORCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============9218956525818937814==-- From adrian@suse.de Mon Sep 9 06:58:42 2019 From: Adrian =?utf-8?q?Schr=C3=B6ter?= To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 08:57:27 +0200 Message-ID: <2136724.LcASdOnh7h@linux-ywca> In-Reply-To: <20190906150805.GA14791@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9187676961725039584==" --===============9187676961725039584== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Freitag, 6. September 2019, 17:08:05 CEST Manfred Hollstein wrote: > On Fri, 06 Sep 2019, 16:04:39 +0200, Manfred Hollstein wrote: > > On Fri, 06 Sep 2019, 15:44:04 +0200, Manfred Hollstein wrote: > > > Hi there, > > > > > > I've given up (I think) trying to understand why OBS sometimes behaves > > > different than what I'd expect. > > > > > > Here is my (current) challenge: > > > > > > I'm trying to build firefox69 in my own project in > > > > > > home:manfred-h:mozilla. The repository metadata is set up as follows: > > > $ osc meta prj home:manfred-h:mozilla > > > > > > > > > mozilla > > > > > > > > > Mozilla based projects and support packages. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > repository="openSUSE_Leap_42.3"/> > > repository="openSUSE_Leap_42.3"/> > > > > > > > > > x86_64 > > > > > > > > > > > > > > > > > repository="openSUSE_Leap_15.1"/> > > > > > > > > > > > > x86_64 > > > > > > > > > > > > > > > > > repository="openSUSE_Leap_15.0"/> > > repository="openSUSE_Leap_15.0"/> > > > > > > > > > x86_64 > > > > > > > > > > > > > > > > > > As you can see, nothing should get build by default (this is enabled > > > purely on a package by package case) and repositories are setup so > > > that "rust" and related packages should be taken from > > > > > > - devel:languages:rust for openSUSE_Leap_15.1 > > > - home:manfred-h:devel:languages:rust for 42.3 and 15.0 > > > > > > firefox69 now needs rust-cbindgen >= 0.9.0, so I copied that package to > > > my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built > > > it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 > > > > > > Still OBS thinks "nothing provides rust-cbindgen >= 0.9.0" for 15.0 and > > > > > > 42.3, but the packages are there: > > > > > ges:rust/rust-cbindgen-0.9.0/openSUSE_Leap_15.0/x86_64/rust-cbindgen-0 > > > .9.0-lp150.1.1.x86_64.rpm> > > > > > ages:rust/rust-cbindgen-0.9.0/openSUSE_Leap_42.3/x86_64/rust-cbindgen- > > > 0.9.0-1.1.x86_64.rpm>> > > > > both providing: > > > rust-cbindgen = 0.9.0-1.1 > > > rust-cbindgen(x86-64) = 0.9.0-1.1 > > > > > > FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to > > > rust-cbindgen in the home:manfred-h:devel:languages:rust project, but > > > this did not change anything unfortunately. > > > > as an update, the linked package "rust-cbindgen" is now "finished" (not > > yet "succeeded"), and after sending my former message, firefox69 is > > "blocked" because of rust-cbindgen now. At least a change... ;) > > On Fri, 06 Sep 2019, 15:54:14 +0200, Adrian Schröter wrote: > > I don't see it unresolvable in home:manfred-h:mozilla, but blocked. > > > > please note that events between repos in different projects are handled > > with low prio. So it might take some time to see an effect. > > and > > On Fri, 06 Sep 2019, 15:58:55 +0200, Andreas Schwab wrote: > > The package is currently building, maybe you didn't wait long enough for > > the scheduler to pick up the newly built packages? > > both of your answers go into the direction I thought I've waited long > enough for... Looks like I just need to wait a little longer :) > > Thanks for you replies anyway! > > In case it doesn't resolve in the coming days, I'll be back ;) don't wait, use "osc buildinfo" to see if you have problems right now. The scheduler will follow, if that has worked.... -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============9187676961725039584==-- From Mathias.Homann@opensuse.org Mon Sep 9 08:47:32 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 10:47:23 +0200 Message-ID: <6342900.6F7EvOdOsu@kumiko> In-Reply-To: <20190906134404.GC4608@saturn.hollstein.homelinux.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3922993641839620067==" --===============3922993641839620067== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit not completely unrelated... due to the fact that firefox68 AND firefox69 both don't build in the mozilla project right now my systems have reverted to the mozilla 60.8esr from the updates repo... which means the more important ones of the addons that I'm using are not working anymore. Also, firefox crashes on exit. *not* funny. Cheers MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============3922993641839620067==-- From wolfgang@rosenauer.org Mon Sep 9 08:51:51 2019 From: Wolfgang Rosenauer To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 10:50:58 +0200 Message-ID: In-Reply-To: <6342900.6F7EvOdOsu@kumiko> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1490352893688260771==" --===============1490352893688260771== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 09.09.19 um 10:47 schrieb Mathias Homann: > not completely unrelated... >=20 > due to the fact that firefox68 AND firefox69 both don't build in the mozill= a=20 > project right now my systems have reverted to the mozilla 60.8esr from the = > updates repo... which means the more important ones of the addons that I'm = > using are not working anymore. Also, firefox crashes on exit. >=20 > *not* funny. can you please elaborate what you are doing on which distribution and so on? Wolfgang --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============1490352893688260771==-- From Mathias.Homann@opensuse.org Mon Sep 9 09:23:59 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 11:23:50 +0200 Message-ID: <2665086.irI1juPWbc@kumiko> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2188292774944533254==" --===============2188292774944533254== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Montag, 9. September 2019, 10:50:58 CEST schrieb Wolfgang Rosenauer: > Am 09.09.19 um 10:47 schrieb Mathias Homann: > > not completely unrelated... > > > > due to the fact that firefox68 AND firefox69 both don't build in the > > mozilla project right now my systems have reverted to the mozilla 60.8esr > > from the updates repo... which means the more important ones of the > > addons that I'm using are not working anymore. Also, firefox crashes on > > exit. > > > > *not* funny. > > can you please elaborate what you are doing on which distribution and so on? I'm running Leap 15.0 and have the mozilla repository enabled, so that I have the same firefox on linux that I have on windows, mainly because some of the addons that I use refuse to work on anything older than the latest firefox. right now the available firefox from the mozilla repo is even older than the one from the updates repo, both are too old for the addons. Cheers MH *Mathias Homann* Mathias.Homann(a)openSUSE:.org[1] irc: [Lemmy] @ freenode, ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102* -------- [1] mailto:Mathias.Homann(a)eregion.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============2188292774944533254==-- From wolfgang@rosenauer.org Mon Sep 9 10:02:03 2019 From: Wolfgang Rosenauer To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 12:02:01 +0200 Message-ID: <0d6120fb-e275-5a01-6c65-61e97b529bb3@rosenauer.org> In-Reply-To: <2665086.irI1juPWbc@kumiko> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1673087264068065345==" --===============1673087264068065345== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 09.09.19 um 11:23 schrieb Mathias Homann: > Am Montag, 9. September 2019, 10:50:58 CEST schrieb Wolfgang Rosenauer: >> Am 09.09.19 um 10:47 schrieb Mathias Homann: >>> not completely unrelated... >>> >>> due to the fact that firefox68 AND firefox69 both don't build in the >>> mozilla project right now my systems have reverted to the mozilla 60.8esr >>> from the updates repo... which means the more important ones of the >>> addons that I'm using are not working anymore. Also, firefox crashes on >>> exit. >>> >>> *not* funny. >> >> can you please elaborate what you are doing on which distribution and so o= n? >=20 > I'm running Leap 15.0 and have the mozilla repository enabled, so that I ha= ve=20 > the same firefox on linux that I have on windows, mainly because some of th= e=20 > addons that I use refuse to work on anything older than the latest firefox. Firefox 69 currently does not build on 15.0 due to old rust toolchain and the rust guys not providing successful rust builds for 15.0 at this moment unfortunately so the toolchain import does not work. Firefox 68.1 is currently building with a hotfix because the packages provided for a very short time before were broken on x86(-64) therefore I wiped the binaries directly after publishing. Wolfgang --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============1673087264068065345==-- From mhollstein@t-online.de Mon Sep 9 11:06:09 2019 From: Manfred Hollstein To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 13:06:02 +0200 Message-ID: <20190909110602.GA3785@saturn.hollstein.homelinux.org> In-Reply-To: <0d6120fb-e275-5a01-6c65-61e97b529bb3@rosenauer.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2481459447383183800==" --===============2481459447383183800== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Mon, 09 Sep 2019, 12:02:01 +0200, Wolfgang Rosenauer wrote: > Am 09.09.19 um 11:23 schrieb Mathias Homann: > > Am Montag, 9. September 2019, 10:50:58 CEST schrieb Wolfgang Rosenauer: > >> Am 09.09.19 um 10:47 schrieb Mathias Homann: > >>> not completely unrelated... > >>> > >>> due to the fact that firefox68 AND firefox69 both don't build in the > >>> mozilla project right now my systems have reverted to the mozilla 60.8e= sr > >>> from the updates repo... which means the more important ones of the > >>> addons that I'm using are not working anymore. Also, firefox crashes on > >>> exit. > >>> > >>> *not* funny. > >> > >> can you please elaborate what you are doing on which distribution and so= on? > >=20 > > I'm running Leap 15.0 and have the mozilla repository enabled, so that I = have=20 > > the same firefox on linux that I have on windows, mainly because some of = the=20 > > addons that I use refuse to work on anything older than the latest firefo= x. >=20 > Firefox 69 currently does not build on 15.0 due to old rust toolchain > and the rust guys not providing successful rust builds for 15.0 at this > moment unfortunately so the toolchain import does not work. For the time being, you could use for 15.0, too. I use it for firefox68 and firefox69 (while my firefox68 is not your 68esr atm). > Firefox 68.1 is currently building with a hotfix because the packages > provided for a very short time before were broken on x86(-64) therefore > I wiped the binaries directly after publishing. see above. > Wolfgang Cheers. l8er manfred --===============2481459447383183800== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ0FBZEZpRUVZaTJ0TlIwNHQr RGJZQi9xcjNhVEx6VHJBZWtGQWwxMk1ob0FDZ2tRcjNhVEx6VHIKQWVubEJRLy9hQkkrRloxWTJ1 N2VEcjZiY1VYemw2ckRSWTZndnlRTnpFWm1xYVdlYUFOYWV4WVZneEpoekxoWgpyQzNqQllCSlRQ NEkvNG5UakRHdStNcitIQTh1a2lBa1RNRzd6aG4rOG90SjlManpKUVU5ZWJCMVQrQkw0MVd0ClBE MlRQZUxCeGxKR3JLUmNDSUxDU01CejJjeCt5TzI1dWNQOFhBbld3dHNkY3hFOW9Pd0pqcnZEWkJz Q25rNlQKZ2p0S1VDKy9aVkwrU3M2QzVkcDd1aHhoZ3E3OTYvbERRLytnK1BlN2JGenM3QjdEeTUw MmphWWxCeXRLVUpsNAp0NHdzSytUSG0wYUdMNFBQajhFT1Y1VUpkek45aitBR2hrM1ZtaWpWdTQ1 ak8yb3JKbFBLN1MvZXo2dXVVc0g0CjVrT2NQM1pXU2xVcWdQalZBRm9LRjB0YU4wQXNLVGZPYmtn T0djQ0c1YkhKc3ZsN0tzWFNTdTQ2azhiQyt6Nm4KMjBReGFMbTExWWhpM0QzZE51T2UxWVpCUWVT TWdraHp3WDI4MkRZNVlWV0ZGVEhCUVdKQkxBaVRISzdCQUM3RQplODhTRGJFejlGSmM4VXgrUjdO bUw3Y3V3RDRQTW5lYUhKUHNxOERYUE9Tb3M0d2dmM1NmYVBlOERubUQxSXNOCkxhTXc1cGZJb1k4 RnE3ZkdVMjdUZUk4SjdSeUI3S3NEOUcvQTBML3JWWlNXTjJ3ZEh6ejh5TUZJbjlvNVZKejEKcmtK U3NXK0hQUkZ3eTJTa3hENm5GM1ZrWDVmeTdsZnBKWGRFT0o0ZE5IQklxRDhlOWszZHV5ZEtyT0xD OGo3SApGMUdCRTJLU0JDRnRQc3NyTVlidW8rUE1lR3B3K0s2QklWZDZ6Mlk3NjFURTRweVRRV3M9 Cj1wWjlTCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============2481459447383183800==-- From Mathias.Homann@opensuse.org Mon Sep 9 17:21:42 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 19:21:30 +0200 Message-ID: <2452318.qgheFTYX6y@kirika.eregion.home> In-Reply-To: <0d6120fb-e275-5a01-6c65-61e97b529bb3@rosenauer.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6932994087800810933==" --===============6932994087800810933== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang Rosenauer: > Firefox 68.1 is currently building with a hotfix because the packages > provided for a very short time before were broken on x86(-64) therefore > I wiped the binaries directly after publishing. dude, if you ever find yourself somewhere in southern lower saxony and in desperate need of beer, coffee, or sandwiches, gimme a holler. -- *Mathias Homann* Mathias.Homann(a)openSUSE.org[1] telegram: https://telegram.me/lemmy98[2] irc: [lemmy] on freenode and ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 * -------- [1] mailto:Mathias.Homann(a)eregion.de [2] https://telegram.me/lemmy98 --===============6932994087800810933== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRR3pCQUFCQ0FBZEZpRUVnQ2tpUVBUZGQz Ym4wc0JDYTQ0Q25oUHl3UUlGQWwxMmlob0FDZ2tRYTQ0Q25oUHkKd1FJVkFnd0FzVUl4V0lqSnAy WU9XNFF4alhZRXpKOUxPUEZOV1FLdWNHMTg0cWRyWXRwN1MwOEpEK2N1Sk5qRgozbWY1dzZRazY2 UTZCWno3S1J2SnVCRksrZTRCUTUzaldhV2dtbmJsQkJLQ2srL29qVjJYV1hkV3pHSXdUems2ClYr dkpyK2RwdjlJUXRFK0JLQlU4T3R0aS9JM1AyNDlhNlBtdHl0Q3E5UXV3TW81ekVpODdXYnkzSlNo eG84MTQKUGhVUU54SnNtZDlsSjFRWXpONXFvT043T0xhWk5DSHYxR2lvR3I2eFhlelB2ZUgvL09v aUxKS3phN0t1MEpDNwpyNkduY2F5NHFkZWdtL2hjenVHNXlXWG1MN2YyY0JGblBHQXZNdEJ2a3B1 NDE2emFHZ2tPaGlINFQxOHpxeDB5Ck1XSVpmR2VFSlFJS1RLNW0zMmxiRDI2dHhFUGlUdmp0Ujlr UjNvdVJpb2NzT2tSNlJHR2pKMUsxNkk3Q1laNlgKcDh4UU1JSDBmWnlqVWFEK2pLSllQNmZTVmda Wk1FZ1hlUHVHT20vSWxmc1I4QUJvUXJQSm9nY09ydS9rN2RXQgpwN3k4bW00NXJ2V2w1SmFJTndo aWZYMThza0JQU05SQ05NZE5kb1EvaUJzNHg1SE01M2JtMDJHMEJXVUVTNytNCnZ2N05LU1ZMCj1D djhaCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============6932994087800810933==-- From Mathias.Homann@opensuse.org Mon Sep 9 19:46:53 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 21:46:43 +0200 Message-ID: <2092262.VxvneAnzs4@kirika.eregion.home> In-Reply-To: <0d6120fb-e275-5a01-6c65-61e97b529bb3@rosenauer.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4456314013378804935==" --===============4456314013378804935== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang Rosenauer: > Firefox 68.1 is currently building with a hotfix because the packages > provided for a very short time before were broken on x86(-64) therefore > I wiped the binaries directly after publishing. hm. that binary crashes immediately when I start any video playback (youtube, twitch). Cheers MH *Mathias Homann* Mathias.Homann(a)openSUSE.org[1] telegram: https://telegram.me/lemmy98[2] irc: [lemmy] on freenode and ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 * -------- [1] mailto:Mathias.Homann(a)eregion.de [2] https://telegram.me/lemmy98 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============4456314013378804935==-- From wolfgang@rosenauer.org Mon Sep 9 20:31:55 2019 From: Wolfgang Rosenauer To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Mon, 09 Sep 2019 22:31:53 +0200 Message-ID: In-Reply-To: <2092262.VxvneAnzs4@kirika.eregion.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6516662999173597536==" --===============6516662999173597536== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 09.09.19 um 21:46 schrieb Mathias Homann: > Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang Rosenauer: >=20 >=20 >> Firefox 68.1 is currently building with a hotfix because the packages >> provided for a very short time before were broken on x86(-64) therefore >> I wiped the binaries directly after publishing. >=20 >=20 > hm. that binary crashes immediately when I start any video playback (youtub= e,=20 > twitch). hmm, unfortunate. But yes, I found another bug in that build which _should_ just cause a bad video coloring. At least that is what is happening for me. If it crashes for you that is quite a bigger issue. The bug should be fixed with recent submission but as I also needed to fix something in NSPR for Tumbleweed the whole repo needs to rebuild which now will take again some time. Wolfgang --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6516662999173597536==-- From Mathias.Homann@opensuse.org Tue Sep 10 06:00:48 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Tue, 10 Sep 2019 08:00:38 +0200 Message-ID: <19850752.QMBBMSJqLP@kirika.eregion.home> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7313748274467715953==" --===============7313748274467715953== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Montag, 9. September 2019, 22:31:53 CEST schrieb Wolfgang Rosenauer: > Am 09.09.19 um 21:46 schrieb Mathias Homann: > > Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang Rosenauer: > >> Firefox 68.1 is currently building with a hotfix because the packages > >> provided for a very short time before were broken on x86(-64) therefore > >> I wiped the binaries directly after publishing. > > > > hm. that binary crashes immediately when I start any video playback > > (youtube, twitch). > > hmm, unfortunate. But yes, I found another bug in that build which > _should_ just cause a bad video coloring. At least that is what is > happening for me. If it crashes for you that is quite a bigger issue. Guess I wasn't completely clear: as soon as I start video playback I can see that the video area is blue - then FF crashes. Detail: nvidia optimus here. Can't test on a "normal" nvidia rig before tomorrow night. > The bug should be fixed with recent submission but as I also needed to > fix something in NSPR for Tumbleweed the whole repo needs to rebuild > which now will take again some time. That's ok, i can just go and have breakfast in the meantime... XD Cheers MH *Mathias Homann* Mathias.Homann(a)openSUSE.org[1] telegram: https://telegram.me/lemmy98[2] irc: [lemmy] on freenode and ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 * -------- [1] mailto:Mathias.Homann(a)eregion.de [2] https://telegram.me/lemmy98 --===============7313748274467715953== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRR3pCQUFCQ0FBZEZpRUVnQ2tpUVBUZGQz Ym4wc0JDYTQ0Q25oUHl3UUlGQWwxM1BBWUFDZ2tRYTQ0Q25oUHkKd1FJR0ZBditOQ1lUL2NhV2VH NlNYeHVSSmZXcGZJa0xkbHEzYVFGdlcyWkhLNHM5OFlTUlkyQkhQS0ZTRTQ4agpqZkRsYmRPUUg5 Ry96a3IvWmxyUSt6dVZFY2MrWGVnMkdnNXV3NmtIQTBaR0JoSUFPWEszU1RWTzRFeEdINisvCnli TXZXMTRqVGFlN1BMQWxCSDJDc3AzT3dTS29UN1JDTHZkbGJCa2h2NzJoYnN6a1Z0SVpaTklsTFFx NURiaXMKajBNOFFoUW1jV3VJdGR3eWJSbkZ2Q1JJaUdXK3RHN3N4TVVSV3B4WFdaalI3L3lpd1N5 V25jUGVsUnMxUEF1TwpHZlRqQ2dLc3IxQ0tuQVpvVTBVeUU2eE1LbFVYQkRFTGhUcGg4Y1RCa1Uv MWM0Tk1CRllpSE1JYWN4Q083ejRJCk0zNEgrZHVUbnRSREtMOHFLbVUwR3NMbmRUSHNYOFNXZUpr aXJsZjRwNUZCTW9NL2l6M0M0ZThLNlRkKzIxSmgKYlhHQmUwV1dYdkhVajJBdVNBNHpOSDd3TTlN SVMrRWpJd3hrUVo1dnVaeU9sWDFWWThGRmNnZ01GODhmRUw5egpyYWZ5OUdGdkkzZWcrUXpmandB akFpTkRxeGFkbW9MREFBR1YwVXU2b0RsWFZsaHFsTWZ0QWd0Nm1KS04rMlQzCmpQcCtOVDFsCj1m djUxCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============7313748274467715953==-- From Mathias.Homann@opensuse.org Wed Sep 11 07:19:20 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Wed, 11 Sep 2019 09:18:59 +0200 Message-ID: <2746730.9Sy1va9NPR@kirika.eregion.home> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6073570510102379464==" --===============6073570510102379464== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Montag, 9. September 2019, 22:31:53 CEST schrieb Wolfgang Rosenauer: > Am 09.09.19 um 21:46 schrieb Mathias Homann: > > Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang Rosenauer: > >> Firefox 68.1 is currently building with a hotfix because the packages > >> provided for a very short time before were broken on x86(-64) therefore > >> I wiped the binaries directly after publishing. > > > > hm. that binary crashes immediately when I start any video playback > > (youtube, twitch). > > hmm, unfortunate. But yes, I found another bug in that build which > _should_ just cause a bad video coloring. At least that is what is > happening for me. If it crashes for you that is quite a bigger issue. > The bug should be fixed with recent submission but as I also needed to > fix something in NSPR for Tumbleweed the whole repo needs to rebuild > which now will take again some time. > > > Wolfgang By now I'm running the binaries from that last build, no more blue videos and no more crashes. What I said about beer/coffee/sandwiches stands. Cheers MH -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6073570510102379464==-- From Mathias.Homann@openSUSE.org Fri Sep 13 06:15:43 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 13 Sep 2019 08:15:32 +0200 Message-ID: <5edb9d90d35b822adf1dde2f86523c18@openSUSE.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3000406138075183863==" --===============3000406138075183863== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 2019-09-09 22:31, schrieb Wolfgang Rosenauer: > Am 09.09.19 um 21:46 schrieb Mathias Homann: >> Am Montag, 9. September 2019, 12:02:01 CEST schrieb Wolfgang >> Rosenauer: >> >> >>> Firefox 68.1 is currently building with a hotfix because the packages >>> provided for a very short time before were broken on x86(-64) >>> therefore >>> I wiped the binaries directly after publishing. >> >> >> hm. that binary crashes immediately when I start any video playback >> (youtube, >> twitch). > > hmm, unfortunate. But yes, I found another bug in that build which > _should_ just cause a bad video coloring. At least that is what is > happening for me. If it crashes for you that is quite a bigger issue. > The bug should be fixed with recent submission but as I also needed to > fix something in NSPR for Tumbleweed the whole repo needs to rebuild > which now will take again some time. not completely unrelated: could you please turn on publishing on the thunderbird68 package but leave building disabled, then wipe its binaries? After they have been removed from the repos you can turn publishing off again... right now the repos contain Thunderbird 68.0 which is basically broken when it comes to addons, and Thunderbird 60.9 which works fine but gets replaced by the broken tb 68 unless you lock it... Cheers Mathias -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============3000406138075183863==-- From wolfgang@rosenauer.org Fri Sep 13 06:34:18 2019 From: Wolfgang Rosenauer To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 13 Sep 2019 08:34:14 +0200 Message-ID: In-Reply-To: <5edb9d90d35b822adf1dde2f86523c18@openSUSE.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0356154888208986131==" --===============0356154888208986131== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, Am 13.09.19 um 08:15 schrieb Mathias Homann: > > not completely unrelated: could you please turn on publishing on the > thunderbird68 package but leave building disabled, then wipe its binaries? > After they have been removed from the repos you can turn publishing off > again... right now the repos contain Thunderbird 68.0 which is basically > broken when it comes to addons, and Thunderbird 60.9 which works fine > but gets replaced by the broken tb 68 unless you lock it... hmm, what do you mean by "basically broken when it comes to addons"? The fact that it does not support old-style xul addons but only webextensions? Or is there anything else? If it's the former there is no reason to remove TB68 because the change will happen anyway. The plan also is to go to 68.1 in Tumbleweed within the next days. The only way to stay with TB 68.9 (I'm not even sure if there will be a 60.10 is to lock it anyway which is always the case if a new version arrives. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============0356154888208986131==-- From Mathias.Homann@opensuse.org Fri Sep 13 07:09:16 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 13 Sep 2019 09:09:03 +0200 Message-ID: <2643648.yK5MgOiI8u@kirika.eregion.home> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4386877920299155457==" --===============4386877920299155457== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Freitag, 13. September 2019, 08:34:14 CEST schrieb Wolfgang Rosenauer: > Hi, > > Am 13.09.19 um 08:15 schrieb Mathias Homann: > > not completely unrelated: could you please turn on publishing on the > > thunderbird68 package but leave building disabled, then wipe its binaries? > > After they have been removed from the repos you can turn publishing off > > again... right now the repos contain Thunderbird 68.0 which is basically > > broken when it comes to addons, and Thunderbird 60.9 which works fine > > but gets replaced by the broken tb 68 unless you lock it... > > hmm, what do you mean by "basically broken when it comes to addons"? > The fact that it does not support old-style xul addons but only > webextensions? Or is there anything else? well, there is the fact that so far no addons have actually been updated, or if they have they don't work - not even the ones that come packaged with it., like lightning. > If it's the former there is no reason to remove TB68 because the change > will happen anyway. maybe then the change shouldn't happen yet? > The plan also is to go to 68.1 in Tumbleweed within the next days. > The only way to stay with TB 68.9 (I'm not even sure if there will be a > 60.10 is to lock it anyway which is always the case if a new version > arrives. guess i'll end up having to do that then - but then maybe you could turn *on* pubishing for a moment, so that the already built 68.1 actually gets out? Or is there still work to be done on that package? I'm trying the 68.1 binaries right now, and the first I see is this: https://gyazo.com/2e1b4633008da15847bd49ffe84921c3 Cheers MH *Mathias Homann* Mathias.Homann(a)openSUSE.org[2] telegram: https://telegram.me/lemmy98[3] irc: [lemmy] on freenode and ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 * -------- [1] https://gyazo.com/2e1b4633008da15847bd49ffe84921c3 [2] mailto:Mathias.Homann(a)eregion.de [3] https://telegram.me/lemmy98 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============4386877920299155457==-- From wolfgang@rosenauer.org Fri Sep 13 07:40:43 2019 From: Wolfgang Rosenauer To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 13 Sep 2019 09:40:40 +0200 Message-ID: In-Reply-To: <2643648.yK5MgOiI8u@kirika.eregion.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6357663152076277088==" --===============6357663152076277088== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 13.09.19 um 09:09 schrieb Mathias Homann: > Am Freitag, 13. September 2019, 08:34:14 CEST schrieb Wolfgang Rosenauer: >> Hi, >> >> Am 13.09.19 um 08:15 schrieb Mathias Homann: >>> not completely unrelated: could you please turn on publishing on the >>> thunderbird68 package but leave building disabled, then wipe its binaries? >>> After they have been removed from the repos you can turn publishing off >>> again... right now the repos contain Thunderbird 68.0 which is basically >>> broken when it comes to addons, and Thunderbird 60.9 which works fine >>> but gets replaced by the broken tb 68 unless you lock it... >> >> hmm, what do you mean by "basically broken when it comes to addons"? >> The fact that it does not support old-style xul addons but only >> webextensions? Or is there anything else? >=20 > well, there is the fact that so far no addons have actually been updated, o= r=20 > if they have they don't work - not even the ones that come packaged with it= .,=20 > like lightning. >=20 >> If it's the former there is no reason to remove TB68 because the change >> will happen anyway. >=20 > maybe then the change shouldn't happen yet? That is what people said when Firefox dropped old-style extension support. And it's similar for a lot of things: At some point it needs to be enforced otherwise it will never happen. I do not say that the timing is perfect but it is how it is. I cannot change anything really. I can try to find out if there is another 60.x release but if not there is no real choice. Otherwise we have bought 4-6 more weeks during that period other people would complain to not get 68.x. >> The plan also is to go to 68.1 in Tumbleweed within the next days. >> The only way to stay with TB 68.9 (I'm not even sure if there will be a >> 60.10 is to lock it anyway which is always the case if a new version >> arrives. >=20 > guess i'll end up having to do that then - but then maybe you could turn *o= n*=20 > pubishing for a moment, so that the already built 68.1 actually gets out? O= r=20 > is there still work to be done on that package? Publishing is turned on. Building is off to save OBS cycles. For a final build (and probable submission to TW) the security changelog entries are missing. The only issue is that I'm not sure which binaries are actually served exactly and if there was a relevant change since building is disabled. > I'm trying the 68.1 binaries right now, and the first I see is this: >=20 > https://gyazo.com/2e1b4633008da15847bd49ffe84921c3 Since I guess that this is called only on first upgrade of a profile I cannot reproduce easily. I will try. Do you have the full URL somewhere on the screen? Wolfgang --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6357663152076277088==-- From Mathias.Homann@opensuse.org Fri Sep 13 08:06:04 2019 From: Mathias Homann To: buildservice@lists.opensuse.org Subject: Re: [opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not? Date: Fri, 13 Sep 2019 10:05:49 +0200 Message-ID: <5133117.1Fta1lfNTW@kirika.eregion.home> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5179703548014203188==" --===============5179703548014203188== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am Freitag, 13. September 2019, 09:40:40 CEST schrieb Wolfgang Rosenauer: > >> hmm, what do you mean by "basically broken when it comes to addons"? > >> The fact that it does not support old-style xul addons but only > >> webextensions? Or is there anything else? > > > > well, there is the fact that so far no addons have actually been updated, > > or if they have they don't work - not even the ones that come packaged > > with it., like lightning. actually by now *most* of the extesions that I have to have work, after you manually reinstall them - not all, but the important ones, I can get at my calendars and contacts. > > I'm trying the 68.1 binaries right now, and the first I see is this: > > > > https://gyazo.com/2e1b4633008da15847bd49ffe84921c3 > > Since I guess that this is called only on first upgrade of a profile I > cannot reproduce easily. I will try. Do you have the full URL somewhere > on the screen? it actually shows up every time I start TB68 - and there is no full URL anywhere. I'll keep trying 68.1 for a bit. Cheers -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============5179703548014203188==--