I am the developer of JC and Jello. JC is currently packaged for Fedora and I would like to see if anyone would consider packaging Jello as well? Or would you know someone interested in doing so?
I created a src rpm spec similar to what we used for JC, so it should be pretty straightforward. (This was done a while back - the latest jello version is now 1.5.2)
Spec URL: https://jello-packages.s3.us-west-1.amazonaws.com/fedora/jello.spec
Description: Query JSON at the command line with Python syntax
Fedora Account System Username: kellyjonbrazil(a)gmail.com
today, I've looked up packages in rawhide providing python3dist(...) = 0 and I
opened bugzillas for them:
While version 0 (or equal versions like 0.0 or 0.0.0) is probably technically
valid, it most certainly indicates a packaging error (most likely but not
necessarily a downstream packaging error).
Should we prevent this error from happening by explicitly erroring (and failing
the build) when it happens? I think it would make the dependency generators
In an unlikely scenario when packagers actually want to package version 0, they
can reach out and we can allow it via some configuration (but [YAGNI], so I
don't want to clutter the generator with yet another option right away).
just letting you know that as of today, I can finally see
pyproject-rpm-macros-1.0.0~rc1-1.el9.noarch in the EPEL 9 Koji buildroot.
That means, the %pyproject_* macros should now have identical features and
behavior across Fedora and EPEL 9.