This forum has been archived. All content is frozen. Please use KDE Discuss instead.

How to install Neon without Calamares?

Tags: None
(comma "," separated)
Źmicier
Registered Member
Posts
6
Karma
0
OS
Calarames still seems to be unable to install a system to an encrypted physical volume [1].

How one is supposed to install Neon without Calamares? With debootstrap(8), for instance? Or on top of minimal Ubuntu?

[1] https://github.com/calamares/calamares/issues/1564
Źmicier
Registered Member
Posts
6
Karma
0
OS
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS
On top of an Ubuntu server install would probably be the simplest.
Then add neon's repositories and install neon-desktop.

Code: Select all
$ wget -qO - 'http://archive.neon.kde.org/public.key' | sudo apt-key add -

$ sudo apt-add-repository http://archive.neon.kde.org/user


This is basically how I used to install Neon's up to date Plasma on my Chromebooks.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
User avatar
boospy007
Registered Member
Posts
237
Karma
0
OS
claydoh wrote:On top of an Ubuntu server install would probably be the simplest.
Then add neon's repositories and install neon-desktop.

Code: Select all
$ wget -qO - 'http://archive.neon.kde.org/public.key' | sudo apt-key add -

$ sudo apt-add-repository http://archive.neon.kde.org/user


This is basically how I used to install Neon's up to date Plasma on my Chromebooks.


Very nice!
Źmicier
Registered Member
Posts
6
Karma
0
OS
claydoh wrote:
> Then add neon's repositories and install neon-desktop.

Is that really enough? I believe, no. There are, at least, APT pinnings, as well:

Code: Select all
diff -urN /dev/shm/50-neon-ubuntu-release-upgrader /etc/apt/preferences.d/50-neon-ubuntu-release-upgrader
--- /dev/shm/50-neon-ubuntu-release-upgrader   1970-01-01 03:00:00.000000000 +0300
+++ /etc/apt/preferences.d/50-neon-ubuntu-release-upgrader   2021-03-31 16:53:12.000000000 +0300
@@ -0,0 +1,23 @@
+# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
+# SPDX-FileCopyrightText: 2020 Harald Sitter <sitter@kde.org>
+
+# Pin ubuntu-release-upgrader. There's no reason we'd ever want to use the
+# upgrader from ubuntu since it's not adjusted to neon. So, same as with
+# base-files we'll want to stick to our version even when there's a new
+# version from ubuntu available. The new version will be merged in due time.
+
+Package: python3-distupgrade
+Pin: origin "archive.neon.kde.org"
+Pin-Priority: 1100
+
+Package: ubuntu-release-upgrader-core
+Pin: origin "archive.neon.kde.org"
+Pin-Priority: 1100
+
+Package: ubuntu-release-upgrader-gtk
+Pin: origin "archive.neon.kde.org"
+Pin-Priority: 1100
+
+Package: ubuntu-release-upgrader-qt
+Pin: origin "archive.neon.kde.org"
+Pin-Priority: 1100
diff -urN /dev/shm/99-focal-overrides /etc/apt/preferences.d/99-focal-overrides
--- /dev/shm/99-focal-overrides   1970-01-01 03:00:00.000000000 +0300
+++ /etc/apt/preferences.d/99-focal-overrides   2021-03-31 16:53:12.000000000 +0300
@@ -0,0 +1,78 @@
+# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
+# SPDX-FileCopyrightText: 2020 Jonathan Riddell <jr@jriddell.org>
+
+Package: libqtav1
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libqtavwidgets1
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libqtav-dev
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libqtav-private-dev
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: qml-module-qtav
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: qtav-players
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libepub-dev
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libepub0
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: ebook-tools-dbg
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: epub-utils
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: bubblewrap
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: zipmerge
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: ziptool
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: zipcmp
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: python-sip
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libzip-dev
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: python-sip-dev
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: wayland-protocols
+Pin: release o=Ubuntu
+Pin-Priority: 1100
+
+Package: libappimage0
+Pin: release o=Ubuntu
+Pin-Priority: 1100
diff -urN /dev/shm/99-neon-base-files /etc/apt/preferences.d/99-neon-base-files
--- /dev/shm/99-neon-base-files   1970-01-01 03:00:00.000000000 +0300
+++ /etc/apt/preferences.d/99-neon-base-files   2021-03-31 16:53:12.000000000 +0300
@@ -0,0 +1,6 @@
+# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
+# SPDX-FileCopyrightText: 2019 Jonathan Riddell <jr@jriddell.org>
+
+Package: base-files
+Pin: origin "archive.neon.kde.org"
+Pin-Priority: 1100
diff -urN /dev/shm/99-neon-qca /etc/apt/preferences.d/99-neon-qca
--- /dev/shm/99-neon-qca   1970-01-01 03:00:00.000000000 +0300
+++ /etc/apt/preferences.d/99-neon-qca   2021-03-31 16:53:12.000000000 +0300
@@ -0,0 +1,11 @@
+Package: libqca*
+Pin: release o=neon
+Pin-Priority: 1100
+
+Package: qca-qt5*
+Pin: release o=neon
+Pin-Priority: 1100
+
+Package: qca2-utils
+Pin: release o=neon
+Pin-Priority: 1100


What else could missed our attention?
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS
Źmicier wrote:claydoh wrote:
> Then add neon's repositories and install neon-desktop.

Is that really enough? I believe, no. There are, at least, APT pinnings, as well:

[snipped]
What else could missed our attention?


The pinning are set via configs found in the package neon-settings-2, which is installed as a dependency of the meta-package neon-desktop.
This particular package has different Neon specific settings involved.
There are other packages included as well that do similar things elsewhere.







As a side note, doing this on a system with an existing Plasma install (ie Kubuntu) will have an extremely high chance of failure due to differences in packaging/dependencies.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
jmacleod
Registered Member
Posts
50
Karma
0
Not wishing to hijack the thread - just the part about adding repositories....

Is there any way of installing Plasma other than task-kde-desktop. Just trying to find an install with only essential packages!

Thanks
User avatar
claydoh
Registered Member
Posts
1170
Karma
9
OS
jmacleod wrote:Not wishing to hijack the thread - just the part about adding repositories....

Is there any way of installing Plasma other than task-kde-desktop. Just trying to find an install with only essential packages!

Thanks



Not sure, as task-kde-desktop is not something found in Ubuntu/Neon. Assuming you are using Debian? Neon is not compatible with Debian.
There, these are some metapackage options to install different levels of Plasma/KDE things:

https://wiki.debian.org/KDE#KDE.27s_software_in_Debian

Probably installing kde-plasma-desktop is what you are looking for. Again, assuming you are using Debian.
If using something related to Ubuntu, and Neon's repos, then neon-desktop is the one to use. Neon only installs the most minimal desktop: Plasma, SDDM, and core apps like Dolphin, Ark, and System Settings.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar