[Bug 276152] Mk/Uses/gem.mk all rubygems fail to download

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 06 Jan 2024 16:33:11 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276152

            Bug ID: 276152
           Summary: Mk/Uses/gem.mk all rubygems fail to download
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: lysfjord.daniel@smokepit.net

Created attachment 247488
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=247488&action=edit
Changes done to "fix" issue.

This might be filed under the wrong thing, but I have to place it somewhere:)

I could not build any rubygem where the gem needed to be downloaded. The
problem started today.

Snippet from a random failing gem (net/rubygem-gitaly):
=======================<phase: fetch          >============================
===== env: NO_DEPENDS=yes USER=root UID=0 GID=0
=> rubygem/gitaly-16.7.0.gem doesn't seem to exist in /portdistfiles/.
=> Attempting to fetch https://rubygems.org/downloads/rubygem/gitaly-16.7.0.gem
fetch: https://rubygems.org/downloads/rubygem/gitaly-16.7.0.gem: Forbidden
=> Attempting to fetch
http://distcache.FreeBSD.org/ports-distfiles/rubygem/gitaly-16.7.0.gem
fetch: http://distcache.FreeBSD.org/ports-distfiles/rubygem/gitaly-16.7.0.gem:
Not Found
=> Couldn't fetch it - please try to retrieve this
=> port manually into /portdistfiles/ and try again.
*** Error code 1


Looking at the URL, it should be without rubygem/, so:
https://rubygems.org/downloads/gitaly-16.7.0.gem . That's the download URL you
get if you go to rubygems.org and search for gitaly and click the download
link.

I fixed it by altering Mk/Uses/gem.mk to not include the ${GEM_DIST_SUBDIR}
when defining DISTFILES, and in the gem-extract function, together with
removing rubygem/ from distinfo.. This is probably not the right way around the
issue, but it makes it work for today..

-- 
You are receiving this mail because:
You are the assignee for the bug.