Bug#901900: dgit in stretch-backports

2018-06-27 Thread Ian Jackson
Sean Whitton writes ("Re: dgit in stretch-backports"): > I prepared the backport earlier today but in a stretch chroot the test > suite has two failures: > > gdr-newupstream FAIL non-zero exit status 16 > gdr-viagit FAIL non-zero exit status 16 > > Ian, could you take a loo

Bug#901900: dgit in stretch-backports

2018-06-27 Thread Sean Whitton
Hello, On Tue, Jun 26 2018, Jonathan Nieder wrote: > Thanks again for this pointer. dgit 5.2 has now hit testing. If > there is anything I can do to help with getting it into > stretch-backports, please don't hesitate to let me know. I prepared the backport earlier today but in a stretch chroo

Bug#901900: dgit in stretch-backports

2018-06-26 Thread Jonathan Nieder
Hi Sean, Sean Whitton wrote: > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Is there somewhere I can read more about that policy? Not that I'm >> complaining :) > > https://backports.debian.org/Contribute/ > > "... you have to ... update your backport when a new version enters > testing ..."

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Jonathan Nieder
Sean Whitton wrote: > (B) We don't do anything special, wait for something in the 5.x series > to hit testing in the normal way, and then update the dgit and git > backports. [...] > In any case, since everyone is happy with (B) for at least a week, we > can do (B) for at least a week. So

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Sean Whitton
Hello Jonathan, Sorry, I wrote my other reply before reading the e-mail to which I'm now replying. On Fri, Jun 22 2018, Jonathan Nieder wrote: > My usual practice has been to backport git versions as soon as they > hit testing. I'd be happy to settle for waiting a week after that. > Two weeks f

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Jonathan Nieder
Hi Sean, Sean Whitton wrote: > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Do you plan to update dgit in backports once it hits testing? > > Yes. Excellent, thank you. [...] >> Is there anything I can do to help? For example, should I prepare an >> upload for 4.4 while we wait for 5.1 to mi

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Sean Whitton
Hello Jonathan, On Fri, Jun 22 2018, Jonathan Nieder wrote: > Do you plan to update dgit in backports once it hits testing? Yes. > Is there anything I can do to help? For example, should I prepare an > upload for 4.4 while we wait for 5.1 to migrate to testing? So far as I can tell from this

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Jonathan Nieder
Ian Jackson wrote: > Jonathan Nieder writes ("Bug#901900: dgit in stretch-backports"): >> Once git 2.18.0 is in testing, I want to update the git package in >> stable-backports. This would require updating dgit as well to a >> version that supports the working-tr

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Ian Jackson
Jonathan Nieder writes ("Bug#901900: dgit in stretch-backports"): > Once git 2.18.0 is in testing, I want to update the git package in > stable-backports. This would require updating dgit as well to a > version supports the working-tree-encoding attribute > (https://

Bug#901900: dgit in stretch-backports

2018-06-22 Thread Jonathan Nieder
Hi Sean et al, Once git 2.18.0 is in testing, I want to update the git package in stable-backports. This would require updating dgit as well to a version supports the working-tree-encoding attribute (https://bugs.debian.org/901900). Do you plan to update dgit in backports once it hits testing?