openSUSE Packaging June 2018

packaging@lists.opensuse.org

34 participants
14 discussions

[opensuse-packaging] New macro to limit resources allocation per thread

by Tomas Chvatal

Hello all, For use in libreoffice, chromium and others I've created macro that should allow you to limit jobs based on some constraints you can set later on in the spec to avoid OOM crashes. The usage is pretty straight forward (Once it is accepted in Tumbleweed): === BuildRequires: memory-constraints %build # require 2GB mem per thread %limit_build -m 2000 make %{?_smp_mflags} ==== Here the _smp_mflags vaule for 8GB machine would be 4 while default is number of cores (lets say 16)... Both macros %jobs and %_smp_mflags are overriden as such the integration should be really painless if you need to do something like this. Tom

2 years, 8 months

[opensuse-packaging] Manually run repo-checker

by Todd Rme

Is there a way to manually run repo-checker on a package or repository? Specifically, I want to run the check to see if the built packages are installable. I think I fixed such an issue but I want to check it before I submit it. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 8 months

[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

3 years, 10 months

[opensuse-packaging] suppressing rpmlint errors and warnings

by Olaf Hering

How does one hide things that rpmlint reports as errors? This "rpmlintrc" is not enough to avoid the build errors due to new polkit things. addFilter("filename-too-long-for-joliet") addFilter("missing-dependency-to-logrotate") addFilter("no-changelogname-tag") addFilter("no-description-tag") addFilter("obsolete-suse-version-check") addFilter("polkit-unauthorized-privilege") addFilter("polkit-untracked-privilege") addFilter("shlib-fixed-dependency") addFilter("shlib-policy-name-error") addFilter("suse-missing-rclink") This is my own pkg, so polkit-* reports are of no concern. Olaf

3 years, 10 months

[opensuse-packaging] Fixing a link to source package

by Axel Braun

Hi, I had branched a couple of python package into a different project, which now all run into an error: Link has errors: conflict in file foo.spec. Obviously the source file has changed, and as I did not touch the spec file, my expectation would be that the linked package takes over these changes, or that there is at least an easy way to sync them again. I've checked osc man page but could not find the right command. Any hints? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 10 months

[opensuse-packaging] %license macro in devel packages

by Michal Rostecki

Hi, I have a question regarding the %license macro. When a spec contain also devel package definition and `%files -n devel` section, should that macro be included in all packages, or only in the "main" package? I tried to google about that: https://www.google.de/search?q=%25license+devel+site%3Abuild.opensuse.org It seems that the majority of packages use %license macro in all %files sections, i.e.: https://goo.gl/77TD6c But there are some packages which don't, i.e.: https://goo.gl/2msyMJ What's the most recommended and correct way of using %license macro with multi-package specs? Cheers, Michal -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 10 months

[opensuse-packaging] stuck jobs

by Mathias Homann

Could someone please kick some of the stuck jobs on the build service? I mean, you can't tell me that TWENTY SIX DAYS in one job is normal (devel:languages:python:Factory/python3 on armv7i), or four days on s390x (the same package) Cheers MH -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -------- [1] https://build.opensuse.org/project/show/devel:languages:python:Factory -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 11 months

[opensuse-packaging] Checking whether package is being upgraded

by John Paul Adrian Glaubitz

Hi! What is the easiest way to determine during the %post scriptlet in a spec file whether the package is currently being upgraded instead of being installed? I checked the documentation but couldn't find anything relevant. I also tried testing whether the first argument to rpm is "2", i.e. "$1 -eq 2" similar to [1] but that seems to work on Fedora only. Anyone can give me a quick hint? Thanks, Adrian > [1] https://github.com/GoogleCloudPlatform/compute-image-packages/blob/master/s… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 11 months

[opensuse-packaging] Need help with qt related build failures.

by Dave Plater

Hi, I've been overwhelmed with build failures, gcc8, boost-python and strange gstreamer error (all fixed). The gcc8 ones are easy enough but I'm a bit stuck on the qt5 errors. Can someone please have a look at : https://build.opensuse.org/package/show/home:plater/qtractor and https://build.opensuse.org/package/show/home:plater/shotcut I'm assuming they are caused by a qt5 update. The non qt problems I've managed to fix. Thanks Dave -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 11 months

[opensuse-packaging] new %{pythons} macro, that isn't defined anywhere

by Hans-Peter Jansen

Hi, I'm observing a new python rpm macro, appearing in BuildRequires: %{pythons} in some packages, that isn't defined anywhere. Consequently, this breaks a few of my branched packages. Example: https://build.opensuse.org/package/view_file/devel:languages:python/python-… Line: 49 Could somebody shed some light on this, please? Thanks in advance, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 11 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging June 2018