Regardings Python and wx: I killed the check for ancient Python versions several weeks ago and have always built against Python 3 and the corresponding versions of wx.
Thatâs true, but this thread is about Debian builds. And problems regarding my builds MUST NOT be reported to the Ubuntu packaging issue tracker as they can not do anything about it.
Yes, of course. I wrote the things in my post because it was mentioned in this thread that
If this has actually been solved or was not a problem, then OK. Now, when I read it again, itâs possible that it doesnât speak about your repository at all, but it wasnât clear.
And jsreynaud was mentioned as the Ubuntu ppa maintainer, while the packaging repo and team was changed to âkicadâ instead of âjsreynaudâ some time ago. The situation was confusing because js is still part of the new team but he has still some legacy repo bearing his name. Just to be clear, the current nightly build repo is https://launchpad.net/~kicad/+archive/ubuntu/kicad-dev-nightly, if anyone â not you â tries to search for kicad repos and finds a wrong one.
You also said you donât have an idea how to report to the ppa maintainer, so I gave the link to the kicad packaging gitlab page which actually has the issue database. (I wonder why you earlier said âyou donât have an ideaâ because you yourself link to the relevant gitlab page.)
In any case, if your package works with python3 and wxPhoenix I can try to use them as the base of dependency detection for my build on Debian.
One last question. How âstableâ you think your repository will be? I mean, often such projects go silent after some time, and I would like to write build instructions which will not get old soon. So I wonder if I can just link to your repository in the instructions and expect that the repo will stay more or less up to date for example a couple of years.
I donât personally use Debian (altough I did years ago), but thank you very much for the repository.
I have to admin I didnât check the included scripts yet. I could flip the shebang line to use python3 but this alone might not make them work again. This should also be adressed upstream (along with finally dropping any python 2 support).
Back then, I was not aware of that repo and, more importantly, the dailybuild branch therein.
The repo will stay at least until v6 is released. But I see no immediate reason to turn it off even after that.
The supported Debian releases will change, though. For example, once bullseye is released, I will continue to build for buster only as long as it doesnât produce additional work. Building a development snapshot for an oldstable release makes very little sense anyway.
Indeed. As for my build instructions, I wouldnât try to get them working on old distros unless it just happens to work. Getting them to work on testing/bullseye would be fine. But I want them to be valid for the KiCad master branch after v6 (pre-v7). The instructions themselves try to be so generic that they work even if KiCad or the distro changes, but they always require packages which make it possible to install the required dependencies. The packages donât even have to be up to date, as long as the dependencies are the same as with the git master branch of the kicad source.
To make bisecting regression bugs easier, I added snapshots to my repository.
They can be accessed using APT as follows:
deb https://debian.sur5r.net/kicad-nightly buster/snapshots/TIMESTAMP main
deb https://debian.sur5r.net/kicad-nightly bullseye/snapshots/TIMESTAMP main
The timestamps correspond to the UTC timestamp of the git commit being built, just as the first part of the package version number.
My current goal is to provide around 2 weeks of snapshots. I will see how that works out and will post here if anything changes.
Please note that I currently do not build all commits but only the latest. So if there are multiple commits while a build is running, all but the last of them will be skipped.
Also, I just changed the workings of my automation to build each commit.
While 6.0 was released, my builds are (of course) still following the master branch.
If some is wondering why there has been no new build for close 3 days, hereâs why:
Part of the package build process is running the test suite shipped with kicad, which started failing about 3 days ago. It seems the test suite is not updated the same way the development is going forward.
As I donât want to waste CPU cycles on compiling packages that get thrown away immediately, Iâve disabled the test suite until further notice.
Feel free to inspect the build logs if youâre interested in which tests fail in detail.