Restore Dapper after Edgy

[NoOp]

NoOp wrote:
> Joshua D. Drake wrote:
>>> 
>>> Questions:
>>> 1. How to restore a Dapper system back to its basic files without
>>> destroying any /home user data and having to reinstall and repartition
>>> the disk? This seems to me to be a basic requirement of this system.
>>> 
>>> 2. How to upgrade to the next Ubuntu version without having to depend on
>>> ubuntu-desktop which installs seriously outdated files?
>>> 
>>> 3. Why is Dapper 6.06x 2 revisions behind OpenOffice when OOo is an
>>> integrated part of the OS desktop? Note: after cleaning out all of the
>>> Ubuntu dated files (2.0.2) OOo 2.0.4 installs and runs just fine.
>>> 
>>> Suggestions/comments? I'm sure that I'm not the only one that has this
>>> issue and has corrupted their system with mixed version files.
>> 
>> I know that this isn't what you want.. but.. I would actually suggest:
>> 
>> apt-get update
>> apt-get dist-upgrade
>> 
>> From the edgy repos. I was in a similar boat recently. Edgy is working
>> just fine for me :)
>> 
>> Joshua D. Drake
>> 
>> 
> 
> Yeah... but it doesn't address the basic request for backing down to
> your existing version if you screw up and install an application from a
> forward repository. I still strongly think that there should be a script
> that will allow you to restore your system to the existing base version
> in cases like this (perhaps a system restore).
> 
> Regarding Edgy; I figured I'd give it a try on one of my test machines.
> I'm now 8 hours into the "upgrade" using  gksudo "update-manager -c -d"
> and it's still not finished. Apparently the update limits the download
> speed, and it took over 7 hours to download the required 1054 files.
> Odd, since it's connected to a verified & well working 1.5MB DSL
> connection. The update connection limited the speed to between 15Kb/s
> and 30kb/s. Speed tests on the link via other networked computers verify
> downloads at the same time at 1.2Mbps to 800Kbps per sec. Perhaps it's
> because the Ubuntu servers are loaded due to the release today, and
> they've limited the bandwidth. If that's the case, I wouldn't blame them.
> 
> 

And after 8 hours, 47 minutes the upgrade crapped.