Opened 7 years ago

Closed 7 years ago

#54399 closed defect (fixed)

xemacs unable to download packages; needs efs (and probably xemacs-basic) in /xemacs-packages

Reported by: drallensmith Owned by: dstrubbe (David Strubbe)
Priority: Normal Milestone:
Component: ports Version: 2.4.1
Keywords: Cc:
Port: xemacs

Description

When (even running with sudo or sudo -H) I attempt to download packages via xemacs, I receive various error messages depending on what in the tools/packages menu I attempt to use; most notably, "Symbol's value as variable is void: allow-remote-paths". As far as I can tell, from README.packages in an xemacs download, this is because there needs to be a /xemacs-packages directory below the /opt/local/lib/xemacs-21.4.22 directory, and in it there needs to be the efs package (and probably the xemacs-basic package, which it uses, unless that one is already part of the port). These can be gotten from - among other places - http://ftp.xemacs.org/pub/xemacs/packages/. Once I make these changes, sudo -H xemacs can download and install (xemacs) packages without problems.

-Allen

Change History (7)

comment:1 Changed 7 years ago by mf2k (Frank Schima)

Cc: dstrubbe removed
Keywords: packages efs xemacs-basic removed
Owner: set to dstrubbe
Status: newassigned

comment:2 Changed 7 years ago by dstrubbe (David Strubbe)

On my machine, installing xemacs creates /opt/local/lib/xemacs-21.4.22/xemacs-packages, and efs appears to be installed, since there is a file /opt/local/lib/xemacs-21.4.22/xemacs-packages/info/efs.info. I am not sure why there would be different behavior for you. Are you using the +no_sumo variant by any chance?

comment:3 Changed 7 years ago by dstrubbe (David Strubbe)

Also, by xemacs-basic, do you mean xemacs-base? I don't see any package called xemacs-basic.

comment:4 Changed 7 years ago by drallensmith

I am using +no_sumo, yes; sorry for not mentioning it - perhaps there should be a "variants" field on the trak form? (And you're correct about it being xemacs-base, not xemacs-basic - oops!)

-Allen

comment:5 Changed 7 years ago by dstrubbe (David Strubbe)

The variants are part of the info requested to be put in the ticket: https://guide.macports.org/#project.tickets.guidelines

Is there a reason you don't want to use the default variant which includes sumo? I don't really know what this sumo package is, and I have just used the default. Potentially I could just remove the +no_sumo variant to solve this problem.

comment:6 Changed 7 years ago by drallensmith

"Sumo" is named that because it's comparatively big, installing all the available packages, and in this instance also installs the mule (multilanguage) version. I can get along with sumo, but my past experience with "mule" is that it decreases reliability. Perhaps these can be separated? Or, at the minimum, "no_sumo" noted to result in needing to download the xemacs-base and efs packages oneself?

-Allen

comment:7 Changed 7 years ago by dstrubbe (David Strubbe)

Resolution: fixed
Status: assignedclosed

In 3c80f5ae05ee5fe9857b96ad36548f7ddcdd1f00/macports-ports:

xemacs: Improve +no_sumo variant.

For variant +no_sumo, install efs and xemacs-base packages, which are required for almost anything. Better description of variant. Closes #54399.

Note: See TracTickets for help on using tickets.