[opensuse-kernel] Re: tumbleweed kernel packages not building
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now. Note that in current kernels we *have* common kernel-devel package generated from kernel-source. It contains generated sources after make prepare or alike I assume. And the kernel-flavor-devel contains flavor specific things. mmarek would know more, hopefully. BTW preload build needs kernel -debuginfo packages to be built... And since OBS is broken in the way it sometimes doesn't rebuild packages when you change debuginfo flag (like it happened now), you would need to trigger a rebuild for the kernels to have -debuginfo, i.e. to build preload... thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, Dec 08, 2010 at 10:20:20PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now.
Thanks, I've updated to your latest version and hopefully that will fix it. Note, how do I automatically update? I created the openSUSE:Tumbleweed/preload package as a link but not a "automatic update" link. I couldn't figure out how to update to your latest version without just deleting the package and adding the link back, which updated to yours. Is there an easier way to do this?
Note that in current kernels we *have* common kernel-devel package generated from kernel-source. It contains generated sources after make prepare or alike I assume. And the kernel-flavor-devel contains flavor specific things. mmarek would know more, hopefully.
Ah, ok.
BTW preload build needs kernel -debuginfo packages to be built... And since OBS is broken in the way it sometimes doesn't rebuild packages when you change debuginfo flag (like it happened now), you would need to trigger a rebuild for the kernels to have -debuginfo, i.e. to build preload...
I caused all of the packages to be rebuilt now, hopefully that will fix this issue where I had some debuginfo packages built and others not due to me changing the project properties last night. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, Dec 08, 2010 at 01:51:00PM -0800, Greg KH wrote:
On Wed, Dec 08, 2010 at 10:20:20PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now.
Thanks, I've updated to your latest version and hopefully that will fix it.
Nope, it's still unresolvable, look at the link above. Any ideas? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 12/09/2010 07:54 AM, Greg KH wrote:
On Wed, Dec 08, 2010 at 01:51:00PM -0800, Greg KH wrote:
On Wed, Dec 08, 2010 at 10:20:20PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now.
Thanks, I've updated to your latest version and hopefully that will fix it.
Nope, it's still unresolvable, look at the link above.
Any ideas?
Ah, I see. Your kernel packages don't have cicount="copy" in their links to kernel-source, so that their release number differs. The non-kernel-source _link should contain something like: <link package="kernel-source" cicount="copy" /> kernel-source is then (this one is OK in your repo): <link project="Kernel:stable" package="kernel-source" rev="a977934d0233d78783be2dacb7a63a52" baserev="a977934d0233d78783be2dacb7a63a52"> And when you want to update to the later kernel, you just change the revs. The other option is to not link kernel:stable and have a local copy and then we would update kernel-source by standard submit requests/accepts. You also have some kind of weird links. If you check out your unexpanded non-kernel-source packages, the sources are there, however only _link should be there. Compare osc co -u openSUSE:Tumbleweed kernel-default e.g. with osc co -u openSUSE:Factory kernel-default If you stay with kernel-source link to kernel:stable (and not a local copy like I wrote above), then there should be also only _link and not full source in unexpanded tree. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 12/09/2010 10:30 AM, Jiri Slaby wrote:
On 12/09/2010 07:54 AM, Greg KH wrote:
On Wed, Dec 08, 2010 at 01:51:00PM -0800, Greg KH wrote:
On Wed, Dec 08, 2010 at 10:20:20PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now.
Thanks, I've updated to your latest version and hopefully that will fix it.
Nope, it's still unresolvable, look at the link above.
Any ideas?
Ah, I see. Your kernel packages don't have cicount="copy" in their links to kernel-source, so that their release number differs.
The non-kernel-source _link should contain something like: <link package="kernel-source" cicount="copy" /> kernel-source is then (this one is OK in your repo): <link project="Kernel:stable" package="kernel-source" rev="a977934d0233d78783be2dacb7a63a52" baserev="a977934d0233d78783be2dacb7a63a52">
And when you want to update to the later kernel, you just change the revs. The other option is to not link kernel:stable and have a local copy and then we would update kernel-source by standard submit requests/accepts.
You also have some kind of weird links. If you check out your unexpanded non-kernel-source packages, the sources are there, however only _link should be there. Compare osc co -u openSUSE:Tumbleweed kernel-default e.g. with osc co -u openSUSE:Factory kernel-default
If you stay with kernel-source link to kernel:stable (and not a local copy like I wrote above), then there should be also only _link and not full source in unexpanded tree.
Perhaps granting me maintainer permissions temporarily so that I fix it all up and then drop them is an option? regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 09, 2010 at 10:34:40AM +0100, Jiri Slaby wrote:
On 12/09/2010 10:30 AM, Jiri Slaby wrote:
On 12/09/2010 07:54 AM, Greg KH wrote:
On Wed, Dec 08, 2010 at 01:51:00PM -0800, Greg KH wrote:
On Wed, Dec 08, 2010 at 10:20:20PM +0100, Jiri Slaby wrote:
On 12/08/2010 10:00 PM, Greg KH wrote:
Hi Jiri,
I've tried importing the Kernel:stable branch into tumbleweed, but it's not able to build the preload kernel module for some odd reason:
nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-default-devel = 2.6.36.1-2 needed by kernel-syms, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-desktop-devel, nothing provides kernel-devel = 2.6.36.1-2 needed by kernel-xen-devel
You can see this at the page at: https://build.opensuse.org/stage/project/monitor?project=openSUSE%3ATumblewe...
I haven't added a few missing kernel builds at the moment (vmi, tracing, docs), but I don't think that should be causing this error to show up.
It's odd that kernel-devel is being asked for, as I didn't think that was really provided by any package anymore.
Hi, I though it will cause problems. I tried to persuade preload to build on all the repos I had there, but the change in preamble I did causes these kind of problems. I reverted it now.
Thanks, I've updated to your latest version and hopefully that will fix it.
Nope, it's still unresolvable, look at the link above.
Any ideas?
Ah, I see. Your kernel packages don't have cicount="copy" in their links to kernel-source, so that their release number differs.
<snip> Ah, yeah, now I remember, setting up the kernel packages was a pain, it was a few years ago that I did the same thing for the moblin repo, and I forgot how I did all that.
Perhaps granting me maintainer permissions temporarily so that I fix it all up and then drop them is an option?
I would _love_ that. What's your obs id? 'jslaby' didn't seem to work. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 12/09/2010 04:40 PM, Greg KH wrote:
Perhaps granting me maintainer permissions temporarily so that I fix it all up and then drop them is an option?
I would _love_ that. What's your obs id? 'jslaby' didn't seem to work.
It's jirislaby. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 09, 2010 at 04:43:04PM +0100, Jiri Slaby wrote:
On 12/09/2010 04:40 PM, Greg KH wrote:
Perhaps granting me maintainer permissions temporarily so that I fix it all up and then drop them is an option?
I would _love_ that. What's your obs id? 'jslaby' didn't seem to work.
It's jirislaby.
Nice, you are now added and feel free to fix up the kernel packages however you wish to do so. I really appreciate this. greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 12/09/2010 04:50 PM, Greg KH wrote:
Nice, you are now added and feel free to fix up the kernel packages however you wish to do so.
OK, it's building now, so let's see what happens in the next few hours.
I really appreciate this.
You are welcome. Later, when you want to update the kernel from Kernel:stable, just do this: osc linkpac -f -r a977934d0233d78783be2dacb7a63a52 Kernel:stable kernel-source openSUSE:Tumbleweed where you change the -r parameter to the revision you want to "check in". The revisions can be found in the output of: osc log Kernel:stable kernel-source regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 09, 2010 at 05:07:19PM +0100, Jiri Slaby wrote:
On 12/09/2010 04:50 PM, Greg KH wrote:
Nice, you are now added and feel free to fix up the kernel packages however you wish to do so.
OK, it's building now, so let's see what happens in the next few hours.
I really appreciate this.
You are welcome.
Later, when you want to update the kernel from Kernel:stable, just do this: osc linkpac -f -r a977934d0233d78783be2dacb7a63a52 Kernel:stable kernel-source openSUSE:Tumbleweed
Ah, that's how you do that, I was trying to figure that out, thanks, I'll go print this out and save it. Also feel free to update the version of the kernel in tumbleweed whenever you feel it should be if you want to. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
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 Or maybe downgrading preload to some lower version should solve that too. However I don't think, it's something we should go for. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
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...
Or maybe downgrading preload to some lower version should solve that too. However I don't think, it's something we should go for.
Nope, I have no problem adding additional packages, that's what this repo is for :) I'll go add those now... Now added and building. 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. 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? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
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
On Thursday 09 December 2010 23:48:19 Jiri Slaby wrote:
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
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.
* 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 target. 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. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 12/09/2010 08:59 PM, Adrian Schröter wrote:
On Thursday 09 December 2010 23:48:19 Jiri Slaby wrote:
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
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 target.
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 _link too? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 09, 2010 at 08:59:25PM +0100, Adrian Schröter wrote:
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 ...
Ok, any pointers to where I can learn the cli better for stuff like "setting up entire distros"? Any help is appreciated. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Thu, Dec 09, 2010 at 11:48:19PM +0100, Jiri Slaby wrote:
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.
I don't think so, it looks like the _link file it creates is a "just point to that repo over there and stay up to date".
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?
Yeah, I think I need to take this to a different list for that, I'll do that now... thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Well, adrian is away, let's try the list. On 12/09/2010 11:48 PM, Jiri Slaby wrote:
On 12/09/2010 11:38 PM, Greg KH wrote:
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
On Thu, Dec 09, 2010 at 02:38:15PM -0800, 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...
Or maybe downgrading preload to some lower version should solve that too. However I don't think, it's something we should go for.
Nope, I have no problem adding additional packages, that's what this repo is for :)
I'll go add those now...
Now added and building.
And it all looks good. I just synced a virtual machine with the repo and rebooted and it works. Nice job, thanks for all of your help here. greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (3)
-
Adrian Schröter -
Greg KH -
Jiri Slaby