I am afraid it is not obsolete nonsense. I just so happened to install debian last night do to an unfortunate event. And I saw discover "scanning for hardware" I looked it up and
https://tracker.debian.org/pkg/discover is maintained by the installer team. So I wish you the best of luck on removal. Sorry !

Breeze
https://packaging.neon.kde.org/kde/breeze.git/log/?h=Neon/unstable_merge
MERGED - 12/7
UPDATED - 12/8&12/9
https://build.neon.kde.org/job/bionic_unstable_kde_breeze/
Notes:
There is still a diff with the default printer page that looked very Neon specific. I need to know if this is not the case and needs to be upstreamed to debian.

This RR is now obsolete due to commit: https://cgit.kde.org/kcoreaddons.git/commit/?id=e53254a009982c379a5ad713139e88a881ca02fb

In T8586#169475, @jriddell wrote:

I wonder if I merge these - should resolve the issue?

peruse in neon only uses kirigami2
plasma-sdk only uses kirigami2 ?
kube doesn't seem to use any kirigami (from a grep of source) so try just removing it there

so I think that means we can kill off kirigami1 packaging and merge in debian's one

so essentially I need to merge our kirigami2 into kirigami ( Neon branches ) - then merge master and then we dump the kirigami2 and kirigami1 and left with only kirigami - I think we need to update jobs to point to kde/kirigami? no trailing 1 or 2.

In T8586#167431, @scarlettclark wrote:

New entry for un-merged NEED assistance

Kpackage
diff --git a/debian/control b/debian/control
index 8a7a919..6d55fd3 100644

• a/debian/control +++ b/debian/control @@ -25,6 +25,7 @@ Vcs-Git: https://salsa.debian.org/qt-kde-team/kde/kpackage.git Package: kpackagetool5 Section: kde Architecture: any +Multi-Arch: foreign Depends: ${misc:Depends}, ${shlibs:Depends} Breaks: kpackagelauncherqml (<< 5.51), libkf5declarative5 (<< 5.51),
  
  I was going to merge request this upstream. But it seems wrong? that is a binary package - I thought foreign was things like docs that are platform independent. @bshah made the commit. I need backup if I am to upstream this.

Knewstuff
There is a diff in rules where we have a fix perms: @jriddell
87cab9b ("dont remove executable on script", 2017-11-09)
+
+override_dh_fixperms:
+ $(overridden_command) -X_update_all_files.sh
Is this something that can be merged into debian? If so I need the "why"

In T8586#167425, @scarlettclark wrote:

New entry for un-merged and reason why.

TO-DO
Kirigami 1 2 what the heck??
Debian seems to package this in a repo called kirigami
We package it in kirigami2 and master is all neon commits. I am not touching this. So confusing..
REASON
The kirigami issue is we package kirigami1 as well as kirigami2 while I think Debian only packages kirigami2.
You could check if the rdepends of qml-module-org-kde-kirigami really still need kirigami1 or if they can be updated and the package dropped

Syndication -
https://packaging.neon.kde.org/kde/syndication.git/log/?h=Neon/unstable_merge

This has a diff in signing keys - this should be pushed to debian?
https://packaging.neon.kde.org/kde/syndication.git/commit/?h=Neon/unstable&id=2de11348d54275afba76daba92100c3ec2ed8fac
REASON
On hold for 5.51 release was missed in debian. Inquiry is in.

Kconfigwidgets -
https://packaging.neon.kde.org/kde/kconfigwidgets.git/log/?h=Neon/unstable_merge

Incidently this has both a .manpages and the manpages are in the -data package - I think debian needs fixing here.
diff --git a/debian/libkf5configwidgets-data.install b/debian/libkf5configwidgets-data.install
index 64d9b94..1f22720 100644

• a/debian/libkf5configwidgets-data.install +++ b/debian/libkf5configwidgets-data.install @@ -1,5 +1,3 @@ etc/ usr/bin/preparetips5 usr/share/locale/* -usr/share/man/*/man1/preparetips5.1 -usr/share/man/*/man1/preparetips5.1 REASON This needs to be upstreamed to debian - WIP - sadly FTBFS
  
  Plasma-framework - https://packaging.neon.kde.org/kde/plasma-framework.git/log/?h=Neon/unstable_merge
  
  diff --git a/debian/control b/debian/control index 276d009..601397f 100644
• a/debian/control +++ b/debian/control @@ -44,6 +44,7 @@ Build-Depends: cmake (>= 3.0~), libxcb-composite0-dev, libxcb-damage0-dev, libxcb-shape0-dev, + mesa-common-dev, pkg-config, pkg-kde-tools (>= 0.15.15ubuntu1~), qtbase5-dev (>= 5.8.0~),
  
  Jonathan commit: https://packaging.neon.kde.org/kde/plasma-framework.git/commit/?h=Neon/unstable_merge&id=e5c294843de12b95fa5ca6dd33236d0c713826f2

Remove class QVariant as per bruns review comment.

In T8586#167425, @scarlettclark wrote:

New entry for un-merged and reason why.

TO-DO
Kirigami 1 2 what the heck??
Debian seems to package this in a repo called kirigami
We package it in kirigami2 and master is all neon commits. I am not touching this. So confusing..
REASON
The kirigami issue is we package kirigami1 as well as kirigami2 while I think Debian only packages kirigami2.
You could check if the rdepends of qml-module-org-kde-kirigami really still need kirigami1 or if they can be updated and the package dropped

Still has depends -
peruse
kube
plasma-sdk
plasma-sdk

*Tier 4 / Porting aids*

In T8586#167501, @jriddell wrote:

when moving /etc files bump the changelog version and add a mainscript in the style of kate's debian/kate5-data.maintscript
and test to make sure, the documentation on what to do with moving conffile seems entirely lacking

Pino already did this one.

*Tier 3*

*Tier 2*

Starting a new thread for MERGED in order..

New entry for un-merged and reason why.

I completely understand your frustration. It has been a long while since we had working appimages for you. Create those bash scripts and I will either integrate them into my system or the current kmymoney way.
Scarlett

My current code is at https://anongit.kde.org/sysadmin/appimage-tooling

Sorry, grumpy warning...

@TheAssassin yes, I was using them for non KDE applications as well.
@ everyone - I guess what I am saying here is I am more than happy to use my existing tools ( ruby ) and help with appimages. I just simply don't have the time to learn python right now. Not to say this is never going to happen, just not now.
Cheers,
Scarlett

Sorry last year was madness for me,
With that said, I have more time now.
I failed miserably with craft even getting anything to build, much less integration with the appimage stuff. Python hates me.
I have resurrected my work from BS appimages. I am more than happy to use it on binary factory to produce appimages relatively easily , and will even help with the scripts. I am very close to ready should it be decided this is an acceptable solution.
Cheers, Scarlett

I still need confirmation on unstable verse testing @sitter @bshah @jriddell

Ok - I am seeing this enough to warrant a comment - I am seeing quite a few changelog entries for 5.51 release as xenial - I thought unstable was bionic?

So far all are failing the lintcmake test. I need help as I can't sort out what needs to be done to fix them. Help please.

pushed.
Looks like there is a que. I am starving and must eat. Will check on it when I get back.

Ready to merge, but when you say good version number... this is probably not one? or is it? extra-cmake-modules (5.50.0-1~) UNRELEASED; urgency=medium I think unstable is 5.51?

Well it seems I made this commit. 3b22cbd ("Add qttools5-dev-tools to ECM for ECMPoQmTools.cmake", 2017-12-08)
It is not brought in by shlibs:Depends so unless something changed in ECMPlQmlTools.cmake I think it may still be needed? I think this requires more investigation.

In T8586#164165, @jriddell wrote:

Diff compared to master is:

-Depends: qttools5-dev-tools, ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}

any reason for that?

Ah ha, yes I forgot I have https://cgit.kde.org/appimage-packaging.git/ I started working on appimages for binary-factory a long time ago but with conflicts with $job I stopped. I am resurrecting that work and kontact is the lucky recipient of being my test application. Hopefully Ben will let me use my existing work rather than start from scratch.

ECM https://packaging.neon.kde.org/kde/extra-cmake-modules.git/commit/?h=Neon/unstable_merge

Hello, just letting you know, I am working on this. Where do you keep the Flatpak recipe? I am only wondering because I do not wish to use the github appimages repos. That was old Blue Systems work and this is free time work, I no longer do appimages for BS. Could we create a packaging/ folder? Thanks

Hi - how important is it ? My plate is really quite full and I don't see being able to get this into debian as it will be going away rather quickly with next kdevelop release..

ok did all that and not seeing jobs still. But on another note - the first one I tried I have changelog madness. How do we want to handle those?

Oh. I totally misunderstood the original instructions. Re-working my script. Thanks.

Ok, branches created. Ran job_updater and.. no jobs. I missed a step somewhere :) Is there a config file I need to update?

Hi, I just saw this. Oops. That is old, but I reckon it still works. I can test and fix it up!

This is complete for debian. On hold for bionic.

Well, I am willing to help out. Just holler if you need/want me to help in anyway on this.

Darn editor.. sorry

All green, please review. Also someone with a tablet should test..

This was pushed, seems I don't know how to do the commit to trigger the close.

This should be all set, due to @bshah fixing my test. thank you! Ben verified that the size on disk shrunk by epic proportions.

This has now been added to digikam.

All branches created and built.

Done

Please review and I will enable all releases