> I tried to reproduce the situation where 'source+arch' appears, but
> failed.
>
> And, as far as I can read the code, dpkg-cross version of
> dpkg-buildpackage should not do this.
>
> First, before doing any .changes processing, it checks if there are
> exactly two files that match pattern ${package}_${version}_*.changes; if
> there is only one (which should be the case when not cross-compiling),
> it does not touch .changes.
>
> Second, if there are two matching files, the 'arch part' of the name of
> merged changes file is built from 'arch parts' of existing .changes
> files. This procedure can't add 'source' there unless it was already
> there on original files.I probably understood how 'sources' come in. If one first runs 'dpkg-buildpackage -S', a .changes file will be created with 'sources' in the arch part of the name. Later, if 'dpkg-buildpackage' is run to create binary packages, it creates a .changes file with real arch part of the name; so there are two .changes files, and they are merged. Probably a good workaround will be not to include 'source' in the merged file name in such case. Committed this workaround to dpkg-cross CVS. This will be in dpkg-cross 1.26 Don't know what to do with this bug now. Probably submitter or debuild maintainer should decide if this is enough to close it. Nikita
pgpEAP5dqMk1p.pgp
Description: PGP signature
