Mailinglist Archive: opensuse-factory (838 mails)

< Previous Next >
Re: [opensuse-factory] kernel 2.6.37.2 for 11.4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/15/2011 10:47 AM, Felix Miata wrote:
On 2011/03/15 06:54 (GMT-0700) Greg KH composed:

On Tue, Mar 15, 2011 at 12:28:14AM -0400, Felix Miata wrote:

>On 2011/03/01 11:06 (GMT+0100) Stephan Kulow composed:

>> I would like to get some feedback on updating from 2.6.37.1 to
2.6.37.2 at
>> this point, so please give
>>
http://download.opensuse.org/repositories/Kernel:/openSUSE-11.4/openSUSE_Factory/

>> a test on your hardware.

Why file a bug for something that is already fixed in our repositories?

I asked on IRC last night about the CIFS mount problem before filing and
got no useful feedback. The single terse response implied I should file
a bug.

The URL Kulow provided to get 37.2 no longer contained it when I tried
to get it a few days later to try on other systems.

I dup'd immediately before testing, and didn't get a fixed kernel from
updates. Therefore I presumed a fix was not generally available, or some
other problem was holding back general availability of 37.2, which I
already knew had a fix that might need to be backported to 37.1.

As a practical matter, and without subscribing to yet another high
traffic mailing list, how's one supposed to know a particular fix made
the transition from announcement to availability when it isn't yet in
updates? I know there is a way, but I never remember it, which makes me
wonder if it's practical. :-(

Aside?: What's the story about
http://lists.opensuse.org/opensuse-maintenance/ ?

If you want the latest kernel, you can always use the Kernel:stable

How does one decide whether that's appropriate to do? Maybe
Kernel:stable should always be an enabled repo? Would that have a
downside? If that's better than official release kernels, why not go
beyond stable to head (or something else, so... many repos to choose from)?

If you're itching to run the latest kernel for a particular release,
Kernel:$RELEASE (e.g. Kernel:openSUSE-11.4) is probably your best bet.
It is synced up with the git repo at least daily and contains what will
end up in the next update. Updates are snapshots of this repo.

AFAIK, Kernel:stable tracks master and is the last state before I check
in a new -RC. Jiri Slaby maintains it, and I'm not entirely sure if
that's the case. Since 2.6.38 just went final, I guess we'll find out. :)

So, it really depends on what you want. Currently, they're identical.
openSUSE {11.5,12,whatever} will probably not be based on 2.6.38 as it's
8 months out and the typical kernel release cycle is 3 months.

That means that when 2.6.39-rc2 is released, master will include it.
openSUSE-11.4 will follow 2.6.37.x and Kernel:stable will follow 2.6.38.x.

[CC'ing Jiri to confirm this is the case]

or openSUSE:Tumbleweed repositories.

Tumbleweed still seems to still have kinks to be worked out, generally,
and due to 11.3 to 11.4 base switch, so I've only one of those enabled
as yet.

This update will push out to the main
openSUSE:11.4 repository in a few weeks.

Few weeks? Kulow told us a 37.2 was available before GM was cut!?!?!?

AFACT, 2.6.37.3 is already in the openSUSE:11.4:Update:Test repo. It
just needs to be released. 2.6.37.4 is already in the
Kernel:openSUSE-11.4 repo.

Submitting the bug report *is* the right thing even if it's immediately
closed as already fixed in the repo.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk1/ge4ACgkQLPWxlyuTD7J8wQCeLXm9EGAOIa/Eusydf231KMDu
JiIAnjtDIYzwWM8HcV8kzeKbMdYu0IfK
=nOxX
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups