[packagekit] PackageKit-Gnome issues in Ubuntu Maverick

Daniel Nicoletti dantti85-pk at yahoo.com.br
Thu Oct 14 21:54:39 PDT 2010


BTW aptcc and python apt backends both have the PATH set. What backend are you 
using?
Using KPackageKit works?

Best.
 ________________________________
Daniel Nicoletti - KDE Developer
http://dantti.wordpress.com
When a wicked man dies, his hope perishes;
all he expected from his power comes to nothing. Prov. 11:7



----- Mensagem original ----
> De: Anders F Björklund <afb at algonet.se>
> Para: PackageKit users and developers list <packagekit at lists.freedesktop.org>
> Enviadas: Quinta-feira, 14 de Outubro de 2010 13:27:14
> Assunto: Re: [packagekit] PackageKit-Gnome issues in Ubuntu Maverick
> 
> Jean Hubbard wrote:
> 
> > I have submitted a bug in regards to this. Bug  #634053. This has been in 
>ongoing problem in Ubuntu. When it has showed the  packages, they dont install. 
>I believe that was the case with Lucid. The smart  backend seems to have similar 
>issues. Bug #598165. Hasnt worked at all since i  been trying it in Karmic.
> 
> I don't think the smart backend bugs were ever  posted upstream ?
> 
> https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/598165
> 
> 
> The  problem is that PackageKit doesn't set PATH for the smart  backend.
> 
> commit e2e963fc22ddbd70575f5cbd42d074789396e4bf
> 
>      APT-DBUS: dpkg requires a PATH variable, so set it. Minior code clean  
>ups.
> 
> 
> Adding the same PATH workaround to the smartBackend too makes it  work:
> 
> +# Required for daemon mode
> +os.putenv("PATH",  
>"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin")
> +
>  if  __name__ == "__main__":
>       main()
> 
> --anders
> 
> _______________________________________________
> PackageKit  mailing list
> PackageKit at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/packagekit
> 


      



More information about the PackageKit mailing list