Bug#859778: RFS: xtrs/4.9d-3

2017-04-24 Thread G. Branden Robinson
At 2017-04-22T16:04:25-0700, Sean Whitton wrote: > > Can you explain your reasoning here? > > Currently, almost all Debian packagers/maintainers use one changelog > entry and version number per upload. So if there are rounds of review > in an RFS, new changes are folded into the previous

Bug#859778: RFS: xtrs/4.9d-3

2017-04-22 Thread Sean Whitton
Hello Branden, On Sat, Apr 22, 2017 at 03:41:48PM -0400, G. Branden Robinson wrote: > > 1) How about merging the -1, -2 and -3~~unreleased changelog entries > > into a single entry, since we're doing a single upload? > > Won't that prompt the question of what happened to -1 and -2? > > Or do

Bug#859778: RFS: xtrs/4.9d-3

2017-04-22 Thread G. Branden Robinson
At 2017-04-22T15:41:48-0400, G. Branden Robinson wrote: > > Given this problem I haven't done a full review, but I'd like to make > > two preliminary suggestions: > > > > 1) How about merging the -1, -2 and -3~~unreleased changelog entries > > into a single entry, since we're doing a single

Bug#859778: RFS: xtrs/4.9d-3

2017-04-22 Thread G. Branden Robinson
At 2017-04-22T07:13:38-0700, Sean Whitton wrote: > control: tag -1 +moreinfo > > Hello Branden, > > I can't get 79e8ccf40499ace8cf36210a7ad9fb157209bbe4 to build. Log > attached. Urp. This is due to the unavailabilty of gropdf on the build host, it looks like. I'll investigate. > Given this

Bug#859778: RFS: xtrs/4.9d-3

2017-04-22 Thread Sean Whitton
control: tag -1 +moreinfo Hello Branden, I can't get 79e8ccf40499ace8cf36210a7ad9fb157209bbe4 to build. Log attached. Given this problem I haven't done a full review, but I'd like to make two preliminary suggestions: 1) How about merging the -1, -2 and -3~~unreleased changelog entries into a