Now in branch but it's not getting pushed to the server for some reasons, needs a sysadmin to look
https://cgit.kde.org/websites/neon-kde-org.git/commit/?id=c89fe7c353d82ba06b283db5434ad49e490f7fec

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

Now switched over to kdesdk-devenv-dependencies

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.

done

@mak, assistance needed. :) ^^

https://lists.freedesktop.org/archives/appstream/2019-June/000288.html

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

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.

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" :)

I have one comment: ISO files are supposed to be burned to optical media. The fact that one can create hybrid ISOs which can also be written to USB drives doesn't mean that all ISOs can be written to USB drives. Most Linux distros generate hybrid ISOs, but some do not, and other operating systems (Windows, for example) do not.

This is implemented in an addon shellprocess already. https://packaging.neon.kde.org/neon/calamares-settings.git/tree/desktop/calamares/desktop/modules/shellprocess_install_translations.conf?h=Neon/unstable&id=89847bf2ff81a1212ad392bf055aec790cbfb851

tracking via meta task https://phabricator.kde.org/T9376

This is available as alpha prototype in unstable now. Remaining stuff tracked at https://phabricator.kde.org/T9376

The flash drive selector is on another screen to avoid using dialog windows extensively. The user will be allowed to proceed to the flash drive selection screen only after selecting a valid ISO image.

Looks good! It doesn't follow the original mockup in that the flash drive selector is on another screen, but that's probably fine.

I am working on the KDE ISO Image Writer as part of GSoC and based on this discussion I created the following mockups:

alkimia

This is done https://build.neon.kde.org/job/merger_gpgme/

Also added to iso seeds and isos rebuilt then put on social media

appimagelauncher now in
the postinst script calls dpkg-architecture but that is part of dpkg-dev which may not be installed. If this is needed it needs a Pre-Depends

needs a second look at phonon them to work out why the build isn't passing

declarative I think too

zeitgeist is qt4 only (and dead)

or maybe not it's probably obsolete.

I've made that annoying job-updater error have some useful debugging so now it says the KDE repo it's look for, the neon repo it's coming from and the branch it cares about. In the case yesterday I had not set all the branches so it was erroring there. Should be fixed now. Please update qca2 packaging and builds and see if you can merge into debian repo ready for upload when it unfreezes

check the released kmymoney and merge packaging into Neon/release-lts ?

git master's cmakelists of labplot have been made standard conform and should now properly report all packages in the cmake feature summary. IOW: CI should now report when things are missing on unstable.

It's a clone of your repo for libappimage yes, you should be able to add yours as a remote and merge in changes.

Hi!
https://packaging.neon.kde.org/backports-bionic/libappimage.git
Is this a mirror of my repo?
https://salsa.debian.org/sgclark-guest/libappimage
I would like to just update my repos in debian salsa, though I guess I can just merge it in via remote add.
Where should I put appimagelauncher? neon-packaging or this bionic-backports thing? Can I mirror my repo?
Thanks,
Scarlett

Looks like you already compiled kmymoney with new alkimia :) will test and merge unless already done.

I've done first two:
Update to alkimia 8
Move to extras/ from bionic backports

This does seem kind of scary. libgmp and mpir have the same symbols so can't be installed at the same time I think. libgmp has a load of very vital rdepends
apt-cache rdepends libgmp10
and can not be removed from the system. So if we are to use MPIR which i think is recommended by the alkimia guy then that would need worked out somehow. It may be worth contacting him directly (Ralf) to ask what he recommends.

Essentialy mpir is not compatible with gmp as they use the same symbols. https://lists.debian.org/debian-science/2015/03/msg00021.html
Debian made the decision to not have it in archive. I can package it, but I do not know what else we may have that uses gmp. It could very well break things. Just letting you know :)

Done but needs merged into Debian when unfrozen by @scarlettmoore

Discover doesn't export appimagehub without packaging and installing scratch/apol/xdgthing so we'll ignore it like Discover wants us to.

libappimage is in and added to kio-extras for thumbnail goodness.

this turned out to be quite the rabbit hole...

the chap that wrote the tooling's collapser.rb was right forward-thinking and the implementation of the Unpacker class in there is actually useful to replace most of the stuff going on in that dockerfile.

https://github.com/kenvandine/gnome-3-28-1804/blob/master/Dockerfile

kipi-plugins now released and split out, nearly semi sane again