[Bug 297497] net/rsync: update to 3.5.0 (security)

[email protected]
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297497

            Bug ID: 297497
           Summary: net/rsync: update to 3.5.0 (security)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://rsync.samba.org/security.html#s3_5_0
                OS: Any
            Status: New
          Keywords: security
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])

Created attachment 273723
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=273723&action=edit
Basic patch to update rsync from 3.4.4 to 3.5.0 (build not working)

Announcement through the rsync-announce mailing list:
"rsync 3.5.0 security release - 33 CVEs"
https://lists.samba.org/archive/rsync-announce/2026/000126.html
see also https://download.samba.org/pub/rsync/NEWS#3.5.0
and https://rsync.samba.org/security.html#s3_5_0


I tried to patch on my own, but I did struggle with multiple things.

1) As I see, the patch files/patch-lib_sysxattrs.c is not included in the
upstream source, but when I remove that file from Ports tree, then portupgrade
does ask for "File to patch:".

2) When I do enable FLAGS / --file-flags, applying the patch
files/extra-patch-file-flags.diff does fail with multiple rejects and
"misordered hunks! output would be garbled" message.

My knowledge of Ports tree magic is not deep enough and I my owledge about C is
almost nothing. So I do not feel comfortable to trace and adjust all the
rejects for files/extra-patch-file-flags.diff.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.