![]() Registered Member ![]()
|
The upgrade is moving the core OS from Ubuntu 16.04 LTS to 18.04 LTS: The kernel, driver stack, and overall software repositories outside of Plasma/Qt, and irrespective of User, git-stable, and git-unstable branches.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
![]() Registered Member ![]()
|
I've tried upgrade to 18.04 on your links. The process itself went without falling but the result was disastrous. Neon is a meta-pack and now it has a bionic resume at sources.list.d. I can not add ppa repositories, the programs I added earlier did not work.
And finally, I got a bad developer version that I could download and install. If I had done so, I would have a correct developer version that works.
sources.list.d neon.list is thet correct
|
![]() Registered Member ![]()
|
As far as I can see from the proper distribution, I got Frankstead distribution. The instructions that are to be used are for testing by the system, try and throw. I'm a fool that I believe in writing that everything works.
I am thinking that the user of Arch or Manjara felt that AUR and localization did not work for him or the user of the Gentoo distro to not do his layman and localization. That's exactly what they received from these superficial tips for upgrading to 18.04 |
![]() Registered Member ![]()
|
Everything works fine with all ppa since weeks. You must edit the file "/etc/lsb-release"
|
![]() Registered Member ![]()
|
Thanks for the advice, now for adding ppa. I've put the localization in en-usa and put my language as the second. For now everything works but now this is not Neon this is Ubuntu..
![]() |
![]() Registered Member ![]()
|
Followed the instructions at https://community.kde.org/Neon/BionicUpgrades.
Upgrade to Bionic went swimmingly on my small laptop.. Had to re-install the Bionic builds of virtualbox and radiotray-ng but both remembered all the settings. No gotcha's after a couple of days. Interestingly, my tower is completely ignoring the edit to "/etc/update-manager/meta-release". Go figure. I'll do a clean install on the tower when the updated iso is released anyway. |
![]() Registered Member ![]()
|
Update worked for me. But I can't turn my PPAs and other software sources back on. When I try the sources tab in Discover>Settings, it is ghosted out and says "NULL." And when I try typing in the console: "sudo software-properties-kde" I get the following error, so I am kind of stuck for now. Any ideas how I should set it?
|
![]() Registered Member ![]()
|
OK, I read that I needed to edit /etc/lsb-release so that gets me my software-properties-kde. But then software-properties-kde tells me that:
"Your local copy of the software catalog is out of date. A new copy will be downloaded." But this fails with: "Refresh failed. Could not download packages" and in the terminal it says: "Home directory not accessible: Permission denied" Executing sudo, is it looking for my home directory, or for root? Does root even have a home directory? This seems to lead back to that "QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'" error again. |
![]() KDE Developer ![]()
|
Update /usr/share/python-apt/templates/neon.info for bionic |
![]() Registered Member ![]()
|
What to do in this file, how many I've seen there is a lot of Ubuntu distributions written. Should it be necessary to replace xenial with bionics or to make an identical structure but to write bionic Very interesting when looking at the setup, everything is Ubuntu and this unofficial version of 18.04 and in the official version with the base 16.04. Neon as the carrier of distribution is put as meta-packing and like all programs that are added from ppa. This unofficial version does not work well if it does not break into Ubuntu and the localization is not resolved. |
![]() Registered Member ![]()
|
AFAIK Neon wil not be updated to 18.04 until those involved are happy that it is fully complete.
See this link from Riddell https://jriddell.org/2018/07/26/kde-neon-bionic-update/ |
![]() KDE Developer ![]()
|
https://packaging.neon.kde.org/neon/set ... 0dd41fe88d |
![]() Registered Member ![]()
|
Thanks for the answer but I have another dilemma. Where to put these definitions in neon.info because at the very beginning there is a group of definitions called devel and then follows xeinal group definitions. Do you delete the devel group and put it from the link or add after the devel group. There is an Ubuntu.info file that also starts with the devel group and there is all that is on the link that is given as an example. If after changes to neon.info I can go back to lsb-release neon instead of ubuntu because now the distribution is called Ubuntu in the grub menu. |
![]() Registered Member ![]()
|
Yes I know, but now I got into that and at least I have a usable distro until the final version is released. |
![]() Registered Member ![]()
|
Neon not releasing until they are completely happy with the product is great news. A rushed and buggy product would be undesirable.
Proud to be powered by Plasma
|
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]