On 12/09/2010 08:59 PM, Adrian Schröter wrote:
On Thursday 09 December 2010 23:48:19 Jiri Slaby
On 12/09/2010 11:38 PM, Greg KH wrote:
On Thu, Dec 09, 2010 at 10:50:36PM +0100, Jiri
On 12/08/2010 10:51 PM, Greg KH wrote:
> Thanks, I've updated to your latest version and hopefully that will
Bah, after few hours of debugging, I found out that we need updated
elfutils and systemtap to persuade stap not to crash during the
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
seriously, the webui is not designed to setup entire distros. It is good
for getting an overview and to do simple things. But you should really learn
osc CLI for your task ...
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
rev is for refering a revision to take.
baserev is information for merging.
Thanks for explanation, could you add it to the wiki (not that anybody
is able to find something in the wiki, but at least it will be there).
* 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?
It is also used when creating a submit request to avoid the need to specify a
Yes, that's exactly what I meant.
But more important it specifies how sources should get
merged with the source
package, handle checkin counter (first part of release number) and so on.
Keep in mind that we usually auto-merge sources without doing commits to show
always the current build state (not in your case, where you freeze the
version). This is a bit different then with classic SCM system where source
changes only happen manually.
/me quite confused now, to stick to one concrete source, is it enough to
linkpac -c, or do I need to have a local copy of the sources along the
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org