Hi! On Mon, 2017-03-13 at 00:02:26 -0400, James McCoy wrote: > On Mon, Mar 06, 2017 at 11:45:20PM -0500, James McCoy wrote: > > This was merged and uploaded in 2.17.2. However, now I see that > > buildinfo files may be arch-qualified even with a _source.changes (e.g., > > by using "sbuild -A --source-only-changes"). That's not currently > > handled properly since "debsign foo_ver_source.changes" expects > > "foo_ver_source.buildinfo" to exist. > > > > Should debsign be deriving the path for the buildinfo from the contents > > of the changes file?
Sorry for not chiming in sooner! > I've changed all of the "child file" handling to use this approach in > 4a4238dbf1e789e998cf047ea0f006e982fba56b. That seems cleaner than > debsign replicating logic to determine the names of related files. Yeah, thanks, that sounds best. Not even scripts in dpkg-dev are assuming any specific name for the buildinfo file, they are always getting it from the .changes file. Thanks, Guillem _______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds