Am Dienstag, 1. März 2011 schrieb Felix Miata:

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.

Small increment with possible partial https://bugzilla.novell.com/show_bug.cgi?id=584493 fix (colors in mc no longer corrupted, but still setterm settings from .bashrc are discarded)? Installed on P4@2.8GHz plus Piii@600MHz laptop. What should we see that's different from 2.6.37.1?

I don't know - and I guess it's best to just leave .1 and create an update later. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Mar 01, 2011 at 07:15:42AM -0500, Greg KH wrote:

On Tue, Mar 01, 2011 at 12:32:31PM +0100, Stephan Kulow wrote:

...

Am Dienstag, 1. März 2011 schrieb Felix Miata:

...

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.

Small increment with possible partial https://bugzilla.novell.com/show_bug.cgi?id=584493 fix (colors in mc no longer corrupted, but still setterm settings from .bashrc are discarded)? Installed on P4@2.8GHz plus Piii@600MHz laptop. What should we see that's different from 2.6.37.1?

I don't know - and I guess it's best to just leave .1 and create an update later.

And miss the security fixes in .2?

{sigh}

Sometimes I wonder why I make these updates...

We will of course follow the 2.6.37.x line with updates ;) I guess coolo is afraid to break stuff and have breakage on the medium. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 2011/03/01 06:14 (GMT-0400) Felix Miata composed:

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_Fac... a test on your hardware.

Small increment with possible partial https://bugzilla.novell.com/show_bug.cgi?id=584493 fix (colors in mc no longer corrupted, but still setterm settings from .bashrc are discarded)? Installed on P4@2.8GHz plus Piii@600MHz laptop. What should we see that's different from 2.6.37.1?

Just discovered 2.6.37.2-3 includes the http://www.mail-archive.com/stable@linux.kernel.org/msg05053.html fix that is missing from the GA kernel built the same day as that fix announcement. :-( filed: https://bugzilla.novell.com/show_bug.cgi?id=679615 -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

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_Fac... 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)?

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!?!?!? Color me perplexed. :-( -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 2011/03/15 07:58 (GMT-0700) Greg KH composed:

On Tue, Mar 15, 2011 at 10:47:05AM -0400, Felix Miata wrote:

...

...

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.

What specifically do you feel are the "kinks to be worked out"?

A round tuit shortage has kept me from being up to speed on its status, maybe there are no kinks, at least none bigger than blips, except...

I have not heard any problems with the current Tumbleweed repo and so far do not have any plans to change the way it works as there are no complaints.

What needs to happen before you feel comfortable using it?

First I have to decide there's more to be gained that lost by replacing 11.2 with 11.4, and I haven't reached that point yet. What's worse, suspecting excess optimism on transitioning to systemd from sysvinit in a single devel cycle, I fear releasenext will be worse than 9.1, 10.1 & 10.3 were combined, and make post-11.4 Tumbleweed a new habit maybe better avoided. For me to get to 11.4 for a production box in the first place: 1-KDE3 has to work. I haven't tried KDE3 on any 11.4 system yet myself. I saw reports lately of significant missing function, but no reports of resolution, while KDE 4.6 continues to omit at least one function I refuse to live without https://bugs.kde.org/show_bug.cgi?id=158556 and has several annoyances I'd rather live without https://bugzilla.novell.com/show_bug.cgi?id=675370 https://bugs.kde.org/show_bug.cgi?id=262695 https://bugs.kde.org/show_bug.cgi?id=260391 https://bugs.kde.org/show_bug.cgi?id=229984 https://bugs.kde.org/show_bug.cgi?id=263562 2-Round tuit shortage has kept me from fully testing for retained ability to run different resolutions on :0 than on :1 and/or :2 using a single display. KMS has confounded the X/xrandr overhaul begun almost 3 years ago, which I avoid for a while longer if sticking to 11.2. 3-Unless https://bugzilla.novell.com/show_bug.cgi?id=584493 gets fixed before I decide to decide, I'll be forced to use a vanilla kernel, but as yet I've found no summary of pros and cons of vanilla vs. release kernel. 4-the backup to my main production box on RAID1 with 11.4 release kernel is not shutting down reliably, mirroring reports I've seen of such trouble by others 5-nfs output from mount command no longer fits on one 128 character line 6-I'm not yet convinced https://bugzilla.novell.com/show_bug.cgi?id=665720 is gone The only thing I actually expect to gain from 11.4, besides extended "support" life, is reliably working sound in 11.0 broke in 11.2, and I expect 11.4 to fix that. As bad as 11.4 looks to me based on the above list, releasenext looks uninviting, requiring significant learning of new ways to do things that have just worked since the beginning of my Linux experience under sysvinit; which means I'll need to goto 11.4 at some point probably before releasenext goes GA, and maybe better sooner than later. -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----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_Fac...

...

...

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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Mar 15, 2011 at 10:31:50PM +0100, Jiri Slaby wrote:

On 03/15/2011 04:12 PM, Jeff Mahoney wrote:

...

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. :)

Yes, this is exactly how it works. I pushed 2.6.37.4 yesterday, will wait for Greg to suck this into the Tumbleweed and then I will bump it to .38.

It's been building in Tumbleweed all day now and should be finished in a few hours. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Mar 15, 2011 at 10:51:55PM +0100, Jiri Slaby wrote:

On 03/15/2011 10:38 PM, Greg KH wrote:

...

On Tue, Mar 15, 2011 at 10:31:50PM +0100, Jiri Slaby wrote:

...

On 03/15/2011 04:12 PM, Jeff Mahoney wrote:

...

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. :)

Yes, this is exactly how it works. I pushed 2.6.37.4 yesterday, will wait for Greg to suck this into the Tumbleweed and then I will bump it to .38.

It's been building in Tumbleweed all day now and should be finished in a few hours.

Ah, the message was delayed, because I was not subscribed to the list.

I noticed the merge in Tumbleweed, so I did the udpate few hours ago. K:stable GIT repo now contains .38 which will mirror to the k:stable OBS repo in the night.

Great, I'll see how that works out and switch Tumbleweed over to it in a few days if it all looks sane.

(I had to fix preload and systemtap once again before the kernel push proper. And it took some time :(. I wish we get rid of that finally.)

Yeah, I'll not miss that at all either... thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Hi; On Mon, Mar 28, 2011 at 10:30 AM, Jiri Slaby wrote:

On 03/15/2011 10:31 PM, Jiri Slaby wrote:

...

On 03/15/2011 04:12 PM, Jeff Mahoney wrote:

...

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. :)

Yes, this is exactly how it works. I pushed 2.6.37.4 yesterday, will wait for Greg to suck this into the Tumbleweed and then I will bump it to .38.

One more question here. Do we want master to follow a stable tree until the next -rc2 is released? Currently it is that: master=2.6.38 + suse patches stable=master+2.6.38.2

should it be now: master=2.6.38.2 + suse patches stable=master ? It's _no_ added work for me.

Then it will be: master=2.6.39-rc2 + suse patches stable=the last master commit before -rc2 + latest stable-38.

Before jumping Tumbleweed into 2.6.38 please note that it has broken bluetooth functionality, see https://bugzilla.novell.com/show_bug.cgi?id=680170 Regards, ismail -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Mon, 28 Mar 2011 10:40:45 +0200 Jiri Slaby wrote:

On 03/28/2011 10:37 AM, İsmail Dönmez wrote:

...

Before jumping Tumbleweed into 2.6.38 please note that it has broken bluetooth functionality, see https://bugzilla.novell.com/show_bug.cgi?id=680170

Thanks for the heads up, but tumbleweed already runs on 2.6.38.

And bluetooth works just fine for me with 2.6.38-27-desktop. But I'm using latest bluez, so this might do the trick. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Mon, 28 Mar 2011 07:16:23 -0700 Greg KH wrote:

Sounds like I should add bluez to tumbleweed as well :)

The bugreport says that updating bluez did not help. So I might just be lucky. I'll SR bluez again for tumbleweed if I think that there is something worth the updating. Right now there is quite some churn there, so there's a risk of breaking stuff. But once I find a worthy new feature or important bugfix, I'll submit bluez to Tumbleweed. If you feel you need it for whatever reason: FACTORY is usually up-to-date wrt. bluez, I'm usually submitting it within a day or two after release (after it passes my minimal smoke tests). -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 03/28/2011 07:10 PM, Stefan Seyfried wrote:

On Mon, 28 Mar 2011 07:16:23 -0700 Greg KH wrote:

...

Sounds like I should add bluez to tumbleweed as well :)

The bugreport says that updating bluez did not help. So I might just be lucky.

I'll SR bluez again for tumbleweed if I think that there is something worth the updating. Right now there is quite some churn there, so there's a risk of breaking stuff.

I run on tumbleweed and BT works for me as well. I.e. I haven't updated bluez. I run on Gnome. So this is probably machine specific. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org