June 2013 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] peazip bug report
by Sérgio Basto 10 Jun '13

10 Jun '13

On Sáb, 2013-06-08 at 17:29 +0200, Jan Engelhardt wrote: > On Saturday 2013-06-08 17:04, Sérgio Basto wrote: > > >> >yum --enablerepo=home_zhonghuaren update > >> >(...) > >> >Updated: > >> > libcaca.x86_64 0:0.99.beta18-13.1 peazip.x86_64 0:4.9.2-2.1 > >> >po-debconf.noarch 0:1.0.16-4.1 > >> > > >> >peazip > >> >[FORMS.PP] ExceptionOccurred > >> > Sender=EReadError > >> > Exception=Error reading mback.ShortCutKey2: Unknown property: > >> >"ShortCutKey2" > >> > Stack trace: > >> > > >> >but with same src.rpm built on fedora with mock runs without errors , > >> >and works pretty well. > >> > >> As you can see, that is a _YUM_ problem, not a building problem. > > > >No, is a binary problem, after yum install or update peazip, the binary > >works different (with errors) build on OBS , is not supposed to work on > >Fedora 18 ? > > > http://code.google.com/p/peazip/issues/detail?id=230 I diff [1] my build and opensuse build and just see this difference : -NOTE: miscellaneous options file not found - using defaults +primary config path: /builddir/.lazarus ls /var/lib/mock/fedora-18-x86_64/root/builddir/ -a . .. .bash_logout .bash_profile .bashrc build .lazarus .rpmmacros ls /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/ -a . .. compilertest.pas environmentoptions.xml cat /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/environmentoptions.xml [2] [1] wget "https://build.opensuse.org/package/rawlog?arch=x86_64&package=peazip&projec…" -O build.log cat build.log | perl -pe 's/\[.*?\] //' > build2.log diff build2.log /var/lib/mock/fedora-18-x86_64/result/build.log -ubBw > diffbuild.txt http://www.serjux.com/diffbuild.txt [2] <?xml version="1.0"?> <CONFIG> <EnvironmentOptions> <Version Value="107" Lazarus="1.0.4"/> <LazarusDirectory Value="/usr/lib64/lazarus"> <History Count="1"> <Item1 Value="/usr/lib/lazarus/"/> </History> </LazarusDirectory> <CompilerFilename Value="/usr/bin/fpc"> <History Count="3"> <Item1 Value="/usr/local/bin/fpc"/> <Item2 Value="/usr/bin/fpc"/> <Item3 Value="/opt/fpc/fpc"/> </History> </CompilerFilename> <FPCSourceDirectory Value="/usr/share/fpcsrc"> <History Count="2"> <Item1 Value="/usr/share/fpcsrc/"/> <Item2 Value="/usr/share/fpcsrc/$(FPCVER)/"/> </History> </FPCSourceDirectory> <MakeFilename> <History Count="1"> <Item1 Value="/usr/bin/make"/> </History> </MakeFilename> <TestBuildDirectory Value="/tmp/"> <History Count="2"> <Item1 Value="/tmp/"/> <Item2 Value="/var/tmp/"/> </History> </TestBuildDirectory> </EnvironmentOptions> </CONFIG> -- Sérgio M. B. -- 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] How to add trees?
by Michael Lindner 10 Jun '13

10 Jun '13

Hi, # osc add * says "skipping directory 'build' " What is the command to add an entire tree? Also can see "add file" but not "add directory" on web interface. Thanks, Michael. -- 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] Submit raw package with _link
by Jan Engelhardt 10 Jun '13

10 Jun '13

Once upon a time (around OBS 1.x/2.0?), it was possible to submit packages that only had a _link file in it. Given home:prj/pkg/_link existed and home:prj/pkg was submitted to devel:foo, there would be, after accepting such SR, a devel:foo/pkg/_link. In the current OBS however, _link files are always expanded such that after acceptance of the SR, devel:foo/pkg/pkg.spec would exist and devel:foo/pkg/_link would not. Without the use of an external communications channel such as email or the message field of a submit requests, how do you submit packages with _links in it? If not, the feature should be restored somehow. Even Factory is said to have some mechanism by now to automatically(?) create respective _link packages when there are multiple .spec files seen. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

Re: [opensuse-buildservice] How to add repository to local OBS instance
by Adrian Schröter 10 Jun '13

10 Jun '13

Am Freitag, 7. Juni 2013, 22:52:28 schrieb Stefan Cocora: > Hi Adrian, > > A couple of questions inline to clarify what I have to do: > > On 28/05/13 09:00, Adrian Schröter wrote: > > On Montag, 27. Mai 2013, 17:15:33 wrote Stefan Cocora: > >> Thanks for your response Philipp, > >> > >> To confirm, yes my local instance is connected to opensuse.org > >> Can I have my local obs connected with opensuse.org and at the same > >> > >> time create another project that tracks packages locally ? > >> > >> I'm not sure I understand what you mean by "If you want to hold the > >> > >> project including the packages locally". > >> > >> Doesn't creating another project and adding rpm/deb manually mean that > >> > >> I'm holding the packages and and the project locally ? > > > > If you want to binary import some packages, create some repo somewhere via > > osc or webui. Ideally in an empty project without sourceshe > > > > Afterwards, you can create the :full directory in > > > > /srv/obs/build/$project/$repo/$arch/:full > > > > and copy your binaries inside. Last, you need to tell the scheduler to > > scan it via > > > > obs_admin --rescan-repository <project> <repository> <architecture> > > > > If this new repo has the Ubuntu repo inside it's path, it is enough to > > build against your new repo in your projects. > > Let's see if I understand this correctly: - create a project with the desired repository > - I've created > /srv/obs/build/home\:stefan\:localubuntu/xUbuntu_13.04/x86_64/\:full on > the obsserver yes > - I do a osc co of home\:stefan\:localubuntu on my laptop > - I add miro as a package inside this project + osc add and commit no, you should not create packages or build in that project. It will work, but you will always have the problem to sort out what is injected and what not. > - do I run rescan-repository after adding the miro packages ? just copy the binaries you want to inject into that :full directory and run the rescan. > - Where should I add the ubuntu repo ? "If this new repo has the Ubuntu > repo inside it's path..." If your home:stefna:localubuntu/xUbuntu_13.04 repo has a path pointing to the standard Ubuntu:13.04/standard repo, you can use your repo in other projects as path. It will get packages from both projects, but prefer the packages from your :localubuntu > >> Regards, > >> Stefan > >> > >> On 27/05/13 11:38, Philipp Seiler wrote: > >>> Hi Stefan, > >>> > >>> On Sun, 26 May 2013 09:05:57 +0100 > >>> > >>> Stefan Cocora <stefan.cocora(a)googlemail.com> wrote: > >>>> Hi all, > >>>> > >>>> I'm trying to build miro 6 for ubuntu 12.04 ubuntu 13.04 using my > >>>> > >>>> self hosted version of OBS. > >>>> > >>>> My self hosted version of OBS is 2.3.8. > >>>> > >>>> The problem with miro is that it needs python-support which exists > >>>> > >>>> only in the ubuntu universe repositories. > >>>> > >>>> Reading the opensuse buildservice mailing list I saw that you can't > >>>> > >>>> add ubuntu's universe to opensuse because of legal issues. > >>>> > >>>> How can I add ubuntu universe to my self-hosted version of OBS ? > >>> > >>> You interconnect your self-hosted OBS with the SUSE one, right? > >>> In this case you can't add RPMs to the repository because the > >>> rpms are directly downloaded from the SUSE OBS. I can provide you one > >>> (not the only?) solution. You create a project in your instance with > >>> prj information, prjconf and the packages > >>> in /srv/obs/build/$DISTRO/$ARCH/:full/ to build without the suse OBS > >>> interconnect. Here you can add the rpms/debs you wish. Maybe the most > >>> from an Install DVD and the additional packages from a repository (for > >>> ubuntu the universe repository). But you need a bit free space per > >>> distro. For example for Ubuntu you need about 10GB space (all > >>> packages twice for i586 and x86_64 arch). > >>> > >>> If you want to hold the project including the packages locally, I'll > >>> answer you with the steps to do that. > >>> > >>> Regards, > >>> > >>> Philipp > > Regards, > Stefan -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Different invocation of service run act differently
by Jan Engelhardt 10 Jun '13

10 Jun '13

To do verification of the raw tarball, I have, in a _service file, <services> <service name="recompress"> <param name="file">*.tar*</param> <param name="compression">none</param> </service> <service name="verify_file"> <param name="file">_service:recompress:Alnuth-3.0.0.tar</param> <param name="verifier">sha256</param> <param name="checksum">7203be33535135af16ba1a1479b057ec5fe4048c628d6d9bd2926824a017b477</param> </service> <service name="recompress"> <param name="file">*.tar*</param> <param name="compression">xz</param> </service> </services> using this, the package builds on the server-side, but only there. When issuing a localrun, I get Compressed Alnuth-3.0.0.tar to Alnuth-3.0.0.tar sha256sum: _service:recompress:Alnuth-3.0.0.tar: No such file or directory Aborting: service call failed: /usr/lib/obs/service/verify_file --file '_service:recompress:Alnuth-3.0.0.tar' --verifier 'sha256' --checksum '7203be33535135af16ba1a1479b057ec5fe4048c628d6d9bd2926824a017b477' --outdir /tmp/tmphm40jp Instead of <param name="file">_service:recompress:Alnuth-3.0.0.tar</param> I could place <param name="file">Alnuth-3.0.0.tar</param> in the _service file, but then it only works locally and not on the server side. Looks like a bug to me.. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] How do I change my password on build.opensuse.org
by Greg Freemyer 10 Jun '13

10 Jun '13

All, I've tried to change it and now my Novell account has a new password: But my build.opensuse.org account still uses the old password. My process was to log into OBS, then go to my home page: https://build.opensuse.org/home Then I clicked on edit my account and updated the password. Apparently the "account" I updated was not the one used by OBS to authenticate my login. This is what now requires the new password to access: https://secure-www.novell.com/selfreg/jsp/protected/manageAccount.jsp Thanks Greg -- 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] How to add repository to local OBS instance
by Stefan Cocora 09 Jun '13

09 Jun '13

Hi all, I'm trying to build miro 6 for ubuntu 12.04 ubuntu 13.04 using my self hosted version of OBS. My self hosted version of OBS is 2.3.8. The problem with miro is that it needs python-support which exists only in the ubuntu universe repositories. Reading the opensuse buildservice mailing list I saw that you can't add ubuntu's universe to opensuse because of legal issues. How can I add ubuntu universe to my self-hosted version of OBS ? Regards, Stefan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] peazip bug report
by Sérgio Basto 08 Jun '13

08 Jun '13

Hi, I build last peazip for Fedora https://build.opensuse.org/package/show?package=peazip&project=home% 3Azhonghuaren the source works when build in and with Fedora 18 and build with mock , but doesn't work when build in OBS. Any ideas ? the builder use Fedora package for Build requires ? Thanks, -- Sérgio M. B. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] How do I complete a osc ci * command
by doiggl＠velocitynet.com.au 07 Jun '13

07 Jun '13

Hello, How do I complete a osc ci * command <it goes vi what do i do next> Thanks Glenn Commands done so far: # osc add * A 00-base.conf A 00-dav.confd. . . # osc st ? httpd.sysconf ? httpd.tmpfiles ? index.html ? manual.conf ? ssl.conf ? userdir.conf ? welcome.conf ? zextract.log A 00-base.conf A 00-dav.conf A 00-lua.conf . . # osc ci * <it goes into vi> --This line, and those below, will be ignored-- A 00-base.conf A 00-dav.conf A 00-lua.conf <SHIFT ZZ> <I quit vi and selected abort> Log message not specified a)bort, c)ontinue, e)dit:a -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Still trying to find a solution when a package depends on universe ubuntu repository
by Gianluca Emme 07 Jun '13

07 Jun '13

Dear All, I'm still struggling to find a solution to build my package that depends for building on others packages that are in the universe ubuntu repository. So, again, I'm desperately asking a feasible solution to any other users encounter my same problem... and also, I'm wondering if the administrations may take in consideration to include the universe repository. This is a short summary of my adventure :-) : - I'm building a package named yarp that depends on libace - libace is into the universe ubuntu repository - universe ubuntu repository is not included into the OBS service - I'm trying to find a way to fullfill the dependency to build my package - the solution I tryied are: 1) download the source package of libace, build it into the OBS without publish it 2) try to fullfill the dependency taking the package from the Debian repository (where libace is into the standard repository) 3) try to install the .deb binary package during the execution of debian.rules before the build All these solution failed for the following reasons: 1) the source package of libace generate about 20 binary packages and then for building it depends on other about 20 dev package and some of those are in the universe repository too !! This imply that I have to recursevily download a lot of source package and rebuild them into the OBS. That's absolutely silly and unfeasible 2) Debian and Ubuntu are incompatibles :-( 3) The dpkg command needs root access to install a .deb package even if I set the --root-dir to the home build directory Do you have in mind some other solution I can try ?? Thanks, Gianluca. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 10