On Tue, Feb 14, 2017 at 06:21:11PM +, Holger Levsen wrote:
> I really want to see a bug number here.
I would have loved to send this mail to such a bug…
> > > also, you uploaded python2.7_2.7.13-3~reproducible1 for amd64, do you
> > > plan to
> > > do upload the other architectures as
On Sun, Feb 19, 2017 at 04:56:25PM -0500, Christos Zoulas wrote:
> Thanks,
Triggered!
https://jenkins.debian.net/view/reproducible/view/Singles/job/reproducible_netbsd/143/console
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
Thanks,
christos
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
On Sun, 2017-02-19 at 11:39:28 -0800, Vagrant Cascadian wrote:
> On 2017-02-19, Guillem Jover wrote:
> >> * .buildinfo files are not generated when creating source-only uploads
> >
> > Fixed. Now always generated.
>
> On a related note, is it currently possible to create a .buildinfo with
> both
On 2017-02-19, Guillem Jover wrote:
>> * .buildinfo files are not generated when creating source-only uploads
>
> Fixed. Now always generated.
On a related note, is it currently possible to create a .buildinfo with
both the source and binary, but a corresponding .changes with only the
source?
Hi!
On Sat, 2016-11-12 at 19:04:53 +0100, Guillem Jover wrote:
> As I've mentioned elsewhere, I've noticed several things with the
> current .buildinfo format, even after the cleanup pre-merge, that
> I'd like to fix or change so that we can hopefully reach Format 1.0.
Ok, let's see what's the
