Date: Mon, 20 Jan 2014 21:28:38 +0400
From: Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] launchpad && bzr import failed
Message-ID: <20140120172838.GB9705@localhost.localdomain>
Mail-Followup-To: geda-user AT delorie DOT com
References: <20140120165851 DOT GA9705 AT localhost DOT localdomain>
 <201401201705 DOT s0KH5Z2I011715 AT envy DOT delorie DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <201401201705.s0KH5Z2I011715@envy.delorie.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

On Mon, Jan 20, 2014 at 12:05:35PM -0500, DJ Delorie wrote:
> 
> The commit robot runs on our git server, so shouldn't be affected by
> anything at launchpad.net.
How then launchpad knows if the fix was committed? I thought it was done
automatically during import from git server on geda-project.org. Or
should I manually mark that the fix for the bug is committed?

> I had no idea we had any bzr support, so I have no idea why it
As I understand it, it is a launchpad feature.

> wouldn't be working.  Some of the failures might be due to the DNS
> problems I had after the firewall upgrade.
Yes, it looks as if the problem with the pcb repository appeared recently
while the geda-gaf repository cannot be read since February, 2013.

And to be more clear, when I say 'administrators' I mean the members of
the gEDA Administrators group on launchpad who own those two
repositories on launchpad.