X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_BZ X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: bzr completely broken? Date: Wed, 03 Aug 2011 11:02:02 -0400 Lines: 14 Message-ID: References: <4E3893AB DOT 5010609 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes 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 > On 6/6/2011 9:01 AM, Andrew Schulman wrote: > > Am I right that bzr is just completely broken in Cygwin? If so, is there > > an ETA to get it fixed? > > > > My bzr is 2.3.1-1, in Cygwin 1.7.9. No matter what bzr command I run, I > > always get the same result: > > As a quick workaround, you can delete all the dll files in > /usr/lib/python2.6/site-packages/bzrlib. bzr will complain that it can't > find the native modules, but it'll fall back to pure-Python code and > work just fine. You can eliminate the warning by putting > "ignore_missing_extensions=True" in ~/.bazaar/bazaar.conf. Interesting - thanks. The problem was solved otherwise, but that's still useful to know. -- 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