Hi,
$ osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t1
$ osc api -m POST -d 'Name: test' \
/build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t2
$ diff -u t[12]
--- t1 2009-09-08 15:56:54.000000000 +0200
+++ t2 2009-09-08 15:56:57.000000000 +0200
@@ -1,13 +1,5 @@
<buildinfo project="home:michal-m" repository="openSUSE_11.0"
package="nafe" downloadurl="http://download.opensuse.org/repositories">
<arch>x86_64</arch>
- <srcmd5>4f263493abe82e1f59603b5a5642b4a0</srcmd5>
- <verifymd5>4f263493abe82e1f59603b5a5642b4a0</verifymd5>
- <rev>2</rev>
- <specfile>nafe.spec</specfile>
- <file>nafe.spec</file>
- <versrel>0.1-2</versrel>
- <bcnt>2</bcnt>
- <release>2.2</release>
<debuginfo>0</debuginfo>
<bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1"
version="11.0" release="79.1" arch="x86_64" project="openSUSE:11.0"
repository="standard" />
<bdep name="acl" preinstall="1" notmeta="1" version="2.2.45"
release="40.1" arch="x86_64" project="openSUSE:11.0"
repository="standard" />
Because of the missing <release>2.2</release> element, osc doesn't
substitute release numbers when building locally. Should osc work around
this (get the buildinfo a second time to find out the release) or should
the backend be fixed (bs_repserver, function getbuildinfo(), that
doesn't fetch the required pieces when called from getbuildinfo_post())?
Michal
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
When building locally in a qemu/chroot and debugging I find I want to edit the
files in the chroot from my desktop gui editor but they're all owned by 399:399.
This pair of patches allows me to set the uid:gid to match my local user and
eases this process.
usage is:
build --build-abuild-id uid:gid
or more usually:
osc build --build-abuild-id 500:500
osc also accepts (and extends the default) .oscrc settings:
build-abuild-id = 500:500
It only supports numeric ids.
The osc patch also adds --map-repo to aggregatepac which
allows repository mapping(s) to be given as SRC=TARGET[,SRC=TARGET]
eg, a real usage:
osc aggregatepac -m
MerStable_Debian_5.0=Mer0.13_Debian_5.0,MerStable_Ubuntu_9.04=Mer0.13_Ubuntu_9.04
Maemo:Mer:0.13:HW:N8x0 advanced-power Maemo:Mer:Stable:HW:N8x0
https://build.opensuse.org/package/view_file?file=_aggregate&package=advanc…
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
Hello Mates,
atm i'm trying to run an Ruby Program. The issue from shell is:
[*] The msfgui interface requires the ruby-gtk2 and ruby-libglade2 packages
[*] Dependencies include ruby-pango, ruby-glib2, ruby-gdkpixbuf2, and ruby-atk
[-] Error: LoadError no such file to load -- gtk2
Have we Packages with that content?
--
Sincerely yours
Sascha Manns
openSUSE Member
openSUSE Ambassador
openSUSE Marketing Team
openSUSE Build Service
Web: http://saschamanns.gulli.to
Blog: http://saigkill.wordpress.com
ClaimID: http://claimid.com/saigkill
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I have looked but could not find any information on when a scheduled build
will start.
I do understand that this will depend on the load and what is in front of
the queue and will be a bit inaccurate.
It still would be nice to know whether something will start in 2 minutes
or 2 hours or 2 days. Or even see where it is in the queue s that you can
do a rough estimate yourself.
houghi
--
To have a nice mailinglist experience, follow the guidelines below:
> Please do not toppost. Please turn off HTML
> Read http://en.opensuse.org/Opensuse_mailing_list_netiquette
> Read http://www.catb.org/~esr/faqs/smart-questions.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I have a local OBS instance running 1.6.0.
I've found that I seem unable to use abortbuild to abort the build of
all packages in a project or project + repo.
The response is always "ok" but the status of the packages doesn't
seem to change (scheduled) and tailing the logs on the instance shows
that package builds continue on their merry way.
In a related question, sometimes I change the build configuration by
editing the file. Even after multiple restarts, *sometimes* the
altered config is picked up and sometimes it isn't. Specifically, I'm
adding Preinstall items. What might be going on here?
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi, can anyone tell me what this means :-
RPM build errors:
cannot open Pubkeys index using db3 - No such file or directory (2)
Thanks
Dave P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I started to package php5-pear-log, that was removed from the openSUSE base
distribution, in the build service in the repository server:php:applications.
(https://build.opensuse.org/project/show?project=server:php:applications)
When building the package, the following warning is issued (local build, using
osc 0.120):
running changelog2spec --target rpm --file
/home/richard/packages/osc/server:php:applications/php5-pear-log/php5-pear-
log.spec
Warning: spec file parser line 37: can't expand %(...)
Warning: spec file parser line 40: can't expand %(...)
Warning: spec file parser line 41: can't expand %(...)
Warning: spec file parser line 48: can't expand %(...)
Warning: spec file parser line 88: can't expand %(...)
Warning: spec file parser line 89: can't expand %(...)
Warning: spec file parser line 90: can't expand %(...)
Warning: spec file parser line 91: can't expand %(...)
Warning: spec file parser line 92: can't expand %(...)
Warning: spec file parser line 93: can't expand %(...)
and some more of those lines.
The variable that those lines have in common is %{peardir}. This variable is
defined at the top of the spec file. The definition is as follows:
%define peardir %(pear config-get php_dir 2> /dev/null)
The variable gets defined nicely, as in the end the build of spec file results
in an src.rpm and binary rpm.
Is this a deficiency in the changelog2spec file tool?
--
Richard
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi
when building exactly the same package in openSUSE:Factory standard and in the
repository openSUSE_Factory i586 the result is different. In openSUSE:Factory
standard the build succeeds, in the openSUSE_Factory (i586) the build fails with an
rpmlint error....
The directories are the same:
packages/osc> diff openSUSE\:Factory/cyrus-imapd server\:Kolab\:UNSTABLE/cyrus-imapd-kolab
Common subdirectories: openSUSE:Factory/cyrus-imapd/.osc and server:Kolab:UNSTABLE/cyrus-imapd-
kolab/.osc
osc version is .120
# cyrus-imapd-kolab> osc build openSUSE_Factory i586 cyrus-imapd.spec
................
The failing output:
... running 99-check-remove-rpms
... removing all built rpms
(order: reverse perl-Cyrus-SIEVE-managesieve cyrus-imapd-devel perl-Cyrus-IMAP cyrus-imapd)
RPMLINT report:
===============
1 packages and 0 specfiles checked; 0 errors, 2 warnings.
Traceback (most recent call last):
File "rpmlint.py", line 324, in <module>
File "rpmlint.py", line 126, in main
File "rpmlint.py", line 199, in runChecks
File "BinariesCheck.py", line 288, in check
NameError: global name 'i' is not defined
The succesfull output:
# openSUSE:Factory/cyrus-imapd> osc build standard i586
... running 99-check-remove-rpms
... removing all built rpms
(order: reverse perl-Cyrus-SIEVE-managesieve cyrus-imapd-debugsource cyrus-imapd-devel cyrus-imapd-
debuginfo perl-Cyrus-IMAP cyrus-imapd perl-Cyrus-SIEVE-managesieve-debuginfo perl-Cyrus-IMAP-debuginfo)
RPMLINT report:
===============
cyrus-imapd.i586: W: files-duplicate /etc/pam.d/sieve /etc/pam.d/pop:/etc/pam.d/imap
cyrus-imapd.i586: W: incoherent-init-script-name cyrus ('cyrus-imapd', 'cyrus-imapdd')
The init script name should be the same as the package name in lower case, or
one with 'd' appended if it invokes a process by that name.
cyrus-imapd.i586: W: missing-lsb-keyword Default-Stop in /etc/init.d/cyrus
cyrus-imapd.i586: W: missing-lsb-keyword Short-Description in /etc/init.d/cyrus
The package contains an init script that does not contain one of the LSB init
script comment block convention keywords that are recommendable for all init
scripts. If there is nothing to add to a keyword's value, include the keyword
in the script with an empty value. Note that as of version 3.2, the LSB
specification does not mandate presence of any keywords.
perl-Cyrus-SIEVE-managesieve.i586: W: zero-length /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-
multi/auto/Cyrus/SIEVE/managesieve/managesieve.bs
perl-Cyrus-IMAP.i586: W: zero-length /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-
multi/auto/Cyrus/IMAP/IMAP.bs
5 packages and 0 specfiles checked; 0 errors, 6 warnings.
med111 finished "build cyrus-imapd.spec" at Wed Sep 30 13:30:56 CEST 2009.
/var/tmp/build-root-standard-i586/usr/src/packages/SRPMS/cyrus-imapd-2.3.14-7.src.rpm
Any idea what is wrong, and what can be done about it?
--
Richard
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Adrian Schröter:
>Am Montag, 14. September 2009 15:09:24 schrieb Johannes Obermayr:
>
>>Hi,
>>
>>I let build some packages on buid service and recognized, that most of them
>>were/are/will not been released in my home: directory on
>>download.opensuse.org (or only many hours later...)
>>
>>So my questions are:
>>Are there any problems? Is this normal? Can I force/accelerate
>>copying/releasing "by hand"?
>>
>>Before I forget: There is/was one package which is/was broken. But none of
>>the other packages depends on it. So this should not be the reason...
>
>
>In general, the publisher is still stopped since thursday, so currently you
>see no updates at all.
>
>In particular, you home project contains some really evil aggregates, just
>copying several Gigabytes without any need.
>
>Can you just build against X11:XOrg and Kernel:HEAD instead of copying the
>files ? (by editing project meta data "osc meta prj -e home:jobermayr".
>
>bye
>adrian
Hi,
I did what you said.
I am building now also against "openSUSE:Factory/snapshot" as "forced".[1][2]
There are following problems:
openSUSE_11.1:
- Built Packages have not been released since 21 Sep 2009.
openSUSE_Factory:
- Packages have been only "scheduled" since yesterday evening except "drm-all" i586 which was built three times today (about 1 am German time, 4:33:14 UTC and 8:58:52 UTC [start times]) but with finishing it is/was "scheduled" again...
- Built Packages have not been released since 21 Sep 2009.
- Ruediger Oertel has a similiar project and his packages have been/are built.[3]
Thanks
Johannes
[1] http://lists.opensuse.org/opensuse-kde/2009-09/msg00146.html
[2] http://lizards.opensuse.org/2009/09/02/building-against-opensusefactory/
[3] https://build.opensuse.org/project/show?project=home%3Aoertel%3ARadeon_DRI2
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
There is expansion error for SLE10 (x86,x86-64) and SLE11(x86-64) for
chrpath. I don't understand why SLE11 i586 has chrpath, but SLE11 x86-64
hasn't? It seems that we need some Substitutes for SLE.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org