Allow passing version for dpkg-genchanges to dpkg-buildpackage for -meta

[Stefan Bader]

On 17.04.2012 03:36, Tim Gardner wrote:
> On 04/16/2012 12:30 PM, Herton Ronaldo Krzesinski wrote:
>> When doing stable updates, we sometimes have cases where we need to
>> include more than one changelog entry on meta packages, for example, we
>> do one release to -proposed, this doesn't end up in updates, another
>> release/abi bump happens, and we must include 2 changelog entries for
>> the packages that will go to updates.
>>
>> Following this is the proposed changes for hardy and the rest of meta
>> packages (lucid and everything supported until precise/q). It changes
>> the Makefile so one can easily specify the previous version so we can
>> tune the changelog generation as needed. It's a simple change, one could
>> always specify the -v manually, but since we already have a Makefile
>> that does everything... why not.
>>
> 
> If you're going that far, then why not make it automagic. Use rmadison to
> extract the current version in updates, e.g.,
> 
> rtg at m1710:~$ rmadison -s lucid-updates linux-meta
> linux-meta | 2.6.32.40.47 | lucid-updates | source
> 
> rtg

As a helper it would take one thing off the list to think about. The updates
version should be out long enough to be correct and the major pain-point of the
past were inter-mixed security updates which are gone...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20120417/960aae05/attachment.sig>