On Tue, Mar 20, 2018 at 06:53:15PM -0400, Nicholas D Steeves wrote: > On Tue, Mar 20, 2018 at 10:44:34PM +0100, Axel Beckert wrote: > > > In my case it was an Debian Unstable which has been upgraded > > regularily since its installation on 2014-04-08. yasnippet-snippets > > has been first installed in version 0~git20150512-1 on Thu May 28 > > 19:16:25 2015 +0200. > > Thank you very much for this information! Luckily the only three > versions are: 0~git20150512-1, 0~git20161123-1, and > 0~git20180307.2b4c4d7e-1. > > Because http://archive.debian.net is not available I'll try building > these three versions, purging my current 0~git20180307.2b4c4d7e-1, and > then sequentially installing/upgrading. My hypothesis is now that > this bug is cause by an artifact introduced by upgrading from the 2015 > to 2016 version.
Well that's strange... No errors... I also tried installing each version on top of the last in a clean sid chroot. Maybe the bug is only triggered when 0~git20150512-1 was built using particular (old) versions of debhelper and/or when the upgrade to 0~git20161123-1 was performed using particular versions of dpkg? If anyone can provide a copy of (or link to) the old yasnippet-snippets_0~git20150512-1_all.deb I would be very appreciative! Cheers, Nicholas
signature.asc
Description: PGP signature
