openSUSE Release Team May 2020

releaseteam@lists.opensuse.org

7 participants
5 discussions

[opensuse-releaseteam] Re: Packages you maintain are present in openSUSE:Leap:15.2

by Dave Plater

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 year, 12 months

[opensuse-releaseteam] next steps with sysconfig in SLE and openSUSE Leap 15.2 ( bsc#1171495)

by Lubos Kocman

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 years

[opensuse-releaseteam] Re: openSUSE:Leap:15.2 - Build fail notification

by Aaron Puchert

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 years

[opensuse-releaseteam] Re: [opensuse-factory] openSUSE:Leap:15.2 - Build fail notification

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

2 years

[opensuse-releaseteam] transactional-update test in openQA

by Ludwig Nussel

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 years

2022

2021

2020

2019

2018

2017

openSUSE Release Team May 2020