severity #906747 normal thanks I now think that this is actually a reprepro issue, and it only applies to the mutt package. Trying to poke a locally built mutt package into the archive bypassing mini-buildd yielded the same error, and I had to manually specify section and priority on the reprepro command line to get the package into the archive.
Otoh, I cannot see any difference between mutt and, for example, ser2net, a package that runs through mini-buildd just fine even if both .dsc files don't contain explicit Section and Priority lines, but have Section and Priority only listed in a "Package-List" stanza. My beef against mini-buildd is therefore reduced to the fact that it once more hides the actual error message in the logs, and that I cannot access the built packages for manual testing since they're killed off as soon as the error happens. Greetings Marc
