May 2014 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] enabling networking for workers
by Darin Perusich 19 Dec '17

19 Dec '17

Hello All, I'm running a private instance and I'd like to enable networking on my workers so they can build some java apps, via maven, which need to download pom's/war's from the net. I ask google but he wasn't much help so I'm hoping someone here can help;-) How can I go about doing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 10

[opensuse-buildservice] Ghost package
by trcs＠gmx.com 14 Dec '15

14 Dec '15

Hi. There is a ghost package in my OBS home project. I'm using the web interface, not the command line one. If you go to https://build.opensuse.org/project/show/home:jcsl:LXDE you can see the real 10 packages in the Packages box on left side, but if you look in the Build Results box, on the right side, you see 11 next to the "succeeded" text. If you then click the succeeded link you find the pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package "pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It even appears in the scheduled and building states when something I'm building triggers its build (I don't know how can this be). Any hints? Greetings. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

Re: [opensuse-buildservice] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] choice for libxml2
by Eric Schirra 02 Jun '14

02 Jun '14

Hello, i have in some package an unresolved error: have choice for libxml2.so.2(LIBXML2_2.5.2) needed by ???: libxml2-2-32bit libxml2-2 Please can somebody fix this in obs? Eric -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 9

[opensuse-buildservice] Old SUSE logo on http://openbuildservice.org/
by Gerald Pfeifer 02 Jun '14

02 Jun '14

Hi guys, I noticed that http://openbuildservice.org/ carries an the SUSE logo in the "Select Your Operating System" banner. Mind using the current one (that has all letters of the same size and in black)? Thanks, Gerald -- Dr. Gerald Pfeifer <gp(a)suse.com> Sr. Director Product Management and Operations, SUSE -- 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] delete a project and packages
by Brian K. White 30 May '14

30 May '14

I branched a package by mistake in the web interface. It created a new subproject under my home project. Now I can't delete either the package or the subproject, either via the delete links in the web ui or by osc rdelete. What I tried: * On the package summary page in the web ui, https://build.opensuse.org/package/show/home:aljex:branches:utilities/byobu there is a link that says "delete package". It just returned a 500 internal server error. * On the subproject summary page in the web ui, https://build.opensuse.org/project/show/home:aljex:branches:utilities there is a link that says "delete project" It just returned a 500 internal server error. * "osc deletepac" says the command is obsolete and to use delete or rdelete. * "osc rdelete home:aljex:branches:utilities byobu" puts me in a vim editor with no explanation, but says something about a log entry when I esc:q! out of it, so I tried again and wrote "created by mistake" and esc:x , and that returns: "/tmp/osc-commitmsgYCbCUa.diff" 3L, 68C written Server returned an error: HTTP Error 500: Internal Server Error * "osc rdelete -r home:aljex:branches:utilities" does the same as above. So how do I delete this package and the subproject project it's in? In the mean time, I DO want the package in home:aljex, so I used "osc linkpac" to put a link in home:aljex without branching or copying again. That worked fine. osc linkpac home:aljex:branches:utilities byobu home:aljex Sending meta data... Done. Creating _link... Done. That's probably not a bad way to leave it for good, but I would like to know why none of the delete commands worked as advertised. -- bkw -- 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] my OBS builds rpms, but not kiwi.... need some help please.....
by rens 30 May '14

30 May '14

Hello I think I am missing something simple, but I cannot find what it is. I cannot get a simple config kiwi to build on *my* OBS. It does build on the openSUSE OBS My OBS says the repository is not available this is the repository definition of my kiwi file. I also tried with openSUSE:13.1/standard (which works on opensuse OBS) but that doesnt work either...... Any ideas ?? <repository type="rpm-md"> <source path="obs://openSUSE:12.2:Update/standard"/> </repository> <repository type="rpm-md"> <source path="obs://openSUSE:12.2:NonFree/standard"/> </repository> <repository type="rpm-md"> <source path="obs://openSUSE:12.2/standard"/> </repository> Best regards Rens -- 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] OBS Private Instance + EPEL
by Andrew Melo 29 May '14

29 May '14

Greetings, Hello all, I've been using/playing with a private OBS instance for a bit and I'm really enjoying it. Kudos to the developers! On my private instance, I'd like to build some packages with BuildRequires that only exist (in Centos/RHEL) in the EPEL repository. These packages (correctly) error out with "unresolvable". I've searched the best I can, but I can't seem to find a way to enable the EPEL repository for the centos build target. Does anyone have a suggestion for this? Thanks! Andrew -- -- Andrew Melo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 8

[opensuse-buildservice] OBS change: new build repo handling
by Michael Schroeder 29 May '14

29 May '14

Hi OBS users, after testing out the new build repository handling on the stage area for a few weeks, we've now enabled it for the home projects as well. Here is what the change is about: OBS maintains an internal repo used for building ("the :full tree"). The "useforbuild" flag can be used to configure if built packages are copied into the tree or not. The problem: ------------ The old code checked the "useforbuild" flag only after a package was successfully built. In that case, the old packages in the full tree were replaced with the new results, otherwise the full tree was not changed. This has a couple of drawbacks: - if two packages built the same binary, the last built wins. Thus, the state of the full tree depends on the timeline of the builds. This somewhat contradicts the build service goal of having reproducible builds. - if the project maintainer changes the useforbuild flag, nothing happens as the flag is only looked at the next time a build is done. This means that it's very hard to repair the effects of a bad useforbuild setting. Our solution: ------------- The new code does away with the dependency on the build timeline. This means that at any point in time the build repository can be reconstructed from the build results. This means: - there's now a fixed rule if the packages build the same binary: the package that comes lexicographical first wins. E.g. if package "A" builds "foo.rpm" and package "B" also builds "foo.rpm", the build repo will contain foo.rpm from "A". - changing "useforbuild" will have an immediate effect on the build repository. Note that the last point makes "useforbuild" semantically different from the "publish" flag. This is a little drawback, but we argue that the "publish" flag is often used to "stage" new releases, which is a bit different from "useforbuild". There's another change that was needed because of the new useforbuild handling: as we need to be able to reconstruct the build repo from the package build results, we also needed to store the build results imported from other architectures (i.e. the -32bit packages) in a different place. Before the change they went directly into the build repo, now we need to store them somewhere else. So we've decided to store them in the packages next to the other build results. E.g. if package foo builds both "foo-1.1.i586.rpm" and "foo-32bit-1.1.x86_64.rpm" on the i586 scheduler and "foo-1.1.x86_64.rpm" on the x86_64 scheduler, we'll now store: i586/foo foo-1.1.src.rpm foo-1.1.i586.rpm foo-32bit-1.1.x86_64.rpm x86_64/foo foo-1.1.src.rpm foo-1.1.x86_64.rpm ::import::i586::foo-32bit-1.1.x86_64.rpm So don't be surprised if you see those strange "::import" files popping up in the build results. (Having the imported binary packages available with the normal package build results also fixes a long standing limitation with kiwi product builds, but I don't want to bore you with the details.) Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1