openSUSE Packaging August 2017

packaging@lists.opensuse.org

34 participants
29 discussions

[opensuse-packaging] Update: New repo-checker to be deployed on August 14th
by Jimmy Berry 18 Aug '17

18 Aug '17

packagers, Roughly four hours ago the switch to the new repo-checker was performed. The factory-auto bot will now assign reviews to the repo-checker user instead of factory-repo-checker [1]. All requests processed before the switch will remain with the old factory-repo-checker. Once the open reviews are all handled (currently 820) the old checker will be completely disabled. If your requests ends up in a staging with requests assigned to the new repo-checker it will effectively block requests assigned to the factory-repo-checker since all reviews in a staging must be accepted. This is likely to occur in large stagings where requests may be superseded or added before accepting the group. The first request to be accepted by the new repo-checker was 516919 [2] while the first to be assigned was 516906 [3]. As such any request IDs greater than 516906 will be assigned to repo-checker instead of factory-repo-checker. Still quite a few problems in Factory to be resolved [5] along with some interesting discoveries [6] due to the new devel project comments. Several file conflicts due to shared namespaces between packages have been resolved after devel comments. Enjoy! [1] https://github.com/openSUSE/osc-plugin-factory/pull/1017 [2] https://build.opensuse.org/request/show/516919 [3] https://build.opensuse.org/request/show/516906 [4] https://github.com/openSUSE/osc-plugin-factory/issues?&q=is%3Aissue%20is%3A… [5] https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashb… [6] https://lists.opensuse.org/opensuse-releaseteam/2017-08/msg00000.html -- Jimmy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] factory-auto says "Unknown tag: bad spec python-wheel.spec"
by Sebastian 18 Aug '17

18 Aug '17

Hi, This request: https://build.opensuse.org/request/show/512806 got declined by factory-auto with this comment: > Output of check script: > Source validator failed. Try "osc service localrun source_validator" > https://files.pythonhosted.org/packages/source/w/wheel/wheel-0.29.0.tar.gz https://files.pythonhosted.org/packages/source/w/wheel/wheel-0.29.0.tar.gz error: line 21: Unknown tag: bad spec python-wheel.spec What does this mean? When running the specified command locally, I don't get this error. I got this error sometime in the last months in another request too, but I don't remember which one it was now. Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

4 5

[opensuse-packaging] OBS Notification Build Failure Spam
by Jan Ritzerfeld 17 Aug '17

17 Aug '17

Hey, OBS Notification currently spams me about build failures in "my" projects although anyone didn't change anything: | getbinaries: missing packages: liblua5_3 Any ideas what I should do now? I didn't see any announcements here... Gruß Jan -- Technological man can't believe in anything that can't be measured, taped or put into a computer. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] turn off debug & save on builspace & create archive failed on file /home/abuild/rpmbuild/BUILDROOT/,,,
by doiggl＠velocitynet.com.au 15 Aug '17

15 Aug '17

Hello, How can i turn OFF debug to save space on build. Thanks --Glenn At end of build I see in log: . . [ 7518s] File[ 7502.920071] serial8250: too much work for irq4 [ 7518s] listed twice: /usr/lib/debug/.build-id [ 7518s] File listed twice: /usr/lib/debug/.build-id [ 7518s] File listed twice: /usr/lib/debug/.build-id [ 7518s] File listed twice: /usr/lib/debug/.build-id [ 7518s] File listed twice: /usr/lib/debug/.build-id [ 7518s] File listed twice: /usr/lib/debug/.build-id [ 7518s] create archive failed on file /home/abuild/rpmbuild/BUILDROOT/kernel-reiser4-4.12.7-3.1.x86_64/usr/lib/debug/lib/modules/4.12.7-3-vanilla/kernel/drivers/mtd/maps/ichxrom.ko.debug: cpio: write failed - No space left on device [ 7519s] [ 7519s] cloud103 failed "build kernel-reiser4.spec" at Tue Aug 15 08:14:29 UTC 2017. [ 7519s] [ 7519s] ### VM INTERACTION START ### [ 7523s] [ 7507.229709] reboot: Power down [ 7525s] ### VM INTERACTION END ### [ 7525s] [ 7525s] cloud103 failed "build kernel-reiser4.spec" at Tue Aug 15 08:14:35 UTC 2017. [ 7525s] # https://build.opensuse.org/package/show/home:doiggl/kernel-reiser4 https://build.opensuse.org/build/home:doiggl/openSUSE_13.1/x86_64/kernel-re… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

Re: [opensuse-packaging] Re: Python packaging for Fedora/CentOS requires /usr/bin/python which doesn't exist
by Axel Braun 15 Aug '17

15 Aug '17

Am Dienstag, 15. August 2017, 08:10:16 CEST schrieb Adrian Schröter: > On Montag, 14. August 2017, 22:54:30 CEST wrote Neal Gompa: > > On Mon, Aug 14, 2017 at 4:50 PM, Kristoffer Grönlund <kgronlund(a)suse.com> wrote: > > > Neal Gompa <ngompa13(a)gmail.com> writes: > > >> On Wed, Aug 9, 2017 at 12:20 PM, jan matejek <jmatejek(a)suse.com> wrote: > > >>> On 9.8.2017 12:25, Kristoffer Grönlund wrote: > > >>>> Hi, > > >>>> > > >>>> I'm having a problem with packaging crmsh for RH distros on OBS: It > > >>>> seems that the rpm packages end up requiring /usr/bin/python which > > >>>> does > > >>>> not exist on those distributions: > > >>>> > > >>>> https://github.com/ClusterLabs/crmsh/issues/161 > > >>>> > > >>>> I can't see any direct requirement in the spec file which would do > > >>>> this > > >>>> other than requiring python itself. > > >>> > > >>> You get automatic requirements on shebang interpreters, i.e., what is > > >>> listed after "#!" at start of your script. > > >>> > > >>> We're actually moving away from using /usr/bin/python. Would it help > > >>> if you changed it to /usr/bin/python2 ? > > >> > > >> For what it's worth, we're moving away from /usr/bin/python in Fedora > > >> as well. We recommend using /usr/bin/python2 or /usr/bin/python3 for > > >> the version of python it should be used with. > > > > > > Thank you, your recommendations seems to have put me on the right > > > track. I managed to clean up the binary requirements, but something > > > weird is happening when I change the shebang to /usr/bin/python2: The > > > rpm ends up still depending on /usr/bin/python. Could it be because > > > /usr/bin/python2 is a symlink to /usr/bin/python in the build > > > environment or something like that? > > > > Maybe. At least in RHEL/CentOS 7, /usr/bin/python is a symlink to > > /usr/bin/python2, which is a symlink to /usr/bin/python2.7, so I doubt it. > > > > You may have something somewhere still declaring "/usr/bin/python" or > > "/usr/bin/env python" as a shebang. > > > > Something is wrong if it's generating a dependency of /bin/python, > > though. That means something is specifically setting "/bin/python" as > > a shebang. > > I could define /usr/bin/python to a specific package given that there > is no definition which exact python version is to be used in RedHat (from > what I read here). You could do some kind of dynamc definition: PACKAGE_DIR=$(ls -d /usr/lib/python3.* )/site-packages HTH Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Python packaging for Fedora/CentOS requires /usr/bin/python which doesn't exist
by kgronlund＠suse.com 15 Aug '17

15 Aug '17

Hi, I'm having a problem with packaging crmsh for RH distros on OBS: It seems that the rpm packages end up requiring /usr/bin/python which does not exist on those distributions: https://github.com/ClusterLabs/crmsh/issues/161 I can't see any direct requirement in the spec file which would do this other than requiring python itself. I've looked at using the newer python rpm macros for crmsh, but since it's a Makefile-based build with some strange requirements, Python 2 only packaging a binary with extra files etc., it's not straight-forward. Any tips or help would be very much welcome :) The packaging is here: https://build.opensuse.org/package/show/network:ha-clustering:Stable/crmsh Cheers, Kristoffer -- // Kristoffer Grönlund // kgronlund(a)suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] Poll about Url vs URL in RPM preamble
by Tomas Chvatal 14 Aug '17

14 Aug '17

Hi all, As per complains here that we should use URL rather than Url in the preamble of the spec-files I've decided to create quick doodle poll. From parser perspective there is 0 difference but since there is vocal proposition for URL instead of Url that is now replaced by spec- cleaner. I decided to create a poll where the majority will become default set value. [1] I will keep the doodle running until 14.8. and announce the results afterwards and tweak spec-cleaner if other value wins. I still think Url is fine as it is not URL in the "Uniform Resource Locator" but just variable name. Thanks for voting Tom [1] https://beta.doodle.com/poll/9y6gfunm8bm8cz3b

13 29

[opensuse-packaging] Changing GNOME/GTK Python package devel projects to GNOME:Factory
by Todd Rme 14 Aug '17

14 Aug '17

Most GNOME and GTK-related Python packages have GNOME:Factory as their devel project. There are a few, however, that still have devel:languages:python as their devel project: python-gnome python-gnome-extras (recently removed from openSUSE:Factory) python-gtk python-gtksourceview python-webkitgtk As part of our general reorganization of Python packages, packages that are of primary interest to a particular toolkit should live in that toolkit's devel project. However, the GNOME:Factory versions of these packages link to the devel:languages:python packages, rather than the openSUSE:Factory ones. So that means I cannot request a devel project change myself. Would it be possible with someone access to GNOME:Factory change the link target of these five packages there to openSUSE:Factory (or break the link in the case of python-gnome-extras) and then request a devel project change for them to GNOME:Factory? Thank you. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] Handling of /var/adm/update-messages
by Olaf Hering 12 Aug '17

12 Aug '17

According to the documentation all messages should be _packaged_ as /var/adm/update-messages/name-version-release-anything: https://old-en.opensuse.org/Software_management/Code11/Scripts_and_Messages However, none of the packages in Factory implements that. Some create them on the fly, some package them as %ghost. Are the packages wrong, or is the documentation outdated? Olaf

2 1

[opensuse-packaging] SLE 12 hdf5 issue
by Todd Rme 11 Aug '17

11 Aug '17

For devel:languages:python, we am getting the following "unresolved" issue for all enabled SLE 12 releases: nothing provides hdf5 = 1.8.12 needed by hdf5-devel nothing provides libhdf5-8 = 1.8.12 needed by hdf5-devel nothing provides libhdf5_hl8 = 1.8.12 needed by hdf5-devel As far as I can tell there are no hdf5-related rpms in the repository, so I can't figure out what is causing this problem. Does anyone have any ideas? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging August 2017