April 2020 - openSUSE Release Team - openSUSE Mailing Lists

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - darktable - Build fail notification
by Dr. Werner Fink 24 Apr '20

24 Apr '20

Is this boo#1160739? On 2020/04/23 22:05:14 +0000, openSUSE release team wrote: > Dear Dr. Werner Fink, > > Following-up the reminder of one week ago, we have to inform you that > 'darktable' is still failing in openSUSE:Leap:15.2. See > https://build.opensuse.org/package/show/openSUSE:Leap:15.2/darktable > > It has been failing to build since Thu Apr 9 03:05:32 2020. > > Please find the time to fix the build of this package. If needed, > also reach out to the broader community, trying to find somebody to > help you fix this package. > Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 1

[opensuse-releaseteam] Re: Refresh of installation media
by Lubos Kocman 24 Apr '20

24 Apr '20

Hello team I'll rather fire few questions for the discussion than particular decision. Which we can discuss later on the opensuse-release team meeting. https://etherpad.opensuse.org/p/ReleaseEngineering-20200422 (already on agenda) I agree about the media refresh. SLE figured out it's useful, RHEL figured out it's useful (6 weeks batch updates with optional media refresh). I can also see how we could mirror SLE Quarterly updates with image refreshes. However, I also understand that our "superior" installer actually supports updates of itself. Which s not the case for e.g. RHEL. I believe that kernel version should not change during the maintenance phase of Leap, so perhaps installer could simply fetch all kmod updates available. Perhaps it already does that (cc Lukas). I'd assume the OS X network recovery does the same (one image + updates) Nobody seem to be doing both efforts to my knowledge, both installer network updates and media refresh. Either one or the other. Wouldn't this be a duplicated effort then? Or am I wrong and somebody is doing both? Just a brainstorm: If SLE quarterly updates could introduce some changes such as "kernel version bump or larger bootloader/shim change" then I'd be absolutely for media refresh. Just to be clear I'm open to this, if there would be some clear benefit to justify extra work for maintenance team. One use case that would support this is * User is trying to install openSUSE Leap on greatest newest ARM hardware. Leap might receive necessary driver updates during the maintenance lifecycle, otherwise it's unbootable. However we seem to be too much behind with kernel compared to TW. So I suppose such user would rather use TW or custom Leap with a newer kernel. Thoughts? Cheers ________________________________________ From: Axel Braun <axel.braun(a)gmx.de> Sent: Monday, 20 April 2020 13:01 To: Lubos Kocman; Ludwig Nussel Subject: Re: Refresh of installation media Am Montag, 20. April 2020, 09:28:22 CEST schrieb Ludwig Nussel: > Am 20.04.20 um 09:18 schrieb Axel Braun: > > Am Montag, 20. April 2020, 07:35:25 CEST schrieb Ludwig Nussel: > >> Am 19.04.20 um 20:07 schrieb Axel Braun: > >>> do you know if we are refreshing the installation media of Leap - > >>> mainly the DVD - on a regular basis? > >> > >> So far no. > > > > Given the fact that a bunch of updates gets into Leap each month - I guess > > with some new drivers backported into the Kernel as well - I feel it makes > > sense to have updated installation media available. > > > > That could mitigate the complaint that Leap has issues with modern > > hardware. > > > What do you think? > > Doesn't matter. I'm not in charge. Maybe talk to PM, looks like they > know what's good for Leap and what the priorities are now. Well, I thought you and Lubos as former/actual Release Manager are the right persons to talk to.... I have no idea who the PM are..... Cheers Axel -- Dr.-Ing. Axel K. Braun M: +49.173.7003.154 T: @coogor Matrix: @docb:matrix.org PGP Fingerprint: 2E7F 3A19 A4A4 844A 3D09 7656 822D EB64 A3BA 290D Public Key available at http://www.axxite.com/axel.braun@gmx.de.asc Personal Freedom starts with free/libre Software ThinkPad T520 running openSUSE Tumbleweed 20200415 -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

5 6

Re: [opensuse-releaseteam] Re: openSUSE:Leap:15.2 - gli - Build fail notification
by İsmail Dönmez 23 Apr '20

23 Apr '20

Hi, On 23 Apr 13:30 2020, Manfred Hollstein wrote: > Hi there, > > can someone please trigger a rebuild for this package? > > https://build.opensuse.org/package/show/openSUSE:Leap:15.2/gli > > The failure is caused by one test failing from time to time. Re-running > the build succeeds most of the time time, so I guess, this is caused by > some environmental stuff in OBS. FWIW, it never failed in my own build > environment. Triggered. - ismail -- Never attribute to malice that which is adequately explained by laziness. SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)

1 0

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - gli - Build fail notification
by Manfred Hollstein 23 Apr '20

23 Apr '20

Hi there, can someone please trigger a rebuild for this package? https://build.opensuse.org/package/show/openSUSE:Leap:15.2/gli The failure is caused by one test failing from time to time. Re-running the build succeeds most of the time time, so I guess, this is caused by some environmental stuff in OBS. FWIW, it never failed in my own build environment. Thx, cheers. l8er manfred On Wed, 22 Apr 2020, 00:05:11 +0200, openSUSE release team wrote: > Dear Manfred Hollstein, > > Please be informed that 'gli' in openSUSE:Leap:15.2 has > not had a successful build since Tue Apr 14 20:05:50 2020. See > https://build.opensuse.org/package/show/openSUSE:Leap:15.2/gli > > This can be due to an error in your package directly or could be > caused by a package you depend on to build. In any case, please do > your utmost to get the status back to building. > > You will get another reminder in a week if the package still fails > by then. > > *** NOTE: > This is an attempt to raise awareness of the maintainers about > broken builds in openSUSE:Leap:15.2. You receive this mail because you are > marked as maintainer for the above mentioned package (or project > maintainer if the package has no explicit maintainer assigned) > > Kind regards, > openSUSE release team <opensuse-releaseteam(a)opensuse.org>

1 0

[opensuse-releaseteam] Re: [opensuse-factory] openSUSE:Leap:15.2 - Build fail notification
by Stasiek Michalski 15 Apr '20

15 Apr '20

On Wed, Apr 15, 2020 at 22:09, openSUSE release team <opensuse-releaseteam(a)opensuse.org> 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. > > - python-psycopg2 It's a shame we don't have file dependencies working, since this package relies on pg_config executable, which has been moved from postgresql-devel to postgresql-server-devel. Fixing the dep name is a hot patch at best, since the script isn't looking for any other functionality outside of having this executable working, and obviously the package name can change at any time in the future, breaking the build again. In any case, here you go https://build.opensuse.org/package/show/home:hellcp:branches:openSUSE:Leap:… LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 0

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - orthanc-wsi - Build fail notification
by Axel Braun 08 Apr '20

08 Apr '20

Hi, Am Mittwoch, 8. April 2020, 00:05:19 CEST schrieben Sie: > Please be informed that 'orthanc-wsi' in openSUSE:Leap:15.2 has > not had a successful build since Tue Mar 31 05:36:57 2020. See > https://build.opensuse.org/package/show/openSUSE:Leap:15.2/orthanc-wsi This is a consequence of the version change to 1.6.0, see: https://groups.google.com/forum/?hl=de#!topic/orthanc-users/m7sJS9umZCI and to be honest, I'm not happy with the reaction of upstream. The proposal from upstream (use debian approach) needs at least some more investigation. If that does not help, we revert to 1.5.8 Cheers Axel -- Dr.-Ing. Axel K. Braun M: +49.173.7003.154 T: @coogor Matrix: @docb:matrix.org PGP Fingerprint: 2E7F 3A19 A4A4 844A 3D09 7656 822D EB64 A3BA 290D Public Key available at http://www.axxite.com/axel.braun@gmx.de.asc Personal Freedom starts with free/libre Software.... ...running openSUSE Leap 15.1 -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 0

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - mgetty - Build fail notification
by Dirk Müller 06 Apr '20

06 Apr '20

Hi, this is known and being fixed - see https://smelt.suse.de/request/215148/ Greetings, Dirk > Am 06.04.2020 um 00:05 schrieb openSUSE release team <opensuse-releaseteam(a)opensuse.org>: > > Dear Dirk Mueller, > > Following-up the reminder of one week ago, we have to inform you that > 'mgetty' is still failing in openSUSE:Leap:15.2. See > https://build.opensuse.org/package/show/openSUSE:Leap:15.2/mgetty > > It has been failing to build since Sat Mar 21 05:34:14 2020. > > Please find the time to fix the build of this package. If needed, > also reach out to the broader community, trying to find somebody to > help you fix this package. > > *** NOTE: > This is an attempt to raise awareness of the maintainers about > broken builds in Tumbleweed. You receive this mail because you are > marked as maintainer for the above mentioned package (or project > maintainer if the package has no explicit maintainer assigned) > > Kind regards, > openSUSE release team <opensuse-releaseteam(a)opensuse.org> -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 0

2022

2021

2020

2019

2018

2017

openSUSE Release Team April 2020