James, thanks for pointing out this. You are right. Using Py_ssize_t*
instead of int* has indeed fixed the problem. We somehow were misguided
reg. the problem. Thanks once again for taking the time to look into this.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
It's not a bug in GCC. It's a bug in the code. The second call to
PyArg_ParseTuple passes an int* where a Py_ssize_t* should be passed. (The
&data_len argument).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
Thanks for the additional information Fredrik. Your analysis was really
helpful. Could you please raise a new Debian GCC bug? If they fix it,
then we'll have no need to make any changes in calendarserver Debian.
Else we will have to force compilation of the package with gcc 4.6.
--
To UNSUBSC
On 08/13/2012 02:58 PM, Rahul Amaram wrote:
Thanks for the additional information Fredrik. Your analysis was really
helpful. Could you please raise a new Debian GCC bug? If they fix it,
then we'll have no need to make any changes in calendarserver Debian.
Else we will have to force compilation of
Hi,
After further analyzing the problem and with help from Glyph Lefkowitz,
Chris Cleeland and Rahul Amaram, I managed to create a test case that
proved it is a gcc bug.
The included tar file includes a simple testcase that can be run
under Debian.
The c file that is the base for this bugrep
Hi,
while debugging the problem, this patch fixed the problem.
--- calendarserver-3.2+dfsg.orig/twext/python/sendmsg.c
+++ calendarserver-3.2+dfsg/twext/python/sendmsg.c
@@ -238,7 +238,7 @@ static PyObject *sendmsg_sendmsg(PyObjec
}
control_message->cmsg_level = level;
Hello,
first I could also confirm the problem after upgrading for squeeze to
wheezy in AMD64.
The source code must not be changed to resolve the problem.
Inserting
UseMetaFD
in /etc/caldavd/caldavd.plist also helps.
Marko
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debi
I am unable to reproduce this problem on my laptop running 32-bit Debian
Testing. Could this bug that you mentioned be specific to 64 bit OS or
perhaps your environment? Also a similar fix has been mentioned for
another bug as well: http://trac.calendarserver.org/ticket/448 .
I could consider
I have now installed the 32 bit version of Wheezy. Calendarserver
accepts queries on port 8008 with "UseMetaFD" enabled.
This bug seems to only be relevant when running the 64 bit version of Wheezy.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubs
To "solve" this problem, you need to disable (Set it to False) the
feature "UseMetaFD" in the file
/usr/lib/python2.7/dist-packages/twistedcaldav/stdconfig.py
This fix was suggested by Chris Cleeland here
http://old.nabble.com/calendarserver-3.2-on-Debian-unstable-throwing-error-%22socket.error%3A
Package: calendarserver
Version: 3.2+dfsg-1
OS:
Fresh install of wheezy using the image debian-wheezy-DI-a1-amd64-netinst.iso
root@caldavd:/etc/caldavd# uname -a
Linux caldavd 3.2.0-2-amd64 #1 SMP Mon Jun 11 17:24:18 UTC 2012 x86_64 GNU/Linux
Config of /var:
/dev/mapper/caldavd-var on /var type
11 matches
Mail list logo
