[hardy] current dist not found in meta-release file

Bug #174266 reported by Bogdan Butnaru on 2007-12-06
14
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Hello! I've updated from Gutsy to Hardy using the update-manager a while ago, to help with testing.

I noticed that every time I start update-manager it prints the message "current dist not found in meta-release file". Is that normal for a pre-release, or is there something missing in a config file somewhere? I seem to vaguely remember something similar around Gutsy alpha, but I haven't seen it in a long time.

The message doesn't seem to have any effect, updates work correctly.

hispanico71 (vittoriobarassi) wrote :

Same problem with i386 platform...

Bogdan Butnaru (bogdanb) wrote :

Still going on with latest Hardy updates.

Philip Peitsch (philip-peitsch) wrote :

This problem still exists trying to go from Gutsy > Hardy Beta

Philip Peitsch (philip-peitsch) wrote :
Download full text (3.4 KiB)

Okay, to update using this tool, you need to save the following text to the file /var/lib/update-manager/meta-release-lts-development NOT meta-release

Now I just need to figure out the GPG error...

=Save below this line=========
Dist: warty
Name: Warty Warthog
Version: 04.10
Date: Wed, 20 Oct 2004 07:28:17 UTC
Supported: 0
Description: This is the warty warthog release
Release-File: http://archive.ubuntu.com/ubuntu/dists/warty/Release

Dist: hoary
Name: Hoary Hedgehog
Version: 05.04
Date: Fri, 08 Apr 2005 08:18:19 UTC
Supported: 0
Description: This is the Hoary Hedgehog release
Release-File: http://archive.ubuntu.com/ubuntu/dists/hoary/Release

Dist: breezy
Name: Breezy Badger
Version: 05.10
Date: Thu, 13 Oct 2005 19:34:42 UTC
Supported: 0
Description: This is the Breezy Badger release
Release-File: http://archive.ubuntu.com/ubuntu/dists/breezy/Release

Dist: dapper
Name: Dapper Drake
Version: 6.06 LTS
Date: Thu, 01 Jun 2006 9:00:00 UTC
Supported: 1
Description: This is the Dapper Drake release
Release-File: http://archive.ubuntu.com/ubuntu/dists/dapper/Release
ReleaseNotes: http://changelogs.ubuntu.com/DapperReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/dapper/main/dist-upgrader-all/current/dapper.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/dapper/main/dist-upgrader-all/current/dapper.tar.gz.gpg

Dist: edgy
Name: Edgy Eft
Version: 6.10
Date: Thu, 26 Oct 2006 12:00:00 UTC
Supported: 1
Description: This is the Edgy Eft release
Release-File: http://archive.ubuntu.com/ubuntu/dists/edgy/Release
ReleaseNotes: http://changelogs.ubuntu.com/EdgyReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/edgy-updates/main/dist-upgrader-all/current/edgy.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/edgy-updates/main/dist-upgrader-all/current/edgy.tar.gz.gpg

Dist: feisty
Name: Feisty Fawn
Version: 7.04
Date: Thu, 19 Apr 2007 13:00:00 +0200
Supported: 1
Description: This is the 7.04 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/feisty/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/feisty-proposed/main/dist-upgrader-all/current/ReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/feisty-proposed/main/dist-upgrader-all/current/feisty.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/feisty-proposed/main/dist-upgrader-all/current/feisty.tar.gz.gpg

Dist: gutsy
Name: Gutsy Gibbon
Version: 7.10
Date: Thu, 18 Oct 2007 12:00:00 UTC
Supported: 1
Description: This is the 7.10 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/gutsy/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/ReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/gutsy.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/gutsy.tar.gz.gpg

Dist: hardy
Name: Hardy Heron
Version: 8.04 LTS
Date: Thu, 10 Apr 2008 12:00:00 UTC
Supported: 0
Description: This is the 8.04 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/hardy/Release
ReleaseNotes: http://archive.ubuntu.com/ubu...

Read more...

Alex Tan (ubuntu-10-alextan) wrote :

As per "peitschie wrote on 2008-04-11" - I followed those instructions to the letter but still get the "current dist not found in meta-release file" message when update-manager is run from the command line.

Currently running 8.04 updated from 7.10

Philip Peitsch (philip-peitsch) wrote :

What's the output of running "lsb_release -a" in a terminal?

Alex Tan (ubuntu-10-alextan) wrote :

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.04
Release: 8.04
Codename: hardy

Philip Peitsch (philip-peitsch) wrote :

Try saving a copy of that text in both /var/lib/update-manager/meta-release-lts-development and /var/lib/update-manager/meta-release . You are sure you're running the beta...?

Having been using a system upgraded this way, I am actually recommending you do a clean install with the final release. My upgrade from Beta => Final has been doing funny things with permissions and PolicyKit... the configuration upgrades haven't been handled properly somehow it seems.

Bogdan Butnaru (bogdanb) wrote :

Interesting, in /var/lib/update-manager I have only a file called meta-release-lts (without development), and it contains:
************
Dist: dapper
Name: Dapper Drake
Version: 6.06 LTS
Date: Thu, 01 Jun 2006 9:00:00 UTC
Supported: 1
Description: This is the Dapper Drake release
Release-File: http://archive.ubuntu.com/ubuntu/dists/dapper/Release
ReleaseNotes: http://changelogs.ubuntu.com/DapperReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/dapper/main/dist-upgrader-all/current/dapper.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/dapper/main/dist-upgrader-all/current/dapper.tar.gz.gpg
************
This system has been continuously updated from Dapper, so it appears this file has never been updated. (Although the file's changed date is 2008-03-13.) Do you mean I should add the two files you mentioned with the output of lsb_release -a? It seems to have a different format.

Ahh... I think you need to add that text I pasted into the meta-release-lts you just looked at.

Bogdan Butnaru (bogdanb) wrote :

I pasted the text above (with the whole list of releases) into /var/lib/update-manager/meta-release-lts and I still get the same warning message when I start update-manager.

lcottereau (laurent-cottereau) wrote :

I had the same problem (I expect it was due to an error during the upgrade process).

Updating /var/lib/update-manager/meta-release-lts with the lines for Hardy LTS (taken from /var/lib/update-manager/meta-release) did not help.

However, updating ~/.update-manager-core/meta-release-lts with the lines for Hardy LTS (taken from ~/.update-manager-core/meta-release, which is the same AFAI can see as /var/lib/update-manager) worked. The ~ is for the user launching "update-manager". Does it work for you ?

Juha Heinanen (jh-tutpro) wrote :

i just remove my update-manager related directories:

 rm -r .update-manager-core
 rm -r .update-notifier

and after that i didn't anymore get the error message.

-- juha

Bogdan Butnaru (bogdanb) wrote :

I previously got this working, but it happened again during Intrepid beta. Why does this still happen every time?

Bogdan Butnaru (bogdanb) wrote :

By the way, I removed the dirs as Juha suggested above, but I still get the message.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Bogdan Butnaru (bogdanb) wrote :

It doesn't seem to happen anymore in Intrepid.

Thanks for following up. I'm closing this report due to your last comment. Don't hesitate to submit any new bug.

Changed in update-manager:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers