Search results for

Re: Proposal: why not turn Leap 15.5 into a trad'l "rolling" distro?

by Carlos E. R.

On 2023-03-26 20:35, Stefan Seyfried via openSUSE Factory wrote: > On 26.03.23 18:19, Fritz Hudnut wrote: > >> Leap could become that platform . . . a "happy medium" between staid >> stability and total rebuilding of the platform every couple of months >> . . . a "freshening" of the kernel and so forth . . . . > > This is what openSUSE was before Leap. > >> Is that >> really "stupid" or . . . simply "inadvisable" in your humble opinion? > > No, you can create that. You "just" need to find enough people willing > to do the necessary work. > > Hint: Leap was created as is for a reason, part of that was that thee is > not enough contributors to sustain the old way of doing things. But if > you can organize enough manpower to pull that off, that will probably > make many people happy. Yes, it would :-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

1 year, 7 months

Re: PAM default configuration bug

by Axel Braun

Am 26. März 2023 21:31:25 MESZ schrieb Jan Engelhardt <jengelh(a)inai.de>: > >On Sunday 2023-03-26 21:12, Joe Salmeri wrote: >> >> Whenever I submit a bug report I always try to include the appropriate people >> for the bug report using in this case >> >> osc maintainer pam >> >> But then when I create the bug report and try to add accounts that are listed >> by that to the CC List, often they don't match anything and therefore are not >> added. > >`osc maintainer` lists usernames. >Bugzilla wants email addresses. > >Use `osc whois osc maintainer -e

1 year, 7 months

Re: Proposal: why not turn Leap 15.5 into a trad'l "rolling" distro?

by Gordon Messmer

On 2023-03-26 11:11, Larry Len Rainey wrote: > On 3/26/23 13:02, Gordon Messmer wrote: >> Very probably, the explanation is going to be a mix of factors, >> including: the major release of Fedora that you're examining was >> recent, and few projects have made breaking changes since its >> release. Without breaking changes, there's no cause to hold back >> updates to those packages. > > If Fedora were stable it would still be on Kernel 5 not Kernel 6. > Yes, as I said: You're looking at Fedora 37, which was released on 2022-11-15, which is later than the Linux kernel version 6, which was released 2022-10-02. It would not be unusual for a stable release to contain Linux kernel version 6 if it were released after that kernel. And, because the kernel's public interface hasn't had any breaking changes since then, it's not necessary to hold it on an earlier release branch within a stable release. I think your definition of "stable" might be... non-standard? Software developers use that term in a way that's not intuitive for many people. https://medium.com/@gordon.messmer/what-does-stable-mean-4447ac53bac8

1 year, 7 months

Re: PAM default configuration bug

by Joe Salmeri

>> `osc maintainer` lists usernames. >> Bugzilla wants email addresses. >> >> Use `osc whois > osc maintainer -e Thanks Jan and Axel that was a big help! I had tried putting @<domainname> on the usernames figuring they were just shortcutting in osc and it sometimes worked but now I see that emails are not always username@domain. They would have been if I set it up 😄

1 year, 7 months

Re: Proposal: why not turn Leap 15.5 into a trad'l "rolling" distro?

by Marco Calistri

Il 26/03/23 09:14, Larry Len Rainey ha scritto: > > Making leap a rolling is stupid as it would become Tumbleweed. > > Most users could care less about being current and needing to update > and rebooting. I have seen some OpenSUSE users do nothing until End of > Life forces them to a new version. > > Rolling requires that you update daily or risk being patched past the > point of the system being stable. > > As support for many users across America, I left Fedora when they > became a rolling and went to Centos, when Walmart went SLES, I went to > OpenSUSE and have not had any reason to switch to another distro. I do > run other distos to test VirtualBox as it is the reason may folks use it. > > I for one say NO to rolling Leap. > > > On 3/26/23 05:04, Emanuel Castelo via openSUSE Factory wrote: >> So the issue is your old machine? >> I would suggest you dont TW, do 15.x without making 15.x rolling or you will be back to TW like issues. >> >> Sent from my iPad >> >>> On Mar 25, 2023, at 20:47, Fritz Hudnut<non.space.1(a)gmail.com> wrote: >>> >>> Folks: >>> >>> Once again, when "we" in TW hit these "balloon upgrades" when >>> thousands of packages are dropped into zypper to maintain the system, >>> and those of us with older hardware (circa '12) run into time >>> consuming issues for our geriatric machines to be able to process them >>> . . . . >>> >>> We get into "discussions" on the forum about what exactly does >>> "rolling" mean vs "new distribution release for total rebuild of the >>> system" . . . and during those interactions it came to me that perhaps >>> Leap 15.5 could be the "mule" for developing the more traditional >>> "rolling" platform, similar to Manjaro, where the basic system is >>> upgraded/maintained . . . generally a couple hundred packages every >>> other week or so . . . ??? Kernel and browser freshness is generally >>> all that an end user such as myself would need, to support his DE of >>> choice. >>> >>> As of late the "protectors of TW" are raging about how "we need to >>> upgrade gcc completely to maintain parity with . . . newness"??? That >>> may indeed be the case, but, In kicking around with TW for roughly 10 >>> years I can't recall a time on the forum when I was having issues, >>> where a guru would say, "You need to upgrade to gcc12, right now!!!!" >>> Or whatever gcc option that would be the next new option. >>> >>> Leap 15.5 could provide the opportunity to continue using that >>> technology, but buttressed with "stability" for the basic system, and >>> just "roll in" kernel updates and so forth, "evolution" rather than >>> "totally revamping every package" as now seems to be the case with TW. >>> >>> Thanks for the bandwidth. IMHO, transforming Leap into a rolling distro should be a wrong approach for OpenSUSE, just because here we already have Tumbleweed, which I use on daily bases with much enjoyment and, on contrary to what you think, I believe it's not stupid at all! But the world is nice also because "your mileage may vary". -- Marco Calistri Build: openSUSE Tumbleweed 20230325 Kernel: 6.2.8-1-default - XFCE: (4.18.1)

1 year, 7 months

Issues with vagrant / libvirt since snapshot from this week Tuesday or Wednesday?

by Johannes Kastl

Hi all, is anyone else experiencing issues with libvirt since mid of this week? I can no longer start VMs using vagrant. Vagrant hangs at "Waiting for domain to get an IP address..." and never gets anywhere. Existing VMs can be started using virsh or libvirt, so it might be an issue with vagrant itself. But it was working until mid of this week, despite being outdated (due to the licensing change). I noticed some errors regarding missing directories on Feb 8th and today: > Feb 08 13:09:28 baten systemd[1]: Starting libvirt legacy monolithic daemon... > Feb 08 13:09:28 baten libvirtd[7841]: libvirt version: 10.0.0 > Feb 08 13:09:28 baten libvirtd[7841]: hostname: baten > Feb 08 13:09:28 baten libvirtd[7841]: Failed to initialize libnetcontrol. Management of interface devices is disabled > Feb 08 13:09:28 baten systemd[1]: Started libvirt legacy monolithic daemon. > Feb 08 13:09:29 baten libvirtd[7841]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/callouts" doesn't exist. This may indicate a packaging or installation error > Feb 08 13:11:28 baten systemd[1]: libvirtd.service: Deactivated successfully. or > > Feb 10 18:31:36 baten systemd[1]: Started libvirt legacy monolithic daemon. > Feb 10 18:31:37 baten libvirtd[4420]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/notifiers" doesn't exist. This may indicate a packaging or installation error And sure enough there are no directories in /usr/lib/mdevctl/scripts.d/ on all of my machines... Kind Regards, Johannes

8 months, 4 weeks

Re: Issues with vagrant / libvirt since snapshot from this week Tuesday or Wednesday?

by Larry Finger

On 2/10/24 11:53, Johannes Kastl wrote: > Hi all, > > is anyone else experiencing issues with libvirt since mid of this week? > > I can no longer start VMs using vagrant. Vagrant hangs at "Waiting for > domain to get an IP address..." and never gets anywhere. > > Existing VMs can be started using virsh or libvirt, so it might be an > issue with vagrant itself. But it was working until mid of this week, > despite being outdated (due to the licensing change). > > I noticed some errors regarding missing directories on Feb 8th and today: > >> Feb 08 13:09:28 baten systemd[1]: Starting libvirt legacy monolithic daemon... >> Feb 08 13:09:28 baten libvirtd[7841]: libvirt version: 10.0.0 >> Feb 08 13:09:28 baten libvirtd[7841]: hostname: baten >> Feb 08 13:09:28 baten libvirtd[7841]: Failed to initialize libnetcontrol. Management of interface devices is disabled >> Feb 08 13:09:28 baten systemd[1]: Started libvirt legacy monolithic daemon. >> Feb 08 13:09:29 baten libvirtd[7841]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/callouts" doesn't exist. This may indicate a packaging or installation error >> Feb 08 13:11:28 baten systemd[1]: libvirtd.service: Deactivated successfully. > > or >> >> Feb 10 18:31:36 baten systemd[1]: Started libvirt legacy monolithic daemon. >> Feb 10 18:31:37 baten libvirtd[4420]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/notifiers" doesn't exist. This may indicate a packaging or installation error > > And sure enough there are no directories in > /usr/lib/mdevctl/scripts.d/ on all of my machines... You are probably getting hit by the update of glibc from 2.38 to 2.39. It shows in VirtualBox as no USB passthrough. I added the Slowroll repo and downdgraded glibc along with the 15 dependent packages and the USB access is restored. See boo#1219766 for repo details. Larry

8 months, 4 weeks

Re: Slowroll RFE support and multimedia codecs

by Shawn W Dunn

On 2/9/24 05:41, Terje J. Hanssen 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 > For new Bugzilla targets, you should be sending a message to bugzilla-admins(a)suse.com And asking for Slowroll to be setup as a Product, under the openSUSE Umbrella. > 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. > As far as things not needing to rely on devel: repositories like multimedia:/libs, that is for the Developers of Slowroll to decide how they want to handle it, and not something that is decided by somebody else. Packman issues don't belong here, as Packman is not part of the openSUSE project, in any way, shape, or form. It's a third-party service, provided by an unaffiliated group, if you wish to see some sort of Slowroll buildtarget on packman, you would need to contact the Packman administrators at https://lists.link2linux.de/cgi-bin/mailman/listinfo/packman > And corresponding installation support for Slowroll using OPI, Zypper, YaST > https://en.opensuse.org/Additional_package_repositories en.opensuse.org is a wiki, and can be edited by anybody, feel free. > https://opensuse-guide.org/codecs.php > https://ostechnix.com/how-to-install-multimedia-codecs-in-opensuse/ > Neither of these sites are part of the openSUSE project, if you have issues with the content they are providing, you should be contacting the administrators of those sites, through whatever mechanism they provide. > > Rgds > Terje J. Hanssen I mean, I'm just going to state this. The -Factory Mailing list isn't the place to make these sorts of requests. I know it's a common misconception, but there is no "In Charge Of" in openSUSE, like there is with Fedora, with FESCo and the SIG's (Just as an example) The developers working on Slowroll are the ones that make the decisions on how they wish to handle it, And I haven't the foggiest if they regularly follow the -Factory ML, or where they may discuss their development roadmaps or models. Packman

8 months, 4 weeks

Re: Slowroll RFE support and multimedia codecs

by Shawn W Dunn

I do just want to make it clear, that I'm not affiliated with the Packman Project, in any way, shape or form. The lone "Packman" there at the end of my response is something I missed while editing, and not any claim to speak on behalf of the Packman Project.

8 months, 4 weeks

BOINC and NVIDIA

by Ed Goforth

Since the latest Tumbleweed update, BOINC is no longer recognizing my NVIDIA card. farmville:~ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240209" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240209" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240209:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240209" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" I have not yet tried doing a rollback because there were several thousand package updates as part of that last zypper dup. The card is definitely seen and utilized by the system, and nvidia-smi, nvidia-settings and clinfo can see it. Even boinc --detect_cpus sees it, though there is a<warning>[coproc] cuMemGetInfo(0) returned 201</warning> Any suggestions?Thanks,Ed

8 months, 4 weeks

openSUSE Factory search results for query "a"