From vadm at googlecode.com  Mon Feb 22 16:08:03 2010
From: vadm at googlecode.com (vadm at googlecode.com)
Date: Mon, 22 Feb 2010 15:08:03 +0000
Subject: [vadm] Issue 4 in vadm: UnicodeDecodeError
Message-ID: <0-5713915690563136699-756257951070810024-vadm=googlecode.com@googlecode.com>

Status: Accepted
Owner: wouter.vanden.hove
Labels: Type-Defect Priority-Medium

New issue 4 by wouter.vanden.hove: UnicodeDecodeError
http://code.google.com/p/vadm/issues/detail?id=4

What steps will reproduce the problem?
1. vadm 0.6.2 + py 1.2.1
2. vadm add a file containing non-ascii chars

What is the expected output? What do you see instead?

{{{
zopeusr at porttst1: /home/zopeusr/bin > vadm commit  /  -m 'autocommit'
Traceback (most recent call last):
   File "/usr/local/bin/vadm", line 5, in <module>
     pkg_resources.run_script('vadm==0.6.2', 'vadm')
   File
"/opt/tools/vadm/lib/python2.5/site-packages/setuptools-0.6c11-py2.5.egg/pkg_resources.py",
line 489, in run_script
   File
"/opt/tools/vadm/lib/python2.5/site-packages/setuptools-0.6c11-py2.5.egg/pkg_resources.py",
line 1207, in run_script
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/EGG-INFO/scripts/vadm",
line 16, in <module>
     main()
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/EGG-INFO/scripts/vadm",
line 13, in main
     vadm.cmdline.main()
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/cmdline.py",
line 576, in main
     return session.cmd(*args)
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/cmdline.py",
line 65, in cmd
     command.execute()
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/cmdline.py",
line 391, in execute
     self.prepare_wc()
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/cmdline.py",
line 128, in prepare_wc
     vadm.sync.all_fs2wc(self.session)
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/sync.py",
line 97, in all_fs2wc
     content_fs2wc(session, target, wcpath)
   File
"/opt/tools/vadm/lib/python2.5/site-packages/vadm-0.6.2-py2.5.egg/vadm/sync.py",
line 68, in content_fs2wc
     wcpath.write(target.read())
   File
"/opt/tools/vadm/lib/python2.5/site-packages/py-1.1.1-py2.5.egg/py/impl/path/svnwc.py",
line 533, in write
     self.localpath.write(content, mode)
   File
"/opt/tools/vadm/lib/python2.5/site-packages/py-1.1.1-py2.5.egg/py/impl/path/local.py",
line 377, in write
     data = py.builtin._totext(data, sys.getdefaultencoding())
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 109:
ordinal not in range(128)
}}}

In my case, the position 109 contained indeed a non-ascii character (?,
?,...) but the beginning of the file was marked at utf-8 with:
{{{
# -*- coding: utf-8 -*-
}}}

However, the problem does not occur when downgrading to py 1.0.2



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

From vadm at googlecode.com  Mon Feb 22 16:21:26 2010
From: vadm at googlecode.com (vadm at googlecode.com)
Date: Mon, 22 Feb 2010 15:21:26 +0000
Subject: [vadm] Issue 5 in vadm: vadm deleted files are not commited to svn
Message-ID: <0-5713915690563136699-9128366571652328359-vadm=googlecode.com@googlecode.com>

Status: Accepted
Owner: wouter.vanden.hove
Labels: Type-Defect Priority-Medium

New issue 5 by wouter.vanden.hove: vadm deleted files are not commited to  
svn
http://code.google.com/p/vadm/issues/detail?id=5

What steps will reproduce the problem?
1. vadm rm /path/to/file
2. do an 'svn stat'  in your ~/.vadm/hostwc-directory
3. vadm commit all
4. files schedules for deleted are not committed to svn:


What is the expected output? What do you see instead?

zopeusr at server: /usr/local/bin > vadm rm autocommit_vadm.sh

zopeusr at server: /home/zopeusr/.vadm/hostwc > svn stat
   D       usr/local/bin/autocommit_vadm.sh

zopeusr at server: /home/zopeusr/.vadm/hostwc > vadm commit / -m  "commit all"
[vadm:warn] nothing to commit at: /


now check again, nothing changed:
zopeusr at porttst1: /home/zopeusr/.vadm/hostwc > svn stat
   D       home/zopeusr/bin/autocommit_vadm.sh
   D       usr/local/bin/autocommit_vadm.sh



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

From vadm at googlecode.com  Mon Feb 22 16:25:30 2010
From: vadm at googlecode.com (vadm at googlecode.com)
Date: Mon, 22 Feb 2010 15:25:30 +0000
Subject: [vadm] Issue 5 in vadm: vadm deleted files are not commited to
	svn
In-Reply-To: <0-5713915690563136699-9128366571652328359-vadm=googlecode.com@googlecode.com>
References: <0-5713915690563136699-9128366571652328359-vadm=googlecode.com@googlecode.com>
Message-ID: <1-5713915690563136699-9128366571652328359-vadm=googlecode.com@googlecode.com>


Comment #1 on issue 5 by wouter.vanden.hove: vadm deleted files are not  
commited to svn
http://code.google.com/p/vadm/issues/detail?id=5

current solution:
in your hostwc-directory you need to do the svn-checking manually:
  > cd ~/.vadm/hostwc
  > svn ci -m 'manual commit'

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings