#9950 F34 Change: Boost 1.75 upgrade
Closed: Fixed 4 months ago by kevin. Opened 5 months ago by mohanboddu.

CC @trodgers


@trodgers What is the status on this change as mass rebuild for f34 is scheduled for this Wed, Jan 20 2021 and I am still seeing boost-1.73 in rawhide as of now.

Metadata Update from @mohanboddu:
- Issue tagged with: change-ack, changes, f34, mass rebuild

5 months ago

@trodgers What is the status on this change as mass rebuild for f34 is scheduled for this Wed, Jan 20 2021 and I am still seeing boost-1.73 in rawhide as of now.

GCC regressions have prevented boost from successfully building. Hopefully -

https://koji.fedoraproject.org/koji/taskinfo?taskID=60115688

Makes the magic happen

Package has been pushed.

@trodgers FYI, I untagged the boost build and I will tag it back into f34 tag just before starting the mass rebuild to avoid any soname bump issues.

Untagged eln build as well, I will tag it back into eln before starting mass rebuild

@trodgers FYI, I untagged the boost build and I will tag it back into f34 tag just before starting the mass rebuild to avoid any soname bump issues.

This is going to break a lot of packages during the mass rebuild if you tag it back in like this. I'd say the dependency issues need to be sorted out before so it can be safely tagged into rawhide.

There are two approaches how to bump a soname in Fedora:

1) tag the new boost in a side tag, then rebuild everything else in dependency order (this needs a provenpackager to do the work).
or
2) create a compat packages with the old soname, put both in rawhide, and rebuild everything in a-z order.

If you just tag it into rawhide without doing either one of the above it is just going to wreak havoc in the mass rebuild due to packages requiring the old version, but only new version being available in the build roots. Anything that transitively build requires something that links against old boost AND build requires boost-devel is going to fail in the mass rebuild, and I'd estimate in the order of 1000 packages fall in this category (10% of the mass rebuild set).

1) tag the new boost in a side tag, then rebuild everything else in dependency order (this needs a provenpackager to do the work).

That's how I've done it in the past, but there wasn't time to do it for this upgrade. The rebuilds can take a week if all goes smoothly. But if the mass rebuild is going to be delayed, we can start those rebuilds in a side tag today.

If that's what you want, please say so ASAP. We'll create a ticket to request the side tag, and we'll want the new boost build tagged into that side tag (so we can start building the dependent packages right away, without building boost itself again).

I would say yes please. Even if you get half way through before the mass rebuild and merge it back into rawhide it's going to be a lot better than not rebuilding anything.

Building into the side tag now ...

Boost and affected packages are on rawhide now. I guess this can be closed as complete.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Login to comment on this ticket.

Metadata