April 2020 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Closing The Leap Gap Weekly Update Meeting 30.04.2020
by Lubos Kocman 04 May '20

04 May '20

Closing the Leap Gap - Weekly Update All meeting minutes can be found here: https://etherpad.opensuse.org/p/ClosingTheLeapGap-meeting Attendees (please add yourself): gp, vmoutoussamy, lpechacek, mawerner, lkocman, mmeissner, sbehlert, jsrain =================================== 1.0 Project plan: https://confluence.suse.com/display/leap/Project+plan =================================== 2.0 Schedule: https://en.opensuse.org/openSUSE:Roadmap openSUSE Leap 15.2 FCS July 2nd 2020 =================================== 3.0 Priority items and blockers List of features marked as "DeveloperProgram" https://jira.suse.com/secure/Dashboard.jspa?selectPageId=34230 JUMP related work is tracked here https://progress.opensuse.org/projects/jump_152/issues Simplified Feature request for openSUSE Leap contributors https://jira.suse.com/browse/JIRA-722 No blockers as of today. =================================== 4.0 Updates from individual teams =================================== 4.1 Product Management Owner: Stefan Behlert Next round of Feature reviews set-up for Wednesday next week. We are progressing nicely on the features, as far as PM can see, but there are still some hills before us. Matthias: Features are ongoing, Stefan and Michal are constantly reviewing project related features. It's quite a lot of requests. Handing of External communication in progress. =================================== 4.2 openSUSE Leap Release Management Owner: Lubos Kocman Friday meeting with QA Maintenance resulted in the following action items: * Have a statistics about tracked SLE Community requests as part of openSUSE Leap 15.2 retrospective. * Add a weekly update about SLE Community requests to openSUSE Release Engineering meeting A CtLG guidance for where to submit request: https://confluence.suse.com/pages/viewpage.action?pageId=476709080 =================================== 4.3. openSUSE Leap Release Engineering Owner: Max Lin Not available =================================== 4.4 SLE Release Management Owner: Alex Herzig, Stefan Weiberg Yast - Issues with 32 bit kernel, this is already clarified (there will be no i586 kernel). These packages will be accepted on staging later today. =================================== 4.5 Autobuild Owner: Lars Vogdt, Adrian Schroeter No udate on Jump project itself. We had a meeting regarding handling of Source submissions with focus on backports project. We've agreed that we'll have a build service extension, and any submission against Jump will be redirected to backports. We will need to discuss with SLE people and autobuild team on how to handle submissions for core packages. We need to take care of handling of submissions against maintenance project (e.g. in case that package origin is SUSE:SLE-15- SP0*) A full ftp tree build is now finished. =================================== 4.6 Maintenance Owner: Stephan Barth Stephan: Same like last week: no news, waiting for workable items. =================================== 4.7 Security Owner: Marcus Meissner No upate, Marcus is involved in current CtLG features. Clarification of ECO and CtLG. This will be covered in FAQ https://confluence.suse.com/pages/viewpage.action?pageId=476709080 =================================== 4.8 Packagehub Owner: Wolfgang Engel Not available. Ismail and Wolfgang were available on the previous meeting regarding Jump Sources (see notes bellow). 4.9 Beta Program Owner: Vincent Moutoussamy We've started a draft of communication regarding recent changes towards improved transparency with the community. Communication will not happen until Monday. Gerald offered help to review the document. Thanks Gerald for community teasers. How would be the go/nogo for the CtLG handled? Lubos: Distribution build wise: I'd like to have a installable image build as part of the Jump:15.2 OBS project. Then we'd like have a period of testing for the community, consume fedback and have a Go-Nogo session on the openSUSE Release Engineering meeting. Gerald: There is multiple related efforts, such opening Bugzilla, improving the feature process, merging changes in Leap to SLE, Jump,.... Many of these should quite non-controversial. Unless there is clear pushback, openSUSE tends to follow a "those who do decide". Lubos: the CtLG effort has multiple building blocks. Each block has probably different set of stakeholders or approvers. Let's make sure that we get them all right. Action item for Lubos is to map efforts on https://en.opensuse.org/Portal:Leap - Discuss, Define and be Transparent with the openSUSE Community: Communication sent to openSUSE but also internal SUSE ML (linux@) and Public SLE Beta ML (sle-beta(a)lists.suse.com): https://lists.opensuse.org/opensuse-project/2020-04/msg00145.html - Upcoming news-o-o -> https://github.com/openSUSE/news-o-o/pull/36 I hope to review some to give an initial inputs on the opening bugzilla initiative next week. Gerald: I've read the email thread and there was just one response. Was it just an update or are there any next steps from the email. Vincent: It was intended to be a status update on all of the efforts and initiatives which are currently. Action item: keep opensuse-project@ updated with perhaps changes. This could be first set of incomming bugs and so on. Way for community to engage or see the value. Vincent: the initiative for bugzilla is a longer term effort, so please expect this to take some time. Gerald: Release early, Release often. =================================== 4.10 Engineering / Product Migration Owner: Jiri Srain No update. Discussion regarding yast dependency on kernel. kernel does not exist for i586. No conclusion yet. Current migration scenarion is being tested by QA (roughly for a month already). Have a look into Fedora single click migration. 3 step migration, in principal everything is in. Necessary packages need to be part of opensuse (migration plugin etc.) SCC will have to be configured properly. We'll have to deal with packaging issues regarding branding packages. Everything should be ideally solved on the packaging side. Some hacks can be done but it's not prefered. Current approach is handling all on the packaging side (Effort by Ludwig). Registration schema (for AutoYaST) is currently in the queue for Public RC milestone of SLES. Todo: Migration path from Leap to Jump. =================================== 4.11 Engineering - Kernel Owner: Libor Pechacek Yast package dependency on kernel on i586 has been resolved. Libor does not see any compelling reason, other than support for "old" hardware, for building 32bit kernel so the 32bit topic is closed for the moment on his side. Maybe we should keep Jump with aligned with SLE as much as possibe, to make the migration path to SLE as easy as possible. We don't have 32bit kernel in SLE therefore it shouldn't be in Jump or Leap as well. This topic was raised because of the yast2 buildrequires on kernel. See SLE RM section. Libor is open to hear any other reasoning to have 32bit in Leap. There are two features about RT, what should QA do about them? The highest RT level, does not come for free and development have invested quite a lot of time to get this working. It's a PM decision. lkocman: sync of kernel-rt was approved, but nothing to do for QA yet on any RT features. stefan: We do not expect Leap to ship the full RT product as of now. Libor: Current Leap kernel has bettert RT behavior than SLE, so the fact that we would not include in in Leap seems awkward. Adrian: Jump would get kernel-rt as soon as it's exported, so would have to blacklist it from ftp tree in Leap. Let's postpone pending RT features (lttng, ...) to the next release. =================================== 4.12 Engineering - Desktop Owner: Stefan Weiberg Not available =================================== 4.13 Quality Assurance Owner: Marita Werner Nothing to do for RT in SP2. Team is looking to all features, and checking whether there is some work for them or not. Vincent: Is there a dedicated team on openSUSE, just like in SLE? Lubos: There is an agreement to have a one person a week dedicated to openSUSE Leap. Marita: Outside of regular work there are some people who are involved more into community effort and people who are less. =================================== 4.14 SLE Architect Owner: Thorsten Kukuk Not present, therefore no update. =================================== 4.15 Marketing and Community management Owner: Douglas DeMaio Not available =================================== 4.16 Marketing Customers & Partners Owner: Sarah Whitlock No update this week. =================================== 4.17 Gerald Owner: Gerald ;-) Gerald and Matthias an interview with Swapnil Bhartiya, an online journalist, on CtLG. Will share link when available. =================================== ## Notes from today's (Apr 30) Jump Sources meeting Attendees: Adrian, Dominique, Ismail, Lubos, Max, Wolfgang If package build fails: backports disables the build and wipes out binaries Leap sources feed the backports project. Adrian would do the sync in a way that sources are not part of the Jump project, and are synced to backports instead. Jump would have only "temporarily forked packages". This would be the case only for packages where functionality is different. Dimstar: This approach makes sense, submissions would be sent to openSUSE:Backports project. How do we handle submissions to SUSE: namespace? Currently subject to Community SLE Feature Requests https://jira.suse.com/browse/JIRA-722 Dimstar: openSUSE:Backports will be the dominant part of the openSUSE Leap. How do we help Backports to manage the incoming work? openSUSE Leap resources would be there to help Backports. We're certainly not reducing the number of resources working on openSUSE. Ismail: Joined resources should improve quality for both Leap and SLE. Adrian: All Submissions would happen against Jump:15.2 (later openSUSE:Leap) and would be automatically redirected to openSUSE:Backports. Backports would still inherit sources from SLE, so we'd not be losing any submissions. This would not be a problem as Backports would remove conflicting packages at GA. Adrian is tracking work in https://jira.suse.com/browse/OBS-59 Max: can you submit parallel requests against Backports? Adrian: The build service part is done in this way, it's the tooling that might not support it yet. openSUSE Leap Staging currently supports only single submit requests against a single package. Will Backports support multiple requests per package? Adrian: think it's a good idea but staging tooling is currently the only part that is missing the support. Ismail doesn't see why we shouldn't support this. Backports currently does not have Staging in place. Adrian: I don't know what to do if we have an SR against Jump and if we redirect it. Won't it be "transformed" into a maintenance request? We've agreed not to allow submissions to Jump from others until 15.2 is released. This will then change after the GA. We would track the pending work on pre-integration testing (install- check on synced packages) that will be tracked in openSUSE Release tools. N��r��y隊Z)z{.��r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��r�+��0��Ǩ�

5 6

[opensuse-factory] Renumbering patches and the factory bot
by Martin Wilck 03 May '20

03 May '20

My current request for hamster-time-tracker https://build.opensuse.org/request/show/798689 (needed to make the hamster GNOME extension work with GNOME 3.36) is repeatedly rejected by the factory bot with messages like this: "A patch (0002-Fix-disable-callback-gnome-shell-3.30- compatibility.patch) is being deleted without this removal being mentioned in the changelog." If you look at the changelog, you can see that the patches have been *renumbered* to avoid ambiguity, and that I've documented this in the changelog in detail. Can someone please override the bot? Or if not, can I get some guidance how to document this such that the bot accepts it? Martin -- Dr. Martin Wilck <mwilck(a)suse.com>, Tel. +49 (0)911 74053 2107 SUSE Software Solutions Germany GmbH HRB 36809, AG Nürnberg GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 23

[opensuse-factory] KMail: broken Umlauts
by Axel Braun 02 May '20

02 May '20

Hi, since some days (at least since release 5.13.1, see https://bugs.kde.org/ show_bug.cgi?id=416758 ) I notice broken Umlauts in Emails. Mostly these mails are not UTF-8: ------=_NextPart_000_014F_01D5D2D4.EC19EF40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This did not change with the latest update (5.13.2) as of todays update. Can anyone confirm this issue? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 14

[opensuse-factory] openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 30 Apr '20

30 Apr '20

Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory 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. - firecracker - hidviz - openmw - racer - rav1e - ripgrep Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>

2 1

[opensuse-factory] Modernizing AutoYaST blog post
by Imobach Gonzalez Sosa 30 Apr '20

30 Apr '20

Hi all, We have just published a blog post summarizing some of the ideas related to the "modernizing AutoYaST" initiative. https://yast.opensuse.org/blog/2020-04-30/modernizing-autoyast Not all ideas are there and it is possible that some of them never get implemented. But it is a nice picture of the options we are considering right now. Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

3 3

[opensuse-factory] no network after tw snapshot 20200425
by Stephen Berman 30 Apr '20

30 Apr '20

When I rebooted Tumbleweed after updating to snapshot 20200425 (which included kernel 5.6.6), the Network Manager showed no active wireless network connection (though it listed the router I connect to), and when I tried to reconnect I was requested (by the policy kit security manager?) to enter the root password, but when I did, nothing happened. I have seen no reports of a similar problem. Only after booting a previous snapshot with kernel 5.6.4 was the network available again. When I run `zypper dup' with this snapshot it wants to install everything from snapshot 20200425 and later. What can I do to restore network access on current tw? Steve Berman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] New Tumbleweed snapshot 20200428 released!
by Dominique Leuenberger 30 Apr '20

30 Apr '20

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: irssi patterns-base patterns-server (20200312 -> 20200325) python-numpy (1.18.2 -> 1.18.3) qemu qemu-linux-user timezone (2019c -> 2020a) timezone-java (2019c -> 2020a) vim xf86-video-intel === Details === ==== irssi ==== - added glib-2-63.patch: - Backport a fix that froze Irssi on GLib >2.62 when typing Ctrl+Space (#1180, #1183) ==== patterns-base ==== Subpackages: patterns-base-apparmor patterns-base-base patterns-base-basesystem patterns-base-basic_desktop patterns-base-console patterns-base-documentation patterns-base-enhanced_base patterns-base-minimal_base patterns-base-sw_management patterns-base-transactional_base patterns-base-x11 patterns-base-x11_enhanced - Recommend bash-completion in enhanced_base as it got lost in the base pattern cleanup ==== patterns-server ==== Version update (20200312 -> 20200325) Subpackages: patterns-server-dhcp_dns_server patterns-server-directory_server patterns-server-file_server patterns-server-kvm_server patterns-server-lamp_server patterns-server-mail_server patterns-server-printing patterns-server-xen_server - Use new macro %arm64 instead of bare arch name - Remove redundant arch armv7hl which is already included in %arm ==== python-numpy ==== Version update (1.18.2 -> 1.18.3) - Disable TestF{77,90}ReturnCharacter on big-endian architectures (#11831) - update to version 1.18.3: * #15916: BUG: Fix eigh and cholesky methods of numpy.random.multivariate_normal * #15929: BUG,MAINT: Remove incorrect special case in string to number... * #15930: BUG: Guarantee array is in valid state after memory error occurs... * #15954: BUG: Check that pvals is 1D in _generator.multinomial. * #16017: BUG: Alpha parameter must be 1D in generator.dirichlet ==== qemu ==== Subpackages: qemu-arm qemu-block-curl qemu-block-dmg qemu-block-gluster qemu-block-iscsi qemu-block-nfs qemu-block-rbd qemu-block-ssh qemu-extra qemu-guest-agent qemu-ipxe qemu-ksm qemu-kvm qemu-lang qemu-microvm qemu-ppc qemu-s390 qemu-seabios qemu-sgabios qemu-tools qemu-ui-curses qemu-ui-gtk qemu-ui-sdl qemu-ui-spice-app qemu-vgabios qemu-vhost-user-gpu qemu-x86 - Minor tweaks to patches and support doc - Add gcc10-maybe-uninitialized.patch in order to fix boo#1169728. ==== qemu-linux-user ==== - Minor tweaks to patches and support doc - Add gcc10-maybe-uninitialized.patch in order to fix boo#1169728. ==== timezone ==== Version update (2019c -> 2020a) - timezone update 2020a (bsc#1169582) * Morocco springs forward on 2020-05-31, not 2020-05-24. * Canada's Yukon advanced to -07 year-round on 2020-03-08. * America/Nuuk renamed from America/Godthab. * zic now supports expiration dates for leap second lists. ==== timezone-java ==== Version update (2019c -> 2020a) - timezone update 2020a (bsc#1169582) * Morocco springs forward on 2020-05-31, not 2020-05-24. * Canada's Yukon advanced to -07 year-round on 2020-03-08. * America/Nuuk renamed from America/Godthab. * zic now supports expiration dates for leap second lists. ==== vim ==== Subpackages: gvim vim-data vim-data-common - update spec.skeleton to current header generated by spec-cleaner ==== xf86-video-intel ==== - Add U_i810-multidef-fix.patch in order to fix boo#1169744. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Renumbering patches and the factory bot
by İsmail Dönmez 30 Apr '20

30 Apr '20

On 30 Apr 08:24 2020, Michal Suchánek wrote: > On Thu, 30 Apr 2020 10:02:20 +0200 > Michael Ströder <michael(a)stroeder.com> wrote: > > > On 4/30/20 7:05 AM, Stephan Kulow wrote: > > > Am 29.04.20 um 20:09 schrieb Jan Engelhardt: > > >> Source0: s.tar.xz > > >> Patch*: [0-9]*.patch > > >> # or even "Patch*: *.diff" -- whatever it is you want for your package > > >> > > > The kernel packages use patches.tar.xz and get away with it. Every > > > package with more than a dozen patches is most likely easier to > > > handle with that approach :) > > > > Isn't it much harder to review changes with that approach? > > Not really. > > First, these tarballs are typically generated from git which is easy to > review in git. > > Second, OBS web UI can show diffs of files inside a tarball. It won't show for big tarballs which is the case for kernel, so let's not do this unless you are kernel. Regards, 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)

2 1

Re: [opensuse-factory] A submission needs review.
by Yi Fan Jiang 30 Apr '20

30 Apr '20

Hello guys, Thanks for jumping in to get the submission settled. I will temporarily take care of the package before a proper maintainer found his/her interests in it 🙂 Best wishes, Yifan

1 0

Re: [opensuse-factory] Renumbering patches and the factory bot
by İsmail Dönmez 30 Apr '20

30 Apr '20

On 30 Apr 08:02 2020, Michael Ströder wrote: > On 4/30/20 7:05 AM, Stephan Kulow wrote: > > Am 29.04.20 um 20:09 schrieb Jan Engelhardt: > >> Source0: s.tar.xz > >> Patch*: [0-9]*.patch > >> # or even "Patch*: *.diff" -- whatever it is you want for your package > >> > > The kernel packages use patches.tar.xz and get away with it. Every > > package with more than a dozen patches is most likely easier to > > handle with that approach :) > > Isn't it much harder to review changes with that approach? Yes it is and it's not really preferred. Kernel team is big enough to handle this, having their own QA etc. - 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