As I've not really had time to work on Fedora for some time, I'm orphaning
all of my packages. This includes:
All but the eclipse package are Java libraries that are dependencies of
For the moment, I've left myself as co-maintainer of my other packages.
I hope to have time to come back to package management in the future.
All the best,
Mary Ellen Foster
Mary Ellen Foster -- http://maryellenfoster.co.uk/
With the new upstream release python-ntplib-0.3.3 the license was
changed from LGPLv2+ to the MIT license. The only package that requires
python-ntplib seems to be anaconda which is not affected by the change,
but I'm rather letting you guys know.
Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic
I can see that RCs of development version of kernel are being built in rawhide.
Which is really great to test new stuff. But I would be pretty scared to run RC
Would it make sense then to also build latest stable releases?
E.g. now it would be 4.1.3. All I can see in koji is this 4.1.3 build  for f22.
During the review of cppformat, it was pointed out that it contained a font
that should be removed because it's packaged with Fedora (
https://bugzilla.redhat.com/show_bug.cgi?id=1216279#c3 ). While working on
resolving this, I was looking into what package provided this font so I
could add the appropriate Requires to get the font and noticed that quite a
few packages also include this font:
yum provides "*/glyphicons-halflings-regular.ttf"
Is this ok? And if not, then is there some way that a set of fedora-review
style audits could be run on existing packages to verify that these sorts
of things didn't accidentally slip through the original review or were
introduced in an update without being noticed?
- define the minimal install (continued)
- define the docker base image (continued)
- minimal disk image for importing into libvirt (continued)
- generic installer? (continued)
- Open Floor
Please add items by replying to this mail.