X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Message-ID: <4C1FD3E8.50308@acm.org> Date: Mon, 21 Jun 2010 14:04:40 -0700 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: cygwin Subject: Need swig 1.3.40 for Subversion Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com It seems that swig-1.3.38 has a bug that produces invalid Python bindings with Python 2.6. I first hit this when building subversion-1.6.11-2 for Python 2.6, but I dismissed the test case failures at the time. Today I built subversion-1.6.12-1 and took the time to investigate. The Python bindings won't run when generated with swig 1.3.38 but run fine when generated with 1.3.40. Therefore, I respectively request that the swig maintainer update swig to 1.3.40. (I believe swig 2.0.0 was just release, but I have no idea if Subversion will build with that version.) For now, I'll release subversion-1.6.12-1 with the bindings generated with 1.3.40. Others won't be able to rebuild from source until 1.3.40 is released (unless they manually build 1.3.40 as I did). -- David Rothenberger ---- daveroth AT acm DOT org Price's Advice: It's all a game -- play it to have fun. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple