[Hardy] do-release-upgrade doesn't retrieve hardy gpg key

Bug #215694 reported by Philip Peitsch on 2008-04-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)

Bug Description

Binary package hint: update-manager

Currently unable to run the `do-upgrade-release -d` file supplied with the Hardy beta as it fails with the following error:

exception from gpg: GnuPG exited non-zero, with code 131072
Debug information:

gpg: WARNING: unsafe permissions on homedir `/tmp/tmpgNl7bk'

gpg: can't open `/tmp/tmpgNl7bk/hardy.tar.gz.gpg'
gpg: verify signatures failed: file open error

This is because the do-upgrade-release script doesn't seem to download the hardy.tar.gz.gpg key at any point in time. The easiest way to hack around this is to insert a "return True" in the /usr/lib/python2.5/site-packages/UpdateManager/Core/DistUpgradeFetcherCore.py at line 107... but of course this means you don't get signature checking so I wouldn't recommend it!

Ashwin (cybernytrix) wrote :

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: close
User-Agent: Python-urllib/2.5
Host: changelogs.ubuntu.com
Proxy-Authorization: Basic basicauthisdumb
Pragma: no-cache
If-Modified-Since: Tue Apr 29 19:01:56 2008

HTTP/1.1 304 Not Modified
Date: Tue, 29 Apr 2008 19:52:27 GMT
Server: Apache/2.0.55 (Ubuntu) mod_python/3.1.4 Python/2.4.3
Last-Modified: Thu, 24 Apr 2008 12:25:57 GMT
ETag: "29401e-cbb-8d27ff40"
Accept-Ranges: bytes
Cache-Control: max-age=7200
Expires: Tue, 29 Apr 2008 21:52:27 GMT
Content-Type: text/plain; charset=UTF-8
Connection: close
Age: 0

Michael Vogt (mvo) wrote :

@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: It looks like your problem is slightly different. You probably get a message like "no new release found" (or similar). Could you please try to remove /var/lib/update-manager/meta-release and run "sudo do-release-upgrade" again?

Changed in update-manager:
status: New → Incomplete
Philip Peitsch (philip-peitsch) wrote :

@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 gives:
No LSB modules are available
Distributor ID: Ubuntu
Description: Ubuntu 8.04
Release: 8.04
Codename: hardy

Ashwin (cybernytrix) wrote :

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:


I suspect this issue will be fixed by that fix as well.

Jayson Rowe (jayson.rowe) wrote :

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 the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
GeekSmith (lixo-geeksmith) wrote :

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:

Easy to reproduce.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers