Re: HEADSUP: libsepol and libsemanage soname bump
On Thu, Nov 05, 2020 at 03:59:18PM +0100, Petr Lautrbach wrote: > > There are few other components which needs to be rebuild: > > > > parted - for some reason it links to libsepol even though I haven't found a > > code > > which would use it. I've proposed patch upstream > > > > https://alioth-lists.debian.net/pipermail/parted-devel/2020-November/005500.html I've applied your patch upstream, and it is currently building for rawhide. Thanks! Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: HEADSUP: libsepol and libsemanage soname bump
On 11/5/20 7:59 AM, Petr Lautrbach wrote: > On Wed, Nov 04, 2020 at 09:47:50AM +0100, Petr Lautrbach wrote: >> Hi, >> >> in order to prevent backward compatibility libsepol and libsemanage used had >> few >> symbols defined twice and used symbol versioning for them. But when LTO was >> enabled these symbols were completely dropped during compilation, see >> https://github.com/SELinuxProject/selinux/issues/245 >> >> In order to fix it, it was decided to drop these duplicate symbols and also >> long >> time deprecated symbols and therefore sonames of libsepol and libsemanage >> were >> bumped. >> >> The following SELinux userspace components are built and prepared to be >> merged in >> "f34-build-side-33413" side tag: >> >> selinux-policy-3.14.7-7.fc34 >> setools-4.4.0-0.1.20201102git05e90ee.fc34 >> checkpolicy-3.1-4.fc34 >> policycoreutils-3.1-5.fc34 >> libsemanage-3.1-4.fc34 >> libselinux-3.1-4.fc34 >> libsepol-3.1-4.fc34 >> >> There are few other components which needs to be rebuild: >> >> parted - for some reason it links to libsepol even though I haven't found a >> code >> which would use it. I've proposed patch upstream >> >> https://alioth-lists.debian.net/pipermail/parted-devel/2020-November/005500.html >> >> shadow-utils - https://src.fedoraproject.org/rpms/shadow-utils/pull-request/6 >> sssd - https://src.fedoraproject.org/rpms/sssd/pull-request/7 >> >> As none of packages which require either libsepol or libsemanage use dropped >> symbols and in order not to break build root during soname bumps I've added >> temporary >> subpackages with original library versions - libsepol-compat with >> libsepol.so.1 >> and libsemanage-compat with libsemanage.so.1. These subpackage will be >> dropped >> as soon as everything is rebuilt in Rawhide. >> >> I've sucessfuly built all packages also in my COPR repository >> https://copr.fedorainfracloud.org/coprs/plautrba/selinux-fedora/builds/ >> >> If there's no objection I'd like to merge the side tag to rawhide as soon as >> possible. >> > This is merged now > https://bodhi.fedoraproject.org/updates/FEDORA-2020-44f878be7e Thanks! Good to have those off my LTO list as well :-) jeff ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: HEADSUP: libsepol and libsemanage soname bump
On Wed, Nov 04, 2020 at 09:47:50AM +0100, Petr Lautrbach wrote: > Hi, > > in order to prevent backward compatibility libsepol and libsemanage used had > few > symbols defined twice and used symbol versioning for them. But when LTO was > enabled these symbols were completely dropped during compilation, see > https://github.com/SELinuxProject/selinux/issues/245 > > In order to fix it, it was decided to drop these duplicate symbols and also > long > time deprecated symbols and therefore sonames of libsepol and libsemanage were > bumped. > > The following SELinux userspace components are built and prepared to be > merged in > "f34-build-side-33413" side tag: > > selinux-policy-3.14.7-7.fc34 > setools-4.4.0-0.1.20201102git05e90ee.fc34 > checkpolicy-3.1-4.fc34 > policycoreutils-3.1-5.fc34 > libsemanage-3.1-4.fc34 > libselinux-3.1-4.fc34 > libsepol-3.1-4.fc34 > > There are few other components which needs to be rebuild: > > parted - for some reason it links to libsepol even though I haven't found a > code > which would use it. I've proposed patch upstream > > https://alioth-lists.debian.net/pipermail/parted-devel/2020-November/005500.html > > shadow-utils - https://src.fedoraproject.org/rpms/shadow-utils/pull-request/6 > sssd - https://src.fedoraproject.org/rpms/sssd/pull-request/7 > > As none of packages which require either libsepol or libsemanage use dropped > symbols and in order not to break build root during soname bumps I've added > temporary > subpackages with original library versions - libsepol-compat with > libsepol.so.1 > and libsemanage-compat with libsemanage.so.1. These subpackage will be dropped > as soon as everything is rebuilt in Rawhide. > > I've sucessfuly built all packages also in my COPR repository > https://copr.fedorainfracloud.org/coprs/plautrba/selinux-fedora/builds/ > > If there's no objection I'd like to merge the side tag to rawhide as soon as > possible. > This is merged now https://bodhi.fedoraproject.org/updates/FEDORA-2020-44f878be7e signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[ELN] Re: HEADSUP: libsepol and libsemanage soname bump
On Wed, Nov 04, 2020 at 03:48:28PM +0100, Miro Hrončok wrote: > On 11/4/20 3:41 PM, Gary Buhrmaster wrote: > > On Wed, Nov 4, 2020 at 8:48 AM Petr Lautrbach wrote: > > > > > As none of packages which require either libsepol or libsemanage use > > > dropped > > > symbols and in order not to break build root during soname bumps I've > > > added temporary > > > subpackages with original library versions - libsepol-compat with > > > libsepol.so.1 > > > and libsemanage-compat with libsemanage.so.1. These subpackage will be > > > dropped > > > as soon as everything is rebuilt in Rawhide. > > > > For some reason I thought lib-compat package > > naming was deprecated in favor of lib1 package > > naming (or lib_1 if the last X was a number) > > for a .1 soname example. Although as a temporary > > bypass that is going away before it is exposed in a > > release I doubt it really matters, but is my understanding > > correct about the preferred new naming conventions? > > You are correct, "compat" in package names is no longer the proper way. > > See https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple > I stand corrected. Thanks. As of now sssd and shadow-utils are already built the side-tag so they don't need it anymore. But it could still cause troubles to ELN so I'll remove -compat packages as soon as I'm sure that they are after this. Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: HEADSUP: libsepol and libsemanage soname bump
On 11/4/20 3:41 PM, Gary Buhrmaster wrote: On Wed, Nov 4, 2020 at 8:48 AM Petr Lautrbach wrote: As none of packages which require either libsepol or libsemanage use dropped symbols and in order not to break build root during soname bumps I've added temporary subpackages with original library versions - libsepol-compat with libsepol.so.1 and libsemanage-compat with libsemanage.so.1. These subpackage will be dropped as soon as everything is rebuilt in Rawhide. For some reason I thought lib-compat package naming was deprecated in favor of lib1 package naming (or lib_1 if the last X was a number) for a .1 soname example. Although as a temporary bypass that is going away before it is exposed in a release I doubt it really matters, but is my understanding correct about the preferred new naming conventions? You are correct, "compat" in package names is no longer the proper way. See https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: HEADSUP: libsepol and libsemanage soname bump
On Wed, Nov 4, 2020 at 8:48 AM Petr Lautrbach wrote: > As none of packages which require either libsepol or libsemanage use dropped > symbols and in order not to break build root during soname bumps I've added > temporary > subpackages with original library versions - libsepol-compat with > libsepol.so.1 > and libsemanage-compat with libsemanage.so.1. These subpackage will be dropped > as soon as everything is rebuilt in Rawhide. For some reason I thought lib-compat package naming was deprecated in favor of lib1 package naming (or lib_1 if the last X was a number) for a .1 soname example. Although as a temporary bypass that is going away before it is exposed in a release I doubt it really matters, but is my understanding correct about the preferred new naming conventions? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
HEADSUP: libsepol and libsemanage soname bump
Hi, in order to prevent backward compatibility libsepol and libsemanage used had few symbols defined twice and used symbol versioning for them. But when LTO was enabled these symbols were completely dropped during compilation, see https://github.com/SELinuxProject/selinux/issues/245 In order to fix it, it was decided to drop these duplicate symbols and also long time deprecated symbols and therefore sonames of libsepol and libsemanage were bumped. The following SELinux userspace components are built and prepared to be merged in "f34-build-side-33413" side tag: selinux-policy-3.14.7-7.fc34 setools-4.4.0-0.1.20201102git05e90ee.fc34 checkpolicy-3.1-4.fc34 policycoreutils-3.1-5.fc34 libsemanage-3.1-4.fc34 libselinux-3.1-4.fc34 libsepol-3.1-4.fc34 There are few other components which needs to be rebuild: parted - for some reason it links to libsepol even though I haven't found a code which would use it. I've proposed patch upstream https://alioth-lists.debian.net/pipermail/parted-devel/2020-November/005500.html shadow-utils - https://src.fedoraproject.org/rpms/shadow-utils/pull-request/6 sssd - https://src.fedoraproject.org/rpms/sssd/pull-request/7 As none of packages which require either libsepol or libsemanage use dropped symbols and in order not to break build root during soname bumps I've added temporary subpackages with original library versions - libsepol-compat with libsepol.so.1 and libsemanage-compat with libsemanage.so.1. These subpackage will be dropped as soon as everything is rebuilt in Rawhide. I've sucessfuly built all packages also in my COPR repository https://copr.fedorainfracloud.org/coprs/plautrba/selinux-fedora/builds/ If there's no objection I'd like to merge the side tag to rawhide as soon as possible. Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
