This was an issue for me, too. If you're using a proxy, like apt-cacher-ng,
you can't download the gpg files and the upgrade fails early. See this thread:
http://ubuntuforums.org/showthread.php?t=436018
Easy to reproduce.
--
[Hardy] do-release-upgrade doesn't retrieve hardy gpg key
https://bu
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Sorry, I finished the upgrade by taking the laptop home :)
I filed another bug for apt problems behind proxy (I used to get the gunzipped
.tar.gz file). It is reported here:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/230832
I suspect this issue will be fixed by that fix as well.
--
[Ha
@michael: That would explain things. It downloaded quite a few
packages and seemed to work ok. I have been running the computer and it
isn't asking for a distro update. All packages appear to be updating
correctly as well. So I have suffered no ill effects so far.
Doing an lsb_release -a give
@peitschie: do-release-upgrade is not designed to work for hardy->hardy
upgrades (like from beta->rc). That is the job of the normal update-
manager or for apt-get dist-ugprade. I'm susprised that it downloaded
anything at all for you, what is the output of lsb_release -a on this
system?
@Ashwin:
I have the same problem. Trying this behind a proxy.
As you can see in the wireshark output, only one request is made and no request
is made for the .gpg file.
wireshark output:
GET http://changelogs.ubuntu.com/meta-release HTTP/1.1
Accept-Encoding: identity
Cache-Control: No-Cache
Connection:
