[opensuse-kernel] Factory update to kernel 2.6.34-rc2 coming
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - 2.6.34-rc2 was tagged over the weekend so I completed the integration with the master branch. KOTD and Kernel:HEAD kernels will be building shortly and once I've gotten a successful round of builds I'll submit to Factory. Since it's an -rc2 release there will probably be some hiccups, and we'd love to get feedback on them. If you run into an issue it would be awesome if you could also confirm whether the issue is in the -vanilla kernel so we know whether to file upstream bugs or not. Thanks and happy testing! - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkunn8IACgkQLPWxlyuTD7J1pgCcCbp/SaGGFJygNfd+f5C+sEI1 UkQAn3heWkXC7KNUG+ib1Lfl/gRSZ3z+ =hf4s -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Mon, Mar 22, 2010 at 9:50 AM, Jeff Mahoney <jeffm@suse.com> wrote:
2.6.34-rc2 was tagged over the weekend so I completed the integration with the master branch. KOTD and Kernel:HEAD kernels will be building shortly and once I've gotten a successful round of builds I'll submit to Factory.
Will the .34-rc2 builds also be pushed to the 11.2-variants, http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2 http://download.opensuse.org/repositories/Kernel:/openSUSE-11.2/openSUSE_11.... Thanks! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/22/2010 12:57 PM, 0bo0 wrote:
On Mon, Mar 22, 2010 at 9:50 AM, Jeff Mahoney <jeffm@suse.com> wrote:
2.6.34-rc2 was tagged over the weekend so I completed the integration with the master branch. KOTD and Kernel:HEAD kernels will be building shortly and once I've gotten a successful round of builds I'll submit to Factory.
Will the .34-rc2 builds also be pushed to the 11.2-variants,
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2
Yes. This just builds against the openSUSE 11.2 repository. This will happen automatically.
http://download.opensuse.org/repositories/Kernel:/openSUSE-11.2/openSUSE_11....
No. This is the openSUSE 11.2 kernel branch and receives fixes from the 11.2 stream. You can check out the branch itself at http://gitorious.org/opensuse/kernel-source/commits/openSUSE-11.2 - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkunoo0ACgkQLPWxlyuTD7LcZgCdFsLEX6OyPPSL+fXZToH1gF/0 owQAn373vgt6h1ssc6ugIEISoyHYReWe =RNeF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
hi, On Mon, Mar 22, 2010 at 10:02 AM, Jeff Mahoney <jeffm@suse.com> wrote:
Will the .34-rc2 builds also be pushed to the 11.2-variants,
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2
Found them, thanks. No kernel-xen there? Checking @, https://build.opensuse.org/platform/show?name=openSUSE_11.2&project=Kernel%3AHEAD kernel-xen seems to be a build target, but @, https://build.opensuse.org/package/show?package=kernel-xen&project=Kernel%3AHEAD the builds report 'excluded' ... Can you clarify? Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2010 11:11 AM, 0bo0 wrote:
hi,
On Mon, Mar 22, 2010 at 10:02 AM, Jeff Mahoney <jeffm@suse.com> wrote:
Will the .34-rc2 builds also be pushed to the 11.2-variants,
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2
Found them, thanks.
No kernel-xen there?
Checking @,
https://build.opensuse.org/platform/show?name=openSUSE_11.2&project=Kernel%3AHEAD
kernel-xen seems to be a build target, but @,
https://build.opensuse.org/package/show?package=kernel-xen&project=Kernel%3AHEAD
the builds report 'excluded' ...
Can you clarify?
Sure. Xen is almost always excluded in the early builds following a version update. It's quite a bit patch set and I don't want to hold up testing on all the other flavors until Xen is ready. So perhaps I spoke too soon when I said that I'll be updating Factory as soon as I get good builds. Coolo, what's your opinion here? 2.6.34-rc2 or xen? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuo20IACgkQLPWxlyuTD7JfIACeMWHwM3mhOGTsYXwWG6YC7rFD XLEAoI8rLXW59pMZf4CyLA+ojzGcDS0l =sM4f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 23, 2010 at 8:16 AM, Jeff Mahoney <jeffm@suse.com> wrote:
Can you clarify?
Sure. Xen is almost always excluded in the early builds following a version update. It's quite a bit patch set and I don't want to hold up testing on all the other flavors until Xen is ready.
So perhaps I spoke too soon when I said that I'll be updating Factory as soon as I get good builds.
Coolo, what's your opinion here? 2.6.34-rc2 or xen?
understood. fwiw, the interest in 2.6.24-rc2 kernel-xen, around here anyway, *is* to be able to deploy/test -- simply in a Guest. atm, my _specific_ interest is in the state/capability of btrfs in the 'new' .34 kernels. Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Dienstag 23 März 2010 schrieb Jeff Mahoney:
Sure. Xen is almost always excluded in the early builds following a version update. It's quite a bit patch set and I don't want to hold up testing on all the other flavors until Xen is ready.
So perhaps I spoke too soon when I said that I'll be updating Factory as soon as I get good builds.
Coolo, what's your opinion here? 2.6.34-rc2 or xen?
That depends on the time frame for the xen flavor. M4 is about to be synced to the mirrors, so there is a pretty big time window for 2.6.34 to stabilize enough for M5. But M5 should have xen I believe. After all it's almost feature freeze time. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Stephan Kulow <coolo@suse.de> 23.03.10 17:51 >>> That depends on the time frame for the xen flavor. M4 is about to be synced to the mirrors, so there is a pretty big time window for 2.6.34 to stabilize enough for M5. But M5 should have xen I believe. After all it's almost feature freeze time.
I hope to get started with it later this week. Without having started (i.e. having seen how much merging work I'll have to go through), I can't really estimate how long it will take until an initial commit. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 23, 2010 at 10:00 AM, Jan Beulich <JBeulich@novell.com> wrote:
Stephan Kulow <coolo@suse.de> 23.03.10 17:51 >>> That depends on the time frame for the xen flavor. M4 is about to be synced to the mirrors, so there is a pretty big time window for 2.6.34 to stabilize enough for M5. But M5 should have xen I believe. After all it's almost feature freeze time.
I hope to get started with it later this week. Without having started (i.e. having seen how much merging work I'll have to go through), I can't really estimate how long it will take until an initial commit.
Understood. Whatever the solution, might we maintain a version-consistent repo _somewhere_ in the interim? E.g., until yesterday, .../Kernel:/HEAD/openSUSE_11.2/x86_64 *had* both kernel-server & kernel-xen -- both .33 versions. Today's update removes the kernel-xen from the repo, and zypper updates 'offer' upgrade to kernel-server anyway which, if accepted, would leave us with version-inconsistent install. The only option would seem to be (?) to *downgrade* to another repo that has both flavors in the same version ... Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2010 01:04 PM, 0bo0 wrote:
On Tue, Mar 23, 2010 at 10:00 AM, Jan Beulich <JBeulich@novell.com> wrote:
Stephan Kulow <coolo@suse.de> 23.03.10 17:51 >>> That depends on the time frame for the xen flavor. M4 is about to be synced to the mirrors, so there is a pretty big time window for 2.6.34 to stabilize enough for M5. But M5 should have xen I believe. After all it's almost feature freeze time.
I hope to get started with it later this week. Without having started (i.e. having seen how much merging work I'll have to go through), I can't really estimate how long it will take until an initial commit.
Understood.
Whatever the solution, might we maintain a version-consistent repo _somewhere_ in the interim?
E.g., until yesterday,
.../Kernel:/HEAD/openSUSE_11.2/x86_64
*had* both kernel-server & kernel-xen -- both .33 versions.
Today's update removes the kernel-xen from the repo, and zypper updates 'offer' upgrade to kernel-server anyway which, if accepted, would leave us with version-inconsistent install. The only option would seem to be (?) to *downgrade* to another repo that has both flavors in the same version ...
I'll let Michal comment further, but my initial answer is "not really." Kernel:HEAD is just the packaged up version of the kernel git repo. It's the kernel development project so there will definitely be some churn. We keep the versions synced in Factory which is really the only place it's important. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuo+ysACgkQLPWxlyuTD7KvnwCfRTd49KESMCwIOh2s63q0SzlA ftkAnju376wIrR4njjw8S3K9GKCs6edG =C8rs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Hi, On Tue, Mar 23, 2010 at 10:32 AM, Jeff Mahoney <jeffm@suse.com> wrote:
We keep the versions synced in Factory which is really the only place it's important.
My attempted point was simply that it's also 'important' to have sync'd for us "11.2-ers". To date, the ONLY place that's available -- with .33 kernels, anyway -- has been the HEAD repos. Now, that's no longer the case. Upgrading to Factory is simply not (yet) an option ...
It's the kernel development project so there will definitely be some churn.
I certainly expect occasional kernel breakage -- that's life with HEAD. And we're "here" to test/report. But, tbh, playing whack-a-mole with repos to just find one that consistently HAS the kernel-flavor one's working with is ... challenging. A disappearing flavor -- with a "whenever" for a return-eta -- is more regression than breakage. Depends on your expectations of 'churn', I understand. I'm curious -- what would YOU recommend for those of us who have been tracking the .33 kernels in multiple-flavors @ HEAD. The old files we HAD are gone, and the new files we NEED won't appear for awhile. Again, there seems to be NO option that's been made available -- other than downgrade. Am I missing something? Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
I've been poking around through the build projects and repos ... does kernel-source-2.6.33-34.1.noarch package exist _anywhere_ we can get it, anymore? I'm happy to manage manually until if/when kernel-xen catches up to the rest of HEAD's kernel flavors, but at least need to get at the source ... which, atm, is also only availble as kernel-source-2.6.34-rc2.1.1.noarch.rpm. Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2010 08:08 PM, 0bo0 wrote:
I've been poking around through the build projects and repos ... does kernel-source-2.6.33-34.1.noarch package exist _anywhere_ we can get it, anymore?
I'm happy to manage manually until if/when kernel-xen catches up to the rest of HEAD's kernel flavors, but at least need to get at the source ... which, atm, is also only availble as kernel-source-2.6.34-rc2.1.1.noarch.rpm.
The RPM isn't available, but you can always build it again yourself via gitorious. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkupZQQACgkQLPWxlyuTD7K0AwCeMRdZMpgokYElynrvhVlEun/F 4j4An2wh7j2A+z7/A1d+NXNusAVSf2P1 =Bdxa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2010 09:04 PM, Jeff Mahoney wrote:
On 03/23/2010 08:08 PM, 0bo0 wrote:
I've been poking around through the build projects and repos ... does kernel-source-2.6.33-34.1.noarch package exist _anywhere_ we can get it, anymore?
I'm happy to manage manually until if/when kernel-xen catches up to the rest of HEAD's kernel flavors, but at least need to get at the source ... which, atm, is also only availble as kernel-source-2.6.34-rc2.1.1.noarch.rpm.
The RPM isn't available, but you can always build it again yourself via gitorious.
BTW this is one of the reasons why some of us have been pushing for true version control in OBS. It'd be so easy to just say, build using this revision. Also, what you want in gitorious is to checkout the rpm-2.6.33-5 tag from the master branch. Then you can do "scripts/tar-up.sh" and that creates a kernel-source directory that contains what the src rpm would. You can build the binary kernel or the source RPM from it. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkupZZcACgkQLPWxlyuTD7IYXQCggLspAwUNgFP8KMFxQHFH4RnV PNYAnA5Z4N+aoxpic0E5ygs1M9eSrsDl =MbhI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 23, 2010 at 6:06 PM, Jeff Mahoney <jeffm@suse.com> wrote:
The RPM isn't available, but you can always build it again yourself via gitorious.
Also, what you want in gitorious is to checkout the rpm-2.6.33-5 tag from the master branch. Then you can do "scripts/tar-up.sh" and that creates a kernel-source directory that contains what the src rpm would. You can build the binary kernel or the source RPM from it.
alright, then. doable. i'm hoping you manage to see my point, however ...
BTW this is one of the reasons why some of us have been pushing for true version control in OBS. It'd be so easy to just say, build using this revision.
i'll certainly second that. further, i'd offer a suggestion to have a "don't completely cripple a repo ... even if it's HEAD" policy considered. maybe only for rather 'core' repos -- like Kernel:HEAD. admittedly, i don't know your infrastructure limitations, but "would've been nice" to simply branch/tag the package repo with all working .33 kernel flavors, keeping it available until the .34 repo at least achieved content parity -- whenever that happens. after all, we are asked to 'test' -- but then have to unwind significantly when even the test-able infrastructure gets horked. thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Mittwoch 24 März 2010 schrieb 0bo0:
admittedly, i don't know your infrastructure limitations, but "would've been nice" to simply branch/tag the package repo with all working .33 kernel flavors, keeping it available until the .34 repo at least achieved content parity -- whenever that happens. after all, we are asked to 'test' -- but then have to unwind significantly when even the test-able infrastructure gets horked.
This is done. It was an explicit decision of Jeff (and others before him) to disable kernel-xen for the moment. That's why it's HEAD not STABLE I guess. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 23.3.2010 19:02, 0bo0 wrote:
Hi,
On Tue, Mar 23, 2010 at 10:32 AM, Jeff Mahoney <jeffm@suse.com> wrote:
We keep the versions synced in Factory which is really the only place it's important.
My attempted point was simply that it's also 'important' to have sync'd for us "11.2-ers". To date, the ONLY place that's available -- with .33 kernels, anyway -- has been the HEAD repos. Now, that's no longer the case.
Upgrading to Factory is simply not (yet) an option ...
I guess a Kernel:Backport project copying (*) the Factory packages would be a cheap solution to this. Adding and additional "stable" stage between Kernel:HEAD and Factory would not be a good idea IMO, as it would require more work to submit kernels to Factory. (*) We don't even need to rebuild the packages for openSUSE $x.$y, just copy the rpms using _aggregates. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
At Tue, 23 Mar 2010 11:02:33 -0700, 0bo0 wrote:
I'm curious -- what would YOU recommend for those of us who have been tracking the .33 kernels in multiple-flavors @ HEAD. The old files we HAD are gone, and the new files we NEED won't appear for awhile. Again, there seems to be NO option that's been made available -- other than downgrade.
FYI, I hold kernel packages of discontinued versions in my OBS repo. The last 2.6.33 SUSE kernel is found in home:tiwai:kernel:2.6.33 repo. There are also 2.6.29 and 2.6.30. 2.6.31 and 32 aren't there since they are still tracked as SLE11 and 11.2 official kernels. Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Wed, Mar 24, 2010 at 3:33 AM, Takashi Iwai <tiwai@suse.de> wrote:
FYI, I hold kernel packages of discontinued versions in my OBS repo. The last 2.6.33 SUSE kernel is found in home:tiwai:kernel:2.6.33 repo. There are also 2.6.29 and 2.6.30.
2.6.31 and 32 aren't there since they are still tracked as SLE11 and 11.2 official kernels.
that's very useful, thanks. and, it addresses the issue of keeping 'stable' Factory-based kernels (atm, .33) around for Factory & 11.2 -- until .34 achieves the aforementioned content parity. Michal, it's not so much an issue of creating another set of kernel builds to be tested, but just _keeping_ the 'stable' .33-release-based Factory/11.2 kernel packages available. Maybe just the _last_ available, stable pkgs ... again, maybe 'just' until the .34-release. tbh, keeping the last available packages of each stable release in a closed repo wouldn't hurt either -- and would take little resource. simply for use-case example, and in an admittedly different application, linode.com does a nice job of keeping old, known-working kernels packages around (http://www.linode.com/kernels/). it's VERY useful to be able to switch when neede without having to build from sources ... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
it's likely obvious, but the following scenario is what we're trying to avoid. examples are a good thing ... rpm -qa | grep -i ^kernel kernel-debug-devel-2.6.33-34.1.x86_64 kernel-xen-devel-2.6.33-34.1.x86_64 kernel-desktop-devel-2.6.33-34.1.x86_64 kernel-default-2.6.33-34.1.x86_64 kernel-default-devel-2.6.33-34.1.x86_64 kernel-source-2.6.33-34.1.noarch kernel-syms-2.6.33-34.1.x86_64 kernel-xen-2.6.33-34.1.x86_64 zypper dup Computing upgrade... ... The following packages are going to be upgraded: kernel-default 2.6.33-34.1 -> 2.6.34-rc2.1.1 x86_64 KernelHEAD obs://build.opensuse.org/Kernel The following packages are going to be downgraded: kernel-debug-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-default-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-desktop-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-source 2.6.33-34.1 -> 2.6.31.12-0.2.1 noarch OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-syms 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-xen 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-xen-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE The following packages are going to change vendor: kernel-debug-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-default-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-desktop-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-source 2.6.33-34.1 -> 2.6.31.12-0.2.1 noarch OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-syms 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-xen 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE kernel-xen-devel 2.6.33-34.1 -> 2.6.31.12-0.2.1 x86_64 OS11-update obs://build.opensuse.org/Kernel -> openSUSE ... I've yet to figure out how to _prevent_ this solution. trying, cat << EOF >> /etc/zypp/locks repo: OS11-oss type: package match_type: glob case_sensitive: on solvable_name: kernel-* repo: OS11-update type: package match_type: glob case_sensitive: on solvable_name: kernel-* EOF results in an arguably more confused, zypper dup ... Computing upgrade... 2 Problems: Problem: problem with installed package kernel-xen-2.6.33-34.1.x86_64 Problem: problem with installed package kernel-xen-devel-2.6.33-34.1.x86_64 Problem: problem with installed package kernel-xen-2.6.33-34.1.x86_64 Solution 1: keep kernel-xen-2.6.33-34.1.x86_64 Solution 2: do not forbid installation of kernel-xen-2.6.31.12-0.2.1.x86_64[OS11-update] Solution 3: do not forbid installation of kernel-xen-2.6.31.12-0.1.1.x86_64[OS11-update] Solution 4: do not forbid installation of kernel-xen-2.6.31.8-0.1.1.x86_64[OS11-update] Solution 5: do not forbid installation of kernel-xen-2.6.31.5-0.1.1.x86_64[OS11-oss] Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c] (c): 1 Applying solution 1 Problem: problem with installed package kernel-xen-devel-2.6.33-34.1.x86_64 Solution 1: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.5-0.1.1.i586[OS11-oss] install kernel-xen-devel-2.6.31.5-0.1.1.i586 despite the inferior architecture do not forbid installation of kernel-source-2.6.31.5-0.1.1.noarch[OS11-oss] Solution 2: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.5-0.1.1.x86_64[OS11-oss] do not forbid installation of kernel-source-2.6.31.5-0.1.1.noarch[OS11-oss] Solution 3: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.8-0.1.1.i586[OS11-update] install kernel-xen-devel-2.6.31.8-0.1.1.i586 despite the inferior architecture do not forbid installation of kernel-source-2.6.31.8-0.1.1.noarch[OS11-update] Solution 4: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.8-0.1.1.x86_64[OS11-update] do not forbid installation of kernel-source-2.6.31.8-0.1.1.noarch[OS11-update] Solution 5: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.12-0.1.1.i586[OS11-update] install kernel-xen-devel-2.6.31.12-0.1.1.i586 despite the inferior architecture do not forbid installation of kernel-source-2.6.31.12-0.1.1.noarch[OS11-update] Solution 6: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.12-0.1.1.x86_64[OS11-update] do not forbid installation of kernel-source-2.6.31.12-0.1.1.noarch[OS11-update] Solution 7: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.12-0.2.1.i586[OS11-update] install kernel-xen-devel-2.6.31.12-0.2.1.i586 despite the inferior architecture do not forbid installation of kernel-source-2.6.31.12-0.2.1.noarch[OS11-update] Solution 8: Following actions will be done: do not forbid installation of kernel-xen-devel-2.6.31.12-0.2.1.x86_64[OS11-update] do not forbid installation of kernel-source-2.6.31.12-0.2.1.noarch[OS11-update] Solution 9: deinstallation of kernel-xen-devel-2.6.33-34.1.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/6/7/8/9/s/r/c] (c): ... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 23, 2010 at 10:00 AM, Jan Beulich <JBeulich@novell.com> wrote:
I hope to get started with it later this week. Without having started (i.e. having seen how much merging work I'll have to go through), I can't really estimate how long it will take until an initial commit.
uname -a Linux nas 2.6.34-rc2-git3-5-xen #1 SMP 2010-03-29 21:26:59 +0200 x86_64 x86_64 x86_64 GNU/Linux more or less back in business ... thanks! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/30/2010 10:33 AM, 0bo0 wrote:
On Tue, Mar 23, 2010 at 10:00 AM, Jan Beulich <JBeulich@novell.com> wrote:
I hope to get started with it later this week. Without having started (i.e. having seen how much merging work I'll have to go through), I can't really estimate how long it will take until an initial commit.
uname -a Linux nas 2.6.34-rc2-git3-5-xen #1 SMP 2010-03-29 21:26:59 +0200 x86_64 x86_64 x86_64 GNU/Linux
more or less back in business ... thanks!
I've submitted this to Factory. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuyDC0ACgkQLPWxlyuTD7LLwwCfZFpPFHrBCx8IaS80ygrW+nHT JMMAnjeSq9xQnhDtok3AkCj1qxezM1q3 =lYI6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 30, 2010 at 7:35 AM, Jeff Mahoney <jeffm@suse.com> wrote:
uname -a Linux nas 2.6.34-rc2-git3-5-xen #1 SMP 2010-03-29 21:26:59 +0200 x86_64 x86_64 x86_64 GNU/Linux
more or less back in business ... thanks!
I've submitted this to Factory.
afayk, will .34 in either Factory or :HEAD pull btrfs only from upstream mainline? or are there plans to pull/build a .34 + btrfs-unstable branch? i understand that 'they' are lagging behind in btrfs-unstable merges into mainline, and that ultimately that's where the issue needs to be resolved, but "would be nice" to be able to test opensuse-"next"-kernel with a usable (btrfs stable/release @ v0.19 is just too 'dusty' ...) btrfs. just asking ... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/30/2010 10:48 AM, 0bo0 wrote:
On Tue, Mar 30, 2010 at 7:35 AM, Jeff Mahoney <jeffm@suse.com> wrote:
uname -a Linux nas 2.6.34-rc2-git3-5-xen #1 SMP 2010-03-29 21:26:59 +0200 x86_64 x86_64 x86_64 GNU/Linux
more or less back in business ... thanks!
I've submitted this to Factory.
afayk, will .34 in either Factory or :HEAD pull btrfs only from upstream mainline? or are there plans to pull/build a .34 + btrfs-unstable branch?
i understand that 'they' are lagging behind in btrfs-unstable merges into mainline, and that ultimately that's where the issue needs to be resolved, but "would be nice" to be able to test opensuse-"next"-kernel with a usable (btrfs stable/release @ v0.19 is just too 'dusty' ...) btrfs.
No. We're only going to package up the mainline kernel with our usual patch set and backported fixes. I may grab some patches from btrfs once 2.6.34-final is released, but I'm not planning on packaging anything up before that. I've mentioned this on the list before, but there is a btrfs-kmp package that is somewhat out of date. I'd accept submit requests for it, but just don't have the time to keep it updated myself. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuyEIQACgkQLPWxlyuTD7KhjQCeNfnpwjkn5s6phiA8ScAzh8Fs ApcAn2klUdLG/aqlGn729HI5Zna5SvxM =Uwbo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 30, 2010 at 7:53 AM, Jeff Mahoney <jeffm@suse.com> wrote:
there is a btrfs-kmp package that is somewhat out of date. I'd accept submit requests for it, but just don't have the time to keep it updated myself.
might you know of any good step-by-steps on how to build/maintain a kmp @ obs? tried a long while ago, but couldn't get the hang of it and, similarly, just don't have the time to keep fighting with it myself. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 30, 2010 at 11:01 AM, 0bo0 <0.bugs.only.0@gmail.com> wrote:
On Tue, Mar 30, 2010 at 7:53 AM, Jeff Mahoney <jeffm@suse.com> wrote:
there is a btrfs-kmp package that is somewhat out of date. I'd accept submit requests for it, but just don't have the time to keep it updated myself.
might you know of any good step-by-steps on how to build/maintain a kmp @ obs?
tried a long while ago, but couldn't get the hang of it and, similarly, just don't have the time to keep fighting with it myself.
I've just been struggling with that myself. Step 1: ignore most of the ones on the OBS currently. Most of the spec files are kludged together from what I can tell. They are way too complex and hard to work with. Step 2: Download and optionally read: http://developer.novell.com/wiki/images/8/80/Kmpm-code11.pdf Step 3: Use the sample spec file at the end of that document as your starting place. HTH Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV AiredForensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev... The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 30, 2010 at 8:35 AM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I've just been struggling with that myself.
Step 1: ignore most of the ones on the OBS currently. Most of the spec files are kludged together from what I can tell. They are way too complex and hard to work with.
agreed. to all points. given the frequency with which it's suggested "DIY @ OBS", the boat's been rather badly missed on the whole "teach a man to fish ..." opportunity to get more involvement.
Step 2: Download and optionally read: http://developer.novell.com/wiki/images/8/80/Kmpm-code11.pdf Step 3: Use the sample spec file at the end of that document as your starting place.
JUST found that referenced at the bottom of http://forums.novell.com/newsflash/whats-new-product-specific-feed/whats-new... ... Reading now. Thanks! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Tue, Mar 30, 2010 at 11:45 AM, 0bo0 <0.bugs.only.0@gmail.com> wrote:
On Tue, Mar 30, 2010 at 8:35 AM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
I've just been struggling with that myself.
Step 1: ignore most of the ones on the OBS currently. Most of the spec files are kludged together from what I can tell. They are way too complex and hard to work with.
agreed. to all points. given the frequency with which it's suggested "DIY @ OBS", the boat's been rather badly missed on the whole "teach a man to fish ..." opportunity to get more involvement.
Step 2: Download and optionally read: http://developer.novell.com/wiki/images/8/80/Kmpm-code11.pdf Step 3: Use the sample spec file at the end of that document as your starting place.
JUST found that referenced at the bottom of http://forums.novell.com/newsflash/whats-new-product-specific-feed/whats-new... ...
Reading now. Thanks!
Thanks for the reference to that webpage it looks very interesting as well. ie. I'm still struggling to get my KMP(s) the way I want them. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV AiredForensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev... The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (7)
-
0bo0 -
Greg Freemyer -
Jan Beulich -
Jeff Mahoney -
Michal Marek -
Stephan Kulow -
Takashi Iwai