[02:53] <IrcsomeBot> <RikMills> https://apps.kde.org/en-gb/arianna/
[02:55] <IrcsomeBot> <myfenris> wished i can join the akademy (re @IrcsomeBot: <RikMills> https://akademy.kde.org/2024/program/)
[02:56] <IrcsomeBot> <myfenris> its already in snap right? (re @RikMills: https://apps.kde.org/en-gb/arianna/)
[10:48] <IrcsomeBot> <RikMills> @sgmoore sorry about the confusion on the purpose fix. my fault
[10:49] <IrcsomeBot> <sgmoore> no worries
[10:57] <IrcsomeBot> <RikMills> @myfenris found a useful thing. withy the new sources list file format, if you add a line before the Signed by: line of Trusted: yes, that skips the need for the signature. Apt still notices, but carries on anyway
[10:57] <IrcsomeBot> <RikMills> @myfenris found a useful thing. with the new sources list file format, if you add a line before the Signed by: line of Trusted: yes, that skips the need for the signature. Apt still notices, but carries on anyway
[10:58] <IrcsomeBot> <myfenris> thanks for sharing .. but if we maintain the current signature should not be a problem too right? (re @RikMills: @myfenris found a useful thing. with the new sources list file format, if you add a line before the Signed by: line of Trusted: yes, that skips the need for the signature. Apt still notices, but carries on anyway)
[10:59] <IrcsomeBot> <RikMills> You and also add a Enabled: yes or Enabled: no line to enable/disable a ppa
[10:59] <IrcsomeBot> <RikMills> eventually it won't be, once LP admins update things (re @myfenris: thanks for sharing .. but if we maintain the current signature should not be a problem too right?)
[10:59] <IrcsomeBot> <RikMills> You can also add a Enabled: yes or Enabled: no line to enable/disable a ppa
[11:00] <IrcsomeBot> <RikMills> I mean eventually the new sig will take over
[11:01] <IrcsomeBot> <RikMills> obviously if you have already added the new one as you have, that will stick
[11:04] <IrcsomeBot> <myfenris> yups this one already noted before (re @RikMills: You can also add a Enabled: yes or Enabled: no line to enable/disable a ppa)
[12:32] <BluesKaj> Hi all
[19:52] <santa_> hi everyone
[19:54] <santa_> RikMills: so purpose is installing some extra files in debian because they have the kaccounts build dep, and these files are conflicting between the kf5 and kf6 version, is that correct?
[19:54] <IrcsomeBot> <sgmoore> Correct
[19:55] <IrcsomeBot> <sgmoore> And hi
[19:55] <santa_> hi sgmoore 
[19:55] <santa_> so ... do you know the file paths of the conflicting files?
[19:56] <IrcsomeBot> <sgmoore> Not at computer,  just know they were service files, one was google
[19:57] <santa_> ok, if you know the files let me know
[19:57] <santa_> so I guess the Breaks/Replaces are "correct" in debian, BUT:
[19:58] <santa_> the kde objective was making kf5 and kf6 co-installable
[19:58] <IrcsomeBot> <sgmoore> /usr/share/accounts/services/kde/nextcloud-upload.service
[19:58] <IrcsomeBot> <sgmoore> /usr/share/accounts/services/kde/google-youtube.service
[19:59] <santa_> aha
[19:59] <IrcsomeBot> <sgmoore> So a bug needs filed upstream then
[19:59] <santa_> so maybe the missed this issue in kde
[19:59] <IrcsomeBot> <sgmoore> Yeah
[19:59] <santa_> indeed, that's what I was going to say
[20:00] <IrcsomeBot> <sgmoore> I go in for surgery in the morning so taking it easy for rest of today if you could file please
[20:00] <santa_> ack
[20:00] <santa_> just for the record: https://community.kde.org/Frameworks/6.0_Release_notes
[20:01] <santa_> there's a "Coinstallability" section there ↑
[20:02] <IrcsomeBot> <sgmoore> Yup, they definitely missed the purpose failure there
[20:43] <santa_> https://bugs.kde.org/show_bug.cgi?id=490471
[20:43] -ubottu:#kubuntu-devel- KDE bug 490471 in frameworks-purpose "Conflicting files between purpose kf5 and kf6" [Normal, Unconfirmed]
[23:04] <Eickmeyer> dpkg-divert as a temp solution?