On Wed, Jun 27, 2018 at 09:39:07AM +0100, Chris Lamb wrote: > Not sure what I did... Just forwarding here to keep the converation > altogether. > > > ----- Original message ----- > From: Debian FTP Masters <ftpmaster@ftp-master.debian.org> > To: lamby@debian.org, Matthias Klose <doko@debian.org>, Nicholas D Steeves <nsteeves@gmail.com> > Subject: lxml_4.2.1-1~bpo9+1_amd64.changes REJECTED > Date: Wed, 27 Jun 2018 08:35:43 +0000 > > > lxml_4.2.1.orig.tar.gz: Does not match file already existing in the pool. > > > binary:python-lxml is NEW. > binary:python-lxml-dbg is NEW. > binary:python-lxml-doc is NEW. > binary:python3-lxml is NEW. > binary:python3-lxml-dbg is NEW. > binary:python-lxml-doc is NEW. > binary:python-lxml-dbg is NEW. > binary:python3-lxml is NEW. > binary:python-lxml is NEW. > binary:python3-lxml-dbg is NEW. > source:lxml is NEW. It definitely wasn't your fault. My mentors upload was so long ago that I decided to just reupload with a fresh copy of the orig tarball that I've verified matches the sha256sum of the one that's already in the archive. https://mentors.debian.net/debian/pool/main/l/lxml/lxml_4.2.1-1~bpo9+1.dsc If I had to guess what happened, my gbp rebuilt the tarball. Sorry. Cheers, Nicholas
Attachment:
signature.asc
Description: PGP signature