May I make a suggestion: Could you please add some functions, so that poor people like me can do the same? Sometimes it would help very much if you could add a function like: - clobber (clean all build packages) - reevaluate the spec files - a package in a project is in deactivated state when it is added. It must first be activated. so that you can overcome such a situation. I was just using the function "add link" in the webinterface. Lateron I worked with osc command client. I work in a way so I first test everything with a local "osc build" before I check in everything. Michael Schroeder wrote:
On Tue, Feb 13, 2007 at 09:00:48PM +0100, Martin Mohring wrote:
I dont see what you mean. Which line in cross-sh4-glibc-bootstrap.spec contains kernel-headers?
Why did it produce glibc* without prefix? Could it be that this was caused by an initial checkin of a link to "openSUSE:Factory/glibc" before I checked in the other files?
I am a little bit confused.
Ok, cross-sh4-glibc-bootstrap got built with srcmd5 34cb71b9b87005b8fdea565d4d3be843 (as stated in the logfile), that's local srcmd5 "d548487d1004c16c57c699164f4ccba4" which contained just the link, but no other spec file. The link was created at 16:42, packages finished building at 17:48.
As it was a plain link the build used glibc.spec (as also stated in the logfile), thus the bad requires and package names.
At 19:15 you added a different specfile, but then the damage was already done, no more building was possible...
I've wiped all the rpms from the cross-sh4-glibc-bootstrap packages, so the build should now pick up the right specfile.
Cheers, Michael.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org