rrsync manpage missing from v3.4.0 release tarball

[dne]

It seems the manpage for rrsync (rrsync.1) was not generated for/included in the 3.4.0 release tarball.

[ncopa]

This is making it complicated to backport the CVE fixes to stable branches of Alpine Linux. Would it be possible to make a 3.4.1 release with the man-pages pre generated in the tarball for backwards compatibility?

[sthen]

This is making it complicated to backport the CVE fixes to stable branches of Alpine Linux. Would it be possible to make a 3.4.1 release with the man-pages pre generated in the tarball for backwards compatibility?

It might not be worth rolling a 3.4.1 release until #697 / #702 and #704 are fixed, and maybe also #701 ..

If you can set commonmark as a build dependency then you can "make man", I didn't really want that for OpenBSD though so I added a generated copy to the ports tree for now.

Surprised that whoever got advance notice of the CVEs didn't notice any of these...

[ncopa]

It might not be worth rolling a 3.4.1 release until #697 / #702 and #704 are fixed, and maybe also #701 ..

•  Internal hashtable error: illegal key supplied! (v3.4) #697 / 3.4.0 -H flag broken #702 done: Fix FLAG_GOT_DIR_FLIST collission with FLAG_HLINKED #705 (maybe also Simple test to validate -H break reported in #702 #703)
• Access to previously freed memory #704 done: Fix use-after-free in generator #706
• 3.4.0 portability regression because of openat(AT_FDCWD #701 done: Fix build on ancient glibc without openat(AT_FDCWD #707

Can I pretty please have my 3.4.1 emergency release with the pre-generated manpages now?
Please? 🥺

[tridge]

@ncopa we'll likely do a 3.4.1 release in the next couple of hours

[ncopa]

Thank you very much!

[tridge]

fixed in 3.4.1