Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-06-18 Thread Sean Whitton
Hello, On Thu, Apr 19 2018, Sean Whitton wrote: > In the next month or so we (Ian Jackson and I) will be releasing a > workflow called dgit-maint-debrebase(7) which > > - is patches-applied; but > - automatically generates a perfect 3.0 (quilt) representation of the > Debian changes. > > I.e. i

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-21 Thread KAction
> > I am okay to wait for your next invention. Last one I remember -- > > separate patches instead of single squashed patch in > > dgit-maint-merge(7) was awesome. > > Sorry but I don't understand this last sentence. Perhaps you could > rephrase. I mean, that I see improvements in dgit, and, wh

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-20 Thread Sean Whitton
Hello, On Fri, Apr 20 2018, kact...@gnu.org wrote: > [2018-04-19 10:14] Sean Whitton >> Hello both, >> >> If Dmitry wants to continue to use dgit-maint-merge(7), using 3.0 >> (quilt) will not help. It will not introduce any additional >> metadata. The only change will be the addition of a patc

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-20 Thread Sean Whitton
Hello, On Fri, Apr 20 2018, kact...@gnu.org wrote: > [2018-04-19 10:14] Sean Whitton >> Hello both, >> >> If Dmitry wants to continue to use dgit-maint-merge(7), using 3.0 >> (quilt) will not help. It will not introduce any additional >> metadata. The only change will be the addition of a patc

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-20 Thread KAction
[2018-04-19 10:14] Sean Whitton > Hello both, > > If Dmitry wants to continue to use dgit-maint-merge(7), using 3.0 > (quilt) will not help. It will not introduce any additional metadata. > The only change will be the addition of a patch header pointing to > dgit-repos. What do you mean by 'ad

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-19 Thread Jeremy Bicha
On Thu, Apr 19, 2018 at 1:14 PM, Sean Whitton wrote: > Since we have submitted two sessions to DebConf18 about this new > workflow, you can be confident the release will come before August :) So > what I would like to suggest is that both of you hang tight for now and > then evaluate this new wor

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-19 Thread Sean Whitton
Hello both, If Dmitry wants to continue to use dgit-maint-merge(7), using 3.0 (quilt) will not help. It will not introduce any additional metadata. The only change will be the addition of a patch header pointing to dgit-repos. Switching to dgit-maint-gbp(7) means using a patches-unapplied workfl

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-19 Thread Jeremy Bicha
Sean, Are you able to help out here? I admittedly haven't really used dgit so I wouldn't really know if I were doing things right. Thanks, Jeremy Bicha On Thu, Apr 19, 2018 at 12:01 AM, wrote: > > control: tags -1 help > > [2018-04-18 14:11] Jeremy Bicha >> Source: inotify-tools >> Version:

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-18 Thread KAction
control: tags -1 help [2018-04-18 14:11] Jeremy Bicha > Source: inotify-tools > Version: 3.14-5 > > Please consider using the dgit-maint-gbp workflow instead of the > dgit-maint-merge workflow. > > The recent switch from 3.0 (quilt) eliminates useful context and > metadata from the Debian pack

Bug#896014: inotify-tools: Consider using dgit-maint-gbp workflow

2018-04-18 Thread Jeremy Bicha
Source: inotify-tools Version: 3.14-5 Please consider using the dgit-maint-gbp workflow instead of the dgit-maint-merge workflow. The recent switch from 3.0 (quilt) eliminates useful context and metadata from the Debian package itself. That metadata is now only available in the git repo. Direct