DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BVDKwx62796081 Authentication-Results: delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=delorie.com X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BVDKwGM2796063 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=linetec.nl Authentication-Results: delorie.com; spf=pass smtp.mailfrom=linetec.nl DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4BVDKwGM2796063 X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: Debian amavisd-new at mail.linetec.nl Content-Type: multipart/alternative; boundary="------------5zYhcI90QNTx5Vk0bicy3Jgu" Message-ID: Date: Tue, 31 Dec 2024 14:20:51 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [geda-user] System reinstall, how to restore gschem - pcb import again? From: "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com References: <08a6ccd6-2543-4d41-a34f-42495341db50 AT linetec DOT nl> <63a5b652-92d5-43c1-8242-b87257364edc AT linetec DOT nl> Content-Language: en-GB, nl In-Reply-To: <63a5b652-92d5-43c1-8242-b87257364edc@linetec.nl> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This is a multi-part message in MIME format. --------------5zYhcI90QNTx5Vk0bicy3Jgu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit OK, simply renaming symlinks doesn't work -- which is not completely unexpected. I think I'll have to dig deeper into lepton and see if I can find any information about how to make it play nice with pcb. Op 31-12-2024 om 13:03 schreef Richard Rasker: > > I did some more digging, and I noticed that gnet-pcbfwd.scm contains > references to gnetlist. On the crashed system, gnetlist was installed > in /usr/local/bin, together with a lot of other gEDA stuff: > > ~/root_backup/usr/local/bin$ ls > *gafgarchivegattribgnetlistgnetlist-legacygrenumgsch2pcbgschemgschlasgsymcheckgsymfixgxyrsMerge_dimPCBPSMergePCBPSpcbpcb_backannotaterefdes_renumschdifftragesymxorn > * > > In the new installation, I located many of these files in /usr/bin, > now with a 'lepton-' prefix: > > $ cd /usr/bin > $ ls lepton* > lepton-archivelepton-clilepton-embedlepton-netlistlepton-refdes_renumlepton-schdifflepton-shelllepton-symfixlepton-upcfg > lepton-attriblepton-configlepton-exportlepton-pcb_backannotatelepton-sch2pcblepton-schematiclepton-symchecklepton-tragesymlepton-update > > Now if these differently named files are indeed the problem, the > question is how I can fix this in the cleanest way possible. > > I'm tempted to create symlinks with the 'old' names (in most cases > simply replacing 'lepton-' with 'g'), but that feels rather messy, and > it may also fail when these newer scripts are not compatible with > calls from this slightly older pcb version. Would perhaps a newer pcb > version find these lepton files automatically? Then I think the best > way forward is to build it from source. > > Anyway, I think I'll try the renamed symlinks first, as they can be > easily removed again, and then see what I can find wrt. pcb versions. > > Regards, > > Richard > > > Op 30-12-2024 om 19:47 schreef Richard Rasker: >> Op 30-12-2024 om 18:37 schreef DJ Delorie (dj AT delorie DOT com) [via >> geda-user AT delorie DOT com]: >>> You need to find the gnet-pcbfwd.scm from the pcb package (wherever it's >>> installed) and at least symlink it from the share/gEDA/scheme/ directory >>> where lepton put all its gnet-*.scm files >> >> OK: >> >> $ locate gnet-pcbfwd.scm >> /usr/share/gEDA/scheme/gnet-pcbfwd.scm >> >> $ locate gnet- | grep lepton >> /usr/share/lepton-eda/scheme/backend/gnet-PCB.scm >> [...] >> /usr/share/lepton-eda/scheme/backend/gnet-vipec.scm >> >> $ cd /usr/share/lepton-eda/scheme/backend/ >> $ sudo ln -s /usr/share/gEDA/scheme/gnet-pcbfwd.scm >> >> But alas, no go, same error as before (Could not open action file >> "/tmp/pcb.XXRMf2PY/gnetlist_output"). >> >> As expected, physically copying the file to /usr/gEDA/share also does >> not make a difference. >> >> FWIW, version information, pcb: >> >> This is PCB, an interactive printed circuit board editor >> version 4.2.2 >> Compiled on Aug 17 2021 at 02:34:03 >> by harry eaton >> >> Lepton: >> >> Lepton-schematic 1.9.18 (git: d24967d) >> >> Is there any other information that might be helpful? >> >> Anyway, thank you for the quick reply - and I hope that a solution >> can be found, because this functionality is rather important to me >> ... If needed, I can of course also build pcb and an older gschem >> version, but that's quite a hassle too because of all the >> dependencies and development packages that need to be installed. >> >> Thanks again, >> >> Richard >> > Met vriendelijke groeten, > > Richard Rasker > -- > Linetec > Akkerstafhof 15 > 7544SP Enschede > 053-4350834 > http://www.linetec.nl/ Met vriendelijke groeten, Richard Rasker -- Linetec Akkerstafhof 15 7544SP Enschede 053-4350834 http://www.linetec.nl/ --------------5zYhcI90QNTx5Vk0bicy3Jgu Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

OK, simply renaming symlinks doesn't work -- which is not completely unexpected.

I think I'll have to dig deeper into lepton and see if I can find any information about how to make it play nice with pcb.


Op 31-12-2024 om 13:03 schreef Richard Rasker:

I did some more digging, and I noticed that gnet-pcbfwd.scm contains references to gnetlist. On the crashed system, gnetlist was installed in /usr/local/bin, together with a lot of other gEDA stuff:

~/root_backup/usr/local/bin$ ls
gaf  garchive  gattrib  gnetlist  gnetlist-legacy  grenum  gsch2pcb  gschem  gschlas  gsymcheck  gsymfix  gxyrs  Merge_dimPCBPS  MergePCBPS  pcb  pcb_backannotate  refdes_renum  schdiff  tragesym  xorn

In the new installation, I located many of these files in /usr/bin, now with a 'lepton-' prefix:

$ cd /usr/bin
$ ls lepton*
lepton-archive  lepton-cli     lepton-embed   lepton-netlist           lepton-refdes_renum  lepton-schdiff    lepton-shell     lepton-symfix    lepton-upcfg
lepton-attrib   lepton-config  lepton-export  lepton-pcb_backannotate  lepton-sch2pcb       lepton-schematic  lepton-symcheck  lepton-tragesym  lepton-update

Now if these differently named files are indeed the problem, the question is how I can fix this in the cleanest way possible.

I'm tempted to create symlinks with the 'old' names (in most cases simply replacing 'lepton-' with 'g'), but that feels rather messy, and it may also fail when these newer scripts are not compatible with calls from this slightly older pcb version. Would perhaps a newer pcb version find these lepton files automatically? Then I think the best way forward is to build it from source.

Anyway, I think I'll try the renamed symlinks first, as they can be easily removed again, and then see what I can find wrt. pcb versions.

Regards,

Richard


Op 30-12-2024 om 19:47 schreef Richard Rasker:
Op 30-12-2024 om 18:37 schreef DJ Delorie (dj AT delorie DOT com) [via geda-user AT delorie DOT com]:
You need to find the gnet-pcbfwd.scm from the pcb package (wherever it's
installed) and at least symlink it from the share/gEDA/scheme/ directory
where lepton put all its gnet-*.scm files

OK:

$ locate gnet-pcbfwd.scm
/usr/share/gEDA/scheme/gnet-pcbfwd.scm

$ locate gnet- | grep lepton
/usr/share/lepton-eda/scheme/backend/gnet-PCB.scm
[...]
/usr/share/lepton-eda/scheme/backend/gnet-vipec.scm

$ cd /usr/share/lepton-eda/scheme/backend/
$ sudo ln -s /usr/share/gEDA/scheme/gnet-pcbfwd.scm

But alas, no go, same error as before (Could not open action file "/tmp/pcb.XXRMf2PY/gnetlist_output").

As expected, physically copying the file to /usr/gEDA/share also does not make a difference.

FWIW, version information, pcb:

This is PCB, an interactive printed circuit board editor
version 4.2.2
Compiled on Aug 17 2021 at 02:34:03
by harry eaton

Lepton:

Lepton-schematic 1.9.18 (git: d24967d)

Is there any other information that might be helpful?

Anyway, thank you for the quick reply - and I hope that a solution can be found, because this functionality is rather important to me ... If needed, I can of course also build pcb and an older gschem version, but that's quite a hassle too because of all the dependencies and development packages that need to be installed.

Thanks again,

Richard

Met vriendelijke groeten,

Richard Rasker
-- 
Linetec
Akkerstafhof 15
7544SP  Enschede
053-4350834
http://www.linetec.nl/
Met vriendelijke groeten,

Richard Rasker
-- 
Linetec
Akkerstafhof 15
7544SP  Enschede
053-4350834
http://www.linetec.nl/
--------------5zYhcI90QNTx5Vk0bicy3Jgu--