current ebuilds have explicit unconditional: src_install() … dosym ../sbin/haproxy /usr/bin/haproxy … which obviously makes it fail on a merged-usr system. Blocks: bug #690294 Reproducible: Always
> which obviously makes it fail on a merged-usr system. To elaborate, we are combining merged-usr with merged-bin. On such systems, /usr/sbin is a symlink to bin (/usr/bin). I don't see the point in having this /usr/bin/haproxy -> ../sbin/haproxy symlink. I would suggest dropping it from the ebuild unconditionally.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4940f3a69c8b9ac9b4dc2511f2e6da8c3ed59ab commit a4940f3a69c8b9ac9b4dc2511f2e6da8c3ed59ab Author: Christian Ruppert <idl0r@gentoo.org> AuthorDate: 2022-09-22 15:30:13 +0000 Commit: Christian Ruppert <idl0r@gentoo.org> CommitDate: 2022-09-22 15:30:31 +0000 net-proxy/haproxy: Remove ancient /usr/bin/haproxy links Bug: https://bugs.gentoo.org/869974 Signed-off-by: Christian Ruppert <idl0r@gentoo.org> net-proxy/haproxy/haproxy-2.2.9999.ebuild | 1 - net-proxy/haproxy/haproxy-2.4.9999.ebuild | 1 - net-proxy/haproxy/haproxy-2.5.9999.ebuild | 1 - net-proxy/haproxy/haproxy-2.6.6.ebuild | 1 - net-proxy/haproxy/haproxy-2.6.9999.ebuild | 1 - net-proxy/haproxy/haproxy-9999.ebuild | 1 - 6 files changed, 6 deletions(-)
Hello, this problem is still present in net-proxy/haproxy-2.5.8 ebuild. Fresh update done today, sync through webrsync.
(In reply to samurai.no.dojo from comment #3) > Hello, > this problem is still present in net-proxy/haproxy-2.5.8 ebuild. > > Fresh update done today, sync through webrsync. 2.5.x never got fixed wrt this - only the live ebuild (".9999") as a side note, I wonder where you got that 2.5.8 »fresh update today« from… *any* 2.5 was removed from the tree more than a week before: > commit ce5c1596f59b22a6c201f07846e6c984fe33c953 > Date: Tue Feb 14 09:26:57 2023 +0100 > net-proxy/haproxy: Cleanup + drop 2.5 due to EoL soon alas, this commit also removed any >2.4 version with a stable keyword - forcing installed 2.5 to be downgraded to 2.4.18 for the latest stable keyword (<- which btw also has not received the fix). maybe there is a STABLERQ pending/missing to bump 2.6?
