virtuoso-7: fetch fails

[mciobanu]

The issue seems to be with Virtuoso, for which a binary isn't found, and then the source isn't found either. It tries to get it from ​http://svwh.dl.sourceforge.net/project/virtuoso/virtuoso/7.2.10 and fails. This is an old URL, not even https, so perhaps it can be adjusted so the build can continue.

I'm on Sonoma, on x86_64.

[ryandesign (Ryan Carsten Schmidt)]

Binaries are not available for virtuoso-7 due to licensing reasons.

The source is available. Fetching virtuoso-7 works fine for me. Attach your main.log file so we can see what happened.

[mciobanu]

Thank you for taking a look.

It turns out the warning I got about my DNS servers ("Your DNS servers incorrectly claim to know the address of nonexistent hosts") was somehow misleading. My understanding was that it could lead to mismatched checksums, but it can also lead to files not being found, and that's what happened.

Well, I fixed my DNS issues and that took care of the downloads, but now I get a segmentation fault. I'm attaching the end of the log (the whole log is 24 MB, and it seems too big).

I guess I should also mention that I'm testing this in QEmu, and the same segmentation fault happens for both Sonoma and Monterey.

[ryandesign (Ryan Carsten Schmidt)]

Replying to mciobanu:

It turns out the warning I got about my DNS servers ("Your DNS servers incorrectly claim to know the address of nonexistent hosts") was somehow misleading. My understanding was that it could lead to mismatched checksums, but it can also lead to files not being found, and that's what happened.

If a file is not found on one server, MacPorts will try another server.

Well, I fixed my DNS issues and that took care of the downloads, but now I get a segmentation fault. I'm attaching the end of the log (the whole log is 24 MB, and it seems too big).

That segmentation fault in onto2vocabularyclass is #68452.

[mciobanu]

Replying to ryandesign:

If a file is not found on one server, MacPorts will try another server.

I understand this now, but I still feel that the message is misleading. It's not that a DNS issue "may cause checksum mismatches", but that we may get some HTML error message instead of an archive with binaries or sources.

That segmentation fault in onto2vocabularyclass is #68452.

Good to know, I'll follow that. Then there is no point in keeping this issue open, but I can't figure how to close it.

Thank you!

[ryandesign (Ryan Carsten Schmidt)]

Replying to mciobanu:

Replying to ryandesign:

If a file is not found on one server, MacPorts will try another server.

I understand this now, but I still feel that the message is misleading. It's not that a DNS issue "may cause checksum mismatches", but that we may get some HTML error message instead of an archive with binaries or sources.

It's not misleading. A misguided ISP may configure their DNS server to point unresolved hosts to a web server configured to return an HTML page with a 200 success response for all requests. MacPorts cannot distinguish such a success response from the success response of a server that actually has the file we are looking for. The HTML file from the misguided ISP's server will not have the checksums of the file we're looking for, and MacPorts will report that as a checksum mismatch.