orphaning python-dmidecode
by Dan Horák
Hi all,
I'm orphaning python-dmidecode, I have inherited it after a member of
our team left and have no interest or use case for it. I vaguely
remember there was a project who relied on python-dmidecode, so if it's
still true, then they should step up. Repoquery returns nothing for
"--whatrequires python3-dmidecode" though.
Dan
3 years, 6 months
Java reviews (with swaps)
by Jerry James
Hi all,
I would like to ask for some input from those of you with Java
packaging experience. The jsonp package has been orphaned, but the
antlr4-project package (which I maintain) still needs it. Since jsonp
has transitioned to the eclipse-ee4j project, I thought it best to let
the current jsonp package die, and replace it with a jakarta-jsonp
package.
The parent POM for jakarta-jsonp, org.eclipse.ee4j:project:pom:, has
not been packaged for Fedora. Other packages with that parent have
simply added %pom_remove_parent to their spec files. With
jakarta-jsonp, though, I'm running into some difficulties doing so.
The parent POM has default version numbers for various plugins. Those
version numbers are not duplicated in the jakarta-jsonp POM. This
leads to maven telling me that the missing version numbers invoke
deprecated functionality and that the project will stop building with
some future version of maven. I could:
(1) add %pom_remove_parent and ignore maven until the project actually breaks;
(2) add %pom_remove_parent and then do some XPath gymnastics to add
the missing version numbers into the jakarta-jsonp POM; or
(3) package the parent POM and stop worrying.
I've chosen to do (3). Tell me if you think this is wrong.
As for jakarta-jsonp itself, the latest version is 2.0.0, but it fails
to build because it needs jakarta-ws-rs 3.x and jakarta-annotations
2.x. We have versions 2.1.6 and 1.3.5, respectively, in Rawhide right
now. Therefore, I have gone with version 1.1.6 of jakarta-jsonp for
now.
Here's the next bit of input I need: why does "%pom_remove_plugin -r
org.apache.maven.plugins:maven-javadoc-plugin" only remove the plugin
from the top-level POM, in spite of the -r flag? I have to manually
remove it from the subdirectory POMs.
Here are the actual review requests. I'm happy to swap reviews.
https://bugzilla.redhat.com/show_bug.cgi?id=1898311 (ee4j-project)
https://bugzilla.redhat.com/show_bug.cgi?id=1898312 (jakarta-jsonp)
Thanks!
--
Jerry James
http://www.jamezone.org/
3 years, 6 months
New ansible module copr
by Silvie Chlupova
Hello!
we recently merged [1] a development version of ansible module for
enabling copr repositories. At this moment we would like to get your
early feedback - before we submit this to Galaxy, or propose this as
ansible core library.
Quick howto. Either copy the copr.py file into
`/usr/share/ansible/plugins/modules/copr.py` or clone the repository
and create a symlink.
The usage is as easy as:
- name: enable foo project from Fedora Copr
copr: name=jdoe/foo
See the README.txt for more info. Any comments or ideas are welcome.
[1] https://pagure.io/copr/copr/blob/master/f/ansible
Copr Team
3 years, 6 months
FESCo meeting today is cancelled 🦃
by Miro Hrončok
FESCo meeting today is cancelled. There is no agenda and Thanksgiving in the US
is tomorrow.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 6 months
