Bug 1635694 - "excludes" CLI option ignores wildcard
Summary: "excludes" CLI option ignores wildcard
Keywords:
Status: CLOSED DUPLICATE of bug 1616118
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1628103
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 13:45 UTC by Vít Ondruch
Modified: 2018-10-05 18:38 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1628103
Environment:
Last Closed: 2018-10-05 18:38:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2018-10-03 13:45:11 UTC
+++ This bug was initially created as a clone of Bug #1628103 +++

It seems that the wildcard in "excludes" option is note respected:

~~~
$ LANG=C.UTF-8 sudo dnf update -x kernel\*
RCM Tools for Fedora 30 (RPMs)                                                                                                                                                     231  B/s | 286  B     00:01    
Failed to synchronize cache for repo 'rcm-tools-fedora-rpms', ignoring this repo.
Last metadata expiration check: 0:11:18 ago on Wed Oct  3 14:31:39 2018.
Dependencies resolved.

 Problem 1: cannot install the best update candidate for package kernel-core-4.17.14-200.fc28.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled
 Problem 2: cannot install the best update candidate for package kernel-core-4.18.5-300.fc29.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled
 Problem 3: cannot install the best update candidate for package kernel-core-4.18.10-300.fc29.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled
 Problem 4: cannot install the best update candidate for package kernel-modules-4.17.14-200.fc28.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled
 Problem 5: cannot install the best update candidate for package kernel-modules-4.18.5-300.fc29.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled
 Problem 6: cannot install the best update candidate for package kernel-modules-4.18.10-300.fc29.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is disabled

... snip ...
~~~

Isn't it somehow related to bug 1615377, where the excludes does not work as expected? Maybe the wildcard is not exploded somewhere ...

--- Additional comment from Vít Ondruch on 2018-10-03 15:32:17 CEST ---

(In reply to Vít Ondruch from comment #9)
> Isn't it somehow related to bug 1615377, where the excludes does
> not work as expected?

libdnf-0.20.0-2.fc30.x86_64 solves the bug 1615377, so it must be something else ...

Comment 1 Jaroslav Mracek 2018-10-03 21:03:59 UTC
Please can you confirm that issue is reproducible with libsolv-0.6.35-3 ? Thanks a lot.

Comment 2 Vít Ondruch 2018-10-04 06:21:03 UTC
(In reply to Jaroslav Mracek from comment #1)
> Please can you confirm that issue is reproducible with libsolv-0.6.35-3 ?
> Thanks a lot.

Yes, it is. The libsolv version was part of the original ticket I cloned and stripped (probably too much).

Comment 3 Jaroslav Mracek 2018-10-04 19:23:14 UTC
I am sorry, but I am unable to reproduce the issue. Please can you provide output from "rpm -q dnf libdnf libsol", "dnf repolist" and "dnf module list".

Comment 4 Vít Ondruch 2018-10-05 10:19:57 UTC
~~~
$ rpm -q dnf libdnf libsolv
dnf-3.6.1-2.fc30.noarch
libdnf-0.20.0-2.fc30.x86_64
libsolv-0.6.35-3.fc30.x86_64
~~~

I'll rather give you more explicit reproducer, so repositories won't play any role:

~~~
$ sudo dnf update --disablerepo=* --enablerepo=rawhide -x kernel\*
Last metadata expiration check: 0:04:27 ago on Fri Oct  5 12:12:17 2018.
Dependencies resolved.

 Problem 1: cannot install the best update candidate for package kernel-4.17.14-200.fc28.x86_64
  - package kernel-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 2: cannot install the best update candidate for package kernel-4.18.5-300.fc29.x86_64
  - package kernel-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 3: cannot install the best update candidate for package kernel-4.18.10-300.fc29.x86_64
  - package kernel-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 4: cannot install the best update candidate for package kernel-core-4.17.14-200.fc28.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 5: cannot install the best update candidate for package kernel-core-4.18.5-300.fc29.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 6: cannot install the best update candidate for package kernel-core-4.18.10-300.fc29.x86_64
  - package kernel-core-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 7: cannot install the best update candidate for package kernel-modules-4.17.14-200.fc28.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 8: cannot install the best update candidate for package kernel-modules-4.18.5-300.fc29.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded
 Problem 9: cannot install the best update candidate for package kernel-modules-4.18.10-300.fc29.x86_64
  - package kernel-modules-4.19.0-0.rc5.git3.1.fc30.x86_64 is excluded

... snip ...
~~~

Comment 5 Vít Ondruch 2018-10-05 10:23:54 UTC
BTW this is also interesting (note the missing wildcard):

~~~
$ LANG=C.UTF-8 sudo dnf update --disablerepo=* --enablerepo=rawhide -x kernel
Last metadata expiration check: 0:09:13 ago on Fri Oct  5 12:12:17 2018.
Error: 
 Problem: package kernel-4.17.14-200.fc28.x86_64 requires kernel-core-uname-r = 4.17.14-200.fc28.x86_64, but none of the providers can be installed
  - conflicting requests
  - problem with installed package kernel-4.17.14-200.fc28.x86_64
~~~

Comparing to previous, there were other packages, which would be installed. This case fails without any attempt to install any package.

Comment 6 Jaroslav Mracek 2018-10-05 10:40:01 UTC
Ok, In upstream I have an additional change for upgrade command that should fix the problem (dnf copr enable jmracek/dnf-upstream). Hope that it helps. There were multiple problems at the same place with nearly identical reports.

Comment 7 Vít Ondruch 2018-10-05 10:53:47 UTC
I am not sure I can install the DNF from Copr on my Rawhide. So I'll wait. The issue is just a bit annoying, not end of the world ;)

Comment 8 Jaroslav Mracek 2018-10-05 18:38:36 UTC
This is a duplicate of 1616118. Please if solution doesn't help, just reopen the bug report.

*** This bug has been marked as a duplicate of bug 1616118 ***


Note You need to log in before you can comment on or make changes to this bug.