[wpkg-users] [Bug 252] Query gives not the same result as synchronize

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=252

Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Rainer Meier <r.meier at wpkg.org>  ---
It does not use "different process" to evaluate update/downgrade etc.

I have fixed a bug regarding architecture. Architecture settings were not taken
into account in remote query mode. So it was always using the local
architecture for query.

Change log:

FIX: Remote query did not take arhictecture into account as saved within
     the settings database (wpkg.xml).
     Fixes bug 252. Thanks to Stefan Pendl.

     NOTE: Remote query will not take into account speial conditions based on
     other checks like file, registry, execute or uninstall. The reason is
     simply that these values are not available on a remote system.
     So WPKG will have to use local values for such checks.
     If you want to use remote query then you should not use such local-based
     checks in conditions in order to avoid getting query results which differ
     from the results on client side.


Please note that I don't think it will be possible to support remote queries
with other checks than host-information based information as this information
is simply unavailable on the remote host. To support all these queries it would
require to mirror basically the whole file system and registry as well.

So if you intent to use remote query with accurate results, then you're asked
not to use any non-host-information conditions in profile or package
assignment.

<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/src/main/resources/wpkg/>

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.