Bug#859409: kicad: Inconsistent footprint naming

2017-04-11 Thread Carsten Schoenert
On Fri, Apr 07, 2017 at 01:45:49PM +0200, Carsten Schoenert wrote:

just for completeness ...

> I can somehow upload the packages somethere if you are willing to test.

Some new prepared packages can be found here:
https://pkg-electronics.alioth.debian.org/kicad-4.0.6/

please note the 4.0.6+dfsg2 packages, this is the recent version while
writing.

Regards
Carsten



Bug#859409: kicad: Inconsistent footprint naming

2017-04-07 Thread Carsten Schoenert
Hello MArk,

On Fri, Apr 07, 2017 at 09:51:02AM +, Mark Morgan Lloyd wrote:
> > You can change your local table ~/.config/kicad/fp-lib-table and add the
> > correct names there
> 
> I guess that's not too bad since there's only about 15 names involved.
> 
> > or, if you haven't modified the table much, delete
> > the file. KiCad will copy the default file with the new library names if
> > you restart KiCad.
> 
> Will that work, since the files in the /usr/share/kicad tree are what's
> wrong?

please note the documentation about footprint management in KiCad.

http://docs.kicad-pcb.org/stable/en/cvpcb.html#_footprint_libraries_management

Especially chapter 5.2.3 is showing what is happen if the user specific
configuration (~/.config/kicad/fp-lib-table) is not found.

So you have two options if you can't delete the old file or you are not
willing to do so.

1. Modify the fp-lib-table as shown in the picture in the introducing of
the chapter 5.2.

2. Alternatively you can modify the file directly as it's a simple text
file.

> > In the end I wouldn't wait for a version 4.0.6 in the Stretch release.
> > If the upload to NEW is going well we need to ask the release team if
> > they would allow a upload to unstable and a unblock for migration to
> > testing.
> > 
> > After the release we could then make a upload to backports every time.
> 
> Apologies if I'm speaking out of turn here but I don't think it should be
> released in this state. The problem is not so much how it looks inside
> Debian, but that KiCad itself is pointing to Debian as the definitive
> location of a usable .deb built from their source repository.
> 
> http://kicad-pcb.org/download/debian/

That's not fully correct, they point to the respective place within the
Debian distribution. So KiCad can't be made responsible what Debian is
then providing by the packages.

> I'd suggest that either it should be fixed inside Debian, or that KiCad
> should be asked to temporarily remove that link since what's being shipped
> doesn't correspond to their sources.

Debian is taking what upstream is providing and it's obviously that the
footprint management is work in process in all times.
We can try to work around about such defects by handling the names
consitent over a main version. For this a powerfull testing and feedback
is needed. And basically a bug report upstream about the problem would
also be not the badest.

Also some autopkgtests which detects such things would be good, for the
footprints it should be that difficult as we simply need to check if the
names inside the package pointing to something valid.

As written, I've prepared a new version 4.0.6 but this is depending on
possible going through NEW. Or we drop the new -doc package and ask the
release team if they would accept the new version in the Stretch release
also.

I can somehow upload the packages somethere if you are willing to test.

Regards
Carsten



Bug#859409: kicad: Inconsistent footprint naming

2017-04-07 Thread Mark Morgan Lloyd

You can change your local table ~/.config/kicad/fp-lib-table and add the
correct names there


I guess that's not too bad since there's only about 15 names involved.


or, if you haven't modified the table much, delete
the file. KiCad will copy the default file with the new library names if
you restart KiCad.


Will that work, since the files in the /usr/share/kicad tree are what's 
wrong?



In the end I wouldn't wait for a version 4.0.6 in the Stretch release.
If the upload to NEW is going well we need to ask the release team if
they would allow a upload to unstable and a unblock for migration to
testing.

After the release we could then make a upload to backports every time.


Apologies if I'm speaking out of turn here but I don't think it should 
be released in this state. The problem is not so much how it looks 
inside Debian, but that KiCad itself is pointing to Debian as the 
definitive location of a usable .deb built from their source repository.


http://kicad-pcb.org/download/debian/

I'd suggest that either it should be fixed inside Debian, or that KiCad 
should be asked to temporarily remove that link since what's being 
shipped doesn't correspond to their sources.


--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]



Bug#859409: kicad: Inconsistent footprint naming

2017-04-03 Thread Carsten Schoenert
Hello,

On Mon, Apr 03, 2017 at 11:41:55AM +0100, markMLl wrote:
 
> Apologies if I'm doing something obviously wrong, but this is the first time 
> I've
> picked up Kicad for years and in the past it's "just worked".
> 
> Progressing from eeschema via a netlist file to pcbnew, I get
> 
> Error loading netlist.
> IO_ERROR: Footprint library path '/usr/share/kicad/modules/
> Buttons_Switches_THT.pretty' does not exist
> from /build/kicad-OLDpkC/kicad-4.0.5+dfsg1/pcbnew/
> kicad_plugin.cpp : Load(): line 283
> 
> The problem would appear to be that there are directories named like
> 
> Buttons_Switches_ThroughHole.pretty
> Capacitors_ThroughHole.pretty
> 
> and so on, while the files femplate/fp-lib-table.for-pretty and
> template/fp-lib-table.for-github have
> 
> (lib (name Buttons_Switches_THT)(type KiCad)(uri 
> ${KISYSMOD}/Buttons_Switches_THT.pretty)(options "")(descr "Buttons and 
> switches, through hole"))
> 
> and so on.

unfortunately upstream has renamed some footprint libraries and also moved
some footprint entries into other libaries that we wasn't aware while
packaging 4.0.5.

I prepared 4.0.6 some days ago which should solve this issue by
symlinking the old libraries to the new ones. But the new package
version needs to go through NEW as it contains a new binary package.

You can change your local table ~/.config/kicad/fp-lib-table and add the
correct names there or, if you haven't modified the table much, delete
the file. KiCad will copy the default file with the new library names if
you restart KiCad.

In the end I wouldn't wait for a version 4.0.6 in the Stretch release.
If the upload to NEW is going well we need to ask the release team if
they would allow a upload to unstable and a unblock for migration to
testing.

After the release we could then make a upload to backports every time.

Regards
Carsten



Bug#859409: kicad: Inconsistent footprint naming

2017-04-03 Thread markMLl
Package: kicad
Version: 4.0.5+dfsg1-4
Severity: normal

Dear Maintainer,

Apologies if I'm doing something obviously wrong, but this is the first time 
I've
picked up Kicad for years and in the past it's "just worked".

Progressing from eeschema via a netlist file to pcbnew, I get

Error loading netlist.
IO_ERROR: Footprint library path '/usr/share/kicad/modules/
Buttons_Switches_THT.pretty' does not exist
from /build/kicad-OLDpkC/kicad-4.0.5+dfsg1/pcbnew/
kicad_plugin.cpp : Load(): line 283

The problem would appear to be that there are directories named like

Buttons_Switches_ThroughHole.pretty
Capacitors_ThroughHole.pretty

and so on, while the files femplate/fp-lib-table.for-pretty and
template/fp-lib-table.for-github have

(lib (name Buttons_Switches_THT)(type KiCad)(uri 
${KISYSMOD}/Buttons_Switches_THT.pretty)(options "")(descr "Buttons and 
switches, through hole"))

and so on.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/1 CPU core)
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 kicad depends on:
ii  kicad-common4.0.5+dfsg1-4
ii  libboost-atomic1.62.0   1.62.0+dfsg-4
ii  libboost-chrono1.62.0   1.62.0+dfsg-4
ii  libboost-context1.62.0  1.62.0+dfsg-4
ii  libboost-date-time1.62.01.62.0+dfsg-4
ii  libboost-filesystem1.62.0   1.62.0+dfsg-4
ii  libboost-iostreams1.62.01.62.0+dfsg-4
ii  libboost-locale1.62.0   1.62.0+dfsg-4
ii  libboost-program-options1.62.0  1.62.0+dfsg-4
ii  libboost-regex1.62.01.62.0+dfsg-4
ii  libboost-system1.62.0   1.62.0+dfsg-4
ii  libboost-thread1.62.0   1.62.0+dfsg-4
ii  libc6   2.24-9
ii  libcairo2   1.14.8-1
ii  libcurl3-gnutls 7.52.1-3
ii  libgcc1 1:6.3.0-11
ii  libgl1-mesa-glx [libgl1]13.0.6-1
ii  libglew2.0  2.0.0-3+b1
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgomp16.3.0-11
ii  libpython2.72.7.13-2
ii  libstdc++6  6.3.0-11
ii  libwxbase3.0-0v53.0.2+dfsg-3
ii  libwxgtk3.0-0v5 3.0.2+dfsg-3
ii  python  2.7.13-2
ii  python-wxgtk3.0 3.0.2.0+dfsg-3+b1
pn  python:any  

Versions of packages kicad recommends:
ii  xsltproc  1.1.29-2.1

Versions of packages kicad suggests:
pn  extra-xdg-menus  
pn  kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d  

-- no debconf information