Hi Colin,
> I noticed you apparently tried to upload 3:4.2.21-1 for this yesterday
> (judging from git), but I don't see it on
> https://tracker.debian.org/pkg/python-django nor in the ftp-master logs.
> Could you check whether the upload got lost somewhere?
Actually there has no attempt at an upload — yet. (And so therefore
nothing has got lost.)
I haven't uploaded the package yet for two reasons:
(1) The Salsa CI tests are currently failing. (Just saw the failure
email this morning, haven't opened it yet.)
(2) There was a direct request from the team behind Debusine [0] that
I try their service for a real update to a real package. I said I
was happy to, especially as this CVE is not critical. (Django is a
great package for this too, because it has so many reverse-deps.)
[0] https://debusine.debian.net/
Some questions for you, however:
Are you inferring an attempt was made from the Git tag or the
existence of the changelog? Or some other indicator? If so, that is
misleading, and I'd be interested to know how I can prevent that in
the future. :)
May I assume you are asking as you'd like to update backports? If so,
I'd be happy to let you know explicitly when I've uploaded something
into unstable.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
