[opensuse-buildservice] Why is kde build when there is no reference to kde in the spec file
Hi,
I'm maintaining a php/pear package. This one normally builds fine, but today I noticed that it builds kde! Why is that?
horde-token> osc bl openSUSE_11.0 i586 | grep kde | head /usr/lib/python2.6/site-packages/osc/conf.py:326: DeprecationWarning: Use of the 'scheme' or 'apisrv' config option is deprecated! See README for migration details. DeprecationWarning) build22 started "build mono-kde4.spec" at Thu Apr 30 08:17:07 UTC 2009. Building mono-kde4 for project 'home:snorp' repository 'SUSE_Factory' arch 'x86_64' srcmd5 '2e0606141c34d28ff28c8f4940138e88' processing specfile /abuild/root_4/.build-srcdir/mono-kde4.spec... running changelog2spec --target rpm --file /abuild/root_4/.build-srcdir/mono- kde4.spec init_buildsystem --prepare --clean --rpmlist /abuild/root_4/.build.rpmlist /abuild/root_4/.build-srcdir/mono-kde4.spec build rpmlint-Factory ... processing specfile /.build-srcdir/mono-kde4.spec... init_buildsystem /.build-srcdir/mono-kde4.spec build rpmlint-Factory ...
The concerning package that I'm working on is server:php:applications horde-token. This package has no reference to kde or what so ever:
horde-token> grep kde * richard@med111:~/packages/osc/server:php:applications/horde-token> ls Horde_Token-0.0.4.tgz horde-token.changes horde-token.spec log
Is there something broken on the server??
On Thu, Apr 30, 2009 at 10:52:55AM +0200, Richard Bos wrote:
I'm maintaining a php/pear package. This one normally builds fine, but today I noticed that it builds kde! Why is that?
Seems like the build job crashed somehow. Now restarted...
M.
Am Donnerstag, 30. April 2009 11:01:53 schrieb Michael Schroeder:
On Thu, Apr 30, 2009 at 10:52:55AM +0200, Richard Bos wrote:
I'm maintaining a php/pear package. This one normally builds fine, but today I noticed that it builds kde! Why is that?
Seems like the build job crashed somehow. Now restarted...
Most likely caused due to the not available source server for some minutes (due to reboot to get the box a new kernel).
However, this should only affected the logfile, which is not nice.
But it should not have submitted foreign packages to your project, which would be a serious problem.
bye adrian
On Thu, Apr 30, 2009 at 11:21:37AM +0200, Adrian Schröter wrote:
Most likely caused due to the not available source server for some minutes (due to reboot to get the box a new kernel).
However, this should only affected the logfile, which is not nice.
But it should not have submitted foreign packages to your project, which would be a serious problem.
A small clarification: the build job crashed due to the unavailable src server, but somehow the failed job wasn't terminated correctly.
What you're now seeing is the next build job running on the build client used for building your job. No wrong packages were generated.
We've restarted all jobs that were broken in such a way.
Cheers, Michael.
Op donderdag 30 april 2009 11:23:52 schreef Michael Schroeder:
On Thu, Apr 30, 2009 at 11:21:37AM +0200, Adrian Schröter wrote:
Most likely caused due to the not available source server for some minutes (due to reboot to get the box a new kernel).
However, this should only affected the logfile, which is not nice.
But it should not have submitted foreign packages to your project, which would be a serious problem.
A small clarification: the build job crashed due to the unavailable src server, but somehow the failed job wasn't terminated correctly.
What you're now seeing is the next build job running on the build client used for building your job. No wrong packages were generated.
We've restarted all jobs that were broken in such a way.
Thanks for the fast service :)
buildservice@lists.opensuse.org
-
Adrian Schröter -
Michael Schroeder -
Richard Bos