dnf-2 on F23 (Re: F23 System Wide Change: Python 3 as Default)

- Original Message - > From: "Zbigniew Jędrzejewski-Szmek" > To: devel@lists.fedoraproject.org > Sent: Wednesday, June 10, 2015 10:05:41 PM > Subject: Re: F23 System Wide Change: Python 3 as Default > > On Wed, Jun 10, 2015 at 08:50:14AM -0400, Jan Kurik wrote: > > = Proposed System Wid

Re: FESCo, Council and Env and Stacks elections - Nomination period is now open

Hello, this is just a reminder, that we still have opened Nomination period for Election to FESCo, Council and Env and Stacks. The nomination period will be open till June the 14th 23:59 UTC. If you are interested in these roles, please add yourself to the lists of nominees. If you have questio

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

- Original Message - > From: "Sandro Mani" > To: "Development discussions related to Fedora" > > Sent: Thursday, June 11, 2015 6:01:12 PM > Subject: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides > Hello, > Investigating bug #1230838, I noticed that when installing mmg3d

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

On 12.06.2015 10:28, Radek Holy wrote: *From: *"Sandro Mani" *To: *"Development discussions related to Fedora" *Sent: *Thursday, June 11, 2015 6:01:12 PM *Subject: *DNF vs YUM, $pkg, $pkg-mpi, $pkg

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

- Original Message - > From: "Sandro Mani" > To: "Development discussions related to Fedora" > > Sent: Friday, June 12, 2015 10:40:40 AM > Subject: Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides > On 12.06.2015 10:28, Radek Holy wrote: > > - Original Message

Re: F23 System Wide Change: Default Local DNS Resolver

On 11.06.2015 22:48, Dan Williams wrote: > On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wrote: >>> decision needs to then be made by the system. I believe that's been >>> mostly due to lack of time for the various parties to sit

Re: dnf install just stops - no explanation

> From: "Tonet Jallo" > In Peru i have the same problem, my ISP is implememtating NAT 3 in its > networks and i found more dnf hangs in some networks with NAT 3, but when i > try use dnf in other ISP network dnf works perfectly, the degmbug results > say some thing like "banned client by web serv

Re: F23 System Wide Change: SELinux policy store migration

On Thu, 11.06.15 06:51, Jan Kurik (jku...@redhat.com) wrote: > = Proposed System Wide Change: SELinux policy store migration = > https://fedoraproject.org/wiki/Changes/SELinuxPolicyStoreMigration I cannot make sense of this with my limited selinux knowledge, could you please elaborate on this on

Re: Better irc policies?

On Wed, 2015-06-10 at 11:20 -0600, Kevin Fenzi wrote: > Well, you signed up to this list to post this right? ;) Please also note that the IRC is not the only place we provide support. Users that aren't technical enough to sign up at the IRC can use http://ask.fedoraproject.org - which is really

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

On 11.06.2015 22:15, Susi Lehtola wrote: On 06/11/2015 09:01 AM, Sandro Mani wrote: So, whose fault is this? Packaging of dnf? Nothing relevant for this caught my eye skimming through the packaging guidelines. I think this is dnf's fault. YUm didn't have the same problem, since if multiple

Re: DKMS is not installing the right kernel-devel package

On Wed, Jun 10, 2015 at 8:44 AM, Dan Book wrote: > > > 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 ju

Re: DKMS is not installing the right kernel-devel package

On Fri, Jun 12, 2015 at 7:24 AM, Neal Gompa wrote: > What about some kind of virtual provides defined in repos/rpm/somewhere that > would automatically grab the kernel-devel package associated with the exact > kernel that is running at the time yum/dnf is installing a program that > depends on it?

Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

Josh Boyer wrote on 12.06.2015 13:55: > On Fri, Jun 12, 2015 at 7:24 AM, Neal Gompa wrote: > [...] > As I said, there are no great solutions here. A "works most of the time"-solution would be: Install kernel-devel by default. But I'm not seriously suggesting that, because I fully agree: It's not

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

- Original Message - > From: "Thorsten Leemhuis" > To: "Development discussions related to Fedora" > > Sent: Friday, June 12, 2015 2:19:10 PM > Subject: Can soft dependencies help to get the proper kernel-devel packages? > (Was: Soft- Re: DKMS is not installing > the right kernel-dev

DNF 1.0.1 Released

The new release brings fixes of the most occurred errors in Fedora 22. Moreover adds SSL support in repository configuration and random sleep dnf-automatic feature. Read more in 1.0.1 release notes [1] on DNF documentation page, try it from testing and give it a karma. [1] http://dnf.readthedocs

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On Fri, Jun 12, 2015 at 8:40 AM, Radek Holy wrote: > > > - Original Message - > > From: "Thorsten Leemhuis" > > To: "Development discussions related to Fedora" < > devel@lists.fedoraproject.org> > > Sent: Friday, June 12, 2015 2:19:10 PM > > Subject: Can soft dependencies help to get the

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

On 06/12/2015 10:28 AM, Radek Holy wrote: If a package "Requires: foo" and both "bar" and "barbaz" "Provides: foo", they are handled as being equally suitable. DNF/libsolv is not going to prefer packages with shorter names. Yes, very much agreed here. Please don't add the yum shortest name hack

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

- Original Message - > From: "Neal Gompa" > To: "Development discussions related to Fedora" > > Sent: Friday, June 12, 2015 2:48:19 PM > Subject: Re: Can soft dependencies help to get the proper kernel-devel > packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel > pack

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On 06/12/2015 02:40 PM, Radek Holy wrote: AFAIK, it is discussed these days whether weak dependencies can be used to express package preferences: https://fedoraproject.org/wiki/PackagingDrafts/WeakDependencies IIRC, there were some concerns but I don't remember what was the conclusion. The OR s

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On 06/12/2015 02:48 PM, Neal Gompa wrote: ​Soft/weak dependencies are allowed, according to FESCo It doesn't matter much what FESCO says of believes in this case. ATM, neither is the technical infrastructure is in place (it is evolving) nor are impact/consequences clear not are the prototypic

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On Fri, Jun 12, 2015 at 9:18 AM, Ralf Corsepius wrote: > On 06/12/2015 02:48 PM, Neal Gompa wrote: > >> Soft/weak dependencies are allowed, according to FESCo > > It doesn't matter much what FESCO says of believes in this case. > > ATM, neither is the technical infrastructure is in place (it is ev

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

- Original Message - > From: "Kalev Lember" > To: "Development discussions related to Fedora" > > Sent: Friday, June 12, 2015 3:09:50 PM > Subject: Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides > > On 06/12/2015 10:28 AM, Radek Holy wrote: > > If a package "Require

Orphaning some packages...

I'm orphaning the following packages: * rubygem-inifile * rubygem-mg * rubygem-wirble * vios-proxy -- Darryl L. Pierce http://mcpierce.blogspot.com/ Famous last words: "I wonder what happens if we do it this way?" pgp9ztSBrcbvk.pgp Description: PGP signature -- devel mailing list deve

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

On 06/11/2015 10:01 AM, Sandro Mani wrote: Hello, Investigating bug #1230838, I noticed that when installing mmg3d-libs, dnf installs Konsole output ptscotch-mpich, whereas yum-deprecated installs scotch. Both scotch and ptscotch-mpich provide the required libscotch.so.0()(64bit), albeit one in

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On 06/12/2015 03:23 PM, Neal Gompa wrote: On Fri, Jun 12, 2015 at 9:18 AM, Ralf Corsepius wrote: On 06/12/2015 02:48 PM, Neal Gompa wrote: Soft/weak dependencies are allowed, according to FESCo It doesn't matter much what FESCO says of believes in this case. ATM, neither is the technical i

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 10:58 +0200, Tomas Hozza wrote: > > > 3. NM waits for some signal from unbound/dnssec-trigger about the > > trustability of the DNS server > > If you think NM needs to do some action (as I don't), we don't have > problem with notifying NM (if you provide some API). > This

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 12 Jun 2015, Matthias Clasen wrote: I've just installed dnssec-trigger on rawhide to try this out, and found that it breaks networking on my Workstation. I used to get a network connection on login, now I get a question mark in top bar, and a status icon with obsure menu options appears.

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 09:57 -0400, Paul Wouters wrote: > On Fri, 12 Jun 2015, Matthias Clasen wrote: > > > I've just installed dnssec-trigger on rawhide to try this out, and > > found that it breaks networking on my Workstation. I used to get a > > network connection on login, now I get a question

Re: Can soft dependencies help to get the proper kernel-devel packages? (Was: Soft- Re: DKMS is not installing the right kernel-devel package)

On Fri, Jun 12, 2015 at 9:41 AM, Ralf Corsepius wrote: > On 06/12/2015 03:23 PM, Neal Gompa wrote: >> >> On Fri, Jun 12, 2015 at 9:18 AM, Ralf Corsepius >> wrote: >>> >>> On 06/12/2015 02:48 PM, Neal Gompa wrote: >>> Soft/weak dependencies are allowed, according to FESCo >>> >>> >>> It doesn

Re: DNF vs YUM, $pkg, $pkg-mpi, $pkg-openmpi having same provides

On 12.06.2015 15:34, Orion Poplawski wrote: On 06/11/2015 10:01 AM, Sandro Mani wrote: Hello, Investigating bug #1230838, I noticed that when installing mmg3d-libs, dnf installs Konsole output ptscotch-mpich, whereas yum-deprecated installs scotch. Both scotch and ptscotch-mpich provide the

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 09:57:38AM -0400, Paul Wouters wrote: > Did your networking actually break, or just the notification icon status? It will definitely break on F22 without the updated SELinux or SELinux in permissive mode. -- Matthew Miller Fedora Project Leader -- devel mailing list de

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 10:58:14AM +0200, Tomas Hozza wrote: > NetworkManager is pure network configuration manager in this scenario. > We don't expect nor want NM to handle /etc/resolv.conf. We will only get > the current network configuration from it and act upon it. NM > configuration will conta

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 10:20 -0400, Matthew Miller wrote: > On Fri, Jun 12, 2015 at 10:58:14AM +0200, Tomas Hozza wrote: > > NetworkManager is pure network configuration manager in this scenario. > > We don't expect nor want NM to handle /etc/resolv.conf. We will only get > > the current network con

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 12 Jun 2015, Matthew Miller wrote: Another integration concern: the network config GUI (and ifcfg files, for that matter) let me list specific DNS servers. With this feature, are those used (and if so, how)? If not, is my configuration just silently ignored? I do not know if it is supp

Re: dnf-2 on F23 (Re: F23 System Wide Change: Python 3 as Default)

On Fri, Jun 12, 2015 at 04:22:38AM -0400, Radek Holy wrote: > > > - Original Message - > > From: "Zbigniew Jędrzejewski-Szmek" > > To: devel@lists.fedoraproject.org > > Sent: Wednesday, June 10, 2015 10:05:41 PM > > Subject: Re: F23 System Wide Change: Python 3 as Default > > > > On Wed

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/12/2015 11:10 AM, Petr Spacek wrote: > HERE we need to coordinate with other parties who might want to write into the > /etc/resolv.conf file. These include (but might not be limited to): > NetworkManager > initscripts > dhclient > libreswan ? > resolved > connman >

freetype rebase

Hi, I've just rebased freetype in rawhide to freetype-2.6. There are 2 API changes because of which some packages can fail to build during next week's mass rebuild. The first one is that redefinition of function 'labs()' as 'ft_labs()' was removed. It is enough to use 'labs()' instead. The seco

Re: New contributor looking for Python projects/packages...

Hi All, Thank you for the responses and the suggestions. The Python SIG looks awesome. I'll definitely be looking into these. Thanks! Best, Alexander GS On Wed, Jun 10, 2015 at 8:13 AM, Stephen Gallagher wrote: > On Tue, 2015-06-09 at 17:38 -0400, Alex G.S. wrote: > > Devel, > > > > Fedor

Re: F23 System Wide Change: Default Local DNS Resolver

> On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wrote: >>> decision needs to then be made by the system. I believe that's been >>> mostly due to lack of time for the various parties to sit down and >>> plan and then program this f

Re: dnf install just stops - no explanation

On Sex, 2015-06-12 at 05:43 -0400, Jan Silhan wrote: > > From: "Tonet Jallo" > > > In Peru i have the same problem, my ISP is implememtating NAT 3 in its > > networks and i found more dnf hangs in some networks with NAT 3, but when i > > try use dnf in other ISP network dnf works perfectly, the d

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

On Thursday, June 11, 2015 08:36:38 AM Florian Weimer wrote: > 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 t

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 17:10 +0200, Petr Spacek wrote: > > On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: > >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wrote: > >>> decision needs to then be made by the system. I believe that's been > >>> mostly due to lack of time for the va

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 10:58 +0200, Tomas Hozza wrote: > On 11.06.2015 22:48, Dan Williams wrote: > > On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: > >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wrote: > >>> decision needs to then be made by the system. I believe that's been

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 11:53:32AM -0500, Dan Williams wrote: > Yeah, we did. From my recollection, most of that focused on the unbound > parts and how NM could add the dns=unbound stuff (which Pavel > contributed) but less on the NM connectivity checking, becuase Fedora > hadn't turned that on by

Re: F23 System Wide Change: SELinux policy store migration

On 06/12/2015 12:17 PM, Lennart Poettering wrote: > On Thu, 11.06.15 06:51, Jan Kurik (jku...@redhat.com) wrote: > >> = Proposed System Wide Change: SELinux policy store migration = >> https://fedoraproject.org/wiki/Changes/SELinuxPolicyStoreMigration > > I cannot make sense of this with my limit

Re: F23 System Wide Change: Default Local DNS Resolver

On 06/12/2015 12:53 PM, Dan Williams wrote: >> b) Broken networks: >> Some networks are so broken that even without captive portal they are not >> able >> to deliver DNSSEC data to the clients. >> >> In that case will try tunnel to other DNS servers on the Internet (Fedora >> Infra or public DNS r

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 00:48 -0400, Paul Wouters wrote: > On Thu, 11 Jun 2015, Dan Williams wrote: > > > Unfortunately the Proposal doesn't say anything about how this will > > actually work, which is something NetworkManager needs to know. It also > > fails to address the failure cases where your

Re: F23 System Wide Change: Default Local DNS Resolver

On Thu, 2015-06-11 at 14:41 -0700, Andrew Lutomirski wrote: > On Thu, Jun 11, 2015 at 1:48 PM, Dan Williams wrote: > > On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: > >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wrote: > >> > decision needs to then be made by the system. I

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 13:00 -0400, Matthew Miller wrote: > I hope we can get a design for this which integrates better with > GNOME > Shell and the existing network icon there. Well we're just not going to ship this in Workstation if it breaks NetworkManager's connectivity checking, nor will we s

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 12:17 -0500, Dan Williams wrote: > > dnssec-trigger prompts the user with a choice of "allow insecure > > DNS" or > > "cache only mode". The latter means "no new DNS and use what's > > already > > in the cache only". > > Yeah, and the interaction story here has been controv

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 12 Jun 2015, Matthew Miller wrote: I personally find the anchor icon very confusing. As a non-expert in this area, it doesn't represent anything which seems relevant to me, and all of the right click menu options, once I figured out to right click, are obscure to me. Agreed. I don't

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 10:17 AM, Dan Williams wrote: > On Fri, 2015-06-12 at 00:48 -0400, Paul Wouters wrote: >> 2) NM/dnssec-trigger does the HTTP and DNS probing and prompting using >> a dedicated container and any DNS requests in that container are >> thrown away with the container onc

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 10:33 AM, Dan Williams wrote: > On Thu, 2015-06-11 at 14:41 -0700, Andrew Lutomirski wrote: >> On Thu, Jun 11, 2015 at 1:48 PM, Dan Williams wrote: >> > On Tue, 2015-06-09 at 12:30 -0400, Matthew Miller wrote: >> >> On Tue, Jun 09, 2015 at 11:34:39AM -0400, Paul Wouters wr

Re: Build-essential packages

On 06/12/2015 12:11 PM, Dennis Gilmore wrote: > On Thursday, June 11, 2015 08:36:38 AM Florian Weimer wrote: >> 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 f

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 12 Jun 2015, Dan Williams wrote: That is why HTTP redirection and DNS failure have to be detected by whatever is the "hot spot detector". Both items weigh in on triggering a hotspot logon window. Agreed. But how does the DNS failure actually get relayed to the thing doing the HTTP req

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 12 Jun 2015, Andrew Lutomirski wrote: All that makes sense. Thanks. FWIW, I think that a little C program to spin up a namespace that's good enough to point a stateless Firefox instance at a captive portal login with overridden DNS nameserver settings would only be a couple of hundred

PHP package reviews for libraries in mediawiki

Hello, Mediawiki was bundling PHP libraries. The latest stable release is attempting to un-bundle them by clearly splitting them out into a "vendor" sub-directory. I have created package reviews for these libraries so they do not have to be bundled. I will work with swapping reviews, too. p

armv7 resources for package maintainers and qa folks

Greetings. I'd like to let package maintainers and qa folks know that we have some armv7 instances available if they need to debug/test/build/check something. For people in the 'packagers' fas group: arm03-packager00.cloud.fedoraproject.org - Fedora 22 arm03-packager01.cloud.fedoraproject.org

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, 2015-06-12 at 11:19 -0700, Andrew Lutomirski wrote: > It wouldn't really have to be Firefox, but getting the browser chrome > right to avoid trivial phishing attacks is critical, and all real > browsers already do that fairly well, whereas the simple embedded web > views (e.g. gnome-shell-p

Re: F23 System Wide Change: Default Local DNS Resolver

On Fri, Jun 12, 2015 at 3:32 PM, Michael Catanzaro wrote: > On Fri, 2015-06-12 at 11:19 -0700, Andrew Lutomirski wrote: >> It wouldn't really have to be Firefox, but getting the browser chrome >> right to avoid trivial phishing attacks is critical, and all real >> browsers already do that fairly w

Re: Qt 5 private headers

Ruslan Nigmatullin wrote: >> Are you willing to help work on it? :) > > Sure, I may have a look. How can I start? Start by identifying precisely what should be declared as private. Offhand I see: /usr/include/qt5/*/private/ /usr/lib(64)/qt5/mkspecs/modules/qt_lib*_private.pri anything more t

Re: Qt 5 private headers

12.06.2015, 16:32, "Rex Dieter" : > Ruslan Nigmatullin wrote: > >>>  Are you willing to help work on it? :) >> >>  Sure, I may have a look. How can I start? > > Start by identifying precisely what should be declared as private. Offhand > I see: > /usr/include/qt5/*/private/ > /usr/lib(64)/qt5/mks

Packaging Guidelines for Applications using Git Submodules

I'm trying to figure out the best way to handle the situation where a project decides to use submodules in Git. The archive generated doesn't incorporate the submodule files. I've done some searching on this, and haven't really come up with much. I've reviewed: Packaging:Github