[opensuse-factory] openSUSE:Leap:15.2 - Build fail notification
Dear Package maintainers and hackers. Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - oprofile - perf - raylib Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Leap:15.2. Kind regards, openSUSE release team <opensuse-releaseteam@opensuse.org>
Am 06.05.20 um 00:05 schrieb openSUSE release team:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks [...] - perf
This seems to come from SUSE:SLE-15-SP2:GA, could someone at SUSE please have a look at this? It would really be a shame if Leap 15.2 came without perf. Best regards, Aaron -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, May 07, 2020 at 01:20:01AM +0200, Aaron Puchert wrote:
Am 06.05.20 um 00:05 schrieb openSUSE release team:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks [...] - perf
This seems to come from SUSE:SLE-15-SP2:GA, could someone at SUSE please have a look at this? It would really be a shame if Leap 15.2 came without perf.
Hi Aaron Both oprofile and perf were fixed yesterday in Leap. As discussed, it appears the maintainer db isn't correct for Leap and they are not failing in SLE15-SP2. The Leap failures were due to a binutils version bump. Thanks! Tony -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, May 05, 2020 at 10:05:13PM +0000, openSUSE release team wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
- oprofile - perf
I have no recollection of receiving any kind of notification that these would not build. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, May 07, 2020 at 05:20:00PM -0700, Tony Jones wrote:
On Tue, May 05, 2020 at 10:05:13PM +0000, openSUSE release team wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
- oprofile - perf
I have no recollection of receiving any kind of notification that these would not build.
Also, if you going to all the trouble of sending such a warning to the ML, how hard is it to add the maintainer of each package listed to the Cc: line? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 8. Mai 2020, 02:20:00 CEST schrieb Tony Jones:
On Tue, May 05, 2020 at 10:05:13PM +0000, openSUSE release team wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
- oprofile - perf
I have no recollection of receiving any kind of notification that these would not build.
Please check your settings: Profile -> Change your notifications -> Package has failed to build HTh Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2020-05-07 at 17:20 -0700, Tony Jones wrote:
On Tue, May 05, 2020 at 10:05:13PM +0000, openSUSE release team wrote:
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted.
- oprofile - perf
I have no recollection of receiving any kind of notification that these would not build.
osc maintainer openSUSE:Leap:15.2 perf bugowner of openSUSE:Leap:15.2 :
I had a quick look as to why you should not have received an email here, and sadly I found: - maintainer of openSUSE:Leap:15.2 : coolo-factory, jberry_factory, lkocman-factory, lnussel_factory, maxlin_factory The bugowner/maintainer information for Leap is non-existant. So the script that sends out those notification mails can't actually find to whom this should be sent. Something for the Leap Release Manager to find a solution for. Cheers, Dominique
On 5/8/20 5:14 PM, Dominique Leuenberger / DimStar wrote: > On Thu, 2020-05-07 at 17:20 -0700, Tony Jones wrote: >> On Tue, May 05, 2020 at 10:05:13PM +0000, openSUSE release team wrote: >>> Dear Package maintainers and hackers. >>> >>> Below package(s) in openSUSE:Leap:15.2 have been failing to build for at >>> least 4 weeks. We tried to send out notifications to the >>> configured bugowner/maintainers of the package(s), but so far no >>> fix has been submitted. This probably means that the >>> maintainer/bugowner did not yet find the time to look into the >>> matter and he/she would certainly appreciate help to get this >>> sorted. >>> >>> - oprofile >>> - perf >> >> I have no recollection of receiving any kind of notification that these would not build. > > I had a quick look as to why you should not have received an email > here, and sadly I found: > >> osc maintainer openSUSE:Leap:15.2 perf > bugowner of openSUSE:Leap:15.2 : > - > > maintainer of openSUSE:Leap:15.2 : > coolo-factory, jberry_factory, lkocman-factory, lnussel_factory, > maxlin_factory > > The bugowner/maintainer information for Leap is non-existant. So the > script that sends out those notification mails can't actually find to > whom this should be sent. Something for the Leap Release Manager to > find a solution for. Would it not make much more sense for the script to call "osc maintainer perf" Our current setup is not designed to handle someone being a maintainer in tumbleweed but not leap (or the other way) even packages that come from SLE should have the SUSE maintainer listed as one of the obs maintainers (If they are not listed that's a bug in process that needs fixing). Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Fri, 2020-05-08 at 17:32 +0930, Simon Lees wrote:
Would it not make much more sense for the script to call "osc maintainer perf" Our current setup is not designed to handle someone being a maintainer in tumbleweed but not leap (or the other way) even packages that come from SLE should have the SUSE maintainer listed as one of the obs maintainers (If they are not listed that's a bug in process that needs fixing).
Lt me just give one counter-example:
osc maintainer meson Defined in package: devel:tools:building/meson bugowner of meson : XRevan86
maintainer of meson : XRevan86, dimstar None of those are SLE-maintainers; yet, the package is in SLE (and has maintainers assigned, I'd hope) and in Leap Sot hat guaranteed overlap is not a given (this is juts one example I was almost sure would be like this. I bet there are more like this around) Cheers Dominique PS: yes, one can claim that I am @suse and thus inherently the SLE maintainer, But that's now how it defacto works. Obviously, I'd help out in case of need.
On 5/8/20 6:32 PM, Dominique Leuenberger / DimStar wrote:
On Fri, 2020-05-08 at 17:32 +0930, Simon Lees wrote:
Would it not make much more sense for the script to call "osc maintainer perf" Our current setup is not designed to handle someone being a maintainer in tumbleweed but not leap (or the other way) even packages that come from SLE should have the SUSE maintainer listed as one of the obs maintainers (If they are not listed that's a bug in process that needs fixing).
Lt me just give one counter-example:
osc maintainer meson Defined in package: devel:tools:building/meson bugowner of meson : XRevan86
maintainer of meson : XRevan86, dimstar
None of those are SLE-maintainers; yet, the package is in SLE (and has maintainers assigned, I'd hope) and in Leap
Sot hat guaranteed overlap is not a given (this is juts one example I was almost sure would be like this. I bet there are more like this around)
Cheers Dominique
PS: yes, one can claim that I am @suse and thus inherently the SLE maintainer, But that's now how it defacto works. Obviously, I'd help out in case of need.
I do have a script that checks this somewhere, I guess I should run it again next week, but last time I ran it we had fixed most of these cases. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Fri, 2020-05-08 at 18:37 +0930, Simon Lees wrote:
osc maintainer meson
Defined in package: devel:tools:building/meson bugowner of meson : XRevan86
maintainer of meson : XRevan86, dimstar
None of those are SLE-maintainers; yet, the package is in SLE (and has maintainers assigned, I'd hope) and in Leap
Sot hat guaranteed overlap is not a given (this is juts one example I was almost sure would be like this. I bet there are more like this around)
Cheers Dominique
PS: yes, one can claim that I am @suse and thus inherently the SLE maintainer, But that's now how it defacto works. Obviously, I'd help out in case of need.
I do have a script that checks this somewhere, I guess I should run it again next week, but last time I ran it we had fixed most of these cases.
I don't think I'd want to accept other people as maintainer of this package. xrevan and myself havae been doing all the lifting here, we harldy have bugs (there is currently one for gcc10 test suite failures); so just 'forcing' a SLE maintainer onto the openSUSE package could be seen as a hostile takeover. Which reminds me back to the days of SUSE Linux 10.x and early openSUSE days, when a community member needed a 'sponsor' from SUSE to get a package acceptable to the distro. Submitrequests can be created by everybody - not only maintainers. Cheers, Dominique
On 5/8/20 6:43 PM, Dominique Leuenberger / DimStar wrote:
On Fri, 2020-05-08 at 18:37 +0930, Simon Lees wrote:
osc maintainer meson
Defined in package: devel:tools:building/meson bugowner of meson : XRevan86
maintainer of meson : XRevan86, dimstar
None of those are SLE-maintainers; yet, the package is in SLE (and has maintainers assigned, I'd hope) and in Leap
Sot hat guaranteed overlap is not a given (this is juts one example I was almost sure would be like this. I bet there are more like this around)
Cheers Dominique
PS: yes, one can claim that I am @suse and thus inherently the SLE maintainer, But that's now how it defacto works. Obviously, I'd help out in case of need.
I do have a script that checks this somewhere, I guess I should run it again next week, but last time I ran it we had fixed most of these cases.
I don't think I'd want to accept other people as maintainer of this package. xrevan and myself havae been doing all the lifting here, we harldy have bugs (there is currently one for gcc10 test suite failures); so just 'forcing' a SLE maintainer onto the openSUSE package could be seen as a hostile takeover. Which reminds me back to the days of SUSE Linux 10.x and early openSUSE days, when a community member needed a 'sponsor' from SUSE to get a package acceptable to the distro.
Submitrequests can be created by everybody - not only maintainers.
The official policy is that they should contact you both and discuss what co maintainership should look like, because generally speaking for shared (SLE/Leap) not just anyone can do submit requests. In some cases this might look like the community maintainers still doing pretty much everything including reviewing any of the SUSE maintainers submissions with the SUSE maintainer simply helping to get the right stuff into SLE and Leap through to everyone working equally and everything in between. This has been the approach everywhere else and I haven't heard of any issues. But maybe in this case there could be an exception given that there is someone in this case who has access. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (6)
-
Aaron Puchert -
Axel Braun -
Dominique Leuenberger / DimStar -
openSUSE release team -
Simon Lees -
Tony Jones