Nightly build size dropped


The 24th December Nightly is much smaller than recent builds.
Either it has stopped including the 3D models or it is not what it claims to be.
As it is unsigned I am wary of downloading to try it.
Anybody know anything?


Ubuntu version 24th December is 6MB heavier than that of September. Linux versions don’t include libraries.


Ubuntu does not include libs. Other distros do. (Example fedora.)


This is the Windows 32 & 64 bit versions. The size has crashed from 800MB plus to 100MB overnight


There is no libraries at all in recent installer(s). I can’t tell if installer will download and install them from GitHub repos. IMO many of nightlies users has already installed full set of libraries, so it’s not necessary to include them every time in this type of installer.
BTW. The NSIS has a weak compression agorithm. That’s why the full installers were such bigger. Using for example INNO Setup, I can create full installer which has only ~300MB (using ultra and solid compression options).

The Virus Total doesn’t report any significant issues.


Stop writing that. All versions on the official KiCad download page are signed. Uploads to that site cannot be performed by the build server without a valid certificate. (An expired certificate was the reason that there were no Windows Nightly updates for a while in November/early December.)

BTW. finally FreeCad is listed as the recommended 3D modeler for KiCad at the end of the install; that is about time! The drop in file size is very much welcome.


It is the Nightlies that I am referring to

At the top of the directory README.txt says “As we don’t have a valid code signing certificate at the moment, downloads are unsigned, and we cannot guarantee their integrity.”
Oddly the README.txt is dated 31st December 2017.

Further, Windows 10 complains that the installer file is not signed

I fetched the 24th December build and found that it is a very “bare bones” installer, with no symbols, footprints, models or help, but is authentic


Oops, I did not notice that message; I was referring to the discussion on the mailing list that explained why the nightly was not uploaded to the official site for a while. So if the information in README.txt is correct and not old and outdated (no way to tell what the original date really was), I stand corrected. (Win7 has not complained other than the standard confirmation screen, but my certificate store might be slightly out of date too.)

Edit: On the build server there is a certificate. Downloading and inspecting reveals that it is valid until 2030-12-31, so this is confusing. Perhaps we could get a clarification from those managing the build server.

Also in the log:
#128 (Dec 15, 2017 5:41:00 PM)
Add p11-kit before reinstalling ca-certificates — oe.nick / githubweb
Fix typos in readme — oe.nick / githubweb
Add missing dll for adb — oe.nick / githubweb


Situation seems complicated. An update here:
There is mention about “sign nightlies manually until a better solution pops up”, but unclear if this is currently in effect.


Wow! I’ve been waiting for this!


It’s fine with me so long as there is another way to get those missing help files and libraries occasionally. Once the old large files age out of the directory, I am not sure that there is.


Where exactly do you see that certificate? Is that from stuff downloaded from or the certificate for the server itself?

The current windows nightlies are not signed anymore because:


I have been experimenting with preparing to be able to provide both a full and a lite installer. I am not sure if we should just do a lite installer with only kicad and a seperate for libs and help files.

One of the goals with the lite installer is to make it easer for people to quickly download the nightly to test stuff.

I did not have time to decide on the final solution so I just pushed changes to effectively make the lite build, such that it can be tested.


It is my opinion that the biggest issue is keeping the 3D models out of the nightly builds.

However, I do like the idea of a “lite” installation. Any user tinkering with the nightlies should have their own libraries and help file information already downloaded locally on their machine.

I’d suggest keeping it as lite as possible, and be prepared to go back to normal if a legitimate complaint is found.


@nickoe, I found it on the windows build server which differs from the official download site. I also referenced that link you provided in a following message. It is not clear if manual signing is in effect, but it does not sound like it from that message.


Please point me directly to that certificate. I do not recognize it.



The certificate start and expiry dates look very suspect, a 20 year lifetime!


Also self-signed with a weird name, doesn’t look legit!


This is OK. This is the normal ca cert bundle. This is used for the github plugin to be able to download via https.

That ACCVRAIZ is some Spanish certificate authority as far as I know. You can also find that exact certificate in your normal windows certificate manager. Open certmgr.msc and look in Trusted root certification authorities, then certificates.

The ACCVRAIZ1 is not the only certificate in ca-bundle.crt, there are many root certificates in there. I don’t know why the windows certificate showing thing is only showing the one certificate. There are many. Open the file in a text editor to see for yourself. This is expected.

That ca-bundle.crt is not used for signing the windows builds, so this is unrelated.