Bug 260376 - textproc/libexttextcat fetch fails
Summary: textproc/libexttextcat fetch fails
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Daniel Engberg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-13 05:19 UTC by dgilbert
Modified: 2022-11-09 23:12 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (office)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dgilbert 2021-12-13 05:19:07 UTC 
I see that libexttextcat was recently updated to 3.4.6.  Problem is: the distfile is unavailable.  dev-www.libreoffice.org (the given site) refuses ssl/443 over ipv6 and stalls forever, never answering for ipv4.  distcache doesn't have the file.

... so this fails and then libreoffice fails ... so ... bad.
Comment 1 Daniel Engberg freebsd_committer freebsd_triage 2021-12-13 08:40:50 UTC 
IPv4 works fine for me
Comment 2 Thierry Thomas freebsd_committer freebsd_triage 2021-12-13 09:36:16 UTC 
No problem here:

=> libexttextcat-3.4.6.tar.xz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch https://dev-www.libreoffice.org/src/libexttextcat/libexttextcat-3.4.6.tar.xz
libexttextcat-3.4.6.tar.xz                            1085 kB 2871 kBps    00s
===> Fetching all distfiles required by libexttextcat-3.4.6 for building

Maybe it was a temporary failure; could you please try again?
Comment 3 dgilbert 2021-12-13 20:40:10 UTC 
Whatever CDN they're using is broken, then.  I can traceroute and ping both v6 and v4.  v6 gives connection refused on 443 and v4 times out without a reply to the SYN packet.
Comment 4 dgilbert 2021-12-29 17:16:54 UTC 
finally had time to figure this one out.  The site is filtering packet-to-big ipv6.  Pretty much anyone on a network behind a tunnel will fail.  Could we cache this one on a freebsd site s.t. this class of people will still get it?
Comment 5 Daniel Engberg freebsd_committer freebsd_triage 2022-11-06 19:58:41 UTC 
This shouldn't be an issue anymore, please reuse this PR if it is.
Comment 6 Graham Perrin freebsd_committer freebsd_triage 2022-11-09 23:12:48 UTC 
Triage: assignment to the person who closed the report.