Please review the draft for week 94's blog post

Hi all, Please review the draft for week 94's blog post: https://reproducible.alioth.debian.org/blog/drafts/94/ Feel free to commit any changes directly to drafts/94.mdwn in Git: https://anonscm.debian.org/git/reproducible/blog.git/ I am very happy to reword and/or rework prior to

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

On Sun, Feb 12, 2017 at 12:46:42AM +0100, Mattia Rizzolo wrote: > On Sun, Feb 12, 2017 at 10:08:54AM +1300, Chris Lamb wrote: > > Hi, > > > > (Attachment was too large for Alioth apparently, so re-sending) > > Yes (I discarded the email from the moderation queue now). BTW, yes, remote to pull

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

On Sun, Feb 12, 2017 at 10:08:54AM +1300, Chris Lamb wrote: > Hi, > > (Attachment was too large for Alioth apparently, so re-sending) Yes (I discarded the email from the moderation queue now). > commit 02d4d20ae8eab1440b0d9fba8eda3df860d259d8 > Author: Chris Lamb >

[PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

Hi, (Attachment was too large for Alioth apparently, so re-sending) commit 02d4d20ae8eab1440b0d9fba8eda3df860d259d8 Author: Chris Lamb Date: Sun Feb 12 10:03:02 2017 +1300 reproducible Debian: Reverse Python 2.x dict order in the second build.

participation in GSoC 2017 / Outreachy 14

Hi folks! As I'm sure all of you read through debian-devel-announce (and Holger's forward here), it's again time to prepare for the summer round of our usual outreach sessions. https://lists.debian.org/debian-devel-announce/2017/02/msg3.html I've made what basically is a copy-paste of our

Bug#854723: diffoscope writes to arbitrary locations on disk based on the contents of an untrusted archive

On Fri, Feb 10, 2017 at 11:07:22AM +1300, Chris Lamb wrote: > tags 854723 + pending > thanks > > > diffoscope may write to arbitrary locations on disk depending on the > > contents > > of an untrusted archive Please use CVE-2017-0359 Cheers, Moritz