I want a STABLE repository which updates it software to the LATEST STABLE releases. Should I use Index of /repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2 instead of the repo I am using now? How stable is my current repo anyway? I do notice however that my current repo is more up to date then the KDE4:/STABLE repo. Eg amarok is 2.2.1 in my repo but only 2.1.x on the KDE4:/STABLE repo. Should I switch to the stable repo when considering stability? I’m confused with the large number of available repo’s…
The stable is a good way to go for sure.
But I can tell you (not sure when)
That kde4.3.4 will be pushed in via Update repo - This is a most unusual move. But @oldcpu was mentioning it earlier to me.
You will see a combination of updates and roll backs
Use the system package switcher on the changed kde repos
When done with kde, go back and do the switch on Packman again too.
Thanks for the info! But can you tell me if the KDE:/43 is considered stable or factory or something in between? And why does the stable repo not contain amarok 2.2.x? 2.2 is considered a stable amarok (I assume) and it is already out for several weeks…
If you want the MOST STABLE, then IMHO you should stop your KDE updates NOW!! and just wait. Let me quote the mailing list post from Will Stephenson of the SuSE-GmbH openSUSE Team:
The KDE and maintenance teams are taking the unprecedented step of a point release update to KDE SC 4.3.4 in our ‘STABLE’ repository and from then as an online update to 11.2. Normally we don’t do version updates in online updates, preferring to backport patches to the released version.
I’ll be straight with you; the impetus for doing this comes from putting 4.3.4 on an enterprise product and we don’t want to maintain two 4.3 codebases, but we’re confident that this is a good thing for openSUSE users, because:
4.3.4 has 2 months’ more upstream bugfixing in it, compared to 4.3.1. This includes a major Plasma performance bug fix.
4.3.4 is the final planned release in the KDE 4.3 series and will therefore have the longest shelf life. It will be easier to apply future fixes from the KDE 4.3 branch to 4.3.4 packages than to 4.3.1 packages.
having 4.3.4 on an enterprise product gives us additional reasons (customers’ money!) to fix bugs in it, benefitting openSUSE users too.
We are aware that any version update has the potential to include regressions, but:
4.3.4 is a point release with only bugfixes and translation updates
we’ve seen a lot of use of the KDE:43 repo from 11.2 users without a lot more bugs
other distributions have already shipped 4.3.2 and are going to push point releases as online updates as well
We have consulted the openSUSE maintenance team, who were in favour of this move. The online update will take place after a period of testing 4.3.4 on 11.2 in KDE : KDE4 : STABLE : Desktop.
The sole drawback to this that we’re aware of is that this will be a large online update download; we hope you will agree the benefits will be worth it.
Season’s greetings!
Will
It appears to me (and maybe I read this wrong) that the online update being intended for 11.2 is being tested in the STABLE repos of KDE4 (noting that KDE-4.3.4 is already very stable). …
kde43 is considered stable
Actually I found it more so than the stable repo already quoted.
11.2 was released with 4.3.1 and normally that wouldn’t change, but it seems that the plan is it will. Certainly it is possible to upgrade via the build service, this has always been the case.
And it will always be the case that kde development (as in the case of amarok you mention) will continue apace and leave 11.2 behind, but we can keep up with that by using the build service.
caf4926 wrote:
> suskewiet;2091556 Wrote:
>> A list of possible repos is found here: ‘KDE/Repositories - openSUSE’
>> (http://en.opensuse.org/KDE/Repositories).
>> Right now I use this repository:
>> ‘http://download.opensuse.org/repositories/KDE:/43/openSUSE_11.2/’
>> (http://download.opensuse.org/repositories/KDE%3A/43/openSUSE_11.2/).
>> But this repo is now longer listed under the list in the first link.
>>
>> I want a STABLE repository which updates it software to the LATEST
>> STABLE releases. Should I use ‘Index of
>> /repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2’
>> (http://tinyurl.com/yfpy8xz) instead of the repo I am using now? How
>> stable is my current repo anyway? I do notice however that my current
>> repo is more up to date then the KDE4:/STABLE repo. Eg amarok is 2.2.1
>> in my repo but only 2.1.x on the KDE4:/STABLE repo. Should I switch to
>> the stable repo when considering stability? I’m confused with the large
>> number of available repo’s…
>
> The stable is a good way to go for sure.
> But I can tell you (not sure when)
> That kde4.3.4 will be pushed in via Update repo - This is a most
> unusual move. But @oldcpu was mentioning it earlier to me.
>
> You will find there is a community version to go with the stable repo
> you quoted
> ‘Index of /repositories/KDE:/KDE4:/Community/openSUSE_11.2’
> (http://tinyurl.com/yh2z7n8)
>
> You will see a combination of updates and roll backs
> Use the system package switcher on the changed kde repos
> When done with kde, go back and do the switch on Packman again too.
>
> This is what I mean in principle:
> http://tinyurl.com/yf4wobr
Per a previous post/thread by (I think) either yourself or oldcpu, I
added the 4.3.4 stable repo. I didn’t disable it - repos are set as follows:
Given that the 4.3.4 updates will be coming down the line anyway, should
I leave it for now, or remove it and just wait for 4.3.4 to be included
in the mainline patches?
Thanks…
…Kevin
Kevin Miller
Juneau, Alaska http://www.alaska.net/~atftb
In a recent poll, seven out of ten hard drives preferred Linux.
caf4926 wrote:
> Kevin. In 11.2 I have
>
> KDE 4.3 |Yes | Yes | 99
> Packman Repository |Yes | Yes | 90
> Updates for openSUSE 11.2-0 |Yes | Yes | 99
> openSUSE-11.2-Non-Oss |Yes | Yes | 99
> openSUSE-11.2-Oss |Yes | Yes | 99
>
> Make this switch first
> ‘ImageBam - Fast, Free Image Hosting and Photo Sharing’
> (http://www.imagebam.com/image/2b9b1858976430)
> apply
>
> then do this one
> http://tinyurl.com/ybrqmzy
Thanks. Nothing turns up on the imagebam page except the usual
marketing stuff. Not sure why - tried it via several browsers. There’s
a small box in the middle where I’d expect an image which just says
‘loading’ but it never does. I’ll give it a try at home. Maybe it’s
something on our network here stepping on it.
…Kevin
Kevin Miller
Juneau, Alaska http://www.alaska.net/~atftb
In a recent poll, seven out of ten hard drives preferred Linux.
I presume that was the intent, the difference due to our respective setups.
Now on to the Packman step. But after that’s done, should I leave 4.3
Stable enabled or disable it and wait for the update repo to catch up.
At some point it seems like they’ll be in sync, and there’s no point in
having two identical repos.
Now on to the Packman step. But after that’s done, should I leave 4.3
Stable enabled or disable it and wait for the update repo to catch up.
At some point it seems like they’ll be in sync, and there’s no point in
having two identical repos.
Either way, I can’t see it making too much difference.
I actually use the Stable repo too. My earlier comment: “Kevin. In 11.2 I have”
Was a generalization to say this is what I would have. No intent to misinform:)
Actually my repo setup is considerably more complicated. But you should be fine in the setting you have and in the step I have outlined.
On 12/22/2009 07:56 PM, caf4926 wrote:
>
>> Now on to the Packman step. But after that’s done, should I leave 4.3
>> Stable enabled or disable it and wait for the update repo to catch up.
>> At some point it seems like they’ll be in sync, and there’s no point in
>> having two identical repos.
> Either way, I can’t see it making too much difference.
>
> I actually use the Stable repo too. My earlier comment: “Kevin. In 11.2
> I have”
> Was a generalization to say this is what I would have. No intent to
> misinform:)
Great - that’s how I was interpreting it hence my going ahead and
applying the steps. I noticed a number of downgrades when I did it, but
assume they were to avoid conflicts.
> Actually my repo setup is considerably more complicated. But you should
> be fine in the setting you have and in the step I have outlined.
Great, thanks. So one (hopefully) final question for now: should I do a
‘zypper up’ or ‘zypper dup’ as a rule? I seem to pull in a good number
more updates doing the ‘dup’.