Am 11.04.2023 um 19:54 schrieb Matthew Seaman:
Hmmm... I wonder if this is the shared library provides/requires thing
that pkg does? If you run ldd(1) against the binaries from
gitlab-shell, is there any indication of linking against a shlib from
the heimdal port?
If so, then that would seem to be a mistake in the gitlab-shell port,
and it should probably add a LIB_DEPENDS against security/heimdal.
Otherwise, all I can suggest is deleting both heimdal and gitlab-shell
packages, and then reinstalling gitlab-shell. Hopefully that will tidy
up the dependency graph.
I think that is it:
cd /usr/local/share/gitlab-shell/
$ ldd gitlab-shell
gitlab-shell:
libthr.so.3 => /lib/libthr.so.3 (0x801193000)
libc.so.7 => /lib/libc.so.7 (0x8011c1000)
$ ldd gitlab-shell-authorized-keys-check
gitlab-shell-authorized-keys-check:
libthr.so.3 => /lib/libthr.so.3 (0x801157000)
libc.so.7 => /lib/libc.so.7 (0x801185000)
$ ldd gitlab-shell-authorized-principals-check
gitlab-shell-authorized-principals-check:
libthr.so.3 => /lib/libthr.so.3 (0x801148000)
libc.so.7 => /lib/libc.so.7 (0x801176000)
$ ldd gitlab-sshd
gitlab-sshd:
libgssapi.so.3 => /usr/local/lib/heimdal/libgssapi.so.3
(0x8012f2000)
libthr.so.3 => /lib/libthr.so.3 (0x801333000)
libc.so.7 => /lib/libc.so.7 (0x801361000)
libheimntlm.so.0 => /usr/local/lib/heimdal/libheimntlm.so.0
(0x80176b000)
libkrb5.so.26 => /usr/local/lib/heimdal/libkrb5.so.26 (0x801777000)
libhx509.so.5 => /usr/local/lib/heimdal/libhx509.so.5 (0x801811000)
libwind.so.0 => /usr/local/lib/heimdal/libwind.so.0 (0x801862000)
libheimsqlite.so.0 => /usr/local/lib/heimdal/libheimsqlite.so.0
(0x80188d000)
libhcrypto.so.4 => /usr/local/lib/heimdal/libhcrypto.so.4
(0x80196d000)
libasn1.so.8 => /usr/local/lib/heimdal/libasn1.so.8 (0x8019ad000)
libcom_err.so.1 => /usr/local/lib/heimdal/libcom_err.so.1
(0x801a59000)
libheimbase.so.1 => /usr/local/lib/heimdal/libheimbase.so.1
(0x801a60000)
libintl.so.8 => /usr/local/lib/libintl.so.8 (0x801a73000)
libroken.so.18 => /usr/local/lib/heimdal/libroken.so.18
(0x801a81000)
libcrypto.so.11 => /usr/local/lib/libcrypto.so.11 (0x801a97000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x801d23000)
I'm not sure how to handle this.
I saw in the commit logs that heimdal is only used if CGO is enabled in
the build. That could maybe be a work-around for this problem.
Gruß
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
