New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #33113 (closed defect: invalid)

Opened 17 months ago

Last modified 15 months ago

openssl: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

Reported by: pkubaj@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: mww@…, jmr@…
Port: openssl

Description

I want to upgrade openssl 1.0.0f_0 to 1.0.0g_0 When I do, there are always plenty of error like in the title.

Attachments

main.log (2.3 MB) - added by pkubaj@… 17 months ago.

Change History

Changed 17 months ago by pkubaj@…

comment:1 Changed 17 months ago by macsforever2000@…

  • Keywords openssl 1.0.0g_0 removed

comment:2 Changed 17 months ago by mww@…

  • Cc jmr@… added

I suppose this is a universal build?

comment:3 Changed 17 months ago by jmr@…

Not really sure why I'm cc'd, but "shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory" suggests it's changed to a directory and then deleted it. Upgrading universal openssl worked fine here, so unless this happens for everyone on 10.7 (I'm on 10.6), you probably want to start by checking for filesystem corruption.

comment:4 Changed 17 months ago by ryandesign@…

  • Summary changed from openssl @1.0.0g_0 "No such file or directory" errors to openssl: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

comment:5 Changed 15 months ago by ryandesign@…

pkubaj, have you made any progress with this? Is this still a problem with openssl 1.0.1, or with any other port? I can't see how it would be an openssl-specific problem.

comment:6 Changed 15 months ago by mww@…

  • Status changed from new to closed
  • Resolution set to invalid

I would also dismiss this report as a file system error. Please re-open if this problem persists with 1.0.1 and/or other ports!

Note: See TracTickets for help on using tickets.