[wpkg-users] User GUI for WPKG-GP

Falko Trojahn wpkg at trojahn.de
Tue Sep 13 13:12:44 CEST 2016


Hello Nils,

first: many thanx for your efforts - your "taskbar updater" is the tool
we ever wanted, but never asked for ;)

>
> Regarding the generated update xml:
>  We have quite the uniform structure regarding os and software in our
> organisation so i didnt really thought about this problem. I had the
> idea you mentioned (using wpkg to query the updates) before but i
> ditched it because i didnt wanted to mess with wpkg-gp in any way 
> when
> i started the project.

The creation of the packages.xml is the problem here, too - we'd need 
to
run the python script on our samba server; the 
create_the_package_ver.exe
even produces an error here on our windows 7 test client:


Y:\packages\wpkg-gp-client\create_pkg_ver_list2>create_pkg_ver_list.exe
-f Y:\ -o test.xml

Traceback (most recent call last):

   File "create_pkg_ver_list.py", line 83, in <module>

   File "create_pkg_ver_list.py", line 44, in create_package_list

   File "<string>", line 62, in parse

   File "<string>", line 38, in parse

cElementTree.ParseError: undefined entity &tb-extension;: line 2, 
column 10

Failed to execute script create_pkg_ver_list


Is there a way to get a log of this run - e.g. to see which of
our xml files leads to this error? Wait, I see: the "undefined entity" 
error
comes from the "templating way" xmls for the thunderbird extensions.


>  Since i ended up creating my own fork anyway this is a good idea and
> it would also fix the problem of not being able to query newly
> installed packages, tho i wonder how big the impact on the wpkg 
> server
> would be if you do this i alot (im not an expert on this topic).
>
>  I will definatly look into this but it will take a bit longer since 
> i
> have to mess more with other peoples code :)

 From time to time we check the correct install/update/removes of all
clients using "wpkgCreateReport" .js tool from "gig mbh Berlin".
May be this could be another way to create the packages.xml server 
side,
since the information provided is per client - perhaps a good starting
point.

Nevertheless, the "wpkg.js /query" way is IMHO the way to go, even
if it is run locally once an hour or twice a day this would be 
sufficient
and should not give too much load on the server.

>
>  Thanks for the feedback!
on this page
  https://github.com/sonicnkt/wpkg-gp-client/wiki/Installation-and-Usage
the link to
   
https://github.com/sonicnkt/wpkg-gp-client/blob/master/wpkg-gp_client.ini
gives a 404 error ...

Best regards,
Falko



More information about the wpkg-users mailing list