Hi!

On Tue, 2016-03-22 at 22:04:00 +0100, Julien Cristau wrote:
> Control: tag -1 moreinfo
> 
> 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?

I've always included portability fixes in previous stable updates, because
they tend to not affect the code executed in Debian (so they tend to be
very low risk), and they tend to be FTBFS fixes but for systems other
than the ones we support in Debian, and because dpkg does not have other
distribution channels other than via Debian.

The arch table updates are required in case we want to add those
arches into the archive, as dak makes use of the dpkg tables in stable
AFAIK. It's also required to be able to bootstrap such ports using
only infrastrcuture from stable. I've always synced them up to now.

> > 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.)

Then I think I'll just take it out, as I'm not sure yet when I'll do an
unstable upload. And instead I'll temporarily amend my local .gitconfig
(which I often forget to do). (The fix is required to avoid leaking
local repo information and divering output such as the one coming from
log.decorate=true, core.quotepath=off, diff.renames=copies and similar
into the generated ChangeLog.)

> > 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.

Ok, attached the new full diff. I've compressed it with xz because it's
huge, and I don't think I ususually provide an unfiltered one.

Thanks,
Guillem

Attachment: dpkg-1.17.26-1.17.27.debdiff.xz
Description: application/xz

Reply via email to