Better Additional PPAs for Brave Bionic Testing

[NoWorries]

I have found after doing a new installation, that the staging kdeapplications, frameworks and misc ppa's that I had in the original post for this topic are no longer required.

[S]sudo add-apt-repository ppa:kubuntu-ppa/staging-kdeapplications
sudo add-apt-repository ppa:kubuntu-ppa/staging-frameworks
sudo add-apt-repository ppa:kubuntu-ppa/staging-misc[/S]

Updates from these ppa's are invoked by selecting the Pre-released and Unsupported option that is in the Muon Package Manager > Configure Software Sources > Updates.

The current status of my Bionic is now:



The staging plasma ppa

sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma

is definitely useful if you want the latest plasma which is shown in the above image. I think that more updates are likely in the coming days.

I am still waiting for the kernel update to 4.15 as I do not have the courage to install it from the deb files that are available.

I hope those who are using the additional ppa's that I initially proposed with the above exclusions are finding their systems as stable as I am.

[oshunluvr]

KDEneon user finally got 5.12:

[NoWorries]

Good to see that Neon is not far behind. Since the only difference between Bionic and Neon is the kernel version. Then I would like to know what is the benefit in having Neon installed?

One interesting feature I have noticed with Bionic is its treatment of updates. When I boot up Bionic I find that, at times, there is a significant download occurring and I then Discover reports that updates are available. If I wait a while before starting Discover to see the updates and then start the update process, no download occurs but it looks as though Discover has already downloaded the packages and is doing the installation from looking at the CPU load.

[Snowhog]

Change your settings. I personally don't allow either background downloading or automatic installation. I want to be in controll of both processes.

[oshunluvr]

Good to see that Neon is not far behind. Since the only difference between Bionic and Neon is the kernel version. Then I would like to know what is the benefit in having Neon installed?

The benefits have dwindled as we approach 18.04. Also, I'm using the "User" edition, Vinny had 5.12 two weeks ago using the Dev. edition. Over the last two years, my KDE/PLasma releases have been weeks or a month ahead of Kubuntu. 18.04 is the stopping point because the Neon team will be moving to it also.

The benefits are a stable base while still having the latest and greatest Plasma. I don't need or often want the litany of software updates to things outside my DE, so Neon lets me opt-out. I'm basically half-way between 16.04 and 18.04 without any do-release-upgrade headaches.

I also no longer jump on the 6-month release band-wagon. I stopped doing that in 2011 when the .10 release once again caused me problems. At that time, I actually went looking for another distro entirely, thinking the rolling-release idea was better. My research revealed few viable options and rather changed my mind about the rolling-release idea. It seems fraught with more problems than it solves, so I'm still here. My server is still on 14.04 and will be until this summer. I will likely move to Neon-18.04 when it's out.

[NoWorries]

Change your settings. I personally don't allow either background downloading or automatic installation. I want to be in controll of both processes.

I certainly agree that it is useful to be in control of both processes. However I have not found anywhere that these processes can be controlled.

I would like to know where the options for the control of the download and update of packages can be set.

[Snowhog]

Launch Muon Package Manager. Click on Settings > Configure Software Sources. Enter your password. Click on Updates. Under Automatic updates check Only notify about available updates.

[NoWorries]

Thanks for the clarification oshunlvr as I now understand where you are coming from.

As you are likely to be aware, I always update my system every 6 months thick and thin. I must admit that I have a tolerant wife and in the past I normally use her laptop to test new releases before committing my system.

This approach may change in the future. At least I always have the latest release available to test and comment on problems in the hope that Kubuntu continues to be advanced.

[oshunluvr]

Thanks for the clarification oshunlvr as I now understand where you are coming from.

As you are likely to be aware, I always update my system every 6 months thick and thin. I must admit that I have a tolerant wife and in the past I normally use her laptop to test new releases before committing my system.

This approach may change in the future. At least I always have the latest release available to test and comment on problems in the hope that Kubuntu continues to be advanced.

Yes, I've followed your bumps in the road

I usually install each release in a VM so if needed, I can check things out. I will say that since o started using Kubuntu - 09.04 - it has gotten better by leaps and bounds. By better, I mean less likely to break. Of course, my skill set has come along a bit since them too, so that helps.

[NoWorries]

Launch Muon Package Manager. Click on Settings > Configure Software Sources. Enter your password. Click on Updates. Under Automatic updates check Only notify about available updates.

Hi Snowhog, you have now clarified where the settings are located. I have been a Synaptic fan for some time now and only use Muon when it provides features that Synaptic does not have. So I failed to checkout Muon to solve my problem. Thanks very much for your guide on how to use Muon to take control of package updates on startup.

I have now tried Muon in areas that it previously disappointed me and am starting to like it a lot. Previously, when I did a new installation, my first action was to install Synaptic. So I have now purged Synaptic from this system and now use Muon.

Thanks for helping me in this area to take another look at Muon. At east my lights are now ON!

[oshunluvr]

I have been a Synaptic fan for some time now and only use Neon when it provides features that Synaptic does not have. So I failed to checkout Neon to solve my problem. Thanks very much for your guide on how to use Neon to take control of package updates on startup.

I have now tried Neon in areas that it previously disappointed me and am starting to like it a lot. So I have now purged Synaptic from this system and now use Neon.

Thanks for helping me in this area to take another look at Neon.

Did you mean "muon" instead of "neon" or are you trying to be funny?

[NoWorries]

So sorry, I was in a hurry and I should have used "Muon".

The reason I was in a hurry was that I was busy testing out Wayland on Bionic and did a post on the success I had in having it run on Bionic. I also was in a hurry to collect my Grandson from School.

Thanks for picking it up so quickly. I am currently doing this post on my Wayland desktop. So I should take it easy and check that I do not make clangers when doing a post.

[oshunluvr]

So sorry, I was in a hurry and I should have used "Muon".

The reason I was in a hurry was that I was busy testing out Wayland on Bionic and did a post on the success I had in having it run on Bionic. I also was in a hurry to collect my Grandson from School.

Thanks for picking it up so quickly. I am currently doing this post on my Wayland desktop. So I should take it easy and check that I do not make clangers when doing a post.

I figured it was something like that, but it sure made for some confusing reading for a bit!

[benny_fletch]

I will likely move to Neon-18.04 when it's out.

Does anyone have any insight on how the current Neon LTS is going to move to 18.04? As in, will there be an upgrade path or will it be a fresh install?

The reason I ask is I am currently running xubuntu 16.04, but I have wanted to get back to a KDE based distro for some time and I do not know if I want to wait until April. I started looking at KDE neon LTS 5.12 and I love it, but before I install it (and commit to the whole process that goes with it) I would like to know what I will be facing in April/May. Any insights would be appreciated!

[oshunluvr]

They're not even saying when they're switching yet, but I would guess within weeks of the release of 18.04. Last I read, they hadn't decided if it would be a mandatory fresh install or a "do-release-upgrade". Personally, I always do a new install anyway.