[wpkg-users] Help with error message:

[Tomasz Chmielewski]

sbotsford wrote:

(...)

>> 1) Could you send me your profiles.xml, hosts.xml and packages.xml?
>>
> Added as attachments
>> 2) What version of WPKG do you use? Could you try the latest testing 
>> (0.9.8-test2)?
>>
> This is the first thing I tried.  Identical behaviour.  Scripten is 
> version 5.6 from the link on the wpkg web page.
> 
>> 3) do you still get this error when you use same profile + packages, 
>> but for a different host?
>>
> 
> No.  If I run wpkg for the classes of machines lab* it does what I 
> expect.  (Not all of what I want, yet, but it works and installs the 3-4 
> packages I've got working properly.)

So you're saying that exactly the same profiles + packages wor for one 
host, but don't work for another?

Then you're probably being affected by some Windows component that's 
either missing, disabled or broken etc.

On a newly installed XP system, WPKG works out of the box, for Windows 
2000 you only have to install "scripten".
Did you see "Code: 800a0030..." thread?

The easiest way to recover from such a situation would be to reinstall 
the affected machines from scratch.
It can be done via using Unattended (http://unattended.sf.net).


>  From your message this is something being spewed out by cscript, and 
> not by wpkg itself.  This by itself is helpful.  Are there alternate js 
> interpreters that give better debugging info?

I'm not aware of any other js interpreters.


> ***
> 
> My next step will be to remove the packages from that profile.  See if I 
> can narrow it down.  I'm betting on a stupid syntax error in my xml files.

If there was a syntax error in any of xml files, it should be reported 
by WPKG.


> ***
> On debugging.  dviPS, part of the TeX distribution has one of the best 
> debugging interfaces I've run into.  With it you gave debug what 
> amounted to a bit field.
> debug = 1    Specials   
> debug = 2    paths
> debug = 4    fonts
> debug = 8    pages
> ... and so on.
> Summing them up allowed you to pick combinations.
> 
> Suppose on wpkg it was something like:
> debug = 1    XML parsing  (Show parse tree?)
> debug = 2    Consistency checking.  (Prints out if host file contains 
> profiles that aren't in profiles, if profiles reference packages that 
> aren't in packages.
> debug = 4    Detailed package checking.  (Verifies the existence of 
> paths, and commands)
> debug = 8    Print the command about to be executed, wait for keypress, 
> print exit status.
> debug = 16    Put the interpreter into some form of debug mode
> 
> Now, I haven't the experience with either XML, JS, or winsnooze to say 
> if any these are good ideas.  Maybe they will spark your ideas.

There is a patch pending to do something like this (sort of). You can 
find it on http://bugs.wpkg.org (search through "open bugs").
But as I said, I guess it has something to do with the host? I don't know.

-- 
Tomasz Chmielewski
http://wpkg.org

_______________________________________________
wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users