I figured the package was not imported because the non-epoch part of the version number was still lower than before. It seems like this is a bug in Maemo's package repository.

The previous version was 0:1.0.0-rc3 and the new was 1:1.0.0-0. As you see, I used the epoch of 1 to make the latter higher than the former. This made the package build without complaining on the autobuilder, but it still was not imported.

Incrementing to version 1:1.0.1-0 fixed the problem with the import, but to me this seems like a bug in the package repository's import function. In this case, there was no big problem, but if someone accidentally types 92.3.4 as the version number instead of 2.3.4, he or she will be unable to import the package without jumping to a higher version number than 92.3.4. So the whole point in using the epoch (a number and a colon in front of the version number) seems to be defeated.

If this is a bug, where should it be reported?