considers dapper-commercial a third party repository and disables it

Bug #66783 reported by James Troup on 2006-10-18
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Medium
Michael Vogt

Bug Description

I just upgraded Avril's laptop from dapper to edgy and the upgrade process warned me that it had detected a 3rd party repository and disabled it for my own safety. But in fact the "3rd party repository" was dapper-commercial. Obviously, that shouldn't be considered 3rd party or disabled on upgrade, but rather changed to edgy like all the other sources.list entries.

Michael Vogt (mvo) on 2006-10-19
Changed in update-manager:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Paul Sladen (sladen) wrote :

Technically it probably is a 3rd party repository; as the software available in 'dapper-commerical' may not actually be available in 'edgy-commerical'.

Perhaps a generic method for rewriting all the "closely supported" archives could be added so that backports/-commerical both get upgraded but other "unknowns" get disabled.

Tollef Fog Heen (tfheen) wrote :

Assigning to mvo.

Changed in update-manager:
assignee: nobody → mvo
Tollef Fog Heen (tfheen) wrote :

Michael, please get this fixed before Herd 4.

Michael Vogt (mvo) wrote :

Thanks for your bugreport.

This is fixed in my local repository (for edgy->feisty) and it will be part of the next upload.

Cheers,
 Michael

Changed in update-manager:
status: Confirmed → Fix Committed
Michael Vogt (mvo) wrote :

Uploaded, awaits a approval.

Albin Tonnerre (lutin) on 2007-03-13
Changed in update-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers