May 2015 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] packages used to build
by Wolfgang Rosenauer 18 May '15

18 May '15

Hi, misleading subject but I'm currently facing something unexpected. I'm building a project against openSUSE:Evergreen:11.4 but it gets the "wrong" openssl version. I need to build against the openssl currently there: # osc ls openSUSE:Evergreen:11.4 openssl ... openssl-1.0.1k.tar.gz ... but the project installs an older one (seems like something also only in openSUSE:Evergreen:11.4 but still older. Is there a cache issue or has it to do with the latest patch being "optional"? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 12

[opensuse-buildservice] osc flushing stdout
by Volker Kuhlmann 17 May '15

17 May '15

Is there a way to force osc to keep flushing stdout, even if it thinks output is not to a terminal? I need to log osc operations that I've been doing so I can see again later who I got into a certain state. Years ago I wrote a wrapper script for such purpose. It basically is <cmd> | tee -a, and I don't know how else to divert program output into a log file. Unfortunately the piping makes osc think it is no longer outputting stdout to a terminal, buffering large chunks first script is not suitable in many ways, one of them being the unreadable output it creates. Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 9

[opensuse-buildservice] osc up impossible
by Volker Kuhlmann 17 May '15

17 May '15

cd ~/osc/devel:ARM:13.2:Contrib:Allwinner osc up Your working copy './kernel-default' is in an inconsistent state. Please run 'osc repairwc ./kernel-default' (Note this might _remove_ files from the .osc/ dir). Please check the state of the working copy afterwards (via 'osc status ./kernel-default') osc repairwc ./kernel-default done. Please check the state of the wc (via 'osc status ./kernel-default'). osc st kernel-default ? kernel-default/README.KSYMS ... osc up resuming broken update... failed to add file 'README.KSYMS' file/dir with the same name already exists osc up kernel-default resuming broken update... failed to add file 'README.KSYMS' file/dir with the same name already exists osc co kernel-default error: './kernel-default' is already an initialized osc working copy osc repairwc kernel-default osc: working copy 'kernel-default' is not inconsistent osc-0.151.2-11.1.noarch So osc can't fix it, check it out, or update it. How do I fix it? Is there any kind of test mode for osc up, so I can check how it proposes to wreck my local copy before actually doing so? The above problem likely resulted from hitting ^C on osc up because it insisted on downloading far more stuff then I needed at the time, at snail's pace when I was doing other work. Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] source_validator causes commit to fail (baselibs.conf)
by Lars Müller 15 May '15

15 May '15

Hi, home:lmuelle:bnc906336/samba.openSUSE_13.1_Update and home:lmuelle:bnc906336/samba.openSUSE_13.2_Update both have the identical baselibs.conf as it is used at network:samba:STABLE/samba or network:samba:MAINTAINED:SLE_12/samba While it was possible to commit to network:samba:STABLE/samba both home:lmuelle:bnc906336/samba.openSUSE_13.*_Update projects don't accept the same commit. While calling osc commit I get: ###ASK /home/lmuelle/opensuse/home:lmuelle:bnc906336/samba.openSUSE_13.1_Update/baselibs.conf - package has samba-client-rpmlintrc: (unchanged) ERROR: '#' referenced in baselibs.conf is not being built ERROR: 'The' referenced in baselibs.conf is not being built ERROR: 'next' referenced in baselibs.conf is not being built ERROR: 'line' referenced in baselibs.conf is not being built ERROR: 'is' referenced in baselibs.conf is not being built ERROR: 'required' referenced in baselibs.conf is not being built ERROR: 'for' referenced in baselibs.conf is not being built ERROR: 'pre-11.0' referenced in baselibs.conf is not being built ERROR: 'builds' referenced in baselibs.conf is not being built ERROR: 'of' referenced in baselibs.conf is not being built ERROR: 'libsmbclient' referenced in baselibs.conf is not being built ERROR: 'libsmbclient' referenced in baselibs.conf is not being built Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpZ6mSdL A service failed with error: 1 Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

4 7

[opensuse-buildservice] i586 packages cannot be published?
by Erico Mendonca 15 May '15

15 May '15

Hello all, Could someone take a look at the package https://build.opensuse.org/package/show/home:wellingtonsilva67/SSSD ? It simply won't publish the i586 binaries even after successfully building them, with the reason "no build possible atm, waiting for jobs in other repositories". Apparently it's been stuck like that for months, even deleting the binaries and rebuilding them again won't work. Perhaps deleting the status files for this would solve the problem? SUSE Erico Mendonça Dedicated Support Engineer (Work)+55 (61) 8594-9557 (Main) +55 (11) 3345-3900 (Personal) +55 (61) 9115-3256 emendonca(a)suse.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] tar_scm and package-meta
by Nathan Cutler 14 May '15

14 May '15

O, OBS gurus: We have a software project in OBS that is using the tar_scm service to generate the tarball from a git repo. Upstream is setting the version number at build time by peeking into the .git directory, so we need to somehow include this directory in the tarball. We tried adding "<param name="package-meta">yes</param>" to the tar_scm XML, and happily I can confirm that this does cause the .git directory to be included in the .tar file. However, after tar_scm completes a glitch occurs: $ osc service dr Cloning into '/tmp/tmpuckA4K/tmpAPx9Ds/ceph'... warning: unable to rmdir src/gmock: Directory not empty HEAD is now at 5ce51ae use same systemd service files for all cluster names. Cleaning: /tmp/tmpuckA4K/tmpAPx9Ds /tmp/tmpuckA4K/ceph-20150511 Compressed ceph-20150511.tar to ceph-20150511.tar.xz rm: remove write-protected regular file ‘/tmp/tmp.aXC3yLlqPE/new/ceph-20150511/.git/modules/ceph-object-corpus/objects/pack/pack-e7789f402323bf1bf59b325bc9c126663c9dc632.idx’? It appears that *something* (not tar_scm) is calling rm -r without -f . . . Any ideas? Nathan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Building for Debian modifies binary file by adding a newline
by Timotheus Pokorra 13 May '15

13 May '15

Hello, At Kolab, we have a problem building a package for php composer. We want to add a binary file (inside the debian.tar.gz). The file is called composer.phar and starts like a php file, but actually is a binary file. Somehow, OBS will add a newline character to the file, which causes a new md5sum for the file. We have reproduced it on the public OBS: https://build.opensuse.org/package/live_build_log/home:tpokorra:kolab/compo… with some debugging in debian.rules, printing the md5sum before and after our current fix. Here is the discussion on the Kolab Devel list: http://lists.kolab.org/pipermail/devel/2015-May/015309.html I have built the package outside of OBS for testing, and it does not modify the file there. We are wondering what step in the OBS causes this, and if we can do a clean workaround, rather than cutting off the newline inside debian.rules again which seems a bit akward. We are wondering about debian transform: https://github.com/openSUSE/obs-build/blob/master/debtransform but cannot find the place that would cause this. Thank you for any insight, Timotheus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] boxes repository
by Eric Jackson 12 May '15

12 May '15

Hello, I am trying to create a project to have OBS generate Vagrant boxes from a kiwi configuration. I am using this as an example: https://build.suse.de/project/repositories/Devel:Cloud:Shared:11-SP3:Update… When I add repositories and select "Kiwi Image builds", I get a repository named "images" and not boxes. How do I add the repository "boxes"? Thanks, Eric

2 1

[opensuse-buildservice] osc bco : "if nothing else specified"
by Karl Eichwalder 12 May '15

12 May '15

I'm using version 0.151. I do not understand what this means: The branched package will live in home:USERNAME:branches:PROJECT/PACKAGE if nothing else specified. For example, the release-notes-sles has 2 .spec files, and a plain 'bco' sometimes copies to home:USERNAME:branches:PROJECT/release-notes-sles, but more often to home:USERNAME:branches:PROJECT/release-notes-SLES-for-VMware (this is the name of the other .spec file). To avoid this, I tried: osc -A https://api.suse.de bco SUSE:SLE-11-SP4:GA release-notes-sles \ home:keichwa:branches:SUSE:SLE-11-SP4:GA release-notes-sles With the intention that it would always copy to home:keichwa:branches:SUSE:SLE-11-SP4:GA/release-notes-sles Unfortunately, it does not. Any hints? -- Karl Eichwalder SUSE Linux GmbH R&D / Documentation Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] submitting a _link
by Olaf Hering 12 May '15

12 May '15

In packman its often requested create a new package which just links back to OBS. But the SR would always expand the _link in the destination project, so the actual content and intent is lost. What has to be done to copy the pkg contents as is from source prj to destination prj via a submit request? Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 18