Postings by Ankur Sinha

Trying to contact package maintainer: Filip Szymański


Would anyone know how to contact Filip? There are a few pending bugs
that they've not replied to yet[1].

Using fedora-active-user: unable to find fedora_cert


Could someone please clarify how fedora-active-user[1] is to be used? It
is unable to find the fedora_cert python bits, and fedora-packager no
longer seems to include this either[2].

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

Science/research get together at Flock

Hello everyone,

If you work in or are interested in science/research and are planning to
attend Flock, please comment on this ticket to let us know:

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

If there are enough of us, we'll try to put together a meetup or a
hackathon to discuss how we can better support science/research as
Fedora community members.

C++ help needed fixing VXL on 32 bit architectures

Hi everyone,

After spending quite a bit of time fixing VXL to build, I've now run
into errors with it building on 32 bit arches.

Unfortunately, I don't foresee myself having enough cycles in the near
future to debug the C++ bits to see what's happening here, and while I
have filed a ticket upstream, they seem to be even busier than us (all
issues seem to get a "A PR would be welcome" response)

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

Any chance any C++ ninjas here would have some time to look into this
please? A PR fixing the issue upstream would be absolutely fantastic.

VXL 2.0.2 coming to rawhide (and F30)


I am currently working on updating VXL to the latest version. It does
not currently build in rawhide/f30, and that also causes other packages
that depend on it to FTBFS: InsightToolKit etc.

Upstream does not version their shared objects, so a soname bump may not
be part of the upgrade, but I will check and rebuild packages that I
have access to or request the respective maintainers to do so.

doxygen crash on aarch64


For one of my packages, doxygen is crashing on aarch64 (and not on any
other arch).

Using docs related fields in Bugzilla


While going through the NeuroFedora package reviews, I was wondering if
it were OK for us to use the documentation related fields in Bugzilla to
mark that we need to update our documentation at
<a href="" title=""></a>. Is it OK if we:

- set a docs contact
- set doc type
- set doc text?

Looking to give these packages new maintainers


I'm trying to focus my rather limited free time on neurofedora[1].
So, I'd like to pass on a number of packages that I no longer use to
maintainers who would give them the required attention.

A few of them were inactive upstream so I have orphaned them. A few of
the rest already have co-maintainers, but more are welcome. I intend to
remove myself from them at the end of the month (31st).

CMake help: "install TARGETS given no LIBRARY DESTINATION for shared library target"


Could I have some help with CMake please?

I have a WIP spec here[1] that won't build.

The "see-also" field in bugzilla


The bugzilla upgrade removed the "see-also" field which I found most
useful. Would anyone have any tips on reproducing its functionality in
the current version?

A bug requesting that it be brought back has been closed as WONTFIX:
<a href="" title=""></a>

I've commented there also, but I'd like to learn how others go about it
without "see-also".

NeuroFedora review swaps


Happy new year, everyone!

I've got two simple python packages that need review. Would anyone like
to swap reviews, please?

- <a href="" title=""></a> python-tvb-gdist
- <a href="" title=""></a> python-tvb-data

They are both easy enough for prospective package maintainers to review
unofficially also.

Moving to python-progressbar2


We're thinking of moving to python-progressbar2[1] in Fedora. It is a
better maintained, more featured implementation of the progressbar
module in Python. Since progressbar[2] and progressbar2 both provide the
same module, we can only include one. We're also dropping the py2 sub
package as is required in rawhide.

From what I can see, only 3 packages use it in Fedora:

- euca2ools
- python-libtaskotron
- python-bitmath

Their owners are cc'd.

Packaging FOSS that requires MATLab at runtime


While packaging software for NeuroFedora[1], we've got quite a few
MATLab toolboxes that are commonly used in scientific research on our
list. SPM[2] is a good example. It is *widely* used in NeuroImaging
research. While it is somewhat compatible with Octave, upstream does not
support it[3]. Since correctness is paramount with such toolboxes, at
present, they must be used with MATLab.

What do we think of including such toolboxes in Fedora?

NeuroFedora review swaps: python-fslpy, python-fsleyes-widgets


Would anyone like to swap reviews please? I've got two more python
packages that are now ready for review:

- python-fslpy: <a href="" title=""></a>
- python-fsleyes-widgets: <a href="" title=""></a>

One can follow the NeuroFedora reviews here:
<a href="" title=""></a>
and here:
<a href=";tags=S%3A+Needs+review" title=";tags=S%3A+Needs+review">;tags=S%3A+Nee...</a>

This is the list of packages in that still need packaging:
<a href=";tags=S%3A+Needs+packaging" title=";tags=S%3A+Needs+packaging">;tags=S%3A+Nee...</a>

openjfx is looking for a maintainer


I have not been able to find an e-mail announcing the orphaning of
openjfx, so I'm doing it in the hope of finding it a new maintainer.

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

Openjfx has been orphaned and needs a maintainer. Tools such as JabRef
depend on it and are currently unusable in Fedora. Would someone
proficient in Java please consider taking it up?

Review swap: python-libNeuroML


Would someone like to swap reviews please? I have a simple python
package that needs reviewing:

python-libNeuroML: <a href="" title=""></a>

Should we also list "Trivial" review tickets on Easyfix?


The EasyFix page[1] is a list of various issues/bugs that are considered
simple enough for new contributors to work with. Currently, from
bugzilla, tickets that use the "EasyFix" key word are listed here.

The package review process suggests the use of "Trivial" on the
Whiteboard for simpler tickets to aid new-comers. So, they seem to serve
the same purpose as EasyFix. Would it be OK to also list these tickets
on the EasyFix page?

I've already opened a PR here for this to done[3].

Unretiring rudeconfig


I would like to un-retire rudeconfig[1,2]. In line with the documented
policy[3], I have submitted a new review ticket here[4].

Would someone like to swap reviews please?

[1] <a href="" title=""></a>
[2] <a href="" title=""></a>
[3] <a href="" title=""></a>
[4] <a href="" title=""></a>

Empty debugsources.list file in build when enabling py2 builds


I have a spec here where I use a simple conditional to toggle py2
builds---so that I can use the same spec and provide py2 for F < 30

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

However, when I flip that variable to enable py2 builds to 1:

the build fails with this error:

I've checked, and the file is indeed empty, but I've not been able to
figure out why. Would anyone have any clues please?

libneurosim: Common interfaces for neuronal simulators


Would someone like to please swap reviews? I'd like to get
libneurosim[1] reviewed since it's needed for other NeuroFedora
packages. This one is also built with and without MPI support, so the
spec is slightly longer than normal.

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

Resurrection of the NeuroFedora SIG


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

I've recently resurrected the NeuroFedora SIG. Many thanks to Igor and
the others who'd worked on it in the past and have given us a firm base
to build on.

The goal
The (current) goal of the NeuroFedora SIG is to make Fedora an easy to
use platform for neuroscientists.

Neuroscience is an extremely multidisciplinary field. It brings together
mathematicians, chemists, biologists, physicists, psychologists,
engineers (electrical and others) computer scientists and more.

Pulling in rpmfusion appstream data with weak dependencies?


We're generating appstream data for rpmfusion packages nowadays to
enable users to install packages from there using gnome-software and
friends too.

Is there a way to automatically pull in the rpmfusion appstream data
packages? We looked at weak dependencies, specifically backward
dependencies. So, we added:

Supplements: appstream-data

to the rpmfusion appstream data spec files.

Review swap: Vimiv - An image viewer with vim-like keybindings


If anyone has any simple reviews pending, I'd love to do a swap. I've
packaged up Vimiv which is a great viewer with Vim like keybindings
ready for review here:

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

Here's a copr for people that would like to try it out in the meantime:

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

Review swap: python-mpd2: It is a Python library which provides a client interface for MPD


Another simple python package that I'd like reviewed - would someone
like to swap reviews please? :)

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

(It's holding up the update of another package: mpdris2)

Review swap: python-rstcheck - Checks syntax of reStructuredText and code blocks nested within it


Would anyone like to swap reviews? python-rstcheck is a rather simple
python package, so I'd be happy to review a similar package in return.

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

Simple python package review swap - python-feedgenerator


Would have a simple review ticket to swap? I'd be happy to take one in
exchange for this python package:

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


Can someone please help with this Java package FTBFS?


Could someone with more knowledge of Java please help with this bug? If
it's because the package is outdated, I'll just retire it.

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

Can I enable C++11 to build a package?


The subtitleeditor package seems to require C++11 enabled to build.
Here's an error in the mock log[1] for the latest failed build[2] for

/usr/include/glibmm-2.4/glibmm/error.h:41:20: note: C++11 'noexcept'
only available with -std=c++11 or -std=gnu++11

Can I enable C++11 to get it to build correctly? I haven't found a
policy that forbids or permits it.


Updating summary and description of a package on pkgdb and the spec


Can the summary and description of a package be changed on pkgdb?

Also, if it can't, is it OK if the summary and description on pkgdb
differ from the spec?


Packaging question on MPI requires


I recently packaged up nest[0] which is widely used in the
computational neuroscience research community. The review ticket is
here[1], and the copr builds are here[2]. Even though the rpm builds
perfectly, dnf won't install them from the copr.