invoking evince generates a dbus warning regarding launchd; how to fix this?
HI; invoking evince generates a dbus warning regarding launchd; how to fix this? dbus[28817]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Thanks, Ken Wolcott
Unable to install a2ps
Hi; Here's another odd failure to install a2ps. Compressed log file attached. Thanks, Ken Wolcott a2ps_main.log.bz2 Description: BZip2 compressed data
Fwd: port install of xemacs fails due to failure to install Xaw3d
Hi Ryan; Forgot to use reply-all. -- Forwarded message - From: Kenneth Wolcott Date: Sun, Nov 20, 2022 at 9:15 PM Subject: Re: port install of xemacs fails due to failure to install Xaw3d To: Ryan Schmidt Here's a fresh install log for Xaw3d (attached compressed) On Sun, Nov 20, 2022 at 6:51 PM Kenneth Wolcott wrote: > > Hi Ryan; > > /opt/local/bin/xz --version > xz (XZ Utils) 5.2.7 > liblzma 5.2.7 > > On Sun, Nov 20, 2022 at 4:51 PM Ryan Schmidt wrote: > > > > On Nov 14, 2022, at 16:22, Kenneth Wolcott wrote: > > > > > This appears to be a common problem with several MacPorts install > > > attempts. > > > > > > How do I install xemacs? > > > > > > excerpt... > > > ---> Extracting Xaw3d > > > ---> Extracting libXaw3d-1.6.4.tar.xz > > > Executing: cd > > > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > > > && /opt/local/bin/xz -dc > > > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > > > /usr/bin/tar -xf - > > > Command failed: cd > > > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > > > && /opt/local/bin/xz -dc > > > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > > > /usr/bin/tar -xf - > > > Killed by signal: 9 > > > Error: Failed to extract Xaw3d: command execution failed > > > > I'm not sure what that would fail at that point. > > > > Does the /opt/local/bin/xz command work otherwise? Does "/opt/local/bin/xz > > --version" give a sensible answer for example? > > Xaw3d_main.log.bz2 Description: application/bzip2
Re: port install of xemacs fails due to failure to install Xaw3d
Hi Ryan; /opt/local/bin/xz --version xz (XZ Utils) 5.2.7 liblzma 5.2.7 On Sun, Nov 20, 2022 at 4:51 PM Ryan Schmidt wrote: > > On Nov 14, 2022, at 16:22, Kenneth Wolcott wrote: > > > This appears to be a common problem with several MacPorts install attempts. > > > > How do I install xemacs? > > > > excerpt... > > ---> Extracting Xaw3d > > ---> Extracting libXaw3d-1.6.4.tar.xz > > Executing: cd > > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > > && /opt/local/bin/xz -dc > > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > > /usr/bin/tar -xf - > > Command failed: cd > > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > > && /opt/local/bin/xz -dc > > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > > /usr/bin/tar -xf - > > Killed by signal: 9 > > Error: Failed to extract Xaw3d: command execution failed > > I'm not sure what that would fail at that point. > > Does the /opt/local/bin/xz command work otherwise? Does "/opt/local/bin/xz > --version" give a sensible answer for example? >
Re: Emacs.app does not run after upgrade to macOS 13.0.1
On Nov 10, 2022, at 11:56, Artemio González López wrote: > > After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes > on launch. Apparently, the problem is that it cannot find a library: > > Crashed Thread:0 > > Exception Type:EXC_CRASH (SIGABRT) > Exception Codes: 0x, 0x > > Termination Reason:Namespace DYLD, Code 1 Library missing > Library not loaded: /opt/local/lib/libicui18n.71.dylib > Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> > /opt/local/lib/libxml2.2.dylib > Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), > '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no > such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), > '/usr/local/lib/libicui18n.71.dylib' (no such file), > '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache) > (terminated at launch; ignore backtrace) icu was updated from version 71.x to 72.x on November 5. Everything that links with icu therefore has to be rebuilt. It is possible that a simple "sudo port upgrade outdated" will not upgrade everything in the correct order, and you may have to initiate individual upgrades by name. For example, in this case, having encountered an error about libxml2 still being linked to icu 71, you should "sudo port upgrade libxml2" first, then try again. If you find another build error about another thing that is still linked with icu 71, upgrade that thing, then retry again, etc.
Re: Emacs.app does not run after upgrade to macOS 13.0.1
On Nov 11, 2022, at 13:34, Artemio González López wrote: > > I’m happy to report that after upgrading my ports —which took several days, > because for some reason gcc12 had to be compiled from scratch— Emacs now > works perfectly. You're on macOS 13 so everything will have to be compiled from source because I have not yet set up the automated build machines for macOS 13.
Re: port install of xemacs fails due to failure to install Xaw3d
On Nov 14, 2022, at 16:22, Kenneth Wolcott wrote: > This appears to be a common problem with several MacPorts install attempts. > > How do I install xemacs? > > excerpt... > ---> Extracting Xaw3d > ---> Extracting libXaw3d-1.6.4.tar.xz > Executing: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > && /opt/local/bin/xz -dc > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > /usr/bin/tar -xf - > Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_Xaw3d/Xaw3d/work" > && /opt/local/bin/xz -dc > '/opt/local/var/macports/distfiles/Xaw3d/libXaw3d-1.6.4.tar.xz' | > /usr/bin/tar -xf - > Killed by signal: 9 > Error: Failed to extract Xaw3d: command execution failed I'm not sure what that would fail at that point. Does the /opt/local/bin/xz command work otherwise? Does "/opt/local/bin/xz --version" give a sensible answer for example?
Re: Where is port command documented?
On Nov 14, 2022, at 03:14, Lukas Oberhuber wrote: > > I was wondering where the port command flags are documented. For example, I'm > trying to uninstall a port in a script, but when two versions of the port are > installed, it interactively asks which I want to uninstall. > > The following versions of gimp3 are currently installed: > 1) gimp3 @2.99.14_0+debugoptimized+quartz+vala > 2) gimp3 @2.99.13_1+debugoptimized+quartz+vala (active) > Enter option(s) [1-2/all]: > > This kills my script. What I can't tell is if port -N uninstall gimp3 exists, > or if that is only for port install. > > And before you say: "try it", it's on a ci system so a little harder to try, > and really, I want a way to understand all the available flags. > > And finally, there is no error message when a flag is used in the wrong > place, so that makes trial and error even harder. Example port install -N > gimp3 does not apply the flag but doesn't error. The port(1) manpage was already mentioned, but a web version of it is also available at: https://man.macports.org/port.1.html Single-dash single-letter flags like "-N" are global and apply to all commands and go after "port" and before the command verb (e.g. "sudo port -N install foo" not "sudo port install -N foo"). Double-dash multi-letter flags are specific to the command verb and go after the command verb and before any subsequent list of ports (like "--no-sync" is specific to the "selfupdate" verb and is used as "sudo port selfupdate --no-sync" not "sudo port --no-sync selfupdate"). If you have multiple versions of a port installed and try to uninstall just by name, it prompts interactively to ask which one(s). If you turn off interactivity with "-N", the uninstall will fail since it doesn't know which one to uninstall. If you want to uninstall all installed versions of a particular port, you could use e.g. sudo port -N uninstall installed and name:'^gimp3$'
