Fedora Account System
Red Hat Associate
Red Hat Customer
Please branch and build reuse in epel10 It currently needs python-binaryornot and python-license-expression to build. If you do not wish to maintain reuse in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS tdawson); please add me through https://src.fedoraproject.org/rpms/reuse/adduser
I have opened bugzillas for the two missing packages.
I'm willing to branch and build once the deps are sorted out. I'll try to keep an eye on them.
python-binaryornot and python-license-expression are now in the epel10 an epel10.0 buildroot. I tried building reuse again, and it builds, but only version reuse-5.0.2-3 reuse-5.0.2-2 and reuse-5.0.2-4 do not build for various dependency problems.
Hi Jan, Any progress on this? I need reuse to build a couple of KDE apps in epel10. For me the most important of those is neochat, a matrix client. If you think it might take you a while to do it, I'm still willing to be a co-maintainer for the epel packages. If that is the case, please add me (FAS tdawson) through https://src.fedoraproject.org/rpms/reuse/adduser
Testing an EPEL10 mock build from the current rawhide branch, Error: Problem: nothing provides requested ((python3dist(python-debian) < 0.1.45 or python3dist(python-debian) > 0.1.45) with (python3dist(python-debian) < 0.1.46 or python3dist(python-debian) > 0.1.46) with (python3dist(python-debian) < 0.1.47 or python3dist(python-debian) > 0.1.47) with python3dist(python-debian) >= 0.1.34)
Correct, the current rawhide branch added another dependency, python-debian to fix %check in rawhide. But from what I can see, the testing works fine on epel10 without that change. That's why I said earlier that version reuse-5.0.2-3 builds properly on epel10.
While you are waiting for Jan, I think I can help unblock your packages. None of them appears to actually need reuse at build time, only (presumably) for upstream CI: - https://src.fedoraproject.org/rpms/arianna/pull-request/2 - https://src.fedoraproject.org/rpms/neochat/pull-request/1 - https://src.fedoraproject.org/rpms/optiimage/pull-request/1 - https://src.fedoraproject.org/rpms/plasma-dialer/pull-request/3 After those four PR’s, reuse should be a leaf package.
Hi, sorry for the lack of updates, I forgot to write something down. I've tried a week or two back, got held on something and got carried away working on something else. I'll take a look on the python-debian dependency and to see if it is actually needed for us.
(In reply to Troy Dawson from comment #6) > Correct, the current rawhide branch added another dependency, python-debian > to fix %check in rawhide. > But from what I can see, the testing works fine on epel10 without that > change. > That's why I said earlier that version reuse-5.0.2-3 builds properly on > epel10. This does not seem to be correct – I was going through the older versions in koji, and all of them have the python-debian dependency there (see https://koji.fedoraproject.org/koji/rpminfo?rpmID=42263808 for the 5.0.2-3 version that you mention). I tried to rebuild that locally for epel10 and got the same error even for the 4.x version; did not yet try anything older. The python-debian dependency seems to be there for a long time; it is used to handle .reuse/dep5 files. It looks to me that we have another branch-and-build request on our hands.
Well, that is a bummer. After Ben's changes to the various KDE apps that depended on reuse, it looks like I no longer need the package in epel10. I am going to withdraw my request for reuse. I appreciate the work you've done of testing builds and looking into the code. And if you still want to put it in when python-debian makes it into epel10, that would be great. But I don't want to track down another python dependency for a package I no longer need. Thanks again for all the work you've done.
OK; since I also do not have the spare capacity to try helping maintain python-debian in EPEL, I'm also deferring this to an indeterminate future when all dependencies will be everywhere and we can just branch and build. :-)