On 2024-08-22 14:16, Andreas Tille wrote: > Hi, > > I intended to fix bugs #1066354 and #836007 of safecat as Bug of the > Day[1]. While #1066354 gcc-14 error seemed to be a low hanging fruit > it turns out I need help to solve some linker issue[2]: > [snip]
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. 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? 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! Best, Antonio (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.) [1] https://github.com/aperezdc/safecat
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
