Annoyences:
1.) factory repo was suddenly openSUSE 11.2 without warning but one insider slang message in the Mailinglist Archive. Even people reading that message did not understand.
2.) You cannot prelink your repo-config to 11.1 (it is named 11.1-rc1). On Release you have to edit the conf files again. And if there is a Rc2 you will have to edit … The most Annoyence is not the editing, but that you have to check the news… Coming from Debian i was used to link the repos to lenny long before this next Debian Release. If i was keen to keep testing, this is now the same as Lenny but will diverge at the Release of Lenny. For me the logic of openSUSE repo naming conventions is not straight forward.
3.) You will geht nearly no updates as an openSUSE11.1-rc1 tester (this was stated in the Mailinglist on Friday).
4.) If you get updates, you probably get no source code (as of kernel update 2.6.27.7-8). Thus you cannot compile fglrx proprietary drivers.
Some good news at last: openSUSE11.1 Kde 4.1.3 packages seem to have some pretty backported features of Kde 4.2
Conclusion: This community does not much to encourage users to test! But openSUSE is ahead as the best supporting Kde distro!
Forwarded internally. Thank-you for your thoughts.
Good luck.
ulenrich wrote:
> Annoyences:
> 1.) factory repo was suddenly openSUSE 11.2 without warning but one
> insider slang message in the Mailinglist Archive. Even people reading
> that message did not understand.
> 2.) You cannot prelink your repo-config to 11.1 (it is named 11.1-rc1).
> On Release you have to edit the conf files again. And if there is a Rc2
> you will have to edit … The most Annoyence is not the editing, but
> that you have to check the news… Coming from Debian i was used to link
> the repos to lenny long before this next Debian Release. If i was keen
> to keep testing, this is now the same as Lenny but will diverge at the
> Release of Lenny. For me the logic of openSUSE repo naming conventions
> is not straight forward.
> 3.) You will geht nearly no updates as an openSUSE11.1-rc1 tester (this
> was stated in the Mailinglist on Friday).
> 4.) If you get updates, you probably get no source code (as of kernel
> update 2.6.27.7-8). Thus you cannot compile fglrx proprietary drivers.
>
> Some good news at last: openSUSE11.1 Kde 4.1.3 packages seem to have
> some pretty backported features of Kde 4.2
>
> Conclusion: This community does not much to encourage users to test!
> But openSUSE is ahead as the best supporting Kde distro!
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Hmmm, maybe it does not really fit because I am not a test of the factory version. However, I tried to test the RC1. It started fine, I could install. But today it seems that somebody packaged a new kernel (2.26.27.7-4.4-pae) which, well, does not really work properly. After I downloaded and installed it with the automated update function, I tried to reboot. However, the system hang. The message was that the boot process could not find /lib/modules/2.6.27.7-4-pae/modules.dep which actually happens to sit at exactly this place. I don’t think that I ever saw such a stupid error before. However, I have no idea how to resolve that and any hint would be greately apreciated. Cheers KUF
the old kernel and initrd are still present in /boot
while booting edit grub lines for old kernel and boot up. check where the new kernel modules are hiding. or probably they are not installed .
auto updates sometimes put us in troubles like this.
make it manual update ask it show the availability of new updates.
i’m new to opensuse and I’ve been testing it since 11.1 beta 2, and I have to agree with you. Now i’ve just freezed until Goldmaster release. If I had know, i’ve just installed 11.0 and wait until 11.1 gets stable.
I like opensuse in general, but It is so discouraging for testers. I think if there is people willing to help in any way you should make thing a little more easier for them.
Just 2 throw in my 2cents, my observation here has been that the change has also been due to the way the alphas and betas got released.
Testing 10.3 an 11.0 went allot smoother for me.
As I understand, this is the first time the whole thing has been done using the build service. This has been a major thing to handle for those having to serve up the releases… (this is my personal observation).
I think the adjustments needed to accomplish the switch to the build service, and the fact that the first build attempts didn’t go so well, account for the lack of good communication & coordination.
Trying to jump in the last alpha release and then first beta stage - didn’t have not much luck there… In whole, testing the new developments and updates in 11.1 was much harder to keep up with for me.
I am glad to see that RC1 is running with much promise… Apart from some small annoyances it’s also very stable. So I am impressed about that!
Hoping the next test ride goes a bit smoother though (for testers & devs alike!!)…
Whats with the whining about being cruel to the testers
There have been many cautions about testing and the pitfalls
if you can’t use due caution then don’t test. wait for the stable release
the whole purpose of testing is to find these things that aren’t working right
then if appropriate filing a bug report. Not cry because you failed to double
check something. And on the help forums ask for help, don’t demand it. We are all fellow users like you that are willing to explain how we solved problems with configurations etc.
In fact I tested because I know how to overcome problems in a beta version (not all off course). Hey, I’ve used Slackware, Debian, Ubuntu and now I’m using OpenSuse and Lunar-Linux. Indeed I’ve made some posts, look at them and tell me if there is a rude demanding on one of them.
I’m just posting an opinion, take it or not, but don’t asume that all people had just come from windows to opensuse yesterday.
@Dale: You might consider how you are expressing yourself? It’s coming across totally generalising every post about this as whining?
There is a difference between whining and attempting to give constructive criticism. The OP clearly is trying to do the later…
If you want to invite new users in the process of testing, it’s also good to see where adjustments can and should be made to facilitate.
There should be clear logic of updates/upgrades. I mean this is the essence of a distribution nowadays where security versus exploits does matter. And software developement gets faster and faster, so people do want more and more such a thing like a rolling release (e.g. arch,sidux etc).
But everywhere I see users asking : “Will it be possible to upgrade from 11.0 to 11.1 ?” And I see answeres like: “Better a clean install on a second partition”
I mean this would be stoneage (…if only used openSUSE repos for software installs)! Why there is a unsecurity about such a matterofcourse !?
There should be a clear none ironicle, none corporate slang communication about important news (such as factory going upgraded to 11.2).
I must disagree with the most stupid error and need to remind You all the “Press any key to continue” when the keyboard is not present Of course it’s in the OS of which we do not speak of
Of course it’s in the OS of which we do not speak of