update-manager fail release upgrade if using apt-cacher

[Paolo Benvenuto]

Binary package hint: update-manager-core

Upgrading from hardy to intrepid, do-release-upgrade stops saying:

$ do-release-upgrade
Checking for a new ubuntu release
Failed Upgrade tool signature
Done Upgrade tool
Done downloading
extracting 'intrepid.tar.gz'
authenticate 'intrepid.tar.gz' against 'intrepid.tar.gz.gpg'
exception from gpg: GnuPG exited non-zero, with code 131072
Debug information:

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

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

Authentication failed
Authenticating the upgrade failed. There may be a problem with the network or with the server.

I get the same error (last 2 lines) if I use the gui command update-manager.

I'm using apt-cacher through apt.conf, which has a line:

Acquire::http::Proxy "http://paolo:3142/";

On the contrary, all runs perfectly if I disable the apt-cacher invoking line of apt.conf

[Walter Garcia-Fontes (walter-garcia)]

Sorry that the issue got unattended at the time of report. Please feel free to reopen by marking the status as "new" if you see this in current versions of update-manager.

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

[Florian Hars (hars)]

The reason seems to be that apt-cacher has a regexp of "index files" that it revalidates to recognize updates, and the default regexp does not match "meta-release-development". If you add that, it detects the new release.

There may be another problem: if the quantal.tar.gz changes during the developent cycle, apt-cacher will not notice the change, as it assumes the tar.gz files are versioned packages that are uniquely identified by their name. That case may be solved if the regexp is changed to also match ^[a-z]+\.tar\.gz (i.e. tars without any version number). Does that file change during it's lifetime?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.