Re: [Base] Base Design WG agenda meeting 8st June 2015 14:15 UTC on #fedora-meeting-2

[Václav Pavlín]

Hi,

Sorry for not being able to join last meeting - I had a training:( I 
won't be able to attend next meeting - I am traveling to US, but if you 
are going to vote about lnykryn joining the WG, please consider me 
voting *+1*.


Thanks,
Vašek

On 06/08/2015 04:58 PM, Harald Hoyer wrote:

On 08.06.2015 10:29, Harald Hoyer wrote:

*IMPORTANT*: #fedora-meeting-2 ... I repeat: *two*

Agenda:
  - Interview candidates for new memberships
  - Optionally accept new members
  - Status - Docker
  - Status - BuildRequires
  - Open Floor

Please add items by replying to this mail.



Minutes:


Minutes (text):


Log:



--

Lead Infrastructure Engineer
Developer Experience
Brno, Czech Republic
Phone: +420 739 666 824

--
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: New contributor looking for Python projects/packages...

[Josef Stribny]

On 06/09/2015 11:38 PM, Alex G.S. wrote:

Devel,

Fedora is my favorite Linux distribution by a wide margin and I 
currently enjoy Workstation on both my work (devops) and home 
computer.  I've started working with Python and I want to contribute 
back to Fedora by taking on small tasks where needed.  Can you suggest 
a list of Python based/oriented components or packages that really 
need developers/maintainers and aren't too overwhelming or complex for 
a first-time contributor?  Also is there a person you suggest I reach 
out to as a point of contact for new contributors?


Thank you!

Best,
Alexander GS




Hi Alexander,

I would suggest to ask on Fedora Python's SIG[0] mailing list.

Regards
Josef

[0] https://fedoraproject.org/wiki/SIGs/Python
-- 
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: New contributor looking for Python projects/packages...

[Miroslav Suchý]

Dne 9.6.2015 v 23:38 Alex G.S. napsal(a):
> Devel,
> 
> Fedora is my favorite Linux distribution by a wide margin and I currently 
> enjoy Workstation on both my work (devops) and
> home computer.  I've started working with Python and I want to contribute 
> back to Fedora by taking on small tasks where
> needed.  Can you suggest a list of Python based/oriented components or 
> packages that really need developers/maintainers
> and aren't too overwhelming or complex for a first-time contributor?  Also is 
> there a person you suggest I reach out to
> as a point of contact for new contributors?

You can help doing reviews:
https://fedoraproject.org/wiki/Package_Review_Process
http://fedoraproject.org/PackageReviewStatus/NEW.html
There is 48 *python* packages waiting for review.

Of course you need to be a packager first to finish a review. So you may 
package something which is not in Fedora yet.
Check this wish list:
https://fedoraproject.org/wiki/Package_maintainers_wishlist?rd=PackageMaintainers/WishList

Or you can become a co-maintainer first and the Python SIG - as suggested by 
Josef - is the right place to start.
-- 
Miroslav Suchy, RHCA
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: New contributor looking for Python projects/packages...

[Pierre-Yves Chibon]

On Tue, Jun 09, 2015 at 05:38:01PM -0400, Alex G.S. wrote:
>Devel,
>Fedora is my favorite Linux distribution by a wide margin and I currently
>enjoy Workstation on both my work (devops) and home computer.A  I've
>started working with Python and I want to contribute back to Fedora by
>taking on small tasks where needed.A  Can you suggest a list of Python
>based/oriented components or packages that really need
>developers/maintainers and aren't too overwhelming or complex for a
>first-time contributor?A  Also is there a person you suggest I reach out
>to as a point of contact for new contributors?

Hi,

Welcome!

The Fedora Infrastructure is also mostly a python shop, so feel free to have a
look there if there are projects you would like to get involved in.
http://fedoraproject.org/easyfix/ might be a start to get some ideas of simple
tasks that can be addressed by new contributors.

If you need more details, feel free to ask :)

Pierre
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

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

[Parag Nemade]

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
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-06-10 18:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =
#topic #1445 F23 Self Contained Changes
.fesco 1445https://fedorahosted.org/fesco/ticket/1445

 = New business =

#topic #1447 F23 System Wide Change: Default Local DNS Resolver
.fesco 1447https://fedorahosted.org/fesco/ticket/1447

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found
athttps://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

jna license fixed

[Mikolaj Izdebski]

License field of "jna" package in rawhide has been corrected from
"LGPLv2+" to "LGPLv2 or ASL 2.0" to match upstream licensing terms.

-- 
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
-- 
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: Better irc policies?

[Chaoyi Zha]

Maybe we can use ASM and fedbot to reduce the spam load? Dedicated spammers
are definitely a problem for all channels, but most channels, such as
#freenode enable +r during a wave of flood, not indefinitely.

I can absolutely agree that having the registration requirement flag
certainly increases the barrier to something newbies or those "trying out"
may not be willing to commit. They may just give up instead of registering
and getting help. I personally try to avoid things that require email sign
ups as much as possible, and I know others do too.

On Tue, Jun 9, 2015, 1:45 PM Kevin Fenzi  wrote:

> On Tue, 9 Jun 2015 19:31:01 +0200
> Andreas Tunek  wrote:
>
> > Currently the #fedora channel on freenode requires some kind of
> > registration.
>
> Yeah. It has for many years...
>
> > In my opinion it is pretty difficult to register on
> > freenode (I have tried but haven't managed).
>
> What part of the process is proving to be difficult?
> If you aren't registered and try and join #fedora it sends you to
> #fedora-unregistered where the entry message, topic and a bot all give
> you links showing how to register.
> Is there something that could be more clear here?
>
> > Do you think it would be
> > possible to drop the registration requirement? It is a pretty big
> > barrier to newbies and people like me who can't find IRC help easily.
> > I know there are a lot of bots and spam, but maybe it would be
> > possible to try and see if it really gets bad?
>
> Well, you are welcome to file a ticket and request that with the irc
> support sig:
> https://fedorahosted.org/irc-support-sig/
>
> But I don't think it's too likely to happen for a lot of reasons:
>
> * Originally the registration was put in place when there were floods
>   of racist ranter bots on freenode. They are much less common now, but
>   I still see them in unregistered from time to time.
>
> * There's also a lot of drive by spam and trollers that get caught by
>   registration.
>
> kevin
>
> --
> 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: New contributor looking for Python projects/packages...

[Stephen Gallagher]

On Tue, 2015-06-09 at 17:38 -0400, Alex G.S. wrote:
> Devel,
> 
> Fedora is my favorite Linux distribution by a wide margin and I 
> currently enjoy Workstation on both my work (devops) and home 
> computer.  I've started working with Python and I want to contribute 
> back to Fedora by taking on small tasks where needed.  Can you 
> suggest a list of Python based/oriented components or packages that 
> really need developers/maintainers and aren't too overwhelming or 
> complex for a first-time contributor?  Also is there a person you 
> suggest I reach out to as a point of contact for new contributors?
> 
> Thank you!
> 
> Best,
> Alexander GS 
> 

The rolekit project[1] is a Python project and a key component of the
Fedora Server deliverables. We're just starting on our F23 efforts. If
you're interested in participating, come by #fedora-server on Freenode
IRC.

[1] https://sgallagh.wordpress.com/2014/12/11/rolekit-or-how-i-learned
-to-stop-thinking-in-terms-of-packages/

signature.asc
Description: This is a digitally signed message part
-- 
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: DKMS is not installing the right kernel-devel package

[Dan Book]

On Wed, Jun 10, 2015 at 2:12 AM, Thorsten Leemhuis 
wrote:

> Dan Book wrote on 09.06.2015 22:01:
> > This has also been a problem for several releases with the akmods from
> > rpmfusion.
>
> There was always a problem; there where just less people running into
> it, because yum/dnf installed "kernel-devel" most of the time, which
> matched the kernel that was running on most systems; but quite a few
> x86-32 users ran into problems afaics, as kernel-PAE get's installed
> there sometimes and hence they needed kernel-PAE-devel.
>
> Mosts of the docs and howtos on the net don't mention that, which leads
> to confused and frustrating users; those in the end might be one of
> multiple problems why they switch to another distribution.
>
> > I think the more "correct" solution (read to the end) would
> > be to somehow prioritize the kernel-devel package (possibly multiple)
> > that matches the installed kernel(s).
>
> That's not a solution, that's solving the problem for some users and
> ignoring others (those that use kernel-PAE for example).
>

"The kernel-devel package that matches the installed kernel(s)" would
include kernel-PAE-devel matching kernel-PAE, in this fantasy land I
invented.


>
> > [...]
>
> CU
> thl
>

-Dan


>
> > On Tue, Jun 9, 2015 at 3:41 PM, Thorsten Leemhuis  > > wrote:
> >
> > On 09.06.2015 21:04, Neal Gompa wrote:
> > > I've noticed that when dkms is installed, it's not grabbing the
> right
> > > kernel-devel package as a dependency.
> >
> > Because that's not possible with ordinary dependencies (might be
> > possible with soft dependencies [Suggests, Enhances etc]) unless we
> > change something in the kernel packaging (see below).
> >
> > > Instead, it grabs
> > > kernel-debug-devel. This occurs on Fedora 21 and 22, and I'm not
> sure
> > > why.
> >
> > Because all kernel*devel package provide kernel-devel iirc.
> >
> > > Anyone have any idea why this is happening and a way to work
> around it?
> >
> > Create something like a meta-package "kernel-devel-all" that depends
> on
> > all available kernel-devel packages (kernel-devel, kernel-PAE-devel,
> > kernel-debug-devel, ...) for the arch in question; then add
> "Requires:
> > kernel-devel-all" to the akmods and dkms packages. That's messy and
> > creates overhead for users, but that's afaics the only way it will
> work
> > for everyone; otherwise you'll always run into situations where a
> > kernel-devel package for one kernel variant gets installed while you
> are
> > running different variant. Example: You get kernel-devel via some
> > dependency in akmods or dkms; but you are running kernel-PAE on your
> > i686 machine, so building modules with akmods or dkms will fail, as
> > that's requires kernel-PAE-devel.
> >
> > HTH; CU, knurd
> > --
> > 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
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

f22 screensaver/lockout issue requiring reboot :/

[Paul Wouters]

Hi,

Am I the only one who is constantly locked out of their X session on
fedora 22? Once the screen locks, it refuses my actual password to
unlock. Even killing X with ctrl-alt-backspace doesn't help because
it will just startup again in locked screen mode. I basically have
to reboot every time my screen locks. And yes, the screensaver
preferences even have "lock screen after" unselected but my screen
gets locked anyway.

I originally upgraded from f19 to f22beta, and even upgraded to 
updates-testing which did not help.


Already tried the rm -rf .gnome* trick in case my f19 settings were
interfering.

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

F23 System Wide Change: Python 3 as Default

[Jan Kurik]

= Proposed System Wide Change: Python 3 as Default =
https://fedoraproject.org/wiki/Changes/Python_3_as_Default

Change owner(s):
* Slavek Kabrda 
* Matej Stuchlik 
* Miro Hroncok 
* Thomas Spura 
* Robert Kuska 

Up until now, Fedora has used Python 2 as the default Python implementation. 
This change proposes switching to Python 3. The details of the term "switching" 
are explained thoroughly in the Scope section. 

== Detailed Description ==
Python 3 is the next generation of Python programming language. It is currently 
mature and stable, since it has been under active development for five years - 
version 3.0 was released in December 2008, current latest stable version is 
3.4.3 released in February 2015. The main reason to switch to Python 3 as the 
default implementation is that Python 2 is in maintenance mode, thus only 
bugfixes and security fixes are accepted upstream. Further reasons are 
mentioned in the Benefit to Fedora section. For this Change to be carried out 
successfully, it is necessary that the key packages in the Fedora software 
stack be ported to Python 3. These are parts of the minimal buildroot, the 
default package manager, programs present on the LiveCD etc. 

== Scope ==
The main goal is switching to Python 3 as a default, in which state:
* DNF is the default package manager instead of Yum, which only works with 
Python 2
* Python 3 is the only Python implementation in the minimal buildroot 
(already done since F22)
* Python 3 is the only Python implementation on the Workstation LiveDVD
* Python 3 is the only Python implementation in minimal cloud image
* Python 3 is the only Python implementation in Atomic host
* It'd also be nice to have Python 3 as the only implementation on the 
Server LiveDVD, but it's not likely 

Changes in packaging:
* Change definition of default python interpreter to python3.
* Change unversioned python macros to python3 (Possibly do that change in 
upstream rpm)
* All applications that use only a single python version MUST use python3 
(unless they have a good reason not to do so). 

Fate of /usr/bin/python:
* /usr/bin/python will still point to Python2 version of interpreter as 
suggested in PEP0394.
* There will be no /usr/bin/python on LiveDVD as python3 will became the 
only python interpreter shipped by default.
* Python (python2 version of the interpreter) package will be still 
available (via dnf install) and will provide /usr/bin/python. 

Work in Fedora 23 Timeframe:
* Proposal owners:
- Continue the work from F21 and F22 timeframe
- Modify comps accordingly
- Apply the changes to Python packaging guidelines 
* Other developers:
Introduce python3- subpackages where appropriate, build against Python 
3 if the package supports it 
* Release engineering:
Nothing 
* Policies and guidelines:
TODO: changes in packaging 


-- 
Jan Kuřík
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-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

F23 Self Contained Change: Containerized Server Roles

[Jan Kurik]

= F23 Self Contained Change: Containerized Server Roles =
https://fedoraproject.org/wiki/Changes/Containerized_Server_Roles

Change owner(s):
* Stephen Gallagher 

Enhance rolekit to be able to deploy Server Roles using the Nulecule Container 
Specification. 

== Detailed Description ==
In Fedora 23, rolekit will gain the ability to deploy Server Roles as 
containerized applications following the Nulecule specification. This will 
allow us to be able to isolate the roles more fully from the rest of the system 
as well as enabling these roles to be migrated to a larger, cloud-based system 
(such as the Atomic Platform). 

== Scope ==
* Proposal owners:
- Design a rolekit framework for deploying Server Roles inside a Docker 
container.
- Implement a reference role to deploy memcached.
- Time-permitting, update the Database Server Role to optionally 
operate within a container. 
* Other developers: N/A (not a System Wide Change) 
* Release engineering: N/A (not a System Wide Change) 
* Policies and guidelines: N/A (not a System Wide Change) 
* Trademark approval: N/A (not needed for this Change) 
-- 
Jan Kuřík
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-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

F23 Self Contained Change: Cockpit Domain Controller GUI

[Jan Kurik]

= F23 Self Contained Change: Cockpit Domain Controller GUI =
https://fedoraproject.org/wiki/Changes/Cockpit_Domain_Controller_GUI

Change owner(s):
* Stephen Gallagher 
* Stef Walter 

Provide a graphical mechanism for deploying a FreeIPA Domain Controller on 
Fedora Server through the Cockpit administrative console. 

== Detailed Description ==
In Fedora 21, we began shipping rolekit, an API for deploying Server Roles on 
Fedora Server. The first such role was the Domain Controller Role, powered by 
the FreeIPA project. The next phase in this effort is to allow deploying this 
role from the graphical environment provided by Cockpit, the administrative 
console for Fedora Server. 

== Scope ==
* Proposal owners:
 - Design and implement a plugin to the Cockpit Project (in JavaScript) 
that will interface with rolekit and provide the described functionality.
 - Tweak Fedora Server default settings to ensure that this functionality 
is available in a standard installation. 
* Other developers: N/A (not a System Wide Change) 
* Release engineering: N/A (not a System Wide Change) 
* Policies and guidelines: N/A (not a System Wide Change) 
* Trademark approval: N/A (not needed for this Change) 
-- 
Jan Kuřík
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-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: F23 System Wide Change: Python 3 as Default

[Colin Walters]

On Wed, Jun 10, 2015, at 08:50 AM, Jan Kurik wrote:
> 
> * Python 3 is the only Python implementation in Atomic host

That's not going to happen unless Ansible learns how to deal
with Python 3 at least:

https://lists.fedoraproject.org/pipermail/devel/2015-January/206903.html

So again, this change is very likely to be "Add Python 3 by default and port a 
lot of things" at least for the base Server and Atomic Host".  Other 
configurations like the Docker base image are more realistic to have Python 3 
only.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

jplesnik pushed to perl-indirect (master). "Perl 5.22 re-rebuild of bootstrapped packages"

[notifications]

From 89a361e7e74d2c9296009a71d9be3db7b0ca73e9 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Wed, 10 Jun 2015 15:15:52 +0200
Subject: Perl 5.22 re-rebuild of bootstrapped packages


diff --git a/perl-indirect.spec b/perl-indirect.spec
index 137d448..6cb0c16 100644
--- a/perl-indirect.spec
+++ b/perl-indirect.spec
@@ -1,6 +1,6 @@
 Name:   perl-indirect
 Version:0.35
-Release:2%{?dist}
+Release:3%{?dist}
 Summary:Lexically warn about using the indirect object syntax
 License:GPL+ or Artistic
 Group:  Development/Libraries
@@ -63,6 +63,9 @@ make test
 %{_mandir}/man3/indirect.3*
 
 %changelog
+* Wed Jun 10 2015 Jitka Plesnikova  - 0.35-3
+- Perl 5.22 re-rebuild of bootstrapped packages
+
 * Wed Jun 03 2015 Jitka Plesnikova  - 0.35-2
 - Perl 5.22 rebuild
 
-- 
cgit v0.10.2



http://pkgs.fedoraproject.org/cgit/perl-indirect.git/commit/?h=master&id=89a361e7e74d2c9296009a71d9be3db7b0ca73e9
--
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

rawhide report: 20150610 changes

[Fedora Rawhide Report]

Compose started at Wed Jun 10 05:15:03 UTC 2015
Broken deps for i386
--
[ambari]
ambari-server-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
ambari-server-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
ambari-server-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey:jersey-client)
ambari-server-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-multipart)
ambari-server-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
ambari-views-1.5.1-3.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires 
mvn(org.apache.juddi:juddi-client)
[boo]
boo-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Utilities) = 
0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Tasks) = 
0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Framework) = 
0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.DotNetTasks) = 
0:0.90.3780.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.Core) = 0:0.90.3780.0
[dmlite-plugins-memcache]
dmlite-plugins-memcache-0.5.0-7.fc20.i686 requires libprotobuf.so.8
[gambas3]
gambas3-gb-pdf-3.7.1-1.fc23.i686 requires libpoppler.so.49
[golang-googlecode-google-api-client]

golang-googlecode-google-api-go-client-devel-0-0.6.gitfc402b0.fc23.noarch 
requires golang(code.google.com/p/goauth2/oauth)
[hadoop]
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-servlet)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hadoop-common-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
hadoop-hdfs-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-hdfs-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-servlet)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-client)
hadoop-tests-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey:jersey-client)
hadoop-yarn-2.4.1-8.fc22.noarch requires 
mvn(com.sun.jersey.contribs:jersey-guice)
[hbase]
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-server)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-json)
hbase-tests-0.98.3-4.fc22.noarch requires 
mvn(com.sun.jersey:jersey-core)
[julia]
julia-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
julia-devel-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
[matreshka]
matreshka-servlet-devel-0.7.0-1.fc23.i686 requires 
matreshka-servlet-lib{?_isa} = 0:0.7.0-1.fc23
matreshka-servlet-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} = 
0:0.7.0-1.fc23
matreshka-spikedog-api-devel-0.7.0-1.fc23.i686 requires 
matreshka-spikedog-api-lib{?_isa} = 0:0.7.0-1.fc23
matreshka-spikedog-api-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} 
= 0:0.7.0-1.fc23
matreshka-spikedog-api-lib-0.7.0-1.fc23.i686 requires 
matreshka-servlet-api{?_isa} = 0:0.7.0-1.fc23

Re: f22 screensaver/lockout issue requiring reboot :/

[Przemek Klosowski]

On 06/10/2015 09:04 AM, Paul Wouters wrote:

Am I the only one who is constantly locked out of their X session on
fedora 22? Once the screen locks, it refuses my actual password to
unlock. Even killing X with ctrl-alt-backspace doesn't help because
it will just startup again in locked screen mode. I basically have
to reboot every time my screen locks. And yes, the screensaver
preferences even have "lock screen after" unselected but my screen
gets locked anyway.
I've seen a similar thing happen in a recent Ubuntu install. Try to 
'select other user' and select yourself again. Does the password work then?


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

License change for perl-Crypt-Blowfish

[Petr Pisar]

I corrected lincese declaration at perl-Crypt-Blowfish package in
Rawhide. It was "Copyright only". It's "BSD and Copyright only" now.

-- Petr

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

perl: f23-perl buildroot

[Colin Macdonald]

I'm updating some of my perl packages in rawhide.  Do I also need to 
submit those to the temporary 'f23-perl' buildroot?  If so, how?


thanks,
Colin

--
Colin Macdonald
Associate Professor
Tutorial Fellow at Oriel College
University of Oxford
--
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: f22 screensaver/lockout issue requiring reboot :/

[Ralf Corsepius]

On 06/10/2015 03:45 PM, Przemek Klosowski wrote:

On 06/10/2015 09:04 AM, Paul Wouters wrote:

Am I the only one who is constantly locked out of their X session on
fedora 22? Once the screen locks, it refuses my actual password to
unlock. Even killing X with ctrl-alt-backspace doesn't help because
it will just startup again in locked screen mode. I basically have
to reboot every time my screen locks. And yes, the screensaver
preferences even have "lock screen after" unselected but my screen
gets locked anyway.

I've seen a similar thing happen in a recent Ubuntu install. Try to
'select other user' and select yourself again. Does the password work then?


Not sure if this is the same issue or related to your issues, but I 
couldn't ssh into machines which were upgraded from f21 to f22.


In my case, "touch /.autorelabel" and rebooting to force an 
SELinux-relabel helped, which makes me believe SELinux was to blame.


Ralf




--
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: perl: f23-perl buildroot

[Petr Šabata]

On Wed, Jun 10, 2015 at 02:53:03PM +0100, Colin Macdonald wrote:
> I'm updating some of my perl packages in rawhide.  Do I also need to submit
> those to the temporary 'f23-perl' buildroot?  If so, how?
> 
> thanks,
> Colin

Nope, don't worry about it.  There's no need for you to do
anything special.

P


pgpp6H08EBbTi.pgp
Description: PGP signature
-- 
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: F23 System Wide Change: Default Local DNS Resolver

[Miloslav Trmač]

Hello,
> = Proposed System Wide Change: Default Local DNS Resolver =
> https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver 
> 
> Install a local DNS resolver trusted for the DNSSEC validation running on
> 127.0.0.1:53. This must be the only name server entry in /etc/resolv.conf.

We’ve had earlier conversations about whether the resolver being used (local, 
remote, container host) is trusted to perform DNSSEC validation. How is this 
resolved? The Change page AFAICS doesn’t say.

Do you e.g. plan to have a configuration file which tells libc/and other 
applications dealing with resolv.conf directly to know whether the resolver can 
be trusted for DNSSEC? Or is perhaps the design that any resolver in 
/etc/resolv.conf is always trusted for DNSSEC, and sysadmins need to ensure 
that this is true if they use a remote one?
Mirek
-- 
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: Better irc policies?

[Kevin Fenzi]

On Wed, 10 Jun 2015 11:18:56 +
Chaoyi Zha  wrote:

> Maybe we can use ASM and fedbot to reduce the spam load? Dedicated
> spammers are definitely a problem for all channels, but most
> channels, such as #freenode enable +r during a wave of flood, not
> indefinitely.
> 
> I can absolutely agree that having the registration requirement flag
> certainly increases the barrier to something newbies or those "trying
> out" may not be willing to commit. They may just give up instead of
> registering and getting help. I personally try to avoid things that
> require email sign ups as much as possible, and I know others do too.

Well, you signed up to this list to post this right? ;) 

kevin




pgpsjZL5eSMLU.pgp
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Schedule for Thursday's FPC Meeting (2015-06-11 16:00 UTC) Follow ups: 5

[James Antill]

 Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-06-11 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.

 Local time information (via. rktime):

2015-06-11 09:00 Thu US/Pacific PDT
2015-06-11 12:00 Thu US/Eastern EDT
2015-06-11 16:00 Thu UTC <-
2015-06-11 17:00 Thu Europe/London  BST
2015-06-11 18:00 Thu Europe/Paris  CEST
2015-06-11 18:00 Thu Europe/Berlin CEST
2015-06-11 21:30 Thu Asia/Calcutta  IST
--new day--
2015-06-12 00:00 Fri Asia/Singapore SGT
2015-06-12 00:00 Fri Asia/Hong_Kong HKT
2015-06-12 01:00 Fri Asia/Tokyo JST
2015-06-12 02:00 Fri Australia/Brisbane EST


 Links to all tickets below can be found at: 

https://fedorahosted.org/fpc/report/13

= Followups =

#topic #281 New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281

#topic #508 New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508

#topic #513 Use python -Es in shbang
.fpc 513
https://fedorahosted.org/fpc/ticket/513

#topic #533 Distinguish between packaging modules and applications
in python packaging
.fpc 533
https://fedorahosted.org/fpc/ticket/533

#topic #539 Procedure for approving package review process exceptions
.fpc 539
https://fedorahosted.org/fpc/ticket/539

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://fedorahosted.org/fpc/report/13

 If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting. 


-- 
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: Better irc policies?

[Gerald B. Cox]

On Wed, Jun 10, 2015 at 4:18 AM, Chaoyi Zha 
wrote:

> certainly increases the barrier to something newbies or those "trying out"
> may not be willing to commit.


Here are the instructions on how to register your nick:
https://freenode.net/faq.shtml#userregistration

The first thing the guide discusses is WHY you should register.

As far as procedures go, this one ranks as one of the easiest IMO.
-- 
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/Minutes from today's FESCo Meeting (2015-06-10)

[Parag Nemade]

===
#fedora-meeting: FESCO (2015-06-10)
===


Meeting started by paragan at 18:00:02 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/fedora-meeting/2015-06-10/fesco.2015-06-10-18.00.log.html
.



Meeting summary
---
* init process  (paragan, 18:00:03)

* #1445 F23 Self Contained Changes  (paragan, 18:01:52)
  * LINK: https://fedorahosted.org/fesco/ticket/1445   (paragan,
18:01:53)
  * LINK: https://fedoraproject.org/wiki/Changes/Netizen_Spin
(paragan, 18:02:23)
  * AGREED: FESCo did not see any updates on the Netizen change page
hence rejecting this change ( -7, 0, 0)  (paragan, 18:07:01)
  * LINK: https://fedoraproject.org/wiki/Changes/SystemFirmwareUpdates
(paragan, 18:07:19)
  * AGREED: https://fedoraproject.org/wiki/Changes/SystemFirmwareUpdates
change (+7, 0, 0)  (paragan, 18:10:23)

* #1447 F23 System Wide Change: Default Local DNS Resolver  (paragan,
  18:10:31)
  * LINK: https://fedorahosted.org/fesco/ticket/1447   (paragan,
18:10:33)
  * LINK:

https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver#Upgrade.2Fcompatibility_impact
(paragan, 18:11:16)
  * AGREED: F23 System Wide Change: Default Local DNS Resolver (+8 , 0,
-0)  (paragan, 18:20:51)

* Next week's chair  (paragan, 18:25:45)
  * nirik will chair next week's meeting  (paragan, 18:26:50)

* Open Floor  (paragan, 18:27:05)
  * LINK: https://fedoraproject.org/wiki/FESCo_election_policy   (nirik,
18:52:37)

Meeting ended at 18:56:01 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* nirik (52)
* paragan (45)
* thozza (33)
* rishi (23)
* sgallagh (22)
* mitr (19)
* jwb (18)
* ajax (13)
* pspacek (6)
* zodbot (6)
* jkurik (5)
* dgilmore (4)
* leigh123linux (2)
* pjones (2)



Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
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: Better irc policies?

[Andreas Tunek]

2015-06-10 20:11 GMT+02:00 Gerald B. Cox :
>
> On Wed, Jun 10, 2015 at 4:18 AM, Chaoyi Zha 
> wrote:
>>
>> certainly increases the barrier to something newbies or those "trying out"
>> may not be willing to commit.
>
>
> Here are the instructions on how to register your nick:
> https://freenode.net/faq.shtml#userregistration
>
> The first thing the guide discusses is WHY you should register.
>
> As far as procedures go, this one ranks as one of the easiest IMO.
>
>
>

This is the actual instruction for registering taken from here:
https://freenode.net/faq.shtml#nicksetup

My comments are in the <<< parts.


What is the recommended way to set up my IRC nickname?

Please follow these steps to set up your nick and configure your
client. Check off each step to make sure it's been done:

Select a permanent, master nickname. If the nickname you want is
registered but has expired, just ask a staffer and in most cases, we
will be happy to drop it for you.

Please avoid using the name of a community project or trademarked
entity, to avoid conflicts. Write down your password and be sure to
keep the sheet of paper in a safe place.

Register your IRC nick:

/msg NickServ REGISTER password yourem...@example.com

 Where do I type this? Maybe if you are an experienced irc user
you would know where, but most people in the world arent.

Replace password with a secure, unguessable password that you keep secret.

The email address that you select will not be given out by staff, and
is mainly used to allow us to help you recover the account in the
event that you forget your password. For this reason, you are required
to use a real, non-disposable, email address. Upon registering, you
will receive an email with a verification command that you will need
to run to complete the registration process. Failure to verify the
account will cause it to be automatically dropped after about 24
hours.

To keep your email address private, rather than displaying it
publicly, mark it as hidden (which is done by default for new
accounts):

/msg NickServ SET HIDEMAIL ON

It's useful, but not required, to have an alternate nick grouped to
your account. For example, if your primary nick is foo:

/nick foo_

then identify to your primary account:

/msg NickServ IDENTIFY foo password

and finally, group the new nick to your account

/msg NickServ GROUP

<< --
> 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: Better irc policies?

[Gerald B. Cox]

On Wed, Jun 10, 2015 at 12:37 PM, Andreas Tunek 
wrote:

> This is the actual instruction for registering taken from here:
> https://freenode.net/faq.shtml#nicksetup
>
>
>
>
*Same instructions my link is a paragraph above so people could
understand the why register part.*



>  Where do I type this? Maybe if you are an experienced irc user
> you would know where, but most people in the world arent.
>

*You need to look at the instructions for how to send messages using your
client.  *
-- 
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: Better irc policies?

[Chaoyi Zha]

Heh, of course, but I didn't sign up to get support. I wouldn't sign up to
a list for a one-time thing, I would need to be a bit more involved with
something to be motivated enough to sign up for a list.

On Wed, 10 Jun 2015 at 13:20 Kevin Fenzi  wrote:

> On Wed, 10 Jun 2015 11:18:56 +
> Chaoyi Zha  wrote:
>
> > Maybe we can use ASM and fedbot to reduce the spam load? Dedicated
> > spammers are definitely a problem for all channels, but most
> > channels, such as #freenode enable +r during a wave of flood, not
> > indefinitely.
> >
> > I can absolutely agree that having the registration requirement flag
> > certainly increases the barrier to something newbies or those "trying
> > out" may not be willing to commit. They may just give up instead of
> > registering and getting help. I personally try to avoid things that
> > require email sign ups as much as possible, and I know others do too.
>
> Well, you signed up to this list to post this right? ;)
>
> kevin
>
>
> --
> 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: F23 System Wide Change: Python 3 as Default

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jun 10, 2015 at 08:50:14AM -0400, Jan Kurik wrote:
> = Proposed System Wide Change: Python 3 as Default =
> https://fedoraproject.org/wiki/Changes/Python_3_as_Default
> 
> Change owner(s):
> * Slavek Kabrda 
> * Matej Stuchlik 
> * Miro Hroncok 
> * Thomas Spura 
> * Robert Kuska 
> 
> Up until now, Fedora has used Python 2 as the default Python implementation. 
> This change proposes switching to Python 3. The details of the term 
> "switching" are explained thoroughly in the Scope section. 
> 
> == Detailed Description ==
> It is currently mature and stable, since it has been under active
> development for five years
More than that, I'm sure.

> == Scope ==
> The main goal is switching to Python 3 as a default, in which state:
> * DNF is the default package manager instead of Yum, which only works 
> with Python 2
Does that mean that dnf-3 is going to become the default which is installed as 
/usr/bin/dnf?
Will "old" dnf be available as /usr/bin/dnf-2?

> Changes in packaging:
> * Change definition of default python interpreter to python3.
What does that mean?

> * Change unversioned python macros to python3 (Possibly do that change in 
> upstream rpm)
Hm, I think that this will break hundreds of packages... Not everything has
been updated to use %{__python2} or %{__python3}, and of those that haven't been
updated, many probably are not ready for switching to python3. I think it 
would be better to avoid a flag day, and simply slowly switch packages
one by one.

> * All applications that use only a single python version MUST use
>python3 (unless they have a good reason not to do so).
Do you intend to file bugs for all such packages or notify maintainers
in some other way?

Zbyszek


-- 
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: Better irc policies?

[Andreas Tunek]

2015-06-10 21:51 GMT+02:00 Gerald B. Cox :
>
> On Wed, Jun 10, 2015 at 12:37 PM, Andreas Tunek 
> wrote:
>>
>> This is the actual instruction for registering taken from here:
>> https://freenode.net/faq.shtml#nicksetup
>>
>>
>>
>
> Same instructions my link is a paragraph above so people could
> understand the why register part.
>
>
>>
>>  Where do I type this? Maybe if you are an experienced irc user
>> you would know where, but most people in the world arent.
>
>
> You need to look at the instructions for how to send messages using your
> client.
>

Yeah, you have to do a lot of quite complicated stuff before you can
register and get any support via irc. To register to this mailing list
you just send an email (or can you fill in a form as well).

/Andreas

>
>
> --
> 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: f22 screensaver/lockout issue requiring reboot :/

[Paul Wouters]

I wrote:


On 06/10/2015 09:04 AM, Paul Wouters wrote:
  Am I the only one who is constantly locked out of their X session on
  fedora 22? Once the screen locks, it refuses my actual password to
  unlock. Even killing X with ctrl-alt-backspace doesn't help because
  it will just startup again in locked screen mode. I basically have
  to reboot every time my screen locks. And yes, the screensaver
  preferences even have "lock screen after" unselected but my screen
  gets locked anyway.


Przemek Klosowski wrote:


I've seen a similar thing happen in a recent Ubuntu install. Try to 'select
other user' and select yourself again. Does the password work then?


I cannot even select "select other user". It remains greyed out. On my
laptop (f21) it turns white when I hoover over it and it works.

Ralf Corsepius wrote:


Not sure if this is the same issue or related to your issues, but I
couldn't ssh into machines which were upgraded from f21 to f22.



In my case, "touch /.autorelabel" and rebooting to force an
SELinux-relabel helped, which makes me believe SELinux was to blame.


That did not make a difference for me. Still fails.

I also tried enabling WaylandEnable=false in /etc/gdm/custom.conf to no
effect. gdm still does not start properly on boot, and when using
"startx" once the screen locks, despite disabling screensaver, all I
can do is reboot.

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: Better irc policies?

[Gerald B. Cox]

On Wed, Jun 10, 2015 at 1:27 PM, Andreas Tunek 
wrote:

> Yeah, you have to do a lot of quite complicated stuff before you can
> register and get any support via irc. To register to this mailing list
> you just send an email (or can you fill in a form as well).
>

Complicated is relative.  If you don't understand how it works, it's best
to research.  There
are many guides a google search away.

IRC can be helpful for support, but being interactive you're assuming that
someone is standing by
waiting for you to ask a question - which may or may not be the case.  IRC
is more functional for online
meetings and group discussions.  Mailing lists, forums, bugzilla, etc. are
better for support and investigation of issues.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Qt 5 private headers

[Ruslan Nigmatullin]

Hi,

I've just noticed that there are not separate packages for private headers of 
Qt 5 in Fedora but there is one for Qt 4. Also I've checked specs of some 
packages like qt5-qtdeclarative which uses private headers during the 
compilation and their rpms depends on qt5-qtbase >= ${qt5_version} instead of 
qt5-qtbase == ${qt5_version} which may be source of various errors (because Qt 
doesn't guarantee API/ABI compatibility for private headers).

Is it made on purpose and how does Fedora guarantee that nothing breaks in case 
of Qt's minor/patch updates?

-- 
Ruslan Nigmatullin
-- 
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: f22 screensaver/lockout issue requiring reboot :/

[Nathanael D. Noblet]

On Wed, 2015-06-10 at 16:39 -0400, Paul Wouters wrote:
>  gdm still does not start properly on boot, and when using
> "startx" once the screen locks, despite disabling screensaver, all I
> can do is reboot.
> 

Can you access the machine via ssh?
-- 
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: dnf install just stops - no explanation

[Nico Kadel-Garcia]

On Tue, Jun 9, 2015 at 9:41 AM, Richard Fearn  wrote:
> I've experienced the same problem with a F22 VM running in VirtualBox.
> (Is yours a VM?) Disabling IPv6 seemed to help a bit, but the problem
> never went away completely.
>
> There a few bugs that talk about similar issues, e.g.:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1206878
> https://bugzilla.redhat.com/show_bug.cgi?id=1214538
>
> There are various ideas out there for how to fix this, e.g. `dnf clean
> all`, or using LIBREPO_DEBUG=1. But none of these worked definitively
> for my VM.
>
> Regards,
>
> Richard

Mind you, yum still works
-- 
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 (2015-06-11)

[Honza Horak]

WG meeting will be at 17:00 UTC (13:00 EST, 19:00 Brno, 13:00 Boston, 
2:00+1d Tokyo, 3:00+1d Brisbane) in #fedora-meeting-2 on Freenode.


= Topics =

* Env&Stacks elections -- what questions to ask the candidates?
(https://fedoraproject.org/wiki/Elections/Questionnaire)

* gathering feedback from users

(https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-June/000809.html)

* Council Engineering update -- what topic we should we focus on as 
Fedora 23/24 goals 
(https://lists.fedoraproject.org/pipermail/env-and-stacks/2015-May/000786.html)


* RHSCL Docker images compatibility with Fedora/Atomic use cases (are 
SCL images as developed under 
https://github.com/sclorg/rhscl2dockerfile/ usable in fedora/atomic or 
do we search for something different?)


* Open Floor

--
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: F23 System Wide Change: Default Local DNS Resolver

[P J P]

   Hello Miloslav,

> On Wednesday, 10 June 2015 8:55 PM, Miloslav Trmač  wrote:
> We’ve had earlier conversations about whether the resolver being used (local,
> remote, container host) is trusted to perform DNSSEC validation. How is this
> resolved? The Change page AFAICS doesn’t say.
>
> Do you e.g. plan to have a configuration file which tells libc/and other
> applications dealing with resolv.conf directly to know whether the resolver 
> can
> be trusted for DNSSEC? Or is perhaps the design that any resolver in
> /etc/resolv.conf is always trusted for DNSSEC, and sysadmins need to ensure 
> that
> this is true if they use a remote one?

   Ummn...not any resolver in resolv.conf, but 127.0.0.1 is considered to be 
trusted. The proposed change is also to ensure that resolv.conf always has only 
127.0.0.1 entry in it; And nothing else.


Configuration changes to indicate 'trusted' character of a resolver was 
proposed to upstream glibc, but that is yet to be resolved properly.

  -> https://www.sourceware.org/ml/libc-alpha/2014-11/msg00426.html


---
Regards
   -P J P
http://feedmug.com
-- 
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: jna license fixed

[Mikolaj Izdebski]

On 06/10/2015 10:39 AM, Mikolaj Izdebski wrote:
> License field of "jna" package in rawhide has been corrected from
> "LGPLv2+" to "LGPLv2 or ASL 2.0" to match upstream licensing terms.

Further investigation showed that the actual license is:

jna: ASL 2.0 and (LGPLv2 or ASL 2.0)
jna-javadoc: ASL 2.0 and (LGPLv2 or ASL 2.0)
jna-contrib: LGPLv2 or ASL 2.0

Reasoning: Most of code is dual-licensed under either LGPL 2.1 only or
Apache License 2.0.  WeakIdentityHashMap.java was taken from Apache CXF,
which is under pure Apache License 2.0.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=988808
https://github.com/twall/jna/issues/252

-- 
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
-- 
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: Noa Resare

[Javi Roman]

Hi Noa, your knowledge about Java packaging and your interest in
Cassandra would be perfect for Fedora SIGs/bigdata [1].

[1] https://fedoraproject.org/wiki/SIGs/bigdata/packaging
--
Javi Roman


On Tue, Jun 9, 2015 at 9:07 PM, Noa Resare  wrote:
> Greetings. It seems I'm back in the fold once more, having done some tiny
> contributions to Fedora way back in the early days.
>
> I work as an engineer at Spotify in Stockholm, and for the last two years or
> so I have been involved in an effort to support the Free Software work going
> in our company.
>
> What brought me back was an interest in java packaging, and I'm very
> impressed by the effort of the Fedora project to get around the problem of
> most java development being done on top of hundreds of binary mystery jars
> of unclear origin. So I have decided to contribute a bit to that effort.
>
> Other interests include automated scalable build and test infrastructure,
> DNS, Cassandra, puppet.
>
> Some of you might have seen me or even had beer with me at conferences such
> as FOSDEM or LinuxCon. I typically wear red shoes.
>
> n
>
> --
> Spotify Free Software ombudsman. I/O Tribe.
>
> --
> 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

Build-essential packages (was: Re: [Guidelines change] Changes to the packaging guidelines)

[Florian Weimer]

On 05/21/2015 10:11 PM, Jason L Tibbitts III wrote:

> The BuildRequires section of the guidelines has been revised; the
> exceptions list is gone.  The release engineering folks are free to
> define the buildroot and rpm is free to change its dependency list.
>  * https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRequires_2
>  * 
> https://fedoraproject.org/w/index.php?title=Packaging%3AGuidelines&diff=413629&oldid=409506
>  * https://fedorahosted.org/fpc/ticket/497

Can we get a build-essential package instead that requires everything
that is needed to get a working C and C++ compiler, and run most
autoconf/automake/libtool-generated scripts (but not the autotools
themselves)?

In my opinion, it is a bad use of developer time to track what programs
exactly are called from ./configure, and how these programs match
sed/grep/coreutils.  It would also  give us a central place where we can
fix breakage due to missing packages in build roots because a
significant fraction of packages got a build-required package through an
indirect dependency.

-- 
Florian Weimer / Red Hat Product Security
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct