[Pkg-netatalk-devel] Netatalk 3.2.2 and 3.2.3

[Daniel Markstedt]

Hi Jonas,

I have now drafted a 3.2.3-1 release in the debian/latest branch:
https://salsa.debian.org/netatalk-team/netatalk/-/tree/debian/latest

Would you mind looking over the state of the code and judge if it is in good enough shape to be uploaded?
I inspected the before-after list of files with `dpkg -c' and couldn't spot any unexpected changes caused by the move to Meson.

One thing I wanted to ask your advice about:
The changelog now defines intermediate releases 3.2.0~ds-1, 3.2.1~ds-1, and 3.2.2-1, which weren't actually uploaded.
Does it make sense to keep these in the changelog, or shall I refactor the totality of the changes between 3.1.18~ds-1 and 3.2.3-1 in one big changelog?

Cheers,
Daniel

On Wednesday, July 10th, 2024 at 6:53 PM, Daniel Markstedt <daniel at mindani.net> wrote:

> Hi Jonas,
>
> A few days ago I integrated the latest Netatalk 3.2.2 tag with the Salsa repo.
> You should be pleased to hear that all traces of the SSLeay license have been eliminated from the codebase.
>
> Right now I'm working towards a 3.2.3 release of Netatalk.
> While attempting to build Netatalk with debuild using the Meson build system,
> lintian pointed out that we're setting rpath on a bunch of binaries, where we shouldn't.
> I have a fix in the pipeline now, plus a few others. Just needs a little more polish.
>
> Once I've released and integrated 3.2.3, I would want to get it into testing for Trixie!
> This way we can restore functionality of the DHX UAM in the Debian package, which I'm excited about.
>
> Best regards,
> Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-netatalk-devel/attachments/20240714/646434f3/attachment.htm>