well im making a snow ball with the repquery  .. i will take other issue

today night i will implement the simulate_install_packages or make a patch
for gnome-packagekit no call it....

when end im send notify to devel-list .. for getting feedback from
foresighters ...

On Wed, Mar 10, 2010 at 4:57 PM, Andres Vargas <zod...@foresightlinux.org>wrote:

>
>
> On Sun, Mar 7, 2010 at 3:08 PM, Bertrand Juglas <b...@juglas.name> wrote:
>
>> I've not waited enough, pkcon update seems to have blocked after a
>> finished update, there was nothing more in the callback line printed
>>
>
> have the lastline printed ???
>
> on the callback its important the end because on the callback send the
> signals of packages whats installed... if tnever end ... then packagekit
> never know conary endprocess of updateall.
>
>
>> in the conary backend all so i had to kill the conary backend to retry
>> and pkmon showed the end of the update system.
>> Now I'm retrying with:
>> sudo pkcon update -y -p -v
>> It doesn't use progress bar but only Percentage lines.
>> It seems to have continued where it was blocked so it has managed to
>> finish, it's pretty annoying me :
>>
>
> im cannot check until now. :( the issue of repquery(
> http://zodman.aa.am/blog/entrada/2010/mar/9/conary-packagekit-its-taped-foresight-release)
> its consumming me.... i have a night trying to find the reason .. of why
> doing a repos.findtrove() taking alot of time end.
>
>
>> 2010/3/7 Bertrand Juglas <b...@juglas.name>:
>> > Hello,
>> > I've checked both, gnome-packagekit stills block after listing
>> > updates, i suppose it's because it doesn't manage to get updates
>> > details.
>> > The pkcon command line doesn't block but does not always updates the
>> > progress bar, mostly for pkcon update, so if you have a very slow wifi
>> > and don't watch the conary backend log, you don't see the progress,
>> > which makes you think it's blocked but it isn"t.
>> > Using a not updated packagekit command line instead of an updated
>> > conary command line doesn't seems really usefull. The main usage of
>> > PackageKit in Foresight is its gnome interface so we should unblock it
>> > as soon as possible, maybe by disabling blocking features if they are
>> > not essential.
>> > Hope it will help you Andres,
>> > have a good week !
>> >
>> > 2010/2/26 Andres Vargas <zod...@foresightlinux.org>:
>> >> check both!
>> >>
>> >> On Fri, Feb 26, 2010 at 2:09 AM, Bertrand Juglas <b...@juglas.name>
>> wrote:
>> >>
>> >>> I will test it during my french afternoon or evening so we can talk
>> about
>> >>> it
>> >>> ;)
>> >>> But you haven't precised if we shoult test the GUI of PackageKit or
>> the
>> >>> commandline or both, what should work after applying your updates?
>> >>> See you later !
>> >>>
>> >>> Le 26 févr. 2010 07:07, "Andres Vargas" <zod...@foresightlinux.org> a
>> >>> écrit :
>> >>>
>> >>> im push a a new branch on PackageKit git repo named conary-devel it
>> have
>> >>> small changes, what can solve the packagekit.
>> >>>
>> >>>
>> >>>
>> >>> Im commit the small patch to fl:2-devel with PackageKit 0.5.6 ...
>> >>>
>> >>>
>> >>>
>> >>> Im test it and seen its non blocker plz
>> >>>
>> >>>
>> >>> When run the packagekit ... check /tmp/conarybackend.log its a log of
>> >>> what conary backend its doing ... and check  if something
>> freeze/stoped
>> >>> for longo. When doing rquery sometimes take me a long time to
>> >>> solve .....
>> >>>
>> >>> Help me to test packagekit plz ....
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Foresight-devel mailing list
>> >>> Foresight-devel@lists.rpath.org
>> >>> http://lists.rpath.org/mailman/listinfo/foresight-devel
>> >>> _______________________________________________
>> >>> Foresight-devel mailing list
>> >>> Foresight-devel@lists.rpath.org
>> >>> http://lists.rpath.org/mailman/listinfo/foresight-devel
>> >>>
>> >> _______________________________________________
>> >> Foresight-devel mailing list
>> >> Foresight-devel@lists.rpath.org
>> >> http://lists.rpath.org/mailman/listinfo/foresight-devel
>> >>
>> >
>> _______________________________________________
>> Foresight-devel mailing list
>> Foresight-devel@lists.rpath.org
>> http://lists.rpath.org/mailman/listinfo/foresight-devel
>>
>
>
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to