Hello,
whether I add "Packager" in a spec file or not, rpmlint complains in both
cases. One time because of hardcoding. The other time because it is
missing.
Could this please be fixed?
What I would like to see is that the buildservice-email-address also used
in the GPG key of the repository is automatically copied into the spec
(like e.g. changelog or revision).
Is this possible (thought that would not fix the hardcoding error
message) or can the name+email be added in the build command directly?
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I tried to compile the fox1.4 package for ubuntu
and wanted to add the sources directly from the debian
server http://packages.debian.org/etch/libfox1.4
Unfortunately when adding the files by URL to my
obs package (like
http://ftp.de.debian.org/debian/pool/main/f/fox1.4/fox1.4_1.4.34.orig.tar.gz)
something went wrong, because the build process fails:
dpkg-source: error: file fox1.4_1.4.34.orig.tar.gz has md5sum
724e66b89b5451d5032165e03ff5228d instead of expected
3424b9d3f9b71e1f53e9c3822de3b76c
I checked this by downloading the file once from the debian site
and once from the obs and they have different checksums indeed.
The sizes are the same thus it is probably not a matter of
automatic gz extraction.
The diff.gz of the same package has the same problem, that's why I think
there might be something wrong with the remote upload.
Has anyone else encountered this problem?
Is there a known workaround besides down-/uploading?
Regards,
Michael
--
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-----
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!
We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host.
Only remaining is the rebuild-loop when kiwi is used inside obs.
Let's hunt that little bug now ;).
Summary:
The scenario is like this: project "imaging:Admin", package "foo", repository "image".
Simple kiwi-config (only bootstrap section!), output is ext2-image. Filename ends in "*0.0.1" (version in the kiwi.xml).
So far: build succeeds, things get uploaded here (also show up in /srv/obs/build/<foo>), BUT not in /srv/obs/repos
and the job is directly rescheduled and thus builds in a loop.
here's the scheduler-log:
event finished:imaging::image::obs-imaging-8d2731b6e7128e3694ffb623f20177a6
0 left)
- imaging/image: obs-imaging built: 3 files
looking at med prio imaging/image (0/0/1/0/17)
- imaging/image
expanding dependencies
sorting 1 packages
- obs-imaging (kiwi)
+autoconf
+automake
[...]
+openvpn
+perl-base
+python
+python-xml
+rpm
+rpm-python
+smart
+terminfo-base
+xenomai
+zlib
meta change, start build
Use of uninitialized value in substitution (s///) at BSFileDB.pm line 86.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 1.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 1.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 1.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 2.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 2.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 2.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 3.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 3.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 3.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 4.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 4.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 4.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 5.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 5.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 5.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 6.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 6.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 6.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 7.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 7.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 7.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 8.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 8.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 8.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 9.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 9.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 9.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 10.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 10.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 10.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 11.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 11.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 11.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 12.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 12.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 12.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 13.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 13.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 13.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 14.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 14.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 14.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 15.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 15.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 15.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 16.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 16.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 16.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 17.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 17.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 17.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 18.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 18.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 18.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 19.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 19.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 19.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 20.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 20.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 20.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 21.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 21.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 21.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 22.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 22.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 22.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 23.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 23.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 23.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 24.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 24.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 24.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 25.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 25.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 25.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 26.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 26.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 26.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 27.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 27.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 27.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 28.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 28.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 28.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 29.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 29.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 29.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 30.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 30.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 30.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 31.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 31.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 31.
Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 32.
Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 32.
Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 32.
scheduled: 1
building: 1, notready: 1
took 0 seconds to check the packages
looking at low prio imaging/image (0/0/0/0/17)
- imaging/image
expanding dependencies
sorting 1 packages
scheduled: 1
building: 1, notready: 1
took 0 seconds to check the packages
waiting for an event...
Looks like BSFileDB doesn't find variables in this case.
My worker sends these files:
$VAR1 = [
{
'filename' => '/tmp//root_1/.build.packages/KIWI/limbo-auto-config.i686-0.0.1',
'name' => 'limbo-auto-config.i686-0.0.1'
},
{
'filename' => '/tmp//root_1/.build.meta',
'name' => 'meta'
},
{
'filename' => '/tmp//root_1/.build.log',
'name' => 'logfile'
}
];
We need to find a way to accept kiwi's output filenames (other than .iso).
I looked at bs_sched, but I'm (a bit) lost finding the right spot.
best regards,
Jan-Simon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I tried to build netcdf on CentOS and it stumbled over
the following line
PreReq: %install_info_prereq
As far as I understand it, this line is needed to prepare
the installation of info files but the (CentOS)
build went through without it as well.
Is this feature unneeded (unsupported) on CentOS?
Should I try to forward my changes to the package
maintainer and which is the preferred way to do so?
(I tried it once with a different package by mailing
him directly and got no answer.)
Regards,
Michael
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
as far as I understand it, there is currently no test whether
a package build by the build service can also be installed
(if it is not used by other packages).
Maybe there already is such a test and I just did not
find the correct settings?
If not, one solution would be to create a dummy package
which has a BuildRequires line mentioning just the
package to test. In the build part it could try to execute
an exectuable of the package and report failures.
Is it possible to create a package consisting of a
spec only?
Is there an easier way to achieve this, because I would
need one extra package for every package I want to test?
Thanks for your help and for providing this service,
Michael
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello Friends,
i've downloaded BOINC Source from svn/tags and maked a *.spec-File. When
i run the OBS/complete rebuild Link, the build runs a while.
But then the Compiler broken:
---snip--
ViewWork.cpp:1041: error: call of overloaded 'wxString(const char*)' is
ambiguous
/usr/include/wx-2.8/wx/string.h:722: note: candidates are:
wxString::wxString(const wxWCharBuffer&) <near match>
/usr/include/wx-2.8/wx/string.h:692: note: wxString::wxString(wxChar,
size_t) <near match>
/usr/include/wx-2.8/wx/string.h:690: note: wxString::wxString(const
wxString&) <near match>
/usr/include/wx-2.8/wx/string.h:682: note: wxString::wxString(int) <near
match>
make[2]: *** [boinc_gui-ViewWork.o] Error 1
make[2]: Leaving directory `/usr/src/packages/BUILD/boinc-
core-6.3.14/clientgui'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/packages/BUILD/boinc-core-6.3.14'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.33556 (%build)
RPM build errors:
cannot open Pubkeys index using db3 - No such file or directory (2)
Bad exit status from /var/tmp/rpm-tmp.33556 (%build)
System halted.
---snap---
Does anyone know, what the error is? My spec-File is attached.
--
Sincereley yours
Sascha Manns
Open-News-Network e.V.
Web: http://saschamanns.gulli.to
Hi,
I tried to build a rpm with some scripts in the rpm.
But on a different platform (e. g. AIX), I need to install the rpm with rpm --ignoreos -i <package>
Is there a way to set the OS value in the rpm file from Linux to aix5.3?
Ulf
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I'm trying to build a package from a binary:
http://wiki.openmoko.org/wiki/Toolchain As it's a cross compilation for
the openmoko I get a log of error due to the |/usr/lib/rpm/brp-*
scripts. I'm wondering how to disable these checks.
By the way i only got openSuSE 11.0 build to work only by adding rpmlint
filter lines.
I'm wondering isn't there a way to just untar the package via rpmbuild in
a way that's untouched by any of the tests?
That is basically what I want to accomplish. I want to able to install the
package in /usr/local as is needed fore this build and have the advantages
of rpm.
I hope my question is clear.
I've attached the errors I get. (The binaries are compiled for a arm
(OpenEmbedded) not a x86/ix86 as it's for cross build).
Regards,
Joop Boonen.