Bug 1512016

Summary:	dnf: conflicting requests - package disabled
Product:	[Fedora] Fedora	Reporter:	Andreas WERNER <wernand>
Component:	dnf	Assignee:	Jaroslav Mracek <jmracek>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	dmach, gtirloni, igor.raits, jmracek, nsoffer, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-12 17:12:08 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 Andreas WERNER 2017-11-10 16:28:48 UTC

Description of problem:

reinstallation of already once manually successfully installed package not possible 


Version-Release number of selected component (if applicable):
dnf
Version      : 2.7.5
Release      : 1.fc26


How reproducible:

Do a local install with dnf, erase installation and try to reinstall again.


Steps to Reproduce:
1. install a package manually by "dnf install /pathtopackage/package.rpm"
2. uninstall package by "dnf erase package"
3. reinstall package by "dnf install /pathtopackage/package.rpm"

Actual results:
error: 
 Problem: conflicting requests
  - package package.x86_64 is disabled


Expected results:

package is installed again as it did the first time


Additional info:

"dnf history info ID" confirms installation and uninstallation of package.rpm with success

Comment 1 Andreas WERNER 2017-11-11 10:34:05 UTC

config files from earlier versions have to be removed prior installation of newer version.

Message is confusing.

Comment 2 Nir Soffer 2018-01-08 10:16:39 UTC

(In reply to Andreas WERNER from comment #1)
> config files from earlier versions have to be removed prior installation of
> newer version.

What config files? where?

How a user is supposed to handle this situation?

> Message is confusing.

So how are we going to fix this?

Comment 3 Giovanni Tirloni 2018-04-16 18:31:32 UTC

Just experienced this today. It's really confusing.

Comment 4 Jaroslav Mracek 2018-06-15 07:28:48 UTC

Please can anyone provide additional information like reproducer with exact package. Additionally please can you reproduce the issue with dnf-3.0 for our repo (dnf copr enable rpmsoftwaremanagement/dnf-nightly)? Additionally outputs in dnf.log with only transaction related to reproducer could be also handy. Thanks a lot.

Comment 5 Ben Cotton 2018-11-26 15:50:08 UTC

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Jaroslav Mracek 2019-04-12 17:12:08 UTC

I believe that the issue is fixed in Fedora 29. Without additional information or reproducer we cannot do more.