Re: port install of xemacs fails due to failure to install Xaw3d

2023-01-30 Thread Kenneth Wolcott
Hi Ryan;

  I get a different error now when trying to install xemacs:

*** PANIC *** Configure tests are not working - compiler is broken.
*** PANIC *** Please examine config.log for compilation errors.

Thanks,
Ken

On Mon, Jan 30, 2023 at 9:43 PM Ryan Schmidt  wrote:
>
> On Nov 20, 2022, at 23:39, Kenneth Wolcott wrote:
> >
> > 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?
> >>>
> > 
>
> Failure to extract in trace mode on Ventura is:
>
> https://trac.macports.org/ticket/66358
>
> Workaround: don't use trace mode
>


xemacs_config.log.bz2
Description: BZip2 compressed data


xemacs_main.log.bz2
Description: BZip2 compressed data


Re: invoking evince generates a dbus warning regarding launchd; how to fix this?

2023-01-30 Thread Kenneth Wolcott
Thank you, works!

On Mon, Jan 30, 2023 at 9:41 PM Ryan Schmidt  wrote:
>
> On Nov 21, 2022, at 00:21, Kenneth Wolcott wrote:
>
> > 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!
>
> Run the command:
>
> port notes dbus
>
> and follow the instructions it prints.
>
>


Re: gv apparently silently fails to install properly

2023-01-30 Thread Kenneth Wolcott
Hi Ryan;

  Thank you for the link to the bug report.

  I just a selfupdate  earlier (after the announcement of a new port
version) and upgraded, then I removed gv and reinstalled (via source)
and I get the same error message. I didn't expect any changes since I
did not see any gv update, just a data point, hope that's useful.

Thanks,
Ken

On Mon, Jan 30, 2023 at 9:37 PM Ryan Schmidt  wrote:
>
> On Dec 19, 2022, at 15:55, Kenneth Wolcott wrote:
> >
> >  I recently uninstalled and re-installed gv.
> >
> >  There were no errors that I saw during the install (source code
> > build forced with "-s").
> >
> > Yet, when I try to invoke gv, I get a what looks to be a linkage error:
> >
> > /opt/local/bin/gv -v dyld[7999]: symbol not found in flat namespace 
> > '_yylex''
>
> https://trac.macports.org/ticket/66211
>
>


Re: port install of xemacs fails due to failure to install Xaw3d

2023-01-30 Thread Ryan Schmidt
On Nov 20, 2022, at 23:39, Kenneth Wolcott wrote:
> 
> 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?
>>> 
> 

Failure to extract in trace mode on Ventura is:

https://trac.macports.org/ticket/66358

Workaround: don't use trace mode



Re: invoking evince generates a dbus warning regarding launchd; how to fix this?

2023-01-30 Thread Ryan Schmidt
On Nov 21, 2022, at 00:21, Kenneth Wolcott wrote:

> 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!

Run the command:

port notes dbus

and follow the instructions it prints.




Re: While trying to install lilypond, libuninameslist failed; install libuninameslist failed

2023-01-30 Thread Ryan Schmidt
On Nov 21, 2022, at 11:02, Kenneth Wolcott wrote:
> 
> While trying to install lilypond, libuninameslist failed; install
> libuninameslist failed
> 
> Executing:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libuninameslist/libuninameslist/work"
> && /usr/bin/gzip -dc
> '/opt/local/var/macports/distfiles/libuninameslist/libuninameslist-20180701.tar.gz'
> | /usr/bin/tar -xf -
> Command failed:  cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libuninameslist/libuninameslist/work"
> && /usr/bin/gzip -dc
> '/opt/local/var/macports/distfiles/libuninameslist/libuninameslist-20180701.tar.gz'
> | /usr/bin/tar -xf -
> Killed by signal: 9
> Error: Failed to extract libuninameslist: command execution failed
> 
> Compressed log file attached.
> 
> Thanks,
> Ken Wolcott
> 

The log shows this was on Ventura, so this bug is:

https://trac.macports.org/ticket/66358

Workaround: don't use trace mode.

Re: gv apparently silently fails to install properly

2023-01-30 Thread Ryan Schmidt
On Dec 19, 2022, at 15:55, Kenneth Wolcott wrote:
> 
>  I recently uninstalled and re-installed gv.
> 
>  There were no errors that I saw during the install (source code
> build forced with "-s").
> 
> Yet, when I try to invoke gv, I get a what looks to be a linkage error:
> 
> /opt/local/bin/gv -v dyld[7999]: symbol not found in flat namespace '_yylex''

https://trac.macports.org/ticket/66211




Re: Issue with installing port

2023-01-30 Thread Ryan Schmidt
On Jan 26, 2023, at 09:07, Will Senn wrote:

> On 1/26/23 1:43 AM, Joshua Root wrote:
>>> I'm trying to get pandoc to install.
>> The ticket for this is , FWIW.
> 
> I promise you I did search :). Thanks for the link though, it confirms it's 
> not just me!
> 
> `sudo port install pandoc -stack` works for now.
> 
> Suppose it didn't though... would I not be able to get the working version 
> that previously existed at all?

https://trac.macports.org/wiki/howto/InstallingOlderPort

> or is this an actual bug  in the recipe for 10.x's that somebody might fix 
> (it not working on MacOS < 11). I'm kind of clueless as to how macports works 
> behind the scenes because it has just pretty much worked for me over the 
> years without my having to worry about it.

The Portfile was deliberately programmed to do something different on macOS 
10.x than on macOS 11 and later. Based on the build failures, that appears to 
have been the wrong thing to do, and the Portfile has since been changed to no 
longer do that.

> I remember somebody way back when telling me that over time, things might 
> eventually stop working, but I thought that was bitrot or something, not this 
> kind of thing.

Most MacPorts contributors test on the latest or at least a recent macOS 
version. Most software developers also upgrade their systems to the latest or 
recent versions. Thus, as time goes on and ports are updated to new versions, 
it becomes increasingly likely that some change is introduced in some OS 
version and that some software starts depending on that change, and that users 
who remain on old OS versions are more likely to experience problems as a 
result. Whenever you find a problem, report it and hopefully someone can figure 
out how to fix it.



MacPorts 2.8.1 has been released

2023-01-30 Thread Joshua Root

The MacPorts Project is pleased to announce the release of version
2.8.1. This is a bugfix release with small changes only. See the
ChangeLog [1] for the list of changes.

If you already have MacPorts installed, the preferred method for
updating is to run:

   sudo port selfupdate

For new installs, there are also package installers available for macOS
versions ranging from macOS 13 Ventura all the way back to 10.4 at [2]. 
The source is also available as tarballs compressed with gzip or bzip2, 
or from the git tag [3].


Detached PGP signatures for the disk images, packages and source
tarballs have been made with my key, which is available on the
keyservers and my MacPorts wiki page [4], the fingerprint being:

0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58  0C02 01FF 673F B4AA E6CD

Josh
(on behalf of the MacPorts Port Managers)

[1] 
[2] 
[3] 
[4] 




OpenPGP_signature
Description: OpenPGP digital signature