On 12/09/2010 11:38 PM, Greg KH wrote:
On Thu, Dec 09, 2010 at 10:50:36PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:51 PM, Greg KH wrote:
Thanks, I've updated to your latest version and hopefully that will fix it.
Bah, after few hours of debugging, I found out that we need updated elfutils and systemtap to persuade stap not to crash during the preload build.
So if you want preload you should do something like: osc linkpac -c devel:tools systemtap openSUSE:Tumbleweed osc linkpac -c Base:System elfutils openSUSE:Tumbleweed
Really? That's wierd, why would those be needed for the kernel? oh, preload, ok, that makes sense now...
Yeah, there is some kind of black magic behind in the preload package.
Oh, I don't think we want to use '-c' for linkpac here, right? We need to manually handle updates, not blindly accept them for now.
-c means stick to the revision it's there now and do not move forward if they update the package in their repo. At least I understand it that way.
If I manually do a 'osc linkpac -r REVISION ...' it seems to look like a different type of link than if I use the web gui to create a link that is a reference as well. Any clues as to why that is?
Different in what way? I'm no expert on the web GUI, I only know, it always does different thing than I wish to do myself ;). The differences I see are: * it creates the _link with both rev and baserev attributes which I didn't find what each of them is for or what's the difference * it copies all the files to the local repository, so I have no idea why it bothers with creating the _link at all. Maybe for easier submit requests? Perhaps some BS guru can explain us? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org