On Thu, Aug 19, 2021 at 1:41 PM Björn 'besser82' Esser <besser82@xxxxxxxxxxxxxxxxx> wrote: > Am Donnerstag, dem 19.08.2021 um 12:49 +0200 schrieb Björn 'besser82' > Esser: > > Am Donnerstag, dem 19.08.2021 um 12:43 +0200 schrieb Ondrej Mosnacek: > > > On Thu, Aug 19, 2021 at 12:34 PM Björn 'besser82' Esser > > > <besser82@xxxxxxxxxxxxxxxxx> wrote: > > > > Am Mittwoch, dem 18.08.2021 um 10:45 +0200 schrieb Ondrej > > > > Mosnacek: > > > > > Hello, > > > > > > > > > > I would like to update quazip to version 1.1 in rawhide (i.e. > > > > > future > > > > > F36) [1][2], but since this update will change sonames > > > > > (libquazip.so > > > > > -> libquazip1-qt4.so and libquazip5.so -> libquazip1-qt5.so), I > > > > > will > > > > > need the dependent packages' maintainers (in Bcc) to rebuild > > > > > them in > > > > > a > > > > > side tag (I'm not a provenpackager, so I can't do that myself, > > > > > although Nicolas (@kwizart) offered to help if needed). > > > > > > > > > > Affected packages: > > > > > bletchmame > > > > > ckb-next > > > > > fritzing > > > > > gimagereader > > > > > GLC_lib > > > > > keepassxc > > > > > krita > > > > > nomacs > > > > > qcad > > > > > qmapshack > > > > > texstudio > > > > > > > > > > Even though the library/include/CMake paths changed, there seem > > > > > to > > > > > be > > > > > no breaking API changes and I added compat symlinks/files to the > > > > > -devel packages so that all packages using the old paths will > > > > > still > > > > > build (and link against the new soname) without modification (I > > > > > tested > > > > > this in COPR, see [3]). So a simple release bump + rebuild into > > > > > the > > > > > side tag should be enough. > > > > > > > > > > After the side tag is merged, I will try to gradually submit PRs > > > > > to > > > > > migrate the dependent packages to use the new paths (either via > > > > > pkgconfig or the CMake modules). Once all dependent packages are > > > > > migrated, it will be possible to remove the compat hacks from - > > > > > devel > > > > > packages (though we might want to keep them longer for user > > > > > convenience). > > > > > > > > > > Current plan: > > > > > 1. I request a side tag, merge [2], and build the new quazip in > > > > > the > > > > > side tag. > > > > > 2. I announce the side-tag in this thread and ask for dependent > > > > > packages to be rebuilt in it. > > > > > 3. Once all the packages are successfully built in the side tag, > > > > > I > > > > > get > > > > > the side tag merged. > > > > > > > > > > If there are no objections, I will execute steps 1 and 2 > > > > > sometime > > > > > next > > > > > week (or sooner if I get a positive acknowledgement for all > > > > > packages). > > > > > Maintainers, please let me know if you are ready to do the side- > > > > > tag > > > > > rebuild, or if you'd prefer to defer this a bit (for example due > > > > > to > > > > > a > > > > > conflict with other group rebuild). > > > > > > > > > > Thanks! > > > > > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1895170 > > > > > [2] https://src.fedoraproject.org/rpms/quazip/pull-request/2 > > > > > [3] https://copr.fedorainfracloud.org/coprs/omos/quazip/monitor/ > > > > > > > > > > > > As everything seems prepared readily, and there a currently no > > > > conflicting rebuilds going on, I'm going to do a rebuild of all > > > > packages > > > > in sidetag: f36-build-side-44792 > > > > > > > > I'll give short notice, as soon as the sidetag is merged with > > > > rawhide. > > > > > > OK, I was going to kick it off in the evening [CEST], but I'm > > > perfectly fine with you doing it all in one go, since you made sure > > > there are no apparent conflicts. Thank you! > > > > > > You're welcome! > > > > Chain-build is running in sidetag: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=74131380 > > > > Cheers > > Björn > > > Things went fine so far, except for nomacs to fails, because vtk is > installable on Rawhide currently. * _not_ installable :) > > Are there any plans to bring this into F35 as well? vtk is installable > there, FYI. I don't have such plans at this point. AFAIK nothing strictly depends on the new quazip version, it's just a matter of keeping up to date with upstream. So I don't think it would be worth the effort to repeat the process in F35. -- Ondrej Mosnacek Software Engineer, Linux Security - SELinux kernel Red Hat, Inc. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
