Re: New ABRT CLI

On 06/02/2015 03:45 PM, Richard Marko wrote: > Hi, > > over last two weeks I completely rewrote abrt-cli to make life easier > for users and developers. > > It now supports tab completion and few new commands like abrt gdb and > abrt debuginfo-install. Without any arguments these commands will use

Re: gcc5 C++11 ABI rebuilds and FTBFS packages

On Wed, May 6, 2015 at 9:10 AM, Dave Johansen wrote: > On Mon, May 4, 2015 at 4:09 AM, Kalev Lember > wrote: > >> iwyu: http://koji.fedoraproject.org/koji/taskinfo?taskID=9651015 >> > > A clang/llvm 3.6 compatible version of include-what-you-use (iwyu) hasn't > been released yet. Once t

Re: New ABRT CLI

On Tue, 2015-06-02 at 15:45 +0200, Richard Marko wrote: > Hi, > > over last two weeks I completely rewrote abrt-cli to make life easier > for users and developers. > > It now supports tab completion and few new commands like abrt gdb and > abrt debuginfo-install. Without any arguments these comma

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, 2 Jun 2015, David Howells wrote: I'm using dnsmasq to look up *.redhat.com addresses over VPN whilst looking up other addresses from my ISP. That is automatically handled for you if you use libreswan for your VPN and unbound is running. It will add a forward for the domain ("redhat.com

Re: F23 System Wide Change: Default Local DNS Resolver

Paul Wouters wrote: > I think most people end up running dnsmasq because of KVM/libvirtd ? I > think those dnsmasq's should be run in "dhcp only" mode and point to > the hosts's unbound. I'm using dnsmasq to look up *.redhat.com addresses over VPN whilst looking up other addresses from my ISP.

Context menu icons in Gnome 3.16

Hi, I'm messing with an old gtk+ program, that I think it's dead upstream and I'm trying to see if I can resurrect it. Among other issues, it should add some entries to nautilus' context menus (which it does) but I can't get their icons to show. Then I noticed that I'm missing all of my context men

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, Jun 02, 2015 at 08:12:23PM +0200, Reindl Harald wrote: > >>the whole purpose of Linux systems was to have open systems, open means also > >>basically understandable and not just "you can grab the source" > > > >Linux is not, and has never been, UNIX > > your phrase has nothing to with the

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, 2 Jun 2015, Simo Sorce wrote: and just because you have a local resolver firefox won't stop it's behavior It can, w/o a local resolver FF developers will definitely keep caching on their own, with a decent local resolver they can allow themselves to disable their own and go back to rel

Re: F23 System Wide Change: Default Local DNS Resolver

Am 02.06.2015 um 20:04 schrieb Solomon Peachy: On Tue, Jun 02, 2015 at 07:56:21PM +0200, Reindl Harald wrote: the whole purpose of Linux systems was to have open systems, open means also basically understandable and not just "you can grab the source" Linux is not, and has never been, UNIX y

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, 2015-06-02 at 19:56 +0200, Reindl Harald wrote: > Am 02.06.2015 um 19:49 schrieb Simo Sorce: > > On Mon, 2015-06-01 at 23:15 +0200, Reindl Harald wrote: > >> a sane system should be as simple as possible so that *one* human is > >> able to determine what is happening without hire 10 special

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, Jun 02, 2015 at 07:56:21PM +0200, Reindl Harald wrote: > the whole purpose of Linux systems was to have open systems, open means also > basically understandable and not just "you can grab the source" Linux is not, and has never been, UNIX. - Solomon -- Solomon Peachy

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, 2015-06-02 at 19:51 +0200, Reindl Harald wrote: > Am 02.06.2015 um 19:45 schrieb Simo Sorce: > > On Mon, 2015-06-01 at 21:44 +0200, Reindl Harald wrote: > >> it don't cache dns respones - try it out in your local network > >> *client applications* may cache respones > >> > >> try it out in

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/02/2015 06:44 PM, Paul Wouters wrote: > On Tue, 2 Jun 2015, David Howells wrote: > >>> 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. >>> >>> The automatic name server entries rec

Re: F23 System Wide Change: Default Local DNS Resolver

Am 02.06.2015 um 19:49 schrieb Simo Sorce: On Mon, 2015-06-01 at 23:15 +0200, Reindl Harald wrote: a sane system should be as simple as possible so that *one* human is able to determine what is happening without hire 10 specialists for each layer There is no human able to understand a complex

Re: F23 System Wide Change: Default Local DNS Resolver

Am 02.06.2015 um 19:45 schrieb Simo Sorce: On Mon, 2015-06-01 at 21:44 +0200, Reindl Harald wrote: it don't cache dns respones - try it out in your local network *client applications* may cache respones try it out in your local network * enter a non existing subdomain in firefox * add the hos

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 2015-06-01 at 23:15 +0200, Reindl Harald wrote: > a sane system should be as simple as possible so that *one* human is > able to determine what is happening without hire 10 specialists for > each > layer There is no human able to understand a complex system like modern computers and OSs,

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 2015-06-01 at 21:44 +0200, Reindl Harald wrote: > 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 > >>> brea

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 2015-06-01 at 21:33 +0200, Reindl Harald wrote: > > 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

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, 2015-06-01 at 21:31 +0200, Reindl Harald wrote: > 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 f

Fedora 22 for IBM z Systems is here!

We are proud to announce the official release of Fedora 22 for IBM z Systems, the community-driven and community-built operating system now available in Server edition. If that's all you need to hear, jump over to Get Fedora to download -- or for current users, run the FedUp upgrade tool. * ht

Re: no product firewall-config in bugzilla?

On Tue, 02 Jun 2015 11:50:07 -0400 Neal Becker wrote: > rpm -qf /usr/bin/firewall-config > firewall-config-0.3.13-7.fc22.noarch > > But I can't select firewall-config in BZ! > I filed my bug under firewalld instead. > https://bugzilla.redhat.com/show_bug.cgi?id=1227419 Yes, thats the right pla

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, 2 Jun 2015, David Howells wrote: 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. The automatic name server entries received via dhcp/vpn/wireless configurations should be stored separate

Re: AppData Guidelines

On 2 June 2015 at 17:17, Gerald B. Cox wrote: > Upstream response is if they are duplicated in the desktop file, then they > aren't needed in the appdata file. This is old advice and no longer true. One mistake I made when first pushing AppStream was to fall back to the .desktop file Name= and Co

Re: F23 System Wide Change: Default Local DNS Resolver

On Tue, Jun 2, 2015 at 2:44 AM, Florian Weimer wrote: > On 06/01/2015 10:57 PM, Andrew Lutomirski wrote: > >> This is glibc we're talking about, though. Have you tried to get a >> glibc bug fixed? It's not a pleasant experience. > > It is possible, but it requires effort. Admittedly, sometimes

AppData Guidelines

I've reviewed Packaging:AppData and have some questions. When running fedpkg lint, I receive:*copyq.x86_64: E: invalid-appdata-file /usr/share/appdata/copyq.appdata.xml* I then issue appstream-util validate copyq.appdata.xml and receive: *copyq.a

no product firewall-config in bugzilla?

rpm -qf /usr/bin/firewall-config firewall-config-0.3.13-7.fc22.noarch But I can't select firewall-config in BZ! I filed my bug under firewalld instead. https://bugzilla.redhat.com/show_bug.cgi?id=1227419 -- Those who fail to understand recursion are doomed to repeat it -- devel mailing list d

Docker base image naming for non-x86_64

Hello all, There was recently a thread on the Fedora ARM mailing list[0] about getting a Fedora ARM image into the official Docker Hub. That discussion lead down the trail of how to best handle the naming for all of this. The current questions are either using Fedora's namespace and just makin

Re: F23 System Wide Change: Default Local DNS Resolver

Jan Kurik wrote: > 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. > > The automatic name server entries received via dhcp/vpn/wireless > configurations should be stored separately (e.g. this is

Re: F23 System Wide Change: Default Local DNS Resolver

On Mon, Jun 01, 2015 at 09:31:14PM +0200, Reindl Harald wrote: > > 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 > poi

Re: Fedora.next PRD refresh

On Tue, Jun 02, 2015 at 09:08:05AM -0400, Stephen Gallagher wrote: > > I am just curious why it would not be held from this year? because of > > time constrains? > We had already communicated to several groups that we wanted to refresh > it before Alpha this cycle (Cloud in particular had moved far

Fedora 22 for POWER is here!

We are proud to announce the official release of Fedora 22 for POWER, the community-driven and community-built operating system now available in Cloud and Server editions. If that's all you need to hear, jump over to Get Fedora to download -- or for current users, run the FedUp upgrade tool. *

Re: Fedora 22: cannot use rpmsign in script - problem with pinentry-gtk-2

Petr Pisar píše v Út 02. 06. 2015 v 07:57 +: > On 2015-06-02, Pavel Lisý wrote: > > I've used rpmsign in script for long time. I worked fine. After upgrade > > to > > Fedora 22 (from Fedora 20) something changed > > > [...] > > > > is starting now pinentry-gtk-2 and forces me to put passphr

New ABRT CLI

Hi, over last two weeks I completely rewrote abrt-cli to make life easier for users and developers. It now supports tab completion and few new commands like abrt gdb and abrt debuginfo-install. Without any arguments these commands will use the last crash that occurred on your system. New cli is

Orphaning/retiring 2 packages

Hi, I don't use these 2 packages any more, and don't want to continue maintaining them. If someone want to take over, I'll be happy to pass them. But if nobody express their interest in the next few days, I'll just retire them. # weighttp This package hasn't had any upstream release since 2011.

ppisar pushed to perl-Getopt-Long (f20). "2.46 bump"

From c04de40ceac1253a6017b902504af9d495a75003 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Tue, 2 Jun 2015 15:06:33 +0200 Subject: 2.46 bump diff --git a/.gitignore b/.gitignore index 902668c..f3c8aba 100644 --- a/.gitignore +++ b/.gitignore @@ -5,3 +5,4 @@ /Getopt-Lo

Re: Fedora.next PRD refresh

On Tue, 2015-06-02 at 09:55 +0700, Truong Anh Tuan wrote: > - 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

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

On Tue, Jun 2, 2015 at 2:47 AM, Václav Pavlín wrote: > 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

Re: Reviving Fedora MIPS

On Mon, Jun 1, 2015 at 4:10 PM, Michal Toman wrote: > Greetings everyone, > > you might know me from my former work on ABRT, or later Power and s390. > For the last few months however, I have been collaborating with > Imagination Technologies to bring back Fedora for MIPS. > > A brief history - s

default btrfs partitioning setup

I have an older setup created by anaconda from 2013, and it looks like UUID=7246327b-1905-4fe2-9b6b-b9376017264f / btrfs subvolid=5,subvol=root00 0 0 UUID=2c04be93-34c1-4016-ba41-60fd9fd90616 /boot ext4 defaults1 2 UUID=7246327b-1905-4fe2-9b6b

rawhide report: 20150602 changes

Compose started at Tue Jun 2 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

Re: Reviving Fedora MIPS

On Mon, Jun 01, 2015 at 10:10:17PM +0200, Michal Toman wrote: > Apart from mips64el, we have lately started working on 32-bit mipsel, to > be ran on the Creator CI20 Borad [4]. This is basically 3 months behind > mips64el so there are no significant results yet, but hopefully will be > soon. I hav

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/01/2015 10:57 PM, Andrew Lutomirski wrote: > This is glibc we're talking about, though. Have you tried to get a > glibc bug fixed? It's not a pleasant experience. It is possible, but it requires effort. Admittedly, sometimes that effort appears disproportionate to what is being fixed. I

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/01/2015 09:33 PM, Reindl Harald wrote: > > > 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 ne

Re: Fedora 22: cannot use rpmsign in script - problem with pinentry-gtk-2

Now, I see that, the answer is in the second link. - Original Message - > From: "Lubos Kardos" > To: "Development discussions related to Fedora" > > Sent: Tuesday, June 2, 2015 10:52:37 AM > Subject: Re: Fedora 22: cannot use rpmsign in script - problem with > pinentry-gtk-2 > > Pet

Re: Fedora 22: cannot use rpmsign in script - problem with pinentry-gtk-2

Petr, do you know if "--passphrase-fd" should still work? Because that is the way how rpm pass passphrase to gpg and it doesn't seem to work. Lubos - Original Message - > From: "Petr Pisar" > To: devel@lists.fedoraproject.org > Sent: Tuesday, June 2, 2015 9:57:38 AM > Subject: Re: Fedor

Re: F23 System Wide Change: Default Local DNS Resolver

"Ryan S. Brown" wrote: > I disagree; for server & cloud deployments it doesn't make sense to > duplicate a DNS server on *every* host, and if you care about DNSSEC > you likely already run a trusted resolver. > > The trust and management models for Server are fundamentally different > from those

Re: F23 System Wide Change: Default Local DNS Resolver

Le Lun 1 juin 2015 21:25, Reindl Harald a écrit : > surely there are many environments beside mine and *that* is why it's > not smart to consider a local dns cache on each and every server There are many environments that benefit from a local DNS cache (for example FAI with flacky DNS, people wi

Re: Fedora 22: cannot use rpmsign in script - problem with pinentry-gtk-2

On 2015-06-02, Pavel Lisý wrote: > I've used rpmsign in script for long time. I worked fine. After upgrade to > Fedora 22 (from Fedora 20) something changed > [...] > > is starting now pinentry-gtk-2 and forces me to put passphrase to modal > window. > > Is any possibility how to disable this beh

Fedora 22: cannot use rpmsign in script - problem with pinentry-gtk-2

Hello I've used rpmsign in script for long time. I worked fine. After upgrade to Fedora 22 (from Fedora 20) something changed This script: - cut -- export LANG=cs_CZ.UTF-8 if [ -n "$PASSPHRASE" ] ; then /usr/bin/expect -f - << EOF spawn rpmsign --addsign $RPMS_TO_SIGN