On Mon, Dec 18, 2006 at 10:50:23AM -0300, Martin Marques wrote:
>
>On Mon, 18 Dec 2006 13:21:06 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>>
>> I haven't uploaded yet; there's another issue with inetd configuration
>> that needs fixing as well I'm afraid. I'm expecting a fix for that
>> ASA
On Mon, 18 Dec 2006 13:21:06 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>
> I haven't uploaded yet; there's another issue with inetd configuration
> that needs fixing as well I'm afraid. I'm expecting a fix for that
> ASAP. Even then, it'll take a couple of days to migrate to testing,
> and
On Mon, Dec 18, 2006 at 10:05:43AM -0300, Martin Marques wrote:
>
>On Fri, 15 Dec 2006 15:57:48 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>> On Fri, Dec 15, 2006 at 02:02:58AM +0100, Julien Cristau wrote:
>
>>>I can confirm that the attached patch fixes this problem for me.
>>
>> Excellent,
On Fri, 15 Dec 2006 15:57:48 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 15, 2006 at 02:02:58AM +0100, Julien Cristau wrote:
>>I can confirm that the attached patch fixes this problem for me.
>
> Excellent, thanks for the help in tracking this down, Julien and
> Samuel! I'll a
On Fri, Dec 15, 2006 at 02:02:58AM +0100, Julien Cristau wrote:
>On Fri, Dec 15, 2006 at 00:59:38 +0100, Samuel Thibault wrote:
>
>> Hi,
>>
>> Looks like the culprit line is update.c:726.
>>
>> unsigned char checksum[16];
>>
>> An unsigned char[16] won't necessarily be aligne
On Fri, Dec 15, 2006 at 00:59:38 +0100, Samuel Thibault wrote:
> Hi,
>
> Looks like the culprit line is update.c:726.
>
> unsigned char checksum[16];
>
> An unsigned char[16] won't necessarily be aligned by gcc. However, it
> is used as a checksum buffer, on which md5_read_
Hi,
Looks like the culprit line is update.c:726.
unsigned char checksum[16];
An unsigned char[16] won't necessarily be aligned by gcc. However, it
is used as a checksum buffer, on which md5_read_ctx() performs 32bit
operations. Hence the SIGBUS on sparc. I guess the best c
On Thu, Dec 14, 2006 at 21:36:51 +0100, Julien Cristau wrote:
> I reproduced this bug (I had seen it a while ago, but never took the
> time to debug it), and got a core dump (without debug symbols).
> Then I installed your packages and reran cvs up to get a useful core
> file, but this time it did
On Thu, 14 Dec 2006 21:36:51 +0100, Julien Cristau <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 12, 2006 at 22:44:21 -0800, Jurij Smakov wrote:
>
>> Hi Martin,
>>
>> Can you please try doing the same debugging trick after installing the
>> cvs package from
>>
>> http://www.wooyd.org/debian/cvs
>>
>>
On Tue, Dec 12, 2006 at 22:44:21 -0800, Jurij Smakov wrote:
> Hi Martin,
>
> Can you please try doing the same debugging trick after installing the
> cvs package from
>
> http://www.wooyd.org/debian/cvs
>
> It contains the non-stripped cvs binary. And type 'backtrace' or 'bt'
> at the gdb pr
Hi Martin,
Can you please try doing the same debugging trick after installing the
cvs package from
http://www.wooyd.org/debian/cvs
It contains the non-stripped cvs binary. And type 'backtrace' or 'bt'
at the gdb prompt after it loads up the core file, and attach the
output to the bug.
Thank
On Tue, 12 Dec 2006 18:00:08 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
> In that case, I'd use a shell script wrapper on the server - install
> it as /usr/bin/cvs, and move the original cvs to cvs.real. The
> following should work for you as a wrapper, I hope:
>
> =
> #
On Tue, Dec 12, 2006 at 02:48:23PM -0300, Martin Marques wrote:
>
>On Tue, 12 Dec 2006 16:19:48 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>> On Tue, Dec 12, 2006 at 01:13:29PM -0300, Martin Marques wrote:
>>>
>>>On Tue, 12 Dec 2006 15:27:42 +, Steve McIntyre <[EMAIL PROTECTED]>
>> wrote:
On Tue, 12 Dec 2006 16:19:48 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 12, 2006 at 01:13:29PM -0300, Martin Marques wrote:
>>
>>On Tue, 12 Dec 2006 15:27:42 +, Steve McIntyre <[EMAIL PROTECTED]>
> wrote:
>
> Check for errors on the server end as well.
What should I look
On Tue, Dec 12, 2006 at 01:13:29PM -0300, Martin Marques wrote:
>
>On Tue, 12 Dec 2006 15:27:42 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>> On Tue, Dec 12, 2006 at 12:09:16PM -0300, Martin Marques wrote:
>>
>> OK. Next question - is it cvs on your local machine or on the server
>> that's d
On Tue, 12 Dec 2006 15:27:42 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 12, 2006 at 12:09:16PM -0300, Martin Marques wrote:
>
> OK. Next question - is it cvs on your local machine or on the server
> that's dying? Can you provoke your client copy of cvs to dump core
> using "ul
On Tue, Dec 12, 2006 at 12:09:16PM -0300, Martin Marques wrote:
>
>On Tue, 12 Dec 2006 14:55:41 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>> On Tue, Dec 12, 2006 at 09:43:19AM -0300, Martin Marques wrote:
>>
>> Hmmm. Signal 10 is SIGBUS, which normally suggests something is badly
>> wrong.
On Tue, Dec 12, 2006 at 09:43:19AM -0300, Martin Marques wrote:
>Package: cvs
>Version: 1:1.12.13-5
>Severity: normal
>
>I have CVS configured to work with ssh as an external autentication
>mecanism. I just passed cvs from stable (sarge) to testing and I'm
>getting this error. When I try to update
On Tue, 12 Dec 2006 14:55:41 +, Steve McIntyre <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 12, 2006 at 09:43:19AM -0300, Martin Marques wrote:
>
> Hmmm. Signal 10 is SIGBUS, which normally suggests something is badly
> wrong. When you say you're using ssh as an authentication method, do
> you me
Package: cvs
Version: 1:1.12.13-5
Severity: normal
I have CVS configured to work with ssh as an external autentication
mecanism. I just passed cvs from stable (sarge) to testing and I'm
getting this error. When I try to update a repository remotly I get this:
$ cvs -q up
? SISTEMA.csv
? javascrip
20 matches
Mail list logo
