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's metadata 4.4 will not help you? (I'll push 4.4 to stretch-backports soon in order to comply with backports policy, anyway.) For 5.x, I already have a working backport of 5.0 in my personal apt repo, so it should be easy to bump that to whichever 5.x release migrates to testing first and push that to stretch-backports. If you want the debs for testing, I can send you the URL for that repo. On Fri, Jun 22 2018, Ian Jackson wrote: > However, we have just released a major new feature and there are > inevitble bugs in it. My current wip branch[1] has fixes for that but > also fixes for other bugs, some of which may themselves cause further > bugs. Just ftr, we have to update stretch-backports once something new migrates to testing, per backports policy. The only way to delay updating the backport is to keep making releases to unstable ;) -- Sean Whitton
signature.asc
Description: PGP signature
