Description of problem: Hello. I tried to update gnome-passwordsafe and seems like now it requires "libhandy-1". 0.0.13 should with API ver 1? Please help me with this issue. Here is upstream MR: https://source.puri.sm/Librem5/libhandy/merge_requests/248 Version-Release number of selected component (if applicable): libhandy-0.0.13-2.fc32 How reproducible: Try to build new https://gitlab.gnome.org/World/PasswordSafe/-/tags/3.99.2 Actual results: meson.build:20:0: ERROR: Dependency "libhandy-1" not found, tried pkgconfig Expected results: Successful build for F32+
@kalev - Perhaps libhandy1 is in order ? Provisional.. bug 1803934
We need libhandy 0.0.13 for F30, F31 too... Thanks
(In reply to David Vásquez from comment #2) > We need libhandy 0.0.13 for F30, F31 too... Thanks Sure, I think it should be fine to build 0.0.13 for F31. Just curious -- why do you need it?
As for bumping the API to "libhandy-1", I'm going to wait with this until it's properly released and GNOME actually starts using it. I think packaging a snapshot is a bit premature at this point. If you need the new API already now, please just bundle the version of libhandy that you need in your program. It should be easy as libhandy supports bundling nicely.
(In reply to Kalev Lember from comment #3) > (In reply to David Vásquez from comment #2) > > We need libhandy 0.0.13 for F30, F31 too... Thanks > > Just curious -- why do you need it? In my case i always need a fresh libhandy for 'gfeeds' [1] where developer constantly using latest libhandy features. Also for Fractal which i building in Copr, but for Copr builds this is not really issue. [1] https://gitlab.gnome.org/World/gfeeds
OK, here you go: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8f8b32ccd4
(In reply to Kalev Lember from comment #3) > (In reply to David Vásquez from comment #2) > > We need libhandy 0.0.13 for F30, F31 too... Thanks > > Sure, I think it should be fine to build 0.0.13 for F31. Just curious -- why > do you need it? Hi, thanks. First, avoiding multiple versions, it help to reduces efforts. Other, I need it for build some rpms and requires current versions.
(In reply to Kalev Lember from comment #4) > If you need the new API already now, please just bundle the version of > libhandy that you need in your program. It should be easy as libhandy > supports bundling nicely. Hi. Kalev, can you help a little bit bit with this? Maybe there is some SPEC example how to bundle properly it for **Fedora**? There is new app appeared which requires new libhandy-1. I bundled it, but in very ugly way which could introduce problem in future. Didn't pushed to repos though.
libhandy 0.80.0 was released a few days ago, which bumps API version to 1.0.0. Some of my packages are starting to depend on libhandy-1 upstream, so it would be great if we could get the ball rolling for libhandy0 compat package / libhandy update to 0.80.
Fabio: Please see https://bugzilla.redhat.com/show_bug.cgi?id=1803934 for a parallel installable libhandy1 package review request. If you hadn't scared away the contributor this issue would be long resolved.
I have prepared a PR for updating the package to 0.80.0 and a separate .spec for libhandy0: https://src.fedoraproject.org/rpms/libhandy/pull-request/1
Thanks. Can you do it the other way around (as in introduce libhandy1)? This would make it easier to build new libhandy1 for F31 and F32 (which I'm sure Artem needs) without possibly causing problems for existing packages that link with libhandy.
I've imported and built libhandy1: https://koji.fedoraproject.org/koji/buildinfo?buildID=1517284 I also added @kalev as admin and @gnome-sig as commiters to the new package. Newpackage updates for f32 and f31 are on their way.
FEDORA-2020-e626b36c91 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e626b36c91
FEDORA-2020-78d91bc814 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-78d91bc814
Excellent! Thanks, Fabio.
FEDORA-2020-78d91bc814 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-78d91bc814 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-78d91bc814 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-e626b36c91 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-e626b36c91 \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e626b36c91 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-78d91bc814 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-e626b36c91 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.