Re: KDE Gear projects with failing CI (master) (27 March 2024)
On Mittwoch, 27. März 2024 23:33:52 CET Albert Astals Cid wrote: > kleopatra - NEW > * https://invent.kde.org/pim/kleopatra/-/pipelines/645399 > * flatpak fails >* It wants an unreleased version of KPim6Mime but the flatpak manifest > says it should work with release/24.02 one of the two needs fixing Already fixed by Tobias: https://invent.kde.org/pim/kleopatra/-/merge_requests/162 Regards, Ingo signature.asc Description: This is a digitally signed message part.
signon-kwallet-extension
Hi all, Due to recent updates in SUSE around signond, i've just had to remove signond-libs-devel from our SUSE Qt 5.15 images. This is due to signond now being built with Qt 6 - and therefore being incompatible with Qt 5. Looking in signon-kwallet-extension though I see it is still Qt 5 code that is unported. It will therefore lose CI coverage support on LInux from today onward until it is ported to Qt 6. Cheers, Ben
Re: signon-kwallet-extension
On 3/28/24 13:04, Ben Cooksley wrote: Hi all, Due to recent updates in SUSE around signond, i've just had to remove signond-libs-devel from our SUSE Qt 5.15 images. This is due to signond now being built with Qt 6 - and therefore being incompatible with Qt 5. Looking in signon-kwallet-extension though I see it is still Qt 5 code that is unported. It will therefore lose CI coverage support on LInux from today onward until it is ported to Qt 6. Cheers, Ben Hi, signon-kwallet-extension is ported to Qt6. It's a bit special in the sense that it must be built against the same Qt version signond is built against, and since that can be either Qt5 or Qt6 signon-kwallet-extension still supports both. For practical intents and purposes it's only the Qt6 build that matters though. At the moment signon-kwallet-extension doesn't have Qt6 CI. This was due to signon and friends not being available in Qt6 CI, but it seem to be time to revisit that now. Cheers Nico
Re: KDE Gear projects with failing CI (master) (27 March 2024)
On Mittwoch, 27. März 2024 23:33:52 CET Albert Astals Cid wrote: > kirigami-gallery - NEW > * https://invent.kde.org/sdk/kirigami-gallery/-/pipelines/645400 > * Android build fails >* Similar problem to the one in kirigami being discussed in the > frameworks mailing list Asked in the Kirigami channel about remaining blockers for merging the existing and seemingly working kf6 branch. That would be more hiding than solving the problem here, but it's necessary longer term anyway. Regards, Volker signature.asc Description: This is a digitally signed message part.
Re: kio-gdrive changes needed to conform to new Google requirements
Hi everyone, The board has gotten a reminder about this again and that the deadline is looming in 21 days. On Fri, Feb 16, 2024 at 3:07 PM Carl Schwan wrote: > I can probably help a bit with e.g. doing the video but starting the process > needs to be done by someone who has access to the google account (probably the > board). Awesome. Thank you. I can sit down with you and do that part. Poke me when you have time please. Cheers Lydia -- Lydia Pintscher - https://lydiapintscher.de - WD:Q18016466 KDE e.V. Board of Directors http://kde.org - http://open-advice.org
Fwd: kio-gdrive changes needed to conform to new Google requirements
and once again i forget to send direct to the ML. From: Björn Strömberg Date: Fri, Mar 29, 2024 at 6:51 AM Subject: Re: kio-gdrive changes needed to conform to new Google requirements To: Carl Schwan this is exactly the reason you don't use google for anything that you care about, they love to lure every one in to depend on them, then they change the rules when they get enough users, many of who would never accept the rules they change to if they had gotten them straight up front. ... classic bait and switch ... personally i would say f google, and mark the module as dead/defect due to google changed rules. if there really is someone who really needs it, they will pull it back through the invent process and becomes the maintainer of it. just my 0.02€ /Björn ps. yes I know I'm writing this from a gmail account... it's one of the main reason for the knowledge of the constant baiting and switching from google... On Fri, Feb 16, 2024 at 4:07 PM Carl Schwan wrote: > On Thursday, February 15, 2024 9:53:39 PM CET Nate Graham wrote: > > Hello folks, > > The KDE e.V. board received an email from Google about changes required > > for kio-gdrive. I've opened an Issue about it at > > https://invent.kde.org/network/kio-gdrive/-/issues/1 with more details. > > To my knowledge, kio-gdrive is maintainerless, so we're in need of a > > kind soul who will volunteer to make any needed changes to the software. > > > > :) Any takers? > > I just looked into it and I don't want to be pesimistic but it sounds like > Google is shutting us down. > > We are currently the 'drive' scope which allow us to access all the files > of > the users. This is the scope that google doesn't want us to use anymore. > > The alternatives proposed by google are: > > - drive.appdata: this allow only to access an app specific folder to store > app > specific data. It's fine if you want to sync app data between an app on > multiple > platforms but not much more. > > - drive.file: this is more a file picker API where the user can select a > file and > allow the application to use it. Again not helpful for a sync client > > See https://developers.google.com/drive/api/guides/api-specific-auth > > So we need to submit for re-verification and hope they allow us to > continue > using the API. We seen to be an allowed use-case according to their doc: > > > https://developers.google.com/workspace/workspace-api-user-data-developer-policy#appropriate_access_to_and_use_ofs > > But it still requires some non-technical work: > > - Create a video of the gdrive workflow including the login and oauth > process > - An annual security assessment (not sure how hard it is to pass and > hopefully > it is free...) > > See: > > https://support.google.com/cloud/answer/13464321?sjid=5292936327783040555-EU# > https://support.google.com/cloud/answer/13465431 > > I can probably help a bit with e.g. doing the video but starting the > process > needs to be done by someone who has access to the google account (probably > the > board). > > Cheers, > Carl > > > > > Nate > > > > >
Fwd: kio-gdrive changes needed to conform to new Google requirements
same as last mail, forgot to send to ML From: Björn Strömberg Date: Fri, Mar 29, 2024 at 7:01 AM Subject: Re: kio-gdrive changes needed to conform to new Google requirements To: Lydia Pintscher Hello Lydia Pintscher, sounds great that someone in the KDE board of directors is down here, i got an idea for you guys! google change the rules on gdrive! then the board will start figuring out how we're going to replace gdrive with kdrive! a solution that looks like gdrive from the users perspective, and is stored on a selfhosted and/or community hosted solution! best way to handle bullies like google is to replace them with something better! selfhosted or community hosted solutions are better than google 7 days a week... with kind easter regards from Sweden /Björn On Thu, Mar 28, 2024 at 8:07 PM Lydia Pintscher wrote: > Hi everyone, > > The board has gotten a reminder about this again and that the deadline > is looming in 21 days. > > On Fri, Feb 16, 2024 at 3:07 PM Carl Schwan wrote: > > I can probably help a bit with e.g. doing the video but starting the > process > > needs to be done by someone who has access to the google account > (probably the > > board). > > Awesome. Thank you. I can sit down with you and do that part. Poke me > when you have time please. > > > Cheers > Lydia > > -- > Lydia Pintscher - https://lydiapintscher.de - WD:Q18016466 > KDE e.V. Board of Directors > http://kde.org - http://open-advice.org >
