Hi Georges and everyone else.

I'm sorry that I left the discussion, I didn't see that it was moved to a
different bug report (which I wasn't subscribed to). Sorry.

> Also, where are your latest scripts located? Someone linked
> https://github.com/onitake/kicad.debian at one time on the list, but
> is that you?

That's my repo, and I just patched in the pull request from Bas.
But I guess it's kind of redundant now that you finished packaging rc1, but it
may still be good to cross-check, in case you missed something.

> It is uninstallable in Jessie and even in Stretch, due to the GCC-5
> transition.

I'm a bit confused there. How is gcc-5 affecting uninstallation?

Or, are you referring to the misplaced plugins in /usr/bin?

> I could build a backport for Jessie, and this one works too; I shall
> launch a new build for it shortly (some packaging bugs have been fixed
> since I tried the first backport).
> 
> The new release cannot be published immediately, because the new source
> package builds new binary packages, like kicad-doc-nl, so somebody from
> ftpmasters will have to bless the new revision.

Nice!

> I had to remove the Github plugin from the build process, because this
> plugins needed to compile a binary which is linked to GPLed libraries
> and to OpenSSL at the same time, which triggers a fata Lintian error
> about license incompatibility. However as the package kicad-common
> provides all the know pretty libraies, and as the default template
> declares those libraries, there is no immediate drawback.

This is a bit of sad news, really, as the github plugin is very useful to
quickly pull in external part libraries. Also makes it easy to share your
footprints with others.

Maybe a modification to use gnutls instead is possible?
I'll post a request to Launchpad, if that makes sense to you.

Georges, did you post your build scripts somewhere public so I can do a local
test build and cross-examine?

Reply via email to