-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./share/containers/fedora.dockerfile
doesn't build
#839
Comments
./share/containers/fedora.dockerfile
doesn't build correctly./share/containers/fedora.dockerfile
doesn't build
libbsd is unwanted in Fedora and RHEL, and the recently released Fedora 39 doesn't contain this dependency. Let's build without it to avoid the compilation error. Resolves: shadow-maint#839 Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com>
libbsd is unwanted in Fedora and RHEL, and the recently released Fedora 39 doesn't contain this dependency. Let's build without it to avoid the compilation error. Resolves: shadow-maint#839 Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com>
It's failing because the latest stable Fedora has been switched to 39 recently, and this one doesn't containe libbsd dependency. |
But Fedora 39 still has libbsd, right? I see it in this page: https://packages.fedoraproject.org/pkgs/libbsd/libbsd/ Did they remove it from the docker container or something? Or did they drop the package in Fedora 39 recently and forgot to update that page? |
Yes, libbsd is still there but it's not recommended to link base packages against libbsd. The package is available for download, but it has to be installed manually, or via a dependency. I dropped the shadow dependency for this package some time ago for Fedora 39+, but I forgot to update the build configuration options. Last week Fedora 39 was released and I guess at some point during this time the containers tag for |
I think we should prefer linking against libbsd:
A problem of not linking to libbsd is that we use our own definition of readpassphrase(3bsd). Usually, I'd say it's fine to dog-food our own definitions of stuff, but that function scares me, at 141 lines of sensitive code. But yeah, if Fedora 39 is out there without the dep, I guess this patch is good. Please document in the commit message that libbsd was removed from the shadow deps in Fedora 39, and you have my |
libbsd is unwanted in Fedora and RHEL, and the recently released Fedora 39 doesn't contain this dependency in the base image. shadow removed libbsd from its dependencies for Fedora 39, so let's build without it to avoid compilation errors. Resolves: shadow-maint#839 Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Reviewed-by: Alejandro Colomar <alx@kernel.org>
I also prefer it, but shadow is included in the base image, and thus having libbsd as a dependency also makes this package part of the base image. This last part wants to be avoided by Fedora. |
libbsd is unwanted in Fedora and RHEL, and the recently released Fedora 39 doesn't contain this dependency in the base image. shadow removed libbsd from its dependencies for Fedora 39, so let's build without it to avoid compilation errors. Resolves: #839 Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Reviewed-by: Alejandro Colomar <alx@kernel.org>
That is on the
master
branch.I removed all the cached images from docker so that it starts from scratch, and I still see the failure. Also, CI started failing for a PR that doesn't touch anything related to readpassphrase(3bsd) or libbsd.
The text was updated successfully, but these errors were encountered: