On Friday 23 July 2010, 14:49:31 Adrian Schröter wrote:
On Friday 23 July 2010 11:12:20 Hans-Peter Jansen wrote:
nothing provides obs-common, nothing provides rubygem-rails-2_3 >= 2.3.5, nothing provides rubygem-rmagick, nothing provides build >= 2009.05.04, nothing provides perl-BSSolv
How do I trick my BS to really use the openSUSE.org packages without adding each of them manually?
These are available in the repository of openSUSE:Tools project. I would add this repo and zypper in should work without problems.
Of course they are. The matter is, that BS should pick them up in order to build the package in question. Probably, I've deleted too much context from this conversation. Sorry. Here's, what I've done (still following README.SETUP): $ osc -A http://localhost:81 meta prj openSUSE:Tools -e # :%s/project="openSUSE:11.1"/project="openSUSE.org:openSUSE:11.1"/ Sending meta data... Done. $ osc -A http://localhost:81 meta pkg openSUSE:Tools obs-server -e # just do a small mod: add a title, otherwise it doesn't get written Sending meta data... Done. The project and package are visible in the local BS webui now. According to README.SETUP, section 6.1, I should prepare the check-in now: <quote> (in a svn co of the current openSUSE build server, in the buildservice/dist subdir) [...] Now prepare for a check-in. This will do a checkout and locally build using the packages from your local buildserver: OSCOPT="-A http://$servername:81" ./distribute </quote> # ~/VCS/GIT/build-service is the current build-service git tree here $ cd ~/VCS/GIT/build-service/dist $ OSCOPT="-A http://localhost:81" ./distribute Server returned an error: HTTP Error 404: Not Found Error getting meta for project 'openSUSE:Tools:Devel' package 'obs-all-svn' It looks like that part of README.SETUP doesn't work anymore. Now, in order to get the BS to build something, I did this: # check out empty package $ osc -A http://localhost:81 co openSUSE:Tools/obs-server $ cd openSUSE:Tools/obs-server # copy the files of obs-server from openSUSE BS into local pkg $ cp ~/src/obs/openSUSE:Tools/obs-server/* . $ > l insgesamt 4920 drwxr-xr-x 3 hp lisa 129 23. Jul 10:38 ./ drwxr-xr-x 4 hp lisa 34 23. Jul 10:38 ../ -rw-r--r-- 1 hp lisa 1256318 23. Jul 10:38 obs-server-2.0.4.tar.bz2 -rw-r--r-- 1 hp lisa 16382 23. Jul 10:38 obs-server.changes -rw-r--r-- 1 hp lisa 21961 23. Jul 10:38 obs-server.spec -rw-r--r-- 1 hp lisa 3738866 23. Jul 10:38 opensuse-themes-2.0.tar.bz2 drwxr-xr-x 2 hp lisa 85 23. Jul 10:38 .osc/ # add files and check in package $ osc -A http://localhost:81 add * A obs-server-2.0.4.tar.bz2 A obs-server.changes A obs-server.spec A opensuse-themes-2.0.tar.bz2 $ osc -A http://localhost:81 ci -m "initial commit" Sending obs-server-2.0.4.tar.bz2 Sending obs-server.changes Sending obs-server.spec Sending opensuse-themes-2.0.tar.bz2 Transmitting file data .... Committed revision 1. $ osc -A http://localhost:81 r openSUSE_11.1 x86_64 openSUSE_11.1 i586 unresolvable The webui Monitor says: nothing provides obs-common, nothing provides rubygem-rails-2_3 >= 2.3.5, nothing provides rubygem-rmagick, nothing provides build >= 2009.05.04, nothing provides perl-BSSolv How am I supposted to use zypper in this scenario? Puzzled and stuck, Pete P.S.: I'm really willing to fix the related documentation, but that implies, that I'm getting there... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org