Am Mittwoch, 22. April 2020, 10:25:59 schrieb Luigi Toscano:
> Would it make sense to bump some calligra requirements (which declares Qt
> 5.3 as the minimum Qt version)?
That would of course not help if somebody wants to build it with (even
slighly) older KDE Frameworks, and it seems a bit
Am Mittwoch, 22. April 2020, 08:46:21 schrieb Dag:
> On 21-04-2020 20:06, Wolfgang Bauer wrote:
> > Am Mittwoch, 8. April 2020, 12:33:43 schrieb Dag:
> >> Source can be found here:
> >> http://download.kde.org/unstable/calligra/calligra-3.1.90.tar.xz
> >
>
Am Mittwoch, 8. April 2020, 12:33:43 schrieb Dag:
> Source can be found here:
> http://download.kde.org/unstable/calligra/calligra-3.1.90.tar.xz
Is is intentional that the english docs are not built/installed anymore (they
are marked as "Not maintained"), but translated ones now are included and
Am Donnerstag, 3. Oktober 2019, 14:11:39 schrieb Jonathan Riddell:
> It's up to distros what they do with our software, we can't control them,
> but we can make a clear recommendation. And once the dependencies no
> longer exist in a supported way we should be responsible for the
> applications
Am Donnerstag, 7. März 2019, 09:16:55 schrieb Wolfgang Bauer:
> I uploaded a fix to phabricator:
> https://phabricator.kde.org/D19581
It has been pushed with commit a08e2ebd589fc3faaa4b79f48fc7ff964e13cad3 .
Can we have another respin please?
Thank you.
Kind Regards,
Wolfgang
Am Mittwoch, 6. März 2019, 22:41:57 schrieb David Faure:
> On mercredi 6 mars 2019 13:31:13 CET Andreas Sturmlechner wrote:
> > On Sat, 2 Mar 2019 at 16:48, David Faure wrote:
> > > Dear packagers,
> > >
> > > KDE Frameworks 5.56.0 has been uploaded to the usual place.
> >
> >
Am Sonntag, 25. November 2018, 23:15:29 schrieb Luca Beltrame:
> In data domenica 25 novembre 2018 22:48:35 CET, Alexander Semke ha scritto:
> > I don't see such a license file in Cantor, neither. Should we also add it
> > here?
>
> Yes, definitely.
But cantor already has a file named "'COPYING"
JFYI:
I did manage to fix the multisegmentkio plugin in time (before the RC
actually), and it wasn't actually a problem in the plugin itself:
https://cgit.kde.org/kget.git/commit/?id=60ecb4405e4175466073c5ae86894452ca7e9df5
And afterwards (as I expected ;-) ) the metalink plugin started to work
Am Sonntag, 12. November 2017, 11:37:55 schrieb Albert Astals Cid:
> And not used by more than a handful of people, so bugs are present (as the
> rest of the thread shows)
Well, regarding the metalink plugin: I meanwhile noticed that the problem is
already there in the KDE4 version, if you
Am Donnerstag, 9. November 2017, 20:58:33 schrieb Andrius Štikonas:
> repo-metadata repository needs to be updated as well.
I suppose you mean sysadmin/repo-metadata.git?
I have no idea what I should change there though...
I did adjust kde-build-metadata.git meanwhile.
Kind Regards,
Wolfgang
Am Donnerstag, 9. November 2017, 21:01:16 schrieb Christoph Feck:
> Given that option 1 is not any better than option 2, I am all for
> merging the exising work branch to 'master' (today or tomorrow). Should
> we not be able to stabilize it, distributions could continue to release
> the 17.08.3
Am Donnerstag, 9. November 2017 schrieb Heiko Becker:
> Ah, I only tested with kde.org and download.qt.io which both use
> MirrorBrain (iirc) and provide metalinks. If I disable the Metalink
> plugin downloads from both sites actually start.
Thanks for this information!
I'll look at it and try to
Am Donnerstag, 9. November 2017, 17:33:36 schrieb Heiko Becker:
> I just gave the current frameworks branch a try and I can't get it to
> download anything, even with the multisegment plugin disabled. The file
> is added to the list, but the download never starts.
Hm, it worked fine in my
So, are there any remaining objections if I merge frameworks to master today?
(Or will somebody else do it? I already tried locally and there are no
conflicts...)
I committed most of my fixes yesterday.
One is still in review though:
https://phabricator.kde.org/D8730
And I still have to commit
Am Mittwoch, 8. November 2017, 16:54:12 schrieben Sie:
> About merging the kf5 work branch to master that late (we've had more than
> two years to do the porting), I'm honestly not very thrilled about it.
Yes, and in those two years it has been ported and work has been done in the
frameworks
Hi all!
I spent some time during the last weeks on the KF5 port of kget to fix
problems I noticed, e.g. opening the transfer history crashed, the bittorrent
plugin wasn't built at all and needed some fixes to actually compile, disabled
plugins disappeared from the settings, some incorrect QUrl
Am Mittwoch, 22. Februar 2017, 22:01:01 schrieb Martin Gräßlin:
> The attack surface is exactly the same as any other X application. It's
> X itself which will make this exploitable.
Yes, obviously, and that's clear to me too.
I won't comment on the rest, because it's not specific to kfloppy as
Am Mittwoch, 22. Februar 2017, 22:42:01 schrieb Martin Steigerwald:
> Am Mittwoch, 22. Februar 2017, 20:07:09 CET schrieb Wolfgang Bauer:
> > Am Mittwoch, 22. Februar 2017, 01:07:42 schrieb Boudhayan Gupta:
> > > I really don't see why this has to exist. Anyone who uses floppies
Am Dienstag, 21. Februar 2017, 18:55:00 schrieb Nicolás Alvarez:
> > On Feb 15, 2017, at 17:58, Wolfgang Bauer <wba...@tmo.at> wrote:
> >
> > Am Mittwoch, 15. Februar 2017, 22:21:19 schrieb Martin Gräßlin:
> >> Please do not consider starting a GUI application a
Am Mittwoch, 22. Februar 2017, 01:07:42 schrieb Boudhayan Gupta:
> I really don't see why this has to exist. Anyone who uses floppies in
> this day and age knows how to use a command line to do a low level
> format.
Maybe, but using a GUI is more comfortable and you don't have to remember
which
Am Donnerstag, 16. Februar 2017, 00:34:38 schrieb Luigi Toscano:
> Really, please, let's try to find another solution than running as root.
Yes, of course..
I'd like to clarify a bit though:
I did (and do) prefer the kauth solution.
I only considered offering to restart the application as root
Am Mittwoch, 15. Februar 2017, 21:55:12 schrieb Boudhayan Gupta:
> What would you say about using Solid to probe floppy drives? I think
> Solid already has the necessary hooks, but if it doesn't, we can add
> them.
Sounds interesting.
Thanks for the suggestion.
I will have a look at that too.
On 11 February 2017 at 13:44, Jonathan Riddell wrote:
> I recommend KFloppy be removed from Applications releases. It
> couldn't find my floppy drive and when I hacked the code to tell it
> where to look it depended on an external tool fdformat which didn't
> work anyway.
Am Sonntag, 15. November 2015, 14:30:30 schrieb Rolf Eike Beer:
> > Well, I am still using floppy disks (and KFloppy) regularly, and would be
> > a
> > bit disappointed to see it disappear. So I'd volunteer to maintain it if
> > necessary.
>
> Congrats, you have become father. Please subscribe to
could upload the patch to
Reviewboard (or commit it) immediately...
- Wolfgang Bauer
On Nov. 12, 2015, 3:42 nachm., Heiko Becker wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboa
25 matches
Mail list logo