Opened 9 months ago
Last modified 4 months ago
#73186 assigned defect
wireshark4 @4.6.0_0+chmodbpf+gnutls+kerberos5+libmaxminddb+libsmi+python313+qt5+zlib: Failed to configure
| Reported by: | thetrial (alabay) | Owned by: | ghosthound |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.11.6 |
| Keywords: | legacy-os, sierra | Cc: | |
| Port: | wireshark4 |
Description
Today macport has choked while trying to build a Wireshark-update on macOS Sierra.
Logfile is attached.
Attachments (1)
Change History (6)
Changed 9 months ago by thetrial (alabay)
comment:1 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 9 months ago by jmroot (Joshua Root)
It would be nice to know why this is unsupported, as it may be something that legacysupport would handle.
comment:3 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
https://gitlab.com/wireshark/wireshark/-/blob/master/doc/wsug_src/wsug_introduction.adoc
- Wireshark 4.4 was the last release branch to support macOS 11.
- Wireshark 4.2 was the last release branch to support macOS 10.14.
- Wireshark 3.6 was the last release branch to support macOS 10.13.
- Wireshark 3.4 was the last release branch to support macOS 10.12.
- Wireshark 2.6 was the last release branch to support Mac OS X 10.6 and 10.7 and OS X 10.8 to 10.11.
- Wireshark 2.0 was the last release branch to support OS X on 32-bit Intel.
- Wireshark 1.8 was the last release branch to support Mac OS X on PowerPC.
The minimum macOS version was increased from 10.11 to 10.13 along with removing workarounds for Qt < 5.15:
https://gitlab.com/wireshark/wireshark/-/commit/b6c161e1f4cca41d6fad248ecf29f443f57e8b25
comment:4 Changed 6 months ago by thetrial (alabay)
Well, I cannot update without error. Is there a workaround? WIll there be a workaround? Even if staying at the last possible version without updating?
comment:5 Changed 4 months ago by thetrial (alabay)
Well I gave up on Wireshark4 and downgraded to Wireshark3. But this is strange – if a port for a version runs for a long time on a system, why can an update break this compatibility? Wireshark4 ran very long on Sierra. An update broke that. Shouldn’t that update than be offside not to break an existing compatibility?
There is another thing. I was excluded quite a while from the ticket system. I had to fake the identifier of the browser to be able to enter trac of MP again. Ain't that peticular? If MP tries to have an downwards compatibility for really old systems (which I really appreciate!), even much older that Sierra – how is it to explain that older browsers have to stay outside? How shall legacy system users report?! Accident or intention?
The log says:
So unfortunately it sounds like the developers have dropped support for macOS Sierra and we'll have to mark the port as requiring macOS High Sierra or later.