>-----------------------------------------------------------------
>I have the following modifications for aaa_base.spec:
>32c32
>< Release: 79.4
>---
>> Release: 79.1
>-----------------------------------------------------------------
How do I prevent the buildservice from patching the spec file release
number?
--
Webmail for Dialup Users
http://www.isp2dial.com/freeaccounts.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
In home:a23d56:opensuse-11.0-minimal:base:repo, my pam package has
been finished for over an hour, but not succeeded. My other packages
blocked because of this.
This is far too slow. How about fixing it.
--
Webmail for Dialup Users
http://www.isp2dial.com/freeaccounts.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Ie got the following problem, when trying to build a package locally
to play around with the spec file:
- ---------
The following package could not be verified:
/var/tmp/osbuild-packagecache/openSUSE:11.0/standard/noarch/texlive-2007-175.1.noarch.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#739ebedd)
- - If the key is missing, install it first.
For example, do the following:
gpg --keyserver pgp.mit.edu --recv-keys 739ebedd
gpg --armor --export 739ebedd > /home/steuer/keyfile-739ebedd
and, as root:
rpm --import /home/steuer/keyfile-739ebedd
Then, just start the build again.
- - If the key is unavailable, you may use --no-verify (which may pose a risk)
- ----------
The key is unavailable, at least I couldn't find it.
Is there a way to disable verifying completely or for problematic packages?
After all it's just a local build
and won't be used in anyway besides build testing.
Or am I missing something obvious?
(Btw: same settings work just fine in the buildservice.)
Detlef
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkj290wACgkQ0g+Q+yDyuZhgBgCeJf0KFSeMQEf5eM3AxlmbdnMH
F8EAoJQaLKcngo2FApHZd6kDGy1t3ZoK
=oXBC
-----END PGP SIGNATURE-----
On Fri, 21 Nov 2008, Christian Stiens wrote:
> Moin,
> ich dachte schon Du bist in Essen. :-)
Essen? Was will ich denn da?
> Könntest Du mir eventuell eine fertig kompilierte Version schicken?
> Oder benötigt die auch zur Laufzeit die neuen QT Libs?
Eben zur Laufzeit brauchst Du die :-). Aber über die Opensuse-Seite kannst
Du die neuen QT-Pakete ohne nachteilige Effekte einfach installieren.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
The download repo for opensuse 11.0
http://download.opensuse.org/distribution/11.0/repo/src-oss/suse/src/
has:
cpio-2.9-60.1.src.rpm
but the buildservice openSUSE:11.0 project has a different version:
># Version: 2.9
># Release: 51
I noticed this when linking my package, because I get the old one.
Why the difference?
--
Webmail for Dialup Users
http://www.isp2dial.com/freeaccounts.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I started a small opensuse 11.0 base system and bootstrapped it. All
packages succeeded except cpio, which fails. Can someone please look
in my project home:a23d56:opensuse-11.0-minimal:self, and see why this
fails. I did not make any changes to the 11.0 package, so I don't see
why it should fail. The rpms were created, how can it fail? Here is
the end of the log:
Supplements: packageand(bundle-lang-other:cpio)
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/var/tmp/cpio-2.9-build
Wrote: /usr/src/packages/SRPMS/cpio-2.9-52.1.src.rpm
Wrote: /usr/src/packages/RPMS/i586/cpio-2.9-52.1.i586.rpm
Wrote: /usr/src/packages/RPMS/i586/cpio-lang-2.9-52.1.i586.rpm
... checking for files with abuild user/group
RPMLINT report:
===============
Traceback (most recent call last):
File "rpmlint.py", line 293, in <module>
File "rpmlint.py", line 97, in main
File "rpmlint.py", line 166, in runChecks
File "SpecCheck.py", line 178, in check
File "Pkg.py", line 146, in readlines
IOError: [Errno 2] No such file or directory:
'/tmp/cpio-2.9-52.1.src.rpm.10814/cpio.spec'
System halted.
--
Webmail for Dialup Users
http://www.isp2dial.com/freeaccounts.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
To make the build script and workers work with rpm 4.6 I had to do this
small modification, which is probably not generic enough and does not
cover all cases, but worksfor me.
Anas
--- build.old 2008-11-21 15:25:23.000000000 -0800
+++ build 2008-11-21 15:26:00.000000000 -0800
@@ -1003,7 +1003,7 @@ for SPECFILE in "${SPECFILES[@]}" ; do
# now clean up RPM building directories
#
rm -rf $BUILD_ROOT$TOPDIR
- for i in BUILD RPMS/`arch` RPMS/i386 RPMS/noarch SOURCES SPECS
SRPMS ; do
+ for i in BUILD RPMS/`arch` RPMS/i386 RPMS/noarch SOURCES SPECS
SRPMS BUILDROOT ; do
mkdir -p $BUILD_ROOT$TOPDIR/$i
test $BUILD_USER = abuild && chown 99:99 $BUILD_ROOT$TOPDIR/$i
done
@@ -1089,7 +1089,7 @@ for SPECFILE in "${SPECFILES[@]}" ; do
fi
rpmbuild=rpmbuild
- test -x $BUILD_ROOT/usr/lib/rpm/rpmi || rpmbuild=rpm
+ #test -x $BUILD_ROOT/usr/lib/rpm/rpmi || rpmbuild=rpm
# su involves a shell which would require even more
# complicated quoting to bypass than this
toshellscript $rpmbuild \
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Banshee is a project, Banshee: is a directory of sub-projects. No, we can't delete Banshee.
Andrew
>>> Detlef Reichelt <detlef(a)die-mafia.de> 10/03/08 5:23 PM >>>
Moin,
we should cleanup the OBS, for example:
Archiving:
and
Archiving
Banshee:
and
Banshee
What is the different between a $NAME and a $NAME:?
Could we delete the $NAME:?
Detlef
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
hi,
is a log file (ex :
https://api.opensuse.org/build/home:surfzoid/Mandriva2009standard/i586/Synt…)
only aviable at the end of the build ?
I would like to add in MonoOSC a similar function of the web client to
see the progress of the build process
--
Cordially.
Small Eric Quotations of the days:
---------------------------------------------------------------------------
If one day one reproaches you that your work is not a work of
professional, say you that:
Amateurs built the arch of Noah, and professionals the Titanic.
---------------------------------------------------------------------------
Few people are done for independence, it is the privilege of the powerful ones.
---------------------------------------------------------------------------
No key was wounded during the drafting of this message.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
