DevHeads.net

Postings by Stephen Gallagher

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

Hash: SHA256

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting onirc.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-27 16:00 UTC'

Links to all issues below can be found
at:https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1737 i686 SIG needs to be functional by F27 release date or we
drop i686 kernel from F28
.fesco 1737https://pagure.io/fesco/issue/1737

#topic #1780 F28 System Wide Change: Annobin
.fesco 1780https://pagu

Summary/Minutes from today's FESCo Meeting (2017-08-11)

Hash: SHA256

===================================
#fedora-meeting: FESCO (2017-08-11)
===================================

Meeting started by sgallagh at 16:01:00 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting/2017-08-11/fesco.2017-08-11-16.01.log.html
.

Meeting summary
* init process (sgallagh, 16:01:00)

* #1721 Non-responsive maintainer process for caillon, and retiring
xchat (sgallagh, 16:04:19)
* AGREED: orphan all of caillon's packages and announce this.

Schedule for Friday's FESCo Meeting (2017-08-11)

Hash: SHA256

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting onirc.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-08-11 16:00 UTC'

Links to all issues below can be found
at:https://pagure.io/fesco/report/meeting_agenda

= Followups =

= New business =

#topic #1760 F27 approved Changes not in MODIFIED status (considered
as not testable)https://pagure.io/fesco/issue/1760

#topic #1758 ImageMagick Unresponsive Maintainer process - hubbitus
(Pav

Provenpackagers dealing with -Werror=format-security issues

There was an issue[1] with GCC7 during the mass-rebuild. Despite the Fedora-wide
setting of -Werror=format-security, GCC did not process its command-line
properly and an unknown number of packages were built without this flag
appropriately set.

Schedule for Friday's FESCo Meeting (2017-02-03)

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-02-03 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>

= Followups =

#topic #1669 F26 System Wide Change: Parallel Installable Debuginfo
<a href="https://pagure.io/fesco/issue/1669" title="https://pagure.io/fesco/issue/1669">https://pagure.io/fesco/issue/1669</a>

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

= New business =

#topic #1675 Libglvnd upda

Proposal: Rethink Fedora multilib support (Take Two!)

On 01/05/2017 11:03 AM, Stephen Gallagher wrote:

So, this thread provided a lot of feedback.

Proposal: Rethink Fedora multilib support

# Overview

For many years, Fedora has supported multilib by carrying parallel-installable
libraries in /usr/lib[64]. This was necessary for a very long time in order to
support 32-bit applications running on a 64-bit deployment. However, in today's
new container world, there is a whole new option.

I'd like to propose that we consider moving away from our traditional approach
to multilib in favor of recommending the use of a 32-bit container runtime when
needed on a 64-bit host.

## Advantages

* Simplification of build-tree creation.

RFC (round 2): Change the default hostname for Fedora 26+

The original thread is getting rather long and I'd like to attempt to summarize
the discussion thus far and see if we can find a way forward from there.

First, some clarifications for preconditions that some people were unaware of
(either on this thread or the ones that popped up on other lists/forums):

1) Fedora has always allowed the hostname to be changed in Anaconda. It's
perhaps not in the most obvious of places (the networking spoke), but it's
there.

RFC: Change the default hostname for Fedora 26+

For as long as I can recall, Fedora has shipped with a default hostname of
"localhost.localdomain"[1].

Unplanned ABI break in http-parser on F23

Recently, I updated http-parser from a 2.1 git prerelease snapshot to the latest
stable release 2.7.1 in all supported Fedora branches. I didn't anticipate any
issues because 1) the soname didn't change and 2) the project upstream uses
semantic versioning, which should imply that 2.7.x should be fully
backwards-compatible with 2.0.

Unfortunately, it looks like this is not perfectly true[1].

Schedule for Friday's FESCo Meeting (2016-08-12)

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 '2016-08-12 16:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1592 - Redefinition of what constitutes a secondary/alternate
architecture in Fedora
<a href="https://fedorahosted.org/fesco/ticket/1592" title="https://fedorahosted.org/fesco/ticket/1592">https://fedorahosted.org/fesco/ticket/1592</a>

#topic #1605 - finish retirement of sysvinit-only packages
<a href="https://fedorahosted.org/fesco/" title="https://fedorahosted.org/fesco/">https://fedorahosted.org/fesco/</a>

Initiating non-responsive maintainer process for T.C. Hollingsworth

For a long time, T.C. did excellent work maintaining the Node.js stack and
pushing for real JavaScript guidelines in Fedora. Unfortunately, he has been
unreachable for over a year now. The most recent activity I can find for him
anywhere on the Internet is Mar 2015 (here on the devel list).

Retiring python-slimit in Rawhide

Upstream is dead (website is gone), it hasn't seen a release in over three years
and nothing in Fedora relies on it anymore.

Schedule for Friday's FESCo Meeting (2016-05-06)

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 '2016-05-06 16:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1444 updates deliverables
.fesco 1444
<a href="https://fedorahosted.org/fesco/ticket/1444" title="https://fedorahosted.org/fesco/ticket/1444">https://fedorahosted.org/fesco/ticket/1444</a>

#topic #1514 Policy for autogenerated code
.fesco 1514
<a href="https://fedorahosted.org/fesco/ticket/1514" title="https://fedorahosted.org/fesco/ticket/1514">https://fedorahosted.org/fesco/ticket/1514</a>

#topic #1570 F24 Changes not in ON_QA st

RE: Plans for Node.js 6.x

Sent from my Galaxy Tab® S2-------- Original message --------From: drago01 < ... at gmail dot com> Date: 5/1/2016 12:00 PM (GMT-05:00) To: Development discussions related to Fedora < ... at lists dot fedoraproject.org> Subject: Re: Plans for Node.js 6.x
On Wed, Apr 27, 2016 at 4:00 AM, Stephen Gallagher < ... at redhat dot com> wrote:

Node.js downgraded to 4.x LTS in Fedora 24

As previously discussed on the fedora-devel list, the Node.js SIG has elected to
downgrade Node.js to the 4.x long-term-support branch rather than ship with the
5.x new-feature branch due to its support lifecycle ending this summer.

I have just bumped epoch and built the new 4.x package in Fedora 24 (along with
several archful modules that required a rebuild to work with the older version).
If you rely on Node.js (even just as part of your builddeps, such as with
nodejs-less), please test and give karma on
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898" title="https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898">https://bodhi.fedoraproject.org/updates/FEDORA-2016-2d314bc898</a>

Plans for Node.js 6.x

OK folks, it's Bad Decision Time.

Today, Node.js 6.0 was released. This is a significant ABI-breaking release,
which means there is no guarantee that existing modules will work with it at all.[1]

Better still, Node.js 5.x is only going to be supported until sometime this
summer, because they're aiming for the 6.x branch to become the new LTS in
October[2].

Node.js 5.9.0 coming to Rawhide next week

Next week, I plan to upgrade Node.js from the 4.x LTS branch to the 5.x stable
branch in Rawhide. This upgrade does break backwards-compatibility and thus will
need re-testing of modules. Also, all native NPMs (those that are built with
architecture-specific packages rather than noarch) will need to be rebuilt to
pick up the new automatic dependency system we have implemented.

Previously, native modules had to be rebuilt for every minor-version bump of
Node.js, but we have tweaked the virtual Provides and Requires to only require a
rebuild at major-version bumps.

Best practices for splitting off a directory to a new partition

During a recent Fedora Server SIG meeting where we were discussing the default
filesystem layout (if you just let Anaconda automatically create partitions),
there was a lot of talk about how certain directories such as /var/log or
/var/www/html, etc. are often split off into their own partitions at customer
sites.

LUA expert to help convert fedora-release %post scripts

As part of efforts in Fedora 24 to address certain issues with the
edition-specific fedora-release content (such as /etc/os-release, /etc/issues
and edition-specific presets), I built a moderately complex series of bash
scripts to run in %post and %posttrans to ensure that all of the right files
were symlinked in the correct places.

Unfortunately, the result here is that %post and %posttrans for fedora-release
now requires both bash and coreutils to function properly, and this introduces a
cyclical dependency.

Orphaning python-django-haystack and python-django-pipeline in Fedora

I no longer need these packages in Fedora (they were there to support Review
Board which is now only in EPEL due to Django incompatibilities), so I've
orphaned them.

I will continue to maintain them on EPEL 7.

Schedule for Friday's FESCo Meeting (2016-02-12)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17: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 '2016-02-12 17:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1539 Are 32-bit upgrades to Fedora 24 release blocking?

Schedule for Friday's FESCo Meeting (2016-02-05)

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

NOTE: due to DevConf.cz, we may not have quorum and these may be discussed
next week instead.

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 '2016-02-05 17:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1539 Are 32-bit upgrades to Fedora 24 release blocking?

Fedora Policy on generated code

Please keep responses on the devel@ list. CCed to the Council list for
visibility and discussion of how this fits with our "Freedom" foundation.

== Premise ==
Some upstream distribute tarballs that include code and content that
has been generated at distribution time.

Schedule for Wednesday's FESCo Meeting (2015-12-09)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18: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 '2015-12-09 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1444 updates deliverables
.fesco 1444
<a href="https://fedorahosted.org/fesco/ticket/1444" title="https://fedorahosted.org/fesco/ticket/1444">https://fedorahosted.org/fesco/ticket/1444</a>

#topic #1478 F24 Self Contained Changes
.fesco 1478
<a href="https://fedorahosted.org/fesco/ticket/1478" title="https://fedorahosted.org/fesco/ticket/1478">https://fedorahosted.org/fesco/ticket/1478</a>

= New business =

#topic #1511 F24 Syste

Some analysis on the size of the minimal and Server installs of Fedora 23

(Please keep responses on the devel@ list; I've set it in the Reply-To.)

To jump right to the premise: The default Fedora Server install is Way
Too Big(TM) and the minimal install (also available on the Fedora
Server install media) is also Too Big.

I've been trying to do some quick-and-dirty analysis of what is in
these default installations in order to figure out where we should be
focusing our efforts. I'll point out that there are two goals that we
need to keep in mind (and the reasons behind them) in order of
increasing importance:

1) Reduce disk space usage.

Seeking help to maintain Review Board packages for Fedora and RHEL/CentOS

As time goes on, it has become more and more difficult to dedicate the
time to maintain the RPM packages of Review Board on Fedora and EPEL.
My day-job responsibilities have increased and I can't spare as much
time as I used to for personal projects like this one.

I still use Review Board daily and will continue to maintain it as
time permits, but I'm looking for someone (ideally with packaging
experience) to assist me, particularly when security releases come out
and I'm unavailable.

System V to systemd unit migration

At the FESCo meeting on October 14th, it was ​decided that the time
has come to finally complete the migration away from System V init
scripts. What does this mean for you as a packager?

When we branch from Rawhide for Fedora 24 (currently ​scheduled for
February 2nd, 2016), we will be immediately retiring any package in
the Fedora collection that relies on a System V init script instead of
a systemd unit file to start.

Schedule for Wednesday's FESCo Meeting (2015-10-07)

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18: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 '2015-10-07 18:00 UTC'

Links to all tickets below can be found at:
<a href="https://fedorahosted.org/fesco/report/9" title="https://fedorahosted.org/fesco/report/9">https://fedorahosted.org/fesco/report/9</a>

= Followups =

#topic #1483 Decision on bundling policy in the Fedora Package Collectio
n
.fesco 1483
<a href="https://fedorahosted.org/fesco/ticket/1483" title="https://fedorahosted.org/fesco/ticket/1483">https://fedorahosted.org/fesco/ticket/1483</a>

= New business =

#topic #1484 unresponsive maintainer: chitlesh
.fesco 1484
<a href="https://fedorahost" title="https://fedorahost">https://fedorahost</a>

Proposal to reduce anti-bundling requirements

I assume that subject line got your attention.

I know this is a long-standing debate and that this thread is likely
to turn into an incomprehensible flamewar filled with the same tired
arguments, but I'm going to make a proposal and then attempt to
respond to many of those known arguments up-front (in the hopes that
we can try to keep the conversation on-track). Please keep the
conversation on <a href="mailto: ... at lists dot fedoraproject.org"> ... at lists dot fedoraproject.org</a> . I CCed packaging@ to
make them aware of this discussion.

Right now, we have a policy that essentially forbids source code from
being bundled into a package.