Sponsored Link
If you want to know what are new features in this release check here
Upgrade from 7.10 to 8.04 LTS follow this procedure
Before you start Upgrading you need to know the following points
- You need to make sure you have complete backup of your machine
- Be sure that you have all updates applied to your current version of Ubuntu before you upgrade.
Now you need to Press Alt-F2 and type update-manager -d Click on Run.
or
Go to System -> Administration -> Update Manager
Starting Update Manager in Progress
Now you can see New Distribution release 8.04 is available for upgrade click on upgrade
This will show you Ubuntu 8.04 Hardy Heron Release notes click on upgrade
Now it will prompt for root password enter your root password click ok
Preparing for upgrade in progress
If you are using any third party sources in your /etc/apt/sources.list file it will be disabled at the time of upgrade process click close
If you have any unsupported libs installed in your machine you can see similar to the following screen click close
Starting the upgrade process window click on Start Upgrade
Downloading the new Packages in Progress
After downloading this will start the installation of packages if you have more than one display managers installed this will prompt you to choose your default display manager and click Forward
Installing Packages in Progress
Installing Packages in Progress in Terminal
If you have installed any applications this will prompt for you to restart the services with new libs click forward
Cleaning Up process in Progress
You need to restart the system to complete the Upgrade by clicking “Restart Now”
Testing Your Upgrade
You can check the ubuntu version installed using the following command
sudo lsb_release -a
update-manager -d !!!!!
I have a Gutsy server, and this is my first upgrade on it.
How can I upgrade through SSH?
try this procedure
Preparing for the Upgrade – Ubuntu Server
You’ll want to make sure that your current installation is completely up to date first. Repeat the below steps until no more updates are offered:
sudo aptitude update
sudo aptitude upgrade
sudo aptitude dist-upgrade
Upgrading Ubuntu 7.10 to 8.04 – Ubuntu Server
To upgrade your Ubuntu Server from 7.10 to 8.04 follow these few steps and you’ll be presented with a menu that will walk you through the upgrade process.
sudo aptitude install update-manager-core
sudo do-release-upgrade
Maybe you should try the following argument
ssh -Xit direct the program I/O to your local X Server if the other machine allows it.
I never tried to upgrade through ssh though.
@Admin
Thanx, I’ll give it a try.
cheers !
finally it is released.
i have installed hardy, i am using hardy for this comment !
have fun guysss !
Ub-noob, you’d do something like –
ssh -X user@domain update-manager
My advice for any newbie attempting a release upgrade is to make sure that you have packages like apt-listbugs, apt-listchanges and wajig installed. They may just save you from some unnecessary anxieties and/or a hosed system.
Prepare for having to make decisions on quite a few unresolved bugs. Many of whom (including some very grave and major ones such as some base packages (e.g. apt), readers simply have no choice but to put them on hold till there are fixes for them. e.g.
serious bugs of synaptic (0.60ubuntu5 -> 0.61ubuntu9)
#456044 – FTBFS with GCC 4.3: missing #includes (Fixed: synaptic/0.61+nmu1)
serious bugs of gnome-app-install (0.4.13-0ubuntu1 -> 0.5.2.7-0ubuntu1)
#476287 – user strings spread confusion about contrib & non-free (Fixed: gnome-app-install/0.5.2.7-1)
serious bugs of apt (0.7.6ubuntu14.1 -> 0.7.9ubuntu17)
#476696 – cdebootstrap should install recommends (Fixed: debian-archive-keyring/2008.04.16+nmu1)
Merged with: 476689
critical bugs of gdebi-core (0.3.2ubuntu1 -> 0.3.8)
#469593 – Gdebi does not install nothing
grave bugs of synaptic (0.60ubuntu5 -> 0.61ubuntu9)
#452377 – A package marked for reinstall, if conflicting, is removed *without warning*
grave bugs of subversion (1.4.4dfsg1-1ubuntu3 -> 1.4.6dfsg1-2ubuntu1)
#477772 – subversion: Segfaults during operation
grave bugs of update-manager (1:0.81 -> 1:0.87.24)
#447641 – update-manager: Won’t launch
Merged with: 434025 451459
#449040 – update-manager: Smart Upgrade removes packages with dependency problems without confirmation
grave bugs of apt (0.7.6ubuntu14.1 -> 0.7.9ubuntu17)
#474947 – MMap, again; and won’t be denied this time
#465241 – bibtex2html has been installed with an unmet dependency
grave bugs of wvdial (1.56-1.2ubuntu2 -> 1.60.1)
#461365 – wvdial 1.56-1.2 is uninstallable
grave bugs of gdebi (0.3.2ubuntu1 -> 0.3.8)
#440834 – gdebi : error on installing deb
#453188 – Cannot execute gdebi installer
grave bugs of ntfsprogs (1.13.1-6 -> 2.0.0-1ubuntu2)
#470512 – ntfsprogs: unclean unmount during normal shutdown
grave bugs of libpam-modules (0.99.7.1-5ubuntu1 -> 0.99.7.1-5ubuntu6)
#444427 – libpam-modules: pam_group: bad users matching
serious bugs of acpid (1.0.4-5ubuntu8 -> 1.0.4-5ubuntu9)
#463535 – logout hangs with libgtk2.0-0 2.12.5-2
serious bugs of apt (0.7.6ubuntu14.1 -> 0.7.9ubuntu17)
#476532 – debian-archive-keyring: unconfigurable due to missing gnupg
serious bugs of aptitude (0.4.6.1-1ubuntu3 -> 0.4.9-2ubuntu5)
#472551 – aptitude accepts to remove essential packages
Notes on some of the terminology used in apt-listbugs.
=> Bug resolved, package can be safely installed again
=> Fix is on the way i.e. perhaps in the next minor version release of the affected package
=> No solution to bug yet.
=> Not a Ubuntu issue, forwarded to upstream devs awaiting their decision and solution.
For what it iis worth, to put a buggy package on hold i.e. prevent which ever package manager you are using from upgrading it, just issue “sudo wajig hold packagename”. To view what are the packages on hold, do a “sudo wajig list-hold”. To unhold a held package, “sudo wajig unhold packagename”
Hmmm I’ll retry the part on the status again…seems like some tags are forbidden…
Notes on some of the terminology used in apt-listbugs.
fixed => Bug resolved, package can be safely installed again
pending-fixed => Fix is on the way i.e. perhaps in the next minor version release of the affected package
pending => No solution to bug yet.
forwarded => Not a Ubuntu issue, forwarded to upstream devs awaiting their decision and solution.
I’m using Gutsy Gibbon on a Dell laptop D600, and it’s not possible for me to upgrade to Hardy Heron. The upgrade message simply does not appear in my Update Manager screen, not even after several Checks. I’m fully updated. What am I doing wrong?
Harrie
Harrie,
Press Alt-F2 and type gksu “update-manager -d”
I tried to upgrade Gutsy to Hardy on my Toshiba laptop but it stalled in the process. when I try again The update package tells me that ‘Not all updates can be installed’ and suggest that I run a Partial Upgrade. When I click partial Upgrade it brings up the Distribution Upgrade window for running the partial upgrade but once this starts prearing the uprade the program stalls (while reading the cache)
Patrik,
I am facing the same issue as Harrie. I tried – Press Alt-F2 and type gksu “update-manager -d”. Still the
Upgrade message is not appearing in the update manager. Is there any other setting that needs to be enabled?
Cheers.
Hey guys,
I’ve posted this on the Ubuntu forums without luck. I’m trying upgrade from 7.10 and I get an authentication error. If I run upgrade manager from the terminal, I get this:
cully@AM/FM:~/.gnup[/email]g$ sudo update-manager
warning: could not initiate dbus
Fontconfig error: Cannot load default config file
Fontconfig error: Cannot load default config file
extracting ‘/tmp/tmpmvI8Vq/hardy.tar.gz’
authenticate ‘/tmp/tmpmvI8Vq/hardy.tar.gz’ against ‘/tmp/tmpmvI8Vq/hardy.tar.gz.gpg’
exception from gpg: GnuPG exited non-zero, with code 131072
Debug information:
gpg: WARNING: unsafe permissions on homedir `/tmp/tmpmvI8Vq’
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768
gpg: Signature made Fri 09 May 2008 11:46:50 AM CDT using DSA key ID 437D05B5
gpg: failed to create temporary file `/tmp/tmpmvI8Vq/.#lk0x8123310.AM/FM.7728′: No such file or directory
gpg: fatal: can’t create lock for `/tmp/tmpmvI8Vq/trustdb.gpg’
Looks like a gnupg error – any ideas????
Any advice would be greatly appreciated!
-C
try to run the following commands
sudo apt-get update
sudo apt-get dist-upgrade
If you still having the same problem try the following command
sudo do-release-upgrade
Thanks for the reply. The first two suggestions don’t return any results – it looks like I’m fully upgraded to 7.10.
The sudo do-release-upgrade returns me the exact same error as I posted before.
Hi, i get the same problem, none of the above suggestions have worked. tried in irc too with no luck on a solution.
Fully updated in 7.10, “sudo do-release-upgrade” returns “Checking for a new ubuntu release
No new release found”
Ok fix found (mine is upgrading now atleast)
gksudo gedit /etc/apt/sources.list
change every word gutsy to hardy (be sure to leave the # in front of cd)
sudo apt-get update
sudo apt-get dist-upgrade
Hi,
I trying to upgrade 7.10 gutsy to 8.04 hardy.
i have done following steps to do that.
sudo aptitude upgrade
sudo aptitude dist-upgrade
sudo aptitude install update-manager-core
sudo do-release-upgrade
It’s given below error.
please, can any one give solution?
rook@rook-desktop:~$ sudo aptitude upgrade
W: The “upgrade” command is deprecated; use “safe-upgrade” instead.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
rook@rook-desktop:~$ sudo aptitude dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
rook@rook-desktop:~$
rook@rook-desktop:~$
rook@rook-desktop:~$ sudo aptitude install update-manager-core
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information… Done
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Building tag database… Done
rook@rook-desktop:~$ sudo do-release-upgrade
Could not find platform independent libraries
Could not find platform dependent libraries
Consider setting $PYTHONHOME to [:]
‘import site’ failed; use -v for traceback
Traceback (most recent call last):
File “/usr/bin/do-release-upgrade”, line 3, in
import warnings
File “/usr/lib/python2.5/warnings.py”, line 7, in
import linecache
File “/usr/lib/python2.5/linecache.py”, line 9, in
import os
ImportError: No module named os
rook@rook-desktop:~$
This is just a small caveat for those of you wanting to do an upgrade from 7.10 to 8.04, and that have lots of hard drives of different types … especially if you’re doing it over ssh:
The names of the drives in /dev might change during the upgrade to 8.04 … I have 4 ata and 2 sata drives, Listing the drives in the same order the changes are:
– 7.10: hda, hdb, hdc, hdd, sda, sdb.
– 8.04: sdc, sdd, sde, sdf, sda, sdb.
In other words, my system previously booted from hda, and now from sdc … (this is done automatically by do-release-upgrade and has not given me any problems).
Of course YMMV, but I would suggest you disable all drives before doing the upgrade (except the ones that’ll hold your system, of course) and then fixing it once rebooted. I had to drag a screen and keyboard to my headless server ’cause it just wouldn’t boot – as the older drives no longer existed in /dev, and the system tries to mount them, you get dropped to a maintenance shell … no ssh access.
I’ve fixed fstab and everything is working just fine now.
I was having problems upgrading. When I tried to do an apt-get update I kept getting 404 errors on all the gutsy directories. I got the same errors (of course) when trying to do apt-get upgrade.
However, what did work for me was:
sudo do-release-upgrade
This updated all my apt-get sources to hardy and then did the OS upgrade. It hasn’t finished yet (running about an hour so far) but it looks like it will. Certainly much further than I was with just apt-get or aptitude.
Thanks!!
– James
I was worried about upgrading. Ububntu Gutsy has been working fine for so long and I’m a newbie (well using Ubuntu for 2 years but never having difficulties, you don’t learn much about the workings.)
I upgraded one week ago. Gutsy Gibbon had no flash player, Wine didn’t work, the video was never quite right, but it worked.
After several hours downloading 1365 packages (that’s what it said), the actual installation took about 40 minutes.
The desktop came up, I logged on, everything worked and was / is about 3 times faster. Flash works, the screen resolutions that I have available are great, Wine works, and even Firefox is more stable (it used to shut down after 6 days because I keep over 60 tabs on 4 desktops running)
I never expected to have my main computer working so well!!!
Even Gutsy Gibbon was better than my Winblows computers – now I would like to toss them – but can’t – one belongs to the company I work for.
Great – seamless upgrade.