Re: MacCvsX 3.3b2 issue fetching hqx'ed files?

Thanks a lot Jens - I'm pretty sure I can live with running the PowerPC
version of cvsnt - it's mostly the server that's limiting performance
anyway. And good to know that I can gradually start killing the hqx
encoding.

Btw - this issue with missing folder icons on Leopard - if you could give
me a hint about where in the code the icons are generated I'd be glad to
try to help fixing that.

Regards

Carsten


>
> Am 16.04.2008 um 11:29 schrieb Carsten G Pedersen:
> >
> > Would it be a known bug that checking out an hqx'ed binary file
> > leads to
> > this error:
> >
> > cvsnt [checkout aborted]: Internal error: cvs_hqx.cpp, 497: Unknown
> > error:
> > -50
> >
> > V 3.3a2 does not exhibit this problem.
> >
>
> Yes, it's something I recently discovered, too. It's actually a bug in
> the Intel version of the cvsnt tool.
>
> As a workaround until it's fixed, you could make MacCvsX use the
> PowerPC version of the tool:
> - open the MacCvsX application package
> - navigate into Contents/Resources/cvsnt/
> - you'll see two folders there: "ppc" and "intel"
> - rename the "intel" folder to something else
> - create a symlink named "intel" in that directory that points to the
> "ppc" folder
>
> If you don't feel comfortable creating symlinks in Terminal, you can
> also just rename the "intel" folder, duplicate the "ppc" folder and
> rename it to "intel".
>
> I found you only need to do this when checking out files that are hqx
> encoded. Afterwards you can revert back your changes.
>
> Sorry for this inconvenience, but I suspect it'll take a few days
> until I get around to fixing this issue in the cvsnt tool...
>
> > Also - we currently have a number of files in the repository that are
> > hqx'ed simply because until now the client didn't have a general
> > option to
> > not encode binaries. Will changing the option to never encode and then
> > commit a new version of the binary actually work?
> >
>
> Yes, if set the encoding options for this file type (or the default
> option if the file type is not covered by a specific option) to plain
> binary and you force a commit or have actually changed the file, the
> committed file should be plain binary.
> This is per-version, though, so when checking out older versions,
> you'll still get the hqx'ed files.
>
> </jum>
> 

[Non-text portions of this message have been removed]


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/cvsgui/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/