we have the data now but I'm unsure how to proceed
[18:22] <sitter> JonathanRiddell-: I'm not quite sure what to do with the html we could pop it into the metadata domain and iframe it on the website, but then I am also not sure where to put it on the website https://build.neon.kde.org/view/mgmt/job/mgmt_version_list_bionic_user/2/artifact/versions.html [18:22] <sitter> also the squishing problem I mentioned earlier screws this plan, so that needs fixing IMO
it didn't like comments in cmake-ignore
yeah seems sorted
Apps / Frameworks / Plasma seems the main use case, although individual extragear apps would also be interesting
I do wonder if we even should care about extragear. That may just complicate things?
This is already solved.
watcher.rb checks which projects.kde.org product a build belongs to and if it is one of the bundles it sends a warning mail and refuses to auto-bump.
kde4 translations are dead upstream. phonon is now using kf5 translations, and I would presume kdeedu too?
kicon cache is a huge drag (10MiB per kde snap). in point of fact I suspect all of .cache is being fairly awkward but I also do not think this is all too solvable. there is no way to ensure that the cache format of snap X is the same as Y, so they couldn't share the cache.
no reply, so inactive, we won't package it
Closing this task for now. We've missed the mark by a bit, and from the neon side things should be more or less in place right now. So, this is mostly blocked on actually having the plasma wayland UX ready for primetime. Or perhaps more importantly, should the requirements change we need to reshuffle the stack anyway, so having a perpetually stuck task serves no purpose.
Mon, Jul 15
Wed, Jul 10
Tue, Jul 9
Do existing installs get migrated, or is this only for new installs?
All ISOs respun and openqa updated as well. Transition complete.
Mon, Jul 8
Reassigning to Neon.
Mon, Jul 1
Fri, Jun 28
I just find the phab board a bit easier to keep track of but I'll keep the two in sync if ever I set up a phab task for a bug report
Works great for me! Maybe the CMS hadn't updated yet.
Thu, Jun 27
Now in branch but it's not getting pushed to the server for some reasons, needs a sysadmin to look
Tue, Jun 25
unstable, testing and release now have updates for libinput by default. pending snapshot for user edition (alongside 5.16.2) and ISO rebuilds for complete resolution
Fri, Jun 21
Wed, Jun 19
Now switched over to kdesdk-devenv-dependencies
Tue, Jun 18
Packaging it for Debian is not difficult (I have a basic packaging locally already). However, unless there is a proper stable release, then it is not worth it.
Of course, since this a Neon task, in Neon you can do whatever you want :) (and I do not care about that)
Now it needs taking into Debian.
Jun 17 2019
@mak, assistance needed. :) ^^
Building locally I get a compile failure so some investigation needed
../src/as-pool.c: In function ‘as_pool_get_components’:
../src/as-pool.c:1287:29: error: implicit declaration of function ‘g_ptr_array_steal_index_fast’; did you mean ‘g_ptr_array_remove_index_fast’? [-Werror=implicit-function-declaration]
g_ptr_array_add (result, g_ptr_array_steal_index_fast (tmp_res, 0)); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ g_ptr_array_remove_index_fast
Actually let's do 0.12.7. It was just released and fixes https://bugs.kde.org/show_bug.cgi?id=406384
Jun 14 2019
branches made, job updater running
pushed packaging but it does not work as sane-config does not get included in sane-backends packages. I've e-mailed the debian sane-backends maintainer.
Jun 10 2019
An issue I see is that on the second view there is no indication of what ISO image you selected, so if you selected the wrong file you have no idea of knowing.
The name seems accurate: it's an app to write ISO images, because it only supports the "write" use case and not the "burn" use case. If it supported optical media too, it might be more aptly named "ISO Image Writer/Burner" :)