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

[Karsten]

Hello Carsten,

Am 29.11.20 um 07:17 schrieb Carsten Schoenert:
> 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.

O.K.

>> 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.

Not for all of us under every circumstances.

>> 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.

But you can see the reported bugs.
You can define them as nonsense, but that will not fix the problem.

> 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?

This all makes no difference when you say it is running for you and there is no bug.

>> 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.

The standard answer from developers is: "Have you tried the actual version".
There is no support of bugs in older versions as used in an stable distribution.
This point of view is understandable, but does not help the user.

>
>> 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 mean 5.1.8+dfsg1-1~bpo10+1 from the backports.
We will see what will happen in later releases.

>
> 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.

Yes - thank you for your support so far!

>  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.

That's understandable.

Besides Debian 10 is running less stable than Debian 8.
There are many detail issues, but Debian 8 is not supported any more ...
An upgrade to testing did fail too - maybe it is possible now.

> 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.

Yes - but first i didn't remember to look at the backports.
It seems new that the pinning does not automatically update to a newer version when it exists.
So it must be done manual for every main package.

Best regards
karsten