The upgrade to remove packages.name and the other language based columns assumes that the multi-language table (i.e. package_names) contains the same content. However, though the 4.5 migration did migrate the contents of packages.name to package_names, it was possible for packages created after the migration to set packages.name but not package_names. In this case the 5.0 migration removes the only existing record of the package name.
To resolve this, let's update the the 5.0 migration to use a query to map values from packages.name to package_names if no record currently exists for the package in package_names. We should also check the other language based columns to make sure no similar issue exists.