Bug#966649: Request for feedback on upload_history re-implementation
Hi,
On 20/08/20 at 22:55 -0700, Asheesh Laroia wrote:
> Hi Lucas!
>
> I'm rereading this, and I have a follow-up question.
>
> It looks to me, based on reading the bug carefully, that /srv/
> udd.debian.org/email-archives/debian-devel-changes/debian-devel-changes.current
> on ullmann successfully receives any new emails to debian-devel-changes. Is
> that accurate?
Yes, it does. The problem with the current implementation is that this
file gets large over time, so it needs to be reset from time to time.
This needs to be handed gracefully. One way to do that would be to
re-import from archives when that occurs.
The good thing about the current implementation is that importing from
the mbox archives, or importing from debian-devel-changes.current, is
almost the same process. One caveat: the mbox archives are now using xz
compression, which is not supported by the current implementation.
IMHO, fixing the current implementation to work with xz archives, and in
the process, port it to Python3, is a good way to solve this issue.
However, I'm not the one writing the code, so any working alternative
works for me, really (as long as it also works from the DSA POV).
Lucas
Reply to: