From Fedora Project Wiki

(update FAQ)
m (Updated broken link.)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= PackageKit Frequently Asked Questions =
{{Admon/note |  This page is for historical reference only.  Much of this information does not apply to other releases beyond Fedora 9 }}
 
== Generic questions ==
== Generic questions ==


* Please see http://www.packagekit.org/pk-faq.html for the most up to date list
Please visit http://www.packagekit.org/ for the most recent news and information relating to the project.


== Fedora specific questions ==
== Fedora specific questions ==


=== What's the status of GPG key import?  ===
=== add/remove programs and gpk-install-file do not work when run as the root user! ===
 
The decision to use PackageKit over pup or pirut in Fedora was taken only very late in the Fedora 9 planning process. At the time the decision was made, PackageKit had just branched for 0.2.x. 0.1.x was in bugfix and trivial fix mode, with no new features allowed. GPG key signing was pretty broken on F9 for a few months.
 
Now 0.2.x is in F9, and 0.3.x is in F10, and 0.4.x is in rawhide, all the GPG key issues are now fixed. Please open bugs if you have problems.
 
=== Why can't I install multiple packages with pkcon, gpk-install-package or system-install-packages? ===
 
If you use Fedora 10 or rawhide, you can.
 
=== Why can't I install multiple packages with 0.1.x or 0.2.x? ===
 
We are looking for input on how the user interface should look like. Jump on the PackageKit mailing list if you have any ideas.
 
=== What about group installations ? ===
 
Request for enhancement has already been filed at https://bugzilla.redhat.com/show_bug.cgi?id=435768
 
=== system-install-packages and gpk-install-file do not work when run as the root user! ===


GTK+ tools should not be run as root. Any GTK+ program run as the root user is a massive security hole -- GTK+ just isn't designed with this in mind. There are numerous attack vectors when running as root, and so we shouldn't be letting programs do such insane, insecure things.
GTK+ tools should not be run as root. Any GTK+ program run as the root user is a massive security hole -- GTK+ just isn't designed with this in mind. There are numerous attack vectors when running as root, and so we shouldn't be letting programs do such insane, insecure things.


=== Lots of f10 packages are showing up! ===
PackageKit is fully compliant with PolicyKit, which offers easy authentication for regular user accounts to perform authorized system administration tasks like software installation.  PolicyKit provides a dialog into which a user can provide the root password, and even hold this authorization permanently so the dialog is not required again later. Logging in as root is not necessary to install packages.
 
I have been running F9 testing for a while and I'm now getting notified of hundreds of fc10 packages.
 
You should run:
<pre>
yum clean all
</pre>
This is a problem with PackageKit being confused by some pre-F9-release metadata you had laying around.


=== PackageKit won't work without NetworkManager ===
=== PackageKit won't work without NetworkManager ===


PackageKit 0.1.0 uses NetworkManager to get network state. 0.2.x provides unix fallbacks and also allows admins to tell PK to ignore NM using the config file.
To continue using PackageKit without NetworkManager, either disable the NetworkManager service, or edit {{filename|/etc/PackageKit/PackageKit.conf}} and change the following value:
0.2.2 will be backported soon.
<pre>UseNetworkManager=false</pre>


=== PackageKit won't work with my proxy server ===
=== PackageKit won't work with my proxy server ===


Short answer:
Short answer:
We're working on it.
If you set this in the "Network Proxy" capplet in GNOME then it should just work. If you need to make manual changes then change the values in {{filename|/etc/PackageKit/PackageKit.conf}}.
 
Long answer:
packagekitd runs as root. This means any session policy will not be used, and any http_proxy variables will have to be exported system wide.
Uisng 0.2.1 you can set the proxy settings in the /etc/PackageKit/PackageKit.conf config file - In 0.2.2 we are fixing this to allow the user to change the system proxy values for PackageKit in the session - hopefully with everything working without any user interaction.


== List of issues filed ==
== List of issues filed ==


* https://bugzilla.redhat.com/buglist.cgi?product=Fedora&version=9&component=gnome-packagekit&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=
For a list of PackageKit issues, visit [https://bugzilla.redhat.com/buglist.cgi?product=Fedora&version=9&component=gnome-packagekit&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc= this link].

Latest revision as of 07:51, 2 October 2015

Note.png
This page is for historical reference only. Much of this information does not apply to other releases beyond Fedora 9

Generic questions

Please visit http://www.packagekit.org/ for the most recent news and information relating to the project.

Fedora specific questions

add/remove programs and gpk-install-file do not work when run as the root user!

GTK+ tools should not be run as root. Any GTK+ program run as the root user is a massive security hole -- GTK+ just isn't designed with this in mind. There are numerous attack vectors when running as root, and so we shouldn't be letting programs do such insane, insecure things.

PackageKit is fully compliant with PolicyKit, which offers easy authentication for regular user accounts to perform authorized system administration tasks like software installation. PolicyKit provides a dialog into which a user can provide the root password, and even hold this authorization permanently so the dialog is not required again later. Logging in as root is not necessary to install packages.

PackageKit won't work without NetworkManager

To continue using PackageKit without NetworkManager, either disable the NetworkManager service, or edit /etc/PackageKit/PackageKit.conf and change the following value:

UseNetworkManager=false

PackageKit won't work with my proxy server

Short answer: If you set this in the "Network Proxy" capplet in GNOME then it should just work. If you need to make manual changes then change the values in /etc/PackageKit/PackageKit.conf.

List of issues filed

For a list of PackageKit issues, visit this link.