On 1 November 2013 21:54, Martijn van Oosterhout <klep...@gmail.com> wrote:
> Probably the import process blew up again. > > The basic issue is that nowadays the Packages files don't contain the > complete descriptions anymore, you need to combine them with the > Translation-en file. The import code was hacked to make it work and > sometimes it blows up and you get this. > > I'll try to remove the excess in the coming days... > > > Ok, so I looked into this and the problem is more subtle. As stated above, the full descriptions are no longer in the Packages files but in the Translation-en file. What appears to be happening is that when a Package changes description and that this change doesn't propagate to all architectures at the same time, then there is a package in a Packages file that refers to a description that isn't present in the Translation-en file. That is the Translation-en only contains one description per package even though there are multiple versions in the archive. I'm not entirely convinced this isn't a bug, but perhaps I'm missing something. Anyway, the code that inserts the package descriptions in the database had a problem where if it couldn't find the description in the Translation-en file, it inserted a single line description. Clearly the wrong behaviour. I added a quick hack to prevent this and today the logs show it affects at least 700(!) packages. Clearly this problem is more widespread (and older) than I thought. I'm going to put some thought into how I can nuke the bad entries without losing anything. I'll let you know when I've fixed it. Have a nice day, -- Martijn van Oosterhout <klep...@gmail.com> http://svana.org/kleptog/
