Re: i386.changes vs source.changes
Malte Forkel <malte.forkel@berlin.de> writes:
> Russ Allbery schrieb:
>> Malte Forkel <malte.forkel@berlin.de> writes:
>>> After some more checking and thinking, I guess I know what's causing
>>> my problems: Its me, probably! I assume the source.changes files are
>>> created while I setup everything for building a package, e.g. by
>>> dh_make calling dpkg-buildpackage -S or whatever. I then use either
>>> debuild and pdebuild to build the binary packages. But while debuild
>>> replaces the source.changes file by an i386.changes file, pdebuild
>>> places the i386.changes file in /var/cache/pbuilder/result and does
>>> not replace the source.changes file.
>> The _source.changes file created by pdebuild is useless. I always
>> delete it in my shell alias that runs pdebuild. I suppose I should
>> have gotten around to filing a wishlist bug to have pdebuild delete
>> it.
> Oh, so its only pdebuild that creates a superfluous _source.changes file
> while all the other little helpers don't and consequently don't have to
> replace later on?
Calling dpkg-buildpackage -S produces a superfluous _sources.changes
file, so anything that uses that method to produce a source package for
build would either need to remove it or would leave it lying around.
pdebuild uses dpkg-buildpackage -S to generate a source package which it
then copies into the chroot to do the full build.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: