Postings by Ben Rosser

Unretiring rtv


I'd like to unretire the 'rtv' package in accordance with the
documented un-retirement policy.

<a href="" title=""></a>

The package seems to have been retired because it could not build with
Python 3.7.

Organizing a "packager experience" objective and working group


We had a recent discussion on this list last month about (among other
things) the current state of Pagure as a replacement for pkgdb [1].

I mentioned in that discussion that there are various issues which
have arisen from the deprecation of pkgdb that have made the packager
workflow ever so slightly worse.

Approved packages that never get imported?


What is the right thing to do when a package's review is approved, but
the package never gets imported into the distribution because the
packager subsequently becomes non-responsive?

Is the non-responsive maintainer policy appropriate, or should the
review be resubmitted entirely?

I've seen this in a few places and not been entirely sure what to do,
as this isn't entirely spelled out in our policies.

Review swaps


I have a handful of packages in the review queue that I'd be willing
to exchange reviews for.

License change in quasselc


As per policy [1] I'm notifying devel@ that the license of quasselc, a
C library implementing the quassel protocol, has changed from GPL v3+
to LGPL v3 [2].

This should only affect the GPLv3+-licensed quassel-irssi (an irssi
plugin that uses quasselc), which is by the same upstream author and
still compatible with the new license, as quassel-irssi is the only
Fedora package depending on quasselc at this time.

Ben Rosser

[1] <a href="" title=""></a>

[2] <a href="" title=""></a>

Review swaps

Anyone interested in review swaps? I have four smallish packages in the
queue, would be happy to take other smallish packages in exchange:

* quassel-irssi: <a href="" title=""></a>

* golang-github-knieriem-markdown:
<a href="" title=""></a>

* nodejs-int64-buffer: <a href="" title=""></a>

* nodejs-qtdatastream: <a href="" title=""></a>
(depends on nodejs-int64-buffer)

Ben Rosser

Review swap for spasm-ng

Is anyone interested in a review swap? I think this is a relatively simple
package, so I'd be willing to take something small in exchange.

spasm-ng: A z80 assembler with extra features for TI calculators
<a href="" title=""></a>

Ben Rosser

Review swap?


Is anyone interested in a review swap for cmap-resources (
<a href="" title=""></a>)?

Unretire python-sockjs-tornado

Hello devel@,

I'd like to unretire python-sockjs-tornado. As far as I can tell, it was
only retired because nobody picked it up when it was orphaned; the project
is still clearly active upstream [1].

I found myself contributing to an ArchiveTeam project [2] a few weeks ago
and as a result wanted to package their toolkit, python-seesaw [3], for
Fedora. Seesaw depends on sockjs-tornado.

Adobe CMap resources license change

Hi everyone,

I am not certain if any packages other than my python-pdfminer are
currently using my packages of the Adobe CMap resources (
<a href="" title=""></a>), but--

The package versions have changed when the upstream repository was moved
from Sourceforge to github earlier this year.

Bundled/embedded data in a package

So I've had a review ticket open on bugzilla for a while now for this
<a href="" title=""></a>

The software, pdfminer, bundles Adobe cmap data to process Chinese,
Japanese, and Korean languages in a pdf file. However, the question is:
does this violate the general prohibition against bundling libraries?

Submitting packages while awaiting sponsorship

Hello all,

I'm still looking for someone to review my Python package (
<a href="" title=""></a> ), and then hopefully
sponsor me as a packager- if anyone would be interested in doing either
that would be greatly appreciated, and I'd try to review one of your
packages in turn (and I would be able to do so formally after sponsorship).

But, the actual point of this message is simply to ask: is it okay for me
to submit additional packages for review while still awaiting sponsorship?
I would assume it is, but I just wanted to make sure before I actually do


Replacing grubby with grub2-mkconfig in kernel install process

In Fedora 17, when you install grub2 and generate a fresh config file, that
config is produced by grub2-mkconfig. However, when you install a kernel
update, the kernel's entry is added to the grub2 boot menu by grubby.

This produces messy grub boot menus. The entries added by grubby read
something like "Fedora (%kernel_version)".

Review request

Hey all,

I'm still looking for someone to review my first package, PDFMiner:
<a href="" title=""></a>

As I am looking for a sponser, I'm afraid I can't formally review any of
your packages in return, but I'd be glad to do some unofficial reviews and
help fix any problems I can notice.

Self introduction

Hello all,

I've been sitting silently in this mailing list for the past few weeks, but
just this afternoon submitted my first package review request for pdfminer,
a Python library for extracting plaintext, HTML, and images from a pdf
file: <a href="" title=""></a>

I learned the basics of writing a spec file a while back, but nothing
really ever came of this as I couldn't find any software I was actually
interested in packaging.