On Tue, Nov 01, 2011 at 12:32:30PM +0100, Adrian Schröter wrote:
Am Dienstag, 1. November 2011, 10:24:53 schrieb Jiri Slaby:
On 10/17/2011 07:30 PM, Greg KH wrote:
Hi Adrian,
We talked at brainshare about the "correct" way to link packages in Tumbleweed, and unfortunatly, I forgot one of the steps as I can't get it to work now.
Here's what I remember: - look up the xsrcmd5 from the "root" package. For example, in the
X11:xfce midori package I would do something like: osc api /source/X11:xfce/midori | grep linkinfo | pick out xsrcmd5
(where 'pick out' is a regex)
- then run 'osc setlinkrev' with that md5 in the Tumbleweed repo.
hm, just running
osc setlinkrev $PROJECT $PACKAGE
or inside of a checked out package is setting it to the current xsrcmd5. No need to lookup it yourself.
Alternative solution would be to run
osc api /source/X11:xfce/midori?expand=1
and pick srcmd5 from directory, this is the effective sourcemd5 of the merged sources.
That seems to be the best one.
Or, maybe best way would be to use the srcmd5 of last successful build:
osc api /build/X11:xfce/openSUSE_Factory/i586/midori/_history
only successfull builds are in this history. this is also the merged source md5.
Hm, that command doesn't work for me here: $ osc api /build/devel:tools:scm/openSUSE_Factory/quilt/_history Server returned an error: HTTP Error 404: Not Found devel:tools:scm/_history I'm guessing that this requires the build repo to also be known for a specific package? Anyway, the srcmd5 from the /source/ directory command above seems to work well for what we need. If the package isn't building properly in the repo, we shouldn't be taking it in the first place :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org