plasma-mobile_6.3.0

Hi @coucouf !

I have a few questions/notes:

• routine-update-cmake-deps doesn't seem to be able to do its thing within a repository without source code. AFAIK all the repositories of the team include debian/ folder only, then... am I missing something? BTW, a script intended to update build-deps after CMakeLists.txt should IMO raise something more severe than a warning when CMakeLists.txt isn't found... I almost missed this one, then I double-checked because it seemed strange for a major release not to bump any build-dep...

plasma-mobile$ ~/pkg-kde-dev-scripts/routine/routine-update-cmake-deps 
[WARNING] File: plasma-mobile-6.3.0/CMakeLists.txt not found, not cmake based project?
[INFO] Updating control file from reqs:

[WARNING] cannot parse package relationship "", returning it raw
[WARNING] cannot parse package relationship "", returning it raw
[WARNING] cannot parse package relationship "${misc:Depends}", returning it raw
[WARNING] cannot parse package relationship "${qml6:Depends}", returning it raw
[WARNING] cannot parse package relationship "${shlibs:Depends}", returning it raw
[WARNING] cannot parse package relationship "", returning it raw
[WARNING] cannot parse package relationship "", returning it raw
[WARNING] cannot parse package relationship "${misc:Depends}", returning it raw
[WARNING] cannot parse package relationship "", returning it raw
diff --git a/debian/changelog b/debian/changelog
index a9f7aa740..27175ef05 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,9 @@
plasma-mobile (6.3.0-1) [-UNRELEASED;-]{+unstable;+} urgency=medium

[-  [ Marco Mattiolo ]-]
  * New upstream release (6.3.0).
  * d/watch: set pgpsigurlmangle option for uscan to check uptream signatures.

 -- [-Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>-]{+Marco Mattiolo <marco.mattiolo@hotmail.it>+}  Sat, 15 Feb 2025 [-11:16:37-]{+12:07:00+} +0100

plasma-mobile (6.2.5-1) unstable; urgency=medium

• CI fails with a strange error about verifying upstream tarball's signature. I see plasma-desktop has the same issue, is there some more context about this? Are we just ignoring it for the moment? Do we have another way to test the packaging (I mean the CI test section, the package itself I've built and tested locally)?

ERROR:root:SOP Error NO_SIGNATURE (3): No Valid Signature found
uscan: error: sopv verify ../plasma-mobile-6.3.0.tar.xz.sig debian/upstream/signing-key.asc subprocess returned exit status 3
Could not find any location for plasma-mobile_6.3.0.orig.tar.*

• trying to troubleshoot the previous point, I've aligned d/watch with the one from plasma-desktop. At the end, pipeline is still failing, but I think it's worth keeping it like in plasma-desktop