I’ve upgraded from running nightly builds last year, to the newly release 6.0. I’m using the Ubuntu package and it reports 6.0.0-rc1 build date 19/11/2021
But I now can’t open any schematics with version tag 20211123 - they have some changed structure. Can I somehow downgrade the file, or will the 6.0 release version allow me to open those schematics?
19/11/21 is older than your 20211123, so no surprise that there is a complaint.
Release was on the 25th December, so a month more recent than either
When v6 was released on 12/24, nightly builds ticked over from v5.99 (pre-v6) to v6.99 (pre-v7) and the nightly file format changed shortly thereafter when some new v7 features were merged into the nightlies.
Were you running a nightly from after 12/24? If so that makes sense – the nightly file format was newer than the v6 file format.
I can’t quite understand from your message what you’re considering “nightly” and “release 6.0” and which dates/versions apply to which.
I have the same problem with Kubuntu. I installed the nightly 6.0.0-rc1, then I installed stable 6.0.0.
And stable 6.0.0 cannot open 6.0.0-rc1 schematics.The message says 6.0.0 is older.
I didn’t use any nightly with a version of 6.99 or later than mid-December, but it seems that the release build file format was forked before then, the -rc1 that is now in the stable repository can’t open those files.
I don’t understand this, there shouldn’t be a rc1 in stable anymore, rc1 is old at this point.
The Ubuntu PPA seems to have only 6.0.0-1, not an RC1 version.
The exact version which I got from the PPA Ubuntu repository is:
Application: KiCad
Version: 6.0.0-rc1-bf2b03b42f~115~ubuntu18.04.1, release build
Libraries:
wxWidgets 3.0.4
libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-166-generic x86_64, 64 bit, Little endian, wxGTK, KDE, x11
Build Info:
Date: Nov 19 2021 15:42:34
wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
Boost: 1.65.1
OCC: 7.5.2
Curl: 7.58.0
ngspice: unknown
Compiler: GCC 7.5.0 with C++ ABI 1011
Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ONDoes it show as upgradeable by apt? Since that is older than what is currently published, it seems like it should offer to update you to the stable 6.0.0-1
Version 6.0.0-1 came from 5.1.12
and 6.0.0-rc1 came from 5.99
You are right, it should work the way you say. But it doesn’t.
Why Linux people can’t just download and install any version of the software they wish?
Like download the package from a server, and install it on a local machine.
Instead, they have to worry about all the repository hassle.
Software repositories are probably OK and they make it easier to install something. But there should be an easy way to install whatever the user wants to. Isn’t it the definition of freedom?
Packages are built against dependency packages in the distro and distro version which are typically shared libraries. So for a user-supplied package this means a different repository for each version of the package (the distro version can be selected automatically by the package manager), and the package manager takes care of pulling in the dependencies.
On Windows, packages tend to be more standalone, relying only on the Windows DLL which have tons of backward compatibility, i.e. tons of crud, and often contain duplicate versions of stuff which could be shared, like Python interpreters. That’s why Linux is leaner.
Also the freedom of open source refers to freedom to read and reuse the source code, not freedom to bare arms 
or other kinds of freedom.
Generally if you stick with the distro’s repos, you will have few issues. Unfortunately distro packages may not include software you want or lag behind releases. So user-supplied repos are needed to fill the gap.
Linux Mint here.
5.1.12 became 6.0.0
5.99s became 6.0.0-rc1 became 6.99
Everything opened in 6.0.0 from 6.0.0-rc1 without any problems whatsoever. 6.0.0 was recognised as newer than 6.0.0-rc1.
Everything was upgraded from the update manager… one click installations.
It all just “worked” as expected.
Only if the sun don’t shine, otherwise it is “slip, slop, slap” 
Thanks Janek.
I have just discovered what is happening with my installations. I use Synaptic package manager in both computers.
In kubutu 20.04 the repo for stable is alright, 6.0.0-1 dated 2021-12-23
In kubuntu 18.04 the repo for stable is 6.0.0-0rc1 dated 2021-11-19 though the ppa webpage says it must be 6.0.0-1-2021-12-23. The nightly is dated 2021-12-10 and it is also 6.0.0-rc1.
In my 20.04 computer stable is 6.0.0-1 and nightly is 6.0.0-rc1.
Please @jsreynaud, could you check the 18.04 repo? Thanks.
Yes, there is an issue on upstream sources that avoid compilation on bionic (18.04)…
Ubuntu 18.04 is not officially support for KiCad 6.0 but 6.0.1 should fix that (the fix is already commited in 6.0 branch).
See: Ubuntu PPA Package repository- 6.0.0.0rc1 gets installed instead of release (#10279) · Issues · KiCad / KiCad Source Code / kicad · GitLab
Thanks Jean Samuel. At least I can work on 20.04
I could upgrade my 18.04 to 20.04 but I prefer to wait for 6.0.1. i do not like to touch the system until it is absolutely mandatory.
Coming from Windows and doing some struggling with Linux Mint, of course the thing you know always seems easier. But your explanation is over (well, my head anyway) and has reinforced my take that Linux is less idiot-friendly and requires more of a geeky attitude than Windows.
I have heard about this Aussie “thing” on the radio here in USA. Not appropriate during winter here in Pacific Northwest when the sun rarely shines and the temp rarely gets about 10 degrees C. (arms will be covered anyway…)
The issue here is running an old LTS version of Ubuntu. Most user who install new software will want to run 20.04 or the latest 6 monthly release 21.10.
you are free to download what you want, but you are then also free to manage the entire dependency that said application requires… I can freely use scipy,Pandas,tensorflow in a PCBnew plugin submit it as a Content Manager entry and linux users would be able to easily deal with it but windows users are not? is that your definition of freedom?
why is this possible? because of the holistic approach to building an OS. Now linux users could also download a flatpak as an encapsulated standalone package but then they don’t have the freedom and the deduplication of “shared libs” that a system-wid approach offers.
if users and developers work with the package manager it works and flows. it is when people fight it or skip steps that it comes back and bites you
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.