Hi,
Quoting Holger Levsen (2016-12-19 10:35:53)
> On Mon, Dec 19, 2016 at 10:02:58AM +0100, Johannes Schauer wrote:
> > Other ways to solve this problem include:
> > - only accept .buildinfo files that include the .dsc filename and checksum
> > - accept .changes files that reference both the .bu
Hi,
Quoting Johannes Schauer (2016-12-20 13:49:27)
> Currently, a buildinfo file does not specify which artifacts were supposed to
> be built (source,any,all).
as guillem points out to me on #debian-dpkg, the Architecture field lists
exactly that. It will contain "source" if the source package wa
Hi,
Quoting Johannes Schauer (2016-12-19 10:02:58)
> I also came up with another question:
and as I'm implementing this, here yet another:
Currently, a buildinfo file does not specify which artifacts were supposed to
be built (source,any,all). What should happen if the buildinfo file was for an
On Mon, Dec 19, 2016 at 10:02:58AM +0100, Johannes Schauer wrote:
> Other ways to solve this problem include:
> - only accept .buildinfo files that include the .dsc filename and checksum
> - accept .changes files that reference both the .buildinfo and the .dsc
those two seem sensible to me.
--
Hi,
Quoting HW42 (2016-12-19 07:37:00)
> So you (at least josch and ntyi) seem to prefer to have the user facing part
> in sbuild/pbuilder and the common functionality in some kind of library. How
> should the "library" interface look like for sbuild?
pbuilder is written in bash, so a plain-text
Johannes Schauer:
> Hi,
>
> Quoting Niko Tyni (2016-12-17 13:40:32)
>> On Thu, Dec 15, 2016 at 02:21:49PM +0100, Johannes Schauer wrote:
>>> Quoting Niko Tyni (2016-12-15 14:04:19)
In general, I like the concept of sbuild/pbuilder accepting .buildinfo
files
as input. This makes the
Hi,
Quoting Niko Tyni (2016-12-17 13:40:32)
> On Thu, Dec 15, 2016 at 02:21:49PM +0100, Johannes Schauer wrote:
> > Quoting Niko Tyni (2016-12-15 14:04:19)
> > > In general, I like the concept of sbuild/pbuilder accepting .buildinfo
> > > files
> > > as input. This makes the user interface simple
On Thu, Dec 15, 2016 at 02:21:49PM +0100, Johannes Schauer wrote:
> Quoting Niko Tyni (2016-12-15 14:04:19)
> > In general, I like the concept of sbuild/pbuilder accepting .buildinfo files
> > as input. This makes the user interface simple. My expectation for this mode
> > of operation would be fo
Hi,
Quoting Niko Tyni (2016-12-15 14:04:19)
> > But then on IRC, HW42 suggested to approach this problem differently.
> > Instead of integrating the functionality of figuring out the right
> > repositories to reproduce the contents of a buildinfo file into sbuild,
> > write a tool that can drive a
On Tue, Aug 02, 2016 at 10:49:00PM +0200, Johannes Schauer wrote:
> But then on IRC, HW42 suggested to approach this problem differently. Instead
> of integrating the functionality of figuring out the right repositories to
> reproduce the contents of a buildinfo file into sbuild, write a tool that
10 matches
Mail list logo
