mepis 3.3.2.test03 works
Posts: 1504
I did as hippy said and downloaded a new copy from a different mirror. This one is working and i am not getting any crashing out to commandline, like i did with the other copy(yes, i did burn that 1 a couple of times at different speeds it was just a bad copy) this one is working great and i have just finished installing libgnome2-perl(missing in this copy and throws up a warning when upgrading or installing)then upgraded my firefox to current. That is all i need for now, i am not reinstalling again if i don't have to(i have reinstalled about 20-30 times testing the updates thing and trying to stop the crashing(with old copy) I am going to leave it alone. It works and i'm happy.
I'm not sure WHY?
Posts: 1504
But the new mepis is working for me now and i just up graded firefox to current with no problems, Yes, I did think test 2 was more up to date though. I do not beleave firefox is unstable as i am using it now with no problems. It's the kde stuff in the repos that are screwed.
It's Not Firefox
Posts: 5513
Nae Nae, I'm not doing any testing with 3.3.2, I'm running live 3.3.1-1 on multiple boxes. It takes a little doing, but I am running firefox 1.0.6 and Thunderbird 1.0.6. It takes a little doing because Mozilla stuff is tied to other libraries that have been going through their own little round-a-bouts. Perhaps they pulled back a rev in 3.3.2-test? to try to stabilize just a bit more. But yes, all the trouble right now seems to be caused because the Debian repositories are trying to bring in KDE 3.4 and all the supporting lumber. Many people are sad 
Jon
unavailable quanta
Posts: 220
Yes, the problem seems to be in the repos pulling kde 3.4.2.
I *have* to have quanta and the "upgrade" deleted it and upon attempted re-install, here is the sad news:
root@2[~]# apt-get install quanta
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
quanta: Depends: kdelibs4 (>= 4:3.3.2-5) but it is not going to be installed
Depends: libcvsservice0 (>= 4:3.3.0-0) but it is not going to be installed
Depends: libqt3c102-mt (>= 3:3.3.4) but it is not going to be installed
Depends: kfilereplace but it is not going to be installed
Depends: klinkstatus but it is not going to be installed
Depends: kommander but it is not going to be installed
E: Broken packages
root@2[~]#
Is there any way around this mess .. short of a fast retreat to 3.3.1? Or even back to test02?
This is painful!
Ken
In a world without walls and fences nobody needs Windows and Gates!
User #104362 with the Linux Counter, http://counter.li.org
TTL on ADSL?
Posts: 220
Another issue I'm having since moving from 3.3.2.test02 to test03, is that my 1.5 Mb/s ADSL dies, frequently !
This hasn't been an issue with any of the previous half dozen MEPIS distros, and not even test02 (nor Ubuntu, or any of the Fedora Cores) but it sure is now.
I have to use OS Center to reset eth0 every time I come back to the system, and I'm guessing that being idle for even a few minutes is killing the eth0.
Is there any way to make eth0 stay up, longer, like always?
Ken
In a world without walls and fences nobody needs Windows and Gates!
User #104362 with the Linux Counter, http://counter.li.org
Try This
Posts: 5513
Pantheus,
Here are a couple things to try. First, make sure that your repositories are clean. Do this stuff as root (as usual):
apt-get clean apt-get update # do this command twice if you see errors the first time
Next, you may need to load quanta from a specific repository. Here's a nifty command to learn more about a package there you ever cared to know 
apt-cache showpkg quanta
The important info is at the top of the screen (you may need to scroll back. You will see that this package is currently in the "testing" repository. So to load it specifically, enter:
apt-get -s install quanta/testing
The "-s" is a "simulated" install. It will show you if there are any other dependencies. If there are dependencies, as long as messages indicate that things will be "installed" then you can safely mvoe ahead. If the simulation indicates that any packages are to be removed, then you may not want to do this! If you wish to go ahead with it, simply do the same command above, only drop the "-s".
I just did a simulated install on my system, and it appears that, in addition to quanta, you would need to install libcvsservice0 from /testing. However, it looks like it WOULD REMOVE a number of packages. This may be due to the continuing instability in KDE 3.4; although according to some other posts KDE 3.4 is becoming more stable as is Mepis 3.3.2.
So I would still recommend holding off for a bit...
Jon
Re: Try This
Posts: 220
So I would still recommend holding off for a bit...
Thanks, Jon, for the most informative reply.
I've done just that .. retreated to box-stock test03, with only the upgrades I can't live without, and that doesn't include kde 3.4.2, yet.
I'm pretty disallusioned with test03 and incompatibility with kde and the repos "integration". That could have been done better!
But I thank you for the help.
Now if I could solve the TTL with DSL !
Ken
Hi ken, I understand you are
Posts: 2299
Hi ken,
I understand you are a bit disillusioned, but on the other hand I'd say that this is a generic problem we are going through. I have never really understood why the repos were called 'unstable', since they often hold upgrades of apps that are supposed to increase the stability. I now see that the unstable does not so much apply to the individual apps, but rather to the repo integration as a whole. The 'Mepis' way to prevent users from haphazardly installing apps and running the risk to (partially) break their system is twofold: disable the repos in sources.list and selling extra CDs. For those of us that take the risk to use the debian repos after all, the problems are forseeable. You cannot both run bleeding edge and stay cut free at the same time. Or you need to give up on pure debian and go for Ubuntu, although stories of broken Ubuntu systems are not few and far between either.
The best advice for now remains: only do installs from testing, and do not use unstable until further notice. People are now actively monitoring and trying out the unstable repos, so there's enough information for you to make a well founded decision to either take the risk or wait a bit more.
Newbie or not Newbie, there's always a question
Re: Hi ken, I understand you are
Posts: 220
For those of us that take the risk to use the debian repos after all, the problems are forseeable. You cannot both run bleeding edge and stay cut free at the same time. Or you need to give up on pure debian and go for Ubuntu, although stories of broken Ubuntu systems are not few and far between either.
I agree .. I have 5 official copies of Ubuntu here, sent from The Netherlands, and tried "Hoary" after giving up on MEPIS for a while ..
I would be happy to send all 5 of them to anyone ... it ain't panacea either! I'll even pay the shipping. 
Bleeding edge is good, (and a major learning experience), but way leary, I'm rapidly becoming.
Ken
Mepis 3.3.2.test03 going backwards???
Posts: 2
I have been following the Mepis page at Distrowatch and noticed that 3.3.2.test02 had Firefox 1.0.6 listed in the packages. And now, 3.3.2.test03 is posted with Firefox 1.0.4 instead.
What is happening? Is Firefox 1.0.6 unstable or is there another reason that Mepis seems to be going backwards in this case????
Please advise.
Thank you for your support!
Nae Nae