Date: Wed, 04 Dec 2024 16:44:00 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 283073] www/rubygem-faraday-gitlab: conflicts with www/rubygem-faraday causing chain reaction of conflicts Message-ID: <bug-283073-21402-m8aMCiZukm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283073-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-283073-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283073 John Hein <jcfyecrayz@liamekaens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ruby@FreeBSD.org --- Comment #6 from John Hein <jcfyecrayz@liamekaens.com> --- (In reply to Matthias Fechner from comment #5) That fixes things for rubygem-vagrant_cloud and rubygem-licenses. But this seems like a never ending problem. I think that if gitlab depends= on an older package than the one that most rubygem ports depend on (e.g., rubygem-net-http), it should be using that older dependency installed in a non-default (private) location. If lots of ports need the old and lots need the new version, they should be installed such that they can be installed together. At this point there are 50+ *-gitlab ports many which are basically just du= pes of the non "-gitlab" port except for one or two "gitlab" vs "non-gitlab" dependencies. Just adding more and more -gitlab ports does not seem like a sustainable plan. So yes, your commit from comment 4 "fixes" the breakage for licensee & vagrant_cloud. But this is a bigger problem. Here's the next one: devel/rubygem-licensee and devel/rubygem-danger result in a conflict: . . =3D=3D=3D> Checking if rubygem-faraday-gitlab is already installed =3D=3D=3D> Registering installation for rubygem-faraday-gitlab-2.12.1 as = automatic pkg-static: rubygem-faraday-gitlab-2.12.1 conflicts with rubygem-faraday-2.= 12.1 (installs files into the same place). Problematic file: /usr/local/lib/ruby/gems/3.2/specifications/faraday-2.12.1.gemspec *** Error code 1 Stop. make[1]: stopped in /usr/ports/www/rubygem-faraday-gitlab *** Error code 1 Stop. make: stopped in /usr/ports/devel/rubygem-danger Sure, we could open a new bug (and a meta-bug for all the -gitlab conflicts that are pushing for the proliferation of -gitlab port "flavors") for rubygem-danger. But we need to think of better ways than basically having a second -gitlab ports tree inside the non-gitlab ports tree. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283073-21402-m8aMCiZukm>