Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python Subject: Re: Build test failure for python-easydev Date: Wed, 23 Jan 2019 17:20:01 +0100 Message-ID: References: X-Original-To: Nick Morrott X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jan 23 16:10:18 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/16726 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190123161004.u7ohc5uqxxiapzoq@an3as.eu Approved: robomod@news.nic.it Lines: 44 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Wed, 23 Jan 2019 17:10:04 +0100 X-Original-Message-ID: <20190123161004.u7ohc5uqxxiapzoq@an3as.eu> X-Original-References: <20190115185501.atbbyriryylzvlua@an3as.eu> <20190116093407.2gzt5qznpnmhp5th@sar0.p1otr.com> <20190122205005.gthvxpn2dy3mb43j@an3as.eu> <20190123065457.3foashzw24kgv2lo@an3as.eu> Xref: csiph.com linux.debian.maint.python:11272 On Wed, Jan 23, 2019 at 09:58:45AM +0000, Nick Morrott wrote: > > Cool. Thanks a lot. Your outright contribution was very helpful and > > really welcome. The only change I made is to revert your commit > > 38022ac5 since there is no point in changing the upstream source that > > way. I agree upstream should not ship that file but if its in the > > upstream tarball I see no need to remove it here. > > Apologies about that. No problem. :-) > My build failed immediately due to the presence > of that file when I started testing, and removing it got the build to > proceed so I could look at the test failures. > > That file is not present in their upstream github repository at the > release date of 0.9.37. pypi points to the repo as the definitive > source location so it's my fault for not investigating the pypi > tarball further. Strange. I have no idea how this file might have sneaked in. It might be that PyPI changed the content of the file without renaming it? I used what I once obtained and stored in pristine-tar. May be you did not used `gbp buildpackage` - thus the difference. > If it persists it can obviously always be removed > automatically via d/copyright if desired. It never harmed my build. I tend to not touch the original tarball via d/copyright to keep the md5sum equally to the download - which does not seem to be the case any more if you are right (I did not mind to check admittedly). I guess it will "heal" for the next version and I have more important things than this on my desk now. > > Definitely. Package is uploaded - one worry less. :-) > > Excellent! Thanks again Andreas. -- http://fam-tille.de