Opened 6 years ago
Closed 6 years ago
#58001 closed defect (fixed)
XviD: livecheck not working
Reported by: | chrstphrchvz (Christopher Chavez) | Owned by: | chrstphrchvz (Christopher Chavez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | XviD |
Description
…though I'm not sure why it doesn't work when the pattern seems to clearly be in the page loaded (should match xvidcore-1.3.5.tar.bz2
).
$ port -d livecheck xvid […] DEBUG: Port (livecheck) version is 1.3.5 DEBUG: Fetching https://labs.xvid.com/Downloads.43.0.html DEBUG: The regex is "xvidcore-([0-9.]+).tar.bz2" Error: cannot check if XviD was updated (regex didn't match)
I thought about simplifying this to something like xvidcore-(\d+\.\d+\.\d+)
but that doesn't work either. Anything more complex than (\d+\.\d+)
seems to not work; is there some quirk in MacPorts'/Tcl's regex at play here?
It seems non-ideal for the .
in ${extract.suffix}
to not be escaped (\.
), but maybe that's not an issue worth worrying about, or ${extract.suffix}
might be unnecessary.
It might also be better to use livecheck.url ${homepage}source/
since that's what the existing one redirects to.
Change History (3)
comment:1 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
Thanks for investigating. Indeed that is a Cloudflare message that is "intentionally enabled" by the site owner, and supposedly has no easy way to bypass.
There is a web SVN; but the latest version isn't tagged, so who knows if the next one will be. I just sent a message to their mailing list to see if there's any suggestions on what to use instead.
comment:3 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
Owner: | set to chrstphrchvz |
---|---|
Resolution: | → fixed |
Status: | new → closed |
When I
curl
that URL, I get a page that contains nothing useful, and this message:Somebody will need to talk to the XviD people about talking to their hosting provider about relaxing whatever security service they're using.
Or we need to find a different URL we can use that is not under such restrictions.