Hello,
we are pleased to announce the new releases of OBS Light (0.5.3).
This new version allows to work on packages hosted on OpenSUSE OBS.
OBS Light provides a GUI and a command line mode to work on packages hosted on an OBS or a FakeOBS.
It does offer to the developer the capability to work directly in the chroot, to re-run each phases of the spec file at will, while creating and committing OBS compatible patches when required.
OBS Light was originally developed for MeeGo and Tizen but the latest change allows OpenSUSE users to benefit from the toolset and while we consider the support of OpenSUSE in Beta stage, we think that it would ease everyday work and we would love to get non embedded users's feedback.
OBS Light client now also creates repositories where your locally built packages are published. These local repo can be used to create image
with Mic (which is integrated in the GUI) or to download the custom packages directly on your target with zypper or yum.
You will find more information about OBS Light at:
* http://en.opensuse.org/openSUSE:OBS_Light
Summary of changes:
Now you can build packages with OBS Light from an OBS server or a fakeobs without an OBS
server).
- OBS Light 0.5.3:
- Build against on OpenSUSE OBS against openSUSE i586 and Fedora (Devel).
- Added status "No build section" when package has no script in the
%build section.
- Added pre-configured servers in wizard.
- Accelerated retrieval of project list from server.
- Removed useless buttons from UI.
To install or update:
* http://en.opensuse.org/openSUSE:OBS_Light_Installation
You can find an appliance including OBS Light here:
* http://susestudio.com/a/e0uuBG/obs-light-obs-client
Do not hesitate to submit bugs or suggestions for improvements on our
bug tracker:
*
https://bugs.meego.com/buglist.cgi?product=Development%20Tools&componen…
Your feedback is welcome.
With thanks, the OBS Light Team.
--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
With obs, can a count of suggessfully built packages for the month be
shown on the 'Scheduler Status' page.
With each successful built package, log a entry like so:
echo 1 >> /tmp/built-packages-count.log
A sample log may look like this:
# cat /tmp/built-packages-count.log
1
1
1
1
1
So in this case:
echo "Built packages for month:" `cat /tmp/built-packages-count.log | wc
-l`
The result based on the example is:
Built packages for month: 5
To reset the value at the beginning of the next month just remove the
/tmp/built-packages-count.log
and the count would start at 1 again after the first successful build of
the next package.
If you see the number is increasing you know packages are being built.
Be interesting to know how many packages are built in a month.
Cheers Glenn
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I was wondering why I was getting so few deltarpms for big package
updates (like libreoffice), and I went and checked the source[0]
It turns out that in line 32 it removes the drpm if its size is more
than half the non-delta size.
Thing is, this criterion is really ill-suited for big RPMs (which is
where deltas save the most bandwidth), since a DRPM on libreoffice
could be more than half the non-delta size, but still save
considerable bandwidth (hundreds of MB).
So... why not use a different threshold?
I propose 80% for packages bigger than 200k, and 50% for smaller packages.
Pseudo-patch:
@ -32,1 +32,5
- let drpmsize=$drpmsize+$drpmsize
+ if (( $drpmsize/200 < 204800 )) ; then
+ let ndrpmsize=$drpmsize+$drpmsize
+ else
+ let ndrpmsize=$drpmsize+$drpmsize/5
+ fi
[0] https://github.com/openSUSE/open-build-service/blob/master/src/backend/work…
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm bug owner of a few packages for a openSUSE projects that aren't
maintained any more.
Can I please be removed as a bug owner, for these specific packages? Then
these won't show up in my list.
openSUSE:11.2:Contrib/NeoTool
openSUSE:11.2:Contrib/cacti
openSUSE:11.2:Contrib/dfu-util
openSUSE:11.2:Contrib/fwbuilder
openSUSE:11.2:Contrib/libfwbuilder
openSUSE:11.2:Contrib/php5-gtk
openSUSE:11.2:Contrib/php5-pecl-cairo
openSUSE:11.4/qprint
openSUSE:11.4/signing-party
Regards,
Joop.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I submitted googletest to Factory a few minutes ago.
https://build.opensuse.org/request/show/130678
And it was "rejected" (because in my request view, I saw it's been put
in my declined request)
But after I clicked into it, it's still open reviews status for
factory-auto and legal-auto scripts.
And no sign of being rejected.
I have only two options "accept" and "revoke"
What can I do?
Marguerite
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi guys,
If I build packages for CentOS-6 on OBS, the resulting debuginfo
packages are named <pkgname>-debug-... but they should be named
<pkgname>-debuginfo-... (so that they can be found by the
debuginfo-install tool).
Can some admin please fix this or do I have to configure anything
special on my own?
- -Fritz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAlRO8ACgkQboM4mAMyprA3gQCgoxCqrUEe9fuwOxhMhI8nBHTQ
tbUAnArOjISA+uCOdZlW8tHBdU+twcbz
=6Vsx
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi, all,
Many and I are curious about the current status of Arch Linux support in OBS.
Last Aug we saw the report from GSoc student saying the backend had finished.
According to the project page, seems we were only lack of a web UI at that time.
On obs github we saw the last commit to obs-build/Build/Arch.pm was
from 4 month ago.
And no useful news on Google can tell whether its usable or not.
Many Archers around me are waiting to see that happen.
So anyone know if it is still under development or just freeze for a while?
Greetings,
Marguerite
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I created a SR to create a new package in factory:
===
130346 State:new By:a_jaeger When:2012-08-09T21:22:26
submit: security/ssdeep ->
openSUSE:Factory
Review by Group is accepted: legal-auto(licensedigger)
Review by Group is accepted: factory-auto(factory-auto)
Review by Group is accepted: legal-team(babelworx)
Review by Group is accepted: autobuild-team(a_jaeger)
From: review(gregfreemyer) -> review(licensedigger) ->
review(factory-auto)
Descr: ssdeep is a tool for computing piecemeal hashes of files. Useful
in malware detection.
Comment: ok, but I'll do some cleanup now, separate request coming.
===
As you see AJ saw some specfile cleanups he wanted. He submitted an
SR to security/ssdeep with those. They've been accepted a couple
hours ago.
Should I superseed the above SR with a new one? Thus causing the
legal review to reset.
Or should I leave the above in place until it is accepted, then do
another SR to get AJ's cleanups in?
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 have different results in local build and OBS build.
Build locally:
[ 25s] ... testing for serious compiler warnings
[ 25s] (using /usr/lib/build/checks-data/check_gcc_output)
[ 25s] (using /home/kent/rpmbuild/BUILD-osc/openSUSE_Factory-x86_64/.build.log)
[ 25s] ... running 03-check-binary-kernel-log
It goes OK.
Build in OBS:
[ 114s] ... testing for serious compiler warnings
[ 114s] (using /usr/lib/build/checks-data/check_gcc_output)
[ 114s] (using //.build.log)
[ 114s]
[ 114s] I: Program returns random data in a function
[ 114s] E: qmetro no-return-in-nonvoid-function src/completer.cpp:199
[ 114s]
Installed post-build-checks-1.0-110.1.noarch.
Local build log:
http://susepaste.org/view/simple/82634078
OBS log:
https://build.opensuse.org/package/rawlog?arch=i586&package=qmetro&project=…
--
WBR
Kyrill
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org