On Friday 19 January 2007 5:35 pm, Toby Johnson wrote:
> Eli Carter wrote:
> > Using a checkout of trunk from today, running on Linux (FC6):
> >
> > Connecting to database ../conversion-20070119h/my_vss-temp/vss_data.db
> >
> > Use of uninitialized value in concatenation (.) or string at ./vss2svn.
On Friday 19 January 2007 5:46 pm, Dirk wrote:
>
> > Connecting to database ../conversion-20070119h/my_vss-temp/vss_data.db
> >
> > Use of uninitialized value in concatenation (.) or string at ./vss2svn.pl
line
> > 1144.
> > Use of uninitialized value in concatenation (.) or string at ./vss2svn.
I'm building ssphys from the same svn checkout as the vss2svn. Is the ssphys
source in http://svn.pumacode.org/repos/vss2svn/trunk/ssphys not the right
ssphys for the vss2svn in
http://svn.pumacode.org/repos/vss2svn/trunk/script ???
The current "version.in" in trunk lists 0.22.0 as the cur
I'm getting this error message:
...
"./ssphys" info -ewindows-1252 "../t/myvss/data/p/peea"
WARNING: control character 0x12 in text input at character 2
WARNING: control character 0x01 in text input at character 1
WARNING: control character 0x01 in text input at character 1
WARNING: control cha
not well-formed (invalid token) at line 23, column 16, byte 835
at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm
line 187
I expect that means that the input file is corrupted in some fashion? (As
opposed to a typo in the XML parser.)
Yes, I would expect this, too
Dirk wrote:
Eli Carter schrieb:
On Monday 22 January 2007 11:32 am, Dirk wrote:
Huh. I just did a re-build, and it seems to be working. Ok, chalk
one uto user error. Sorry for the noise.
No problem. After several years of working, I came across a lot of
situations where we
Dirk, did you ever get a chance to test this patch? Would it be
possible for you to upload a new ssphys.exe? Send me a private email
if you need the login details again.
Ok, I have finished testing. Now all labels, filenames, comments, and so
on are in the correct encoding (* at least on my
Dirk wrote:
Dirk, did you ever get a chance to test this patch? Would it be
possible for you to upload a new ssphys.exe? Send me a private email
if you need the login details again.
Ok, I have finished testing. Now all labels, filenames, comments, and
so on are in the correct encoding (* at
@Toby: I think you can start to package a new version.
Sounds good... so I'm still using .exe version 0.22.0 from 19 January,
correct?
Yes, the issue was in vss2svn, not in ssphys. If you have time, you
could probably add a better check for a wrong version number or a failed
start of ssphy
I started a new module AutoProps to start development on this issue. I
is currently only a simple module that will read a subversion config.
But there is no functionality in there. Only a test. We will get a hash
of filepatterns/properties. So the next step is to evaluate the itempath
against a
Dirk wrote:
@Toby: I think you can start to package a new version.
Sounds good... so I'm still using .exe version 0.22.0 from 19
January, correct?
Yes, the issue was in vss2svn, not in ssphys. If you have time, you
could probably add a better check for a wrong version number or a
failed s
Dirk wrote:
I started a new module AutoProps to start development on this issue. I
is currently only a simple module that will read a subversion config.
But there is no functionality in there. Only a test. We will get a
hash of filepatterns/properties. So the next step is to evaluate the
itemp
12 matches
Mail list logo
