Bug 2245095 - libserf rpm .spec doesn't use scons, and therefore doesn't link against GSSAPI
Summary: libserf rpm .spec doesn't use scons, and therefore doesn't link against GSSAPI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libserf
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-19 17:13 UTC by Richard Harman
Modified: 2023-12-20 02:33 UTC (History)
4 users (show)

Fixed In Version: libserf-1.3.10-3.fc40 libserf-1.3.10-3.fc39 libserf-1.3.10-3.fc38
Clone Of:
Environment:
Last Closed: 2023-12-07 15:03:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA SERF-204 0 None None None 2023-12-08 11:39:08 UTC

Description Richard Harman 2023-10-19 17:13:18 UTC
libserf-1.3.9-27 has a .spec that doesn't use scons to build, and as a result won't link against GSSAPI; which is impacting my use of subversion under Fedora against a GSSAPI enabled websvn repo.

Default from package from f38:

$ ldd /usr/lib64/libserf-1.so
	linux-vdso.so.1 (0x00007ffec250f000)
	libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fb2df800000)
	libssl.so.3 => /lib64/libssl.so.3 (0x00007fb2dfd5e000)
	libz.so.1 => /lib64/libz.so.1 (0x00007fb2dfd44000)
	libapr-1.so.0 => /lib64/libapr-1.so.0 (0x00007fb2dfd04000)
	libaprutil-1.so.0 => /lib64/libaprutil-1.so.0 (0x00007fb2dfcd5000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fb2df622000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fb2dfcc9000)
	libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007fb2dfc90000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fb2dfc65000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fb2dfe3a000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fb2df541000)

When I compile libserf (as per libserf's instructions) w/ scons GSSAPI=/usr:

$ ldd libserf-1.so
	linux-vdso.so.1 (0x00007ffe60be6000)
	libssl.so.3 => /lib64/libssl.so.3 (0x00007f208b443000)
	libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f208b000000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f208b429000)
	libapr-1.so.0 => /lib64/libapr-1.so.0 (0x00007f208afc0000)
	libaprutil-1.so.0 => /lib64/libaprutil-1.so.0 (0x00007f208af91000)
	libldap.so.2 => /lib64/libldap.so.2 (0x00007f208af2c000)
	liblber.so.2 => /lib64/liblber.so.2 (0x00007f208af1a000)
	libdb-5.3.so => /lib64/libdb-5.3.so (0x00007f208ad51000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f208ad26000)
	libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f208acd0000)
	libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f208abf7000)
	libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f208abdf000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f208abd6000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f208a9f8000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f208a9ee000)
	libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f208a9b5000)
	libevent-2.1.so.7 => /lib64/libevent-2.1.so.7 (0x00007f208a95d000)
	libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f208a93e000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f208a85b000)
	libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f208a84b000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f208a844000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f208a832000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f208b51e000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f208a805000)
	libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f208a769000)

Reproducible: Always

Comment 1 Fedora Update System 2023-12-07 15:02:10 UTC
FEDORA-2023-3ced4ec1b2 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3ced4ec1b2

Comment 2 Fedora Update System 2023-12-07 15:03:43 UTC
FEDORA-2023-3ced4ec1b2 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2023-12-11 10:00:13 UTC
FEDORA-2023-757af7f881 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-757af7f881

Comment 4 Fedora Update System 2023-12-11 11:49:01 UTC
FEDORA-2023-46153e60e3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-46153e60e3

Comment 5 Fedora Update System 2023-12-12 01:29:46 UTC
FEDORA-2023-757af7f881 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-757af7f881`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-757af7f881

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-12-12 02:39:25 UTC
FEDORA-2023-46153e60e3 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-46153e60e3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-46153e60e3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-12-18 02:03:32 UTC
FEDORA-2023-757af7f881 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-12-20 02:33:26 UTC
FEDORA-2023-46153e60e3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.