Search results for

Re: Testers Wanted: longterm kernel

by Nikolai Nikolaevskii

Kernel:/slowroll:/Backport is for Leap 15.5? https://download.opensuse.org/repositories/Kernel:/slowroll:/Backport/stand… It is better to call LTS kernel as LTS, not as Slowroll: https://download.opensuse.org/repositories/Kernel:/slowroll/ as https://download.opensuse.org/repositories/Kernel:/LTS/ And https://download.opensuse.org/repositories/Kernel:/slowroll:/ as https://download.opensuse.org/repositories/Kernel:/LTS:/

8 months, 4 weeks

Re: RPM 4.19 - first list of missing user provides

by Jan Engelhardt

On Monday 2024-02-05 14:52, Martin Wilck via openSUSE Factory wrote: >> https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups > >While we're at it, would it make sense to create something like an >UID/GID registry and assign fixed UID/GID numbers to some system users >and groups? That was done 25 years ago and it did not prevail even then. https://github.com/openSUSE/aaa_base/ e.g. commit 5d7a12d8ce9e48606a027bd2fbbe5c932246b184

8 months, 4 weeks

Re: [factory] [15.6] dracut requires wicked?!?!

by Felix Miata

Martin Wilck composed on 2024-02-05 14:41 (UTC+0100): > On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo Factory wrote: >> The following requirement was already added for 15.5: >> ``` >> Requires: (iputils or arping2 or wicked) >> ``` >> But yes, maybe it does no make much sense for desktop-only use cases. > this would only trigger if someone had neither iputils nor arping2 nor > wicked installed. It is important because network device bringup in the > initrd may fail without it. We can't simply remove it. > I guess we can add NetworkManager in the list (I am not sure what NM > uses to check for duplicate address detection; but if NM is in use, I > don't think we'll use the network-legacy dracut module, right?) I can't see how that would help here. I thought I made it evident in OP that neither NM nor Wicked are installed, thus can't be responsible for network setup here. systemd-networkd.socket is all I have explicitly enabled to bring up networking. > We can consider modularizing the dracut package more, so that only the > ifup-legacy subpackage depends on wicked. But that's about all we can > do here. Antonio Feijoo composed on 2024-02-05 17:32 (UTC+0100): > Yes, shipping a network subpackage seems the cleanest way, BTW adopted by > Fedora/RH [1] since forever [2]. > [1] https://src.fedoraproject.org/rpms/dracut/blob/rawhide/f/dracut.spec#_151 > [2] https://github.com/dracutdevs/dracut/commit/ec74fa8789453a7949869947ba07e66… I use only systemd-network on Fedora as well, on every systemd distro actually. Leap is my primary and very most used. Home. :) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

8 months, 4 weeks

Re: RPM 4.19 - first list of missing user provides

by Ben Greiner

Am 05.02.24 um 09:52 schrieb Andreas Schwab: > On Feb 03 2024, Jan Engelhardt wrote: > >> There is a different problem with py3.12, too: >> >> security:forensics/lib* does a multipython build, which errors out with >> >> ... >> [ 43s] make[2]: Entering directory '/home/abuild/rpmbuild/BUILD/libevt-20240203/pyevt' >> [ 43s] /usr/bin/mkdir -p '/home/abuild/rpmbuild/BUILD/rtpython312_bin_suffix/usr/' >> [ 43s] /usr/bin/bash ../libtool --mode=install /usr/bin/install -c pyevt.la '/home/abuild/rpmbuild/BUILD/rtpython312_bin_suffix/usr/' >> [ 43s] libtool: error: error: cannot install 'pyevt.la' to a directory not ending in /usr/ >> >> That only seems to happen with python 3.12 && security:forensics, >> and the error message does not even make sense, of course it ends in usr/. > It is the trailing slash that apparently confuses it, but then the > library directory should be /usr/lib or /usr/lib64, not /usr. Looks > like the expansion of a variable with an empty value. > Correct. (There must be some copy and paste error. The current build log of libevt does not have the unexpanded python312_bin_suffix in that path: [ 60s] /usr/bin/bash ../libtool --mode=install /usr/bin/install -c pyevt.la '/home/abuild/rpmbuild/BUILD/rt/usr/' [ 60s] libtool: error: error: cannot install 'pyevt.la' to a directory not ending in /usr Compare to the python3.10 iteration before: [ 44s] /usr/bin/mkdir -p '/home/abuild/rpmbuild/BUILD/rt/usr/lib64/python3.10/site-packages' [ 44s] /usr/bin/bash ../libtool --mode=install /usr/bin/install -c pyevt.la '/home/abuild/rpmbuild/BUILD/rt/usr/lib64/python3.10/site-packages' So don't let yourself mislead you by the bogus error message. The real problem is that python 3.12 removed distutils from the standard library. Upstream's python autoconf macro depends on it. It's all either solved by replacing distutils.sysconfig with sysconfig [1] or providing distutils from setuptools in the interim [2]. - Ben [1] https://github.com/libyal/libbde/pull/68 [2] https://build.opensuse.org/request/show/1143980

8 months, 4 weeks

python setuptools

by Peter Czanik

Hi, I submitted syslog-ng to Base:System and then to Factory. It compiled successfully in my home project, then in Base:System, and also while it was under review for Factory. Today I updated my Tumbleweed installation and was surprised to see that syslog-ng is still at the old version. I checked, and it failed to build in Factory, missing "setuptools": [ 164s] (cd ./modules/python-modules && /usr/bin/python3 setup.py \ [ 164s] build --build-base="/home/abuild/rpmbuild/BUILD/syslog-ng-4.6.0/modules/python-modules/build" \ [ 164s] egg_info --egg-base="/home/abuild/rpmbuild/BUILD/syslog-ng-4.6.0/modules/python-modules" \ [ 164s] install --record=/home/abuild/rpmbuild/BUILD/syslog-ng-4.6.0/modules/python-modules/install-manifest.txt --root="/home/abuild/rpmbuild/BUILDROOT/syslog-ng-4.6.0-218.3.x86_64" --install-lib="/usr/lib64/syslog-ng/python") [ 164s] Traceback (most recent call last): [ 164s] File "/home/abuild/rpmbuild/BUILD/syslog-ng-4.6.0/modules/python-modules/setup.py", line 24, in <module> [ 164s] from setuptools import setup [ 164s] ModuleNotFoundError: No module named 'setuptools' [ 164s] make[4]: *** [Makefile:34010: pymodules-install] Error 1 [ 164s] make[3]: *** [Makefile:32461: install-exec-am] Error 2 [ 164s] make[2]: *** [Makefile:30970: install-am] Error 2 [ 164s] make[1]: *** [Makefile:29058: install-recursive] Error 1 [ 164s] make: *** [Makefile:30963: install] Error 2 [ 164s] error: Bad exit status from /var/tmp/rpm-tmp.bxkktG (%install) (full logs at https://build.opensuse.org/package/live_build_log/Base:System/syslog-ng/sta…) What changed during the weekend? :-) Is there a workaround / fix for this problem? Peter

8 months, 4 weeks

Re: RPM 4.19 - first list of missing user provides

by Marcus Meissner

On Mon, Feb 05, 2024 at 11:24:33PM -0600, Paul Lipps via openSUSE Factory wrote: > > > > On Feb 3, 2024, at 4:59 AM, Dominique Leuenberger <dimstar(a)opensuse.org> wrote: > > > > So far I have found this list: > > > >> grep -P "(user|group)" rebuildpacs.openSUSE\:Factory-standard.yaml | > > sed "s/needed by.*//g" | sort -u > > - nothing provides group(amanda) > > - nothing provides group(atheme) > > - nothing provides group(bird) > > snip > > - nothing provides user(znc) > > > > If you spot a user which belongs to one of your packages, please pick > > it up and provide a fix for it (packages will be uninstallable by > > zypper until fixed) > > > > Are items on this list being addressed? I ask because I am a user of znc, and I’m not sure if I need to open a bug or report this elsewhere. various volunteers are going over the list. znc fix is already submitted for instance. Ciao, Marcus

8 months, 4 weeks

Re: Add binary blob driver to Factory

by Joan Torres

Thanks for your answer. Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo?

9 months

Re: Add binary blob driver to Factory

by Lubos Kocman

There are dedicated projects for such packages. You just need to submit it there. https://build.opensuse.org/project/show/openSUSE:Leap:15.6:NonFree https://build.opensuse.org/project/show/openSUSE:Factory:NonFree On Fri, Feb 2, 2024 at 12:36 PM Joan Torres via openSUSE Factory <factory(a)lists.opensuse.org> wrote: > > Thanks for your answer. > > Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo? -- Best regards Luboš Kocman openSUSE Leap Release Manager

9 months

Re: Add binary blob driver to Factory

by Marcus Meissner

Hi, Still, packages in there need a valid redistribution license verified by legal. Ciao, Marcus On Fri, Feb 02, 2024 at 12:47:07PM +0100, Lubos Kocman via openSUSE Factory wrote: > There are dedicated projects for such packages. You just need to > submit it there. > > https://build.opensuse.org/project/show/openSUSE:Leap:15.6:NonFree > https://build.opensuse.org/project/show/openSUSE:Factory:NonFree > > On Fri, Feb 2, 2024 at 12:36 PM Joan Torres via openSUSE Factory > <factory(a)lists.opensuse.org> wrote: > > > > Thanks for your answer. > > > > Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo? > > > > -- > > Best regards > > > Luboš Kocman > openSUSE Leap Release Manager -- Marcus Meissner (he/him), Distinguished Engineer / Senior Project Manager Security SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew McDonald, Werner Knoblich, HRB 36809, AG Nuernberg

9 months

RPM 4.19 already in Factory

by Ana Guerrero Lopez

Dear community, In case you didn't update your Tumbleweed systems yet, RPM 4.19.1 was accepted earlier this week. As outlined below, some packages will still need updates. Have a nice weekend! Ana On 19/01/2024 13:56, Ana Guerrero Lopez wrote: > > Dear Tumbleweed hackers and packagers, > > > After a lengthy staging period, RPM 4.19 is shaping up and all issues > noticed in the rings (packages guaranteed to build/be installable) > have been addressed or have fixes pending. > > As you are all aware, the rings cover only about 20% of the packages > in Factory. > > > The release notes for RPM 4.19 are at https://rpm.org/wiki/Releases/4.19.0 > > Out of the RPM release notes (https://rpm.org/wiki/Releases/4.19.0) > the two most noteworthy bullets are: > > > * Any non-root ownership in the %files section (through %attr() or > %defattr()) now generates an automatic dependency on the named user > and/or group. This dependency can be satisfied by another package > shipping a sysusers.d(5) file or the /etc/passwd and /etc/group files > themselves. Existing packages shipping any of these files will have to > be rebuilt with RPM 4.19 in order for them to carry the respective > user and/or group provides. This may require distro-level coordination > to ensure proper installation of all the affected packages. For more > information, please consult the manual. > > > * %patch without arguments (previously an alias to %patch 0) is now > a build error (use %patch N instead) > > > The %patch one is rather simple and results in a build failure; > monitoring your devel packages should give you hints very soon if your > package is impacted. We created submit requests for most, if not all, > packages affected by that in the last months. > > > The story around the users can be trickier to be identified, as the > build might succeed, but the package not being installable at the end > due to missing dependencies reported. This usually happens when users > are generated in %pre scripts using useradd. Either convert those > packages to use sysusers.d > (https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups) > or, as a quickest measure, usually helpful if no other package relies > on the same users, manually add the respective Provides: > user(USERNAME) and Provides: group(GROUPNAME) to the package > generating the relevant user (as done for example in cluster-glue, > https://build.opensuse.org/request/show/1138101 for reference) > > > If you have any questions or need with your package, the > opensuse-packaging mailing list is always at your disposal. > > > Ana, > > on behalf of the Release Team > >

9 months

openSUSE Factory search results for query "a"