<br><tt><font size=2>On 6 October 2010 16:23, <rotru@br.ibm.com>
wrote:<br>
>> I uploaded an example of the codes here:<br>
>> We have to hide some repositories and make them available
on the fly when specific users run yum or any front-end application to
it .<br>
>> We get the repos from a webservice and add them dynamically.<br>
<br>
> Right, now your error makes sense. PackageKit doesn't really support<br>
> adding and removing repos like this. Put bluntly, it's a hack, and
I'm<br>
> surprised it even worked in yum.</font></tt>
<br>
<br><tt><font size=2>Not sure if we could call it a hack, because the plugins
were developed</font></tt>
<br><tt><font size=2>to support stuff like that: exclude packages, add/remove
repos, disable</font></tt>
<br><tt><font size=2>plugins, etc. The plugin have been worked for more
then 5 years. I have</font></tt>
<br><tt><font size=2>not seen issues in the yum command line and with Yumex
nether.</font></tt>
<br><tt><font size=2><br>
<br>
> Are you assuming that the UID of the yum process is going to be<br>
> different for each user? PackageKit runs yum as root in a very secure<br>
> clean environment. Without looking at the actual source of your<br>
> plugin, I can't really tell that from your examples.<br>
<br>
No, no, I do not use the Yum process UID. The plugin behavior is the same</font></tt>
<br><tt><font size=2>as the examples I provided. The only difference is
that every user has a</font></tt>
<br><tt><font size=2>kind of UID (locally written), that is what I send
to the webservice, to</font></tt>
<br><tt><font size=2>get the proper repos as a string stream. In the examples
I omitted this </font></tt>
<br><tt><font size=2>part and wrote the repos string like if I was received
from the webservice.</font></tt>
<br><tt><font size=2><br>
</font></tt>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif"><br>
Rodrigo Trujillo</font>