Re: F24 System Wide Change: Default Local DNS Resolver

On 04.12.2015 21:46, Dan Williams wrote: > On Fri, 2015-12-04 at 16:09 +0100, Timotheus Pokorra wrote: >>> is deployed in probably half of the homes in Germany... Also I am >>> pretty sure other routers form other manufacturers do the same >>> thing. Now, if we default to DNSSEC validation soon, do

Re: F24 System Wide Change: Default Local DNS Resolver

On 05.12.2015 18:57, Florian Weimer wrote: > On 11/30/2015 05:14 PM, Jan Kurik wrote: >> We want to have Unbound server installed and running on localhost by >> default on Fedora systems. Where necessary, have also dnssec-trigger >> installed and running by default > > Would someone please clarify

Re: Direct messages

On Mon, Dec 07, 2015 at 11:29:32AM +0600, Dmitrij S. Kryzhevich wrote: I just want to know what happened to direct messages about issues with packages. When builds fail i.e. during mass rebuilds I have a message about it. If for some reasons dependencies tree was broken (in rawhide, i.e., it is

Re: F24 System Wide Change: Default Local DNS Resolver

On 04.12.2015 15:57, Lennart Poettering wrote: > On Tue, 01.12.15 11:15, Tomas Hozza (tho...@redhat.com) wrote: > >> You are not mistaken. >> >> This is the third time, because previously we rather moved the change to the >> next Fedora to bring better user experience. Every time there was somethi

Re: DNF could improve messages about package auto-removal

Hi, > One would hope (assume?) that there's something to keep dnf from > thinking I no longer need Firefox, or emacs, or some other big package > just because nothing else depends on it any more. That seems to be in place at least for kernel and dnf. Recently I've tried to uninstall some small

Re: DNF could improve messages about package auto-removal

Note that packages installed by PackageKit are not marked as installed, so dnf always thinks it can remove them. No, DNF treats unmarked packages as installed by user => it never autoremoves them. Unfortunately, it seems that Packagekit is incorrectly marking all installed packages as dependen

Re: Can Koji handle a soname change and a self-dependency?

Kevin Fenzi wrote: > On Tue, 1 Dec 2015 15:46:26 +0100 > Björn Persson wrote: > > GPRbuild is > > linked to XMLada, and both GPRbuild and XMLada are linked to libgnat, > > as are all other Ada programs and libraries. > > > > With every major GCC upgrade the soname of libgnat changes, and all > >

Re: Direct messages

On Mon, Dec 07, 2015 at 03:30:34PM +0600, Dmitrij S. Kryzhevich wrote: > >On Mon, Dec 07, 2015 at 11:29:32AM +0600, Dmitrij S. Kryzhevich wrote: > >>I just want to know what happened to direct messages about issues with > >>packages. > >> > >>When builds fail i.e. during mass rebuilds I have a mess

FESCo, Council, FAmSCo elections - Voting starts on Tuesday 2015-Dec-08 at 00:00 UTC

Hello everyone! The voting for FESCo,Council and FAmSCo elections is going to start on Tuesday 2015-Dec-08 at 00:00 UTC. I would be happy if you can review setup of the Voting system, to make sure all the candidates are listed and have correct nicks entered. In case you find any discrepancy, pleas

Re: Some comps cleanup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Can somebody explain me why Rawhide comps are called F24? Trying to use "git blame" and surprisingly (or not that much), almost every line was created by Kevin Fenzi. Why we are using git if we break the history this way? How can I find what was rea

Retired - nspluginwrapper

Hi Folks, I'm going to retire and remove nspluginwrapper from Fedora 24 and newer [1]. Firefox and Chromium does not use that any more. Please speak up if you need that. ma. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1289053 -- devel mailing list devel@lists.fedoraproject.org http://lis

Re: Bodhi front page after login

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dne 6.12.2015 v 20:42 Kevin Fenzi napsal(a): > On Sun, 6 Dec 2015 20:17:37 +0100 > Reindl Harald wrote: > >> Am 06.12.2015 um 20:06 schrieb Michael Schwendt: >>> When I log in at https://bodhi.fedoraproject.org/ the new web ui >>> greets me with

Re: Some comps cleanup

On 12/07/2015 11:42 AM, Vít Ondruch wrote: > Can somebody explain me why Rawhide comps are called F24? Trying to use > "git blame" and surprisingly (or not that much), almost every line was > created by Kevin Fenzi. Why we are using git if we break the history > this way? How can I find what was re

Re: Some comps cleanup

Dne 7.12.2015 v 11:56 Kalev Lember napsal(a): > On 12/07/2015 11:42 AM, Vít Ondruch wrote: >> Can somebody explain me why Rawhide comps are called F24? Trying to use >> "git blame" and surprisingly (or not that much), almost every line was >> created by Kevin Fenzi. Why we are using git if we break

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 07.12.15 10:48, Tomas Hozza (tho...@redhat.com) wrote: > On 04.12.2015 15:57, Lennart Poettering wrote: > > On Tue, 01.12.15 11:15, Tomas Hozza (tho...@redhat.com) wrote: > > > >> You are not mistaken. > >> > >> This is the third time, because previously we rather moved the change to > >

Re: Bodhi front page after login

> I can hardly see what has my "profile" in common with my updates. They should be shown on the welcome screen. I agree completely. My biggest complain about new Bodhi so far. It's really difficult to navigate and the link should show appropriate cursor (now it shows cursor for editing text inst

rawhide report: 20151207 changes

Compose started at Mon Dec 7 05:15:03 UTC 2015 Broken deps for i386 -- [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0 IQmol-2.3.0

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 07.12.15 10:15, Tomas Hozza (tho...@redhat.com) wrote: > On 05.12.2015 18:57, Florian Weimer wrote: > > On 11/30/2015 05:14 PM, Jan Kurik wrote: > >> We want to have Unbound server installed and running on localhost by > >> default on Fedora systems. Where necessary, have also dnssec-trigg

Re: F24 System Wide Change: Default Local DNS Resolver

Hi, > Quite frankly: a setup like this one isn't just very typical for home > router networks, but also in many companies, where ".lan" or > ".companyname" or something like that is frequently established in the > internal network. And you will make Fedora incompatible with all these > networks

Re: yum: Critical path update in testing for 4 months?

On Sun, 06 Dec 2015 20:52:19 -0800, Adam Williamson wrote: > > > That doesn't really add up. > > > > What doesn't add up? > > We were talking about a yum update that had been sitting around for > four months, with +10 karma. That may be the subject, but the messages have referred to many ot

Re: yum: Critical path update in testing for 4 months?

On Mon, 07 Dec 2015 03:29 +0100, Kevin Kofler wrote: > Adam Williamson wrote: > > I've never understood why the idea of a 'last push of security fixes' > > for an EOL release makes any sense. It's *EOL*. It doesn't matter if > > there's a last-day push or not: everyone should stop using it the nex

Re: Bodhi front page after login

On Mon, 7 Dec 2015 11:53:26 +0100, Vít Ondruch wrote: > > You can find all your updates under the 'profile' tab. You could even > > set a bookmark to this page. > > > > I can hardly see what has my "profile" in common with my updates. They > should be shown on the welcome screen. It's not the

Re: Bodhi front page after login

Am 07.12.2015 um 14:05 schrieb Michael Schwendt: On Mon, 7 Dec 2015 11:53:26 +0100, Vít Ondruch wrote: You can find all your updates under the 'profile' tab. You could even set a bookmark to this page. I can hardly see what has my "profile" in common with my updates. They should be shown o

Between a rock and a hard place

Hi! libunwind package is now part of RHEL 7.2. It got retired from EPEL7 three days ago (and incidentally the Release went backwards so upgrade path is broken): https://bugzilla.redhat.com/show_bug.cgi?id=1288313 Unfortunately, that leaves CentOS users in a bit of a pickle, as libunwind is no

Re: Bodhi front page after login

On Mon, 7 Dec 2015 14:20:40 +0100, Reindl Harald wrote: > why can't you not just set a bookmark in the time you write 5 mails? I've adjusted my bookmarks more than 18 hours ago already. That doesn't make the bodhi welcome page any better, though. The left column is a flood of uninteresting messa

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 10:17:20AM +0100, Tomas Hozza wrote: > > Older Netgear routers also used http://routerlogin.net before they were > > set up. > If they don't own the domain, then this is simply hijacking of domain > name space, which is not owned by them. It is expected, that these > "clever

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 12:23:34PM +0100, Lennart Poettering wrote: > > As you've said, this is basically an attack and hijacking of someone's > > else domain name space. It is not correct and it is not expected that > > this will work with DNSSEC. > Humm, I find that way too cavalier... I am prett

Re: F24 System Wide Change: Default Local DNS Resolver

On 07.12.2015 12:23, Lennart Poettering wrote: > On Mon, 07.12.15 10:48, Tomas Hozza (tho...@redhat.com) wrote: > >> On 04.12.2015 15:57, Lennart Poettering wrote: >>> On Tue, 01.12.15 11:15, Tomas Hozza (tho...@redhat.com) wrote: >>> You are not mistaken. This is the third time, be

Re: F24 System Wide Change: Default Local DNS Resolver

On 07.12.2015 14:52, Matthew Miller wrote: > On Mon, Dec 07, 2015 at 12:23:34PM +0100, Lennart Poettering wrote: > >> As you've said, this is basically an attack and hijacking of someone's > >> else domain name space. It is not correct and it is not expected that > >> this will work with DNSSEC. >

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 02:59:18PM +0100, Tomas Hozza wrote: > > I agree with Lennart. Whether or not this is expected to work with > > DNSSEC is of academic interest given that people will expect it to work > > with _their computers_, regardless of what they're running. > I guess next time I'll no

Re: F24 System Wide Change: Default Local DNS Resolver

On 07.12.2015 15:00, Matthew Miller wrote: > On Mon, Dec 07, 2015 at 02:59:18PM +0100, Tomas Hozza wrote: > >> I agree with Lennart. Whether or not this is expected to work with > >> DNSSEC is of academic interest given that people will expect it to work > >> with _their computers_, regardless of w

Re: F24 System Wide Change: Default Local DNS Resolver

On 7 December 2015 at 14:04, Tomas Hozza wrote: > I took this conversation as a mean for improvement. When an email is titled "F24 System Wide Change" I think a lot of people (like me) were under the impression you wanted this to be a new feature in Fedora 24. Richard. -- devel mailing list deve

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 03:04:06PM +0100, Tomas Hozza wrote: > > On Mon, Dec 07, 2015 at 02:59:18PM +0100, Tomas Hozza wrote: > > >> I agree with Lennart. Whether or not this is expected to work with > > >> DNSSEC is of academic interest given that people will expect it to work > > >> with _their c

Re: F24 System Wide Change: Default Local DNS Resolver

On 07.12.2015 15:15, Richard Hughes wrote: > On 7 December 2015 at 14:04, Tomas Hozza wrote: >> I took this conversation as a mean for improvement. > > When an email is titled "F24 System Wide Change" I think a lot of > people (like me) were under the impression you wanted this to be a new > feat

Re: F24 System Wide Change: Default Local DNS Resolver

Lennart Poettering wrote: > in germany "Fritzbox" wifi routers are very > popular. Their configuration page is reachable under the "fritz.box" > pseudo-domain from inside their wifi network, and all other systems on > the network are also eachable below this domain under their > DHCP-configured ho

Re: F24 System Wide Change: Default Local DNS Resolver

Lennart Poettering wrote: > You *have* to use the local DNS servers by default, even if they are > crap. I for one want my laptop to be suspicious of random DNS servers it encounters in public places, and bypass them if they're found to be lying. I also want to be able to make an exception in ca

Re: F24 System Wide Change: Default Local DNS Resolver

On 01/12/15 15:59, Randy Barlow wrote: > This sounds overall pretty neat to me! One detail came to my mind: how > would this interact with VPN DNS servers? In my experience with VPNs, > it's common for them to provide a DNS server that allows internal host > resolution to work. Would this local res

Re: F24 System Wide Change: Default Local DNS Resolver

Am 07.12.2015 um 15:56 schrieb Pádraig Brady: On 01/12/15 15:59, Randy Barlow wrote: This sounds overall pretty neat to me! One detail came to my mind: how would this interact with VPN DNS servers? In my experience with VPNs, it's common for them to provide a DNS server that allows internal hos

Re: Between a rock and a hard place

On Mon, Dec 07, 2015 at 01:44:30PM +, Jamie Nguyen wrote: > Hi! > > libunwind package is now part of RHEL 7.2. It got retired from EPEL7 > three days ago (and incidentally the Release went backwards so upgrade > path is broken): > > https://bugzilla.redhat.com/show_bug.cgi?id=1288313 > > U

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 07.12.15 13:25, Gerd Hoffmann (kra...@redhat.com) wrote: > Hi, > > > Quite frankly: a setup like this one isn't just very typical for home > > router networks, but also in many companies, where ".lan" or > > ".companyname" or something like that is frequently established in the > > inte

Re: Between a rock and a hard place

On 07/12/15 14:59, Pierre-Yves Chibon wrote: On Mon, Dec 07, 2015 at 01:44:30PM +, Jamie Nguyen wrote: Hi! libunwind package is now part of RHEL 7.2. It got retired from EPEL7 three days ago (and incidentally the Release went backwards so upgrade path is broken): https://bugzilla.redhat

F24 Self Contained Change: sen - terminal user interface for docker engine

= Proposed Self Contained Change: sen - terminal user interface for docker engine = https://fedoraproject.org/wiki/Changes/sen--tui-for-docker Change owner(s): * Tomas Tomecek sen enables you to manage your containers and images interactively directly from command line. Interface is similar to h

Re: Between a rock and a hard place

On Mon, Dec 7, 2015 at 6:44 AM, Jamie Nguyen wrote: > So, in the general case of packages being retired from EPEL7 because > they have moved to RHEL, how do we avoid missing packages in the future? What is the issue with the CR CentOS repository? - Ken -- devel mailing list devel@lists.fedorapro

Re: F24 System Wide Change: Default Local DNS Resolver

On Dec 7, 2015 1:49 AM, "Tomas Hozza" wrote: > > On 04.12.2015 15:57, Lennart Poettering wrote: > > On Tue, 01.12.15 11:15, Tomas Hozza (tho...@redhat.com) wrote: > > > >> You are not mistaken. > >> > >> This is the third time, because previously we rather moved the change to the > >> next Fedora

Re: F24 Self Contained Change: sen - terminal user interface for docker engine

* provide an information it's available and documentation how to use it (maybe via developer portal, or release notes) This would be a nice addition for developer portal. +1 from me. Best Josef -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/deve

[POC-change] Fedora packages point of contact updates

Change in package status over the last 168 hours 2 packages were orphaned cherrytree [f23, f22, f21, master] was orphaned by cheeselee Hierarchical note taking application https://admin.fedoraproject.org/pkgdb/pack

Re: F24 System Wide Change: Default Local DNS Resolver

On 07.12.2015 16:44, Andrew Lutomirski wrote: > > On Dec 7, 2015 1:49 AM, "Tomas Hozza" > wrote: > > > > On 04.12.2015 15:57, Lennart Poettering wrote: > > > On Tue, 01.12.15 11:15, Tomas Hozza (tho...@redhat.com > > > ) wrote: > > > > > >> You

Re: Direct messages

On Mon, Dec 07, 2015 at 11:29:32AM +0600, Dmitrij S. Kryzhevich wrote: > I just want to know what happened to direct messages about issues with > packages. > If one of dependencies was retired I have... nothing. Yes, I'm not reading > messages in devel@ with "Orphan" title careful. I missed that o

Fedora Rawhide 20151207 compose check report

Missing expected images: Cloud disk raw i386 Cloud_atomic disk raw x86_64 Kde disk raw armhfp Kde live i386 Cloud disk raw x86_64 Kde live x86_64 Images in this compose but not Rawhide 20151206: Mate live i386 No images in Rawhide 20151206 but not this. Failed openQA tests: 2 of 52 ID: 486 Te

Re: Between a rock and a hard place

On 07/12/15 14:59, Pierre-Yves Chibon wrote: >> So, in the general case of packages being retired from EPEL7 because >> they have moved to RHEL, how do we avoid missing packages in the future? > > Could make a compat package in EPEL7 be an option? > This way you introduce back the version that was

Re: Between a rock and a hard place

FYI, this discussion might be better on the actual epel-devel list... On Mon, 7 Dec 2015 15:17:54 + Paul Howarth wrote: > On 07/12/15 14:59, Pierre-Yves Chibon wrote: ...snip... > > Could make a compat package in EPEL7 be an option? > > This way you introduce back the version that was presen

Re: Between a rock and a hard place

On 07/12/15 15:33, Ken Dreyer wrote: > On Mon, Dec 7, 2015 at 6:44 AM, Jamie Nguyen wrote: >> So, in the general case of packages being retired from EPEL7 because >> they have moved to RHEL, how do we avoid missing packages in the future? > > What is the issue with the CR CentOS repository? It's

Re: Some comps cleanup

On Mon, 7 Dec 2015 12:20:27 +0100 Vít Ondruch wrote: > Dne 7.12.2015 v 11:56 Kalev Lember napsal(a): > > On 12/07/2015 11:42 AM, Vít Ondruch wrote: > >> Can somebody explain me why Rawhide comps are called F24? Trying > >> to use "git blame" and surprisingly (or not that much), almost > >> ever

Re: Bodhi front page after login

On Mon, 7 Dec 2015 14:44:42 +0100 Michael Schwendt wrote: > On Mon, 7 Dec 2015 14:20:40 +0100, Reindl Harald wrote: > > > why can't you not just set a bookmark in the time you write 5 > > mails? > > I've adjusted my bookmarks more than 18 hours ago already. > > That doesn't make the bodhi we

Re: yum: Critical path update in testing for 4 months?

On Sun, 6 Dec 2015 22:29:33 +0100 Michael Schwendt wrote: > On Sun, 6 Dec 2015 12:40:45 -0700, Kevin Fenzi wrote: > > > Perhaps. But you are speculating that this is the case here. > > Unless you have talked to the maintainer and thats what they told > > you? > > I'm not speculating as I did

limb changed nb's 'watchcommits' permission on perl-IO-Socket-IP (el6) to 'Approved'

limb changed nb's 'watchcommits' permission on perl-IO-Socket-IP (el6) to 'Approved' https://admin.fedoraproject.org/pkgdb/package/perl-IO-Socket-IP/ -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org http

Re: yum: Critical path update in testing for 4 months?

On Mon, 7 Dec 2015 00:08:37 +0100 Reindl Harald wrote: > yes, i expect this when i am able to follow all fedora and 7 other > mailing-lists including bodhi-mails and give karma and review 100-400 > mail samples for bayes-training every day besides my daily jobs as > the only sysadmin for more t

Re: F24 System Wide Change: Default Local DNS Resolver

On 12/07/2015 04:48 AM, Tomas Hozza wrote: >> So, here's a question: in germany "Fritzbox" wifi routers are very >> popular. Their configuration page is reachable under the "fritz.box" >> pseudo-domain from inside their wifi network, and all other systems on >> the network are also eachable below

Re: Fedora 23 cloud image (and, for that matter, minimal anything) bloat

Hi Chris, On 2015-09-22 04:26, Chris Murphy wrote: ... For the cloud image, extlinux actually works. The problem pops up with any image intended for baremetal whre UEFI Secure Boot support is needed, and right now GRUB2 does and extlinux doesn't, so any "atomic" image would need GRUB2. Wh

Re: yum: Critical path update in testing for 4 months?

On Mon, 7 Dec 2015 10:53:32 -0700, Kevin Fenzi wrote: > So, what you would like would be: > > a) If you have autokarma set and the update doesn't reach autokarma, > push it automatically when it reaches the timeout. With a customisable timeout, it would be a good feature. > b) Have another bo

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 07.12.15 17:23, Tomas Hozza (tho...@redhat.com) wrote: > > Can you elaborate a bit? Is the intent that, if .box were private, then > > .box would be forwarded to DHCP-provided revolvers regardless of whether > > those resolvers were functional when asking for DNSSEC signature data? > >

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 07.12.15 15:31, Björn Persson (Bjorn@rombobjörn.se) wrote: > Lennart Poettering wrote: > > You *have* to use the local DNS servers by default, even if they are > > crap. > > I for one want my laptop to be suspicious of random DNS servers it > encounters in public places, and bypass them

Reminder: Distributions Devroom CFP - Deadline 10-December

On Nov 02 15:46, Brian Stinson wrote: > FOSDEM 2016 - Distributions Devroom Call for Participation > > The Distributions devroom will take place 30 & 31 January, 2016 at FOSDEM, in > room K.4.201 at Université Libre de Bruxelles, in Brussels, Belgium. > > As Linux distributions converge on simil

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 7, 2015 at 11:31 AM, Lennart Poettering wrote: > On Mon, 07.12.15 17:23, Tomas Hozza (tho...@redhat.com) wrote: > >> > Can you elaborate a bit? Is the intent that, if .box were private, then >> > .box would be forwarded to DHCP-provided revolvers regardless of whether >> > those res

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 7 Dec 2015, Lennart Poettering wrote: Hmm? If I work for a company "Foo Corp" that defined .foocorp as its private TLD, then I won't be able to access servers in that local network until I added .foocorp to a local whitelist Foo Corp should not have done that. If you had picked .hotel

Re: F24 System Wide Change: Default Local DNS Resolver

Am 07.12.2015 um 20:48 schrieb Paul Wouters: Move your own domains within one of your real legitimate domains, and you have the freedom to do whatever you want. Start moving away from split DNS because that's going to be very hard to support. that's simply not possible for every environment

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 7 Dec 2015, Matthew Miller wrote: I read your whole post. Those possibilities seem pretty limited, from the point of view of serious regressions in Fedora usability. It isn't that I "like" Fedora being less than technically correct (especially around security-related features), but I don

Re: F24 System Wide Change: Default Local DNS Resolver

On 12/07/2015 08:31 PM, Lennart Poettering wrote: > Hmm? If I work for a company "Foo Corp" that defined .foocorp as its > private TLD, then I won't be able to access servers in that local > network until I added .foocorp to a local whitelist, is that what you > are saying? Or do you want to ship

Re: F24 System Wide Change: Default Local DNS Resolver

On 12/07/2015 07:21 PM, Paul Wouters wrote: > Well, there is going to be a very interesting lawsuit about damage then > because in a few months .box will be live run by a Hong Kong company > called "NS1 Limited" > > https://www.icann.org/resources/agreement/box-2015-11-12-en > > .box Regi

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 7 Dec 2015, Lennart Poettering wrote: In case this is blocked on the network, Unbound is configured to tunnel the DNS queries to Fedora public infrastructure over TCP (80, 443) or SSL (443), in which case this is similar to the first situation, when Unbound forwards queries to the resolv

Fwd: Re: F24 System Wide Change: Default Local DNS Resolver (fwd)

(resending - looks like mty @redhat.com is not subscribed) On 12/07/2015 04:48 AM, Tomas Hozza wrote: So, here's a question: in germany "Fritzbox" wifi routers are very popular. Their configuration page is reachable under the "fritz.box" pseudo-domain from inside their wifi network, and all oth

stalled package review

This package review: https://bugzilla.redhat.com/show_bug.cgi?id=751749 has been stalled for several years now since the original submitter (Karel Klíč) never got back to it, even though the review was approved. Since it is not packaged yet, the nonresponsive package maintainers policy does not ap

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, 7 Dec 2015, Florian Weimer wrote: Clearly, fedora cannot be changed to hijack a real domain, so Fritzbox better solve this quickly with an update, even if no one actually will update their router :( Well, AVM could just register fritz.box and leave it unsigned, which solves the problem

Re: F24 System Wide Change: Default Local DNS Resolver

Am 07.12.2015 um 21:40 schrieb Paul Wouters: On Mon, 7 Dec 2015, Florian Weimer wrote: Clearly, fedora cannot be changed to hijack a real domain, so Fritzbox better solve this quickly with an update, even if no one actually will update their router :( Well, AVM could just register fritz.box

Re: stalled package review

On Mon, Dec 7, 2015 at 9:40 PM, Jos de Kloe wrote: > This package review: https://bugzilla.redhat.com/show_bug.cgi?id=751749 > has been stalled for several years now since the original submitter > (Karel Klíč) never got back to it, even though the review was approved. > > Since it is not packaged

Re: yum: Critical path update in testing for 4 months?

On Mon, 2015-12-07 at 20:19 +0100, Michael Schwendt wrote: > On Mon, 7 Dec 2015 10:53:32 -0700, Kevin Fenzi wrote: > > > So, what you would like would be: > > > > a) If you have autokarma set and the update doesn't reach autokarma, > > push it automatically when it reaches the timeout. > > Wit

Orphaned Packages in rawhide (2015-12-07)

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If y

Orphaned Packages in rawhide (2015-12-07)

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If y

Re: F24 System Wide Change: Default Local DNS Resolver

On Monday 07 December 2015 14:57:36 Paul Wouters wrote: > But you gain nothing with waiting. There is no "fix" to wait for. Those > stolen domains are broken and they will start to fail. The only difference > could be that fedora won't be the first where this breaks on, but I > thought "First" was

Re: F24 System Wide Change: Default Local DNS Resolver

Lennart Poettering wrote: > On Mon, 07.12.15 15:31, Björn Persson (Bjorn@rombobjörn.se) wrote: > > > Lennart Poettering wrote: > > > You *have* to use the local DNS servers by default, even if they are > > > crap. > > > > I for one want my laptop to be suspicious of random DNS servers it > > en

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 08:49:03AM -0500, Matthew Miller wrote: > On Mon, Dec 07, 2015 at 10:17:20AM +0100, Tomas Hozza wrote: > > > Older Netgear routers also used http://routerlogin.net before they were > > > set up. > > If they don't own the domain, then this is simply hijacking of domain > > na

Re: F24 System Wide Change: Default Local DNS Resolver

On Mon, Dec 07, 2015 at 04:12:20PM +0100, Lennart Poettering wrote: > On Mon, 07.12.15 13:25, Gerd Hoffmann (kra...@redhat.com) wrote: > > > Quite frankly: a setup like this one isn't just very typical for home > > > router networks, but also in many companies, where ".lan" or > > > ".companyname"

Re: Direct messages

If your username is krege you got at least three e-mail on 2015-11-26, -15 and -10 to krege fedoraproject org, therefore I suggest that you check your Spam folder/e-mail configuration. Correct. But there are no that messages on those dates. I do have three letters to krege at fedoraproject at