Update manager does not show update to 7.10

Can you open a terminal window (Applications menu, Accessories) and type

dpkg --configure -a
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Let us know what is displayed.

First line should be

sudo dpkg --configure -a

Dear Tony,

Thanks for the quick response.

I typed in the commands you suggested.

What is displayed is (I have skipped the output of the update command):

saurabh@nprl462:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

saurabh@nprl462:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Best regards,
Saurabh

Hi,
first of all it is recommended to use Synaptic for upgrading, not the command line. Not to speak of the simple handling.
Second, the actual Version of the distribution, 7.04, has to be updated first before proceeding to the dist-upgrade to 7.10

Anyway, I would suggest to clean up the system first.
https://help.ubuntu.com/community/SynapticHowto#How%20to%20free%20disk%20space

Before a dist-upgrade there shouldn't be any third parties in the sources.list, if, I would suggest to comment them out or deactivating them within Synaptic menu -> settings -> sources, afterwards reloading the package list.

Or using the command line:
sudo apt-get autoclean
sudo apt-get autoremove
https://help.ubuntu.com/community/AptGet/Howto#Maintenance%20commands

Then proceeding with:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Good luck.

Hi Sam,

Thanks for the suggestions.

I would be most happy to use synaptic, but I was so far only following suggestions to use the command line, since my update manager does not any more permit upgrading. Also I had indeed updated 7.04 before trying to upgrade to 7.10.

As suggested by you, I cleaned up the system, and also deactivated the third party sources (in my case medibuntu) using the synaptic menu. For good measure, I also used the command line and keyed in the autoclean and autoremove apt-get commands.

I then gave the apt-get update/upgrade/dist-upgrade commands as listed by you. As before, I get:

saurabh@nprl462:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

saurabh@nprl462:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Going back to your original suggestion of use the synaptic for upgrading to 7.10, how do I do it ? So far you suggested only command line solutions.

Thanks for your help
Best regards
Saurabh

Can you post the result of the following command?

uname -r

When you run System menu, Administration, Update Manager is there no button that shows the updates or a distribution update as being available?

If not then try opening the System menu, Administration, Software Sources and in the "Download From" dropdown, choose "Other" and then the "Best Server button".
This will rewrite the software sources with the best available for your location after running some tests.

Then try Update Manager again.

Dear Tony,

Result of the command uname -r is:

2.6.20-17-generic

I had wondered myself whether the version of linux had been upgraded. But I had no way of finding out what it was earlier!

When I run Update Manager as you say, there is no button that shows that the updates or distribution update is available. I have a screen shot. I will probably have to mail this to you separately.

I tried your suggestion of using the Best Server under Software Sources, I did a reload of sources, and tried Update Manager again. No luck.

I also tried sudo apt-get upgrade, sudo apt-get dist-upgrade etc. But no result.

Regards,
Saurabh

Dear Tony,

Here is the screenshot of update manager attached.

Best,
Saurabh
_________________________________________________________________________

On Fri, 4 Jul 2008, Tony Mugan wrote:

> Your question #38004 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> Status: Open => Answered
>
> Tony Mugan proposed the following answer:
> Can you post the result of the following command?
>
> uname -r
>
> When you run System menu, Administration, Update Manager is there no
> button that shows the updates or a distribution update as being
> available?
>
> If not then try opening the System menu, Administration, Software Sources and in the "Download From" dropdown, choose "Other" and then the "Best Server button".
> This will rewrite the software sources with the best available for your location after running some tests.
>
> Then try Update Manager again.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/38004/+confirm?answer_id=5
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> You received this question notification because you are a direct
> subscriber of the question.
>

This is one way of determining which version of Ubuntu you have running

uname -r

One thing you could do is replace the respositories yourself

sudo gedit /etc/apt/sources.list

Any line with a # at the start is commented out so you can ignore them
All other lines that contain "edgy" can be replaced with "gutsy".

Then back into Update Manager and reload.

Hi,
first of all 7.04 ist named "Feisty" and can be upgraded to 7.10 "Gutsy", it is not possible to upgrade directly from Edgy 6.10 to Gutsy 7.10.
https://help.ubuntu.com/community/UpgradeNotes

The command to find out about your current release is:
lsb_release -a
It shows for example:
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy

In the graphical interface (GUI) this can be found in system administration -> system monitor -> TAB system
Also the version of the current Kernel appears there.
Or using this command, which includes also whether the system architecture is 32 or 64 bit:
uname -a

Back to Synaptic:
Please check in the menu -> preferences -> software sources -> TAB updates : Show new distribution releases, if there are regular upgrades activated.
Is there maybe also checked that upgrades should be downloaded in the background, means hidden?
Just go through all TABs and check options for your needs, but the default settings are usually set correct.

Please check in preferences -> TAB distribution which behavior on updating is activated, it should be highest version.

Is there a notification area in the panel activated which shows you when an update is available with a red symbol?

If everything shows you correct settings and upgrading still doesn't work, please copy and paste the content of sources.list in here to check on this.

Thanks.

Ooops, yes "feisty" to "gutsy" is the correct migration.

Normal behaviour is for the Distribution upgrade to be offered once you have got all the latest updates which you confirmed earlier with
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Software Sources is under the Administration menu.
On the Updates Tab, you should have "normal releases" selected under the "Release Upgrade" dropdown list.

Dear Tony,

On Sat, 5 Jul 2008, Tony Mugan wrote:

>
> One thing you could do is replace the respositories yourself
>
> sudo gedit /etc/apt/sources.list
>
> Any line with a # at the start is commented out so you can ignore them
> All other lines that contain "edgy" can be replaced with "gutsy".
>
> Then back into Update Manager and reload.

Thanks for the suggestions. I think this will probably the only way out.
However, I still wonder what it is on my computer which tells the update
manager that I do not need to upgrade to gutsy, and whether there is a
way to get around this.

Best regards,
Saurabh

Dear Sam,

Thanks for the commands for knowing the installed linux versions.

>
> Back to Synaptic:
> Please check in the menu -> preferences -> software sources -> TAB updates : Show new distribution releases, if there are regular upgrades activated.
> Is there maybe also checked that upgrades should be downloaded in the background, means hidden?
> Just go through all TABs and check options for your needs, but the default settings are usually set correct.
>

Under Ubuntu updates, what is checked is "Important securate updates". I
tried checking also "Unsupported updates", but that did not help.
Under Automatic Updates, what is checked is "Only notify about available
updates", and not "Download all updates in the background.

> Please check in preferences -> TAB distribution which behavior on
> updating is activated, it should be highest version.
>

Yes, I have checked "Always prefer the highest version"

> Is there a notification area in the panel activated which shows you when
> an update is available with a red symbol?

There was a notification in the panel when updates were available, and I
have updated all packages whenever the red symbol appear. In fact while
I was typing this, the red symbol appeared and I updated -- guess what
-- the update manager package!

I would like to remind you that the update manager did at one time show
me that upgrade to 7.10 was available. So at that time my setting -- in
the sources, in the preferences of synaptic manager, etc. were correct.
After that I did not change any of these -- except to exclude medibuntu.
So the problem lies somewhere else.

>
> If everything shows you correct settings and upgrading still doesn't
> work, please copy and paste the content of sources.list in here to check
> on this.
>

Here we go:

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://ubuntu.dcc.fc.up.pt/ feisty main restricted universe
deb-src http://ubuntu.dcc.fc.up.pt/ feisty main restricted

## Major bug fix updates produced after the final release of the
## distribution.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ubuntu.dcc.fc.up.pt/ feisty multiverse
deb-src http://ubuntu.dcc.fc.up.pt/ feisty multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://in.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse
# deb-src http://in.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse

deb http://ubuntu.dcc.fc.up.pt/ feisty-security main restricted universe
deb-src http://ubuntu.dcc.fc.up.pt/ feisty-security main restricted
deb http://ubuntu.dcc.fc.up.pt/ feisty-security multiverse
deb-src http://ubuntu.dcc.fc.up.pt/ feisty-security multiverse
deb http://archive.ubuntu.com/ubuntu/ feisty-proposed restricted main multiverse universe
deb http://archive.ubuntu.com/ubuntu/ feisty-backports restricted main multiverse universe

Dear Tony,

>
> Normal behaviour is for the Distribution upgrade to be offered once you have got all the latest updates which you confirmed earlier with
> sudo apt-get update
> sudo apt-get upgrade
> sudo apt-get dist-upgrade
>
> Software Sources is under the Administration menu.
> On the Updates Tab, you should have "normal releases" selected under the "Release Upgrade" dropdown list.
>

Under Software Sources Updates Tab, I see "Ubuntu updates" and
"Automatic updates". I dont see "Release upgrade". In any case, now I
have checked: Important security upgrades and recommended upgrades. So
I don't know what is meant by "normal releases". But I hope these should
do.

(Clarification: when I sent the sources.list, I had proposed updates and
backport updates checked -- by mistake. These were not checked when I
had actually tried the updates. )

Best regards,
Saurabh

Hi,
sources.list looks ok for me, if backported und proposed are commented out and also the settings are ok.
Since you've started a dist upgrade it should content Gutsy, so please show the output from
lsb_release -a

Back to your entry, you were dist upgrading already and the process interrupted, because of less memory, did you check this now after cleaning up?
To find out type in a Terminal
df -h

If you still need more space try cleaning up with
sudo apt-get clean

to repair further steps can be taken, as Tony said above, with
sudo dpkg --configure -a

finally to try dist upgrading again, all "feisty" in your sources.list should be "gutsy" and then proceed with the commands provided above.

Hi Sam,

Thanks for taking out some more time to write.

> sources.list looks ok for me, if backported und proposed are commented out and also the settings are ok.
> Since you've started a dist upgrade it should content Gutsy, so please show the output from
> lsb_release -a
>

saurabh@nprl462:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.04
Release: 7.04
Codename: feisty

> Back to your entry, you were dist upgrading already and the process interrupted, because of less memory, did you check this now after cleaning up?
> To find out type in a Terminal
> df -h
>
> If you still need more space try cleaning up with
> sudo apt-get clean
>

After clean I have 1.3G in / and 1.2G in /usr. I hope that will do. (I
did not note how much the message on trying the update to gutsy said it
would need).

> to repair further steps can be taken, as Tony said above, with
> sudo dpkg --configure -a
>
> finally to try dist upgrading again, all "feisty" in your sources.list
> should be "gutsy" and then proceed with the commands provided above.
>

I will some day do this -- as I do want to upgrade to gutsy. However, I
would really like know why update manager does not give the option of
upgrade like it used to. If there is no simple (or as you and Tony
probably agree, not even a complicated way) of restoring the function of
Update Manager, I would like to report it as a bug.

Please let me know what you and Tony feel.

Thanks.

Best regards,
Saurabh

Hi,
ok, as we can see there is still Feisty 7.04 on your system, means no dist-upgrade was made.
From my view I'm certain it's not related to a bug and since we try to help and provide you with commands it shouldn't be complicated to reach the result that your system will upgrade to Gutsy.
Did you try this command and what's the output
sudo dpkg --configure -a

Please check in Synaptic if those packages are installed (search button in the menu):
update-manager
update-manager-core
update-notifier
update-notifier-common
ubuntu-desktop

They all should be installed, then switch to the main server in preferences -> sources, reload packages list.
What happens?

Dear Sam,

Thanks for your mail.

>> From my view I'm certain it's not related to a bug

But it is a bug which has been reported:
https://bugs.launchpad.net/bugs/149203

So I added a line there sharing my experience.

>and since we try to help and provide you with commands it shouldn't be
>complicated to reach the result that your system will upgrade to Gutsy.

I agree that with your suggestions, I should be able to upgrade to
Gutsy. I am not in a hurry since Feisty works well by and large. I would
greatly prefer it if the update can be done through update-manager.
It is more that it has become a sort of a challenge to understand what
is going wrong!

> Did you try this command and what's the output
> sudo dpkg --configure -a
>

I tried it: there is no output.

> Please check in Synaptic if those packages are installed (search button in the menu):
> update-manager
> update-manager-core
> update-notifier
> update-notifier-common
> ubuntu-desktop
>

They were all already installed, except update-notifier-common, which
"search" did not show up at all.

> They all should be installed, then switch to the main server in preferences -> sources, reload packages list.
> What happens?
>

I did as suggested, started update-manager, still doesn't show option
for
upgrade to 7.10.

I tried, after this, sudo apt-get update, upgrade, dist-upgrade, no
luck.

I want to tell you something else I tried earlier: seeing some postings
on problems with update-manager, I looked at the file
.update-manager-core/meta-release. I found:

---------------------------------------
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"><!--BODY{background-color:#ffffff;font-family:verdana,sans-serif}PRE{font-family:sans-serif}--></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to process the request:
<PRE>
GET /meta-release HTTP/1.1
Accept-Encoding: identity
Host: changelogs.ubuntu.com
Cache-Control: No-Cache
Connection: close
Pragma: no-cache
User-Agent: Python-urllib/2.5

</PRE>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Invalid Request
</STRONG>
</UL>

<P>
Some aspect of the HTTP Request is invalid. Possible problems:
<UL>
<LI>Missing or unknown request method
<LI>Missing URL
<LI>Missing HTTP Identifier (HTTP/1.0)
<LI>Request is too large
<LI>Content-Length missing for POST or PUT requests
<LI>Illegal character in hostname; underscores are not allowed
</UL>
<P>Your cache administrator is <A HREF="mailto:<email address hidden>"><email address hidden></A>.

<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Fri, 11 Jul 2008 04:43:01 GMT by prlmisc.prl.res.in (squid/2.6.STABLE4)
</ADDRESS>
</BODY></HTML>
---------------------------------------------------

Sorry for including this long file (this is actually what I got today,
but earlier it was a similar file), but I did not want to cut something
which would make it look funny. Obviously, something was going wrong. So
I copied the meta-release file from another machine (running Hardy). But
again, on starting update-manager, a similar HTML file got overwritten.

Guessing that there may a permission problem, I copied the meta-release
file from changelogs.ubuntu.com (I figured this looking at some python
file which update-manager calls), and started update-manager from the
command line with a sudo:

sudo update-manager -c

Indeed, update-manager opened showing an option to upgrade to 7.10. (I
had also, following some old postings, copied the meta-release file into
/var/lib/update-manager/ I dont know if this was relevant). It also
gave a warning:

warning: could not initiate dbus

I eagerly clicked on the upgrade button. But the upgrade hung after a
while. I have repeated this process just now, and I post the messages
below:

------------------------------------------
Traceback (most recent call last):
   File
"/usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py", line
914, in on_button_dist_upgrade_clicked
     fetcher.run()
   File
"/usr/lib/python2.5/site-packages/UpdateManager/Core/DistUpgradeFetcherCore.py",
line 153, in run
     if not self.showReleaseNotes():
   File
"/usr/lib/python2.5/site-packages/UpdateManager/DistUpgradeFetcher.py",
line 79, in showReleaseNotes
     release_notes = urllib2.urlopen(uri)
   File "/usr/lib/python2.5/urllib2.py", line 121, in urlopen
     return _opener.open(url, data)
   File "/usr/lib/python2.5/urllib2.py", line 366, in open
     protocol = req.get_type()
   File "/usr/lib/python2.5/urllib2.py", line 241, in get_type
     raise ValueError, "unknown url type: %s" % self.__original
ValueError: unknown url type:
------------------------------------------------------------

The update-manager window is hazy at this point, and nothing happens
for a long time. So I interrupted with ^C. Then, the following
additional messages get appended:

---------------------------------------
Traceback (most recent call last):
   File "/usr/bin/update-manager", line 91, in <module>
     app.main(options)
   File
"/usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py", line
1017, in main
     gtk.main()
KeyboardInterrupt
-----------------------------------------

Of course, all the above steps are reproducible: If I start update
manager from the system -> adminstration , again the meta-release file
gets over written by some garbage.

Please let me know if this helps.

Best regards,
Saurabh

Hi,
thanks for the information and yes, it is a challenge.
Unfortunately the bug you've joined is old and doesn't provide information how to proceed.
Maybe you also like to add the link to this question.
Additional there are relevant logs in /var/log/dist-upgrade, e.g. apt- and main-log.
Or using command line for selecting errors:
grep -i error /var/log/dist-upgrade/*

Are there broken packages listed in Synaptic (to find in the side menu -> status or -> user defined)?
Because of
>File "/usr/lib/python2.5/urllib2.py", line 241, in get_type
     raise ValueError, "unknown url type: %s" % self.__original
ValueError: unknown url type:<
you could try to reinstall the package python2.5 and please also check if python-vte is installed.

Please also check if the first two lines of /etc/hosts are set correct.

Quote:
>...copied the meta-release file into
/var/lib/update-manager/ I dont know if this was relevant)...<

The mentioned folder is empty here.

For the record you could report this issue here:
http://bugs.python.org/

I think this isn't trivial and geeks should have a look at it.

> Unfortunately the bug you've joined is old and doesn't provide information how to proceed.
> Maybe you also like to add the link to this question.

Sorry for the long silence. I did add something to the bug, but I forgot
to add a link to this question. I am not sure how to do it, but I will
try to do it.

> Additional there are relevant logs in /var/log/dist-upgrade, e.g. apt- and main-log.
> Or using command line for selecting errors:
> grep -i error /var/log/dist-upgrade/*
>

I am sending you the relevant /var/log/dist-upgrade/main.log file as
attachment. The apt.log file in this can be confusing, because that is
from a later attempt at doing an upgrade with -p option. This had a
problem because I had hplip package installed from a tarball. (I have
now uninstalled it).

> Are there broken packages listed in Synaptic (to find in the side menu -> status or -> user defined)?

No there are not broken packages in synaptic.

> Because of
>> File "/usr/lib/python2.5/urllib2.py", line 241, in get_type
> raise ValueError, "unknown url type: %s" % self.__original
> ValueError: unknown url type:<
> you could try to reinstall the package python2.5 and please also check if python-vte is installed.
>

I did a reinstall of python2.5, but it did not help.

> Please also check if the first two lines of /etc/hosts are set correct.
>

Yes, they seem to be correct.

> Quote:
>> ...copied the meta-release file into
> /var/lib/update-manager/ I dont know if this was relevant)...<
>
> The mentioned folder is empty here.
>

I know now that this is relevant. With some trials, I have understood
one of the problems I had: That of network proxy setting. I had setting
for direct connection to network (even though for browsers I need a
proxy setting) because for changing repositories, this is the setting
which works. Using a the setting of the proxy server leads to errors
while loading package information (I dont know why). So during all my
experiments, the proxy was not set. Then, if I tried to start
update-manager, the files

.update-manager-core/meta-release

and

/var/lib/update-manager/meta-relase

got overwritten with garbage.

After setting the correct ip address of the proxy server, not only are
these files preserved, but I also can get an option in update-manager
for upgrade to 7.10.

However, I still cannot upgrade to 7.10 on clicking on the upgrade
button -- the update-manager hangs, with the same error message as
before.

Incidentally, this does not work if the file
/var/lib/update-manager/meta-release is absent or corrupt.

> For the record you could report this issue here:
> http://bugs.python.org/
>
> I think this isn't trivial and geeks should have a look at it.
>

OK, I will try to do this when I find time.

Best regards,
Saurabh

> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/38004/+confirm?answer_id=18
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi,
wonderful, that was the first time you've mentioned proxy settings.
The setting in Synaptic should be direct connection in settings -> network
If you have such a file in /etc/apt/apt.conf remove the proxy entry.
And what about the settings in system -> preferences -> network proxy?

After removing any proxy settings repeat the mentioned commands above like
sudo dpkg --configure -a
and a restart of the system wouldn't hurt either.

Regarding the bug 149203 just copy&paste the url from this question there.
There is also the function to load up the logs, for each log it will generate a new post, don't worry about that and about reporting back any time.

Finally and off topic, maybe rethink why using a proxy if you are behind a router and using Ubuntu.

Hi Sam,

> wonderful, that was the first time you've mentioned proxy settings.
> The setting in Synaptic should be direct connection in settings -> network
> If you have such a file in /etc/apt/apt.conf remove the proxy entry.
> And what about the settings in system -> preferences -> network proxy?
>

Perhaps I was not clear:

1. For a change of software source, and downloading package information,
it is essential to have system -> preferences -> network proxy set to
direct connection (does not matter what the synaptic -> network setting
is)

2. For update-manager to show possible upgrade to 7.10, it is necessary
to have system -> preferences -> network proxy set to the ip address of
the proxy server. It does not work otherwise -- using direct connection
under network proxy replaces the .update-manager-core/meta-release file
by garbage.

So there is some sort of conflict.

> After removing any proxy settings repeat the mentioned commands above like
> sudo dpkg --configure -a
> and a restart of the system wouldn't hurt either.
>

I tried this, it did not work.

Today, I tried first to start update-manager from system ->
administration, with the network proxy set to the proxy server ip. I got
the option to upgrade, but on clicking the button, it hung, giving the
same message in /var/crash/_usr_bin_update-manager.1000.crash

Somehow, I decided to use

update-manager -c -d

and guess what, I could get the update to work! So while I am writing
this, the upgrade is proceeding and promises to finish in 9 hours.
I hope that for some reason the power does not go off during this.

I will write a report later on how the upgrade fares.

> Finally and off topic, maybe rethink why using a proxy if you are behind
> a router and using Ubuntu.
>

I did not quite follow this remark. Can you please explain a bit. I
think you are saying something very useful.

Best regards,
Saurabh

> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/38004/+confirm?answer_id=20
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi Saurabh,
first of all I cross my fingers that the upgrade is a success and congratulation to your patience and effort.
From this point of view the proxy settings seemed to mess up the procedure of upgrading and this wouldn't be the first time.
http://ubuntuforums.org/showthread.php?s=e5ac0a545f9e5e5af15e59bb007a4a7e&t=828243&highlight=update+manager&page=2

http://ubuntuforums.org/showthread.php?s=e77e743e3b76dc17745551853e308051&t=805535&highlight=upgrade%2Bproxy

However, the use of a proxy or not is a very personal subjective issue. Although the objective use of a proxy can be and probably will be discussed forever. The regarding question is how to gain anonymity and if a proxy is a reliable answer to that.

https://help.ubuntu.com/community/AptGet/Howto#Setting%20up%20apt-get%20to%20use%20a%20http-proxy

Here's a report on the update to gutsy:

Once it started, the update was smooth. There was a slight hitch that it
ran out of space in / and stalled. I freed space by moving a couple of
directories from / to /home (which is a different partition),
maintaining a link.

In short, the main problem was knowing the correct proxy settings and
making sure that the meta-release related files were intact. However,
there was no warning that such problems might arise.

Thanks for all the help and suggestions.

Best regards,
Saurabh

_________________________________________________________________________

Saurabh D. Rindani Telephone: +91 79 26314462
Theoretical Physics Division Fax : +91 79 26314460, 26314900
Physical Research Laboratory Email : <email address hidden>
Navrangpura Web : http://www.prl.res.in/~saurabh
Ahmedabad 380009
_________________________________________________________________________

Hi,
thanks for the report and congratulations.
For example, I've made myself a todo list before upgrading and never experienced any problems. One todo is to clean the apt cache and update the older version. Old Kernel images for example occupy lots of space and can be removed within Synaptic.
A proxy is no default setting, so before I try out system changes I go and research howtos and consequences.
To have the home/user directory on a different partition is a very good idea in case of any failure.
However now, enjoy Gutsy, it's a comfortable version, but be told, Hardy, in my view of course, is the best what I've experienced until now.

Dear Sam,

I have upgraded to hardy -- not without problems, though! Configuration
of locales got stuck. Killing the process several times helped. But
finally, going by workarounds in bug reports, I had to reboot with an
earlier kernel, and the configure locales, and then running system ->
adminstration -> language support.

Hardy also upgraded firefox to 3.0, and in the process, it did not
update my bookmarks. I had to go to the backup of bookmarks and import
from there.

So I am all ready to get the best of hardy.

Thanks and regards,
Saurabh

_________________________________________________________________________

Saurabh D. Rindani Telephone: +91 79 26314462
Theoretical Physics Division Fax : +91 79 26314460, 26314900
Physical Research Laboratory Email : <email address hidden>
Navrangpura Web : http://www.prl.res.in/~saurabh
Ahmedabad 380009
_________________________________________________________________________

On Thu, 24 Jul 2008, Sam wrote:

> Your question #38004 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> Status: Open => Answered
>
> Sam proposed the following answer:
> Hi,
> thanks for the report and congratulations.
> For example, I've made myself a todo list before upgrading and never experienced any problems. One todo is to clean the apt cache and update the older version. Old Kernel images for example occupy lots of space and can be removed within Synaptic.
> A proxy is no default setting, so before I try out system changes I go and research howtos and consequences.
> To have the home/user directory on a different partition is a very good idea in case of any failure.
> However now, enjoy Gutsy, it's a comfortable version, but be told, Hardy, in my view of course, is the best what I've experienced until now.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/38004/+confirm?answer_id=24
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/38004
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi Saurabh,
thanks again for reporting your advanced upgrading procedures, I have to use the plural now.
I'm sorry for the problems you've experienced, but there isn't a manifest which gives a 100% warranty of flawless changes of course. Nevertheless you've made a good job and made backups.
To your kind interest there is a howto relating to Hardy, which is not offical and there exist of course lots more, on top the official community docs.
http://ubuntuguide.org/wiki/Ubuntu:Hardy

However, enjoy Ubuntu and to get not off topic please consider this question as solved, thanks.