Hi.
I have installed OpenSuSE 13.2 beta 1 and now would like upgrade it to OpenSuSE 13.2 rc1.
There’s no update in bug icon on tray(KDE4). I have still kernel 3.16.
There is, but it doesn’t show any updates and therefore is always hidden. Click on the small up-arrow right next to the digital clock to show hidden system tray icons and you will see it.
The preferred way to upgrade is to run “sudo zypper dup” anyway.
Some other possible ways:
- Run Apper or choose it in KDE’s system settings
- Use YaST->Software Management (click on “View”, choose “Repositories”, then right-click on the package list and select “All in this list”->“Update if a newer version exists”)
The problem with the updater applet not showing any updates is fixed in Factory already, so it should work in 13.2 final.
I have still kernel 3.16.
So?
That’s not going to change.
3.16(.3) is the kernel included in 13.2 Beta as well as RC1 (and even Factory doesn’t have a newer one yet).
AFAIK they wait with submitting 3.17 to Factory until 3.17.1 is out at least.
No idea whether 3.17 will still make it into openSUSE 13.2 then.
Sorry. I updated my system yesterday, but I have read in OpenSUSE 13.2 RC1 is 3.17 kernel.
On 2014-10-10 12:46, wolfi323 wrote:
> - Use YaST->Software Management (click on “View”, choose “Repositories”,
> then right-click on the package list and select “All in this
> list”->“Update if a newer version exists”)
No, update unconditionally. That’s equivalent to dup, I understand.
> AFAIK they wait with submitting 3.17 to Factory until 3.17.1 is out at
> least.
> No idea whether 3.17 will still make it into openSUSE 13.2 then.
They are considering it, but for later on the cycle.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Not quite.
“Update unconditionally” will also reinstall all packages that have not changed.
As there only should be updates (no downgrades) between Beta and RC1 (haven’t checked), “Update if a newer version exists” should be good enough and I would prefer it.
> AFAIK they wait with submitting 3.17 to Factory until 3.17.1 is out at
> least.
> No idea whether 3.17 will still make it into openSUSE 13.2 then.
They are considering it, but for later on the cycle.
Yes, they were considering it.
But the cycle is almost over now (we’re at RC1 already), so it cannot really be done much later in the cycle… 
It has been decided now to stay at 3.16 for 13.2 though:
http://lists.opensuse.org/opensuse-kernel/2014-10/msg00023.html
And to be honest, I don’t think it would be a good idea to still push 3.17 in that close to the release.
Maybe they will do an online update to 3.17.x at some time according to that mailinglist thread, but that update to 3.12 that was talked about/discussed never happened for 13.1 either, so I wouldn’t really bet on it.
On 2014-10-10 16:36, wolfi323 wrote:
>
> robin_listas;2668737 Wrote:
>> On 2014-10-10 12:46, wolfi323 wrote:
>> No, update unconditionally. That’s equivalent to dup, I understand.
> Not quite.
> “Update unconditionally” will also reinstall all packages that have not
> changed.
Yes, that’s a fair point.
There is no “update if different” option, unless “update
unconditionally” means just that in their parlance :-?
> As there only should be updates (no downgrades) between Beta and RC1
> (haven’t checked), “Update if a newer version exists” should be good
> enough and I would prefer it.
I’m a bit paranoid, so I would use “zypper dup” in text mode 
>> They are considering it, but for later on the cycle.
>>
> Yes, they were considering it.
> But the cycle is almost over now (we’re at RC1 already), so it cannot
> really be done much later in the cycle…
After release, I meant.
> It has been decided now to stay at 3.16 for 13.2 though:
> http://lists.opensuse.org/opensuse-kernel/2014-10/msg00023.html
That’s what I was referring to when I posted 
> And to be honest, I don’t think it would be a good idea to still push
> 3.17 in that close to the release.
That’s what they said. 3.17 is largely untested.
> Maybe they will do an online update to 3.17.x at some time according to
> that mailinglist thread, but that update to 3.12 that was talked
> about/discussed never happened for 13.1 either, so I wouldn’t really bet
> on it.
It may happen on the Evergreen phase. It did for 11.4, they upgraded to
the version used on SLES in order to tag along on their patches.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
No, it doesn’t mean that.
“Update unconditionally” does reinstall the package if there is no different version, otherwise it would not be “unconditionally”…
It’s the same as “zypper in -f” actually, I’d say.
> As there only should be updates (no downgrades) between Beta and RC1
> (haven’t checked), “Update if a newer version exists” should be good
> enough and I would prefer it.
I’m a bit paranoid, so I would use “zypper dup” in text mode
Ok, but then you do not use the update applet either…
>> They are considering it, but for later on the cycle.
>>
> Yes, they were considering it.
> But the cycle is almost over now (we’re at RC1 already), so it cannot
> really be done much later in the cycle…
After release, I meant.
> It has been decided now to stay at 3.16 for 13.2 though:
> http://lists.opensuse.org/opensuse-kernel/2014-10/msg00023.html
That’s what I was referring to when I posted
Ok. I first read it as “later in the development cycle”.
But then it occured to me that you might actually refer to that possible online update via the update repo some time after the release.
Anyway, I thought it would be good to clarify that.
> And to be honest, I don’t think it would be a good idea to still push
> 3.17 in that close to the release.
That’s what they said. 3.17 is largely untested.
Yes, and it’s not only about the stability.
Not all kernel modules (that are not part of the kernel itself) might build already against 3.17.
E.g. virtualbox fails to build now:
http://lists.opensuse.org/opensuse-kernel/2014-10/msg00032.html
So until this is fixed, virtualbox could not be part of the distribution, but more importantly also the guest additions (like the video driver) would be missing.
Other packages might be affected as well.
This would be solvable of course, but it’s definitely too late now without delaying the release again.
> Maybe they will do an online update to 3.17.x at some time according to
> that mailinglist thread, but that update to 3.12 that was talked
> about/discussed never happened for 13.1 either, so I wouldn’t really bet
> on it.
It may happen on the Evergreen phase. It did for 11.4, they upgraded to
the version used on SLES in order to tag along on their patches.
Yes, I know. And that’s the current plan AFAIK: stay with 3.11 for the official support period, and then let the Evergreen team decide whether they want to switch to 3.12 or not.
There was the discussion to officially switch to 3.12 months ago, when 3.11 was EOLed upstream. And the preference back then seemed to have been to do it, at least by those that participated in the discussion. But we are still at 3.11, probably until Evergreen takes over.
I just think the same thing might happen with 13.2, and the official update will not materialize. And in this case there will be no Evergreen update either…
On 2014-10-11 17:56, wolfi323 wrote:
>
> robin_listas;2668783 Wrote:
>> There is no “update if different” option, unless “update
>> unconditionally” means just that in their parlance :-?
> No, it doesn’t mean that.
> “Update unconditionally” does reinstall the package if there is no
> different version, otherwise it would not be “unconditionally”…
> It’s the same as “zypper in -f” actually, I’d say.
Sounds reasonable.
>> I’m a bit paranoid, so I would use “zypper dup” in text mode
> Ok, but then you do not use the update applet either…
I use yast online update all the time… I seldom use zypper, with dup
being the exception.
>> That’s what I was referring to when I posted
> Ok. I first read it as “later in the development cycle”.
> But then it occured to me that you might actually refer to that possible
> online update via the update repo some time after the release.
Yep.
> Anyway, I thought it would be good to clarify that.
Absolutely
>>> And to be honest, I don’t think it would be a good idea to still push
>>> 3.17 in that close to the release.
>>
>> That’s what they said. 3.17 is largely untested.
> Yes, and it’s not only about the stability.
> Not all kernel modules (that are not part of the kernel itself) might
> build already against 3.17.
> E.g. virtualbox fails to build now:
Oh 
> http://lists.opensuse.org/opensuse-kernel/2014-10/msg00032.html
> So until this is fixed, virtualbox could not be part of the
> distribution, but more importantly also the guest additions (like the
> video driver) would be missing.
Not ripe for eating yet.
>> It may happen on the Evergreen phase. It did for 11.4, they upgraded to
>> the version used on SLES in order to tag along on their patches.
>>
> Yes, I know. And that’s the current plan AFAIK: stay with 3.11 for the
> official support period, and then let the Evergreen team decide whether
> they want to switch to 3.12 or not.
Mmm.
> There was the discussion to officially switch to 3.12 months ago, when
> 3.11 was EOLed upstream. And the preference back then seemed to have
> been to do it, at least by those that participated in the discussion.
> But we are still at 3.11, probably until Evergreen takes over.
> I just think the same thing might happen with 13.2, and the official
> update will not materialize. And in this case there will be no Evergreen
> update either…
No, not unless 3.11 becomes unmaintainable for some unknown yet reason.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)