Bug 459868

Summary:	Package installer doesn't check local directory for dependency resolution
Product:	[Fedora] Fedora	Reporter:	Bevis King <brwk>
Component:	gnome-packagekit	Assignee:	Robin Norwood <robin.norwood>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9	CC:	rhughes, richard
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-14 13:08:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bevis King 2008-08-23 10:04:16 UTC

Description of problem:
When you attempt to install a package using the package installer by right clicking on a file, it does not check the location of the original file when resolving dependencies, nor does it give an option to do so.  Also if you select all the necessary files using <CTRL>-<left-click>, it tries to invoke package installer for all of them instead of consolidating it into a single request (which would enable the user to specify the additional packages needed).

Thus you want to install package xyz which in turn needs package xyz-core, xyz-samples, and xyz-tools - all four packages are present in your Download directory; you browse there (via user's home icon, etc) right click on xyz and choose "Install Package" and it'll tell you it can't because it can't resolve the dependencies because xyz-core, xyz-samples and xyz-tools are not available.  Yet they are in the directory that the xyz package is being installed from.

Version-Release number of selected component (if applicable):
gnome-packagekit-0.1.12-12.20080430.fc9.x86_64

How reproducible:
All the time.

Steps to Reproduce:
1.  Download some RPMs which have dependencies on each other
2.  Browse in Nautilus to the Download directory
3.  Right click, choose Install Package on one of them
4.  Give root password if necessary
5.  Dependency resolution will fail and package can not be installed
  
Actual results:
Installation fails.

Expected results:
Installer checks for having been provided with the necessary dependency packages in the same directory or offers the user a file browser to select the packages that will resolve the dependency stated.

Additional info:

Comment 1 Bevis King 2008-08-23 10:31:13 UTC

If you have mutual dependencies, ie xyz-tools needs xyz and xyz needs xyz-tools it is impossible to install the packages using this method due to this problem.  Granted that is probably broken packaging...

Comment 2 Richard Hughes 2008-08-23 12:03:34 UTC

Can you try to upgrade to 0.2.4 and then repeat the control-click install method please? 0.1.x was unable to batch install local files, but 0.2.x should be able to. I don't want to include the PWD or a random directory for depsolving as this will produce results the user may not expect.