Re: [Kde-pim] The Future or KDE PIM Releases

Hey, > What's meant by "KDE Accounts"? well we also had a look into the code. It is a resource that will adds all local users from kde to your kaddressbook. Regards, sandro signature.asc Description: This is a digitally signed message part.

Re: Distros and QtWebEngine

cally superior to any other > thing out there but making that code an acceptable package is another thing. > > So basically what I'm trying to say is: don't expect us down streamers to > easily package QtWebEngine soon, if we ever get to it. > > I'm really sor

Re: Alternative to QDateTime::isDateOnly ?

o know when we save/load from ical f.ex. normally nobody sets bithdays with time, but rfc allows it. * for a valid time you need for sure a valid timezone otherwise a time doesn't make sense. Regads, sandro -- Sandro Knauß Software Developer Kolab Systems AG Zürich, Switzerland e: kna.

Replacement for KDateTime

Hello, the kdepim is discussing how we can replace KDateTime inside kdepim (primarly kcalcore) . There are some issues, why we can't replace it simply with QDateTime. * indivual timezone support, this is something that we need when parsing ical and have no known timezone information. I havn't

Re: Replacement for KDateTime

Hey John, > OK, I had a quick look at this and to do it in Qt and it wasn't actually > that hard. You can see the result at: > > https://codereview.qt-project.org/#/c/122750/ > > This should support the full set of VTIMEZONE rules, have a look and let me > know if not. > > I'm not sure if it wi

Re: [Kde-pim] PIM dependency metadata

Hey, > There are a couple of issues, namely: > a) For some reason it depends on plasma-workspace - this seems > completely wrong to me. Please be careful when adding items to the > dependency chain this was added because of ktimezoned, that is part of plasma-workspace to run tests in kcalccore

Re: [Kde-pim] PIM dependency metadata

Hey, > Yep, this sounds like ktimezoned should move to KF5. > > How are non-plasma users supposed to get correct timezones in e.g. PIM apps > otherwise? non-plamsa users are currently doomed :D Mostly I wanted a happy CI to do the rewrite from KDateTime,KTimezone etc. to theire QT5 replacements

Re: Review Request 129339: Allow building kwalletd against gpgme++ from gpgme 1.7

> On Nov. 5, 2016, 10:39 a.m., Andreas Sturmlechner wrote: > > kwalletd/CMakeLists.txt, line 8 > > > > > > Please do this in reverse logic, same as in the kwallet.git commit you > > are referring to - that means s

Re: Review Request 129339: Allow building kwalletd against gpgme++ from gpgme 1.7

/backend/backendpersisthandler.cpp (line 36) <https://git.reviewboard.kde.org/r/129339/#comment67540> unrelated change? kwalletd/kwalletwizard.cpp (line 43) <https://git.reviewboard.kde.org/r/129339/#comment67539> unrelated change? - Sandro Knauß On Nov. 5, 2016, 9:35 a

Re: Review Request 129339: Allow building kwalletd against gpgme++ from gpgme 1.7

> On Nov. 5, 2016, 10:30 p.m., Sandro Knauß wrote: > > these two changes look unreleaded to the patch. > > Antonio Rojas wrote: > No, these are required because they were pulled indirectly by kdepimlibs' > gpgme++, but not by gpgme's one. Okay I see norma

Re: Review Request 129339: Allow building kwalletd against gpgme++ from gpgme 1.7

for someone else to decide, in my view this > is a nice fix to stay in line with KDE Applications 16.12 neighbourhood, > since the otherwise required kdepimlibs-4 conflicts with the new GpgME++ > bindings... anyway, pretty FEATURE_SUMMARY output is probably secondary. > > Sandro Knauß

Re: Please cleanup your scratch and clone repositories

Moin, > Done. one deleted one created :) I was not that effective. But I'll hopefully can delete the last one within the next days... Best Regards, sandro

Re: libkdav

it is not a Frameworks, and I think we as PIMsters were wrong in pushing this into that namespace. * CI support will come and is already requested :) Best Regards, sandro -- Am Montag, 19. Dezember 2016, 12:29:03 CET schrieb Sandro Knauß: > Hey, > > > > moved Akonadi parts alre

Re: CI Requirements - Lessons Not Learnt?

Hey, > how about some simple rule like "new dependencies every first of the month", > and 1 week notice. For the developer this would mean in the worst case 5 > weeks waiting, which is probably quite a lot. I think this is not necessary. Because sysadmins can comment the dependency bump. I think

Re: Draft Policy: Dependency Changes and CI

Hey, thanks for writing this down! > this month, a heated exchange on kde-core-devel about a dep > change breaking CI has moved us to draft a new policy to better > handle situations like this in the future. Hopefully. The first two paraphrases are okay For me the whole text sounds to bureaucra

Longer holidays Feb-Aug

Hey, just a short notice. From Feb to Aug. I won't be available very much at computer, because I'll do a longer holiday in South France. I'll still will answer mails, but not as fast as currently and I won't nearly do any programming. Best Regards, sandro

Re: Distro integration for Plasma Browser Integration (was: Re: Plasma Browser Integration is in kdereview

Hey, > > What options are possible to distribute extensions via distro packaging? You can package for both browses extensions, that works quite nicely: Here is one I made for Debian and Firefox: https://tracker.debian.org/pkg/firefox-kwallet5 For Chrome the debian Wiki tells, that extensions are

Re: Zanshin is in kdereview

Hey, > 2) the third one (libkdepim) I'm forbidden to link against since it's private API to kdepim (turned into a dumping ground apparently...). > > Obviously, as soon as libkdepim is cleaned up (which I regularly hear it's > supposed to happen) and features are moved in proper frameworks I'll

Re: Zanshin is in kdereview

Hey, > > But I don't see why you are not just link against the relevant parts of > > kdepim and remove the copy. And than tell kdepim that you are using these > > files, so the team can take that into account when touching the files. > > As I mentioned earlier I don't because that is private API

Re: [SECURITY] CVE-2019-7443 (kauth) in kdelibs

Hi, > kdelibs last release was 4.14.35 in August 2017. > > kdelibs is no longer maintained. > > Qt 4 last release was 4.8.7 in May 2015. > > Qt 4 is no longer maintained. > > Our suggestion is to stop using any qt4/kdelibs based software and move to > the future if you're concerned about secur

Re: KDiff3 1.8 release.

Hi, > I uploaded an untagged 1.7.90 version to Debian so it could still make it > in the next Debian release buster (which is supposed to get rid of QT4). > => https://packages.debian.org/buster/kdiff3 ;) > > > Eike is the Debian packaging managed in a repo somewhere? Are you > > > interested

Re: KDE Itinerary in kdereview

Hi, > KDE Itinerary has been moved to kdereview: > > Code: https://invent.kde.org/kde/itinerary > Workboard: https://phabricator.kde.org/project/board/280/query/all/ > > KDE Itinerary is a Kirigami-based mobile application for managing your > itinerary as a timeline, including access to your tra

Re: Gitlab Bugzilla integration

Hey, Great, one missing feature less! > This functionality can be seen in action on > https://invent.kde.org/graphics/digikam/-/commit/7ca7bf03b11ae72842006af8a66 > ed02894a4a605 (note that content posted prior to this being enabled may not > feature links due to caching in Gitlab) The commit us

Re: Kirigami Addons in KDEReview

Hey, any news for kirigami-addons getting out of review? I strongly vote for getting it out of review or at least release a new 0.3. So far I can tell master has a lot improved Date picker, that at least for my usage ( laptop with mouse) I could now use ktrip to select a date and time *yeah*.

Re: XWayland Video Bridge in kdereview

Hey, > First it should go through kdereview, then I'd suggest starting to > release it with Plasma 5.27 in one of the minor releases. I don't > think it's something we have done before but it doesn't add new > dependencies and it has an impact in our product offering which is, > incidentally, froz