Here is what I get when I try to upgrade:

Code: Select all

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Entering ResolveByKeep 10%
  Dependencies are not satisfied for neon-adwaita:amd64 < none -> 0.0+p18.04+git20180904.1047 @un uN Ib >
Keeping package neon-adwaita:amd64
  Policy breaks with upgrade of neon-desktop:amd64 < 4+p18.04+git20180904.1046 -> 4+p18.04+git20181003.1744 @ii umU IPb >
Keeping package neon-desktop:amd64
Calculating upgrade... Done
The following packages have been kept back:
  neon-desktop
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Code: Select all

$ sudo apt list --upgradable -a
Listing... Done
neon-desktop/bionic 4+p18.04+git20181003.1744 amd64 [upgradable from: 4+p18.04+git20180904.1046]
neon-desktop/bionic 4+p18.04+git20181003.0942 amd64
neon-desktop/bionic,now 4+p18.04+git20180904.1046 amd64 [installed,upgradable to: 4+p18.04+git20181003.1744]
neon-desktop/bionic 4+p18.04+git20180823.1431 amd64

Is it a bug? I'd appreciate any help in solving this.

UPGRADE KDE NEON
$ sudo pkcon refresh
$ sudo pkcon update
Буде тебе счастье

Thank you for a fast answer, it upgraded successfully with pkcon commands.

But this makes me curious, what's the difference between apt and pkcon? Why was apt unable to resolve dependencies?

PARTyZAN wrote:Thank you for a fast answer, it upgraded successfully with pkcon commands.

But this makes me curious, what's the difference between apt and pkcon? Why was apt unable to resolve dependencies?

Using apt upgrade on an Ubuntu system does not install new package dependencies , apt full-upgrade does. This is different from how it normally is done in Debian, and has caused some confusion, so using pkcon (the commandline version of what Discover uses, via packagekit, under the hood) is the preferred method in order to keep this confusion at bay.

Apt will still work just fine, if used as it is in Ubuntu.

Got you, thanks for explanation.