Hi, Just to finish up, as the fix seemed trivial (us the PG to set the deps) I have pushed an update doing just this. So update and try again.
Chris > On 21 Apr 2019, at 5:23 am, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > Hi, > > I was curious, so I fired off a build using the buildbots, just to see what > would happen in a clean environment. > > https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/84721/steps/install-dependencies/logs/stdio > > <https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/84721/steps/install-dependencies/logs/stdio> > > And indeed I see the dep on qt5-XYZ there. Interestingly, qt511-base, the > version I would expect, is also there. > > So, looking again at > > https://github.com/macports/macports-ports/blob/master/net/wireshark3/Portfile > > <https://github.com/macports/macports-ports/blob/master/net/wireshark3/Portfile> > > If you look at the qt5 variant, defined at line 63, the issue is actually > obvious really. The qt5 portgroup is correctly used, to pick the right qt5 > build, but then at line 68 there are hardcoded deps on specific ‘qt5’ > versions, which undoes the good work of the qt5 PG. This is a bug in the > wireshark port, which should be looked into. I suggest you file a trac ticket > to ask the maintainer to take a look. > > Chris > > On 21 Apr 2019, at 4:47 am, Chris Jones <jon...@hep.phy.cam.ac.uk > <mailto:jon...@hep.phy.cam.ac.uk>> wrote: > >> Hi, >> >> There is a qt5 port group specifically designed to handle picking the >> correct qt5 version for a given platform. See >> >> https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/qt5-1.0.tcl >> >> <https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/qt5-1.0.tcl> >> >> In your case, on osx 10.11 it should be using the qt511 ports, which use >> 5.11, rather than the main qt5 ports, which currently install 5.12. >> >> So it is strange that you are trying to install qt5-base, as qt511-base >> should be used instead in your case. >> >> I assume your ports are fully up to date ? >> >> Please run >> >> > sudo port sync >> > sudo port upgrade outdated >> > sudo port clean all >> >> Then try again installing the particular wireshark version you want (there >> are numerous) and if it still fails post the complete log file. >> >> Chris >> >> On 20 Apr 2019, at 11:30 pm, Greg Earle <ea...@isolar.dyndns.org >> <mailto:ea...@isolar.dyndns.org>> wrote: >> >>> I've got a Mac mini running El Capitan 10.11.6. I've held the OS back >>> because I have a FireWire audio interface on it and FireWire is deprecated >>> in more recent OSes. >>> >>> I am having a problem with my Blu-ray player not recognizing NFS shares on >>> the same Mac mini. I went to install Wireshark to debug the NFS traffic >>> but it won't install because the current "qt5-qtbase" port is only for >>> Sierra or newer: >>> >>> -- >>> Mac-mini:~ admin$ sudo port install qt5-qtbase >>> ---> Computing dependencies for qt5-qtbase >>> ---> Fetching distfiles for qt5-qtbase >>> Error: qt5-qtbase requires macOS 10.12 or later >>> Error: Failed to fetch qt5-qtbase: incompatible OS version >>> Error: See >>> /opt/local/var/macports/logs/_private_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qtbase/main.log >>> for details. >>> Error: Follow https://guide.macports.org/#project.tickets >>> <https://guide.macports.org/#project.tickets> to report a bug. >>> Error: Processing of port qt5-qtbase failed >>> -- >>> >>> Is there any way to build/install an older Wireshark/Qt5 port combo that >>> will still work on El Capitan? >>> >>> My impression of MacPorts has always been that you can only build/install >>> whatever port happens to be installed after you last did a "port self >>> update". I can't really risk going to Sierra and have this audio interface >>> stop working. :-/ >>> >>> - Greg
smime.p7s
Description: S/MIME cryptographic signature
