Because I no longer administer a mailserver that benefits from SRS, and I thus
no longer use postsrsd, I request an adopter for the postsrsd package.

The package is fairly low-maintenance, with usually only one tidying-up upload
needed every release cycle. The packaging is mostly straightforward and in
fairly good shape. It's lintian-clean, hosted on Salsa, and upstream is
responsive. The version currently in unstable lags one release behind upstream,
but the only change of note in that version, a security fix, has already been
backported to the version in both stable and unstable.

The package description is:
 PostSRSd provides Sender Rewriting Scheme (SRS) support for Postfix via
 TCP-based lookup tables. SRS is needed if your mail server acts as a forwarder,
 and the mail originates from a server with Sender Policy Framework (SPF)
 enabled.

Hello,

I would like to adopt this package. I maintain a mailing list server
where I am already using postsrsd.

I think this was not forwarded to Oxan, so I'm resending it to
1017361-submitter@bugs.debian.org

Cheers
Timo

Hi,

You're right, thanks for the forward.

That's great! The packaging is currently hosted in the Debian group on
Salsa, so as a DD you should already have access to it. I'm not aware of
anything that needs to be done for the handover, so feel free to take
over that repository (or move it elsewhere, if you prefer), and to
upload a new version with you listed as Maintainer.

If you've any questions about the current packaging, don't hesitate to
reach out!

Cheers,
Oxan

Hello Abhijith,

I guess you are not interested anymore?

cu Andreas

Hello Andreas,

I am interested. I have pushed latest upstream source to
salsa.(https://salsa.debian.org/debian/postsrsd). Made an upload for
Raju (Cc'ed). But I failed to package latest upstream to Debian repo.
I tried and hit at obstacle and then left at there.

I am happy to pass it you and Raju. Let me know.

[...]

Hello,

I am not going to adopt it (Using exim). It is just that I browsed over
the open RC bug list and found both an RC bug (#1068053) and a ITA that
did not look like it was going anywhere and wondered what was up.

FWIW I played a little bit with 2.0.8 and got it to build with:
a) extending b-d by libconfuse-dev, check, pkgconf, systemd-dev
b) Patching cmake/FindCheck.cmake
-    find_path(Check_subunit_LIBRARY subunit HINTS ${PC_SUBUNIT_LIBRARY_DIRS})
+    find_library(Check_subunit_LIBRARY subunit HINTS ${PC_SUBUNIT_LIBRARY_DIRS})
[This is now upstream issue #176)
c) Invoking cmake with -DFETCHCONTENT_TRY_FIND_PACKAGE_MODE=ALWAYS
(Borrowed from OpenSuse ;-)

It is not enough to get a functioning package, but it is packaging and
not compilation from there on.

cu Andreas

Hi,

I’ve made merge request at salsa repo (
https://salsa.debian.org/debian/postsrsd/-/merge_requests/3), which should
make postsrsd 2.x version buildable.



I’ve updated version from upstream 2.0.9 that adds most of the commits
(since 2.0.8 version didn't include them).



I’m not a Debian dev and I’m definitely not sure if everything is ok, so I
would like to ask you, if you could review it and merge / comment on it, so
anybody who maintains the project now and has any knowledge about
releseases could take it forward.



Thanks

David

Hello David,

Thank you very much for the merge request.

I did take a look. And it seems you placed all commits on top of
master. Usually we don't track upstream commits. We take upstream
release tarball, extract and push everything to upstream branch in a
single commit and merge to master.

We also create a branch called prisitine-tar in the process, which can
be later used to generate exact same tarball.

So can you push all upstream 2.0.8..2.0.9 changes to upstream branch.
And debian/ related changes to master. Also push prisitine-tar files.

I am not sure whether it can be done in a single MR.

Regards
Abhijith

[Re-sending with @debian.org address to land on recipient inbox]