Opened 12 months ago
Closed 11 months ago
#68669 closed defect (fixed)
duplicity @0.8.18: error: unrecognized arguments: --librsync-dir=/opt/local
Reported by: | matthias-scheler (Matthias Scheler) | Owned by: | kurthindenburg (Kurt Hindenburg) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | sonoma | Cc: | jmroot (Joshua Root) |
Port: | duplicity |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
After upgrading my Mac to macOS Sonoma I rebuild all the ports as suggested in the migration guide. Unfortunately "duplicity" fails to build:
---> Computing dependencies for duplicity ---> Fetching archive for duplicity ---> Attempting to fetch duplicity-0.8.18_0.darwin_23.x86_64.tbz2 from https://packages.macports.org/duplicity ---> Attempting to fetch duplicity-0.8.18_0.darwin_23.x86_64.tbz2 from https://mse.uk.packages.macports.org/duplicity ---> Attempting to fetch duplicity-0.8.18_0.darwin_23.x86_64.tbz2 from https://fra.de.packages.macports.org/duplicity ---> Building duplicity Error: Failed to build duplicity: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_duplicity/duplicity/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port duplicity failed
I've attached the build log file mentioned in the above error message.
Attachments (1)
Change History (4)
Changed 12 months ago by matthias-scheler (Matthias Scheler)
Attachment: | duplicity.log added |
---|
comment:1 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | sonoma added |
Summary: | duplicity 0.8.18 fails to build under macOS Sonoma → duplicity @0.8.18: error: unrecognized arguments: --librsync-dir=/opt/local |
comment:2 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | jmroot added |
---|
This is probably more fallout from the python portgroup defaulting to python.pep517 yes
since last month.
comment:3 Changed 11 months ago by kurthindenburg (Kurt Hindenburg)
Owner: | set to kurthindenburg |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Bulid log file