bugsie left an un neccsaryly terse response in closing
https://bugs.kde.org/show_bug.cgi?id=484997
I have oveer rulled the closure as default app permissions can be adjusted
in the setup for building flatpak in CI.
kdiff3 will make one or two releases but needs only frameworks. This support
will end in three months. master is qt6 only now.
Apr 20, 2024 8:35:40 PM Ben Cooksley :
> Hi all,
>
> I have just flipped the switch that has moved the CI system over to using Qt
> 6.7 for Linux builds on our SUSE
kdiff3 will make one or two releases but needs only frameworks. This support
will end in three months. master is qt6 only now.
Apr 20, 2024 8:35:40 PM Ben Cooksley :
> Hi all,
>
> I have just flipped the switch that has moved the CI system over to using Qt
> 6.7 for Linux builds on our SUSE
kdiff3 will make one or two releases but needs only frameworks. This support
will end in three months. master is qt6 only now.
Apr 20, 2024 8:35:40 PM Ben Cooksley :
> Hi all,
>
> I have just flipped the switch that has moved the CI system over to using Qt
> 6.7 for Linux builds on our SUSE
Does anyone have insight as to why this is happeing:
/Resources/qml/org/kde/i18n/localeData/libki18nlocaledataqmlplugin.dylib']
succeeded with exit code 0
Library dependency
Does anyone have insight as to why this is happeing:
/Resources/qml/org/kde/i18n/localeData/libki18nlocaledataqmlplugin.dylib']
succeeded with exit code 0
Library dependency
nevermind looking at really old mail I never deleted.
Jan 29, 2024 9:08:13 PM Michael Reeves :
> could someone please inform scrpty that 1.11 is the new kf5 stavble branch.
> 1.10 is no longer being released.
>
> Nov 1, 2023 11:12:29 PM reporter123 (@reporter123) :
>
>
could someone please inform scrpty that 1.11 is the new kf5 stavble branch.
1.10 is no longer being released.
Nov 1, 2023 11:12:29 PM reporter123 (@reporter123) :
>
> *reporter123 pushed to branch 1.10 at reporter123 /
> kdiff3[https://gitlab.com/reporter123/kdiff3]*
>
> *Commits:*
>
> *
>
Kdiff3 has run into a compilation bug in boost-hearders 1.80 on MacOS
std::unary_function and std::binary_function are no longer available in
C++17 and C++20. They can be re-enabled by defining
_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION. They are also marked as
[[deprecated]] in C++11 and
As of two days ago I am getting:
Library dependency
'/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/extragear/kdiff3/archive/Applications/KDE/
kdiff3.app/Contents/Frameworks/libpulse-mainloop-glib.0.dylib' does not
exist
On the MacOS build for kdiff3.
ueprints-kde/-/commit/03023ae74c1273ec06757d56732d39bf9a611c62>
[kdiff3] Fix blacklist syntax
Commit Author
Michael Reeves <https://invent.kde.org/mreeves>
Pipeline #493762
<https://invent.kde.org/packaging/craft-blueprints-kde/-/pipelines/493762>
triggered by Michael Reeves <https://invent.kde.org/mree
Is libicu in the CI images already?
kf6 is detected.
On Fri, Jun 16, 2023 at 1:52 PM Luigi Toscano
wrote:
> Michael Reeves ha scritto:
> > How arekf5options and qt5options man page links going to be handled for
> > application supporting both kf5 and kf6?
>
> Applications should decide whether to sup
How are kf5options and qt5options man page links going to be handled for
application supporting both kf5 and kf6?
What's the plan for sys admin tickets currently needed to publish releases?
May 26, 2023 5:10:43 PM Ben Cooksley :
> On Fri, May 26, 2023 at 9:31 AM Nate Graham wrote:
>> On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks
>> have no real "home"; they just have project
>>>
Some other than myself needs to resolve this but I have no idea who.
-- Forwarded message -
From: 石庭豐
Date: Wed, May 24, 2023 at 12:25 PM
Subject: [kdiff3] [Bug 470221] New: KDiff3 in winget store still at version
1.9.6
To:
https://bugs.kde.org/show_bug.cgi?id=470221
I receiving complaints about French words appearing sporadically on
KDiff3's GUi even when KDiff3 itself is set to use English.
I strongly suspect a setup issue within Windows but require assistance to
rule out frameworks/qt involvement in the issue.
https://bugs.kde.org/show_bug.cgi?id=442607
KDiff3 is in a similar position to GCompris and would not at this benefit from
auto closing or extra messaging on MR's
Mar 6, 2023 3:29:12 PM Johnny Jazeix :
> Hi,
>
> for GCompris, we don't have a lot of MR and even if some are old, we still
> plan to take over them at some point (we know
KDiff3 is in a similar position to GCompris and would not at this benefit from
auto closing or extra messaging on MR's
Mar 6, 2023 3:29:12 PM Johnny Jazeix :
> Hi,
>
> for GCompris, we don't have a lot of MR and even if some are old, we still
> plan to take over them at some point (we know
That looks a lot better. Weird magic numbers are what enums are ment to
avoid.
On Wed, Jan 11, 2023 at 7:26 AM Nicolas Fella wrote:
> On 1/10/23 22:49, Michael Reeves wrote:
> > /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime
> > error: load of value 42
de 2023, a les 22:49:43 (CET), Michael Reeves va
> escriure:
> > /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime error:
> > load of value 4294967295, which is not a valid value for type
> > 'Qt::ConnectionType'
> >
> > SUMMARY: UndefinedBehaviorSa
/usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime error:
load of value 4294967295, which is not a valid value for type
'Qt::ConnectionType'
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
/usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64 in
The issue stems for
This is the question I need answered. Windows by default gives the most
useless crash report I've ever seen. All I know from that is that the crash
point is inside qt but that doesn't help at all with a Qt based
application. Worse a lot the documentation I find assumes you are a)
debugging a
Are we able to get a proper stack trace of the crash?
On Mon, Oct 24, 2022 at 3:33 PM Ingo Klöcker wrote:
> On Montag, 24. Oktober 2022 19:21:11 CEST Michael Reeves wrote:
> > I've got a report that the installer seems to crash on startup would like
> > some assistance ident
I've got a report that the installer seems to crash on startup would like
some assistance identfiing the cause.
https://bugs.kde.org/show_bug.cgi?id=459484
Much as I don't like running KIO as root. The alternative right now is running
Dolphin itself as root. KIO still has no kauth/Polkit support.
Oct 14, 2022 4:34:36 AM Harald Sitter :
> On Thu, Oct 13, 2022 at 10:32 PM Albert Astals Cid wrote:
>>
>> El dijous, 13 d’octubre de 2022, a les
You might have better look at kde-win...@kde.org that list is specific to
Windows.
Sep 11, 2022 12:23:06 AM Paul Burns :
> Hi
>
> I am attempting to build QGIS from source. QGIS includes QCA and also calls
> for the OSSL plugin. I am using Qt5 64 bit Windows 10 as my dev environment.
>
> I
I just read this in the Automate and systematize internal processes Goal
Move clang-format from a git hookscript to pre-commit CI so that merge
requests will show a CI failure when badly-formatted changes exist, and
people can see this in a nice UI and fix them
I now have no way to even test macosx builds for kdiff3, I have no access to a
64bit Intel mac. What are the plans for this and Windows
builds. I have a functional windows based craft installed locally.
Sep 3, 2022 12:47:06 AM Ben Cooksley :
> On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley
I now have no way to even test macosx builds for kdiff3, I have no access to a
64bit Intel mac. What are the plans for this and Windows
builds. I have a functional windows based craft installed locally.
Sep 3, 2022 12:47:06 AM Ben Cooksley :
> On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley
I now have no way to even test macosx builds for kdiff3, I have no access to a
64bit Intel mac. What are the plans for this and Windows
builds. I have a functional windows based craft installed locally.
Sep 3, 2022 12:47:06 AM Ben Cooksley :
> On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley
The kdiff3 1.10 branch has been created and is now on string/feature freeze.
Fair enough but could we at least have a way to turn it off if we know what
it's about but still want to keep our dependencies lower than what ever current
frameworks happens to decide on.
May 16, 2022 2:02:26 PM Christoph Cullmann (cullmann.io)
:
> On 2022-05-16 19:38, Alexander Neundorf
On Tue, May 10, 2022 at 10:48 AM Christoph Cullmann (cullmann.io) <
christ...@cullmann.io> wrote:
> On 2022-05-10 15:33, Nate Graham wrote:
> > On 5/10/22 04:15, Ingo Klöcker wrote:
> >>> https://manifesto.kde.org/commitments/
> >>
> >> I don't see anything in there that would force the same
That would only affect people who manually update ECM and in that case the
error comes first. So warning isn't much use to projects like kdiff3 which
don't encourage ot support this kind of wierdness anyway
On Tue, May 3, 2022, 12:26 PM Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net>
That would only affect people who manually update ECM and in that case the
error comes first. So warning isn't much use to projects like kdiff3 which
don't encourage ot support this kind of wierdness anyway
On Tue, May 3, 2022, 12:26 PM Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net>
Could someone please explain why this warning was add to FindKF5.cmake:
CMake Warning (dev) at
/usr/share/ECM/modules/ECMFindModuleHelpers.cmake:112 (message):
Your project should require at least CMake 3.16.0 to use FindKF5.cmake
Call Stack (most recent call first):
Could someone please explain why this warning was add to FindKF5.cmake:
CMake Warning (dev) at
/usr/share/ECM/modules/ECMFindModuleHelpers.cmake:112 (message):
Your project should require at least CMake 3.16.0 to use FindKF5.cmake
Call Stack (most recent call first):
In all honesty formatting is something that should be dealt with
automatically. I use clang-format as part of my IDE just so I don't have to
think about formatting in addition to the actual functionality of the code
I'm writing. Auto formatting as you type helps a lot in keeping code
consistently
What would be needed to build from a tar ball on Windows. I have a craft setup
locally but it likes to use git.
Jan 21, 2022 2:10:19 PM Ben Cooksley :
> On Sat, Jan 22, 2022 at 7:52 AM Michael Reeves wrote:
>> This is being cross posted because I am not subscribed to kde-window and
&
What would be needed to build from a tar ball on Windows. I have a craft setup
locally but it likes to use git.
Jan 21, 2022 2:10:19 PM Ben Cooksley :
> On Sat, Jan 22, 2022 at 7:52 AM Michael Reeves wrote:
>> This is being cross posted because I am not subscribed to kde-window and
&
Thanks.
On Fri, Jan 21, 2022 at 2:10 PM Ben Cooksley wrote:
> On Sat, Jan 22, 2022 at 7:52 AM Michael Reeves
> wrote:
>
>> This is being cross posted because I am not subscribed to kde-window and
>> replies have not shown up in mail archives when I contacted that lis
Thanks.
On Fri, Jan 21, 2022 at 2:10 PM Ben Cooksley wrote:
> On Sat, Jan 22, 2022 at 7:52 AM Michael Reeves
> wrote:
>
>> This is being cross posted because I am not subscribed to kde-window and
>> replies have not shown up in mail archives when I contacted that lis
This is being cross posted because I am not subscribed to kde-window and
replies have not shown up in mail archives when I contacted that list for
other issues. The bug in question is here:
https://bugs.kde.org/show_bug.cgi?id=442607
As far as I can see the setup for kdiff3 is correct but does
This is being cross posted because I am not subscribed to kde-window and
replies have not shown up in mail archives when I contacted that list for
other issues. The bug in question is here:
https://bugs.kde.org/show_bug.cgi?id=442607
As far as I can see the setup for kdiff3 is correct but does
What is the status for MacOS builds?
Jan 9, 2022 4:34:38 AM Ben Cooksley :
> Hi all,
>
> Over the past week substantial work has meant that we now have a successfully
> compiling seed job for Frameworks on Windows under Gitlab.
>
> This is a significant step on the road to announcing general
What is the status for MacOS builds?
Jan 9, 2022 4:34:38 AM Ben Cooksley :
> Hi all,
>
> Over the past week substantial work has meant that we now have a successfully
> compiling seed job for Frameworks on Windows under Gitlab.
>
> This is a significant step on the road to announcing general
Where are the artifacts being uploaded to? They don't seem to show in
gitlab. In particular the coverage report is of interest to me.
On Sat, Nov 27, 2021 at 1:31 PM Ben Cooksley wrote:
> Hi all,
>
> As mentioned in the subject, i'm happy to announce the general
> availability of native Gitlab
Where are the artifacts being uploaded to? They don't seem to show in
gitlab. In particular the coverage report is of interest to me.
On Sat, Nov 27, 2021 at 1:31 PM Ben Cooksley wrote:
> Hi all,
>
> As mentioned in the subject, i'm happy to announce the general
> availability of native Gitlab
Where are the artifacts being uploaded to? They don't seem to show in
gitlab. In particular the coverage report is of interest to me.
On Sat, Nov 27, 2021 at 1:31 PM Ben Cooksley wrote:
> Hi all,
>
> As mentioned in the subject, i'm happy to announce the general
> availability of native Gitlab
How do we get a visual on exactly which lines are covered by auto testing
and which aren't?
How do we get a visual on exactly which lines are covered by auto testing
and which aren't?
Michael Reeves
May 19, 2021, 7:24 PM
KDiff3 1.9.3 is now released.
It can be found at
http://download.kde.org/stable/kdiff3/kdiff3-1.9.3.tar.xz.mirrorlist
kdiff3-1.9.3.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
Fixes multiple regressions in file
One thing the seems entirely missing is any documentation what so ever of
craft's runtime confurable options. I'm talking things maintainers can do
in their config scripts not the end-user config file which is self
documented.
On Wed, Jun 9, 2021, 1:27 PM Frederik Schwarzer wrote:
>
>
> On
One thing the seems entirely missing is any documentation what so ever of
craft's runtime confurable options. I'm talking things maintainers can do
in their config scripts not the end-user config file which is self
documented.
On Wed, Jun 9, 2021, 1:27 PM Frederik Schwarzer wrote:
>
>
> On
The default has been set back to 1.69.0 to resolve the more general
breakage. However kdiff3 can not use this version of boost headers and
will block at config time by design.
https://build.kde.org/job/Extragear/job/kdiff3/job/kf5-qt5%20WindowsMSVCQt5.15/
KDiff3 requires boost-headers 1.71.0 or later due to an MSVC specific
link time bug See https://github.com/boostorg/safe_numerics/issues/71.
Craft however is refusing to take the updated configuration files into
Based on https://gitlab.gnome.org/GNOME/mutter/-/issues/217
I am terminating support for gnome/wayland unless and until gnome
stops force client side decoration on everyone.
On Sun, May 23, 2021 at 9:16 AM Michael Reeves wrote:
>
> Could some familaur with Wayland/gnome client side deco
Could some familaur with Wayland/gnome client side decorating have a look
at this? I have a suspicion gnome is trying to force this feature on kdiff3.
On Sun, May 23, 2021, 4:27 AM wrote:
> https://bugs.kde.org/show_bug.cgi?id=436826
>
> solot...@gmail.com changed:
>
>What
This is a fix for 436958 previous 1.9.0 and 1.9.1 releases should be
disregarded.
KDiff3 1.9.2 is now released.
It can be found at https://download.kde.org/stable/kdiff3/
kdiff3-1.9.2.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
File processing should be much
Or maybe not. I'll have another look at this now that emergency fix is
addressed. Calling SourceData::readAndPreprocess on a SourceData object
flagged as a directory shouldn't be happening.
On Thu, May 13, 2021, 3:59 PM Michael Reeves wrote:
> I was looking at the wrong file then. That v
I was looking at the wrong file then. That very likely is related to bug
436958.
On Thu, May 13, 2021, 3:35 PM Ingo Klöcker wrote:
> On Donnerstag, 13. Mai 2021 07:53:05 CEST Michael Reeves wrote:
> > That's a crash in the implicit default constructor of QTemporaryFile.
>
> I
.
If that fixes the problem then the patch will resolve your case as well.
On Thu, May 13, 2021, 3:35 PM Ingo Klöcker wrote:
> On Donnerstag, 13. Mai 2021 07:53:05 CEST Michael Reeves wrote:
> > That's a crash in the implicit default constructor of QTemporaryFile.
>
> I don't think
That's a crash in the implicit default constructor of QTemporaryFile. And
that would be a Qt bug if its reproducible. You sure you have the current
1.9 branch and built from that?
On Wed, May 12, 2021, 7:30 PM Aleix Pol wrote:
> On Thu, May 13, 2021 at 1:00 AM Michael Reeves
>
Thanks do we have the text of the assert?
On Wed, May 12, 2021, 7:30 PM Aleix Pol wrote:
> On Thu, May 13, 2021 at 1:00 AM Michael Reeves
> wrote:
> >
> > Could someone other than myself please have a look at this.
> >
> > https://bugs.kde.org/show_
Could someone other than myself please have a look at this.
https://bugs.kde.org/show_bug.cgi?id=436958
None of these issues affect my system. I strongly suspect a distro
specific issue. https://bugs.gentoo.org/show_bug.cgi?id=789330. The
offending commit makes no sense as a true root cause. I
That's a crash in the implicit default constructor of QTemporaryFile. And
that would be a Qt bug if its reproducible. You sure you have the current
1.9 branch and built from that?
On Wed, May 12, 2021, 7:30 PM Aleix Pol wrote:
> On Thu, May 13, 2021 at 1:00 AM Michael Reeves
>
Thanks do we have the text of the assert?
On Wed, May 12, 2021, 7:30 PM Aleix Pol wrote:
> On Thu, May 13, 2021 at 1:00 AM Michael Reeves
> wrote:
> >
> > Could someone other than myself please have a look at this.
> >
> > https://bugs.kde.org/show_
Could someone other than myself please have a look at this.
https://bugs.kde.org/show_bug.cgi?id=436958
None of these issues affect my system. I strongly suspect a distro
specific issue. https://bugs.gentoo.org/show_bug.cgi?id=789330. The
offending commit makes no sense as a true root cause. I
Please don't make my life hard with this kind of unilateral decision making
if kde aa whole decides to move ro gitlab that's one thing. I am not going
to keep dealing with users confusion caused by projects like yours engaging
in undiscussed experiments for support. That.comes frim someone who
KDiff3 1.9.0 is now released.
It can be found at https://download.kde.org/stable/kdiff3/
kdiff3-1.9.0.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
File processing should be much faster now.
The contetual menu is fixed on Windows.
Known Issues/Limitations:
*As
Thanks.
On Thu, Jan 28, 2021, 2:17 PM Andreas Cord-Landwehr
wrote:
> On Donnerstag, 28. Januar 2021 10:20:54 CET Konstantin Kharlamov wrote:
> > On Wed, 2021-01-27 at 17:36 -0500, Michael Reeves wrote:
> > > Is there way to reading and writing small files in the CI? I'm in
Thanks.
On Thu, Jan 28, 2021, 2:17 PM Andreas Cord-Landwehr
wrote:
> On Donnerstag, 28. Januar 2021 10:20:54 CET Konstantin Kharlamov wrote:
> > On Wed, 2021-01-27 at 17:36 -0500, Michael Reeves wrote:
> > > Is there way to reading and writing small files in the CI? I'm in
Is there way to reading and writing small files in the CI? I'm in the
process of writing auto tests for kdiff3.
Is there way to reading and writing small files in the CI? I'm in the
process of writing auto tests for kdiff3.
KDiff3 1.8.5 is now released.
It can be found at https://download.kde.org/stable/kdiff3/
kdiff3-1.8.5.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
Known Issues/Limitations:
*As of this time binary comparison has been temporarily disabled due to
stability
KDiff3 MacOS X build at binary factory is failing with the fallowing error:
16:04:13 CMake Error at
/Users/packaging/Craft/BinaryFactory/macos-64-clang/dev-utils/cmake-base/CMake.app/Contents/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218
(message):
16:04:13Could NOT find
KDiff3 MacOS X build at binary factory is failing with the fallowing error:
16:04:13 CMake Error at
/Users/packaging/Craft/BinaryFactory/macos-64-clang/dev-utils/cmake-base/CMake.app/Contents/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218
(message):
16:04:13Could NOT find
I have added support for KIO::UDSEntry::UDS_LOCAL_PATH in master this will
be part of the upcoming 1.9 branch. Also the detection of links via KIO has
been fixed. This is fixed in the 1.8 branch official release of 1.8.5 will
come late today or tomorrow. Display name support is planned for master
I have added support for KIO::UDSEntry::UDS_LOCAL_PATH in master this will
be part of the upcoming 1.9 branch. Also the detection of links via KIO has
been fixed. This is fixed in the 1.8 branch official release of 1.8.5 will
come late today or tomorrow. Display name support is planned for master
message -
From: Michael Reeves
Date: Fri, Dec 18, 2020, 5:02 PM
Subject: [sdk/kdiff3] src: Disable problematic clazy warnings
To:
Git commit 4b319434a0a0e9c11f3de358bb307dca75750fb7 by Michael Reeves.
Committed on 18/12/2020 at 21:58.
Pushed by mreeves into branch 'master'.
Disable
message -
From: Michael Reeves
Date: Fri, Dec 18, 2020, 5:02 PM
Subject: [sdk/kdiff3] src: Disable problematic clazy warnings
To:
Git commit 4b319434a0a0e9c11f3de358bb307dca75750fb7 by Michael Reeves.
Committed on 18/12/2020 at 21:58.
Pushed by mreeves into branch 'master'.
Disable
to the dmg. That said
> iirc signing the app is a requirement before submitting the app to apple's
> notarization service in the first place.
>
> On Thu, Oct 22, 2020 at 11:12 AM Ben Cooksley wrote:
>
>> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves
>> wrote:
>>
>
e app to apple's
> notarization service in the first place.
>
> On Thu, Oct 22, 2020 at 11:12 AM Ben Cooksley wrote:
>
>> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves
>> wrote:
>>
>>> Could someone familiar with the CI and OS X signing machinism look at
&
Could someone familiar with the CI and OS X signing machinism look at this.
https://bugs.kde.org/show_bug.cgi?id=428062
I have no way to test or fix this issue. Which as far as I know is an issue
with the CI on binary factory.
to the dmg. That said
> iirc signing the app is a requirement before submitting the app to apple's
> notarization service in the first place.
>
> On Thu, Oct 22, 2020 at 11:12 AM Ben Cooksley wrote:
>
>> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves
>> wrote:
>>
>
e app to apple's
> notarization service in the first place.
>
> On Thu, Oct 22, 2020 at 11:12 AM Ben Cooksley wrote:
>
>> On Fri, Oct 23, 2020 at 6:08 AM Michael Reeves
>> wrote:
>>
>>> Could someone familiar with the CI and OS X signing machinism look at
&
Could someone familiar with the CI and OS X signing machinism look at this.
https://bugs.kde.org/show_bug.cgi?id=428062
I have no way to test or fix this issue. Which as far as I know is an issue
with the CI on binary factory.
KDiff3 1.8.4 is now released.
It can be found at https://download.kde.org/stable/kdiff3/
kdiff3-1.8.4.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
Known Issues/Limitations:
*As of this time binary comparison has been temporarily disabled due to
stability
"You keep track of your patches (more or less
succesfully) and cherry-pick or port them."
This sums up what I do with kdiff3. In fact right now trying to merge
between stable and master or the other way around would be a nightmare
project due to heavy refactoring.
On Mon, Aug 24, 2020, 4:07 PM
The odd naming is a flatpac requirement if you want the icon auto
extracted. Otherwise flatpac will have to be told explicitly to rename the
icon.
On Tue, Aug 11, 2020, 3:38 AM Christophe Giboudeaux
wrote:
> On lundi 3 août 2020 23:12:25 CEST Albert Astals Cid wrote:
> > > I added the icon and
On Tue, Jul 7, 2020, 10:44 AM Jonathan Riddell wrote:
> There's an old web page on sourceforge, have you tried to get this removed?
>
I should have access now.
>
> You can add release into to the appstream file to get that onto
> kde.org/applications
>
ility/9ndvvx243rfh?activetab=pivot:overviewtab#
> <https://urldefense.com/v3/__https://www.microsoft.com/en-gb/p/kdiff-3-diff-utility/9ndvvx243rfh?activetab=pivot:overviewtab*__;Iw!!KGKeukY!kFQYtIg2DbY-nE60gJ9qlbisy_SQ_J0GDRtJZnuyib3bLFshe2--mUU9Xe7Go_yUCw$>
>
> Jonathan
>
>
KDiff3 1.8.3 is now released.
It can be found at https://download.kde.org/stable/kdiff3/
kdiff3-1.8.3.tar.xz.mirrorlist
MacOS X and Windows 64 bit binaries have also been released.
Known Issues/Limitations:
*As of this time binary comparison has been temporarily disabled due to
stability
Is there a record of the work done so far? It looks like some of the errors
look like the result off missing #include *.moc. I only know having run
into this myself. Usually in clang/gcc. Not sure why this would show up
only in MSVC. I can investigate when I get home. I build kdiff3 for windows
so
How does one specify dependencies in flatpak for binary-factory.kde.org.
signature.asc
Description: This is a digitally signed message part.
Is there a record of the work done so far? It looks like some of the errors
look like the result off missing #include *.moc. I only know having run
into this myself. Usually in clang/gcc. Not sure why this would show up
only in MSVC. I can investigate when I get home. I build kdiff3 for windows
so
Is there a record of the work done so far? It looks like some of the errors
look like the result off missing #include *.moc. I only know having run
into this myself. Usually in clang/gcc. Not sure why this would show up
only in MSVC. I can investigate when I get home. I build kdiff3 for windows
so
I plan on trying to release 1.8.3 in a two week. This should give some time
for things to settle down now that the initial move to Gitlab is done.
On Tue, Apr 14, 2020, 5:19 AM Simon Persson
wrote:
> On 2020-04-07 05:09, Adriaan de Groot wrote:
> > On Monday, 6 April 2020 12:32:54 CEST Simon Persson wrote:
> .
>
>
>
> >
> > - Uses a handful of deprecated methods; depending on what exactly you
> want to
> > be compatible with, you might
1 - 100 of 184 matches
Mail list logo
