[06:37] πŸ‘Œthen can give a try to prove the theory ☺️ [07:00] will wait till everything finished then can give a try .. [10:45] I have forked/renamed sources for kirigami-addons, kwayland and libkscreen preety much done if we need them to ease landing of Plasma 6 [10:46] nice, thanks [10:47] kaccounts-integration, and signond may have been sidestepped by not building kf6-purpose with option kaccounts I think [10:47] as long as we are happy with not having the online accounts KCM in plasma for a bit [10:48] @RikMills I am going to have a pile of uploads for you later. SRU's I need to fix version and they never got uploaded, stupid packageset and my inability to do my job. [10:48] sure [10:49] Yeah, we have enough things to make sure works without adding that painful stack. [10:49] on plasma 6 ibqaccessibilityclient in ubuntu now has a duel build for Qt5 and Qt6, so that is not a problem here [10:50] I think bismuth can be killed as it will be useless for plasma 6 and seems no upstream port [10:51] As far as the online accounts KCM, my primary use case was GDrive integration, and that has been unreliable for years. [10:52] Yeah, we dropped kio-gdrive off the default install a while back [10:53] For an interim release I think we can sacrifice a few things to get plasma in [10:54] FYi, Debian have only plasma-workspace and plasma-desktop left to package, and I think they are WIP [10:55] Yeah, I think arraybolt is doing the copyright for Deltaone on those. [10:55] Rather him than me! :D [10:56] Right?!?! lol [11:44] Hi all [11:53] @RikMills https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/angelfish/+ref/kubuntu_noble_archive angelfish is ready. [11:59] I have been asking for our packageset to be updated for upload rights for months now and continued to be ignored. It just occurred to me that I am not going to be able to upload much of anything with qt6 stuff. I am feeling a bit defeated. [12:00] gbp-archive only works for things that are UNRELEASED in the changelog (re @sgmoore: @RikMills https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/angelfish/+ref/kubuntu_noble_archive angelfish is ready.) [12:01] gbp-archive worked fine. It got rejected because the sighner doesn't have rights to upload [12:01] story of my life [12:02] I mean it now has noble, so I can't use gbp-archive to prepare the upload (re @sgmoore: gbp-archive worked fine. It got rejected because the sighner doesn't have rights to upload) [12:03] oh, Simon never complained about that. I will remove the noble and tag. Apologies. [12:04] Yeah, it can be worked around, but it is a faff [12:04] he probably doesn't use ka [12:05] true [12:07] Fixed [12:11] @RikMills also going to need oracular uploads.. :( will fix the repo. [12:13] is profile angelfish /usr/bin/angelfish flags=(unconfined) really all that is needed for the profile? [12:14] Well I had it more restrictive, but things didn't work. So I looked at all the gnome apps canonical did and that is what they had... [12:15] Nice. :) [12:15] lol [12:17] angelfish uploaded [12:18] thank you, oracular archive is ready. [12:25] KF6? (re @sgmoore: thank you, oracular archive is ready.) [12:27] kf6 ppa doesnt have pub key [12:30] It does, but the weaker one is now rejected in oracular (re @myfenris: kf6 ppa doesnt have pub key) [12:32] uploaded (re @sgmoore: thank you, oracular archive is ready.) [12:41] @fenris edit the ppas source file in /etc/apt/sources.list.d [12:41] owh its rejected .. (re @RikMills: It does, but the weaker one is now rejected in oracular) [12:42] W: GPG error: https://ppa.launchpadcontent.net/kubuntu-ppa/staging-frameworks6/ubuntu oracular InRelease: The following signatures were invalid: E4DFEC907DEDA4B8A670E8042836CB0A8AC93F7A (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 17FB29293721A2CD [12:42] E: The repository 'https://ppa.launchpadcontent.net/kubuntu-ppa/staging-frameworks6/ubuntu oracular InRelease' is not signed. [12:43] to which key to edit? (re @RikMills: @fenris edit the ppas source file in /etc/apt/sources.list.d) [12:44] replace the pgp signed bloc with this: (re @myfenris: to which key to edit?) [12:46] https://irc-attachments.kde.org/87af4fda/ppasig.txt [12:46] make sure to keep the one space indent [12:46] launchpad admins are working to fix this, but it is taking a while [12:47] I ran into this a few days ago, which is why I know how to work around it [12:48] thanks [12:48] but it would not trigger any update/upgrade :) [12:49] temp workaround works (re @RikMills: I ran into this a few days ago, which is why I know how to work around it) [12:51] on purpose? or need to wait for the plasma6 too (re @myfenris: but it would not trigger any update/upgrade :)) [12:51] on purpose? or need to wait for the plasma6 packages too (re @myfenris: but it would not trigger any update/upgrade :)) [12:52] If you have any frameworks kf6 packages installed, they would upgrade (what is built so far) (re @myfenris: on purpose? or need to wait for the plasma6 packages too) [12:52] If you don't have any installed, then it will do nothing [12:53] for sure i don't have any kf6 πŸ™ˆ [12:53] so need to install separately ... co-exist kf5 n kf6? [12:54] /me blurry [12:54] kf5 and kf6 frameworks can live side by side [12:54] owh [12:54] same goes to plasma6 later? [12:54] it is plasma that won't be able to [12:55] owh i see (re @RikMills: it is plasma that won't be able to) [12:55] which makes it difficult to land [12:55] πŸ™ˆ (re @RikMills: which makes it difficult to land) [12:56] because a lot of 3rd party packages have decide to depnd on parts of plasma 5 [12:56] so hows neon does that ? remove the 3rd party packages? [12:56] they don't care if they break 3rd party things [12:56] owh [12:57] so kubuntu will removed the 3rd party thingy or whats the workaround? [12:59] in order of preference a) get them ported to Qt6/Kf5 if possible, (b) make a new source of the plasma 5 package they depend on so it can co-exist with the plasma 6 one, (c) remove it (re @myfenris: so kubuntu will removed the 3rd party thingy or whats the workaround?) [13:05] The team need to decide it I guess? Is it's the 3rd party has long list or crucial apps to kde/kubuntu user's? Can't we choose (c) 1st while they do (a) & (b)? [13:05] Just my 2 cent [13:08] For some. Some however are part of other flavours core packages. e.g. ukiu packages that are part of ubuntu-kylin [13:09] I see , noted .. they acknowledged about this right? (re @RikMills: For some. Some however are part of other flavours core packages. e.g. ukiu packages that are part of ubuntu-kylin) [13:10] Yes. They don't have any QT6 port in the pipeline [13:10] so looking like (b) [13:11] 🫣 (re @RikMills: Yes. They don't have any QT6 port in the pipeline) [13:26] @RikMills , does experimental ppa ok to test? [13:27] or until the discover solved ? [13:27] No, it is missing plasma-workspace and plasma-desktop (re @myfenris: @RikMills , does experimental ppa ok to test?) [13:27] it will break all the things... [13:28] 🫑 (re @RikMills: it will break all the things...) [13:38] need to wait for this right? (re @RikMills: FYi, Debian have only plasma-workspace and plasma-desktop left to package, and I think they are WIP) [13:40] At least that. Maybe even longer, as things like dependencies may need fixing. [13:40] We will say when we think testing is ok [13:40] @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/falkon noble ready [13:41] btw, do dolphin/kio has similar to this : https://www.omgubuntu.co.uk/2024/04/set-up-onedrive-file-access-in-ubuntu [13:41] Not ware of it [13:41] *aware [13:41] ok (re @sgmoore: @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/falkon noble ready) [13:45] and so is oracular now [13:50] @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ghostwriter noble is ready [13:53] @sgmoore I guess oracular uploads as well [13:54] yeah oracular as well please [14:03] @sgmoore falkon in oracular archive is 24.05.1-1 but your upload is 24.01.75-1build6 [14:10] Oh, must have had a new release in Debian. How do I do that sync thing? [14:11] ka-sync-archive [14:11] OK thanks [14:11] then commit the changed files [14:42] @RikMills falkon fixed I hope... what a mess, I guess I have to PR that in debian? I am not sure they have the same userns issue as us though... [14:43] They didn't when this first came up [14:44] I reckon they still don't as the maintainer seems pretty active. [14:45] oh well, now I know to sync before anything haha. thank you [14:48] @sgmoore am I missing something? oracular branches are still at 24.01.75 [14:48] umm [14:51] I am clearly missing something. it is syncing to noble. /me checks ka-sync-archive flags [14:52] Distribution %s is not either 'debian' or 'ubuntu' guess I need to update something [14:53] also long as your ka knows that oracular is the dev branch, it should sync that [14:54] is your ka from git or a ppa? [14:55] How do I tell it that? updating ka-metadata didn't help. hmm not sure on this lappy. [14:56] do which ka-sync-archive [14:57] looks like I built the deb myself from git. But that was awhile ago, building new deb with the 5 million changes lol [14:59] I'm doing Option 3 for here: https://git.launchpad.net/ka/tree/doc/source/INSTALL.rst [15:00] so I just have to do a git pull in ~/ka/ to be up to date with git master [15:00] I'm doing Option 3 from here: https://git.launchpad.net/ka/tree/doc/source/INSTALL.rst [15:01] nice! will set that up to avoid cases such as today. [15:01] in there is conf/defaultrc:ubuntu-unstable-name = oracular [15:02] which I think is where ka-sync-archive gets its default [15:02] k [15:03] if your run git master, you can also bug santa_ about fixes and features needed πŸ˜‰ [15:10] ok... so now that worked lol, we have a kf6 package... we aren't ready for that I reckon. [15:11] or are we? [15:12] If someone wants to go to the trouble of converting the packaging, and depends are available, then we could [15:12] it looks like it synced experiemental. I am so confused. [15:13] Wait... maybe I synced that [15:13] So many packages to remember [15:13] ok so I just need to re-do my apparmor stuff and call it a day on this one. [15:15] :) [15:43] @RikMills falkon oracular ready [15:47] Going to have to do this manually, as the dingbat of a debian developer (not in qt/kde team) who maintains falkon refuses to use the release tars (re @sgmoore: @RikMills falkon oracular ready) [15:48] yeah he uses very odd versions too. it is a pain [15:56] uploaded (re @sgmoore: @RikMills falkon oracular ready) [16:02] Better set an alarm on my phone for session 2 [16:02] Of the flavour sync [16:03] Well this sync thing was a very valuable lesson for today. Kmail had changes too. [16:03] Yeah me too [16:04] @sgmoore falkon FTBFS [16:04] cp debian/falkon-apparmor debian/falkon/etc/apparmor.d/usr.bin.falkon [16:04] cp: cannot stat 'debian/falkon-apparmor': No such file or directory [16:05] Oops [16:06] Pushed missing files @RikMills sorry bout that [16:07] It happens [16:08] but needs a changelog (re @sgmoore: Pushed missing files @RikMills sorry bout that) [16:08] K [16:09] Pushed [16:12] and uploaded === NotEickmeyer is now known as Eickmeyer [18:07] @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-welcome both noble and oracular ready. [18:22] oracular barch is versioned 5.27.11-0ubuntu3.1 (re @sgmoore: @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-welcome both noble and oracular ready.) [18:23] oracular branch is versioned 5.27.11-0ubuntu3.1 (re @sgmoore: @RikMills git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-welcome both noble and oracular ready.) [18:23] should be ubuntu4 [18:23] fixing [18:23] Bah, sorry [18:25] np [18:29] uploaded [18:47] sorry , where can i monitor the debian wip for plasma-desktop & plasma-workspace ; [18:50] https://salsa.debian.org/qt-kde-team/kde/plasma-workspace/-/tree/debian/experimental?ref_type=heads [18:50] https://salsa.debian.org/qt-kde-team/kde/plasma-desktop/-/tree/debian/experimental?ref_type=heads [18:50] thanks ... [19:06] desktop - error at compiling , workspace - error with dependencies ... am i read it correctly? [19:07] i read it at build jobs [19:10] Ignore that. That is just an automatic ci build which is going to fail on dependencies and other things. [19:11] Real things happen when it is uploaded to experimental repo [19:11] sure ... just refreshing my CI knowledge [19:16] its rusty 😏