Hi Antonio,
Am Thu, Aug 22, 2024 at 08:48:55PM -0600 schrieb Antonio Russo:
> I noticed the change of upstream to [1], but there's no import of any of
> the work done in there. It looks like @aperezdc has already gone about
> porting the package to meson, presumably solving this problem. Looking
> through the rest of the minimal work done on the package since the 1.13
> import, there are a handful that make use of modern standard C libraries,
> a few that add or remove documentation, and two commits that might be
> controversial: 185e8bf and 6c14784.
Thanks a lot for that hint.
> The first removes the maildir.sh script and a no-op warn-auto.sh file
> which seems to have only been used as part of its bespoke build system.
> The second changes the behavior if DTLINE and RPLINE are defined, which
> apparently has something to with qmail---I didn't bother to investigate.
> Maybe these commits can be safely reverted if we want that "old" behavior?
Seems it took even over one of our Debian patches which I was able to
remove.
> My point is that either the new upstream should be used, or we should
> admit that Debian is now acting as upstream of the package. Maybe it's
> worth it to just cherry pick the build system changes? It really seems
> unlikely it's worth someone's time it to maintain an abandoned, single-purpose
> build system designed in the late 20th century with ~1400 lines of code
> for a ~1800 LOC project!
We will *definitely* not become upstream. I pointed the watch file to
the latest Git commit and filed an ITS bug.
> (PS: Thank you so much for caring about these old packages. I'm sure
> someone's workflow depends on these, and they may not realize how
> precarious that is.)
You are welcome and thanks a lot for your hint. I added the comment to
the Bug of the Day matrix channel[2] that contacting debian-mentors@l.d.o
helps over night. ;-)
Kind regards
Andreas.
> [1] https://github.com/aperezdc/safecat
[2] https://matrix.to/#/#debian-tiny-tasks:matrix.org
--
https://fam-tille.de
