Kevin Fenzi | 28 Jan 04:26 2015

Schedule for Wednesday's FESCo meeting (2015-01-28 at 18UTC)

Following is the list of topics that will be discussed in the FESCo
meeting tomorrow at 18:00UTC in #fedora-meeting on

Links to all tickets below can be found at:

= Followups =

#topic ticket #1326 change to fesco replacement process?
.fesco 1326

#topic ticket #1392 Review scope of "Python 3 as default" Change for F22
.fesco 1392

= New business =

#topic ticket #1393 Making perl-sig a watcher on all perl packages
.fesco 1393

#topic ticket #1394 Use timedatex when an NTP package is installed
.fesco 1394

#topic ticket #1407 F22 System Wide Change: Vagrant Box for Fedora Atomic and Fedora Cloud -
.fesco 1407
(Continue reading)

Jason L Tibbitts III | 28 Jan 04:03 2015

[Guielines Change] Changes to the packaging guidelines

%license must be used in place of %doc to designate any file containing
the license information for a package. See and

Guidelines for DevAssistant packages (DAP) were added:

The Python guidelines relating to naming of executables in /usr/bin were
updated to account for F22's "Python3 by default" feature:

The Python Egg packaging guidelines have been cleaned up to properly
refer to egg packages and egg metadata:

Clarified the naming guidelines to indicate how language bindings are
named: lua-randomdb instead of randomdb-lua:

Added information on dealing with unversioned shared libraries:

The systemd guidelines were revised to include a section about the use
of PrivateDevices and PrivateNetwork:

Information on when timer activation must and must not be used was
added to the Systemd guidelines:
(Continue reading)

Casper | 27 Jan 23:11 2015

Is it a SELinux policy problem ?

Or is it a luajit problem ?

Dear devs hello.
I would like to determine if these AVC are caused by prosody, lua, or
a wrong SELinux policy.

lancaster ~ # systemctl status prosody
● prosody.service - Prosody XMPP (Jabber) server
   Loaded: loaded (/usr/lib/systemd/system/prosody.service; disabled)
         Active: inactive (dead)

lancaster ~ # sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      29

lancaster ~ # rpm -q prosody luajit

systemd start:
janv. 27 19:28:03 lancaster prosodyctl[21208]: PANIC: unprotected
error in call to Lua API (runtime code generation failed, restricted
(Continue reading)

Adrian Reber | 27 Jan 17:34 2015


I am planning to orphan the IRC client ninja. One of the reasons to
orphan it is that there is a build system[1] which has the same name.
In Fedora the ninja build system is called ninja-build which makes it
incompatible with most other Linux distributions[2]. In addition the
current release is from 2002 and upstream does not exist anymore.
Most of the other Linux distributions do not even ship it, although
there are other packages which are called ninja. It seems the name ninja
is already taken multiple times and maybe not a good idea for future



devel mailing list
devel <at>
Fedora Code of Conduct:
Jerry James | 27 Jan 17:03 2015

Re: Cannot start 2 VMs on F21

I asked the question below on the virt mailing list about 2 weeks ago.
There have been a grand total of zero responses so far.  I'll ask the
same question here, in hopes that somebody knows something that could

On Wed, Jan 14, 2015 at 11:19 AM, Jerry James <loganjerry <at>> wrote:
> Greetings,
> I recently upgraded my work machine from F20 to F21, via fedup.  Now I
> cannot run two VMs at the same time, as I used to be able to do, at
> least with virt-manager.  If I try to start a second VM via
> virt-manager, I get an error message:
> ------------------------------------------------------------------------------
> Error starting domain: Unable to read from monitor: Connection reset by peer
> Details:
> Error starting domain: Unable to read from monitor: Connection reset by peer
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/", line 89, in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/", line 125, in tmpcb
>     callback(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/", line 1388, in startup
>     self._backend.create()
>   File "/usr/lib64/python2.7/site-packages/", line 999, in create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: Unable to read from monitor: Connection reset by peer
(Continue reading)

Frantisek Kluknavsky | 27 Jan 16:25 2015

refactoring alternatives


I have a packaging question. Package gnuplot contained binary 
/usr/bin/gnuplot-wx. Subpackage gnuplot-qt contained binary 
/usr/bin/gnuplot-qt with roughly the same functionality using different 
GUI. Now it is time to declare qt default and wxGTK obsolete. 
/usr/bin/gnuplot-qt should be in default package gnuplot, 
/usr/bin/gnuplot-wx in subpackage gnuplot-wx.

My question is about alternatives. Both packages do something like suggests:
if [ $1 = 0 ]; then
     %{_sbindir}/alternatives --remove gnuplot %{_bindir}/gnuplot-wx || :
Now the name of the binary in package 'gnuplot' changes during an 
update. But the package is not removed and the %preun scriptlet thinks 
that old alternative should be left untouched.

What is the correct way to do this? My best idea so far is to increase 
priority of new alternative. Old alternative will remain rotting but a 
regular unknowing user will not notice broken symlinks after update.

Thank you very much and have a nice day.


devel mailing list
devel <at>
(Continue reading)

Marek Brysa | 27 Jan 13:24 2015

ABRT Crash statistics January 2015

Hi everyone,

first, on behalf of our team, let me invite you all to a talk I'm going to give
at the Developer Conference 2015 in Brno about the ABRT server. Details are
available here:

It's one again time to share with you some of the crash statistics ABRT server
has collected in the last 30 days. There have been 3,067,031 crashes in Fedora
20 and 21 in total, which is 1.8 million lower than last time, but still a huge
number. There has been transition from Fedora 20 to 21, as evidenced by:

Kernel oopses keep dominating with about 90% of the crashes. Some of the
biggest problems from last month have been resolved and their fixes confirmed
using "probable fixes".

Non-kernel problems can be also filtered using the "Type" field:

Note that you can now filter problems belonging to your whole group (e.g.
group::gnome-sig) by looking for it in the "Associate or Group" field. Also
kernel maintainers may now filter kernel oopses by excluding selected taint

As always, we welcome any suggestions to improve ABRT's server and these
statistics. The server's project lives here:

(Continue reading)

Fedora Rawhide Report | 27 Jan 10:02 2015

rawhide report: 20150127 changes

Compose started at Tue Jan 27 05:15:06 UTC 2015
Broken deps for i386
	Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	aeskulap-0.2.2-0.19beta1.fc22.i686 requires
	barman-1.3.3-4.fc22.noarch requires python-dateutil < 0:2.0
	boswars-2.7-5.fc22.i686 requires
	broccoli-2.3-1.fc22.i686 requires bro-2.3
	python-broccoli-2.3-1.fc22.i686 requires bro-2.3
	cab-0.1.9-12.fc22.i686 requires cabal-dev
	dnssec-check- requires
	dnssec-check- requires
	fawkes-lua-0.5.0-19.fc22.i686 requires
(Continue reading)

Jaroslav Reznik | 27 Jan 01:01 2015

FESCo elections are open

FESCo elections are now open and we're looking for five new
committee members. Elections closes promptly at 23:59 UTC
on February 3rd. Don't forget to vote!

To cast your vote, go to:

Read more about Fedora elections at

and about the new FESCo at

We use range voting in this process — vote for as many or as
few candidates as you like on a sliding scale.

Note: we were planning Env and Stacks WG elections too but
as number of candidates was the same as open seats, Env and
Stacks group decided not to run elections this time and
accept all candidates as committee members. See the announce-
ment from Honza Horak.

The Fedora Magazine interviews got delayed as we were waiting
for more questions being asked from the community. If you
need it to make your decision, please check magazine later. 

(Continue reading)

Honza Horak | 26 Jan 23:16 2015

New Env & Stacks WG crew - elections not necessary

Dear contributors,

based on the Governance Charter [1], the first Environment and Stacks 
working group elections were supposed to be held these days. We looked 
for 4 new voting members for the group.

The nominations period ended few days back and there are exactly 4 
nominations at [2]. Based on my poor math, since 4 - 4 = 0 there is no 
sense in holding the elections, since the results are already set.

Thus, let me cancel further election process and join me to welcome the 
following new members of Environment and Stacks working group:

* Slavek Kabrda (bkabrda), who's already been member so far
* Colin Walters (walters)
* Tomas Tomecek (ttomecek)
* Petr Hracek (phracek)

Guys, welcome on board, I'm looking forward to work with you!

The rest of the voting crew is:
* Honza Horák (hhorak)
* Nick Coghlan (ncoghlan)
* Jens Petersen (juhp)
* Václav Pavlín (vpavlin)
* Stuart Campbell (sicampbell)


(Continue reading)

Adam Williamson | 26 Jan 22:26 2015

DNF replacing yum: fedup?

I note the ReplaceYumWithDnf Change page:

says nothing about fedup. However, fedup uses yum:

[adamw <at> adam fedup (master %)]$ grep -R yum * | wc -l

Has this been considered yet? Should porting fedup to dnf be in the 
scope of this Change? Does that affect its practicability for F22?

Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net


devel mailing list
devel <at>
Fedora Code of Conduct: