Bug 441674

Summary: system-install-packages does not work
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: gnome-packagekitAssignee: Robin Norwood <robin.norwood>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: otaylor, robin.norwood
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-04-12 16:53:45 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:
Bug Depends On:    
Bug Blocks: 441857, 441977    

Description Tim Waugh 2008-04-09 13:30:09 UTC 
Description of problem:
The system-install-packages program does not work.

Version-Release number of selected component (if applicable):
gnome-packagekit-0.1.11-1.fc9

How reproducible:
100%

Steps to Reproduce:
1.yum remove -y hpijs || :
2.system-install-packages hpijs
  
Actual results:
Error dialog saying:

  Failed to install
  No such file ''

Expected results:
Package should be installed.

Additional info:
Worked fine in Fedora 8.
Comment 1 Owen Taylor 2008-04-10 15:25:06 UTC 
Right now system-install-packages is a symlink to gpk-install-file,
but s-i-p can install files or packages
What we need is a wrapper in our packaging that:

 - Checks if the arguments exist, if so does install-file
 - Otherwise does install-package
 - Dialogs if a mixture is specified

I'll work on that today. (We should actually change things to use 
gpk-install-package directly, I think, in the long term.)
Comment 2 Owen Taylor 2008-04-10 18:15:55 UTC 
I've committed a wrapper script and the .spec file changes to package CVS.
This can be closed when a package gets built and pushed.
Comment 3 Richard Hughes 2008-04-11 15:28:25 UTC 
Owen, you sure you committed it? - i can't see any such change in CVS/devel.
Comment 4 Owen Taylor 2008-04-11 16:26:44 UTC 
step 1: commit
step 2: write the above comment
step 3: notice that the commit failed with a conflict
step 4: merge, kick off a local build to make sure that the merge was OK
step 5: go off and do something else, forget about it

Now actually commited.
Comment 5 Richard Hughes 2008-04-12 16:53:45 UTC 
I've built this for rawhide and F9.