[Pkg-electronics-devel] Bug#913864: KiCad is not usable, because cvpcb is not working

[Carsten Schoenert]

Control: notfound -1 5.0.1+dfsg1-3
Control: tags -1 - wontfix
Control: notfound 913864 5.0.2+dfsg1-1

Hello Karsten,

next time please start a new bug report. Now there is a cloned old
report there the old history is completely indpendent from your issue.
This makes it not easier to follow the red line.

Am Sun, Nov 29, 2020 at 02:49:38AM +0100 schrieb Karsten:
 
> i am talking about the features behind the button "Assign PCB
> footprints to schematic symbols" (see screenshot).

It's obvious to me what you are talking about. I know what CvPcb is
doing.

> How this simple part of KiCad cannot be used as intended?
> Using the wrong hand for the mouse? :-)

Simple things can be difficult if you don't know what the right is thing
to do is clear to you.

You say "It doesn't work", I've tested CvPcb from 5.0.2 with some of my
projects and I don't see a problem, I can assign footprints what ever I
like to assign. I can set the filtering from no filtering to the most
strict filterung which is the only thing that has impact to the visible
list with the footprints on the right.

I have no idea what the point is where you assume CvPcb is broken. How
can I readjust your situation? What your are doing (and what not).
What other package you might have installed from backports or third
party repositories which might have a bad interact with kicad from
stable? But I don't think this is happen in any way.
Any third party plugin installed which might have impact on your side?

> Fact is that this part of KiCad seems to be very buggy.

I disagree. I don't know any upstream bug report about CvPcb or from the
KiCad forum from about the last two years.
And I don't know some Git related history about bug fixing in this area
within the 5.1 cycle.

> I did not open a new bug report for it, because i thought the problems
> of the described problem are to similar.
> One time this part crashed, but this was really not reproducible.

If you think your issue is related to the original report why don't you
have written about this in first place? The other report has a lot of
information how the library symbol clashing can be found and which
library/symbol is the right combination. Have you really tried out these
steps at your own?

> It's fine that it is running stable on your system.
> But this is no explanation that it must be stable everywhere.
> On the other hand i think that you can't do anything to solve this bugs.

If your issue is really a upstream issue than it needs to be reported
to the upstream developers. The KiCad team is really responsive and quick
to fix such things once they have understand what problem is responsible
for the visible behavior.

> We must wait until this bugs are solved in newer versions of Kicad.
> Version 5.1.8 seems to be on the way ...

You mean 5.1.9 for sure.

I believe this report will start bit rotting, searching a possible issue
in this rather old version is exhausting and mostly useless in my eyes
as the current supported version is 5.1.8. Te current rules of the
release team makes it hard to update the version of kicad in stable due
rather big source code changes that are not related to the baisc rules
for updates of packages in stable.
I don't have really time to jump into work which nobody will use and
honor somehow in the end.

You have found a newer version in backport where you don't have problems
with. And the backports archive is exactly the use case for newer
versions with newer and improved features like KiCad upstream does within
their release for the stable cycle.

Regards
Carsten