Could you provide the actual logs? That way we can see the errors and look at fixing the problems instead of just issuing a warning to user. The next month and a half is devoted to fixing such problems.
Thanks, Cody A.W. Somerville On Wed, Mar 5, 2008 at 12:07 AM, vidd <[EMAIL PROTECTED]> wrote: > Thanks for the links.... > These were extremely useful > > Results: > > Changing the /etc/apt/sources.list and running sudo apt-get update && > sudo apt-get dist-upgrade > AND > Using synaptic > Failed miserably > I was left with a completely broken system, with too many failures > to bother naming. > (This was not unexpected, since these methods are for > release-to-release, not intended for such a drastic update) > > RECOMMENDATION: > Add a very prominent note to the website for users and administrator > to NOT use these methods > > Using the update-manager > An up-to-date dapper install has update-manager installed > As instructed, the -d switch was required (presumable will not be > upon final release) > Worked fairly well > Required post-upgrade maintenace: > sudo apt-get -f install to fix broken packages > sudo apt-get update && sudo apt-get dist-upgrade to get the > updates that required the broken packages > > ****TURN OFF SCREENSAVER**** > I had forgotten to do this one upgrade attempt, and ended up with a > blue screen and a mouse pointer > I was able to continue by switching to command line > ([ctrl]+[alt]+[F1]) and running sudo dpkg --configure -a > > RECOMMENDATION: > Include a strong warning about screensaver, and include a "if you > have trouble" paragraph. > Three lines from the command line will fix all issues I encountered > (in order) > sudo dpkg --configure -a > sudo apt-get -f install > sudo apt-get update && sudo apt-get dist-upgrade > > > I have not been able to successfully test the server upgrade > instructions at this time, and I dont believe I will have the time, as I > will be working on pinpointing a specific java/web browser issue (a > topic for a different post) > > Thank you > > vidd > > > Kaspar Kööp wrote: > > you should also check these links out: > > > > https://wiki.ubuntu.com/LTSUpgradesHowto > > https://blueprints.launchpad.net/ubuntu/+spec/lts-upgrades > > https://wiki.ubuntu.com/LTSUpgrades > > > > k > > > > > > On 20/02/2008, *vidd* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > > wrote: > > > > I am preparing to test the ability to upgrade from 6.06.2 directly > to > > hardy, without the incremental steps between. > > > > Dapper Install > > I have no Dapper install disks handy, so I took a breezy install > > disk and installed CLI-only > > I edited the sources.list file to comment out the cd, enabled > all > > repo's, and replaced all instances of "breezy" with "dapper" > > I upgraded from breezy to dapper via apt-get update and apt-get > > dist-upgrade > > I added xubuntu to the CLI-only with apt-get install > > xubuntu-desktop > > > > Hardy Install -- phase one > > Manually edit sources.list , replacing "dapper" with "hardy" > > Upgrade via CLI with sudo apt-get update && sudo apt-get > > dist-upgrade > > Report any issues > > *****should sudo aptitude update && sudo aptitude dist-upgrade be > > tested > > as well? > > > > Hardy Install -- phase two > > Format and re-install per "Dapper Install" (see above) > > Upgrade via upgrade tool (is this available to test yet?) > > Report any issues > > > > Test system: > > Pentium II 350 MHz > > 384 MB Ram > > 15 GB hard drive > > > > > > -- > > xubuntu-devel mailing list > > [email protected] <mailto: > [email protected]> > > https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel > > > > > > > -- > xubuntu-devel mailing list > [email protected] > https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel > -- Cody A.W. Somerville
-- xubuntu-devel mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
