The Update respository of files lacks decent filenames, the scripts don't enforce a naming system. (Bug 247619). Even with that implemented though, which will solve new files, the existing files need to be renamed to that system and the DB needs to be mass updated to reflect the new structure. Also, a side effect of the lack of Bug 247619, is that files with the same name get overwritten, etc. Leading to situations like with User Agent Switcher 0.5/0.6 where two versions point to the same file. (which happened to be 0.5 not 0.6) The files need to be verified that they are the versions the DB thinks they are, to prevent Extension update from going into an infinite loop.

What do we do with the broken ones? And how are we going into an infinite loop?

Broken ones are deleted. Infinite Loop occurs when the wrong lower version is downloaded as a higher version. Such as 0.6 being downloaded as 0.5, then Firefox thinks 0.6 still is newer.

They also need to be verified that they are the GUID the DB thinks they are. and if they're not.. the right one needs to be in the DB if it isn't.

Tweaking settings to make this stand out on my buglist. Please do not alter. The update repository *absolutely* needs to be consistancy checked before Firefox 1.0 gets released. As it's likely update-beta and update will likely still be seperate sites for the release this process will have to be done again when update-beta lands and we'll have to be very careful to maintain consistancy in the between time.

Converted the repository over to new naming, some known issues that i'll track down after the load drops. dealing with version mismatches.

All outstanding issues resolved. All items are the version they claim to be now. Though some newer versions of some items are likely to have gone missing as they were never really there. :-/

Moving more bugs to new component.

Repository was last consistency checked on 12/15. As update-beta's DevCP is now in control of the repository it should stay consistent with naming, even though Update-Beta has not yet been launched officially. This bug is now fixed.