openSUSE Packaging March 2018

packaging@lists.opensuse.org

24 participants
14 discussions

[opensuse-packaging] %license and build failures on SLE12

by Takashi Iwai

Hi, recently there have been a few updates of package to use %license for the license files. And this seems triggering the build failures for SLE12. How would we cure this? Fiddling with some prjconf stuff? thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 7 months

[opensuse-packaging] submitting 2 packages with the same source

by Jordi Massaguer Pla

Hi packagers :) , I have these two packages which have the same source. I've seen sometimes we have a package foo with 2 spec files, foo.spec and bar.spec, and then we have another package, bar, which is a link to foo. This way, both share the same source. I tried to do that, but when I submitted (osc sr) foo and bar to another project, the link was lost, and instead I had two independent packages with a copy of the same source. Is there a way to keep the link? I tried the "--update-link" option but didn't make a difference. Thanks in advance jordi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 9 months

[opensuse-packaging] Ownership issues with /usr/share/licenses in SLE-12

by John Paul Adrian Glaubitz

Hello! I'm trying to build python-pytest-relaxed for SLE-12 in backports which is required as a dependency for one of the tools we are using for the public cloud stuff. The build fails with RPM complaining about /usr/share/licenses being unowned: [ 4s] ... running 01-check-debuginfo [ 4s] ... testing for empty debuginfo packages [ 4s] ... running 02-check-gcc-output [ 4s] ... testing for serious compiler warnings [ 4s] (using /usr/lib/build/checks-data/check_gcc_output) [ 4s] (using /var/tmp/build-root/openSUSE_Backports_SLE-12-x86_64/.build.log) [ 4s] ... running 03-check-binary-kernel-log [ 4s] ... running 04-check-filelist [ 4s] ... checking filelist [ 4s] python-pytest-relaxed-1.0.0-0.noarch.rpm: directories not owned by a package: [ 4s] - /usr/share/licenses [ 4s] python3-pytest-relaxed-1.0.0-0.noarch.rpm: directories not owned by a package: [ 4s] - /usr/share/licenses [ 4s] [ 4s] suse-laptop failed "build python-pytest-relaxed.spec" at Fri Dec 15 13:35:27 UTC 2017. [ 4s] Normally, this issue is fixed by installing the package which install this directory into the chroot, either through a Preinstall directive in the project configuration or by adding the package in question to Build-Depends in the spec file. The directory /usr/share/licenses is provided by filesystem which I tried preinstalling through the aforementioned mechanisms. However, I still keep running into the ownership issue as shown above. Does anyone have any idea what I am doing wrong? Thanks, Adrian -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 10 months

[opensuse-packaging] Selecting GCC version

by Matthias Fehring

Hello, is there a simple way to force the GCC version used to build a package? openSUSE Leap 42.2 for example uses GCC 4.8 as default compiler, but also provides packages for GCC 5.3. Simply using BuildRequires gcc5 pulls gcc5 in but still uses gcc48 to build the package (especially in Build Service). So is there maybe some Buid Service or spec file switch (bcond) to select the used GCC version? Best greetings Matthias Fehring P.S. Not sure if it is a problem with my browser settings, but when I try to search lists.opensuse.org, it is not possible for me to limit the results to a specific list. Even if I set one, I get results from all lists, what makes searching almost impossible, because most results are commit messages. -- Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre. (Friedrich Schiller - Die Räuber) www.buschmann23.de GPG-Key: 0x614C3258 GPG Fingerprint: D786 DDF8 4CA9 00BC CDE0 9A5F CCC5 125D 6E87 D4FC

2 years, 10 months

[opensuse-packaging] Where to submit if package has no devel project ?

by Sébastien 'sogal' Poher

Hello everybody, I use 'most' as pager, this package is currently absent from Leap 15.0. I have made an upgraded package [0] for it but couldn't find a devel project for 'most', only the OBS page for Leap 42.3 [1] I am not sure what to do here: - submitting to Factory/most directly from my home project ? or - branch Leap:42.3/most, upgrade it then submit to Factory/most ? - anything else ? Thank you for any advice on this. Regards [0] https://build.opensuse.org/package/show/home:sogal/most [1] https://build.opensuse.org/package/show/openSUSE:Leap:42.3/most -- Sébastien 'sogal' Poher -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

[opensuse-packaging] removing 42.2 on Virtualization:containers and devel:CaaSP:Head:ControllerNode

by Jordi Massaguer Pla

Hi, I just removed 42.2 repository in V:c and disabled that in d:C:H:CN, since 42.2 had reached EOL on Jan, 26th. regards jordi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

[opensuse-packaging] removing 42.2 from devel:languages:go

by Jordi Massaguer Pla

Hi all, I just removed openSUSE 42.2 from devel:languages:go since 42.2 had reached EOL on Jan, 26th. regards jordi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

[opensuse-packaging] use of sed to fix python2 script interpreter

by Sébastien 'sogal' Poher

Hi everyone, I am packaging pyrenamer [0] in order to submit it to Factory. As it is, I got this warning [1] because of the 'shebang' calling '/usr/bin/env python' instead of '/usr/bin/python' (which should be 'python2'). I have fixed it by adding the following: sed -i 's|/usr/bin/env\ python|/usr/bin/python2|1' %{buildroot}/%{_bindir}/%{name} in %install section. Is it a good way to do it or is there a more recommended way ? Thank you [0] https://build.opensuse.org/package/show/utilities/pyrenamer [1] full warning is: pyrenamer.noarch: E: env-script-interpreter (Badness: 9) /usr/bin/pyrenamer /usr/bin/env python This script uses 'env' as an interpreter. For the rpm runtime dependency detection to work, the shebang #!/usr/bin/env python needs to be patched into #!/usr/bin/python otherwise the package dependency generator merely adds a dependency on /usr/bin/env rather than the actual interpreter /usr/bin/python. Alternatively, if the file should not be executed, then ensure that it is not marked as executable or don't install it in a path that is reserved for executables. -- Sébastien 'sogal' Poher -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

[opensuse-packaging] Upgrade path from xinetd to systemd socket-activated service

by Michal Srb

Hi, Some time ago I converted the VNC service in xorg-x11-Xvnc package from being a xinetd service to be a socket-activated systemd service. However this change does not preserve the enabled state - people who had VNC enabled and upgrade get it disabled again. Is there some preferred way to transfer the "enabled" state during such upgrade? My idea so far is to check for /etc/xinetd.d/vnc.rpmsave in %post. If it exist and the service inside was enabled, then enable the systemd socket. Michal Srb -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

[opensuse-packaging] /usr/share/icons/hicolor directories not owned by a package

by Aivar Annamaa

Hi! I experimented with packaging Thonny, Python IDE for beginners (http://thonny.org). Here is my attempt: https://build.opensuse.org/package/show/home:aivarannamaa/thonny It is based on Fedora package https://src.fedoraproject.org/rpms/thonny but I changed some package names and included some other tweaks. This SPEC builds nicely on my own computer (Tumbleweed) but the Open Build Service complains about icon folders not owned by a package: [ 44s] thonny-2.1.16-7.1.noarch.rpm: directories not owned by a package: [ 44s] - /usr/share/icons/hicolor [ 44s] - /usr/share/icons/hicolor/128x128 [ 44s] - /usr/share/icons/hicolor/128x128/apps ... My SPEC does require hicolor-icon-theme, so I expected that these folder are owned by that package. Any ideas how to fix this? Do I understand correctly that in order to get this Thonny into openSUSE repos it needs to first build on Open Build Service? best regards, Aivar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging March 2018