Failure in svn update qooxdoo-contrib

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Failure in svn update qooxdoo-contrib

zaucker
Hi,

there seem to be a problem in
https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib

svn up qooxdoo-contrib/
svn: Can't convert string from 'UTF-8' to native encoding:
svn: qooxdoo-contrib/Bugs/1589/?\195?\182?\195?\164?\195?\188?\206?\169?\206?\169?\195?\159?\195?\134?\195?\184

... and perhaps other files ...

Cheers,
Fritz

--
Oetiker+Partner AG tel: +41 62 775 99 03 (direct)
Fritz Zaucker                        +41 62 775 99 00 (switch board)
Aarweg 15                            +41 79 675 06 30 (mobile)
CH-4600 Olten                   fax: +41 62 775 99 05
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Derrell Lipman
On Thu, Dec 17, 2009 at 15:32, Fritz Zaucker <[hidden email]> wrote:
Hi,

there seem to be a problem in
https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib

svn up qooxdoo-contrib/
svn: Can't convert string from 'UTF-8' to native encoding:
svn: qooxdoo-contrib/Bugs/1589/?\195?\182?\195?\164?\195?\188?\206?\169?\206?\169?\195?\159?\195?\134?\195?\184

I just updated and then applied a few pending commits. I suspect there's something particular to your svn setup in relation to utf-8, but unfortunately I have no idea what that could be.

Derrell


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Thomas Herchenroeder
In reply to this post by zaucker
> Hi,
>
> there seem to be a problem in
> https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib
>
> svn up qooxdoo-contrib/
> svn: Can't convert string from 'UTF-8' to native encoding:
> svn:
> qooxdoo-contrib/Bugs/1589/?\195?\182?\195?\164?\195?\188?\206?\169?\206?\169?\195?\159?\195?\134?\195?\184
>
> ... and perhaps other files ...

I doubt that, unless other commiters are also working with hard-core
unicode path names :). Read the corresponding bug for background info.
While this one is closed, there are already follow-up bugs for
platform-dependent issues (eg. on OSX).

Obviously your svn client has problems bringing this repository path onto
your hard disk. Which platform is that? Do you have a file system that
supports unicode? Why do you want to check out bug data anyway (I would
skip the whole Bugs path if I were you)?

T.


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

fritz
On Fri, 18 Dec 2009, thron7 wrote:

>> Hi,
>>
>> there seem to be a problem in
>> https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib
>>
>> svn up qooxdoo-contrib/
>> svn: Can't convert string from 'UTF-8' to native encoding:
>> svn:
>> qooxdoo-contrib/Bugs/1589/?\195?\182?\195?\164?\195?\188?\206?\169?\206?\169?\195?\159?\195?\134?\195?\184
>>
>> ... and perhaps other files ...
>
> I doubt that, unless other commiters are also working with hard-core
> unicode path names :). Read the corresponding bug for background info.
> While this one is closed, there are already follow-up bugs for
> platform-dependent issues (eg. on OSX).

Ok. I think I saw another Bugs sub directory with a similar message, but
can't reproduce it now.

> Obviously your svn client has problems bringing this repository path onto
> your hard disk. Which platform is that?

Ubuntu karmic

> Do you have a file system that supports unicode?

I have never tried ... so I guess, perhaps not.

> Why do you want to check out bug data anyway (I would skip the whole Bugs
> path if I were you)?

I don't really WANT to, I was just trying to update qooxdoo-contrib (as a
whole) and I guess the Bugs directory must have made it there recently. I
guess I'll go back to checkin out only the contribs I really need/want.

Cheers,
Fritz

--
Oetiker+Partner AG tel: +41 62 775 99 03 (direct)
Fritz Zaucker                        +41 62 775 99 00 (switch board)
Aarweg 15                            +41 79 675 06 30 (mobile)
CH-4600 Olten                   fax: +41 62 775 99 05
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Derrell Lipman
In reply to this post by Thomas Herchenroeder
On Thu, Dec 17, 2009 at 18:09, thron7 <[hidden email]> wrote:

Why do you want to check out bug data anyway (I would
skip the whole Bugs path if I were you)?

No one likely wants the Bugs path, but it's part of qooxdoo-contrib. I believe that it has no business being in qooxdoo-contrib; rather it should be in its own repository all together. Excluding certain elements of qooxdoo-contrib is not something that we want to encourage people to do.

Derrell
 

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

oetiker
In reply to this post by Thomas Herchenroeder
Hi Thomas,

Today thron7 wrote:

> > Hi,
> >
> > there seem to be a problem in
> > https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib
> >
> > svn up qooxdoo-contrib/
> > svn: Can't convert string from 'UTF-8' to native encoding:
> > svn:
> > qooxdoo-contrib/Bugs/1589/?\195?\182?\195?\164?\195?\188?\206?\169?\206?\169?\195?\159?\195?\134?\195?\184
> >
> > ... and perhaps other files ...
>
> I doubt that, unless other commiters are also working with hard-core
> unicode path names :). Read the corresponding bug for background info.
> While this one is closed, there are already follow-up bugs for
> platform-dependent issues (eg. on OSX).
>
> Obviously your svn client has problems bringing this repository path onto
> your hard disk. Which platform is that? Do you have a file system that
> supports unicode? Why do you want to check out bug data anyway (I would
> skip the whole Bugs path if I were you)?

we are (still) using latin1 encoding ... (LANG=enUS) but I agree this is a
subversion issue ... although it is probably not ideal to trigger
it from the contrib tree ...

the way to get the Bugs part is to try and checkout ALL
contributions which is porbably not all that an unreasonable idea
...


cheers
tobi

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch [hidden email] ++41 62 775 9902 / sb: -9900

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Thomas Herchenroeder
In reply to this post by Derrell Lipman


Derrell Lipman wrote:
On Thu, Dec 17, 2009 at 18:09, thron7 <[hidden email]> wrote:

Why do you want to check out bug data anyway (I would
skip the whole Bugs path if I were you)?

No one likely wants the Bugs path, but it's part of qooxdoo-contrib. I believe that it has no business being in qooxdoo-contrib; rather it should be in its own repository all together. Excluding certain elements of qooxdoo-contrib is not something that we want to encourage people to do.

Interesting. I'd put it the other way round: Checking out the entire qooxdoo-contrib is not something I would encourage people to do. It's a collection, and from a collection you pick.

T.


Derrell
 

------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev

_______________________________________________ qooxdoo-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

fritz
On Fri, 18 Dec 2009, thron7 wrote:

> Derrell Lipman wrote:
>> On Thu, Dec 17, 2009 at 18:09, thron7 <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     Why do you want to check out bug data anyway (I would
>>     skip the whole Bugs path if I were you)?
>>
>> No one likely wants the Bugs path, but it's part of qooxdoo-contrib. I
>> believe that it has no business being in qooxdoo-contrib; rather it
>> should be in its own repository all together. Excluding certain elements
>> of qooxdoo-contrib is not something that we want to encourage people to
>> do.
>
> Interesting. I'd put it the other way round: Checking out the entire
> qooxdoo-contrib is not something I would encourage people to do. It's a
> collection, and from a collection you pick.

As I frequently work on the train on my laptop, I did a complete checkout of
qooxdoo-contrib as I might want to try something I hadn't thought about
before.

Of course, a bit more structure below qoxxdoo-contrib would make it more
feasable, e.g.

  qooxdoo-contrib/Bugs
  qooxdoo-contrib/0.7
  qooxdoo-contrib/0.8
  qooxdoo-contrib/1.0

(compatibility is the issue).

If I remember right, there is a Bugzilla enhancement request about that,
already.

Cheers,
Fritz

--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker                        +41 62 775 9900 (switch board)
Aarweg 15                            +41 79 675 0630 (mobile)
CH-4600 Olten                   fax: +41 62 775 9905
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Thomas Herchenroeder


Fritz Zaucker wrote:
On Fri, 18 Dec 2009, thron7 wrote:

  
Derrell Lipman wrote:
    
On Thu, Dec 17, 2009 at 18:09, thron7 <[hidden email] 
[hidden email]> wrote:

    Why do you want to check out bug data anyway (I would
    skip the whole Bugs path if I were you)?

No one likely wants the Bugs path, but it's part of qooxdoo-contrib. I
believe that it has no business being in qooxdoo-contrib; rather it
should be in its own repository all together. Excluding certain elements
of qooxdoo-contrib is not something that we want to encourage people to
do.
      
Interesting. I'd put it the other way round: Checking out the entire
qooxdoo-contrib is not something I would encourage people to do. It's a
collection, and from a collection you pick.
    

As I frequently work on the train on my laptop, I did a complete checkout of
qooxdoo-contrib as I might want to try something I hadn't thought about
before.
  

I stopped doing that when somebody working on Eclipse support for qooxdoo checked in the source code for the enire Eclipse JSDT parser.

T.

  

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

Andreas Ecker
In reply to this post by fritz
Hi Fritz!

On Fri, 2009-12-18 at 10:44 +0100, Fritz Zaucker wrote:

> Of course, a bit more structure below qoxxdoo-contrib would make it more
> feasable, e.g.
>
>   qooxdoo-contrib/Bugs
>   qooxdoo-contrib/0.7
>   qooxdoo-contrib/0.8
>   qooxdoo-contrib/1.0
>
> (compatibility is the issue).
>
> If I remember right, there is a Bugzilla enhancement request about that,
> already.

Hmm, maybe you mixed something up? From a contribution's point-of-view
(and that of its maintainers) IMHO it is still preferable to have an
entire contribution (i.e. including all its versions) physically live in
one folder. What you are absolutely right about, though, is to make the
orthogonal aspect (i.e. framework compatibility) accessible much more
easily from a user's perspective (e.g. through a web interface). This
means it doesn't have to be how the code repository is organized.

This, as well as some other valid points (Bugs area), is something we
started to think over already and plan to figure out (with the
contributors) early next year to further improve the qooxdoo-contrib
infrastructure.

There are parts in qooxdoo-contrib currently to allow for a maximum of
collaboration (like bug fixing) and transparency. Well, that could
benefit from a more radical separation of the concerns, also given that
the contribs themselves are going to flourish and qooxdoo-contrib to
grow, right. ;-)

TTYL,

Andreas

--
Andreas Ecker
Project Lead
http://qooxdoo.org



------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

fritz
Hi Andreas,

On Fri, 18 Dec 2009, Andreas Ecker wrote:

> On Fri, 2009-12-18 at 10:44 +0100, Fritz Zaucker wrote:
>> Of course, a bit more structure below qoxxdoo-contrib would make it more
>> feasable, e.g.
>>
>>   qooxdoo-contrib/Bugs
>>   qooxdoo-contrib/0.7
>>   qooxdoo-contrib/0.8
>>   qooxdoo-contrib/1.0
>>
>> (compatibility is the issue).
>>
>> If I remember right, there is a Bugzilla enhancement request about that,
>> already.
>
> Hmm, maybe you mixed something up? From a contribution's point-of-view
> (and that of its maintainers) IMHO it is still preferable to have an
> entire contribution (i.e. including all its versions) physically live in
> one folder.

Sure, all contribs are below the same folder in the setup I describe above.
Nothing prevents somebody to

   svn co qooxdoo-contrib

(although it's still not clear to me at all why Bugs should live there ...
see Derrell's comment)


> What you are absolutely right about, though, is to make the orthogonal
> aspect (i.e. framework compatibility) accessible much more easily from a
> user's perspective (e.g. through a web interface).

That would certainly be useful ...

> This means it doesn't have to be how the code repository is organized.

... and again, I don't think that there is much benefit in the repository
NOT reflecting this orthogonality. Except that it's not that easy to define
that aspect with contribs that might work with various releases
simultaneously without any changes (how likely this case is you can probably
judget better than I).

> This, as well as some other valid points (Bugs area), is something we
> started to think over already and plan to figure out (with the
> contributors) early next year to further improve the qooxdoo-contrib
> infrastructure.

Cool.

> There are parts in qooxdoo-contrib currently to allow for a maximum of
> collaboration (like bug fixing) and transparency.

Which is great (AND also some danger, but SVN always allows me to go back if
I or somebody else screwed up).

> Well, that could benefit from a more radical separation of the concerns,
> also given that the contribs themselves are going to flourish and

It certainly looks like it ... although I personally think the contrib area
should be as small as possible (and everything "good" should be become a
part of the main line).

> qooxdoo-contrib to grow, right. ;-)

Everything else would surprise me very much (also some of my hopes is
certainly on 1&1 management to continue to support the project at this
level).

Cheers,
Fritz

--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker                        +41 62 775 9900 (switch board)
Aarweg 15                            +41 79 675 0630 (mobile)
CH-4600 Olten                   fax: +41 62 775 9905
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failure in svn update qooxdoo-contrib

fritz
In reply to this post by Thomas Herchenroeder
On Fri, 18 Dec 2009, thron7 wrote:

>> As I frequently work on the train on my laptop, I did a complete checkout
>> of qooxdoo-contrib as I might want to try something I hadn't thought
>> about before.
>
> I stopped doing that when somebody working on Eclipse support for qooxdoo
> checked in the source code for the enire Eclipse JSDT parser.

Cool idea ... ;-)

Cheers,
Fritz

--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker                        +41 62 775 9900 (switch board)
Aarweg 15                            +41 79 675 0630 (mobile)
CH-4600 Olten                   fax: +41 62 775 9905
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel