October 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] 10 hours package signing?
by Bjoern Voigt 16 Oct '17

16 Oct '17

Some of my build service packages currently take a very long time. E.g. https://build.opensuse.org/package/live_build_log/home:bjoernv:branches:net… The build process itself is fast (118 seconds). But since 10 hours the status is "signing". Some other packages of the same repository are ready now. Is there an build service problem or is it my fault? Where can I report such problems in future? Greetings, Björn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] python-redfish singlespec conversion: update-alternatives, subpackage common
by Johannes Kastl 14 Oct '17

14 Oct '17

Dear python-experts, I wanted to play around with python-redfish, so I started to package it. mnhauke already had a package, which I took as a starting point and tried to convert to singlespec. home:ojkastl_buildservice:Redfish_openSUSE 2 questions: ### I copied the update-alternative stuff from another spec (I think python-chardet), and it seems to build, but this is in the logs. Am I missing something in the spec? Error in the mv commands (mv /usr/bin/redfish-client /usr/bin/redfish-client-2.7 etc.)? Conditional missing? > [ 71s] (order: reverse python-redfish-common python2-redfish python3-redfish) > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-client-2.7 doesn't exist > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-check-cartridge-2.7 doesn't exist > [ 71s] warning: %postun(python2-redfish-0.4.1-3.1.noarch) scriptlet failed, exit status 2 > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-client-3.6 doesn't exist > [ 71s] update-alternatives: error: alternative path /usr/bin/redfish-check-cartridge-3.6 doesn't exist > [ 71s] warning: %postun(python3-redfish-0.4.1-3.1.noarch) scriptlet failed, exit status 2 ### I created a subpackage python-redfish-common and required it in the preamble, as there are some files, that seem to exist or be needed in both the python2 and python3 package. %files -n %{name}-common %config(noreplace) %{_sysconfdir}/redfish-client.conf %{_datadir}/redfish-client %{_mandir}/man1/python-redfish.1%{ext_man} I have not tested, whether both versions can use the same config file (I guess so). There are some templates in %{_datadir}/redfish-client that seem to be needed by both versions. Is this a valid approach? Or should I solve this differently? I found nothing (or missed it) in the singlespec page. ### Thanks in advance for any hints, tips, tricks and comments! Johannes

3 3

[opensuse-packaging] Be very careful with Requires(pre)!
by Michael Schroeder 13 Oct '17

13 Oct '17

Hi Packagers, some days I stumbled over an oddity in the wicked package. Rpm allowed the deinstallation of the "wicked" and "libwicked-0-6" packages even if wicked-service was still installed. It turned out that the issue was with Requires(pre). What many packagers seem to not know is that this means two things: - the package is needed in the prein scriptlet - the package is no longer needed after the installation (!) This is also cleary stated in the rpm's documentation: http://rpm.org/user_doc/more_dependencies.html#scriptlet-dependencies Note that this was not a problem for PreReq, as it is identical to Requires(pre,preun) and thus the package needs to be kept installed. But it's dangerous to simply change PreReq to Requires(pre), as seemed to be done for a large amount of packages. So I'd like to ask all of you to check your packages if you have a Requires(pre) that's also needed at runtime. The most correct way of fixing this is to simply add another line without the (pre): Requires(pre): libwicked-0-6 = %{version} Requires: libwicked-0-6 = %{version} Thank you, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Building python-chardet for Leap 42.2 fails, if python-coverage is not added to the project
by Johannes Kastl 13 Oct '17

13 Oct '17

Hi all, I get build failures for python-chardet in my Redfish_openSUSE project, but only for Leap 42.2. home:ojkastl_buildservice:Redfish_openSUSE/python-chardet [ 33s] File "/usr/lib/python2.7/site-packages/hypothesis/core.py", line 32, in <module> [ 33s] from coverage.files import canonical_filename [ 33s] ImportError: cannot import name canonical_filename It seems to build fine for 42.2 in d:l:p. devel:languages:python/python-chardet My first guess would be that it needs python-coverage as BuildRequires. Which might be available on other versions of Leap and Tumbleweed and in d:l:p. I tried linkpac'ing python-coverage to my project (for 42.2. only), and yes, suddenly python-chardet builds fine for 42.2. 2 questions: My naive guess would be that python-coverage (or %{python_module coverage}) is missing from the BuildRequires of python-chardet. But why does it get pulled in, once there is a version of python-coverage available, even without being added to the spec? Or is it pulled in by one of the dependencies of python-chardet, so that package's spec needs to be adapted? Or both spec files? Or is there a version available, but not in the right version? Leap 42.2 has python-coverage, it seems: | python-coverage | Paket | 3.7.1-6.3 | x86_64 | openSUSE-Leap-42.2-Oss | python3-coverage | Paket | 3.7.1-4.4 | x86_64 | openSUSE-Leap-42.2-Oss Thanks in advance! Confused. Johannes

2 3

[opensuse-packaging] [Fwd: [opensuse-factory] Deprecation of devel:languages:python3]
by Tomas Chvatal 13 Oct '17

13 Oct '17

Hi, as I was poked that there might be people interested in this even here please read up and discuss on opensuse-factory mailinglist to avoid cluttering. (Also there already is some discussion thus if not subscribed check up the lists.opensuse.org archives) Tom

1 0

[opensuse-packaging] Re: [opensuse-factory] rpmlint 1.10 about to enter openSUSE Factory
by Richard Biener 11 Oct '17

11 Oct '17

On Mon, 9 Oct 2017, Dirk Müller wrote: > Hi, ... > - env-script-interpreter: This is a new check that has a Badness of 9. > The value is so low because it triggers tremendously often right now. > Basically, for shell scripts installed with chmod +x in the typical > binary directories like /usr/bin and the like, it is alerting when the > script shebang starts with "#!.*env ". The intention here is to avoid > the rpm-dependency logic add a file-depends on /usr/bin/env (which is > useless) and have the *actual* interpreter added as dependency > instead. So to silence the warning, something like > > sed -i -e "1 s,#! */usr/bin/env python,#!/usr/bin/python2," > %{buildroot}/%{_bindir}/*.py > > is needed. This lets the rpm-dependency magic add a proper > file-depends on /usr/bin/python2, pulling in python-base if it isn't > installed already. Huh, why not fix RPM instead? Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

4 3

[opensuse-packaging] Aw: Re: [opensuse-factory] Re: SUSE Studio Express questions
by Axel Braun 10 Oct '17

10 Oct '17

> Gesendet: Montag, 09. Oktober 2017 um 18:12 Uhr > Von: "Roger Oberholtzer" <roger.oberholtzer(a)gmail.com> > An: "Andreas Jaeger" <aj(a)suse.com> > Cc: "Jim Henderson" <hendersj(a)gmail.com>, opensuse-factory <opensuse-factory(a)opensuse.org> > Betreff: Re: [opensuse-factory] Re: SUSE Studio Express questions > > On Mon, Oct 9, 2017 at 9:32 AM, Andreas Jaeger <aj(a)suse.com> wrote: > > On 2017-10-09 09:07, Roger Oberholtzer wrote: > >> On Fri, Oct 6, 2017 at 2:09 PM, Andreas Jaeger <aj(a)suse.com> wrote: > >>> On 2017-09-26 12:34, Roger Oberholtzer wrote: > >>>> On Mon, Sep 25, 2017 at 8:33 PM, Jim Henderson <hendersj(a)gmail.com> wrote: > >>>> > >>>> It would be great if one could import a kiwi project that one > >>>> currently runs on a local computer. Not just one set up in Studio. > >>> > >>> You should be able to add kiwi files that you have locally, there's > >>> nothing magic here. What is not working for you? > >> > >> I have not figured out the general work flow. I can choose some > >> pre-defined things to build. So I am guessing one chooses one of > >> those, and then changes files as needed? > >> > >> I guess I need to play with it a bit to see what I can do. An "Import > >> local KIWI spec" would make sense. Of course, I only have a handful of > >> these. So if I get the steps sorted out I can do things by hand. I'm > >> okay with that. As long as I know what makes sense to change. > >> > > > > See also > > http://openbuildservice.org/2017/09/27/suse-studio-express/ > > I've added my kiwi files, but I get a error that nothing defines any > of the packages I want. I know that if I specify the repository wrong > I get an error. But I don't get that kind of error. > > https://build.opensuse.org/package/show/home:rogeroberholtzer/rsl-oem-42.3 > > This pretty much works as a native build on my Leap 42.3. I expect it > would get further along. I'm sure I'm just blind. There are some error messages regarding 'have choice of...' - fix them by adding the respective package to your build, then try again I cc opensuse-packaging, we should follow-up there. Cheers Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Re: [opensuse-kernel] What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process.
by Takashi Iwai 09 Oct '17

09 Oct '17

On Mon, 09 Oct 2017 11:50:59 +0200, Matthias Brugger wrote: > > > > On 10/07/2017 03:54 PM, doiggl(a)velocitynet.com.au wrote: > > Hello. > > > > What reiser4 parameters do I to append to .config to enable the > > reiser4-for-4.13.0.patch in kernel build process. > > > > The reiser4-for-4.13.0.patch applies to kernel ok. > > > > Build Log shows: > > + patch -s -F0 -E -p1 --no-backup-if-mismatch -i > > ../patches.rpmify/reiser4-for-4.13.0.patch > > > > I put 'reiser4' parameters in zreiser4parameters.txt and it gets appended > > that to .config > > I just trigger rebuild process. > > > > I think the best way would be to change the needed config parameters > in the configs you care from config.tar.bz2 Yes, either that or putting the new stuff into patches.addon.tar.bz2 and config.addon.tar.bz2. Takashi > > Regards, > Matthias > > > Thanks for your expertise. > > --Glenn > > > > # > > > > project info, patch and log urls: > > > > :project > > # https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla > > > > spec: > > # > > https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… > > > > :apply reiser4 patch > > # > > https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… > > > > :reiser4 parameters used added to: zreiser4parameters.txt > > CONFIG_DEBUG_INFO_REDUCED=n > > CONFIG_DEBUG_INFO_SPLIT=n > > CONFIG_FRAME_POINTER_UNWINDER=n > > CONFIG_GDB_SCRIPTS=n > > CONFIG_REISER4_DEBUG=n > > CONFIG_REISER4_FS=m > > CONFIG_SUSE_KERNEL_SUPPORTED=y > > > > > > #add reiser4 parameters to .config line , from spec file: > > /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i > > zreiser4parameters.txt` >> .config > > > > > > :build log > > # > > https://build.opensuse.org/public/build/home:doiggl/openSUSE_Leap_42.3/x86_… > > > > # > > Steps done in specfile: > > ---------------------- > > > > KERN_DIRS="-C .. O=$PWD" > > if test -e %_sourcedir/TOLERATE-UNKNOWN-NEW-CONFIG-OPTIONS; then > > yes '' | make oldconfig $MAKE_ARGS $KERN_DIRS > > else > > cp -v .config .config.orig > > > > ###########add reiser4 params to config > > /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i > > zreiser4parameters.txt` >> .config > > #########add repser4 params to config > > #cat zreiser4parameters.txt > > #CONFIG_REISER4_DEBUG=n > > #CONFIG_REISER4_FS=m > > ######### > > > > > > # > > From last build log: > > [ 43s] '.config' -> '.config.orig' > > [ 43s] ++ /usr/bin/find /home/abuild/rpmbuild/BUILD/. > > [ 43s] ++ grep -i zreiser4parameters.txt > > [ 43s] + /bin/cat > > [ 43s] + make silentoldconfig -j6 -C .. > > O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj > > [ 43s] make: Entering directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' > > [ 43s] make[1]: Entering directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' > > [ 43s] GEN ./Makefile > > [ 43s] HOSTCC scripts/basic/fixdep > > [ 44s] HOSTCC scripts/kconfig/conf.o > > [ 44s] SHIPPED scripts/kconfig/zconf.tab.c > > [ 44s] SHIPPED scripts/kconfig/zconf.lex.c > > [ 44s] SHIPPED scripts/kconfig/zconf.hash.c > > [ 44s] HOSTCC scripts/kconfig/zconf.tab.o > > [ 47s] HOSTLD scripts/kconfig/conf > > [ 47s] scripts/kconfig/conf --silentoldconfig Kconfig > > [ 47s] * > > [ 47s] * Restart config... > > [ 47s] * > > [ 47s] * > > [ 47s] * File systems > > [ 47s] * > > [ 47s] Second extended fs support (EXT2_FS) [N/m/y/?] n > > [ 47s] The Extended 3 (ext3) filesystem (EXT3_FS) [N/m/y/?] n > > [ 47s] The Extended 4 (ext4) filesystem (EXT4_FS) [Y/n/m/?] y > > [ 47s] Use ext4 for ext2 file systems (EXT4_USE_FOR_EXT2) [Y/n/?] y > > [ 47s] Ext4 POSIX Access Control Lists (EXT4_FS_POSIX_ACL) [Y/n/?] y > > [ 47s] Ext4 Security Labels (EXT4_FS_SECURITY) [Y/n/?] y > > [ 47s] Ext4 Encryption (EXT4_ENCRYPTION) [Y/n/?] y > > [ 47s] EXT4 debugging support (EXT4_DEBUG) [N/y/?] n > > [ 47s] JBD2 (ext4) debugging support (JBD2_DEBUG) [N/y/?] n > > [ 47s] Reiser4 (EXPERIMENTAL) (REISER4_FS) [N/m/y/?] (NEW) aborted! > > [ 47s] > > [ 47s] Console input/output is redirected. Run 'make oldconfig' to > > update configuration. > > [ 47s] > > [ 47s] make[2]: *** [silentoldconfig] Error 1 > > [ 47s] make[1]: *** [silentoldconfig] Error 2 > > [ 47s] make[1]: Leaving directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' > > [ 47s] make: *** [sub-make] Error 2 > > [ 47s] make: Leaving directory > > `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' > > [ 47s] error: Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) > > [ 47s] > > [ 47s] > > [ 47s] RPM build errors: > > [ 47s] Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) > > [ 47s] > > [ 47s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:40 > > UTC 2017. > > [ 47s] > > [ 47s] ### VM INTERACTION START ### > > [ 52s] [ 45.550906] reboot: Power down > > [ 52s] ### VM INTERACTION END ### > > [ 52s] > > [ 52s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:45 > > UTC 2017. > > > -- > To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org > -- 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] What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process.
by doiggl＠velocitynet.com.au 07 Oct '17

07 Oct '17

Hello. What reiser4 parameters do I to append to .config to enable the reiser4-for-4.13.0.patch in kernel build process. The reiser4-for-4.13.0.patch applies to kernel ok. Build Log shows: + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-for-4.13.0.patch I put 'reiser4' parameters in zreiser4parameters.txt and it gets appended that to .config I just trigger rebuild process. Thanks for your expertise. --Glenn # project info, patch and log urls: :project # https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla spec: # https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… :apply reiser4 patch # https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… :reiser4 parameters used added to: zreiser4parameters.txt CONFIG_DEBUG_INFO_REDUCED=n CONFIG_DEBUG_INFO_SPLIT=n CONFIG_FRAME_POINTER_UNWINDER=n CONFIG_GDB_SCRIPTS=n CONFIG_REISER4_DEBUG=n CONFIG_REISER4_FS=m CONFIG_SUSE_KERNEL_SUPPORTED=y #add reiser4 parameters to .config line , from spec file: /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i zreiser4parameters.txt` >> .config :build log # https://build.opensuse.org/public/build/home:doiggl/openSUSE_Leap_42.3/x86_… # Steps done in specfile: ---------------------- KERN_DIRS="-C .. O=$PWD" if test -e %_sourcedir/TOLERATE-UNKNOWN-NEW-CONFIG-OPTIONS; then yes '' | make oldconfig $MAKE_ARGS $KERN_DIRS else cp -v .config .config.orig ###########add reiser4 params to config /bin/cat `/usr/bin/find /home/abuild/rpmbuild/BUILD/. | grep -i zreiser4parameters.txt` >> .config #########add repser4 params to config #cat zreiser4parameters.txt #CONFIG_REISER4_DEBUG=n #CONFIG_REISER4_FS=m ######### # >From last build log: [ 43s] '.config' -> '.config.orig' [ 43s] ++ /usr/bin/find /home/abuild/rpmbuild/BUILD/. [ 43s] ++ grep -i zreiser4parameters.txt [ 43s] + /bin/cat [ 43s] + make silentoldconfig -j6 -C .. O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj [ 43s] make: Entering directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' [ 43s] make[1]: Entering directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' [ 43s] GEN ./Makefile [ 43s] HOSTCC scripts/basic/fixdep [ 44s] HOSTCC scripts/kconfig/conf.o [ 44s] SHIPPED scripts/kconfig/zconf.tab.c [ 44s] SHIPPED scripts/kconfig/zconf.lex.c [ 44s] SHIPPED scripts/kconfig/zconf.hash.c [ 44s] HOSTCC scripts/kconfig/zconf.tab.o [ 47s] HOSTLD scripts/kconfig/conf [ 47s] scripts/kconfig/conf --silentoldconfig Kconfig [ 47s] * [ 47s] * Restart config... [ 47s] * [ 47s] * [ 47s] * File systems [ 47s] * [ 47s] Second extended fs support (EXT2_FS) [N/m/y/?] n [ 47s] The Extended 3 (ext3) filesystem (EXT3_FS) [N/m/y/?] n [ 47s] The Extended 4 (ext4) filesystem (EXT4_FS) [Y/n/m/?] y [ 47s] Use ext4 for ext2 file systems (EXT4_USE_FOR_EXT2) [Y/n/?] y [ 47s] Ext4 POSIX Access Control Lists (EXT4_FS_POSIX_ACL) [Y/n/?] y [ 47s] Ext4 Security Labels (EXT4_FS_SECURITY) [Y/n/?] y [ 47s] Ext4 Encryption (EXT4_ENCRYPTION) [Y/n/?] y [ 47s] EXT4 debugging support (EXT4_DEBUG) [N/y/?] n [ 47s] JBD2 (ext4) debugging support (JBD2_DEBUG) [N/y/?] n [ 47s] Reiser4 (EXPERIMENTAL) (REISER4_FS) [N/m/y/?] (NEW) aborted! [ 47s] [ 47s] Console input/output is redirected. Run 'make oldconfig' to update configuration. [ 47s] [ 47s] make[2]: *** [silentoldconfig] Error 1 [ 47s] make[1]: *** [silentoldconfig] Error 2 [ 47s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13/linux-obj' [ 47s] make: *** [sub-make] Error 2 [ 47s] make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.13.5/linux-4.13' [ 47s] error: Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) [ 47s] [ 47s] [ 47s] RPM build errors: [ 47s] Bad exit status from /var/tmp/rpm-tmp.Ps4R3M (%prep) [ 47s] [ 47s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:40 UTC 2017. [ 47s] [ 47s] ### VM INTERACTION START ### [ 52s] [ 45.550906] reboot: Power down [ 52s] ### VM INTERACTION END ### [ 52s] [ 52s] lamb77 failed "build kernel-vanilla.spec" at Sat Oct 7 06:06:45 UTC 2017. -- 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] factory-auto declines deletion request of linked package
by Michal Srb 06 Oct '17

06 Oct '17

Hi, I am trying to request deletion of openSUSE:Factory/lldb4 which is a link to openSUSE:Factory/llvm4. It was there because llvm4 was multispec package with llvm4.spec and lldb4.spec files in it, but since sr#532127 it won't be anymore. The original packages from lldb4.spec will be subpackages in llvm4.spec. The request is automatically declined with following message: "This is an incorrect request, it's a linked package to openSUSE:Factory/ llvm4" Why is that a reason to decline the request? Is there some other way to delete linked packages? Thanks, 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 1