Hi Emilio,
> Will you send a follow-up DLA announcement with the correct number?
Definitely. That should be hitting the list at around the same time I send this
mail.
> With respect to the process, I wonder how this happened and if
> there's something that can be improved in our scripts to avoid a
> similar issue in the future.
Indeed. I'd welcome ways of adjusting the process so that this doesn't
happen again.
Whilst I did use `gen-DLA --save`, I suspect that the `git push`
failed because I needed to rebase my local Git checkout and then the
subsequent `git push` failed for some reason.
This sounds like it can easily happen given the activity to the
security-tracker repo, so deleting the DLA-XXXX file may not be the
perfect solution. In this scenario, I would have to rebase manually on
the command-line and then entirely return the `gen-DLA --save`
command, re-entering all the information again which might get a bit
annoying.
Maybe this would be good logic to introduce if we scripted the rebase
at the very top of gen-DLA, but that is not entirely unproblematic
either. Thoughts welcome.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
