X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-disposition:content-transfer-encoding
         :in-reply-to:user-agent;
        bh=IvjSPvoRXMzWTCTRe4eNnVz98R16c23c4/sjxJxJgZI=;
        b=ZQA6meLEVMlIvoxdHUANbUCvQRWObnDHeVLPxBGPBGEXeXvKYvouhL4GhAEZdvcBYQ
         7kvmpAqsOQCsob9OYAcJl7hpqERpUEbQKbb6+ZfdJEy0z/2fK5VdSJgBAqrN0F7bnTo5
         kMRCx/yHD7Ut6EJ6UcoMBu7l9PB+h+FyJ89/7uvT6Yba44IEcC8kEuNJj8dA/K0q31qz
         P//A++AEh+ruViEnkorcOrifCgNxL7SdfpjXs/ofboYBFnkDWm2N/0ETrTX1AziUR7/F
         EZ0TrGzuRF4j40TfdnkL056Nqsh0pVmMZMKvCjiHntzEJ4JwIqNTkELAqZPl42/9D/i+
         p40A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to
         :references:mime-version:content-disposition
         :content-transfer-encoding:in-reply-to:user-agent;
        bh=IvjSPvoRXMzWTCTRe4eNnVz98R16c23c4/sjxJxJgZI=;
        b=TotNXme/xVAw4kafYam3GLORiqNdB+imHb4Au8/Rnn/EY/zapmShO4QdOeAryw1xXJ
         lF+aXhXa3NUuZtmfHeryb9KHjNbBUv4Ik7cc2bPLo/G1GHeKth7dpDr7CqA8QohdPOpj
         Y3EeiJVtlqCNV2J42+MQV1S2KKEjaKN8nbYJRnVPi2GbbpVsNX/ftK3epgxAtDmAqHEY
         HUhhPveRfA5ib1MuFWDFTQy4xtoHS4Xu+rnV07w8XhBjiLbZ5oMoaoDjEWfpygBIomB6
         DawS/jxrP901r0p776cyDQBoPv4Hi0l6STAND7rGBWUZTwurMHDujRUjzObN0bGNiSS/
         AD1Q==
X-Gm-Message-State: AMke39kDvcP01nr2+pEGqOLffjrB6udx2fNG7E02uT3AmXYVunIVR33FSMyIixX760vTbQ==
X-Received: by 10.25.166.131 with SMTP id p125mr3280078lfe.142.1487440954957;
        Sat, 18 Feb 2017 10:02:34 -0800 (PST)
Date: Sat, 18 Feb 2017 21:02:32 +0300
From: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
To: geda-help AT delorie DOT com
Subject: Re: [geda-help] Please help with multiple-pages schematics
Message-ID: <20170218180232.GB23464@localhost.localdomain>
Mail-Followup-To: geda-help AT delorie DOT com
References: <CAEoZ9Hi01S7_QOETXLyBF1fOPeFUT_34YRiooJbbFSrDV956NQ AT mail DOT gmail DOT com>
 <FE10A69B-DB86-4182-A223-25AEE5FF697E AT noqsi DOT com>
 <CAEoZ9HgxR8qm9vfr6TUHgxPTeOGZ=a7Mc8NrwmPvJOLyXHa5fg AT mail DOT gmail DOT com>
 <CAJXU7q8-XPJ+9k3C4bVWvYe5ci1eFGrnNfeCBQoykhdWAM9s0g AT mail DOT gmail DOT com>
 <11BDEC14-5D1D-4157-B552-582C1E75D00E AT noqsi DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <11BDEC14-5D1D-4157-B552-582C1E75D00E@noqsi.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Sat, Feb 18, 2017 at 10:39:06AM -0700, John Doty wrote:
> 
> On Feb 18, 2017, at 3:41 AM, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
> 
> > 
> > On 18 February 2017 at 08:27, Vasily Olekhov (olekhov AT gmail DOT com) [via geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
> > Thank you John, I've got your point.
> > Can you hint how should I reference CONN1 on the second page?
> > It should be the same component CONN1 from the first page.
> > 
> > This is a slightly unusual way of doing things. I _thought_ it should work, but having checked, it is actually generating a bad netlist.
> > 
> > My Windows dual-boot has gEDA 1.6.1..... so this could be some bug which is fixed since then. What version do you use?
> > 
> 
> This is a very old bug. I suppose it’s rarely encountered: most of us don’t try to do things that way. It’s still present in lepton pulled from git yesterday.

Yes, this is
1) a misguiding abuse of components in schematics
2) a bug in gnetlist consisting in having no check of package
consistency wrt the number of its pins and conflicting pinnumbers
(and pinseqs IIUC).

-- 
  Vladimir