Control: tag -1 moreinfo Hi Guillem,
On Mon, Mar 21, 2016 at 16:49:35 +0100, Guillem Jover wrote: > Here's a proposed dpkg 1.17.27, with cherry picked fixes from master > (already in unstable). These include fixes for regressions, memory > leaks, portability, interaction with tools such as GNU tar or the > system shell, install-info transition, and a sync of the architectures > supported (in case some of these end up accepted in the archive). > Why do the portability and architecture tables changes need to be in stable? > The change for Config-Version should be safe, as at worst it will have > no effect, otherwise packages relying on the correct behavior will > start to work now, it will also make upgrades easier, for example for > systemd, which I'm aware suffered from this problem. > > The «git log» fix is not yet in master though, but it should also be > safe, otherwise the build would simply fail. And I've just realized it's > not documented in debian/changelog, it will be in the ChangeLog, but I > could add it to debian/changelog too. > Yes, please do ship it in sid first, and please document it in debian/changelog. (Or you could have explained it here, but you didn't, so debian/changelog will do.) > The changes have passed all unit tests which are part of the build, > and all functional test in the dpkg-tests git repo. Attached a diff > with translation updates filtered. > Thanks. Please also provide a full diff. Cheers, Julien
