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

Hi guys, I am sorry I missed the meeting yesterday - I had a training I completely forgot about, but anyway, my comments to the topic(s) follow: Gathering of an information for the modularization proposal should surely be a common effort of e&s and Base - as both WGs has edditions/spins as t

yum for mock in RHEL 6?

https://fedoraproject.org/wiki/Mock#Mock_on_EL_6_and_EL_7:_Yum.2C_and_DNF I just ran into this issue and I was wondering if it's possible for this flag to be add to the default config on RHEL 6/7. Thanks, Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/ma

Re: Fedora.next PRD refresh

- Original Message - > From: "Stephen Gallagher" > To: "Server SIG" , > desk...@lists.fedoraproject.org, > devel-annou...@lists.fedoraproject.org, cl...@lists.fedoraproject.org > Sent: Tuesday, June 2, 2015 2:03:44 AM > Subject: Fedora.next PRD refresh > == Future PRD Refreshes == > S

Re: ddclient Sponsorship

> The owner doesn't necessarily need to be a sponsor. If he is willing > to > mentor you, he can open a ticket in the packager-sponsors trac to get > you > added as a co-maintainer. See here: Hey Scott, I've read that, I just assumed that he didn't want to mentor me as he didn't want the p

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 22:57 schrieb Andrew Lutomirski: On Mon, Jun 1, 2015 at 1:42 PM, drago01 wrote: On Mon, Jun 1, 2015 at 9:28 PM, Andrew Lutomirski wrote: I agree it's not essential for a server, but it can be quite helpful to work around glibc bugs. For example, I've hit https://sourceware.

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 1, 2015 at 1:42 PM, drago01 wrote: > On Mon, Jun 1, 2015 at 9:28 PM, Andrew Lutomirski wrote: >> On Mon, Jun 1, 2015 at 12:25 PM, Ryan S. Brown wrote: >>> On 06/01/2015 01:55 PM, Jason L Tibbitts III wrote: > "RSB" == Ryan S Brown writes: RSB> I disagree; for serve

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 1 Jun 2015, drago01 wrote: production. Yes, that's a glibc bug, and glibc should fix it. Nonetheless, bugs like that wouldn't matter as much if there were a local resolver. That's not how bugs should be dealt with ... if there is a bug it should be fixed where it is not duct taped thi

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 1, 2015 at 9:28 PM, Andrew Lutomirski wrote: > On Mon, Jun 1, 2015 at 12:25 PM, Ryan S. Brown wrote: >> On 06/01/2015 01:55 PM, Jason L Tibbitts III wrote: "RSB" == Ryan S Brown writes: >>> >>> RSB> I disagree; for server & cloud deployments it doesn't make sense to >>> RSB>

Reviving Fedora MIPS

specific languages - haskell, erlang, ocaml etc. I have already been playing with some of those and there is a list of issues on the wiki. Hopefully you will like Fedora MIPS back Regards, Michal [1] http://mipsfedora.imgtec.com/development/22/mips64el/images/20150601/ [2] http://mipsfedora.imgtec.com

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 21:38 schrieb Andrew Lutomirski: On Mon, Jun 1, 2015 at 12:29 PM, Chris Adams wrote: Once upon a time, Andrew Lutomirski said: I'm with Jason here. Glibc's resolver is amazingly buggy, and things break randomly and unreproducibly when this happens. A good setup would have

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 1, 2015 at 12:29 PM, Chris Adams wrote: > Once upon a time, Andrew Lutomirski said: >> I'm with Jason here. Glibc's resolver is amazingly buggy, and things >> break randomly and unreproducibly when this happens. A good setup >> would have a local resolver and glibc would be configur

Fedora.next PRD refresh

== Overview == Back at the beginning of the Fedora.next initiative when we created the working groups, we tasked them with creating "Product Requirement Documents" (PRDs) to guide the development of each of these core groups. * https://fedoraproject.org/wiki/Workstation/Workstation_PRD * http

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 21:28 schrieb Andrew Lutomirski: On Mon, Jun 1, 2015 at 12:25 PM, Ryan S. Brown wrote: A local DNS resolver would certainly be a surprise to me. Again, this comes back to the expectation that a server isn't hopping networks or running somewhere un-trusted where there's a high

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 20:30 schrieb Andrew Lutomirski: I would think that avoiding a single point of failure (your LAN nameserver) would be a *good* thing and your holy one and only resolver on localhost is not a single point of failure? in fact it would take much longer to recognize a failing and

Re: F23 System Wide Change: Default Local DNS Resolver

Once upon a time, Andrew Lutomirski said: > I'm with Jason here. Glibc's resolver is amazingly buggy, and things > break randomly and unreproducibly when this happens. A good setup > would have a local resolver and glibc would be configured to cache > nothing whatsoever. Then, if you need to pe

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 1, 2015 at 12:25 PM, Ryan S. Brown wrote: > On 06/01/2015 01:55 PM, Jason L Tibbitts III wrote: >>> "RSB" == Ryan S Brown writes: >> >> RSB> I disagree; for server & cloud deployments it doesn't make sense to >> RSB> duplicate a DNS server on *every* host, and if you care about >>

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/01/2015 01:55 PM, Jason L Tibbitts III wrote: >> "RSB" == Ryan S Brown writes: > > RSB> I disagree; for server & cloud deployments it doesn't make sense to > RSB> duplicate a DNS server on *every* host, and if you care about > RSB> DNSSEC you likely already run a trusted resolver. > >

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 21:19 schrieb Stephen Gallagher: On Mon, 2015-06-01 at 20:58 +0200, Reindl Harald wrote: so with setup a dns cache on each and every machine you fuckup your network because you introduce the same negative TTL caching affecting OSX clients for years now Harald, please modera

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 2015-06-01 at 20:58 +0200, Reindl Harald wrote: > so with setup a dns cache on each and every machine you fuckup your > network because you introduce the same negative TTL caching affecting > > OSX clients for years now Harald, please moderate your tone. It's unpleasant to the other p

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 20:30 schrieb Andrew Lutomirski: On Mon, Jun 1, 2015 at 11:02 AM, Reindl Harald wrote: Am 01.06.2015 um 19:55 schrieb Jason L Tibbitts III: "RSB" == Ryan S Brown writes: RSB> I disagree; for server & cloud deployments it doesn't make sense to RSB> duplicate a DNS server

Planned Outage: server reboots - 2015-06-03 21:00 UTC

Planned Outage: server reboots - 2015-06-03 21:00 UTC There will be an outage starting at 2015-06-03 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2015-06-03 21:00

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 1, 2015 at 11:02 AM, Reindl Harald wrote: > > Am 01.06.2015 um 19:55 schrieb Jason L Tibbitts III: >>> >>> "RSB" == Ryan S Brown writes: >> >> >> RSB> I disagree; for server & cloud deployments it doesn't make sense to >> RSB> duplicate a DNS server on *every* host, and if you

Re: F23 System Wide Change: Default Local DNS Resolver

Am 01.06.2015 um 19:55 schrieb Jason L Tibbitts III: "RSB" == Ryan S Brown writes: RSB> I disagree; for server & cloud deployments it doesn't make sense to RSB> duplicate a DNS server on *every* host, and if you care about RSB> DNSSEC you likely already run a trusted resolver. I disagree gen

Re: F23 System Wide Change: Default Local DNS Resolver

> "RSB" == Ryan S Brown writes: RSB> I disagree; for server & cloud deployments it doesn't make sense to RSB> duplicate a DNS server on *every* host, and if you care about RSB> DNSSEC you likely already run a trusted resolver. I disagree generally in the case of server deployments. Having a

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

On 01.06.2015 10:50, Harald Hoyer wrote: > *IMPORTANT*: #fedora-meeting-2 ... I repeat: *two* > > Agenda: > - Interview candidates for new memberships > - Optionally accept new members > - Open Floor > > Please add items by replying to this mail. > > Minutes:

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/01/2015 10:37 AM, Tomas Hozza wrote: > On 06/01/2015 03:32 PM, Matthew Miller wrote: >> On Mon, Jun 01, 2015 at 08:03:27AM -0400, Jan Kurik wrote: >>> People use Fedora on portable/mobile devices which are connected to >>> diverse networks as and when required. The automatic DNS >>> configura

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 01, 2015 at 04:37:11PM +0200, Tomas Hozza wrote: > This is work in progress. We will not enable the change in products > and environments in which it will turn out that it does not make sense. Cool; just wanted to be sure that that was being thought about seriously, and it sounds like

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 1 Jun 2015, Tomas Hozza wrote: Yes, we think the change makes sense for Server. It is still beneficial from the security point of view to do the DNSSEC validation on Server. Agreed. Even though the configuration on Server will be static, dnssec-trigger + unbound can be used for this.

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/01/2015 03:32 PM, Matthew Miller wrote: > On Mon, Jun 01, 2015 at 08:03:27AM -0400, Jan Kurik wrote: >> People use Fedora on portable/mobile devices which are connected to >> diverse networks as and when required. The automatic DNS >> configurations provided by these networks are never tru

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 01, 2015 at 08:03:27AM -0400, Jan Kurik wrote: > People use Fedora on portable/mobile devices which are connected to > diverse networks as and when required. The automatic DNS > configurations provided by these networks are never trustworthy for > DNSSEC validation. As currently there i

Self Introduction

Hello, I'm introducing myself shortly as suggested in https://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide?rd=Fedora_Packager_for_Eclipse_User_Guide#Submiting_For_Review . My name is Sopot Cela and I'm a committer in the Eclipse platform project as well as a RedHat employee in

[Bug 1226608] perl-Test-Run-0.0303 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1226608 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version|

F23 System Wide Change: Default Local DNS Resolver

= Proposed System Wide Change: Default Local DNS Resolver = https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver Change owner(s): P J P , Pavlix , Tomas Hozza , Petr Špaček Install a local DNS resolver trusted for the DNSSEC validation running on 127.0.0.1:53. This must be the on

[POC-change] Fedora packages point of contact updates

Change in package status over the last 168 hours 1 packages were orphaned fwbuilder [f22, f21, f20, master] was orphaned by till Firewall Builder https://admin.fedoraproject.org/pkgdb/package/fwbuilder 18 packages

Re: RFC: LiveUSB Creator Revamped

> Hi everyone, > > for quite a while, I've been working on implementation of a new, revamped > UI, designed by Jakub Steiner for the LiveUSB Creator [0]. Currently, me > and Luke are slowly moving to merge the changes back into the master > branch of the tree. Some stuff is not done, like descript

rawhide report: 20150601 changes

Compose started at Mon Jun 1 05:15:03 UTC 2015 Broken deps for i386 -- [OpenTK] OpenTK-1.1-1.4c.fc22.noarch requires mono(mscorlib) = 0:2.0.0.0 OpenTK-1.1-1.4c.fc22.noarch requires mono(System.Xml) = 0:2.0.0.0 OpenTK-1

[Test-Announce] 2015-06-01 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting # Date: 2015-06-01 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We haven't had a QA meeting in a long time, it seems we could do another session. The only important

[Bug 1226484] perl-CGI-4.20 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1226484 Jitka Plesnikova changed: What|Removed |Added Status|NEW |MODIFIED Fixed In Version|

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

*IMPORTANT*: #fedora-meeting-2 ... I repeat: *two* Agenda: - Interview candidates for new memberships - Optionally accept new members - Open Floor Please add items by replying to this mail. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/