Learn more about these different git repos.
Other Git URLs
We are about to rebase Boost in Rawhide, in accordance with the approved feature https://fedoraproject.org/wiki/Features/F18Boost150 . Since changes in Boost libraries have a large impact, we would like to request a dedicated koji tag where we could do the rebuilds that the rebase entails. It is expected that this will take place in every Fedora release.
To quantify the "large impact": there's about 100 packages that need to be rebuilt, otherwise they won't run after the soname bump implied by the rebase.
Replying to [ticket:5230 pmachata]:
It is expected that this will take place in every Fedora release.
what exactly does this statement mean?
side tags make things harder for secondary arches. I strongly prefer that side tags not be used. what is the expected turn around time for rebuilding effected packages?
Replying to [comment:2 ausil]:
Replying to [ticket:5230 pmachata]: It is expected that this will take place in every Fedora release. what exactly does this statement mean?
We rebase boost in every release. This always implies breaking many rawhide packages for several weeks.
I expect that most rebuilds would be resolved within about two weeks, then it would be possible to merge the tag. Well, actually this only holds if I can make the rebuilds myself, which I don't think is possible. If it's left for respective maintainers to do, then it's those "several weeks" that I mentioned.
We want to use side tag to address complaints about the semiannual rawhide breakage. If there is a better way to achieve the same without making life difficult for maintainers of secondary arches, then I'll be happy to do it that way instead.
Any progress on this, please? If you don't think this is necessary for boost updates, or that making extra side tag for this is not worth it, then that's ok as well, but it needs to be stated.
sorry for the delay, I personally do not think it needs a side tag, but i have created one f18-boost, if you run:
{{{fedpkg build --target=f18-boost}}}
you will be able to do your builds. do keep in mind that there is a f18 mass rebuild starting tomorrow. please let us know when your work is completed and we can merge it back.
Ok, thank you.
I would like to merge f18-boost now. Thank you.
{{{ Checking 27 builds... Tagging adobe-source-libraries-1.0.43-13.fc18 into f18 Tagging akonadi-1.8.0-2.fc18 into f18 Tagging barry-0.18.3-3.fc18 into f18 Tagging bastet-0.43-17.fc18 into f18 Tagging boost-1.50.0-1.fc18 into f18 Tagging calligra-2.5.0-2.fc18 into f18 Tagging calligra-l10n-2.5.0-2.fc18 into f18 Tagging clementine-1.0.1-12.fc18 into f18 Tagging digikam-2.8.0-1.fc18 into f18 Tagging esteid-browser-plugin-1.3.3-3.fc18 into f18 Tagging gappa-0.16.1-2.fc18 into f18 Tagging gwenview-4.9.0-2.fc18 into f18 Tagging kde-runtime-4.9.0-4.fc18 into f18 Tagging kde-workspace-4.9.0-3.fc18 into f18 Tagging kdepimlibs-4.9.0-2.fc18 into f18 Tagging libcmis-0.2.3-3.fc18 into f18 Tagging libmspub-0.0.2-3.fc18 into f18 Tagging libvisio-0.0.19-2.fc18 into f18 Tagging libwps-0.2.7-3.fc18 into f18 Tagging mbox2eml-0.1.1-15.fc18 into f18 Tagging mdds-0.6.0-2.fc18 into f18 Tagging permlib-0.2.6-4.fc18 into f18 Tagging pingus-0.7.6-4.fc18 into f18 Tagging strigi-0.7.7-7.20120626.fc18 into f18 Tagging undertaker-1.2-7.fc18 into f18 Tagging vdrift-20111022-6.fc18 into f18 Tagging wesnoth-1.10.3-5.fc18 into f18 Tagging 27 builds. }}}
merged in
Metadata Update from @pmachata: - Issue set to the milestone: Fedora 18 Alpha
Login to comment on this ticket.