Re: DNF package upgrade availability/discovery blocked by versionlocks

On Fri, Mar 24, 2017 at 10:38 AM, Felix Miata wrote: > Michael Mraka composed on 2017-03-24 08:54 (UTC+0100): > >> Felix Miata: > > >>> [mc-4.8.18 has been broken since release, so I locked 4.8.17] > > ... >>> >>> How is one expected to discover via dnf when (18 day old)

Re: dnf group and dnf group list diff ?

Hi, it seems like a bug. Can you please report a bug here [1], include whole output of `dnf group`, `dnf group summary`, `dnf list` and `cat /var/lib/dnf/groups.json`? Thanks, Honza [1] https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora=dnf On Fri, Feb 24, 2017 at 8:18 PM, Catalin

Re: Dependency rebuild order

Hi, my former colleague was investigating how to do it. This task had been already solved by the mach project available at http://thomas.apestaart.org/projects/mach/ and packaged in Fedora under the same name. Interesting bits are inside ./scirpts/mach.in (more specifically in Root.rebuild() and

Re: When to make packeges "dnf protected"

On Sat, Dec 3, 2016 at 7:34 PM, Neal Gompa wrote: > On Sat, Dec 3, 2016 at 1:10 PM, Rolf Fokkens wrote: >> Hi all, Hi, >> As the maintainer of bcache-tools I ran into the situation that a collegue >> accidentally removed bcache-tools, resulting in a

Re: dnf pulling in kernel-debug for L2TP

On Mon, Nov 7, 2016 at 3:54 AM, Chris Adams wrote: > I was trying to figure out why I had kernel-debug* packages installed, > and tracked it to xl2tpd wanting "kmod(l2tp_ppp.ko)". That is provided > by kernel-debug-modules-extra and kernel-modules-extra; dnf choose to >

Re: DNF and PackageKit background data usage

On Thu, Nov 3, 2016 at 10:13 AM, Gerd Hoffmann wrote: > Hi, > >> > The metalinks already provide checksums and timestamps for the >> > metadata. So instead of dumbly going out and re-downloading the entire >> > metadata at hardcoded intervals, couldn't we rather just check if

Re: DNF and PackageKit background data usage

On Tue, Nov 1, 2016 at 9:59 AM, Miroslav Suchý wrote: > Dne 31.10.2016 v 12:55 Tom Hughes napsal(a): >> The problem, as I believe has been repeatedly explained, is that you don't >> really have any idea whether the connection >> is metered. Yes you may be trying to guess by

Re: User Visible Terminology

Hi On Fri, Sep 16, 2016 at 5:02 PM, Petr Šabata wrote: > On Thu, Sep 15, 2016 at 10:59:55AM -0400, Matthew Miller wrote: >> On Thu, Sep 15, 2016 at 02:25:52PM -, Mary Clarke wrote: >> > * enable vs install vs select >> >> select is the worst :) > > It's what I

Re: Last DNF-1 version, DNF-2 coming to rawhide

On Fri, Sep 2, 2016 at 5:20 PM, Tomasz Torcz <to...@pipebreaker.pl> wrote: > On Fri, Sep 02, 2016 at 05:04:40PM +0200, Honza Silhan wrote: >> >> DNF-2 release candidate will land into rawhide. It will bring many new >> features and bug fixes. DNF-2 is using libdnf ins

Last DNF-1 version, DNF-2 coming to rawhide

Hi, DNF-1.1.10 and DNF-PLUGINS-CORE-0.1.21 has been released. Note this will be the last version and only critical bug fixes will be backported into DNF-1. Look into release notes [1][2] for more details. DNF-2 (current DNF upstream) will be actively developed and take the lead. DNF-2 release

[EPEL-devel] Re: new DNF for everyone

On Fri, Aug 26, 2016 at 9:39 PM, Orion Poplawski wrote: Hi, > On 08/26/2016 12:26 PM, Sérgio Basto wrote: >> On Sex, 2016-07-01 at 13:04 -0400, Honza Šilhan wrote: >>> Hi, >>> >>> DNF is in EPEL for more than one year, unfortunately there was still >>> the old >>> DNF-0.6.4