Am Dienstag, den 14.11.2017, 13:42 -0700 schrieb Jason Gunthorpe: > On Tue, Nov 14, 2017 at 09:34:06PM +0100, Benjamin Drung wrote: > > > I can often find debian packaging from upstream projects that > > either > > use their complete own packaging or a very outdated fork of the > > packaging from Debian. > > But it creates a technical problem, eg now that you are going to make > a -2, where will the changelog commit go? When all commits for -2 are accepted in the master branch, I would update debian/changelog to have the 15-2 entry between 15-1 and 16-1. An alternative would be to just have one changelog entry in the master branch and document the basis, e.g.: rdma-core (16-1) unstable; urgency=low * New upstream release. * Packaging is based on rdma-core 15-2 from Debian * Downgrade debhelper to >= 9 to support Debian 7 & 8 -- Jason Gunthorpe <jgg@xxxxxxxxxxxxxxxxxxxx> Tue, 14 Nov 2017 12:24:09 +0100 > Ideally the changelog commit should match the actual git tree that > was > used to produce the debian source tar ball. Otherwise things start to > get very confusing :) > > Jason -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 D - 10405 Berlin Email: benjamin.drung@xxxxxxxxxxxxxxxx URL: https://www.profitbricks.de Sitz der Gesellschaft: Berlin Registergericht: Amtsgericht Charlottenburg, HRB 125506 B Geschäftsführer: Achim Weiss, Matthias Steinberg -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
