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
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
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
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
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
Hi,
I'm currently running into the issue described here:
http://lists.opensuse.org/opensuse-buildservice/2014-01/msg00156.html
The following statements seem to be to be true:
1) In a given distribution, only the most recently built version of a
package will be available to satisfy BuildRequires
2) If a mis-matched version of a BuildRequires dependency exists in a
distribution in a package's project, no other project's distributions
will be searched for that dependency, even if the BuildRequires
specifies a version available in a different distribution that is in
the repository search configuration
Can someone please confirm they are correct?
If they are correct, are there any plans to support multiple versions
of builds for satisfying BuildRequires? I started to look at the code
around this and it seems pretty dense - what direction would you point
someone in if they wanted to modify this behavior? The only other
options I can think of are all very cumbersome in terms of
administrative overhead within OBS.
Thanks for your help.
Andy
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
People, Friends, Packagers,
are you ready for another set of great features for your free software
packaging needs? We are with version 2.5. of the Open Build
Service(OBS)!
With this release you can plug OBS into your continuous
integration/delivery chain thanks to the new token API that let's you
trigger builds from revision control systems like github. 2.5 further
merges the Web UI and API into one single Ruby on Rails app, so it is
easier for you to maintain, easier for us to extend and most important
way snappier to use for your packagers.
This release also begins to unify the various places where you can
configure things into the OBS API, introduces an integrated comment and
notification system and saves your OBS servers some cycles by
automatically cleaning up left over branches. As you can see our team
never tires to be awesome! Read on for more, in depth, information about
OBS version 2.5.
http://openbuildservice.org/2014/03/31/version-2.5/
The Open Build Service Team
--
http://openbuildservice.org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
it seems there is a problem armbuild13.
All jobs scheduled on this arm worker are in schedule state, then it is in building state for a short time and again schedule state.
Guillaume
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi Guillaume,
> this is armbuild07. Should be disabled ASAP since jobs scheduled on it are now in failed state.
Interesting, there is a bitflip in the initrd for the guest on that
worker. I've refreshed the initrd now to the correct state.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
I've now managed to resolve the problem I had with the build targets
being unavailable. I checked the version of the appliance (iso
installer) that I was using and I discovered it was 2.4. I went to the
2.5 repo and installed a new OBS server from the 2.5 ISO. I imported my
project and added the interconnect the the reference obs site. My
project immediately started to build with all the targets and completed
successfully.
The question I now have is how does one get a download link for the
finished rpm package? I can see the packages in the RPMS folder of the
build root but there's no download link in the web api.
--
Matthew
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org