Opened 7 months ago

Closed 5 weeks ago

#65114 closed defect (fixed)

bzr @2.6.0_3: bzr merge with bzr+ssh no longer functions

Reported by: ianstyxial Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: highsierra Cc: judaew (Vadym-Valdis Yudaiev)
Port: bzr

Description (last modified by ryandesign (Ryan Schmidt))

The port bzr @2.6.0_3 (active) on macOS 10.13.6 the bzr merge with bzr+ssh no longer functions. Indeed, if I run

$ bzr merge bzr+ssh://pi@lyra/~/AVision/

I get the error messages as in the attached file, starting with

Merging from remembered submit location bzr+ssh://pi@lyra/~/AVision/
bzr: ERROR: exceptions.SyntaxError: invalid syntax (signing.py, line 32)

bzr has worked fine for years with bzr+ssh, but I recently upgraded to the latest port of Bazaar on macOS 10.13.6, and I ran into this issue.

Check version:

sh-3.2# port installed bzr
The following ports are currently installed:
  bzr @2.6.0_3 (active)

Indeed:

bash-3.2$ bzr --version
Bazaar (bzr) 2.6.0
  Python interpreter: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python 2.7.18
  Python standard library: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
  Platform: Darwin-17.7.0-x86_64-i386-64bit
  bzrlib: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/bzrlib
  Bazaar configuration: /Users/ian/.bazaar
  Bazaar log file: /Users/ian/.bzr.log

Attachments (1)

bzr_merge_over_ssh.out (8.2 KB) - added by ianstyxial 7 months ago.
standard output, including error messages of bzr merge, using bzr+ssh

Download all attachments as: .zip

Change History (8)

Changed 7 months ago by ianstyxial

Attachment: bzr_merge_over_ssh.out added

standard output, including error messages of bzr merge, using bzr+ssh

comment:1 Changed 7 months ago by ryandesign (Ryan Schmidt)

Description: modified (diff)
Keywords: highsierra added
Owner: set to raimue
Port: bzr added
Status: newassigned
Summary: port bzr @2.6.0_3 on macOS 10.13.6 : bzr merge with bzr+ssh no longer functionsbzr @2.6.0_3: bzr merge with bzr+ssh no longer functions

comment:2 Changed 8 weeks ago by chrishecker

I am having the same problem. I'm looking into it, and it looks like nacl dropped support for python 2.7 in their 1.5.0 release (https://pynacl.readthedocs.io/en/latest/changelog/), but it was integrated in the macports python py27-pynacl package anyway without noticing? Not sure how tests didn't catch this, since it literally won't compile due to the type annotations mentioned above? Can I mention the maintainer here @stromnov or the folks who did the checkin @blazewicz and @judaew?

I'm going to try to roll back to 1.4.0 and see if that fixes it.

Okay, I got this working by following the steps on this page: https://trac.macports.org/wiki/howto/InstallingOlderPort

The bad commit is this: 787884021c6882862ee38e73924b5de6e4109201

So the right command is: git checkout 65ff5a6e0ceddc8bcf48596dda8450d1565c232f

Then this will build 1.4.0: sudo port install subport=py27-pynacl

Installing py27-pynacl @1.4.0_0

And then bzr+ssh protocol works!

Can we get the 1.5.0 backed out of the py27 builds to fix this?

Thanks, Chris

comment:3 Changed 7 weeks ago by judaew (Vadym-Valdis Yudaiev)

Owner: changed from raimue to raimue, judaew

comment:4 Changed 7 weeks ago by judaew (Vadym-Valdis Yudaiev)

Cc: judaew added
Owner: changed from raimue, judaew to raimue

comment:5 Changed 5 weeks ago by Vadym-Valdis Yudaiev <judaew@…>

Resolution: fixed
Status: assignedclosed

In 725d54f012381b7fdafd5974f83ac4b61f2f430c/macports-ports (master):

py27-pynacl: Downgrade to 1.4.0, close trachttps://github.com/macports/macports-ports/pull/65114

Closed: #65114

comment:6 Changed 5 weeks ago by judaew (Vadym-Valdis Yudaiev)

Resolution: fixed
Status: closedreopened

Sorry, I mixed up the ticket number. This commit refers to #64919.

comment:7 Changed 5 weeks ago by judaew (Vadym-Valdis Yudaiev)

Resolution: fixed
Status: reopenedclosed

This problem is linked and fixed in #64919. If not, please re-open the ticket.

Note: See TracTickets for help on using tickets.