Back to bug 2155713

Who When What Removed Added
Red Hat Bugzilla 2022-12-22 01:40:42 UTC Pool ID sst_cs_software_management_rhel_8
Red Hat One Jira (issues.redhat.com) 2022-12-22 02:18:39 UTC Link ID Red Hat Issue Tracker RHELPLAN-143067
Stepan Broz 2022-12-22 14:40:03 UTC Severity medium urgent
CC sbroz
Priority unspecified urgent
Stepan Broz 2022-12-22 15:57:23 UTC Keywords EasyFix, Patch
Component dnf libdnf
Pavla Kratochvilova 2023-01-02 14:13:24 UTC Keywords Triaged
CC pkratoch
Priority urgent medium
Jaroslav Rohel 2023-02-06 15:23:16 UTC CC jcastran
Assignee packaging-team-maint jrohel
CC jrohel
Martin Banas 2023-03-21 06:51:07 UTC CC mbanas
Martin Banas 2023-05-22 08:28:12 UTC Flags needinfo?(jrohel)
Jaroslav Rohel 2023-05-24 11:13:01 UTC Status NEW POST
Flags needinfo?(jrohel)
Martin Banas 2023-06-07 06:14:17 UTC Fixed In Version libdnf-0.63.0-16.el8
Doc Type If docs needed, set a value Bug Fix
Nicola Sella 2023-06-07 08:59:08 UTC CC nsella
Status POST MODIFIED
Eva Mrakova 2023-06-13 11:33:24 UTC QA Contact swm-qe emrakova
errata-xmlrpc 2023-06-13 12:45:49 UTC Status MODIFIED ON_QA
Eva Mrakova 2023-06-14 10:58:46 UTC Status ON_QA VERIFIED
Jaroslav Rohel 2023-08-14 08:37:50 UTC Doc Text Cause:
"proxy=_none_" sets the proxy name to "_none_". But in YUM (RHEL 7) "_none_" has a special meaning -> don't change proxy settings.

Consequence:
A configuration file from RHEL 7 containing "proxy=_none_" is not compatible with DNF.

Fix:
In the DNF proxy settings, treat "_none_" as an empty string. An empty string has the same meaning as "_none_" in YUM.

Result:
"proxy=_none_" means do not change proxy settings. The configuration is backward compatible with YUM (RHEL 7).

Back to bug 2155713