Unable to fetch sources from GitLab instance

[Jason Liu]

Indeed, I was downloading the tarball and manually putting it into the
distfiles directory, so that I could get the rest of the Portfile written.
I guess I'll just have to take it on faith that one of the newer buildbots
will manage to save the distfile into distfiles.macports.org before the
older builders attempt their builds.

I'm aware of the curl issues on older Macs, since this topic was recently
discussed on this mailing list as well... which is why I tried manually
running /usr/bin/curl on the tarball, which downloaded fine on both my
10.13 High Sierra and 10.11 El Capitan machines. That's why I was confused
when MacPorts couldn't seem to download the file. I was under the
impression that MacPorts uses the Apple/system libcurl, which... is the
same as what /usr/bin/curl uses? Or am I mistaken about that?

In any case, thanks Dave, for trying it out and letting me know that I'm
not slowly losing my mind writing these Portfiles. 😆 (Or maybe I am
anyway, haha)

-- 
Jason Liu


On Sat, Jul 29, 2023 at 10:26 PM Dave Allured - NOAA Affiliate via
macports-dev <macports-dev at lists.macports.org> wrote:

> Jason, port fetch with your unmodified portfile works fine for me.
> Monterey x86_64, Macports 2.81, freshly updated.  I think your portfile
> recipe for this gitlab instance is good.  There have been several recent
> reports of Macports fetch problems.  These often relate to down level Apple
> native versions of curl on older Macs, improper certificate updates on
> servers, etc.
>
> There is a shortcut if it is only a single tar file.  Instead of spending
> time diagnosing, just manually download the distfile, which you already
> have.  Then manually insert that into
> (prefix)/var/macports/distfiles/librist, then re-run port install, as
> described in https://trac.macports.org/wiki/ProblemHotlist#fetch-failures.
> Port install will then skip the problematic download and be happy with the
> local copy.  When your portfile is later merged into Macports, the distfile
> will be propagated to various mirrors, which will then serve anyone having
> problems with the original server.
>
> Also see:  https://trac.macports.org/wiki/ProblemHotlist#letsencrypt
>
>
> On Sat, Jul 29, 2023 at 9:14 AM Jason Liu <jasonliu at umich.edu> wrote:
>
>> By the way, here is my Portfile for librist, in case anyone wants to try
>> and see whether fetching from VideoLAN's GitLab instance works for them.
>> --
>> Jason Liu
>>
>>
>> On Fri, Jul 28, 2023 at 11:47 PM Jason Liu <jasonliu at umich.edu> wrote:
>>
>>> Hi all,
>>>
>>> I suppose I should be directing this question to René Bertin, since he's
>>> the maintainer of the VLC port, but I'm sending this to the entire dev
>>> mailing list, in case anyone else has any ideas.
>>>
>>> I'm trying to create a Portfile for librist, which is one of the
>>> projects that's being hosted on https://code.videolan.org. My question
>>> to René (and everyone else) is: Have you had any luck trying to fetch
>>> sources from code.videolan.org? When I try to use the gitlab PortGroup,
>>> MacPorts doesn't seem to find a tarball at the URL that is generated by the
>>> PortGroup. However, I'm able to download the file using a web browser, and
>>> even curl downloads the file just fine:
>>>
>>> /usr/bin/curl -LROJk
>>> https://code.videolan.org/rist/librist/-/archive/v0.2.7/librist-v0.2.7.tar.bz2
>>>
>>> Does anyone have any explanation for the behavior that I'm seeing?
>>> --
>>> Jason Liu
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230729/89837a35/attachment.htm>