Steffen Nurpmeso wrote on 28/06/2019: > Paride Legovini wrote in <b477c054-fa6a-dd93-2fe3-892d46e09a74@ninthfloo\ > r.org>: > |Steffen Nurpmeso wrote on 27/06/2019: > |> Paride Legovini wrote in <a8755ae8-a3b9-fba5-c24a-fbebec0f6c35@ninthfloo\ > |> r.org>: > |>|Steffen Nurpmeso wrote on 20/06/2019: > |>|> the patch was reversed; here is the right one. > |>| > |>|Just to be sure, is your last "ivan.diff" patch all that's needed to fix > |>|this bug? I would like to have it fixed in buster, but given that we're > |>|so deep in the freeze I'll have to ship only a minimal fix for this > |>|specific bug; an import of a new minor version changing other stuff > |>|won't be accepted. This will mean patching 14.9.11. > |> > |> Oh-oh, 14.9.11 is a year old! :) I do not understand that > |> security policy of Debian, for such a small program with a single > |> developer. So many bugs fixed! I would even update to [master] > |> or [stable/stable] and use the grappa mode! Sigh. :) > | > |Yeah I'm sorry for the skipped release, I promise I will backport the > |latest one once buster is released, but for the moment v14.9.11 is the > |version we have to work with. > | > |The policy for acceptable changes during the full freeze period is > |pretty clear: > | > |https://release.debian.org/buster/freeze_policy.html > | > |and I don't think an update to e.g. 14.9.14 will fit. > > That definetely not, i had to rewrite the entire child process and > job control signal handling to something that i almost like. And > the rest of the way we will make, too! > > I was thinking more of the [stable/stable] branch, which is > v14.9.13 plus fixes, and which can be turned into a release with > the grappa mode of mk/make-release.sh (as documented in README).
Hi Steffen, This would totally make sense in my opinion, the problem is we don't have v14.9.13 in Debian, but v14.9.11, and we need two "UPDATE" version bumps (in the MAJOR.MINOR.UPDATE semantic) to get to 14.9.13, on which we can apply the bug fixes in the stable/stable branch. And UPDATE releases are not bugfix-only releases, so not really suitable for inclusion while Debian is in deep freeze. I can of course backport the latest stable version of s-nail once Buster is released, and I will, but that's not the same of course. Please let me know if I misunderstood something, and thanks a lot for your feedback. Paride
