Package: ftp.debian.org
Severity: important

gcc-5-ports is rejected because the package used for the build is not yet
accepted.  This is sub-optimal.  I understand that you don't want to accept
packages which are built against outdated packages, however in this case a valid
upload is rejected for administrative reasons.

And even if the gcc-5 upload is accepted, I'm not able to re-upload the
gcc-5-cross package without changing the md5sums/signature of the package.

Hi,

Matthias Klose <doko@debian.org> writes:

Was the rejected upload also NEW?

We require that Built-Using sources are in the target archive, though I
guess for NEW packages having them in NEW might be okay too (but then
they would have to be accepted in the right order or would get rejected
at that stage).

I don't want dak to copy things out of new in order to fulfill
Built-Using dependencies.

Only the .changes needs to have a new signature.

Ansgar

In this case, yes (two new binaries libphobos-5-dev-armhf-cross and
libphobos-5-dev-armel-cross).

but wouldn't it be an option to put such a package into NEW as well, if the
needed dependency is found in NEW?

Matthias