- openSUSE Release Team

New devel project: devel:languages:rust:crates
by Matwey Kornilov 03 Dec '20

03 Dec '20

Hi, Could you please add devel:languages:rust:crates as a devel project for Factory? I would like to submit rust-zram-generator (upstream project URL: https://github.com/systemd/zram-generator ). It is systemd generator for creating compressed RAM (swap in RAM) devices. This kind of swap is popular on single board computers where RAM is limited and microSD card is not quite endurant for running swap on it.

3 2

[opensuse-releaseteam] Mailing Lists Migration 10. Nov
by openSUSE Admins 09 Nov '20

09 Nov '20

Hi, We will be temporarly freezing the openSUSE Mailing Lists infrastructure for the time of migration on 10. Nov 2020 after 10:00 CET. We will send out another email confirming the details of the migration once it's finished. You can read on the details of the migration at https://en.opensuse.org/openSUSE:Mailing_Lists_Migration You are subscribed to the following mailing lists: opensuse-factory To unsubscribe from a mailing list, send an email to {listname}+unsubscribe(a)opensuse.org (for example opensuse-factory+unsubscribe(a)opensuse.org for the opensuse-factory mailing list) Sorry for the inconvenience, openSUSE Mailing Lists Admins -- 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] New devel project: X11:Solus
by Callum Farmer 09 Aug '20

09 Aug '20

Budgie desktop environment is now being maintained by me after re-inclusion was requested on Reddit. SRs are being declined by Factory Auto bot because the project was de-registered after being unmaintained. So, I need it re-registered as a Factory devel project. Thanks, -- Callum Farmer callumjfarmer13(a)gmail.com openSUSE/GitHub/GitLab - gmbr3 -- 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: Packages you maintain are present in openSUSE:Leap:15.2
by Dave Plater 29 May '20

29 May '20

On 5/28/20, Ludwig Nussel <ludwig.nussel(a)suse.de> wrote: > This is a friendly reminder about your packages in openSUSE:Leap:15.2. > > Please verify that the included packages are working as intended and > have versions appropriate for a stable release. Changes may be submitted > until > April 26th [at the latest]. > Hi, I just wondered if the above date is correct. Thanks Dave -- 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] next steps with sysconfig in SLE and openSUSE Leap 15.2 ( bsc#1171495)
by Lubos Kocman 12 May '20

12 May '20

Hello team, we have two problems * openSUSE Leap upgrade from 15.1 to 15.2 is reporting downgrade of sysconfig (Thanks to Darix for raising the issue) * Backporting of change from Factory to SLE (bsc#1171495) has a negative feedback from Thorsten. Previous discussion about the issue can be found here https://bugzilla.suse.com/show_bug.cgi?id=1159566 Seems like we have a conflict of opinions and our time window of when we can still change something in SP2/Leap 15.2 is getting short. As per Thorsten's comment I did already open an RFE https://github.com/openSUSE/openSUSE-release-tools/issues/2439 for openSUSE release tools to ignore conflict on %ghost files. What are next steps? My main concern is not to have a broken product / project. Thank you Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

2 1

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - Build fail notification
by Aaron Puchert 08 May '20

08 May '20

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-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

2 1

[opensuse-releaseteam] Re: [opensuse-factory] openSUSE:Leap:15.2 - Build fail notification
by Tony Jones 08 May '20

08 May '20

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-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

1 1

[opensuse-releaseteam] transactional-update test in openQA
by Ludwig Nussel 06 May '20

06 May '20

Hi, Looking at the test fail of transactional-update for MicroOS 15.2: https://openqa.opensuse.org/tests/1256193#step/transactional_update/11 So the test has a tarball with ready made rpms that it wants to install. Now this fails on MicroOS 15.2. Turns out that maintenance bumped¹ the version of the update test packages to 5.1 so that's what I have in 15.2. Wheres that tarball was built with Factory packages that have version 5. The version doesn't really matter for the Tumbleweed tests as the update-test packages are not installed by default there. Stable distros do have them by default though during beta test. So calling zypper in on a package with lower version will not do anything. Of course we could version bump the package in Factory, rebuild the tarball and have newer version rpms. I fear that this would just work temporarily though until release numbers increase. So how about changing the test to not use a tarball but install from the repo instead, ie just calling transactional-update with package name rather than filename? Looks like even Factory has the update test packages in the :Update repo. So should work, right? cu Ludwig [1] bug 1070228, I already asked to apply the change to Factory too -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, HRB 36809 (AG Nürnberg), GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org

2 4

[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