DevHeads.net

Postings by Ankur Sinha

Open NeuroFedora team meeting: 1500 UTC on Thursday, 10th October

Hello everyone,

You are all invited to attend the Open NeuroFedora team meeting this week
on Thursday (10th October) at 1500UTC in #fedora-neuro on IRC (Freenode):

<a href="https://webchat.freenode.net/?channels=#fedora-neuro" title="https://webchat.freenode.net/?channels=#fedora-neuro">https://webchat.freenode.net/?channels=#fedora-neuro</a>

You can convert the meeting time to your local time using:
$ date --date='TZ="UTC" 1500 next Thu'

or use this link:
<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=Neuro-Fedora+team+meeting&amp;iso=20191010T15&amp;p1=%3A" title="https://www.timeanddate.com/worldclock/fixedtime.html?msg=Neuro-Fedora+team+meeting&amp;iso=20191010T15&amp;p1=%3A">https://www.timeanddate.com/worldclock/fixedtime.html?msg=Neuro-Fedora+t...</a>

The meeting will be chaired by @ankursinha (FranciscoD).

VIT version 2 changed license from GPL to MIT

Hello,

Vit has been rewritten from scratch in Python and released as version 2.
As part of this re-write, it also changed license to from GPLv3 to MIT.

<a href="https://github.com/scottkosty/vit" title="https://github.com/scottkosty/vit">https://github.com/scottkosty/vit</a>

This does not affect any other packages. I'm building the new version
for F30+ now.

Has fedpkg + dist-git replaced rpmbuild for building new/local packages?

Hi,

I was looking at this quick-docs page[1] which is mentioned in the "New
package process for existing contributors" page[2]. It now does not use
rpmbuild---it uses `fedpkg` and dist-git.

This is also linked to the "Join the package maintainers page"[3].

Is this now the suggested way---and is this what newcomers should be
using? I see that it has advantages---once packages are approved, we use
dist-git.

Logs of the weekly NeuroFedora meeting: October 3, 2019

Hello,

Here are the logs from today's meeting. The next meeting will be in a
week's time. It will be chaired by @ankursinha (me).

- HTML logs:
<a href="https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.2019-10-03-15.06.log.html" title="https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.2019-10-03-15.06.log.html">https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.20...</a>
- HTML minutes:
<a href="https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.2019-10-03-15.06.html" title="https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.2019-10-03-15.06.html">https://meetbot.fedoraproject.org/fedora-neuro/2019-10-03/neurofedora.20...</a>

The text minutes are pasted below for your convenience:

=========================================
#fedora-neuro: "NeuroFedora - 2019-10-03"
=========================================

Meeting started by bt0 at 15:06:58 UTC.

Looking for a maintainer for freemedforms

Hello,

I am looking to give away freemedforms[1]. It isn't part of our packages
for NeuroFedora, and those are what I'd like to focus my limited
resources on now.

It does not currently build in f31+ and may require dialogue with
upstream to fix.

<a href="https://src.fedoraproject.org/rpms/freemedforms" title="https://src.fedoraproject.org/rpms/freemedforms">https://src.fedoraproject.org/rpms/freemedforms</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1735221" title="https://bugzilla.redhat.com/show_bug.cgi?id=1735221">https://bugzilla.redhat.com/show_bug.cgi?id=1735221</a>

Please let me know if you would like to take it up, otherwise I will
retire it from Fedora on Friday (27th September). It will get
orphaned/retired as part of the FTBFS process otherwise anyway.

Please welcome @alciregi to the packager group

Hello,

I've just sponsored @alciregi to the packagers group.

They've been around the Fedora community for a while already and have
helped with QA/Marketing/Join/AskFedora and lots of other things. Now,
they are also looking to help the NeuroSIG with packaging and learn the
process along the way. I've added them to the neuro-sig where they will
help co-maintain our package list, and pick up the required
skills/knowledge.

Please welcome them to the packager and neuro-sig groups.

@alciregi: you already know all this, but for completeness: please
e-mail the various lists when you need to :)

Open NeuroFedora team meeting: 1500 UTC on Thursday, 19th September

Hello everyone,

You are invited to attend the Open NeuroFedora team meeting this week
on Thursday at 1500UTC in #fedora-neuro on IRC (Freenode):

<a href="https://webchat.freenode.net/?channels=#fedora-neuro" title="https://webchat.freenode.net/?channels=#fedora-neuro">https://webchat.freenode.net/?channels=#fedora-neuro</a>

You can convert the meeting time to your local time using:
$ date --date='TZ="UTC" 1500 next Thu'

or use this link:
<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190919T15&amp;p1=1440&amp;ah=1" title="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190919T15&amp;p1=1440&amp;ah=1">https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+te...</a>

The meeting will be chaired by @ankursinha.

Help needed with failing PPC build: cannot find MPI with openmpi

Hello,

A tool I am trying to package is failing only on PPC somehow:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1731487" title="https://bugzilla.redhat.com/show_bug.cgi?id=1731487">https://bugzilla.redhat.com/show_bug.cgi?id=1731487</a>

Proven packager help request: DCMTK (and dependent packages) require update in F29/F30

Hello,

A CVE[1] in dcmtk was fixed in 3.6.4 which is in F31+. F29 and F30 are
still at 3.6.2 however, and need updating.

DNF system-upgrade instructions on docs.fp.o

Hello,

Sometime ago, the dnf system-upgrade instructions were moved from the
wiki[0] to docs.fp.o[1].

Could folks please take a few minutes to check it for correctness? If
it's fine, we should make the wiki page redirect to the quick-doc too.

[0] <a href="https://fedoraproject.org/wiki/DNF_system_upgrade" title="https://fedoraproject.org/wiki/DNF_system_upgrade">https://fedoraproject.org/wiki/DNF_system_upgrade</a>
[1] <a href="https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/" title="https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/">https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/</a>

Open NeuroFedora team meeting: 1500 UTC on Thursday, 12th September

Hello everyone,

You are invited to attend the Open NeuroFedora team meeting this week
on Thursday at 1500UTC in #fedora-neuro on IRC (Freenode):

<a href="https://webchat.freenode.net/?channels=#fedora-neuro" title="https://webchat.freenode.net/?channels=#fedora-neuro">https://webchat.freenode.net/?channels=#fedora-neuro</a>

You can convert the meeting time to your local time using:
$ date --date='TZ="UTC" 1500 next Thu'

or use this link:
<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190912T15&amp;p1=1440&amp;ah=1" title="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190912T15&amp;p1=1440&amp;ah=1">https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+te...</a>

The meeting will be chaired by @mhough.

Open NeuroFedora Meeting agenda for 2019-09-05

Hello,

Please join us for the weekly Open NeuroFedora team meeting tomorrow.
Details below:

Open NeuroFedora team meeting: 1500 UTC on Thursday, 29th August.

Hello everyone,

You are invited to attend the Open NeuroFedora team meeting this week
on Thursday at 1500UTC in #fedora-neuro on IRC (Freenode):

<a href="https://webchat.freenode.net/?channels=#fedora-neuro" title="https://webchat.freenode.net/?channels=#fedora-neuro">https://webchat.freenode.net/?channels=#fedora-neuro</a>

You can convert the meeting time to your local time using:
$ date --date='TZ="UTC" 1500 next Thu'

or use this link:
<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190829T15&amp;p1=1440&amp;ah=1" title="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting&amp;iso=20190829T15&amp;p1=1440&amp;ah=1">https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+te...</a>

The agenda for the meeting is:

- Introductions and roll call.
- Pagure tickets related to our progress on computational neuroscience
tools:
<a href="https://pagure.io/neuro-" title="https://pagure.io/neuro-">https://pagure.io/neuro-</a>

Sponsored @major to the packager group

Hi everyone,

@major has been helping us with NeuroFedora packages, so I've sponsored
them to the packager group as a team-member of the neuro-sig group.

Please welcome them to the packager group!

Unable to install numpy with pip in python3.8

Hello,

Now that python3.8 has landed, I am trying to fix the packages that
don't build with it. For a few of these, I need to set up a virtual
environment with numpy in it. However, when I try to install numpy using
pip in the virtual env, it fails:

$ sudo dnf builddep python3-numpy

$ pew new -p /usr/bin/python3.8 numpy_test
$ pip install numpy

This fails with a long list of errors (attached). Numpy installs on
python3.7 just fine. Would someone be able to point out what I'm doing
wrong here?

CharLS update to 2.0.0 required (soname bump) (rhbz 1744789)

(Re-sending, got the e-mail address wrong)

Hi!

A new version of CharLS is out and needs to be updated in Fedora. It
contains changes in API/ABI so the following will need to be rebuilt:

dnf repoquery --disablerepo= --enablerepo=-source --arch=src --whatrequires CharLS-devel
dcm2niix-0:1.0.20180622-3.fc30.src
dcmtk-0:3.6.2-4.fc29.src
dcmtk-0:3.6.4-1.fc31.src
gdcm-0:2.8.8-4.fc30.src
gdcm-0:2.8.8-5.fc31.src

I can rebuild all of these as they are maintained by NeuroFedora, but I
do not have commit rights to CharLS.

Trivial review swap: taskopen

Hello,

Would anyone like to swap trivial reviews? I have "taskopen" here ready
for a full review:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1743802" title="https://bugzilla.redhat.com/show_bug.cgi?id=1743802">https://bugzilla.redhat.com/show_bug.cgi?id=1743802</a>

taskopen- Script for taking notes and open urls with taskwarrior.

Making a saved search public on Bugzilla

Hello,

Would anyone know how to make a saved search public on Bugzilla?

Taskjuggler COPR and its relevance

Hello,

It somehow slipped my radar that rubygem-taskjuggler had been retired.
Even though upstream isn't exactly active, the current git HEAD builds
fine. I've set it up in a COPR here now:

<a href="https://copr.fedorainfracloud.org/coprs/ankursinha/Takjuggler" title="https://copr.fedorainfracloud.org/coprs/ankursinha/Takjuggler">https://copr.fedorainfracloud.org/coprs/ankursinha/Takjuggler</a>

The updated spec and sources are here on my fork:
<a href="https://src.fedoraproject.org/fork/ankursinha/rpms/rubygem-taskjuggler/" title="https://src.fedoraproject.org/fork/ankursinha/rpms/rubygem-taskjuggler/">https://src.fedoraproject.org/fork/ankursinha/rpms/rubygem-taskjuggler/</a>

Given that upstream isn't active, I don't want to un-retire it just yet.
I'm not proficient in Ruby either so if something breaks and upstream
doesn't fix it, I won't be able to do much either.

What other external trackers would you like added to Bugzilla?

Hi,

The new "external trackers" bits in Bugzilla leaves out quite a few
commonly used ones. I filed a ticket[1] and was asked to contact the
admins. Before I do so, I thought I'd post here so we can make a list of
trackers we want to get added.

Orphaned pykalman---inactive upstream

Hello,

pykalman is no longer maintained upstream. I have, therefore, orphaned
it.
<a href="https://src.fedoraproject.org/rpms/python-pykalman" title="https://src.fedoraproject.org/rpms/python-pykalman">https://src.fedoraproject.org/rpms/python-pykalman</a>

It is now suggested to use other libraries:
<a href="https://github.com/pykalman/pykalman/issues/86" title="https://github.com/pykalman/pykalman/issues/86">https://github.com/pykalman/pykalman/issues/86</a>

First experience with building a module: newbie queries

Hello,

I finally got around to modules. I wanted to provide users with two
versions of NEST: 2.16.0 and 2.18.0. So, I:

- requested branches for 2.18.0 and 2.16.0 in dist/git:
<a href="https://src.fedoraproject.org/rpms/nest/branches?branchname=master" title="https://src.fedoraproject.org/rpms/nest/branches?branchname=master">https://src.fedoraproject.org/rpms/nest/branches?branchname=master</a>
- requested a new module and two branches (streams?) in modules also:
<a href="https://src.fedoraproject.org/modules/nest/branches?branchname=master" title="https://src.fedoraproject.org/modules/nest/branches?branchname=master">https://src.fedoraproject.org/modules/nest/branches?branchname=master</a>

- I then added nest.yaml to both, and ran `fedpkg module-build`.

Now, I'm not sure I've done it all correctly, so I have a few questions:

1.

Build failure with Openmpi on ppc64le

Hi!

I've been working on packaging MUSIC[1]. It builds correctly for all
arches apart from ppc64le where the build fails due to an openmpi
related error. Would anyone have an idea what is causing this?

Scratch build:
<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=36346224" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=36346224">https://koji.fedoraproject.org/koji/taskinfo?taskID=36346224</a>

Failing ppc64le build:
<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=36346229" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=36346229">https://koji.fedoraproject.org/koji/taskinfo?taskID=36346229</a>

Fedora and Free Science meetup at Flock

Hello!

Science, like Free/Open Source software should be open for all to use,
modify, explore, learn, and share. This is especially important to
ensure that the results from scientific work are not merely limited to
"academia", but are easily understandable by people in other walks of
life also.

Reminder: please use the "Trivial" keyword to mark easy reviews for newcomers

Hello!

Please consider using the "Trivial" keyword in the whiteboard to mark
simple reviews that newcomers can work on.
<a href="https://fedoraproject.org/wiki/Package_Review_Process#The_Whiteboard" title="https://fedoraproject.org/wiki/Package_Review_Process#The_Whiteboard">https://fedoraproject.org/wiki/Package_Review_Process#The_Whiteboard</a>

We list these separately on the cached review tracker:
<a href="https://fedoraproject.org/PackageReviewStatus/" title="https://fedoraproject.org/PackageReviewStatus/">https://fedoraproject.org/PackageReviewStatus/</a>

Easyfix has also been updated to list these:
<a href="https://fedoraproject.org/easyfix/" title="https://fedoraproject.org/easyfix/">https://fedoraproject.org/easyfix/</a>

For bugs in general, one can also use the "EasyFix" keyword in the
whiteboard to get their bugs listed in the easyfix list.
<a href="https://fedoraproject.org/wiki/Easyfix" title="https://fedoraproject.org/wiki/Easyfix">https://fedoraproject.org/wiki/Easyfix</a>

Any suggestions on how all of this may be improved is always

Trying to contact package maintainer: Filip Szymański

Hello,

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

Hello,

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="https://github.com/pypingou/fedora-active-user" title="https://github.com/pypingou/fedora-active-user">https://github.com/pypingou/fedora-active-user</a>
[2] <a href="https://src.fedoraproject.org/rpms/fedora-packager/blob/master/f/fedora-packager.spec#_78" title="https://src.fedoraproject.org/rpms/fedora-packager/blob/master/f/fedora-packager.spec#_78">https://src.fedoraproject.org/rpms/fedora-packager/blob/master/f/fedora-...</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="https://pagure.io/neuro-sig/NeuroFedora/issue/242" title="https://pagure.io/neuro-sig/NeuroFedora/issue/242">https://pagure.io/neuro-sig/NeuroFedora/issue/242</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="https://github.com/vxl/vxl/issues/638" title="https://github.com/vxl/vxl/issues/638">https://github.com/vxl/vxl/issues/638</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)

Hiya,

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.