Hi Lucas,
On Thu, Aug 13, 2020 at 11:24:42PM +0200, Lucas Nussbaum wrote:
>
> Well, why don't you look at the code?
No idea whether it is sensible to answer rhetorical questions.
Since you asked despite you probably know that I'm doing even more than
usual for Debian Med since COVID-19 here some other reasons than the
usual ENOTIME excuse:
- The development of that code is intransparent to me
- Someone - whoever it was - just droped
/srv/udd.debian.org/upload-history/munge_ddc.py.tentative
at 2020-08-01 which seems to be a Python3 port of munge_ddc.py
- I had simply hoped that your bug report might have triggered
an action of the maintainer of that code (whoever this might be)
- I was afraid to do some naive pocking in some code I need to
understand first (while other more competent developers are
just busy to fix things).
In other words: Its not really an inviting environment for potential
helpers.
To at least do something against the latter I injected everything I
categorized as "code or data that come from some source I do not have
any idea where to obtain from" into Git
https://salsa.debian.org/qa/udd/-/commit/a0408b9d03a9e26a775a9525760a02199c306f5d
I repeat that I consider it sensible to develop here in Git and work
with symlinks to /srv/udd.debian.org/upload-history/ - but even this was
not yet confirmed by those people who initially developed the code (nor
those who are working on munge_ddc.py.tentative.
IMHO the next logical step would be to replace the now unusable
munge_ddc.py by munge_ddc.py.tentative set the symlinks and simply
call the procedure to see what happens. Do you want me to do this
or is there anybody who has a better idea to proceed (which I would
be very happy about).
Kind regards
Andreas.
--
http://fam-tille.de
