releng

#9455 Block/Retire boost169 on Fedora 32
Closed: Can't Fix by mohanboddu. Opened by denisarnaud.

Closed: Can't Fix
Reopen Issue

  • boost169 has been inadvertently released on Fedora 32, whereas it was aimed to be only a compatibility on EPEL distributions. It now blocks, on Fedora 32, packages such as MKVToolnix. See https://bugzilla.redhat.com/show_bug.cgi?id=1835079 for more details.

  • When do you need this? (2020/05/15)

  • When is this no longer needed or useful? End of Life for F32

  • If we cannot complete your request, what is the impact? Some packages like MKVToolnix may be blocked on Fedora 32

Link to the RPM source repository: https://src.fedoraproject.org/rpms/boost169

@denisarnaud Sorry, but we cannot do this as F32 is already out. We allow retiring on development releases only that is branched or rawhide. Once the release is out, we cannot retire a package on it.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

In this case, create an update to boost package that obsoletes boost169 package. That should solve the issue.

In this case, create an update to boost package that obsoletes boost169 package. That should solve the issue.

Thanks for the suggestion. @jwakely has just patched Boost. We could add an obsolete clause on F32 for Boost, you're right. Jon, would you be so kind as to add it?

Yes, I'll do that tomorrow morning. Does the obsolete tag need to be on rawhide too, or just F32?

Ugh ... do I need to add it for every one of the 30+ subpackages? So boost-devel obsoletes boost169-devel and boost-atomic obsoletes boost169-atomic etc? Simply adding it to the boost package doesn't help if somebody has the various subpackages installed individually.

As I wrote on fedora-devel, I think updating fedora-obsolete-packages should fix the problem without touching boost.
  • boost-1.69.0-18.fc32, obsoleting boost169 on Fedora 32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8770cfebcd

For reference, discussion on the Fedora devel mailing list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JWSYT4B2FNRTHGJ5VWP37JNJBEYS3OFP/

As I wrote on fedora-devel, I think updating fedora-obsolete-packages should fix the problem without touching boost.

I suppose now that boost has been spammed with all the obsolete tags there's no point doing anything in fedora-obsolete-packages. Oh well.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.