On Sat, 2015-05-30 at 20:57:33 +0200, Stefano Zacchiroli wrote: > On Sun, Jul 06, 2014 at 11:04:09AM +0200, Guillem Jover wrote: > > This also affects stable, it would be nice if a stable update could be > > prepared, I'm ready to help if needed, given that the “regression” was > > caused by the dpkg update. > > FWIW I've noticed in Debsources logs both this issue, and what seems to > be another occurrence of it on the moodle package. I've now reported it > here https://bugs.debian.org/787271
> Is there a dpkg update planned to fix this in stable (or oldstable)? > If so, I'll be glad to test it on the sources.d.n machine. This wont be "fixed" in dpkg, that change was necessary to fix a security issue in dpkg. In many cases it made visible existing broken patches, like the one in moodle, which before the dpkg fix was only getting partially applied, which renders that moodle security fix partially moot. In others the patch was malformed and patch would apply it correctly, but making dpkg try to distinguish between malformed or malfeasant patches would go from either impossible, too difficult or an arms race. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
