[Test-Announce] 2014-04-07 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2014-04-07 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time again today/tomorrow! Apologies for the late notice. Let's take a look at the plan to do Rawhide validation testing, and any other items I've forgotten... == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Rawhide validation testing 3. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Self Introduction: Oden Eriksson
lördagen den 5 april 2014 13.18.15 skrev Paulo César Pereira de Andrade: 2014-04-03 7:50 GMT-03:00 Oden Eriksson o...@nux.se: Hello, Hi Oden, Small Linux world, isn't it ? :-) Ha ha, yeah. Been active with packaging, productization and maintaining packages for Mandriva Linux since 1999 and thought I should give it a try at fedora. First cut is this one: https://bugzilla.redhat.com/show_bug.cgi?id=1083962 And, it seems I need a sponsor here. Anyone? If nobody with MariaDB and MySQL expertise that already commented in your review request steps in, I will sponsor you. Sounds great. Actually, I work part time at SkySQL AB and this is sort of part of that scope. Cheers. Paulo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Self Introduction: Oden Eriksson
Even smaller than one would think. /me joins the party :) Alexander Kurtakov Red Hat Eclipse team - Original Message - From: Oden Eriksson o...@nux.se To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Monday, April 7, 2014 9:49:22 AM Subject: Re: Self Introduction: Oden Eriksson lördagen den 5 april 2014 13.18.15 skrev Paulo César Pereira de Andrade: 2014-04-03 7:50 GMT-03:00 Oden Eriksson o...@nux.se: Hello, Hi Oden, Small Linux world, isn't it ? :-) Ha ha, yeah. Been active with packaging, productization and maintaining packages for Mandriva Linux since 1999 and thought I should give it a try at fedora. First cut is this one: https://bugzilla.redhat.com/show_bug.cgi?id=1083962 And, it seems I need a sponsor here. Anyone? If nobody with MariaDB and MySQL expertise that already commented in your review request steps in, I will sponsor you. Sounds great. Actually, I work part time at SkySQL AB and this is sort of part of that scope. Cheers. Paulo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Meeting minutes from Env-and-Stacks WG meeting (2014-04-01)
On 04/06/2014 08:21 PM, Kevin Fenzi wrote: obs-signd also stores private key and passphrase on local disk right? IIRC yes. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Considering GNOME 3.12 as an F20 update
- Original Message - On Thu, 2014-04-03 at 22:34 -0500, Rex Dieter wrote: The gnome-3.12 copr includes a couple of low-level package updates that change abi/api that affects other desktops, notably: upower-0.99 PackageKit-0.9.x Are these 2 required by gnome-3.12 or would it be possible to use the (current) f20 versions? PackageKit should not need to be updated. upower will be a small problem. GNOME might need to be patched to use the older upower in F20 (or the other desktops could be patched to use the newer upower). I'd prefer to limit updates to GNOME only, so it would be desirable to get GNOME patched. It's easier to test if one desktop works well when patched than trying to test the whole world of other desktops (and probably forget something). So make this change self-contained rather than system wide. Otherwise I'm in favour of updates, these days it's pretty standard to even change the UI during life cycle of product and actually, users usually call for it (recently for example the OS in my STB changed from scratch and I was eagerly waiting for it ;-). Of course, it needs to be communicated to users. Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Summary of accepted Fedora 21 Changes - weeks 13/14
Greetings! This is a summary of FESCo's accepted Fedora 21 Changes for weeks 13 and 14 (2014-03-26 and 2014-04-02 meetings). Reminder: the Change Submission deadline for System Wide Change is tomorrow (2014-04-08 23:59 UTC). =Accepted changes= == System Wide Changes == * Modular Kernel Packaging for Cloud URL: https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196807.html Kernel modules that are not necessary in virtualized environments become optionally (un)installable. * Optional Javadocs URL: https://fedoraproject.org/wiki/Changes/OptionalJavadocs Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196808.html Make javadoc subpackages of Java packages optional in guidelines and communicate this change to users. * Ruby on Rails 4.1 URL: https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1 Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196803.html Ruby on Rails 4.1 is the latest version of well know web framework written in Ruby. * Java 8 URL: https://fedoraproject.org/wiki/Changes/Java8 Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196962.html Make Java 8 (provided by OpenJDK 8 which is java-1.8.0-openjdk) the default Java runtime. The current default Java runtime (Java 7, provided by OpenJDK 7, java-1.7.0-openjdk) will be obsoleted and removed. This is essentially an upgrade to the latest Java and OpenJDK version. * PrivateDevices=yes and PrivateNetwork=yes For Long-Running Services URL: https://fedoraproject.org/wiki/Changes/PrivateDevicesAndPrivateNetwork Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/197175.html Let's make Fedora more secure by default! Recent systemd versions provide two per-service switches PrivateDevices?=yes/no and PrivateNetwork?=yes/no which enable services to run without access to any physical devices in /dev, or without access to kind of network sockets. So far this has seen little use in Fedora, and with this Fedora Change we'd like to change this, and enable these for all long-running services that do not require device/network access. notting has question to note: is disconnecting the netlink and audit namespace truly required, or just merely a choice of what they decided to remove? == Self Contained Changes == * Amplab Tachyon - https://fedoraproject.org/wiki/Changes/AmplabTachyon discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197168.html Amplab-Tachyon is a fault tolerant distributed file system enabling reliable file sharing at memory-speed across cluster frameworks. * Apache Mesos - https://fedoraproject.org/wiki/Changes/ApacheMesos discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197180.html Apache Mesos is a cluster manager for sharing distributed application frameworks. This change brings Mesos to Fedora, which many have called a micro-kernel for the data center. * Apache Spark - https://fedoraproject.org/wiki/Changes/ApacheSpark discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196967.html Apache Spark is a fast and general engine for large-scale data processing. This change brings Spark to Fedora, allowing easy deployment and development of Spark applications on Fedora. * Improved Scala Ecosystem Support - https://fedoraproject.org/wiki/Changes/ImprovedScalaEcosystem discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196964.html Fedora now supports several essential parts of the Scala language ecosystem as well as building packages with sbt, the de facto build tool for the Scala community. Scala proposal owners to work to develop packaging guidelines * DNSSEC support for FreeIPA - https://fedoraproject.org/wiki/Changes/IPAv3DNSSEC discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197177.html FreeIPA with integrated DNS server will support serving of DNSSEC secured zones and automatic DNSSEC key maintenance. This first version will have only the very basic functionality with limited user interface and limited resiliency. Next versions (to be delivered in Fedora 22 time frame) will improve resiliency and user interface significantly. * NFS Ganesha File Server - https://fedoraproject.org/wiki/Changes/NFSGanesha discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196968.html NFS Ganesha is a user mode file server that supports NFSv3, NFSv4, and NFSv4.1 including pNFS for distributed filesystems. It uses loadable filesystem driver modules to support its backend filesystems. It also integrates 9P.2000L file service = Rejected Changes = * Security Policy In The Installer URL: https://fedoraproject.org/wiki/Changes/SecurityPolicyInTheInstaller Announcement:
[Bug 1083418] perl-Log-Dispatch-2.41-1.fc21 FTBFS
https://bugzilla.redhat.com/show_bug.cgi?id=1083418 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|tcall...@redhat.com |ppi...@redhat.com --- Comment #3 from Petr Pisar ppi...@redhat.com --- I don't know why, but if /usr/sbin/sendmail is available the test pass. The requires e-mail modules do not require /usr/sbin/sendmail because they allow local /usr/sbin/sendmail or SMTP, both optional. I will add /usr/sbin/sendmail into build-requires on the executable to this package. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=npPYLNezrFa=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Packaging of libdb-6+
On 04/03/2014 09:14 PM, Paul Howarth wrote: On Thu, 03 Apr 2014 15:53:04 +0200 Honza Horak hho...@redhat.com wrote: On 04/03/2014 11:20 AM, H. Guémar wrote: Since AGPL is fedora-compliant license, there's no blocker to get libdb6 into packages collection. Besides, libdb5 is still critical for many packages (like RM), until we get rid of it, I can only agree with your proposal. Maybe, it's still time to rename the current libdb = libdb5 and get newer releases named libdb starting F21 This would be possible only by co-operation with the depended packages, since they usually use BuildRequire: libdb-devel. So after just rebuilding those to link against libdb-6, some of the packages would start to suffer from license incompatibilities. But I agree that libdb-6.x + libdb5-5.x scenario looks better than libdb-5.x + libdb6-6.x. Anyway, to make some marketing for this change, we should have a Self contained change page for this [1]. Change Proposals Submission Deadline is 2014-04-08 btw. [1] http://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes It's not a self-contained change really. Without a good deal of co-ordination it'll end up causing problems like https://bugzilla.redhat.com/show_bug.cgi?id=768846 in which there are symbol conflicts when a process ends up trying to load two different versions of libdb. I understand and agree that there is a risk of some issues, but the issues won't have platform-wide influence imho, so this doesn't seem to me like that we need to take this update as a system-wide change, if you meant that. Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging of libdb-6+
On 07/04/14 14:43, Honza Horak wrote: On 04/03/2014 09:14 PM, Paul Howarth wrote: On Thu, 03 Apr 2014 15:53:04 +0200 Honza Horak hho...@redhat.com wrote: On 04/03/2014 11:20 AM, H. Guémar wrote: Since AGPL is fedora-compliant license, there's no blocker to get libdb6 into packages collection. Besides, libdb5 is still critical for many packages (like RM), until we get rid of it, I can only agree with your proposal. Maybe, it's still time to rename the current libdb = libdb5 and get newer releases named libdb starting F21 This would be possible only by co-operation with the depended packages, since they usually use BuildRequire: libdb-devel. So after just rebuilding those to link against libdb-6, some of the packages would start to suffer from license incompatibilities. But I agree that libdb-6.x + libdb5-5.x scenario looks better than libdb-5.x + libdb6-6.x. Anyway, to make some marketing for this change, we should have a Self contained change page for this [1]. Change Proposals Submission Deadline is 2014-04-08 btw. [1] http://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes It's not a self-contained change really. Without a good deal of co-ordination it'll end up causing problems like https://bugzilla.redhat.com/show_bug.cgi?id=768846 in which there are symbol conflicts when a process ends up trying to load two different versions of libdb. I understand and agree that there is a risk of some issues, but the issues won't have platform-wide influence imho, so this doesn't seem to me like that we need to take this update as a system-wide change, if you meant that. It's a bit borderline I think. It doesn't affect the whole platform but quite a number of otherwise unrelated packages will need updating to libdb-6, in particular rpm, httpd, any httpd modules and their dependencies that are affected, sendmail etc. Paul. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphaning java-1.5.0-gcj
There have been a few discussions about this in the past but no action. With feature freeze approaching for F21, I think this is a good time to address this. I will be orphaning java-1.5.0-gcj in Fedora on April 8th. If anyone wants to take over, please let me know. Please do keep in mind though that we really should just remove GCJ (despite the effect it will have on pdftk) as preferred by one of the primary authors of it (Andrew Haley): How does this affect the bring up of new architectures, I seem to remember when doing the various variants of ARM we needed this for bringup of the newer releases, is that still the case or is there other means of achieving that? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Agenda for Env-and-Stacks WG meeting (2014-04-08)
WG meeting will be at 16:00 UTC, 17:00 Central Europe, 12:00 (noon) Boston, 9:00 San Francisco, 1:00 Tokyo in #fedora-meeting on Freenode. == Topic == I sent three Change proposals. If you have any comments, please share them. * https://fedoraproject.org/wiki/Changes/SCL * https://fedoraproject.org/wiki/Changes/Playground_repository * https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL * continue in Open Questions about Playground * https://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_%28draft%29#Open_Questions * see dnf plugin http://mmaslano.livejournal.com/10322.html See you, Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
retire seam-solder
hi folks, i would like to withdraw seam-solder. Cause: active development of solder has been halted this project has been migrated over to apache deltaspike . the current release, also, don't support the actual |jboss-logging-tools| [1] package and have some problems with java 8 [2]. regards gil [1] |jboss-logging-tools = 1.0.3| [2] [ERROR] /builddir/build/BUILD/seam-solder-3.1.1.Final/impl/src/main/java/org/jboss/solder/serviceHandler/ServiceHandlerBeanLifecycle.java:[70,47] incompatible types: java.lang.Object cannot be converted to H attachment: puntogil.vcf-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging of libdb-6+
On 04/07/2014 03:51 PM, Paul Howarth wrote: On 07/04/14 14:43, Honza Horak wrote: On 04/03/2014 09:14 PM, Paul Howarth wrote: On Thu, 03 Apr 2014 15:53:04 +0200 Honza Horak hho...@redhat.com wrote: On 04/03/2014 11:20 AM, H. Guémar wrote: Since AGPL is fedora-compliant license, there's no blocker to get libdb6 into packages collection. Besides, libdb5 is still critical for many packages (like RM), until we get rid of it, I can only agree with your proposal. Maybe, it's still time to rename the current libdb = libdb5 and get newer releases named libdb starting F21 This would be possible only by co-operation with the depended packages, since they usually use BuildRequire: libdb-devel. So after just rebuilding those to link against libdb-6, some of the packages would start to suffer from license incompatibilities. But I agree that libdb-6.x + libdb5-5.x scenario looks better than libdb-5.x + libdb6-6.x. Anyway, to make some marketing for this change, we should have a Self contained change page for this [1]. Change Proposals Submission Deadline is 2014-04-08 btw. [1] http://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes It's not a self-contained change really. Without a good deal of co-ordination it'll end up causing problems like https://bugzilla.redhat.com/show_bug.cgi?id=768846 in which there are symbol conflicts when a process ends up trying to load two different versions of libdb. I understand and agree that there is a risk of some issues, but the issues won't have platform-wide influence imho, so this doesn't seem to me like that we need to take this update as a system-wide change, if you meant that. It's a bit borderline I think. It doesn't affect the whole platform but quite a number of otherwise unrelated packages will need updating to libdb-6, in particular rpm, httpd, any httpd modules and their dependencies that are affected, sendmail etc. This thread misses one important information. This change is not only about changing license from GPL to AGPL, but there is also a change in version, since libdb-6 is AGPLv3+ (change from GPLv2+). So, updating of the components won't happen in all cases that simple, since for some of them the upgrade would mean to introduce license incompatibility (components that are GPLv2 only like RPM). That means that some of the packages will need to stay with libdb-5 or will start link against some other GPLv2+ alternative. Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Owner-change] Fedora packages ownership change
Change in ownership over the last 168 hours === 3 packages were orphaned python-keystoneclient [EL-6,devel,f19,f20] was orphaned by apevec Python API and CLI for OpenStack Keystone https://admin.fedoraproject.org/pkgdb/acls/name/python-keystoneclient perl-HTML-FormatText-WithLinks [EL-6] was orphaned by mmaslano HTML to text conversion with links as footnotes https://admin.fedoraproject.org/pkgdb/acls/name/perl-HTML-FormatText-WithLinks lbzip2 [EL-5,EL-6,devel,epel7,f19,f20] was orphaned by lzap Fast multi-threaded implementation of bzip2 https://admin.fedoraproject.org/pkgdb/acls/name/lbzip2 4 packages unorphaned - cicku unorphaned : npth [devel] jruzickaunorphaned : python-keystoneclient [EL-6,devel,f19,f20] mizdebskunorphaned : lbzip2 [EL-5,EL-6,devel,epel7,f19,f20] rlandmann unorphaned : perl-HTML-FormatText-WithLinks [EL-6] 6 packages were retired golang-github-guelfey-godbus [EL-6,devel,epel7,f19,f20] was retired by lsm5 Go client bindings for D-Bus https://admin.fedoraproject.org/pkgdb/acls/name/golang-github-guelfey-godbus actdiag [f19,f20] was retired by dridi actdiag generates activity-diagram images from text https://admin.fedoraproject.org/pkgdb/acls/name/actdiag seqdiag [f19,f20] was retired by dridi seqdiag generates sequence-diagram images from text https://admin.fedoraproject.org/pkgdb/acls/name/seqdiag nwdiag [f19,f20] was retired by dridi nwdiag generates network-diagram images from text https://admin.fedoraproject.org/pkgdb/acls/name/nwdiag rubygem-cloudservers [f20] was retired by mhayden A Ruby API to version 1.0 of the Rackspace Cloud Servers product. https://admin.fedoraproject.org/pkgdb/acls/name/rubygem-cloudservers rubygem-cloudfiles [devel,f19,f20] was retired by mhayden A Ruby version of the Rackspace Cloud Files API https://admin.fedoraproject.org/pkgdb/acls/name/rubygem-cloudfiles 5 packages changed owner limbgave to cicku : python-pygit2 [epel7] limbgave to cicku : logstalgia [EL-6,epel7] limbgave to mystro256 : xsensors [EL-6,epel7] limbgave to cicku : subnetcalc [EL-6,epel7] limbgave to cicku : lnav [EL-6,epel7] Sources: https://github.com/pypingou/fedora-owner-change -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Summary of accepted Fedora 21 Changes - weeks 13/14
On Mon, 07.04.14 15:00, Jaroslav Reznik (jrez...@redhat.com) wrote: * PrivateDevices=yes and PrivateNetwork=yes For Long-Running Services URL: https://fedoraproject.org/wiki/Changes/PrivateDevicesAndPrivateNetwork Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/197175.html Let's make Fedora more secure by default! Recent systemd versions provide two per-service switches PrivateDevices?=yes/no and PrivateNetwork?=yes/no which enable services to run without access to any physical devices in /dev, or without access to kind of network sockets. So far this has seen little use in Fedora, and with this Fedora Change we'd like to change this, and enable these for all long-running services that do not require device/network access. notting has question to note: is disconnecting the netlink and audit namespace truly required, or just merely a choice of what they decided to remove? To answer this: the kernel network namespace thing PrivateNetwork= is built on disconnects all address families at once. There's no choice to only disassociate some address families, either all or none. (except for the weirdness of AF_UNIX sockets in the fs namespace which stay connectable as long as the fs is reachable, see feature page). Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging of libdb-6+
On 07/04/14 15:54, Honza Horak wrote: On 04/07/2014 03:51 PM, Paul Howarth wrote: On 07/04/14 14:43, Honza Horak wrote: On 04/03/2014 09:14 PM, Paul Howarth wrote: On Thu, 03 Apr 2014 15:53:04 +0200 Honza Horak hho...@redhat.com wrote: On 04/03/2014 11:20 AM, H. Guémar wrote: Since AGPL is fedora-compliant license, there's no blocker to get libdb6 into packages collection. Besides, libdb5 is still critical for many packages (like RM), until we get rid of it, I can only agree with your proposal. Maybe, it's still time to rename the current libdb = libdb5 and get newer releases named libdb starting F21 This would be possible only by co-operation with the depended packages, since they usually use BuildRequire: libdb-devel. So after just rebuilding those to link against libdb-6, some of the packages would start to suffer from license incompatibilities. But I agree that libdb-6.x + libdb5-5.x scenario looks better than libdb-5.x + libdb6-6.x. Anyway, to make some marketing for this change, we should have a Self contained change page for this [1]. Change Proposals Submission Deadline is 2014-04-08 btw. [1] http://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes It's not a self-contained change really. Without a good deal of co-ordination it'll end up causing problems like https://bugzilla.redhat.com/show_bug.cgi?id=768846 in which there are symbol conflicts when a process ends up trying to load two different versions of libdb. I understand and agree that there is a risk of some issues, but the issues won't have platform-wide influence imho, so this doesn't seem to me like that we need to take this update as a system-wide change, if you meant that. It's a bit borderline I think. It doesn't affect the whole platform but quite a number of otherwise unrelated packages will need updating to libdb-6, in particular rpm, httpd, any httpd modules and their dependencies that are affected, sendmail etc. This thread misses one important information. This change is not only about changing license from GPL to AGPL, but there is also a change in version, since libdb-6 is AGPLv3+ (change from GPLv2+). So, updating of the components won't happen in all cases that simple, since for some of them the upgrade would mean to introduce license incompatibility (components that are GPLv2 only like RPM). That means that some of the packages will need to stay with libdb-5 or will start link against some other GPLv2+ alternative. Does libdb-6 have the same symbol names as libdb-5? If so, there's probably not a lot of packages that can be built with libdb-6 without the possibility of causing symbol conflicts with others built against libdb-5 (which can't be updated for license reasons). Paul. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packaging of libdb-6+
On 04/07/2014 05:31 PM, Paul Howarth wrote: On 07/04/14 15:54, Honza Horak wrote: On 04/07/2014 03:51 PM, Paul Howarth wrote: On 07/04/14 14:43, Honza Horak wrote: On 04/03/2014 09:14 PM, Paul Howarth wrote: On Thu, 03 Apr 2014 15:53:04 +0200 Honza Horak hho...@redhat.com wrote: On 04/03/2014 11:20 AM, H. Guémar wrote: Since AGPL is fedora-compliant license, there's no blocker to get libdb6 into packages collection. Besides, libdb5 is still critical for many packages (like RM), until we get rid of it, I can only agree with your proposal. Maybe, it's still time to rename the current libdb = libdb5 and get newer releases named libdb starting F21 This would be possible only by co-operation with the depended packages, since they usually use BuildRequire: libdb-devel. So after just rebuilding those to link against libdb-6, some of the packages would start to suffer from license incompatibilities. But I agree that libdb-6.x + libdb5-5.x scenario looks better than libdb-5.x + libdb6-6.x. Anyway, to make some marketing for this change, we should have a Self contained change page for this [1]. Change Proposals Submission Deadline is 2014-04-08 btw. [1] http://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes It's not a self-contained change really. Without a good deal of co-ordination it'll end up causing problems like https://bugzilla.redhat.com/show_bug.cgi?id=768846 in which there are symbol conflicts when a process ends up trying to load two different versions of libdb. I understand and agree that there is a risk of some issues, but the issues won't have platform-wide influence imho, so this doesn't seem to me like that we need to take this update as a system-wide change, if you meant that. It's a bit borderline I think. It doesn't affect the whole platform but quite a number of otherwise unrelated packages will need updating to libdb-6, in particular rpm, httpd, any httpd modules and their dependencies that are affected, sendmail etc. This thread misses one important information. This change is not only about changing license from GPL to AGPL, but there is also a change in version, since libdb-6 is AGPLv3+ (change from GPLv2+). So, updating of the components won't happen in all cases that simple, since for some of them the upgrade would mean to introduce license incompatibility (components that are GPLv2 only like RPM). That means that some of the packages will need to stay with libdb-5 or will start link against some other GPLv2+ alternative. Does libdb-6 have the same symbol names as libdb-5? If so, there's probably not a lot of packages that can be built with libdb-6 without the possibility of causing symbol conflicts with others built against libdb-5 (which can't be updated for license reasons). Good question. Jan, can you investigate it, please? Honza -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20140407 changes
Broken deps for i386 -- [PyKDE] PyKDE-3.16.6-14.fc20.i686 requires sip-api(10) = 0:10.0 [ale] ale-0.9.0.3-13.fc20.i686 requires libMagickCore-6.Q16.so.1 [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [derelict] derelict-tcod-3-26.201410303git9570453.fc21.i686 requires tcod derelict-tcod-devel-3-26.201410303git9570453.fc21.i686 requires tcod [dmapd] dmapd-0.0.69-2.fc21.i686 requires libMagickWand-6.Q16.so.1 dmapd-0.0.69-2.fc21.i686 requires libMagickCore-6.Q16.so.1 [drawtiming] drawtiming-0.7.1-12.fc21.i686 requires libMagickWand-6.Q16.so.1 drawtiming-0.7.1-12.fc21.i686 requires libMagickCore-6.Q16.so.1 [gammaray] gammaray-2.0.0-1.fc21.i686 requires qt(x86-32) = 1:4.8.5 gammaray-2.0.0-1.fc21.i686 requires libvtkjsoncpp.so.1 gammaray-2.0.0-1.fc21.i686 requires libvtkTestingIOSQL.so.1 gammaray-2.0.0-1.fc21.i686 requires libvtkTestingGenericBridge.so.1 gammaray-2.0.0-1.fc21.i686 requires libvtkRenderingHybridOpenGL.so.1 [gdb-heap] gdb-heap-0.5-15.fc21.i686 requires glibc(x86-32) = 0:2.18.90 [gnome-pie] gnome-pie-0.5.5-3.20130330git0a5aa2.fc20.i686 requires libbamf3.so.0 [gofer] ruby-gofer-0.77-1.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [golang-github-smarterclayton-go-systemd] golang-github-smarterclayton-go-systemd-devel-0-0.4.git5cb9e9e.fc21.noarch requires golang(github.com/guelfey/go.dbus) [gtkd] gtkd-2.0.0-45.20140301gitaf01da8.fc21.i686 requires gstreamer-plugins-basexz [httpdtap] httpdtap-0.2-2.fc21.noarch requires kernel-debuginfo httpdtap-0.2-2.fc21.noarch requires httpd-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-util-debuginfo httpdtap-0.2-2.fc21.noarch requires apr-debuginfo [imageinfo] imageinfo-0.05-19.fc20.i686 requires libMagickCore-6.Q16.so.1 [kawa] 1:kawa-1.11-5.fc19.i686 requires servlet25 [kxstitch] kxstitch-0.8.4.1-17.fc21.i686 requires libMagickWand-6.Q16.so.1 kxstitch-0.8.4.1-17.fc21.i686 requires libMagickCore-6.Q16.so.1 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks [libghemical] libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3 libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1 [libyui-gtk] libyui-gtk-2.43.7-1.fc21.i686 requires libyui.so.5 [libyui-ncurses] libyui-ncurses-2.44.1-1.fc21.i686 requires libyui.so.5 [libyui-qt] libyui-qt-2.43.5-1.fc21.i686 requires libyui.so.5 [mojomojo] mojomojo-1.10-1.fc20.noarch requires perl(HTML::FormFu::Element::reCAPTCHA) [mpqc] mpqc-2.3.1-23.fc20.i686 requires libf77blas.so.3 mpqc-2.3.1-23.fc20.i686 requires libatlas.so.3 [netdisco] netdisco-1.1-6.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [nifti2dicom] nifti2dicom-0.4.6-3.fc20.i686 requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libitksys-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libitkopenjpeg-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libitkdouble-conversion-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libitkNetlibSlatec-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libgdcmMSFF.so.2.2 nifti2dicom-0.4.6-3.fc20.i686 requires libgdcmDICT.so.2.2 nifti2dicom-0.4.6-3.fc20.i686 requires libQVTK.so.5.10 nifti2dicom-0.4.6-3.fc20.i686 requires libITKznz-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libITKniftiio-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires libITKgiftiio-4.4.so.1 nifti2dicom-0.4.6-3.fc20.i686 requires
Re: Orphaning java-1.5.0-gcj
On 04/07/2014 03:23 PM, Peter Robinson wrote: There have been a few discussions about this in the past but no action. With feature freeze approaching for F21, I think this is a good time to address this. I will be orphaning java-1.5.0-gcj in Fedora on April 8th. If anyone wants to take over, please let me know. Please do keep in mind though that we really should just remove GCJ (despite the effect it will have on pdftk) as preferred by one of the primary authors of it (Andrew Haley): How does this affect the bring up of new architectures, I seem to remember when doing the various variants of ARM we needed this for bringup of the newer releases, is that still the case or is there other means of achieving that? As of JDK8, OpenJDK can be cross-compiled. Not before time, either. Andrew. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Thu, 2014-04-03 at 19:44 -0700, Andrew Lutomirski wrote: On Apr 3, 2014 7:18 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 04.04.2014 03:08, schrieb Andrew Lutomirski: Once upon a time (Fedora 15? -- I've lost track), it was possible to reinstall the bootloader using grub-install. besides that it is the wrong list: What's the right list? grub2-install $ grub2-install /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. This is with efi. WTF is a GRUB drive? Will this set up the boot You don't want to be doing any kind of grub(2)-install if you actually have a native UEFI install. That's not how UEFI booting works. But it's difficult to divine from your emails how your system is actually set up at all. Can you please answer the following? 1. What is the output of 'efibootmgr -v'? 2. Do you have a /boot/efi/EFI/fedora/grub.cfg ? 3. Do you have a /boot/grub/grub.conf ? 4. Do you have a /boot/grub2/grub.cfg ? For a 'yes' answer to 2, 3 or 4 it would be nice to have the contents visible somewhere. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
its now grub2-install /dev/sdX Corey W Sheldon Owner, 1st Class Mobile Shine 310.909.7672 www.facebook.com/1stclassmobileshine On Mon, Apr 7, 2014 at 8:16 PM, Adam Williamson awill...@redhat.com wrote: On Thu, 2014-04-03 at 19:44 -0700, Andrew Lutomirski wrote: On Apr 3, 2014 7:18 PM, Reindl Harald h.rei...@thelounge.net wrote: Am 04.04.2014 03:08, schrieb Andrew Lutomirski: Once upon a time (Fedora 15? -- I've lost track), it was possible to reinstall the bootloader using grub-install. besides that it is the wrong list: What's the right list? grub2-install $ grub2-install /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. This is with efi. WTF is a GRUB drive? Will this set up the boot You don't want to be doing any kind of grub(2)-install if you actually have a native UEFI install. That's not how UEFI booting works. But it's difficult to divine from your emails how your system is actually set up at all. Can you please answer the following? 1. What is the output of 'efibootmgr -v'? 2. Do you have a /boot/efi/EFI/fedora/grub.cfg ? 3. Do you have a /boot/grub/grub.conf ? 4. Do you have a /boot/grub2/grub.cfg ? For a 'yes' answer to 2, 3 or 4 it would be nice to have the contents visible somewhere. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Mon, 2014-04-07 at 20:20 -0400, Corey Sheldon wrote: its now grub2-install /dev/sdX It's not for UEFI. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
grub2 is the default now with or without uefi Corey W Sheldon Owner, 1st Class Mobile Shine 310.909.7672 www.facebook.com/1stclassmobileshine On Mon, Apr 7, 2014 at 9:49 PM, Adam Williamson awill...@redhat.com wrote: On Mon, 2014-04-07 at 20:20 -0400, Corey Sheldon wrote: its now grub2-install /dev/sdX It's not for UEFI. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Tue, Apr 8, 2014 at 4:49 AM, Adam Williamson awill...@redhat.com wrote: On Mon, 2014-04-07 at 20:20 -0400, Corey Sheldon wrote: its now grub2-install /dev/sdX It's not for UEFI. -- It would be good if someone who knows something could rewrite the GRUB_2 wiki page to say that. And to stop referring to a release of Fedora that is no longer supported. The Unified Extensible Firmware Interface wiki page is rather outdated and unhelpful as well. Surprisingly, the best information I could find about efibootmgr is in a page that is actually about Fedup. Here's what I've discovered: If you have UEFI and you have run grub2-install, you need to un-do that by re-installing grub2-efi: yum reinstall grub2-efi And since Windows on my system places itself first in the EFI boot list every time it is booted, you need to run efibootmgr -v # (to learn Fedora's boot number) efibootmgr -o boot#1,boot#2,... # (to choose which system you want to boot by default) If you want to see how Anaconda originally ran efibootmgr, you can look at /var/log/anaconda/anaconda.program.log Fred -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Mon, 2014-04-07 at 23:54 -0400, Corey Sheldon wrote: grub2 is the default now with or without uefi But you don't run grub2-install on a UEFI native installation of Fedora. UEFI boot loading does not involve a bootloader installed in that manner. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
So just to refresh my understanding of your setup: you have a non-bootable system with a standard uefi dual-boot? and you can't seem to get the bootloader (grub) to re-install Corey W Sheldon Owner, 1st Class Mobile Shine 310.909.7672 www.facebook.com/1stclassmobileshine On Tue, Apr 8, 2014 at 12:16 AM, Fred New fred.new2...@gmail.com wrote: On Tue, Apr 8, 2014 at 4:49 AM, Adam Williamson awill...@redhat.comwrote: On Mon, 2014-04-07 at 20:20 -0400, Corey Sheldon wrote: its now grub2-install /dev/sdX It's not for UEFI. -- It would be good if someone who knows something could rewrite the GRUB_2 wiki page to say that. And to stop referring to a release of Fedora that is no longer supported. The Unified Extensible Firmware Interface wiki page is rather outdated and unhelpful as well. Surprisingly, the best information I could find about efibootmgr is in a page that is actually about Fedup. Here's what I've discovered: If you have UEFI and you have run grub2-install, you need to un-do that by re-installing grub2-efi: yum reinstall grub2-efi And since Windows on my system places itself first in the EFI boot list every time it is booted, you need to run efibootmgr -v # (to learn Fedora's boot number) efibootmgr -o boot#1,boot#2,... # (to choose which system you want to boot by default) If you want to see how Anaconda originally ran efibootmgr, you can look at /var/log/anaconda/anaconda.program.log Fred -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Tue, 2014-04-08 at 00:27 -0400, Corey Sheldon wrote: So just to refresh my understanding of your setup: Neither I nor Fred are the original poster who had the problem. He hasn't posted to this thread since Thursday. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
is that a fair understanding as you know the issue? Corey W Sheldon Owner, 1st Class Mobile Shine 310.909.7672 www.facebook.com/1stclassmobileshine On Tue, Apr 8, 2014 at 12:31 AM, Adam Williamson awill...@redhat.comwrote: On Tue, 2014-04-08 at 00:27 -0400, Corey Sheldon wrote: So just to refresh my understanding of your setup: Neither I nor Fred are the original poster who had the problem. He hasn't posted to this thread since Thursday. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reinstalling the bootloader
On Tue, 2014-04-08 at 07:16 +0300, Fred New wrote: The Unified Extensible Firmware Interface wiki page is rather outdated and unhelpful as well. In what way? I wrote it, just a month or two ago. I'm not aware of anything in it which is outdated. If you have UEFI and you have run grub2-install, you need to un-do that by re-installing grub2-efi: yum reinstall grub2-efi That won't 'undo' anything. The grub2-efi package doesn't actually have any scripts, so reinstalling it doesn't really do anything much. And since Windows on my system places itself first in the EFI boot list every time it is booted, That's likely an issue in your system's firmware or Windows install (somehow). It shouldn't be doing that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: rawhide report: 20140404 changes
It is definitely useful, but I wish there was some way of excluding long-standing problems that no one cares to fix. It might be nice if there was a counter for how many weeks they have been broken, though probably a bit harder to implement. Jens -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
File Sys-Virt-1.2.3.tar.gz uploaded to lookaside cache by berrange
A file has been added to the lookaside cache for perl-Sys-Virt: 89f462785d77b0822f13d6e7b5e3a30c Sys-Virt-1.2.3.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Sys-Virt] Update to 1.2.3 release
commit b8376d7612d59902bd20a18589dde6c94defdbd3
Author: Daniel P. Berrange berra...@redhat.com
Date: Mon Apr 7 12:05:56 2014 +0100
Update to 1.2.3 release
perl-Sys-Virt.spec |5 -
sources|2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-Sys-Virt.spec b/perl-Sys-Virt.spec
index 6f791d9..e1257c4 100644
--- a/perl-Sys-Virt.spec
+++ b/perl-Sys-Virt.spec
@@ -1,7 +1,7 @@
# Automatically generated by perl-Sys-Virt.spec.PL
Name: perl-Sys-Virt
-Version:1.2.2
+Version:1.2.3
Release:1%{?dist}%{?extra_release}
Summary:Represent and manage a libvirt hypervisor connection
License:GPLv2+ or Artistic
@@ -59,6 +59,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Mon Apr 7 2014 Daniel P. Berrange berra...@redhat.com - 1.2.3-1
+- Update to 1.2.3 release
+
* Mon Mar 3 2014 Daniel P. Berrange berra...@redhat.com - 1.2.2-1
- Update to 1.2.2 release
diff --git a/sources b/sources
index a0031ba..c74ff6b 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-acfaf1fb0e2d708522458b97eb28bcd3 Sys-Virt-1.2.2.tar.gz
+89f462785d77b0822f13d6e7b5e3a30c Sys-Virt-1.2.3.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Frontier-RPC] Modernize the spec file
commit 64d69aac8a4a90994d8862ad54f8ffeabff17b62
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 7 14:08:51 2014 +0200
Modernize the spec file
perl-Frontier-RPC.spec | 42 --
1 files changed, 20 insertions(+), 22 deletions(-)
---
diff --git a/perl-Frontier-RPC.spec b/perl-Frontier-RPC.spec
index 118323d..7befd3f 100644
--- a/perl-Frontier-RPC.spec
+++ b/perl-Frontier-RPC.spec
@@ -11,19 +11,30 @@ Patch1: perl-frontier-raw-serve.patch
Patch2: perl-frontier-undef-scalar.patch
Patch3: security-xml-external-entity.patch
Patch4: apache2.patch
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
-BuildRequires: perl(LWP::UserAgent), perl(XML::Parser),
perl(ExtUtils::MakeMaker)
-Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
-Requires: perl-Frontier-RPC-doc
+BuildRequires: perl
+BuildRequires: perl(ExtUtils::MakeMaker)
+# Run-time:
+# Apache2::Const not used at tests
+# Apache2::ServerUtil not used at tests
+BuildRequires: perl(HTTP::Daemon)
+BuildRequires: perl(HTTP::Request)
+BuildRequires: perl(HTTP::Status)
+BuildRequires: perl(LWP::UserAgent)
+BuildRequires: perl(MIME::Base64)
+BuildRequires: perl(strict)
+BuildRequires: perl(vars)
+BuildRequires: perl(XML::Parser)
+Requires: perl(:MODULE_COMPAT_%(eval `perl -V:version`; echo $version))
+Requires: perl-Frontier-RPC-doc =
%{?epoch:%{epoch}:}%{version}-%{release}
%package Client
Summary:Frontier-RPC-Client Perl module
Group: Development/Libraries
License:GPL+ or Artistic
-Requires: perl-Frontier-RPC-doc
+Requires: perl-Frontier-RPC-doc =
%{?epoch:%{epoch}:}%{version}-%{release}
-# fix conflicts between those two packages
+# To solve conflicts between those two packages
%package doc
Summary:Frontier-RPC-Client Perl module documentation
Group: Development/Libraries
@@ -53,45 +64,32 @@ Documentation and examples to Frontier::RPC and
Frontier::RPC::Client.
%patch4 -p1
%build
-%{__perl} Makefile.PL INSTALLDIRS=vendor
+perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
-rm -rf $RPM_BUILD_ROOT
-
make pure_install DESTDIR=$RPM_BUILD_ROOT
-
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
-
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
-%clean
-rm -rf $RPM_BUILD_ROOT
-
%files
-%defattr(-,root,root,-)
%{perl_vendorlib}/*
%files Client
-%defattr(-,root,root,-)
%{perl_vendorlib}/Frontier/Client.pm
%{perl_vendorlib}/Frontier/RPC2.pm
%files doc
-%defattr(-,root,root,-)
%doc ChangeLog Changes COPYING README examples/
%{_mandir}/man3/*
%changelog
* Mon Apr 07 2014 Petr Pisar ppi...@redhat.com - 0.07b4p1-20
-- Rebase perl-frontier-raw-call.patch to suppress *.orig files
-- Rebase perl-frontier-undef-scalar.patch to suppress *.orig files
-- Rebase apache2.patch to suppress *.orig files
-- Rebase security-xml-external-entity.patch to suppress *.orig files
+- Rebase patches to suppress creating *.orig files
+- Modernize the spec file
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.07b4p1-19
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Frontier-RPC] Rebase patches to suppress creating *.orig files
commit 21e0bfccb5f4f6896cb57f9cc317283e1c3998ce
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 7 13:45:13 2014 +0200
Rebase patches to suppress creating *.orig files
apache2.patch | 46 +---
perl-Frontier-RPC.spec |8 +-
perl-frontier-raw-call.patch | 26 +---
perl-frontier-undef-scalar.patch | 24 --
security-xml-external-entity.patch | 27 +
5 files changed, 104 insertions(+), 27 deletions(-)
---
diff --git a/apache2.patch b/apache2.patch
index 5cd9ebb..ad9a27a 100644
--- a/apache2.patch
+++ b/apache2.patch
@@ -1,47 +1,65 @@
Frontier-RPC-0.07b4p1/lib/Apache/XMLRPC.pm.apache2 2007-11-08
17:01:28.0 +0100
-+++ Frontier-RPC-0.07b4p1/lib/Apache/XMLRPC.pm 2007-11-08 17:24:46.0
+0100
-@@ -10,16 +10,18 @@
+From a6259081437a560451c0b6830204e1d81288e46a Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Mon, 7 Apr 2014 13:53:40 +0200
+Subject: [PATCH] Apache2 support
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
- package Apache::XMLRPC;
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/Apache/XMLRPC.pm | 21 -
+ 1 file changed, 12 insertions(+), 9 deletions(-)
+diff --git a/lib/Apache/XMLRPC.pm b/lib/Apache/XMLRPC.pm
+index 1f2aec7..a9f16d2 100644
+--- a/lib/Apache/XMLRPC.pm
b/lib/Apache/XMLRPC.pm
+@@ -10,16 +10,18 @@
+
+ package Apache::XMLRPC;
+
-use Apache::Constants qw(:common);
+use Apache2::Const;
+use Apache2::ServerUtil;
use Frontier::RPC2;
-
+
sub handler {
my $r = shift;
-
+
- my $conf = $r-server_root_relative( $r-dir_config( XMLRPC_Config ) );
+ my $path = $r-dir_config( XMLRPC_Config );
+ my $conf = Apache2::ServerUtil::server_root_relative( $r-pool, $path );
-
+
if( -f $conf ) {
- unless( $rt = do $conf ) {
+ unless( my $rt = do $conf ) {
die Couldn\'t parse conf file ($conf): $@\n if $@;
die Couldn\'t compile conf file ($conf): $!\n unless defined $rt;
die Couldn\'t run conf file ($conf)\n unless $rt;
-@@ -28,15 +30,16 @@
-
+@@ -28,15 +30,16 @@ sub handler {
+
my $decoder = Frontier::RPC2-new();
-
+
- my $content;
- $r-read( $content, $r-header_in( 'Content-length' ) );
+ if (defined $clength and $clength = 0) {
+ my $content;
+ $r-read( $content, $r-headers_in-{'Content-length'} );
-
+
- my $answer = $decoder-serve( $content, $Apache::XMLRPC::map );
+my $answer = $decoder-serve( $content, $Apache::XMLRPC::map );
-
+
- $r-send_http_header();
- $r-print($answer);
+$r-print($answer);
+ }
-
+
- return OK;
+ return Apache2::Const::OK();
}
-
+
1;
+--
+1.9.0
+
diff --git a/perl-Frontier-RPC.spec b/perl-Frontier-RPC.spec
index 3cfdd18..118323d 100644
--- a/perl-Frontier-RPC.spec
+++ b/perl-Frontier-RPC.spec
@@ -1,7 +1,7 @@
Summary:A Perl interface for making and serving XML-RPC calls
Name: perl-Frontier-RPC
Version:0.07b4p1
-Release:19%{?dist}
+Release:20%{?dist}
License:GPL+ or Artistic
Group: Development/Libraries
URL:http://search.cpan.org/dist/Frontier-RPC/
@@ -87,6 +87,12 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Mon Apr 07 2014 Petr Pisar ppi...@redhat.com - 0.07b4p1-20
+- Rebase perl-frontier-raw-call.patch to suppress *.orig files
+- Rebase perl-frontier-undef-scalar.patch to suppress *.orig files
+- Rebase apache2.patch to suppress *.orig files
+- Rebase security-xml-external-entity.patch to suppress *.orig files
+
* Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.07b4p1-19
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
diff --git a/perl-frontier-raw-call.patch b/perl-frontier-raw-call.patch
index f989e92..7b69ad9 100644
--- a/perl-frontier-raw-call.patch
+++ b/perl-frontier-raw-call.patch
@@ -1,6 +1,21 @@
Frontier-RPC-0.06/lib/Frontier/Client.pm.orig Sat Nov 20 19:13:21 1999
-+++ Frontier-RPC-0.06/lib/Frontier/Client.pm Wed Dec 19 18:42:55 2001
-@@ -50,6 +50,26 @@
+From aa8833ac7d92fa9d9903a849420dcffc33a00974 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com
+Date: Mon, 7 Apr 2014 13:42:03 +0200
+Subject: [PATCH] Add Frontier::Client::raw_call subroutine
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/Frontier/Client.pm | 34 +-
+ 1 file changed, 21 insertions(+), 13 deletions(-)
+
+diff --git a/lib/Frontier/Client.pm b/lib/Frontier/Client.pm
+index 800acab..6ea7b60 100644
+--- a/lib/Frontier/Client.pm
b/lib/Frontier/Client.pm
+@@ -55,6 +55,26 @@ sub new {
sub call {
my $self = shift;
@@ -27,7
[perl-Log-Dispatch] Build-require a sendmail program for tests
commit 43bf8908182acf16b20816589e973a9989c0dccb
Author: Petr Písař ppi...@redhat.com
Date: Mon Apr 7 15:16:54 2014 +0200
Build-require a sendmail program for tests
perl-Log-Dispatch.spec |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
---
diff --git a/perl-Log-Dispatch.spec b/perl-Log-Dispatch.spec
index 931cada..20a7c14 100644
--- a/perl-Log-Dispatch.spec
+++ b/perl-Log-Dispatch.spec
@@ -11,7 +11,7 @@
Name: perl-Log-Dispatch
Version:2.41
-Release:1%{?dist}
+Release:2%{?dist}
Summary:Dispatches messages to one or more outputs
Group: Development/Libraries
License:Artistic 2.0
@@ -40,6 +40,9 @@ BuildRequires: perl(warnings)
# testsuite
BuildRequires: perl(Test::More) = 0.88
+# If LOG_DISPATCH_TEST_EMAIL is passed to tests, a sendmail will be needed,
+# bug #1083418
+BuildRequires: %{_sbindir}/sendmail
%if %{with release_tests}
# for improved tests
@@ -96,6 +99,9 @@ make test %{?with_release_tests:RELEASE_TESTING=1}
LOG_DISPATCH_TEST_EMAIL=root
%{_mandir}/man3/*.3pm*
%changelog
+* Mon Apr 07 2014 Petr Pisar ppi...@redhat.com - 2.41-2
+- Build-require a sendmail program for tests (bug #1083418)
+
* Fri Aug 16 2013 Ralf Corsépius corse...@fedoraproject.org - 2.41-1
- Upstream update.
- Spec cleanup.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Bug 1083418] perl-Log-Dispatch-2.41-1.fc21 FTBFS
https://bugzilla.redhat.com/show_bug.cgi?id=1083418 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Log-Dispatch-2.41-2.fc ||21 Resolution|--- |RAWHIDE Last Closed||2014-04-07 09:32:24 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RQegA8la6ga=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the rawhide tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-Catalyst-Controller-HTML-FormFu
perl-Catalyst-Controller-HTML-FormFu has broken dependencies in the rawhide tree: On x86_64: perl-Catalyst-Controller-HTML-FormFu-0.09004-4.fc20.noarch requires perl(HTML::FormFu::MultiForm) On i386: perl-Catalyst-Controller-HTML-FormFu-0.09004-4.fc20.noarch requires perl(HTML::FormFu::MultiForm) On armhfp: perl-Catalyst-Controller-HTML-FormFu-0.09004-4.fc20.noarch requires perl(HTML::FormFu::MultiForm) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: perl-GnuPG-Interface
perl-GnuPG-Interface has broken dependencies in the rawhide tree: On x86_64: perl-GnuPG-Interface-0.50-1.fc21.noarch requires perl(MooX::late) On i386: perl-GnuPG-Interface-0.50-1.fc21.noarch requires perl(MooX::late) On armhfp: perl-GnuPG-Interface-0.50-1.fc21.noarch requires perl(MooX::late) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Broken dependencies: mojomojo
mojomojo has broken dependencies in the rawhide tree: On x86_64: mojomojo-1.10-1.fc20.noarch requires perl(HTML::FormFu::Element::reCAPTCHA) On i386: mojomojo-1.10-1.fc20.noarch requires perl(HTML::FormFu::Element::reCAPTCHA) On armhfp: mojomojo-1.10-1.fc20.noarch requires perl(HTML::FormFu::Element::reCAPTCHA) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[389-devel] Source directory is now list-able
http://port389.org/sources is now open and list-able. The default sort order is latest first. The http://port389.org/wiki/Source page has been updated with this link. -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: Project Locations and Basic Setup
On Mon, Apr 07, 2014 at 03:19:41AM -0400, Martin Krizek wrote: - Original Message - From: Tim Flink tfl...@redhat.com To: qa-devel@lists.fedoraproject.org Sent: Friday, April 4, 2014 4:50:25 PM Subject: Project Locations and Basic Setup I think most of this came up in an earlier thread but I'm not finding it right now, so I'm starting a new one. I'm proposing that we make all the taskotron-related projects as similar as we can with regard to git repo setup, location and how we do reviews. If we keep them all slightly different, it makes asking for contributions more difficult and the contributions guide (which still needs to be written :-/) more complicated. To be specific, the repos that I'm including in this are: - libtaskotron - taskotron-trigger - resultsdb - resultsdb_frontend - resultsdb_api - pytap13 - fake_fedorainfra The settings that I'm proposing for all those repos are: - use gitflow and set 'develop' as the default branch - host projects under bitbucket/fedoraqa * makes it easier to say find our projects at this url instead of find projects X,Y and Z here. find A and B here - code submissions and issues/tasks are tracked through phabricator Any objections to doing this to all the repos I mentioned? No objections. In addition, we need to make sure that each repo has its .arcconfig file with correct project_id. No objections. pgpwP4JzpzA7c.pgp Description: PGP signature ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: qa host firmware updates
On Fri, 4 Apr 2014 11:42:02 -0600 Tim Flink tfl...@redhat.com wrote: Since nobody is using beaker at the moment, I'm going to tackle that host next. It should be back up by the end of the day. I'll update the thread when I've finished all the upgrades. As a progress update, all of the non-autoqa-production hosts have been updated and I'm starting on the 3 autoqa production hosts. This means that we'll be operating at a lower-than-normal capacity until everything is done. All the tests should continue to run but the rate at which they're executed will be slower. Tim signature.asc Description: PGP signature ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Summary of accepted Fedora 21 Changes - weeks 13/14
Greetings! This is a summary of FESCo's accepted Fedora 21 Changes for weeks 13 and 14 (2014-03-26 and 2014-04-02 meetings). Reminder: the Change Submission deadline for System Wide Change is tomorrow (2014-04-08 23:59 UTC). =Accepted changes= == System Wide Changes == * Modular Kernel Packaging for Cloud URL: https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196807.html Kernel modules that are not necessary in virtualized environments become optionally (un)installable. * Optional Javadocs URL: https://fedoraproject.org/wiki/Changes/OptionalJavadocs Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196808.html Make javadoc subpackages of Java packages optional in guidelines and communicate this change to users. * Ruby on Rails 4.1 URL: https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1 Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196803.html Ruby on Rails 4.1 is the latest version of well know web framework written in Ruby. * Java 8 URL: https://fedoraproject.org/wiki/Changes/Java8 Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/196962.html Make Java 8 (provided by OpenJDK 8 which is java-1.8.0-openjdk) the default Java runtime. The current default Java runtime (Java 7, provided by OpenJDK 7, java-1.7.0-openjdk) will be obsoleted and removed. This is essentially an upgrade to the latest Java and OpenJDK version. * PrivateDevices=yes and PrivateNetwork=yes For Long-Running Services URL: https://fedoraproject.org/wiki/Changes/PrivateDevicesAndPrivateNetwork Announcement: https://lists.fedoraproject.org/pipermail/devel/2014-March/197175.html Let's make Fedora more secure by default! Recent systemd versions provide two per-service switches PrivateDevices?=yes/no and PrivateNetwork?=yes/no which enable services to run without access to any physical devices in /dev, or without access to kind of network sockets. So far this has seen little use in Fedora, and with this Fedora Change we'd like to change this, and enable these for all long-running services that do not require device/network access. notting has question to note: is disconnecting the netlink and audit namespace truly required, or just merely a choice of what they decided to remove? == Self Contained Changes == * Amplab Tachyon - https://fedoraproject.org/wiki/Changes/AmplabTachyon discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197168.html Amplab-Tachyon is a fault tolerant distributed file system enabling reliable file sharing at memory-speed across cluster frameworks. * Apache Mesos - https://fedoraproject.org/wiki/Changes/ApacheMesos discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197180.html Apache Mesos is a cluster manager for sharing distributed application frameworks. This change brings Mesos to Fedora, which many have called a micro-kernel for the data center. * Apache Spark - https://fedoraproject.org/wiki/Changes/ApacheSpark discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196967.html Apache Spark is a fast and general engine for large-scale data processing. This change brings Spark to Fedora, allowing easy deployment and development of Spark applications on Fedora. * Improved Scala Ecosystem Support - https://fedoraproject.org/wiki/Changes/ImprovedScalaEcosystem discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196964.html Fedora now supports several essential parts of the Scala language ecosystem as well as building packages with sbt, the de facto build tool for the Scala community. Scala proposal owners to work to develop packaging guidelines * DNSSEC support for FreeIPA - https://fedoraproject.org/wiki/Changes/IPAv3DNSSEC discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197177.html FreeIPA with integrated DNS server will support serving of DNSSEC secured zones and automatic DNSSEC key maintenance. This first version will have only the very basic functionality with limited user interface and limited resiliency. Next versions (to be delivered in Fedora 22 time frame) will improve resiliency and user interface significantly. * NFS Ganesha File Server - https://fedoraproject.org/wiki/Changes/NFSGanesha discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196968.html NFS Ganesha is a user mode file server that supports NFSv3, NFSv4, and NFSv4.1 including pNFS for distributed filesystems. It uses loadable filesystem driver modules to support its backend filesystems. It also integrates 9P.2000L file service = Rejected Changes = * Security Policy In The Installer URL: https://fedoraproject.org/wiki/Changes/SecurityPolicyInTheInstaller Announcement:
