Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2

To: Santiago Ruano Rincón <santiagorr@riseup.net>, 819243@bugs.debian.org
Cc: 819244@bugs.debian.org
Subject: Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
Date: Mon, 28 Mar 2016 10:57:56 +0100
Message-id: <[🔎] 1459159076.2441.147.camel@adam-barratt.org.uk>
Reply-to: "Adam D. Barratt" <adam@adam-barratt.org.uk>, 819243@bugs.debian.org
In-reply-to: <[🔎] 20160326225804.GC26245@riseup.net>
References: <[🔎] 145891376032.22153.4847989447226956392.reportbug@riseup.net> <[🔎] 1458914282.2441.97.camel@adam-barratt.org.uk> <[🔎] 20160326225804.GC26245@riseup.net>

On Sat, 2016-03-26 at 23:58 +0100, Santiago Ruano Rincón wrote:
> Thanks. Packages uploaded.

It looks like you uploaded only the source and arch:all packages for
jessie, but named the changes file _amd64.changes. Please don't do that,
as it blocks the buildd upload from that architecture (due to dak
keeping all of the .changes files in dists/proposed-updates).

I've asked ftp-master to rename and re-inject the buildd upload.

Regards,

Adam

Reply to:

References:
- Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
  - From: Santiago Ruano Rincón <santiagorr@riseup.net>
- Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
  - From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
  - From: Santiago Ruano Rincón <santiagorr@riseup.net>

Prev by Date: Bug#819409: jessie-pu: package: torbrowser-launcher/0.1.9-1+deb8u3
Next by Date: Processed: Re: Bug#819409: jessie-pu: package: torbrowser-launcher/0.1.9-1+deb8u3
Previous by thread: Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
Next by thread: Processed: Re: Bug#819243: jessie-pu, wheezy-pu: package librsvg/2.40.5-1 and librsvg/2.36.1-2
Index(es):
- Date
- Thread