April 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Strange issue with failing inter project dependencies
by Hans-Peter Jansen 14 Apr '11

14 Apr '11

Dear OBS aficionados, I suffer from a strange build failure, where packages from other projects aren't found, although they exist and were published already. Offending package: python-dip, build for openSUSE_11.2 https://build.opensuse.org/package/show?package=python-dip&project=home%3Af… This depends on python-sphinx, which seems missing for 11.2, and this depends on python-jinja2 and python-pygments. Since I've build these packages for the outphased 11.1 anyway, I've enabled build for 11.2, too. https://build.opensuse.org/package/show?package=python-sphinx&project=home%… https://build.opensuse.org/package/show?package=python-jinja2&project=home%… https://build.opensuse.org/package/show?package=python-pygments&project=hom… Neither of these packages nor the projects have further constraints defined, they enable debug, and the latter two enable build of the 11.1 and 11.2. Especially, they don't play any games with the usedforbuild flags, as this has bitten me before. The home:frispete:python has the openSUSE_11.2 target defined as: <repository name="openSUSE_11.2"> <path repository="openSUSE_11.2" project="home:frispete:database"/> <path repository="openSUSE_11.2" project="devel:languages:python"/> <path repository="standard" project="openSUSE:11.2:Update"/> <arch>i586</arch> <arch>x86_64</arch> </repository> The home:frispete:PyQt-next has the openSUSE_11.2 target defined as: <repository name="openSUSE_11.2"> <path repository="openSUSE_11.2" project="home:frispete:python"/> <path repository="standard" project="openSUSE:11.2:Update"/> <arch>i586</arch> <arch>x86_64</arch> </repository> But both, local and BS build attempts lead to: buildinfo is broken... it says: unresolvable: nothing provides python-jinja2 needed by python-sphinx, nothing provides python-pygments needed by python-sphinx They question is, why can't build locate these packages, although they exist and are referenced properly, aren't they? TIA, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] .oscignore to ignore tarballs downloaded by source service?
by Michal Marek 14 Apr '11

14 Apr '11

Hi, I see there is no way to set ignore patterns on a per-package basis, i.e. some .oscignore or rather _oscignore file. Would you accept a patch that adds such feature? The problem I'm trying to solve is following: The kernel-source package is maintained in a git repository and a script exists to generate a source package that can be built using rpmbuild, osc build or the buildservice. To avoid having to upload the 70M+ linux tarball each time you branch the package in the buildservice, I would like to use the download_url service to let the server download it. But at the same time, I would like to have the tarball locally as before, so that plain rpmbuild works. But then I need to tell osc to ignore the linux tarball and avoid messages like this: $ osc ci File "linux-2.6.38.tar.bz2" is listed in package meta but does not exist. (s)kip/(r)emove/(e)dit file lists/(c)ommit/(A)bort? I *could* save the tarball as "_service:download_url:linux-2.6.38.tar.bz2", which osc properly ignores, and handle such filename in the %prep section, but that would be really hackish. Being able to just do echo "linux-$version.tar.bz2" >kernel-source/_oscignore when generating the source package would be much cleaner. Thanks, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Is there any integration/system test for OBS?
by victor.liu＠nokia.com 13 Apr '11

13 Apr '11

Hello, We're setting up a private OBS instance for our production build system, it will be nice to get running some Integration/system test cases to verify our OBS installation or any further possible upgrade. But we can just find some unit/functional test cases at: http://en.opensuse.org//openSUSE:Build_Service_Testsuite. Is there any integration/system test cases available? What's the way to make integration/system testing before releasing each OBS release? Thanks Victor -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] unable to submit maintenance update - multiple source changes
by Petr Mladek 13 Apr '11

13 Apr '11

Hi, I have troubles to submit packages for LO maintenance update from the project home:pmladek:openSUSE-11.4. I get the following error: --- cut --- $:/home/pmladek/bs/home:pmladek:openSUSE-11.4> osc sr Submitting package libreoffice-languagetool Submitting package libreoffice-libs-gui Submitting patchinfo _patchinfo:libreoffice_input_method_and_grammar to openSUSE:11.4:Update:Test, openSUSE:11.4:Update:Test Everything fine? Can we create the requests ? [y/n] y Server returned an error: HTTP Error 400: Bad Request <status code="400"> <summary>request contains multiple source changes for package &quot;_patchinfo:libreoffice_input_method_and_grammar&quot;</summary> </status> --- cut --- Do you have any idea what the message means and how to fix it, please? Best Regards, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Why isn't a public download of the tarball in openCOLLADA possible?
by Dave Plater 13 Apr '11

13 Apr '11

I'm collaborating on the blender and more significantly openCOLLADA needed by blender and created by me as a shared library build from svn the only place it's available. The Fedora people are asking for a url for the source which atm the Fedora packager retrieves from the source rpm. Why are all the sources of the package available for download in the web ui except the tarball? I've also seen a few differences in what Fedora requires and the openSUSE Fedora build. Devel = graphics openCOLLADA or home:plater:blender openCOLLADA which has Fedora builds as well. Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH] checkout git branch with tar_scm source servce
by Will Stephenson 12 Apr '11

12 Apr '11

The following patch enables tar_scm to checkout a specified git branch instead of HEAD. For svn, the option is meaningless as the branch is part of the URL. I don't know anything about Hg, so can't say if the option is used there. For now I have marked it (git only). Any comments? Where is tar_scm's source repo so I can submit it there? Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 18

[opensuse-buildservice] Moving packages...
by Ciro Iriarte 12 Apr '11

12 Apr '11

Hi, any quick tip to move packages between projects?, can I branch a package and delete it from "upstream"?, any better approach? Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] OBS 2.2.72 alpha release, bigger changes ...
by Adrian Schröter 12 Apr '11

12 Apr '11

We are pushing out a new OBS 2.3 alpha release right now. This one has some significant changes due to the switch to apache. The appliance users should be able to just replace their appliance. If you use packages you need to read the README files. While the new setup works much better for me, I would like to hear some feedback. Esp. about update problems. You can find some more background information in my blog: http://monarchieundalltag.wordpress.com/2011/04/12/obs-2-2-72-released-swit… bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] Moving packages...
by Ciro Iriarte 12 Apr '11

12 Apr '11

2011/4/11 Dominique Leuenberger <dominique(a)leuenberger.net>: > On Mon, 2011-04-11 at 16:58 -0400, Ciro Iriarte wrote: >> Hi, any quick tip to move packages between projects?, can I branch a >> package and delete it from "upstream"?, any better approach? > > osc copypac > > branching will create a link in the destination project and if you then > delete the source, you end up with a broken link. > > Dominique > > Thanks a lot to everyone that answered.. Regard, CI.- -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Fwd: [opensuse-buildservice] Moving packages...
by Enrico Pilz 11 Apr '11

11 Apr '11

2011/4/11 Ciro Iriarte <cyruspy(a)gmail.com> > > Hi, any quick tip to move packages between projects?, can I branch a > package and delete it from "upstream"?, any better approach? Interesting question. Me looks in the help, only plausible candidate is 'mv' - what does it? $ osc help mv mv: Move SOURCE file to DEST and keep it under version control Usage: osc mv SOURCE DEST Options: -h, --help show this help message and exit -f, --force forces removal of entire package and its files Are SOURCE and DEST projects? Is this like the mv in git? Enrico > > Regards, > > -- > Ciro Iriarte > http://cyruspy.wordpress.com > -- > -- > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1