Living on the Edge with KDE Project Neon

[NoWorries]

Ok, I lied, musta clicked the same link twice, or it looks like updates are rolling now

I did note a few failed-to-build packages earlier, don't see them now

Lying is a very emotive term and, in the spirit of this forum, I would never say the you lied but you made an honest mistake, which is very easy to make.

[vinnywright]

today’s updats 9/11/14

The following packages will be upgraded:
  apport apport-kde project-neon5-baloo project-neon5-frameworkintegration
  project-neon5-kactivities project-neon5-karchive project-neon5-kauth
  project-neon5-kbookmarks project-neon5-kcmutils project-neon5-kcodecs
  project-neon5-kcompletion project-neon5-kconfig project-neon5-kconfigwidgets
  project-neon5-kcoreaddons project-neon5-kcrash project-neon5-kdbusaddons
  project-neon5-kde-cli-tools project-neon5-kdeclarative project-neon5-kded
  project-neon5-kdelibs4support project-neon5-kdesignerplugin
  project-neon5-kdesu project-neon5-kdewebkit project-neon5-kdnssd
  project-neon5-kdoctools project-neon5-kemoticons project-neon5-kfilemetadata
  project-neon5-kglobalaccel project-neon5-kguiaddons
  project-neon5-khelpcenter project-neon5-khotkeys project-neon5-khtml
  project-neon5-ki18n project-neon5-kiconthemes project-neon5-kidletime
  project-neon5-kinfocenter project-neon5-kinit project-neon5-kio
  project-neon5-kio-extras project-neon5-kitemmodels project-neon5-kitemviews
  project-neon5-kjobwidgets project-neon5-kjs project-neon5-kjsembed
  project-neon5-kmenuedit project-neon5-knewstuff project-neon5-knotifications
  project-neon5-knotifyconfig project-neon5-kparts project-neon5-kplotting
  project-neon5-kpty project-neon5-krunner project-neon5-kservice
  project-neon5-ksysguard project-neon5-ktexteditor project-neon5-ktextwidgets
  project-neon5-kunitconversion project-neon5-kwallet
  project-neon5-kwidgetsaddons project-neon5-kwin project-neon5-kwindowsystem
  project-neon5-kwrited project-neon5-kxmlgui project-neon5-libkscreen
  project-neon5-libksysguard project-neon5-libnm-qt project-neon5-milou
  project-neon5-oxygen project-neon5-plasma-desktop
  project-neon5-plasma-framework project-neon5-plasma-nm
  project-neon5-plasma-workspace project-neon5-polkit-qt-1
  project-neon5-powerdevil project-neon5-solid project-neon5-sonnet
  project-neon5-systemsettings project-neon5-threadweaver python3-apport
  python3-problem-report
80 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.3 MB of archives.
After this operation, 4,096 B of additional disk space will be used.
Do you want to continue? [Y/n]

and of course I hit Y

VINNY

O and to add,,,,,,,we would never think claydoh intentionally lied !!

[Teunis]

A Firefox problem, after a restart it has forgotten it's previous tabs etc.

I've been comparing file permissions etc. between the regular Firefox and the Neon one but so far no luck.

[claydoh]

A Firefox problem, after a restart it has forgotten it's previous tabs etc.

I've been comparing file permissions etc. between the regular Firefox and the Neon one but so far no luck.

Firefox should be using the stock Mozilla config directory, shouldn't it?

[Teunis]

Upon installation of Neon Firefox seems to have made a copy of the Mozilla directory.
Part of it is under ~/.mozilla/firefox/code.default.neon/ and another part under ~/.project-neon5-kde/cache/mozilla/firefox/code.default

[claydoh]

Upon installation of Neon Firefox seems to have made a copy of the Mozilla directory.
Part of it is under ~/.mozilla/firefox/code.default.neon/ and another part under ~/.project-neon5-kde/cache/mozilla/firefox/code.default

I'd get rid of/move the one in neon, that looks to be a cache anyway (as it would also be in your ~/.cache folder normally, in a regular session). perhaps it is corrupt, or not being copied over or something.

[Teunis]

Yes, that's the one!
I renamed iit, upon restarting Firefox a new one was created and Firefox gave it's usual oops with the option to restore the last session.

Thanks for the pointer!

[Teunis]

Since two days I'm getting this error from Muon, any suggestions?

/var/cache/apt/archives/project-neon5-kio_0.0+git20141007.0321+neon4~50c0005~14.04_amd64 .deb
trying to overwrite '/opt/project-neon5/lib/x86_64-linux-gnu/plugins/kcm_trash.so', which is also in package project-neon5-kio-extras 0.0+git20140928.0353+neon4~90b5683~14.04

[claydoh]

Since two days I'm getting this error from Muon, any suggestions?

Packaging snafu, or change - the file kcm_trash.so was originally found in the package project-neon5-kio-extras 0.0+git20140928.0353+neon4~90b5683~14.04 (note the date in red)
It is now in the package project-neon5-kio_0.0+git20141007.0321+neon4~50c0005~14.04. Whether by change in the source archives or (less likely) a packaging error, it can happen at times, especially as the bleeding edge stuff that neon builds from can be in flux or transition as to how KDE splits up the codebase.

It is an easy fix, though.

sudo dpkg -i --force-overwrite /var/cache/apt/archives/project-neon5-kio_0.0+git20141007.0321+neon4~50c0005~14.04_amd64 .deb
We are manually installing the new package, and telling it to overwrite any files that are marked as having been installed from a different package.

[Teunis]

Ah force from the cache!

Thanks for the help, all is well.

[vinnywright]

Since two days I'm getting this error from Muon, any suggestions?

when I got that error ,,,, a day or 2 ago ,,,,,,it was during a 110 package upgrade .

whitch stoped it from being configured ,,,,,,I first ran

sudo apt-get -f install

whitch set up/configured all the unpacked packages then did the

[FONT=Monospace]sudo dpkg -i --force-overwrite [COLOR=#333333]/var/cache/apt/archives/project-neon5-kio_0.0+git20141007.0321+neon4~50c0005~14.04_amd64 .deb [/COLOR][/FONT]

,,,,,, and all was well.

guess in hind site I should have reported it @hear ,,,,,,,,oops

VINNY

[Teunis]

Whether the first post is a report with solution or a quest for a solution we generally see/get one anyway

[rjvbb]

the bleeding edge stuff that neon builds from can be in flux or transition as to how KDE splits up the codebase.

No, that's not KDE's doing, that's the choice of a packager, IMHO.

What's going on with the Project Neon5 PPAs? The weekly snapshot has completely disappeared, and the daily one is now marked "DO NOT USE", with a pointer to another package source that just reeks like it might install KF5 in the main tree, under /usr. And things aren't ripe for that AFAIC.

[Rog132]

Ci / cp

What's going on with the Project Neon5 PPAs? The weekly snapshot has completely disappeared, and the daily one is now marked "DO NOT USE", with a pointer to another package source ...

https://launchpad.net/~neon/+archive/ubuntu/kf5



Continuous Integration / Continuous Packaging

kubuntu-devel -- Kubuntu Developer Discussion: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

continuous packaging? anyone?: https://lists.ubuntu.com/archives/ku...st/008651.html

# what is this?
CP is essentially what project-neon does, build all packages off of
upstream git. Conceptually this technically is supposed lto be like
proper CI (i.e. build as often as possible with as small changes as
possible and run tests). Since this is partially not very practical
from a packaging perspective let's for now think of it as regular
daily builds.

# what's wrong with neon? :O
Neon is built in a very specific way. Namely:
- completely different prefix
- excessive envrionment manipulation to separate data lookup (as much
as possible) as well as user specific data and settings storage
- single binary units (i.e. each upstream git repo creates exactly one
debian package)
It is made this way because it creates next to no overhead in
packaging, this is curcial to what neon is meant to achive: Provide
the most bleeding edge of KDE software *next to* the ongoing efforts
of high quality packaging we do manually. In other words neon is made
in such a way that it does not take away developer time from the real
meat, at the expense of Debian policy compliance (in some ways
anyway)...

More links:

- Project neon: https://lists.ubuntu.com/archives/ku...er/008922.html

- CP rollout plan: https://lists.ubuntu.com/archives/ku...st/008693.html
- kubuntu cp ppa name: https://lists.ubuntu.com/archives/ku...er/008735.html
- CP, jenkins, and all that madness: https://lists.ubuntu.com/archives/ku...st/008712.html
- kubuntu-ci & issues at hand: https://lists.ubuntu.com/archives/ku...er/008764.html

[rjvbb]

So while the dust settles, the (more or less?) automatic package creation in the daily and weekly snapshots have been stopped, meaning there is no way to install an up-to-date parallel KF5 workspace for the foreseeable future?

And is there an answer already whether it will remain possible to install KF5 in parallel to the currently packaged high quality KDE4 environment?