Your message dated Sat, 24 May 2025 18:49:57 +0000
with message-id <[email protected]>
and subject line Bug#1106236: Removed package(s) from unstable
has caused the Debian Bug report #805831,
regarding pcb: ExecuteFile function does not update pin labels
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
805831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805831
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pcb
Version: 20140316-3
Severity: normal
Tags: upstream


When transferring a gschem circuit diagram to PCB, one step is to run a 
pre-generated ExecuteFile command from within PCB, on a file containing a list 
of ChangePinName commands.
This is not working. Individual ChangePinName commands work, but a group of 
them within a command file is being ignored.
No entry is generated in the Log Window, even when an incorrect file name is 
used.

After the problem was seen, a simplified PCB file containing one component was 
created, along with a set of three ChangePinName commands in a .cmd file.
The ExecuteFile command was tried with and without quotes around the file name, 
and with both relative and full-path filenames. Nothing worked.
One of the ChangePinName commands was copied from the .cmd file and pasted into 
the PCB command execution window, and this worked correctly.
Trying an invalid command name in the PCB command window does generate a log 
entry of 'no action', suggesting that 'ExecuteFile' is being recognised but not 
executed.
A commented line was removed from the .cmd file, with no change in behaviour.
I have examined the PCB file before and after the attempts, using a text 
editor, to determine whether this is a display problem. The file is not being 
changed.

I have used the PCB package with gschem for several years.
I have always done the ExecuteFile(<pcb-name>.cmd) step in the transfer, but 
have never really paid attention to whether it worked, as I never needed it to. 
Most components are unaffected by it.
I therefore cannot say for sure when this problem arose, but I believe it 
worked seven or eight years ago.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pcb depends on:
ii  pcb-common  20140316-3
ii  pcb-gtk     20140316-3

pcb recommends no packages.

pcb suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1:4.3.0-4+rm

Dear submitter,

as the package pcb has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1106236

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to