Mandi! Rainer Meier
In chel di` si favelave...
I hope this will not have any unwanted side-effects. Test and
feedback is appreciated.
Quickly tested. Seems OK:
--- wpkg-voldemort-1.1.2.log.1 2011-07-20 18:29:47.005159123 +0200
+++ wpkg-voldemort-1.2.1rc3.log.1 2011-07-20
Hi Marco,
On 20.07.2011 18:33, Marco Gaiarin wrote:
Quickly tested. Seems OK:
Thanks for verifying.
Can I ask you to re-verify it in your environment with RC4?
http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.2/
I did some further improvements which should improve speed and
Hi Marco,
On 20.07.2011 18:33, Marco Gaiarin wrote:
Quickly tested. Seems OK:
Thanks for verifying.
Can I ask you to re-verify it in your environment with RC4?
http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.2/
I did some further improvements which should improve
Hi Stefan,
On 20.07.2011 23:16, Stefan Pendl wrote:
Seems host matching is now broken:
host name=VM-.+ profile-id=VirtuelleRechner /
Results in the attached log.
I have tested with the same regular expression and here it works for me. Would
you mind providing your hosts files:
-
Seems host matching is now broken:
host name=VM-.+ profile-id=VirtuelleRechner /
Results in the attached log.
I have tested with the same regular expression and here it
works for me. Would
you mind providing your hosts files:
- hosts/Hosts_PhysikalischeRechner.xml
-
Hi Stefan,
On 20.07.2011 23:16, Stefan Pendl wrote:
Seems host matching is now broken:
host name=VM-.+ profile-id=VirtuelleRechner /
Results in the attached log.
I have tested with the same regular expression and here it
works for me. Would
you mind providing your hosts
Hi Stefan,
On 20.07.2011 23:37, Stefan Pendl wrote:
Attached find the hosts files.
Many thanks for the files and for further testing. Indeed I seem to have broken
or over-optimized XML reading and forgot to take into account that loadXML()
seems not to modify the existing XML DOM source but
FIX: Fixed reading multiple XML files from directory. The
last commit included
too many optimizations and did not take into account
that MSXML creates a
new XML document when loadXML() is used on a XML DOM
object instead of
just modifying the existing one. So the root
Really i've not understood the new ''host matching'' schema, or i'm
missing something, but something big.
I've switched to wpkg.js 1.2, and at the fist run on a test machine:
2011-07-19 11:54:26, DEBUG : Initialized temporary local log file:
C:\WINDOWS\TEMP\wpkg-logInit.log
2011-07-19
Hi Marco,
On 19.07.2011 12:37, Marco Gaiarin wrote:
Really i've not understood the new ''host matching'' schema, or i'm
missing something, but something big.
I've switched to wpkg.js 1.2, and at the fist run on a test machine:
2011-07-19 11:54:26, DEBUG : Initialized temporary local log
information you provide it seems to be logical and intentional for
me that the
default profile is applied to the host since your name=. would
match all the
hosts. If you don't intend to match them all then make sure
hosts.xml does not
contain such a catch all host entry which will
Hi Heiko,
On 19.07.2011 13:51, heiko.hel...@horiba.com wrote:
information you provide it seems to be logical and intentional for
me that the
default profile is applied to the host since your name=. would
match all the
hosts. If you don't intend to match them all then make sure
Honestly I did even not think about this too much before since in my
mind people
were using one or the other, but not both. But as it's technically
possible to
use hosts.xml and hosts/*.xml at the same time I think the old
approach was more
logical.
I thought the same, but when I
Honestly I did even not think about this too much before since in my
mind people
were using one or the other, but not both. But as it's technically
possible to
use hosts.xml and hosts/*.xml at the same time I think the old
approach was more
logical.
I thought the same,
Mandi! heiko.hel...@horiba.com
In chel di` si favelave...
subdirectory. In one RC, WPKG started to load hosts.xml first and the
definitions in the hosts/ subdirectory after that.
Could be an explanation. I've reverted immediately to 1.1.2, and the
loga are now:
2011-07-19 13:01:51, DEBUG
Hi Stefan,
On 19.07.2011 17:36, Stefan Pendl wrote:
I might be able to check the logs to find the RC where this behavior changed.
Well, I did a diff between version 1.2 and 1.1.2 in the relevant functions and
did not discover a change in behavior. Maybe it was changed during fixing some
Hi Marco,
On 19.07.2011 18:24, Marco Gaiarin wrote:
Mandi! heiko.hel...@horiba.com
In chel di` si favelave...
subdirectory. In one RC, WPKG started to load hosts.xml first and the
definitions in the hosts/ subdirectory after that.
Could be an explanation. I've reverted immediately to
Mandi! Rainer Meier
In chel di` si favelave...
Maybe I will not have time today; meanwhile you can still use 1.1.2
or use the work-around.
Don't worry!
Sorry for any inconvenience,
Don't worry! Looking at previous mesage seems also that the ''guilty''
could be also the Microsoft XML
Many thanks for the log. It seems to clearly read the files
from the hosts/
folder first while WPKG 1.2 reads hosts.xml first. I will
investigate why this
happens. And yes, I plan to revert to previous behavior if
technically feasible.
Maybe I will not have time today; meanwhile
Hi Stefan,
On 19.07.2011 19:00, Stefan Pendl wrote:
Investigating the wpkg.js source, there has nothing changed in the function
used to get the hosts information.
The file was always read before the folder from a source code point of view.
Right, that's then exactly what I was wondering
Investigating the wpkg.js source, there has nothing changed
in the function used to get the hosts information.
The file was always read before the folder from a source
code point of view.
Right, that's then exactly what I was wondering about.
However probably we
should clearly
Hi Stefan,
On 19.07.2011 21:18, Stefan Pendl wrote:
What I can think of is that the host matching has reversed.
Previously it was done back-to-front, whereas now it is done front-to-back,
since host matching code has surly changed to support
/allowMultiple.
Good hint. But I had a look at
Hi all,
On 19.07.2011 22:01, Rainer Meier wrote:
But I see that historically (compared many old versions) the hosts.xml file was
always loaded first. Which is probably the wrong way around. So I am going to
implement it the other way around.
Let's see what will happen.
I have just checked in
23 matches
Mail list logo
