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
Sometimes you have appA in your repo building for both old and new
openSUSE versions. appA depends on libA > X, but only the latest
openSUSE version provides it. openSUSE <latest-1> came with libA
<X-1>. The solution is to package libA > X for the old distributions
and usually you do that linking to the devel project.
I would like an openSUSE:Current project that would always contains
the latest supported version of the packages. Right now the packages
from openSUSE:12.1:Update, but once 12.2 is released it should be
changed to openSUSE:12.2:Update. This way I could link to those
packages instead of linking to the devel project. It would let me
compile appA in old distros while giving to the users a libA package
that is not soooooo unsupported (this would be officially unsupported
anyway, but...).
I would like this since it's a single place to change when a new
openSUSE version is released (If needed I can do it).
Looking at the openSUSE:12.1:Update project metadata I guess it would
just need be something like
<project name="openSUSE:Current">
<title>Current version of openSUSE</title>
<description></description>
<link project="openSUSE:12.1:Update"/>
<debuginfo>
<enable/>
</debuginfo>
</project>
But I'm not sure since I never really saw a doc explaining the meaning
of <link> in the *project metadata*, only in _link files.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all,
I wanted a way to quickly compare a project with its "upstream"
project, and a quick hack ended up as a new osc plugin:
https://gist.github.com/616b476a9c592a0a2a89
(Copy to your ~/.osc-plugins or /var/lib/osc-plugins to try it.)
Example usages:
$ osc prdiff --include=client openSUSE:Factory Cloud:OpenStack:Factory
differs: python-glanceclient
identical: python-keystoneclient
differs: python-novaclient
differs: python-quantumclient
identical: python-swiftclient
$ osc prdiff --new-only --exclude='crowbar|rubygem' \
systemsmanagement:chef:10:staging \
systemsmanagement:crowbar:2.0
identical: couchdb
identical: erlang
identical: gecode
identical: js
differs: rabbitmq-server
new only: all-barclamps-good
new only: fakechroot
new only: libyaml
new only: ruby
new only: ruby-common
new only: ruby19
new only: sleshammer
$ cd ~/OBS/home/aspiers/branches/devel/languages/ruby/
$ osc prdiff --diffstat --requests
differs: ruby-common
generate_buildrequires.sh | 31 ++++++++++++++++++++++++++-----
ruby-common.changes | 8 ++++++++
2 files changed, 34 insertions(+), 5 deletions(-)
148023 State:new By:aspiers When:2013-01-11T11:04:14
submit: home:aspiers:branches:devel:languages:ruby/ruby-common -> devel:languages:ruby
Descr: - Fix it to work even if all-good has just been created locally
via mkpac and doesn't exist server-side yet. - Improve support
for running within a branch of the original project. This
allows submitreqs which change all-good.spec.
Feedback welcome. I'd also like to know if it makes sense to include
this in osc core (my vote is yes, but I'm biased ;-)
Cheers,
Adam
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
while looking for a recent scratch http://scratch.mit.edu/ in opensuse
I found that there are different versions of squeak running around in
X11:Sugar and devel:languages:smalltalk. The latter project seems not
to have seen any updates for almost three years, so I decided to
submit all of my changes to Education (where scratch lives). Is there
any smalltalker who wants to revive it or is it better to have it all
in Education?
Best regards,
Michael
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
All,
On OBS (the public instance) I'm used to searching for packages (libewf in
this case) and getting a list of results.
With each result I'm used to seeing the project the specific instance of
the package is in.
Not anymore.
https://build.opensuse.org/search?utf8=%E2%9C%93&search_text=libewf&commit=…
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
i don't know if this is known, the update for rubygem-delayed_job from SLE 11 SDK Updates is kept
back, because obs-api requires a version < 2.0.0
This persists since the ruby upgrades in the last weeks. Is the new version of rubygem-delayed_job
really not compatible with obs-api?
host:/srv/obs/log # zypper in rubygem-delayed_job-3.0.3-0.7.3.2.x86_64
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: obs-api-2.3.8-3.1.x86_64 requires rubygem-delayed_job < 2.0.0, but this requirement cannot
be provided
deleted providers: rubygem-delayed_job-1.8.4-3.3.x86_64
uninstallable providers: rubygem-delayed_job-1.8.4-0.1.38.x86_64[SLE11-SDK-SP2]
rubygem-delayed_job-1.8.4-3.2.i586[openSUSE:Tools:2.3]
rubygem-delayed_job-1.8.4-3.2.x86_64[openSUSE:Tools:2.3]
Solution 1: Following actions will be done:
downgrade of obs-api-2.3.8-3.1.x86_64 to obs-api-1.7.7-0.3.1.x86_64
install obs-api-1.7.7-0.3.1.x86_64 (with vendor change)
obs://build.opensuse.org/openSUSE:Tools --> SUSE LINUX Products GmbH, Nuernberg, Germany
Solution 2: do not install rubygem-delayed_job-3.0.3-0.7.3.2.x86_64
Solution 3: break obs-api-2.3.8-3.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c): c
host:/srv/obs/log # rpm -q obs-api --requires|grep delayed_job
rubygem-delayed_job < 2.0.0
Regards,
Carsten
Open Build Service(OBS) 2.3.8 just got released
===============================================
This release brings regression fixes when used together with newer
rubygem-rails-2.3.x versions. This fixes an endless loading build status
in the webui.
OBS 2.3.8 is published in "openSUSE:Tools:2.3" project:
http://download.opensuse.org/repositories/openSUSE:Tools:2.3/
Appliances can be used as usual:
http://en.opensuse.org/openSUSE:Build_Service_Appliance
The official release notes:
Feature backports:
==================
* none
Changes:
========
* webui: Added openSUSE 12.3 and Fedora 18 to default list
Bugfixes:
=========
* webui: build results show up again with latest Rails 2.3 security update
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de