Search results for

Re: Is slowroll broken

by Bernhard M. Wiedemann

On 06/05/2024 18.16, Larry Len Rainey wrote: > I have gotten this for the last 2 hours: > > Retrieving repository 'update' metadata > .................................[error] > Repository 'update' is invalid. > [update|http://cdn.opensuse.org/update/slowroll/repo/oss/] Valid > metadata not found at specified URL > History: > - File > './repodata/092c3f567b7f8167f967c92f73b950d2711d141e2411cdf3dfea7ebc4c0a0ef4fe94f7a7364f90bfb6aa1a2546bab4af6e7ea3f528f3d8886309c9f2e3aaa6be-filelists-ext.xml.zst' not found on medium 'http://cdn.opensuse.org/update/slowroll/repo/oss/' Yes, the version bump was in progress and the update repo kept getting published very often through some issue in OBS. It should be better now. Ciao Bernhard M.

6 months

Re: vote on slowroll name

by Roger Oberholtzer

I use Tumbleweed as my Desktop, as well as on a server or two. I agree that it is rock solid. The only loose canon is NVIDIA. On the other hand, we have measurement systems that are not office bound (road condition measurements, mobile mapping, etc). They need to be stable as we can make them. And, it is not convenient to update them regularly as they are in the hands of customers. So we usually choose a Leap release and then use that as our official release for a couple years. We make an installer using KIWI so that every system is 100% identical (baring any hardware differences that we cannot control). Every couple of years we move to a new Leap. It is a workable solution; however, it gets more difficult after our Leap is EOL and we need a new package that was not in our original KIWI install. As long as the package exists, we have a method to get them into our systems in a controlled fashion. But after EOL it gets to be a crap shoot. And an indicator that it's time to make a new KIWI installer and re-install the systems. Rinse and repeat, as it were. We had toyed with using Tumbleweed in this context. Unfortunately, the rolling release that I like so much on my desktop is a problem in this other use context. Getting all measurement systems to have the same Tumbleweed snapshot at the same time is like herding cats. As we deliver a binary installer, matching library versions across independent Tumbleweed versions is near impossible. Also, our current approach does not require an Internet connection at any point in the system build/maintain process. Does slowroll address our situation? I'm not sure. If something like a Tumbleweed's zypper dup could be done with slowroll but at a far less often frequency, and if a slowroll release could be around for a bit of time thus allowing different systems to get to the same slowroll release but done perhaps weeks apart, then perhaps it might. If anything, this discussion has us looking at the possibility of making our software into a flatpack. It has dozens of commands so the task is perhaps involved. But decoupling our code from the underlying OS might be a good thing. We already do something similar to be able to build Leap 15.3 (our current Leap) programs in our constantly changing Tumbleweed build environment. More of a chroot setup. But still a separation of our needs from those of the OS. On Mon, Sep 25, 2023 at 9:32 AM Chris McGimpsey-Jones | MP Portfolio Management <chrisjones.unixmen(a)gmail.com> wrote: > I agree with Dave. > I use Tumbleweed for my daily and it's rock solid. > I don't know where any perception that it's unstable comes from, > because it's not the experience I have. > I also disliked almost all of the proposed names, but more importantly > for me is that I don't see any reason or need for slowroll. > Perhaps I'm missing something here but what/who is the target user > base for slowroll? > > > > On Mon, Sep 25, 2023 at 1:17 PM Dave Gom <nemesis68(a)gmx.com> wrote: > > > > For me Tumbleweed is robust and stable like a rock and I don't see the > need of a slower version but I understand some users were leaved > "systemless" some times and it was an uncomfortable situation. > > Any way I don't like any of the proposed names so I want to suggest a > couple of them. "Tumbleweed step" because a step behind from tumbleweed, or > Tumbleweed trust or trusty, for obvious reasons. > > Regards. > > > > Sent: Monday, September 25, 2023 at 2:56 AM > > From: "Dave Gom" <nemesis68(a)gmx.com> > > To: factory(a)lists.opensuse.org > > Subject: VOTE ON SLOWROLL NAME > > > > > -- Roger Oberholtzer

1 year, 1 month

Re: vote on Slowroll name

by Carsten Ziepke

On Wed, 20 Sep 2023 19:09:15 +0200 "Bernhard M. Wiedemann" <bwiedemann(a)suse.de> wrote: > Hi, > > I setup a survey to decide if we want to rename Slowroll and to what > https://survey.opensuse.org/index.php?r=survey/index&sid=839619 > > Something like "openSUSE Tumbleweed-Slowroll edition" is nicely > descriptive but a bit unwieldy. > > My plan is to keep this open for some weeks - e.g. until 2023-10-08 > > Ciao > Bernhard M. Impressive list! Voted. -- ...and scantily clad females, of course. Who cares if it's below zero outside. -- Linus Torvalds

1 year, 1 month

Re: vote on Slowroll name

by Michael Hamilton

On Thursday 21 September 2023, Bernhard M. Wiedemann wrote: > Hi, > > I setup a survey to decide if we want to rename Slowroll and to what > https://survey.opensuse.org/index.php?r=survey/index&sid=839619 > > Something like "openSUSE Tumbleweed-Slowroll edition" is nicely > descriptive but a bit unwieldy. > > My plan is to keep this open for some weeks - e.g. until 2023-10-08 > > Ciao > Bernhard M. > The Telegraph plant is another plant that moves: https://en.wikipedia.org/wiki/Codariocalyx_motorius OpenSUSE Telegraph and OpenSUSE Tumbleweed As for the names on the existing list, OpenSUSE Driftwood seems quit apt. That's my 2c.

1 year, 1 month

Re: Slowroll and amdgpu-pro and alternatives

by Patrik Jakobsson

On Tue, 2023-11-28 at 13:14 +0100, Peter McD wrote: > Hi, > > I use Leap 15.5 a my main system because of openCL for Darktable which > simply works faster with the proprietary amdgpu-pro driver. Hi Peter, Which other drivers have you tested with? There's a chance that the amd-opencl package from AOMP [1] might be an alternative. > > Slowroll is rooted in Tumbleweed and that in turn is presently not > famous for support of amdgpu-pro. amd-opencl from AOMP should work fine with Tumbleweed. -Patrik > > Are there any plans to chance that for Slowroll? > > Peter [1] https://build.opensuse.org/package/show/science:GPU:ROCm/aomp

11 months, 1 week

Re: Slowroll updates

by Bernhard M. Wiedemann

On 11/05/2024 17.56, cagsm wrote: > is slowroll supposed to have these many repo problems every day or the > other? right now atm e.g. > > sudo zypper ref > Repository 'base-non-oss' is up to date. > Repository 'base-oss' is up to date. > Repository 'h264' is up to date. > Repository 'packman' is up to date. > Retrieving repository 'update' metadata It could be solved with sed -i 's/cdn\./download./' /etc/zypp/repos.d/*repo or zypper in openSUSE-repos-Slowroll It seems, the CDN is not that good at handling large files. Ciao Bernhard M.

5 months, 3 weeks

Re: Slowroll RFE support and multimedia codecs

by Neal Gompa

On Fri, Feb 9, 2024 at 8:42 AM Terje J. Hanssen <terjejhanssen(a)gmail.com> wrote: > > Hello list, > > I don't know if this is the correct location for this topic. > > Even that Slowroll may be in a test phase, it would be wishable to have > somewhere to communicate and route specific requests for support and > enhancements. For example Product name 'Slowroll' in bugzilla, possibly > mailing list and forum. > > So far I have used product name Tumbleweed in bugzilla regarding > ffmpeg-6-6.1.1 > https://bugzilla.suse.com/show_bug.cgi?id=1219259 > > To do real test of Slowroll on desktops as I want, we need to use it as > a full time replacement for Leap 15.5 or Tumbleweed. > That is, we need optional access to all additional package repositories > for multimedia:/libs, codecs enabled tools and applications from OBS and > All from Packman. > > And corresponding installation support for Slowroll using OPI, Zypper, YaST > https://en.opensuse.org/Additional_package_repositories > https://opensuse-guide.org/codecs.php > https://ostechnix.com/how-to-install-multimedia-codecs-in-opensuse/ > I'm going to say the quiet part out loud: why do you need anything from Packman? What is *left* from a multimedia perspective? Outside of an alternate build of ffmpeg enabling more exotic things and a couple of particularly "special" libraries, we shouldn't need Packman for anything and we should not be encouraging people to install Packman for daily use. Web content should just work these days, as Lubos, Jan, Bjorn, and I have been particularly aggressive about ensuring all the basic cases are covered by default. We also should be striving for things to be integrated in the main repositories rather than telling people to activate random extra OBS projects, because random repos on people's systems are just asking for trouble in a whole new way. -- 真実はいつも一つ！/ Always, there's only one truth!

8 months, 4 weeks

ALP-Leap-replacement Architecture Meeting Minutes - 25 July 2023

by Richard Brown

ALP-Leap-replacement Architecture Meeting - https://en.opensuse.org/openSUSE:ALP/ArchitectureTeam Meetings take place on https://meet.opensuse.org/meeting and notes are available at https://etherpad.opensuse.org/p/weeklymeeting Participants: Richard, Lubos, Valentin, Marcus, Bernhard, Phoeinx, Knurpht, Rob, Emiliano, Ish, Dirk 1. Update from Richard: Communications - There has been NO communication on https://matrix.to/#/#alp:opensuse.org since July 1 Q from Richard - have discussions been happening elsewhere? A- There hasn't been much, but there has been some conversations. Richard needs to fix his Matrix client ;) but more people should join and discuss also. Ongoing efforts - there are currently 2 concepts for an ALP-Based-Leap Replacement https://en.opensuse.org/openSUSE:ALP/ArchitectureTeam#Experimental/Research… Linarite update - No progress yet Slowroll update- "I did a snapshot of a random Tumbleweed version (20230705) and setup OBS projects to build a package update ontop of it. That worked with some help from Adrian. During that we discovered that we will probably need an own project like openSUSE:Slowroll to have our own prjconf that can move independently of Factory/Tumbleweed. https://build.opensuse.org/projects/openSUSE:ALP:Experimental:Slowroll/meta I also started https://github.com/bmwiedemann/slowroll-tools that already provides data for a core-ness value for a given package. More tools should be added there later, e.g. to do heuristics on .changes files and code diffs to provide input to the required risk+benefit-assessment. One open question is if we want multiple overlapping slowroll versions. If most work is automated, that should not be much extra effort. Then we could have a slowroll-2023-07 followed by a slowroll-2024-01 with overlapping support periods so that sysadmins can dup on their own schedule. It could be like openSUSE before Leap (but with more automation to keep the work easy). I would like that." 2. Discussing concepts for additional Experiments/Research Projects No additional concepts raised 3. Any other buisness - Group mail from Max, is this another concept? Richard - doesn't seem to be, but does provide many good questions the group needs to consider. - Was recurring suggestions via YouTube and Reddit that openSUSE may not need a Leap replacement. What do we think as a group? A- To be kept in mind and maybe used as a question in poll (see below) Lubos - would like to see a solution for community to be able to touch the maintenance workflow Marcus - the group needs to define what the Leap replacement looks like before worrying about how to maintain it Richard - exactly - well if we did Slowroll, then we wouldn't have a maintenance workflow like the current Leap at all Phoenix - What does lifecylce mean in the context of Slowroll? Richard - Something along the lines of how often/how quickly after a package is in Tumbleweed does it appear in Slowroll Phoenix - But the metric of how often is a package updated is mostly irrelevant for a point release. Users expect a system to be installed and then mostly stay stable. The important question is "are packages maintained" and that does not necessarily align with packages being kept at bleeding edge Dirk - Also Packages in SLES are maintained which means, they will be updated when there is a reason for them to be updated. Lubos - Max tries to update all community packages in Leap 15.X few times during the development cycle. We have it as part of our release process. It's true that some of the SLES packages were not updated since SLES 15(.0):GA, these receive on demand updates typically requested via Jira or https://code.opensuse.org/leap/features Dirk - suggestion to create a poll to gain feedback on which concepts folk might like https://en.opensuse.org/Portal:15.5/Retrospective has plenty feedback on Leap 15.5 pros+cons Ish - the poll should be really specific, and it should be done for Members only, using the election platform. Ish volunteers to run it. AI - Richard, Lubos, Dirk to work on wording for Ish. Poll is likely to focus on the concepts we have on the table, namely Slowroll, Linarite, and not-replacing-Leap. Phoenix - Shares some thoughts - Leap users like Leap because they like a point release. If we give them a rolling release they'll probably just go to a different distro. Contributing to Leap is very difficult and gets in the way of a point release. The main thing contributions want to do is just add new packages, so, why not have a concept which is an expanded packagehub, which a much simpler contribution process. Richard - cool idea..it's not really different from openSUSE:Backports and would likely face the same challenges gathering contributions Lubos - you'll hit the problems we already hit..new package requires an update to FOO which blocks the change until the dependency can be updated in the next point release Richard - Exactly, this is why Tumbleweed has the concept of "To be able to change any one thing, we need to be able to change everything". Any point release model will effectively block such contributions for months or years at a time. Next meeting - after pool closing, TBA -- Richard Brown Distributions Architect SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman

1 year, 3 months

Re: QSVEnc package missing on Slowroll

by Terje J. Hanssen

Den 29.10.2024 12:52, skrev Axel Braun: > Am Dienstag, 29. Oktober 2024, 11:42:05 Mitteleuropäische Normalzeit schrieb Terje J. Hanssen: >> Den 29.10.2024 05:05, skrev Bernhard M. Wiedemann: >>> >>> On 27/10/2024 14.55, Terje J. Hanssen wrote: >>>> Hi List >>>> >>>> QSVEnc is meant to investigate performance and image quality of HW >>>> encoder (QSV) of Intel. There are build packages for Fedora and >>>> Ubuntu, but it is missing for openSUSE Slowroll. >>> Slowroll only gets packages from Tumbleweed, so someone would need to >>> send it there. >>> >>> Ciao >>> Bernhard M. >> Yes, it is seemingly is missing on all openSUSE, Tumbleweed/Slowroll and >> Leap. >> Does it fit in somewhere? > sure. Build it locally in your home project and submit it to a development project, from where it can go to TW and Leap. Check for similar packages to find a suitable project. > hardware for example? > > Cheers > Axel Sorry, I am not a capable package builder myself. I meant if it may fit in by someone capable to do build it ? Rgs Terje J. H

1 week, 3 days

Re: Mesa 23.1.7 32-bit libraries missing in updates repo on Slowroll

by Bernhard M. Wiedemann

On 13/09/2023 17.33, Kostadin Shishmanov via openSUSE Factory wrote: > When I try to install steam on slowroll, for some reason Mesa-32bit-23.1.7 is missing from the "updates" repo and instead zypper asks me to downgrade Mesa to 23.1.5 in order to go through, which makes KDE use llvmpipe. Can someone figure out why the 32bit libraries of mesa 23.1.7 are missing from updates? Yes, it is a known issue on the todo list. Currently we cannot build i586 packages in Slowroll, because we don't have the required 32-bit build tools available there. They are not published in Tumbleweed anymore and we just import that published snapshot. Ciao Bernhard M.

1 year, 1 month

openSUSE Factory search results for query "Slowroll"