On Mon, 2020-06-01 at 20:53 +0200, Mattia Rizzolo wrote:
> But so, do you think the first step lies in pbuilder/sbuild to decide an
> interface for the package maintainers to use, or for the buildd managers
> (wanna-build/buildd and launchpad) to decide on an interface that
> sbuild needs to
On Mon, Jun 01, 2020 at 09:40:19PM +0800, Paul Wise wrote:
> Re-reading the above thread, I now think that debhelper/dpkg-dev is the
> wrong layer to be implementing this and that we want it in the hooks or
> config for the build system in use; launchpad, sbuild, pbuilder etc.
>
[…]
>
> So, I
On Mon, 2020-06-01 at 11:12 +0200, Mattia Rizzolo wrote:
> I know this has been linked in multiple places, but I'll link it
> again:
> https://bugs.launchpad.net/launchpad/+bug/1845159
> there has also been a relevant thread in debian-devel a few months
> back, spawned off the debian/.build
On Sun, May 31, 2020 at 02:49:46PM -0700, Vagrant Cascadian wrote:
> On 2020-05-17, Paul Wise wrote:
> > On Sat, 2020-05-16 at 22:58 +, Chris Lamb wrote:
> >> My gut feeling is that this is the avenue we want to explore. Having a
> >> separate mechanism to capture this build-specific metadata
On 2020-05-17, Paul Wise wrote:
> On Sat, 2020-05-16 at 22:58 +, Chris Lamb wrote:
>> My gut feeling is that this is the avenue we want to explore. Having a
>> separate mechanism to capture this build-specific metadata would be an
>> elegant solution and, as you imply, having the logs would
