Please branch and add meanwhile to EPEL 9. A scratch build worked just fine, so no other changes should be required. This package is needed to build Pidgin and clear bug 2044092. https://koji.fedoraproject.org/koji/taskinfo?taskID=88706548
Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/45337 In the meanwhile (pun intended) I've updated meanwhile to the latest release on github and cleaned up the SPEC file: https://src.fedoraproject.org/rpms/meanwhile/c/91088ce1969bd92981362196168d5f3e85bd65d6?branch=rawhide If you can, it would be nice to know if this update works: https://bodhi.fedoraproject.org/updates/?packages=meanwhile I've not been using meanwhile for many years (it's Lotus still a thing?), would be nice to have additional maintainers for the package. If you want I can add you as a maintainer.
Hi Simone, Since I've never written code against this lib/package directly, I wouldn't know how to test it, beyond running `make test` or `make check` from within the build directory. I haven't looked at the spec file, but I assume that's already happening, and passing when it's built on Koji? Personally, I'm just trying to get Pidgin working. There were a few missing dependencies, so once all of them are available, I can presumably test Pidgin, and report back with a new bug report if there's a problem? L~ P.S. This could be a silly question, but I don't see the EL9 branch at https://src.fedoraproject.org/rpms/meanwhile ... is there a lag?
(In reply to Ladar Levison from comment #2) > Since I've never written code against this lib/package directly, I wouldn't > know how to test it, beyond running `make test` or `make check` from within > the build directory. I haven't looked at the spec file, but I assume that's > already happening, and passing when it's built on Koji? No I meant if you could actually test the Lotus/Sametime integration, but it seems not. > > Personally, I'm just trying to get Pidgin working. There were a few missing > dependencies, so once all of them are available, I can presumably test > Pidgin, and report back with a new bug report if there's a problem? Yes sure, this of course is fine. > P.S. This could be a silly question, but I don't see the EL9 branch at > https://src.fedoraproject.org/rpms/meanwhile ... is there a lag? Look here, once this is approved, the branch is created and I will try to build it (tonight or tomorrow morning at maximum): (In reply to Simone Caronni from comment #1) > Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/45337
(In reply to Simone Caronni from comment #3) > Look here, once this is approved, the branch is created and I will try to > build it (tonight or tomorrow morning at maximum): > > (In reply to Simone Caronni from comment #1) > > Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/45337 Ah. I saw that, but I didn't realize the branch needed approval. I thought the package maintainer could do it unilaterally. I'm still learning.
FEDORA-EPEL-2022-cb34d33dd8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cb34d33dd8
FEDORA-EPEL-2022-cb34d33dd8 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cb34d33dd8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-cb34d33dd8 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.