Re: i386.changes vs source.changes
Ben Finney <firstname.lastname@example.org> writes:
> Russ Allbery <email@example.com> writes:
>> Cyril Brulebois <firstname.lastname@example.org> writes:
>>> You call it superfluous. It's particularly helpful for source-only
>> Well, yes, it's superfluous for Debian, which doesn't support
>> source-only uploads.
> But not for hackers preparing packages for Debian, who want to present
> those for others to inspect or collaborate on. A prime example being
> the mentors.debian.net workflow.
So, y'all realize that pdebuild --buildresult .. by default breaks the
*_source.changes file that it generates because it regenerates a source
package as part of the regular build, right? How are you actually using
that *_source.changes file? Always having pdebuild put its build
results in a different location than where it generates the source
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>