64-bit lib64alsa2-devel remove packages

[MBantz]

Wanted to put this post in testing section where this issue has been mentioned, but I cannot post there apparently.

Attempting to update 64 bit, lib64alsa2-devel wants to remove an enormous bunch of packages,

cheers,
MBantz

[ghostbunny]

hi,

you have to sign up for getting access to the testing section.

sign up here http://www.pclinuxos.com/forum/index.php/topic,104577.0.html

every packager which isn't a global mod or admin have to sign in like a tester

regards
ghostbunny

[henryz]

I also complained about this very thing earlier.  The lib64alsa2-devel update will remove most of KDE (4.6.5), amongst a long list of other apps.   I applied this update & it basically trashed KDE (4.6.5).  That was a controlled test & I had a fresh backup, so no lasting harm was done.  I think the current batch of updates were actually meant for testing/KDE 4.8.2, but I'm not entirely sure that's the crux of the problem.  I've searched thru the forum posts to see if there was a mandate to upgrade KDE (64-bit, testing section not activated) to 4.8.2 (currently in testing section).  If there was such a requirement, I can't find it.  The current, non-testing 64-bit system is quite stable (even though not a "final" version).  I plan to give things some time & see if they get sorted out by the devs -  If not, then I'll activate the testing section and update KDE/fix other broken stuff (if possible). 

[Old-Polack]

I also complained about this very thing earlier.  The lib64alsa2-devel update will remove most of KDE (4.6.5), amongst a long list of other apps.   I applied this update & it basically trashed KDE (4.6.5).  That was a controlled test & I had a fresh backup, so no lasting harm was done.  I think the current batch of updates were actually meant for testing/KDE 4.8.2, but I'm not entirely sure that's the crux of the problem.  I've searched thru the forum posts to see if there was a mandate to upgrade KDE (64-bit, testing section not activated) to 4.8.2 (currently in testing section).  If there was such a requirement, I can't find it.  The current, non-testing 64-bit system is quite stable (even though not a "final" version).  I plan to give things some time & see if they get sorted out by the devs -  If not, then I'll activate the testing section and update KDE/fix other broken stuff (if possible). 

There is no such thing as a non testing 64 bit PCLinuxOS release.

[djohnston]

I've searched thru the forum posts to see if there was a mandate to upgrade KDE (64-bit, testing section not activated) to 4.8.2 (currently in testing section).

Just a slight correction. For 64bit, it is the test section. For 32bit, it is the testing section. And, like Old-Polack said, there is no non-testing 64bit version yet, regardless of which repository sections are enabled.

[Archie]

And surely this post should not exist outside the Testing section.

Non-testers won't be able to post on the Testing section unless they sign up, which in turn means waiving your right to support by enabling the test/testing sections, and report issues and problems without expectations of support to the Testing section.

djohnston, I would have thought you'd be a tester.

The devs are already aware of the situation and are working to rectify it.

[djohnston]

djohnston, I would have thought you'd be a tester.

I don't understand your meaning. 

[Archie]

djohnston, I would have thought you'd be a tester.

I don't understand your meaning. 

My bad. You are already a tester. What I meant was for MBantz, the original poster. My apologies.

[Neal ManBear]

MBantz,     
Sign up for testing. This is required of packagers.     
http://www.pclinuxos.com/forum/index.php/topic,104577.0.html     

henryz,     
If you are running 64bit, you should sign up for testing, too.     

[henryz]

I'll give some thought to becoming a tester, although I don't relish the thought of rebuilding my system at relatively short intervals.  (Yes - I am aware of the benefits of a separate /home partition and other ways to reduce the re-install time/grief).  One of my concerns is that 64-bit may take a long time to become "stable" or "production".  32-bit spent years as a "preview" before becoming a final.  It was, however, quite stable and useful as a production system.  I guess my (evidently flawed) understanding was that 64-bit, without the "test" section activated was of similar status: stable enough for routine use (as a hobbyist), but not a true final version.  If this is not to be the case with the current 64-bit, I need to know that up front.  Anyway, thanks for letting me ramble a bit, philosophically.

     

[Neal ManBear]

henryz,
If you use 64bit, you are a tester. The sign up is for becoming an official tester.     
The test section for 64bit was added for testing newer versions of KDE plus some other apps. That does not mean that all of 64bit is not in testing. It is.     

Anything that is in testing is not supported. Your assumption that 64bit is production ready is just an assumption. That has never been stated by any developer on this forum.     

We are working on 64bit to get it ready for release, but until it is ready, it will be a test.     

[henryz]

I never assumed it was production.  64-bit appeared to be usable at the hobbyist level without a large amount of user intervention.  I will not continue to assume so.  (Not meant as a complaint - thanks for clarifying.)

[Archie]

Heya henryz,

You have brought up some genuine concerns. Upfront, there's still a lot of work to be done, and we really need good testers and packagers. You have your own opinion of 64-bit ... and we are pleased to note that "it appears to be usable at the hobbyist level" but the fact of the matter is, it is still in testing and there are still lots of wrinkles that need ironing out. There are apps to be rebuild and tested against the latest KDE (at the moment it's 4.8.3) and Qt. The latest kernel is being assessed.

In testing, we do not offer support and it is unethical to ask for help fixing broken apps and systems but we do look for workarounds and fixes. And there are broken apps, and breaking your install does happen. It's the risks, and a terrible one at that ... but someone has to do it. Thank you very much, testers!

At the moment, 64-bit without "test" enabled will definitely bork your install. So if user have "test/testing" enabled and updates don't go their way, that would be unfortunate.

One of my concerns is that 64-bit may take a long time to become "stable" or "production".

Although the focus of our efforts is on this architecture, be assured that i586 is also in development ... and not too far behind 64-bit ... it's actually closer than many might not believe.

We could surely use another committed user to help out.

Peace and much respect,
Archie

[MBantz]

Well, I only once had the need to enable test section (to get pkgutils installed) - during all the years with PCLinuxOS,

at the moment I package on my working system because my cpu cannot virtualize a 64 VM (I didn't read the small print when buying this lappy :-) - enabling testing would probably bork my system. I'm running 64 bit LXDE from the day it was launched.

I package for fun and to help others out, I will not hope I need to register all around to continue packaging,

I can only recommend testers to keep two vm's - one with testing enabled and one without,

cheers,
MBantz

[Neal ManBear]

Martin,
The reason for packagers to sign up is not to be a tester so much as it is to post test topics. That is, when a package of yours is put in testing/test, you post a topic to request it be tested.     
It is not necessary that you personally be a tester, in other words. We only need for you to "collect, analyze and use to fix" reports on apps you have in testing/test.