considers dapper-commercial a third party repository and disables it

[James Troup]

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.

[Paul Sladen (sladen)]

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)]

Assigning to mvo.

[Tollef Fog Heen (tfheen)]

Michael, please get this fixed before Herd 4.

[Michael Vogt (mvo)]

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

[Michael Vogt (mvo)]

Uploaded, awaits a approval.