July 2022 - openSUSE Project - openSUSE Mailing Lists

Re: ALP Git-Packaging-Workflow group created
by Adrian Schröter 21 Jul '22

21 Jul '22

On Donnerstag, 21. Juli 2022, 09:34:17 CEST Jan Engelhardt wrote: > > On Wednesday 2022-07-20 16:37, Dirk Müller wrote: > > > >> I would make the case that OBS history is not particularly interesting > >> for its _messages_ [..] > > > >[.. ]There are some suggestions around using git notes for the end-user > >changelog, but that hasn't been evaluated in detail yet. Any > >suggestions or input welcome. > > Adam Majer held a conversation with a few individuals ahead of the > openSUSE conf 2022 for thoughts, I'd like to repaste some of that > since it was originally off-list and still hope to see this coming to > build.opensuse.org soon. > > --- > > Date: Tue, 31 May 2022 15:33:31 +0200 > From: Jan Engelhardt > To: adamm > Cc: stroeder > > On Tuesday 2022-05-31 12:50, Adam Majer wrote: > > > https://build.opensuse.org/project/show/devel:ALP > > https://code.opensuse.org/adrianSuSE/Alp > > https://code.opensuse.org/adrianSUSE/zypper > > https://code.opensuse.org/package/zypper > > > > Internally, most of the feedback from maintainers I've talked to is > > along the lines of "ok, so I'll have to adapt to this I guess", ie. > > not enthusiastic :-) > > > > I would like to get your thoughts about this and any suggestions of > > what you would expect this "new" approach to have. > > * Because the git checkout does not have the .osc directory, the osc > build line is a bit longer than usual. > > osc build --alternative-project openSUSE:Factory standard x86_64 pdns.spec the current osc can checkout a scmsync package. You get a local git clone, but osc remains working with local builds inside. The downside atm is that it still creates a .osc which need to be ignored by git. I hope we will find a better solution for that in future. Try osc co home:adrianSuSE:OBSGIT git-example-1 for an example package which defines a git url. At least osc-0.179 is required for this though. > * Checking out /package/zypper: the tarball is a (dangling) symlink to > /ipfs. > > ALP is "just" a spin/a distribution -- let's deploy this git scheme for > an "actual" development prj and see how that works out. I could think > of a few to spare for the experiment that have low volume > (security:netfilter, maybe network:telephony). > > > > Also, any sticking points when it comes to current (current OBS) > > workflow that git could improve? > > * Some command-line equivalent for `osc sr` will be needed if git is used as a > backend. `git push` to /jengelh/zypper is (would be) easy, but making > the actual SR/MR/PR.. if I don't know better, would require opening a > browser, and one shouldn't have to go to a browser. A sr would not transfer the git information atm (and on purpose). That means you can work with such a git setup in your devel or home project and submit request the result to factory for example. However, the long term plan here is that the sr gets actually replaced by a pull request in the git hosting instance. -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

1 0

Re: ALP Git-Packaging-Workflow group created
by Dirk Müller 20 Jul '22

20 Jul '22

Hi Jan, > I wonder how the ipfs symlinks stored in pagure would be handled. > Fuse mount, or another global hook like git-lfs? For now we're not looking at the pagure setup at all. I personally have no experience with ipfs and it wouldn't work for the certified part of the SUSE product building, so it is a dead end. We're taking Git with LFS as plan A, unless there are compelling reasons against it, we will not look back. > I would make the case that OBS history is not particularly interesting > for its messages, because (a) we have had .changes files, > (b) the SVN-ish nature of the OBS SCM meant that you can't go back > and edit messages or commits, so there is little incentive to write > up much if you missed it in the first commit. Right, the *.changes files are still part of the commit content, so you get these as part of the commits (and follown commits). There are some suggestions around using git notes for the end-user changelog, but that hasn't been evaluated in detail yet. Any suggestions or input welcome. Greetings, Dirk

1 0

ALP Git-Packaging-Workflow group created
by Dirk Müller 20 Jul '22

20 Jul '22

Git Packaging Workflow Exploration A few colleagues from SUSE, namely the build service team and others like myself are exploring the options on what the best way would be to use Git, rather than the current open Build Service source handling, for storing openSUSE / SLE package sources. This was originally launched under the ALP Workgroup umbrella but for now is timeline wise decoupled from this effort, except that if we would decide to switch, that it would have to happen before the first commercially supported Alp release would be branched off openSUSE Factory. For now, all of this is in the exploration and experimentation phase and no decision in either way has been taken. Meanwhile, we do however feel confident and organized enough to be open to wider feedback. If you're interested in any of the topics please let the work package driver know, or if in any doubt contact me. Here's the current list of work packages and their state: * Exploration of the Git Hosting options (run by me) openSUSE already has some experience with Pagure.io (used by https://code.opensuse.org/ for example) and GitHub (used by various openSUSE projects under https://github.com/openSUSE) as well as some projects also in GitLab (used by a few community efforts as well as SUSE-internally for hosting) so we explored another option named Gitea, which is now available to the community under https://gitea.opensuse.org/. Please note that this is not a production service, and can lose data or disappear at any point in time, it is only being operated in the context of the Git packaging workflow exploration. * Exploration of the history import from the SUSE and openSUSE build service source history (run by Stephan Kulow). Stephan Kulow has managed to import the majority of existing history of packages that landed in released products or in openSUSE Tumbleweed as history into package-git repositories and published under https://gitea.opensuse.org/rpm . As an example the history of zlib is here: https://gitea.opensuse.org/rpm/zlib/commits/branch/factory which is significantly more detailed than a similar effort implemented by Bernhard Wiedemann a couple of years ago on our code.opensuse.org instance: https://code.opensuse.org/package/zlib/commits/master Your feedback on the history import quality and how it could be made better is very much appreciated. The key difference compared to the pagure setup is that we use Git LFS for storing large files (like tarballs for example) and currently these large files are mapped via a small redirector proxy directly to the openSUSE build service source service. With that the git repository history is extremely small and very manageable for local cloning. * Exploration of the git packaging workflow going forward. Alberto Planas, with contributions by others, has written up ideas and options in the following document: https://github.com/aplanas/openSUSE-git/blob/main/notes-about-git.md Please provide feedback either as a pull request or as a discussion entry in the forum here: https://github.com/aplanas/openSUSE-git/discussions * Exploration of build and status integration. This one is less well-defined, but for now it is about automatically syncing new changes in the git repository with the state of the Build Service instance that is used for building as well as exploring the options for reporting back the build status into the Git Hosting infrastructure. This is currently worked on by Adrian Schroeter. We store the meeting time and minutes under https://en.opensuse.org/openSUSE:ALP/Workgroups/Git-Packaging-Workflow In case there are any questions, feel free to reach out to related work package owners or myself. Greetings, Dirk

1 0

Raw results from openSUSE Leap 15.4 retrospective are available!
by Lubos Kocman 19 Jul '22

19 Jul '22

Hello openSUSE! Big thanks to everyone who participated in the openSUSE Leap 15.4 release survey. And yet again apologize for the initial miscommunication. We received incredible 760 responses in total, which is a nice increase compared to the previous years (605, 409). Raw data is already available at https://en.opensuse.org/Portal:15.4/Retrospective As for the past two releases, I want to yet again process the release retrospective results in a few public rounds, categorize responses, and share feedback with respective teams once done. We had at least three rounds of review last time. Numbers tell me we'll need more this time, or we need to find a more effective way of categorizing. We'll announce more rounds if necessary. https://meet.opensuse.org/meeting Monday 18th July 9:00 am - 10:00am CEST Tuesday 19th July 3:30 pm - 4:40 pm CEST (Before regular meeting) Thursday 21th July 8:00 pm - 9:00 pm CEST (Before regular meeting) Best regards Lubos Kocman openSUSE Leap Release Manager

1 1

minutes Board Meeting Monday 2022-07-18 13:00 CEST
by Syds Bearda 18 Jul '22

18 Jul '22

= Board Meeting Monday 2022-07-18 13:00 CEST = * Present: Axel, Gerald, Gertjan, Maurizio, Neal, Syds, Gertjan * Guests: Doug * Not present: Attila == TSP Program Update == * Doug: still work in progress with SUSE Finance, manager. Reached out to new contact within Finance * TSP is still a work in progress from SUSE Finance. Some TSP's have not been paid yet, but those are being worked through by SUSE Finance. Payment will come soon (hopefully). * TSP in general it's a point of frustration, cause of no movements from SUSE. New people are looking at and needs to be explained, currently decisions are going to be made higherup at SUSE. * If Doug needs our help, he'll let us know. == Moderator accountability across all platforms == * https://code.opensuse.org/board/tickets/issue/9 * Meeting in the next two weeks * AI Maurizio to call for that meeting == Creating a consistent way to document differences in policy between devel projects == * https://code.opensuse.org/board/tickets/issue/20 * Closed for lack of activity for a year == Bar t-shirts == * https://code.opensuse.org/board/tickets/issue/31 * Board will support once becomes active again; closing for now. == openSUSE online communities == * https://code.opensuse.org/board/tickets/issue/38 * Code of Conduct has been rolled out (and was triggered by this ticket). == Make Membership / Election official aware of all members of the Emeritus Members group. * https://code.opensuse.org/board/tickets/issue/49 * https://code.opensuse.org/board/tickets/issue/5 * AI: get list from Simon (Gerald reached out to Simon) == Follow-up from oSC: "A Fork in the Road" == * Syds reached out to Patrick, still needs to talk to him regarding research on legal entities. Continued at private part at CEST 13.35 Meeting closed at CEST 14.00

1 0

Minutes of openSUSE Board meeting 2022-07-04
by Maurizio Galli 18 Jul '22

18 Jul '22

= Board Meeting Monday 2022-07-04 13:00 CEST = * Present: Attila, Axel, Gerald, Maurizio, Syds, Gertjan ( late ) * Guests: Doug, Emily * Excused: Neal == Follow-up from oSC: "A Fork in the Road" == * openSUSE Futures session initiated by the board at openSUSE Conference * Recording of opening session at https://youtu.be/ixx8uQQwr90 * Recording of closing session not yet available. * Patrick Fitzgerald kindly agreed to do some research about legal entities * AI Syds: contact Patrick Fitzgerald * AI all: gather snippets we want to put together, then work on mail to project@ in next meeting == Mod team == * Mod team needs to meet and decide if the document summarizing the mission statement and practices is ready to be shared with the community. == openSUSE.Asia Summit == * Maurizio and Attila should represent the board with a keynote Meeting closed

1 0

Community Meeting/ALP WG: Week 29
by ddemaio 18 Jul '22

18 Jul '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. The Community Meeting will be on Thursday at 19:00 UTC. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. BOARD MEETING The biweekly board conference call with the board is scheduled for today at 13:00 Europe/Berlin time. The meeting will be in the regular Board Meeting Room at https://meet.opensuse.org/OSBoard ASIA SUMMIT CFP The Call for Papers for the openSUSE.Asia Summit is now open until July 31. That leaves 27 days to submit your proposal for the online event. Submit your proposal at https://events.opensuse.org. Please find the news at https://news.opensuse.org/2022/07/01/osa-cfp/ LOGO Yes, We need a logo from this year's openSUSE.Asia Summit. Find out how to submit your logo idea at https://news.opensuse.org/2022/07/01/osa-cfl/ v/r Doug

1 0

Re: Raw results from openSUSE Leap 15.4 retrospective are available!
by Marcus Meissner 15 Jul '22

15 Jul '22

Hi, On Thu, Jul 14, 2022 at 09:02:19PM +0300, Andrei Borzenkov wrote: > On 14.07.2022 20:55, G McAlister wrote: > > On 14/07/2022 17:53, Andrei Borzenkov wrote: > >> On 13.07.2022 15:14, Jan Engelhardt wrote: > >> ... > >>> * https://download.opensuse.org/update/leap/15.3/sle/repodata/4c483b355b0c317… > >>> is 101 MB. > >>> > >>> The big elephant in the room: xz compress it. It's 28 MB. > >>> (Similar gains for the other xml.gz files I guess) > >>> > >>> * I know zypper does a file conflict check, but it does that > >>> right before rpm transaction start when it already has all the rpm files (and > >>> thus contents). Why do we need filelists.xml at all? > >> I wonder when it is downloaded at all? This file is not in > >> /var/cache/zypp/raw, this file is not present in zypper.log. Four files > >> downloaded by zypper are deltainfo, updateinfo, susedata, primary. > >> Actually looking at libzypp, it explicitly skips filelists. > >> > >> File lists used by command-not-found come from primary.xml. > >> > > The Remote Mirroring Tool (RMT) downloads filelists.xml. > > > > RMT by definition mirrors repository, so it downloads everything in this > repository. In any case, it has no impact on end-system update time - > repository download happens before repository mirror is used for update. I have opened a ticket, and Adrian also found there is some weird setting missing that reduces download speed (some meta checksumming issue). Ciao, Marcus

1 0

Re: Raw results from openSUSE Leap 15.4 retrospective are available!
by Marcus Meissner 13 Jul '22

13 Jul '22

On Wed, Jul 13, 2022 at 01:46:54PM +0200, Jan Engelhardt wrote: > > On Wednesday 2022-07-13 12:52, Lubos Kocman wrote: > >Raw data is already available at > >https://en.opensuse.org/Portal:15.4/Retrospective > > The summary of the "bad" column: > > >* certbot is gone at least this is meanwhile resolved. > >* packages too old > >* slow repositories (actually, from own experience, > > it's due to the *size* of the rpmmd files being outragerous) This is something we need to think about, split update repos perhaps into multi arch again. > >* patent related user "issues" with ffmpeg > >* non-patent related user issues with ffmpeg > >* some issue that should have been a bugzilla report instead of a > > retrospective response Ciao, Marcus

1 0

Community Meeting/ALP WG: Week 28
by ddemaio 08 Jul '22

08 Jul '22

Hi all, Since I won't be at the WG on Tuesday, I'm sending this out now. We had a community meeting last night and created a merchdesigns folder in https://github.com/openSUSE/artwork. This folder is for spreadshirt designs for merchandise. If anyone is interested in creating a design for an openSUSE t-shirt, please feel free to put it in there. You can find the meeting notes from last nights community meeting at https://etherpad.opensuse.org/p/weeklymeeting20220707 The ALP Work Group (WG) will take place on July 12 at 14:30 UTC. The Community Meeting will be on July 14 at 19:00 UTC. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. The Call for Papers for the openSUSE.Asia Summit is open until July 31. Please submit your proposal at https://events.opensuse.org. There is also a need for a logo. Find out how to submit your logo idea at https://news.opensuse.org/2022/07/01/osa-cfl/ v/r Doug

1 0