On 2022-02-16, Simon McVittie wrote:
> On Sun, 13 Feb 2022 at 14:13:10 -0800, Vagrant Cascadian wrote:
>> Obviously, this would interfere with any meaningful reproducible builds
>> testing for any package that did something like this. Ideally metadata
>> like this about a build should *not* be incl
On 2022-02-14, Paul Wise wrote:
> On Sun, 2022-02-13 at 14:13 -0800, Vagrant Cascadian wrote:
>
>> * Split build metadata into a separate file or archive
>>
>> Some of the debian-installer packages generate tarballs that are not
>> .deb files and are included in the .changes files when uploading t
On Sun, Feb 13, 2022 at 02:13:10PM -0800, Vagrant Cascadian wrote:
> Curious to hear your thoughts!
I'd just like to comment with three rather general comments:
a.) thanks for bringing this up here, Vagrant.
b.) solving this seems to be a requirement for getting the build-essential
package se
On Wed, 2022-02-16 at 16:51 +, Simon McVittie wrote:
> If the maintainers of dak (our eternally overworked ftp team) want to
> pick up build logs as first-class artifacts produced by both failed
> and successful builds, they're welcome to do so (and then handling my
> prototype of test artifac
On Wed, 16 Feb 2022 at 23:25:46 +0800, Paul Wise wrote:
> Simon McVittie wrote:
> > handling build logs is not dak's job (and I don't think handling
> > things like the binutils test results should be dak's job either).
>
> It has always felt weird to me that build logs are entirely separate to
>
Simon McVittie wrote:
> Relatedly, I would like to be able to capture some information about
> builds even if (perhaps especially if) the build fails.
That is a good point that I hadn't considered.
> so that failing builds can also produce artifacts, to help the
> maintainer and/or porters to fi
On Sun, 13 Feb 2022 at 14:13:10 -0800, Vagrant Cascadian wrote:
> Obviously, this would interfere with any meaningful reproducible builds
> testing for any package that did something like this. Ideally metadata
> like this about a build should *not* be included in the .deb files
> themselves.
Rela
On Sun, 2022-02-13 at 14:13 -0800, Vagrant Cascadian wrote:
> * Split build metadata into a separate file or archive
>
> Some of the debian-installer packages generate tarballs that are not
> .deb files and are included in the .changes files when uploading to
> the archive; making a similar gener
A while ago I noticed binutils had some embedded logs in one of it's
packages, which included timing information about the test suite runs
which will almost certainly have differences between the different
builds, even on the exact same machine:
https://bugs.debian.org/950585
My proposed patch
9 matches
Mail list logo
