[wpkg-users] WPKG-gp on 64-bit? Also, WPKG Client issues on Win7 and a wpkg.js bug

Brent A Nelson brent at phys.ufl.edu
Tue Apr 6 23:16:47 CEST 2010

On Tue, 6 Apr 2010, Rainer Meier wrote:

> Hi,
> On 06.04.2010 01:07, Brent A Nelson wrote:
>> PPS While I'm at it, I'll mention that wpkg.js 1.1.2 can not reliably
>> process dozens of individual XML files, at least in the case of packages
>> definitions.  We had to use the little merge script that was posted (on
>> the wiki?); otherwise, WPKG would simply not see several packages (and
>> as you add more packages, the ones that are invisible change).  I
>> believe it did claim to read all the xml files.  There's a bug in there
>> somewhere. Merged together into a packages.xml, though, wpkg has been
>> great.
> Could you try the latest (unreleased) stable version (1.1.3-RC3)?
> It's available here:
> <http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/wpkg.js?revision=118>
> In fact I think the code to read XML files has not been altered since a very
> long time and you seem to be the first one having troubles with it.
> Does this happen on all nodes or just on a few?
> Could it be network related?
> Can you post or send me a full debug log of WPKG? Any exceptions printed?
> If there are exceptions we might catch them and retry reading the file if an
> error occurs.
> Probably it's about the format or encoding of the XML file(s). If you're able to
> identify a specific file where it happens you could send it to the list for
> analysis.
> Without any reproducible use-case it's difficult to identify any problem.

It must have been a temporary issue with my setup or my test client.

I experienced it when I was doing a lot of development on just one or two 
clients, a couple of months ago.  Perhaps the client wpkg.xml files were 
confused, or there were broken packages that have since been fixed, but I 
can no longer reproduce the problem with my setup.  I'll leave my packages 
unmerged as separate files (all 53 of them, and growing) and be sure to 
report if the problem resurfaces.



More information about the wpkg-users mailing list