DevHeads.net

Postings by Randy Barlow

Schedule for Friday's FESCo Meeting (2018-05-04)

The following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2018-05-04 15:00 UTC'

Links to all issues below can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Followups =

#topic #1877 large number of packages FTBFS in F28
.fesco 1877
<a href="https://pagure.io/fesco/issue/1877" title="https://pagure.io/fesco/issue/1877">https://pagure.io/fesco/issue/1877</a>

= New business =

#topic #1878 Please change "Everything" directory to something less
inaccurately comprehensive
.fesco

Status of OwnCloud/NextCloud

Greetings!

It seems that OwnCloud and NextCloud might be unmaintained in Fedora.

Gating packages in Rawhide

Greetings fellow Fedorans!

I would like to kick off a general discussion about how we might gate
packages in Rawhide. I think it would be nice to get something in place
for the Fedora 29 timeframe.

As one of the Bodhi contributors, I am inclined to suggest that we could
use Bodhi on Rawhide, similar to how we use it for our stable/branched
releases, with more relaxed rules (perhaps 1 day in testing or something
simple).

It may be possible to automate the process a bit to make it less heavy
for developers, though there is some complication for multi-package
updates (more on that in a bit).

Critpath karma

Greetings!

Does anybody here know the history and/or purpose behind Bodhi's
critical path karma? A brief grepping of Bodhi's codebase makes me think
it isn't really used by Bodhi for any purpose other than recording and
displaying people's entries. I.e., it doesn't seem to be used in Bodhi's
state machine. It also seems to be confusing for testers.

Does it serve a purpose? If not, should we remove it?

389-ds-base and freeipa on 32 bit arches

Greetings gcc maintainers!

A FESCo issue[0] has been filed due to the dropping of 389-ds-base and
freeipa on 32 bit arches for Fedora 28. This was done without a change
request being filed, so FESCo is trying to decide how best to handle it.

It seems there are some concerns about whether the C tooling correctly
handles some cases for 32-bit arches that led to the decision by the IPA
maintainers to drop support for 32-bit.

Schedule for Friday's FESCo Meeting (2018-02-16)

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

Note that this is a change in time from the previous FESCo meeting time.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2018-02-16 15:00 UTC'

Links to all issues below can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Followups =

#topic #1767 F28 Self Contained Changes
.fesco 1767
<a href="https://pagure.io/fesco/issue/1767" title="https://pagure.io/fesco/issue/1767">https://pagure.io/fesco/issue/1767</a>

#topic #1767 F28 Self Contained Changes: VA-API 1.0.0
https:/

Orphaned python-fedmsg-atomic-composer

With Bodhi 3, we don't use python-fedmsg-atomic-composer anymore:

<a href="https://src.fedoraproject.org/rpms/python-fedmsg-atomic-composer" title="https://src.fedoraproject.org/rpms/python-fedmsg-atomic-composer">https://src.fedoraproject.org/rpms/python-fedmsg-atomic-composer</a>

I probably should have just retired it, but I figured I'd orphan it in
case someone out there still wants it to exist for some reason. I also
forgot that it is not possible to orphan packages only on one branch
(i.e. Rawhide) ever since we switched away from pkgdb and so now I
slightly regret orphaning it instead of retiring it on master, since
bodhi 2 on epel 7 and f26/f27 do still use this package.

Schedule for Friday's FESCo Meeting (2017-10-06)

The following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2017-10-06 16:00 UTC'

Links to all issues below can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= New business =

#topic #1779 Consider fedora-* initscript units
.fesco 1779
<a href="https://pagure.io/fesco/issue/1779" title="https://pagure.io/fesco/issue/1779">https://pagure.io/fesco/issue/1779</a>

#topic #1780 F28 System Wide Change: Annobin
.fesco 1780
<a href="https://pagure.io/fesco/issue/1780" title="https://pagure.io/fesco/issue/1780">https://pagure.io/fesco/issue/1780</a>

= Open Floor =

For more c

erlang-p1_pam license change: GPLv2 --> ASL 2.0

The upstream for erlang-p1_pam has changed their license from GPLv2 to
ASL 2.0 in version 1.0.1[0]. I almost missed it since that's a .z
release! I plan to make that update only on Rawhide[1] (to version
1.0.3).

[0] https://github.com/processone/epam/blob/master/CHANGELOG.md
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1415854

dnf bodhi plugin

Hello!

I had an idea for a summer internship project, but I wanted to ask my
fellow Fedora devs if something like this already exists so it doesn't
get created as a duplicate project.

The idea is to create a dnf plugin that would allow you to do this:

$ sudo dnf upgrade FEDORA-2017-30604deb62

That update is a Gnome update, and likely has packages in it that you
don't use, but others that you do.

PSA: Bodhi client auth issue fix

There is a common issue that people have been hitting with the Bodhi
CLI.

vagrant-hostmanager-1.8.6 license change: MIT → MPLv2.0

vagrant-hostmanager has changed its license from MIT to MPLv2.0 with
version 1.8.6:

<a href="https://github.com/devopsgroup-io/vagrant-hostmanager/compare/v1.8.5...v1.8.6" title="https://github.com/devopsgroup-io/vagrant-hostmanager/compare/v1.8.5...v1.8.6">https://github.com/devopsgroup-io/vagrant-hostmanager/compare/v1.8.5...v...</a>

Due to this, I only plan to release 1.8.6 on Rawhide[0].

[0] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1447820" title="https://bugzilla.redhat.com/show_bug.cgi?id=1447820">https://bugzilla.redhat.com/show_bug.cgi?id=1447820</a>

Unretire nodejs-grunt-contrib-copy

Hello!

I would like to unretire nodejs-grunt-contrib-copy[0], and have filed a
package re-review:

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

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1432995

application and header files

Hello!

During a package review[0], I suggested that a CLI application's header
files need to go into a -devel subpackage (they are currently not being
packaged, except for the -debuginfo subpackage.) The reviewer
disagrees, but fedora-review uses the word must. I went to the
packaging guidelines[1] to find out if they say that header files must
be packaged for applications, but it seems that they don't explicitly
say that.

What if you only want to package part of upstream?

Hello!

In working on packaging Ampache, I found a dependency that has a
bundled version of this file:

<a href="https://github.com/kazuhikoarase/qrcode-generator/blob/master/js/qrcode.js" title="https://github.com/kazuhikoarase/qrcode-generator/blob/master/js/qrcode.js">https://github.com/kazuhikoarase/qrcode-generator/blob/master/js/qrcode.js</a>

I started working on doing the right thing and packaging that file
separately, but it seems that the repository also has qrcode
implementations for ActionScript, Java, PHP, and more.

Want to help me package Ampache?

Hello Fedora devs!

I recently started working on getting Ampache packaged for Fedora, and
it turns out it is no small feat. There are two problems:

0) 5 of the packages have been abandoned upstream, and have been
replaced with different packages that are now recommended. Ampache is
aware of this and does intend to switch, but at this time they still
depend on these 5 packages.

python-ipdb license change (GPLv2+ -> BSD)

Hello fellow devs!

I recently unorphaned python-ipdb and in working to get it updated to
it's latest release I noted that upstream's license has shifted from
GPLv2+ to BSD with their 0.9 release (Rawhide currently has 0.8.3). I'm
working on updating Rawhide to 0.10.1, but I will leave F24/25 on
0.8.3.

What to do when you have a bundled library that has no upstream and you don't know the version?

Hello Friends!

Igor and I were having a discussion on a package review ticket[0] about
how to handle a bundled library that seems to have no upstream that
either of us can find, and for which we don't know its version!

According to the packaging guidelines, it is OK to bundle the library
in certain circumstances, but the package must use Provides:
bundled(<libname>) = <version> in the spec file.

Since we don't know the version, it's difficult to know what to do
here.

Bodhi 2 coming to a Rawhide near you

Hello again Fedora friends!

I just built bodhi-2.1.8-1.fc26 for Rawhide, and wanted to give you a
heads up as it is a backwards incompatible change. Rawhide previously
had bodhi-0.9.12.2-5.fc25.noarch so this is a pretty major update.

The bodhi client is probably what most of you are used to interacting
with (possibly only through fedpkg, which wraps it). The new CLI is a
rewrite from the old one, and has different commands and options. I
took a stab at writing the new man page from scratch and I think I got
most things covered.

ejabberd, pam, and setuid root

Hello my fellow Fedora friends!

It's 01:00 in my local time and perhaps I should be resting instead of
trying to figure out chicken-and-egg problems at such a time, but my
tired mind is on the fence about the solution to one of my tickets and
I would love the input of others:

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

Let's just say that daemon package A creates user/group A and depends
on library B. One of library B's binaries needs to be installed setuid
root because it is for PAM authentication, but I'd rather install the
binary 4750 or 4700 than 4755.