November 2023 - openSUSE Packaging - openSUSE Mailing Lists

Conflicting requests for new JPM package
by Jochen Breuer 12 Dec '23

12 Dec '23

Hi folks, hi Soc, I've just noticed that we've got conflicting requests to create a new JPM package in devel:languages:misc. JPM is the Janet Project Manager tool and Janet is already in devel:languages:misc. So JPM is kind of missing there. There is a request from uncomfyhalomacro [0] and one from me [1]. Both are very similar. The main difference is that I'm using the bootstrapping script from upstream and uncomfyhalomacro is installing files manually. Not sure if the linux_config.janet is really needed past installation, but this is something we can discuss afterwards. While I like the approach with the bootstrapping script more, I'd be happy if any of them would be accepted. We could then start improving on top of the accepted package. Cheers, Jochen [0] https://build.opensuse.org/request/show/1123454 [1] https://build.opensuse.org/request/show/1125447

1 1

Howto BuildRequire a higher gcc version for #include <filesystem>? Or else?
by Alexander Krupp 13 Nov '23

13 Nov '23

Hello, I am trying to build a c++ based package on obs for 15.4, 15.5, Tumbleweed, which includes <filesystem>. Unfortunately this seems to be standard from gcc-c++>=11 on, only. BuildRequires: gcc>=11 results in "nothing provides gcc>=11". I have also tried "gcc >=11", and BuildConflicts: gcc however, this completely breaks. I have tried "gcc11-c++" which installs, but is not used in the build. Is it possible to switch to a higher gcc version via spec file alone? Or is it possible to compile this with gcc<11 by means of some CC flags? I have searched on the net extensively, without result. I would appreciate a pointer to any information that could help. Thank you in advance, Alex

3 3

rpmlint complains about rpath
by Cor Blom 03 Nov '23

03 Nov '23

Hi all, I have worked on updating kbibtex.[1] However, I get a rpmlint complaint that the executable and some libaries include reference to rpath or runpath (/usr). I have used "chrpath -d" to remove them so that the build succeeds, but I can't imagine this is a good approach. Is this something I should report upstream or is there is trick, like a build flag, to solve this in a nice way? Thanks. Cor [1] https://build.opensuse.org/package/show/home:cornelisbb:branches:KDE:Extra/…

3 3

How to build a static libjanet?
by Jochen Breuer 03 Nov '23

03 Nov '23

Hi folks, I'm currently working on bringing jpm[0], the Janet Project Manager, to the repos. Overall I'd say it looks good, but one feature of jpm isn't working. Normally you can build statically linked binaries with jpm if there is a libjanet.a. Now in Janet[1] we unfortunately only build libjanet.so. I know next to nothing about meson/c. Is it possible to build the share and the static libjanet in the same run for janet-devel? Thanks, Jochen [0] https://build.opensuse.org/package/show/home:brejoc/jpm [1] https://build.opensuse.org/package/show/devel:languages:misc/janet

2 2