Bug 1313666

Summary:	dnf: FutureWarning with --exclude=name
Product:	[Fedora] Fedora	Reporter:	Lukas Slebodnik <lslebodn>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	grgoffe, ignatenko, jsilhan, mluscon, packaging-team-maint, pnemade, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-26 15:48:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Slebodnik 2016-03-02 07:38:55 UTC

Description of problem:
Future warning is printed if dnf is called with argument --exclude


Version-Release number of selected component (if applicable):
dnf-1.1.6-2.fc24.noarch
python3-3.5.1-6.fc24.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
1. dnf update --exclude=dummy_name
# it can be also name of real package

Actual results:
/usr/lib64/python3.5/re.py:203: FutureWarning: split() requires a non-empty pattern match.
  return _compile(pattern, flags).split(string, maxsplit)

Expected results:
There isn't any warning.

Comment 1 Honza Silhan 2016-03-14 12:32:21 UTC

Thanks for the report.

Comment 2 Parag Nemade 2016-04-12 04:17:38 UTC

*** Bug 1326079 has been marked as a duplicate of this bug. ***

Comment 3 Igor Gnatenko 2016-04-26 15:48:19 UTC


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