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,
Seems the armv7 waiting queue is quite long now. And there is only a few
native armv7 workers, at the same time it seems there is no
qemu-based-armv7 workers. At the same time, seems that all of armv6
workers are qemu.
The question is what is the policy not to run armv7 on x86_64 workers?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
osc tab completion is broken since always. If wanted I could give you
many utterly broken examples but I can't imagine that there is someone
who does not know the problems. Does it acually does something useful
for somebody?
Do we really need to enable it by default? At least we should disable
network access in _any_ tab completion. Even if osc would work at
all ...obs servers are very often not reachable ... even more annoying.
BTW what is the preferred way to disable it? Does
removing /etc/profile.d/osc.*sh survives an update?
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
According to the spec file of my project on OBS:
https://build.opensuse.org/package/view_file/home:andisugandi/ignsdk/ignsdk…
Why the installation is failed (openSUSE 13.1, x86_64):
> su -c 'zypper install ignsdk-devtools'
Password:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides libqt5-qtwebkit needed by ignsdk-1.1.3-9.1.x86_64
Solution 1: do not install ignsdk-devtools-1.1.3-9.1.x86_64
Solution 2: break ignsdk-1.1.3-9.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c):
Any suggestions, please?
Btw, happy holiday! :)
Thanks in advance.
--
Andi Sugandi.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I can log into OBS on the web, but when I try to search for something,
it seems to lock up.
If someone can fix that, it would be nice.
I'm using obs search in the meantime, but I don't know how to do
wildcards with it.
Thanks
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
As I'm getting more and more build error due to out of memory condition
see osc remotebuildlog home:bruno_friedmann:mapserver64 sfcgal openSUSE_Factory i586 | less
I'm looking for a way to define a minimal requirement for the builder (when the build is done on vm started with -m 3000 it finish correctly)
Is that kind of definition exist, if yes, where can I setup it (repo,package level?)
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
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 new to obs, so I'm not fluent with it.
I have a project that builds fine for OS12.2 and OS13.1. Unfortunately,
it segfaults for OS12.3, for which I am actually building.
Can I do something to prevent this ? I downloaded the logfile. This is
the last part of it :
[ 301s] + cd tagainijisho-1.0.1
[ 301s] + make
DESTDIR=/home/abuild/rpmbuild/BUILDROOT/tagainijisho-1.0.1-6.1.i386 install
[ 301s] [ 2%] Built target tagaini_sqlite
[ 301s] Scanning dependencies of target build_kanji_db
[ 301s] [ 2%] Building CXX object
src/core/kanjidic2/CMakeFiles/build_kanji_db.dir/Kanjidic2Parser.cc.o
[ 303s] [ 2%] Building CXX object
src/core/kanjidic2/CMakeFiles/build_kanji_db.dir/KanjiVGParser.cc.o
[ 305s] [ 3%] Building CXX object
src/core/kanjidic2/CMakeFiles/build_kanji_db.dir/BuildKanjiDB.cc.o
[ 308s] [ 3%] Building CXX object
src/core/kanjidic2/CMakeFiles/build_kanji_db.dir/__/XmlParserHelper.cc.o
[ 308s] Linking CXX executable build_kanji_db
[ 309s] [ 3%] Built target build_kanji_db
[ 309s] Scanning dependencies of target kanjidic2-db
[ 309s] [ 3%] Generating ../../../kanjidic2.db
[ 309s] /bin/sh: line 1: 3240 Segmentation fault ./build_kanji_db
-len,en,fr,de,es,ru /home/abuild/rpmbuild/BUILD/tagainijisho-1.0.1
/home/abuild/rpmbuild/BUILD/tagainijisho-1.0.1
[ 309s] make[2]: *** [kanjidic2.db] Error 139
[ 309s] make[1]: ***
[src/core/kanjidic2/CMakeFiles/kanjidic2-db.dir/all] Error 2
[ 309s] make: *** [all] Error 2
[ 309s] error: Bad exit status from /var/tmp/rpm-tmp.jVDiVn (%install)
[ 309s]
[ 309s]
[ 309s] RPM build errors:
[ 309s] Bad exit status from /var/tmp/rpm-tmp.jVDiVn (%install)
[ 310s] /.build/build: line 373: 244 Killed
background_monitor_process
[ 312s] [ 289.371852] SysRq : Power Off
[ 312s] [ 289.374412] reboot: Power down
Thanks for any pointers,
Koenraad
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
could you please change the obs-emails to not send all recipients in
the "to:" list? I'm getting frustrated by those people who hit
reply-all all the time in order to discuss with the request reviewer..
It would be great if both from: and reply-to would point to some email
address that either deletes the email right away, responds with some
"use the webui!" autoresponder or forwards it to the request directly.
I'd prefer to have the out-of-band discussion not happening in my inbox.
Thanks,
Dirk
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Inside the chroot environment during "osc build", the /etc/mtab contains
the entries of the outside environment. Therefore, tools relying on that
file fail, e.g. df:
df -a > /dev/null ; echo $?
df: ‘/sys/kernel/security’: No such file or directory
df: ‘/sys/fs/cgroup’: No such file or directory
df: ‘/sys/fs/cgroup/systemd’: No such file or directory
df: ‘/sys/fs/pstore’: No such file or directory
df: ‘/sys/fs/cgroup/cpuset’: No such file or directory
df: ‘/sys/fs/cgroup/cpu,cpuacct’: No such file or directory
df: ‘/sys/fs/cgroup/memory’: No such file or directory
df: ‘/sys/fs/cgroup/devices’: No such file or directory
df: ‘/sys/fs/cgroup/freezer’: No such file or directory
df: ‘/sys/fs/cgroup/net_cls’: No such file or directory
df: ‘/sys/fs/cgroup/blkio’: No such file or directory
df: ‘/sys/fs/cgroup/perf_event’: No such file or directory
df: ‘/sys/fs/cgroup/hugetlb’: No such file or directory
df: ‘/dev/hugepages’: No such file or directory
df: ‘/dev/mqueue’: No such file or directory
df: ‘/sys/kernel/debug’: No such file or directory
df: ‘/sys/fs/fuse/connections’: No such file or directory
df: ‘/run/user/1000/gvfs’: No such file or directory
df: ‘/var/run/user/1000/gvfs’: No such file or directory
df: ‘/var/tmp/build-root/standard-i586/proc’: No such file or directory
df: ‘/var/tmp/build-root/standard-i586/dev/pts’: No such file or directory
1
Is there a discussion about this to get it fixed?
Thanks & have a nice day,
Berny
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org