Re: BinNMU changelog handling for Multi-Arch: same packages
- To: Russ Allbery <rra@debian.org>
- Cc: Jonathan Nieder <jrnieder@gmail.com>, debian-dpkg@lists.debian.org, debian-release@lists.debian.org, joeyh@debian.org, sbuild@packages.debian.org
- Subject: Re: BinNMU changelog handling for Multi-Arch: same packages
- From: Raphael Hertzog <hertzog@debian.org>
- Date: Wed, 11 Jul 2012 20:45:15 +0200
- Message-id: <20120711184515.GG14405@rivendell.home.ouaza.com>
- Mail-followup-to: Russ Allbery <rra@debian.org>, Jonathan Nieder <jrnieder@gmail.com>, debian-dpkg@lists.debian.org, debian-release@lists.debian.org, joeyh@debian.org, sbuild@packages.debian.org
- In-reply-to: <87bojm8ejo.fsf@windlord.stanford.edu>
- References: <20120711072305.GG7822@rivendell.home.ouaza.com> <20120711073537.GA2006@burratino> <20120711114439.GD11359@rivendell.home.ouaza.com> <87bojm8ejo.fsf@windlord.stanford.edu>
On Wed, 11 Jul 2012, Russ Allbery wrote:
> I don't think it's mandatory that we save the information, but it
> certainly would be nice. I'd like apt-listchanges to show me the binary
> NMU changelog. I've used that information before on the local system, and
> that's a lot more convenient than going to the web and trying to do
> archeology on what happened.
>
> Saving the binary NMU changelog in a separate file feels like the right
> solution to me.
The right *temporary* solution then. Remember that this was meant as an
intermediary solution until the full changelog (with the bin-nmu entry)
is just integrated in the package medata (control.tar).
But it's true that it might require more than a cycle until we're there so
it's probably best to not drop this information, even if it's only a
temporary measure.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
Reply to: