REMINDER: Fedora 27 Change Checkpoint: Proposal submission deadline (System Wide Changes) in two weeks

2017-06-19 Thread Jan Kurik
Hi everyone! The submission deadline for System Wide Change Proposals of Fedora 27 [1] is coming pretty soon - in two weeks on July 4th. Please, submit your System Wide Changes by this deadline, earlier better. As the deadline applies for System Wide Changes it is always good to have most of Self

Fedora 27 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)

2017-06-19 Thread Jan Kurik
Greetings! Today, on 2017-June-20, we have reached Fedora 27 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild) [1]. At this point, only Changes not requiring mass rebuild will be accepted for Fedora 27. Any Change Proposal requiring mass rebuild should be scheduled

F27 System Wide Change: Kerberos KCM credential cache by default

2017-06-19 Thread Jan Kurik
= System Wide Change: Kerberos KCM credential cache by default = https://fedoraproject.org/wiki/Changes/KerberosKCMCache Change owner(s): * Jakub Hrozek Default to a new Kerberos credential cache type called KCM which is better suited for containerized environments and provides a better user exp

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Nick Coghlan
On 20 June 2017 at 02:49, Przemek Klosowski wrote: > On 06/19/2017 10:50 AM, Iryna Shcherbina wrote: > > The reason behind the second change is that there are a lot of Python 2 only > packages having `python-xxx` in Requires, which will start pulling Python 3 > dependencies when we switch to Pytho

[Fedocal] Reminder meeting : Modularity Office Hours

2017-06-19 Thread nils
Dear all, You are kindly invited to the meeting: Modularity Office Hours on 2017-06-20 from 10:00:00 to 11:00:00 US/Eastern At https://meet.jit.si/fedora-modularity The meeting will be about: This is where you ask the Fedora Modularity Team questions (and we try to answer them)! Join us [

Re: /usr/bin/qemu-kvm symlink

2017-06-19 Thread Antti Jarvinen
Daniel P. Berrange writes: > The way you configure QEMU for different architectures varies considerably, Yes. Also debian 9 is missing /usr/bin/qemu-kvm while $ ls -l /usr/bin/qemu* | wc 60 5404258 $ which includes qemuctl, so -1. -- Antti _

Fedora 26-20170619.n.0 compose check report

2017-06-19 Thread Fedora compose checker
Missing expected images: Workstation live i386 Kde live x86_64 Workstation live x86_64 Kde live i386 Failed openQA tests: 3/102 (x86_64), 1/2 (arm) ID: 110191 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/110191 ID: 110225

Fedora Rawhide-20170619.n.0 compose check report

2017-06-19 Thread Fedora compose checker
Missing expected images: Cloud_base qcow2 x86_64 Atomic qcow2 x86_64 Workstation live i386 Kde live x86_64 Cloud_base raw-xz x86_64 Server boot i386 Atomic raw-xz x86_64 Workstation live x86_64 Kde live i386 Failed openQA tests: 79/102 (x86_64), 18/18 (i386), 1/2 (arm) Old failures (same test fa

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Przemek Klosowski
On 06/19/2017 10:50 AM, Iryna Shcherbina wrote: The reason behind the second change is that there are a lot of Python 2 only packages having `python-xxx` in Requires, which will start pulling Python 3 dependencies when we switch to Python 3 as default. This will most possibly cause a number of

Planned Outage - Fedora Buildsystem Server reboots - 2017-06-20 21:00UTC

2017-06-19 Thread Kevin Fenzi
There will be an outage starting at 2017-06-20 21:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2017-06-20 21:00 UTC Reason for outage: We will be applying updates and reboot

Node.js v8.x in Fedora

2017-06-19 Thread Zuzana Svetlikova
Hi everyone, as there is nothing stopping us now, the nodejs package in Rawhide will soon be updated to Node.js v8.x. It also comes with npm@5 and new V8. Note that upstream has made a lot of changes and your projects/packages might have some issues. I'll update nodejs in rawhide next week, if y

Reviews Weekly

2017-06-19 Thread nobody
Start Date: 2017-06-12 10:08:01.939731 End Date: 2017-06-19 10:08:01.939731 Björn "besser82" Esser : 2 https://bugzilla.redhat.com/show_bug.cgi?id=128 hardening-wrapper https://bugzilla.redhat.com/show_bug.cgi?id=1461769 module-macros David King : 2 https:/

Reviews Weekly

2017-06-19 Thread nobody
Start Date: 2017-06-05 10:08:01.519243 End Date: 2017-06-12 10:08:01.519243 Remi Collet : 5 https://bugzilla.redhat.com/show_bug.cgi?id=1460523 php-psr-link https://bugzilla.redhat.com/show_bug.cgi?id=1460524 php-fig-link-util https://bugzilla.redhat.com/show_bug.

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Tom Hughes
On 19/06/17 15:50, Iryna Shcherbina wrote: If you expect your package to work when we switch to Python 3 as default, then you should already switch it to Python 3 or provide a Python 3 subpackage and depend on `python3-xxx`. Well to do that I'll have to patch all upstream's scripts which is a

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Iryna Shcherbina
The reason behind the second change is that there are a lot of Python 2 only packages having `python-xxx` in Requires, which will start pulling Python 3 dependencies when we switch to Python 3 as default. This will most possibly cause a number of unexpected issues, which is what we are trying t

Re: Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Tom Hughes
On 19/06/17 14:59, Iryna Shcherbina wrote: Recently, there were two important changes to Python packaging guidelines. The first one bans usingtheambiguous `python` prefix in binary RPM package names [1]. Thus you must explicitly definethePython version by using either `python2-` or `python3-`.

Proposed Mass Bug Filing: Renaming "python-" binary packages to "python2-"

2017-06-19 Thread Iryna Shcherbina
Hi all, Currently, in Fedora package names, "python" without a version number generally means Python 2. We would like to make it mean Python 3, but to make that switch, we first need to make sure nothing uses unqualified "python". All packages should use the "python2-" or "python3-" prefix. Th

F27 Self Contained Change: PHP 7.2

2017-06-19 Thread Jan Kurik
= Proposed Self Contained Change: PHP 7.2 = https://fedoraproject.org/wiki/Changes/php72 Change owner(s): * Remi Collet < remi at fedoraproject dot org > Update the PHP stack in Fedora to latest version 7.2.x == Detailed Description == Update the PHP stack in Fedora to latest version 7.2.x. PHP

Re: Is Jean-Francois Saucier (jsaucier) still maintaining radiotray package? Bugreports remain unread.

2017-06-19 Thread ghost-87
So, I suggest to remove radiotray from repos, for three reasons: 1) radiotray upstream is dead 2) radiotray depends on dead gstreamer0.10 3) fedora's radiotray maintainer is dead, too). If anyone interested in lightweight tray radio, there is radiotray-ng (https://github.com/ebruck/radiotray-ng

Re: running MTF tests in taskotron

2017-06-19 Thread Kamil Paral
On Mon, Jun 19, 2017 at 10:13 AM, Tomas Tomecek wrote: > The way I envision this is that the test would be invoked via taskotron's > API, > something like: > > $ taskotron trigger --koji-build= > > The CLI tool would contact taskotron's API and would submit a new test > run. For > me, it's an im

Re: /usr/bin/qemu-kvm symlink

2017-06-19 Thread Daniel P. Berrange
On Sat, Jun 17, 2017 at 05:25:18PM +, Zbigniew Jędrzejewski-Szmek wrote: > Hi, > > I was told [1] that /usr/bin/qemu-kvm is obsolete, and that the right > thing is to use 'qemu-system-x86_64 -enable-kvm', and that Arch and > Gentoo and qemu upstream don't support /usr/bin/qemu-kvm. Fedora prov

Re: running MTF tests in taskotron

2017-06-19 Thread Tomas Tomecek
Quoting Jan Scotka (2017-06-16 17:27:48) > > > It would be awesome if I could execute a command locally which would > > trigger > > testing process inside taskotron. This way I could make sure the tests get > > picked up correctly -- I definitely don't want to do rebuilds just for > > sake of > >

ppisar pushed to perl-Dumbbench (f26). "0.111 bump"

2017-06-19 Thread notifications
From 302e425ce9ec215aa66b82158763b7f8fa637848 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Mon, 19 Jun 2017 10:11:49 +0200 Subject: 0.111 bump --- .gitignore | 1 + perl-Dumbbench.spec | 31 +-- sources | 2 +- 3 files