https://invent.kde.org/graphics/kuickshow and imlib1
Hello,
1. Can someone build kuickshow? If so, how?
2. Can we please archive https://invent.kde.org/graphics/kuickshow ?
Thanks.
Technical details:
Maybe I got something wrong, but.
https://invent.kde.org/graphics/kuickshow seems to depend on imlib1 . Which
is https://download.gnome.org/sources/imlib/1.9/ imlib-1.9.15.tar.bz2 667.2
KiB 2004-Sep-24 14:45
imlib1 is no longer packaged by Debian or Ubuntu. I cannot build it from
source code "load.c:579:3: error: too few arguments to function
'DGifCloseFile'", "load.c:194:21: error: invalid use of incomplete typedef
'png_struct' {aka 'struct png_struct_def'}".
In fact kuickshow is a wrapper around imlib1/imlibwidget.cpp.
https://docs.enlightenment.org/api/imlib2/html/ says "Imlib 2 is the
successor to Imlib. It is NOT a newer version - it is a completely new
library.", "Date: 1999-2004". So, Rasterman is trying to replace imlib1
with something better since 1999.
Sunsetting Cervisia
Hello, I vote that we archive https://invent.kde.org/sdk/cervisia Reasons: * CVS version control system is not that used anymore. At least not in the KDE Community. * Hundreds of build warnings, clangd warnings, clazy warnings, PVS-Studio warnings. * Complex architecture. I do not know how to start the GUI app. Has kpart, has a dbus daemon/service. Questions: * Should we archive Cervisia? * If yes. How can I help to make the process faster? Thanks.
Remove Qt4 from sysadmin/repo-metadata
Hello, If it is OK. I would want to remove Qt4 and KDE version 4 from sysadmin/repo-metadata. The first step that I want to do: delete sysadmin/repo-metadata/dependencies/dependency-data-latest-qt4 and sysadmin/repo-metadata/dependencies/dependency-data-stable-qt4. May I do this? Thanks.
Remove web_module sidebar from network/konqueror
Hello, If it is OK. I would want to remove the web_module sidebar from network/konqueror. https://invent.kde.org/network/konqueror/-/merge_requests/142 Reasons: * Depends on KHTML. * This is a feature that was probably written before Mozilla Firefox, in the days of Mozilla Suite (i.e. the current Mozilla Seamonkey). And Mozilla Suite had a complex sidebar that could do tens of things. Opera web browser also had this complex type of a sidebar. I vote that we remove from Konqueror the sidebar that just displays a website. Thanks.
Solid - not needed translated strings?
Hello, >From what I see, the KDE Framework 5 Solid does not need translations for the strings: #~ msgctxt "Solid::DeviceInterface|A pointing device" #~ msgid "PointingDevice" #~ msgctxt "Solid::DeviceInterface|A keyboard" #~ msgid "Keyboard" #~ msgctxt "Solid::DeviceInterface|Internet Gateway device type" #~ msgid "Internet Gateway Device" And a number of strings like: "msgctxt "Solid::DeviceInterface| device type"" Question 1: are those strings used/needed? Question 2: if they are not used/needed, can I remove them? Thanks.
Archiving KDE Telepathy?
+1
KDE git repositories that will not be ported to Qt6
Hello, What is the list of KDE git repositories that will not be ported to Qt6? I guess that some of these are: frameworks/kdelibs4support, frameworks/kjs, frameworks/khtml, frameworks/kross. Thanks.
https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/160
Hello, Beginners that want to program for KDE start by building KDE git repositories using kdesrc-build. They find it really hard to convert the kdesrc-build error "Unable to configure kpat with KDE CMake" to the solution "sudo apt install libfreecell-solver-dev". Yes, the reasons are: they do not know enough about their Linux distribution, they did not read the entire wiki page https://community.kde.org/Get_Involved/development and its children. Please help me get https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/160 merged. This way, we will get at the end of the kdesrc-build output: "Possible solution: Install the build dependencies for the modules: krfb, kpat. Using 'sudo apt build-dep ', 'sudo dnf builddep ' or similar. See https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Install_the_dependencies " Thanks.
Can we archive https://invent.kde.org/games/kmuddy ?
Hello, Can we archive https://invent.kde.org/games/kmuddy ? Can we do the reverse of the incubation procedure https://community.kde.org/Incubator/Incubated_Projects to kmuddy? Reasons: * The last git commit that is not by "Script Kiddy - translation" and not a build warning fix/deprecation fix is from 2020.11. https://invent.kde.org/games/kmuddy/-/commits/master * kmuddy is not available as a package in the package repositories of Ubuntu, Fedora, Arch, KDE neon etc. * I cannot find a MUD HTTP online server. * I cannot find a Linux MUD server software package (*.deb) in the Ubuntu repositories. * I am not sure if https://invent.kde.org/games/kmuddy/-/tree/master/libmxp is even built by default. * Depends on KDELibs4Support. * kmuddy needs work. * Do we want to port kmuddy to Qt6? Thanks.
Re: KUbuntu folks please update the "How to create useful crash reports" wiki page
My contributions: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debuginfod And the mention about debuginfod support in Ubuntu, Debian, Fedora and openSUSE Tumbleweed. On Tue, Nov 8, 2022 at 1:23 PM Aleix Pol wrote: > Including the Kubuntu list, just in case. > > Aleix > > On Mon, Nov 7, 2022 at 8:57 PM Albert Astals Cid wrote: > > > > In https://bugs.kde.org/show_bug.cgi?id=461258 I asked the reported to > provide a backtrace and he realized that > > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 > > links to https://wiki.kubuntu.org/DebuggingProgramCrash that does not > exist. > > > > Please someone that knows how to install debug symbols in Kubuntu update > that page accordingly. > > > > Cheers, > > Albert > > > > >
Can we archive https://invent.kde.org/sdk/qml-lsp ?
Can we do the reverse of the incubation procedure https://community.kde.org/Incubator/Incubated_Projects to qml-lsp? Reasons: * It does not have a master branch. Or equivalent. * Is written in golang. * Has funny git commit messages. Thanks.
Re: KUbuntu folks please update the "How to create useful crash reports" wiki page
> Please someone that knows how to install debug symbols in Kubuntu update that page accordingly. Done. https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Procedure_.28K.29Ubuntu_gdb_without_debuginfod On Fri, Nov 11, 2022 at 10:18 PM Marius P wrote: > My contributions: > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debuginfod > > And the mention about debuginfod support in Ubuntu, Debian, Fedora and > openSUSE Tumbleweed. > > On Tue, Nov 8, 2022 at 1:23 PM Aleix Pol wrote: > >> Including the Kubuntu list, just in case. >> >> Aleix >> >> On Mon, Nov 7, 2022 at 8:57 PM Albert Astals Cid wrote: >> > >> > In https://bugs.kde.org/show_bug.cgi?id=461258 I asked the reported to >> provide a backtrace and he realized that >> > >> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 >> > links to https://wiki.kubuntu.org/DebuggingProgramCrash that does not >> exist. >> > >> > Please someone that knows how to install debug symbols in Kubuntu >> update that page accordingly. >> > >> > Cheers, >> > Albert >> > >> > >> >
Can we make kpat not depend on black-hole-solitaire by default?
Hello, Debian and Ubuntu do not package yet https://github.com/shlomif/black-hole-solitaire Can we make kpat not depend on https://github.com/shlomif/black-hole-solitaire by default? Reasons: 1. In order to build kpat on Kubuntu 22.10, we need to edit kdesrc-build. 2. Debian and Ubuntu need to have in file "rules" "override_dh_auto_configure:... -DWITH_BH_SOLVER=OFF". Thanks. Technical details. kdesrc-build patch: $ git diff diff --git a/kf5-applications-build-include b/kf5-applications-build-include index 52b453c..63ed776 100644 --- a/kf5-applications-build-include +++ b/kf5-applications-build-include @@ -145,6 +145,12 @@ module-set kmix cmake-options -DKMIX_KF5_BUILD:STRING=TRUE end module-set +module-set kpat +repository kde-projects +use-modules kpat +cmake-options -DWITH_BH_SOLVER=OFF +end module-set + module-set kdegames repository kde-projects use-modules kde/kdegames amor
Re: Registration
Hello, When you say "Did you design this thing in such way that a VPN user is considered a spammer?" who do you think this "you" person or group of persons is? Thanks. On Mon, Jan 16, 2023 at 11:13 AM wrote: > I've filled the captcha properly and I'm using a VPN. Did you design this > thing in such way that a VPN user is considered a spammer? Really? > > -- > I'm using Tutanota - the end-to-end encrypted email service > > > > 16 янв. 2023 г., 12:03 От bcooks...@kde.org: > > On Mon, Jan 16, 2023 at 9:58 PM wrote: > > Hello there! > I've just tried to register on your KDE Identity thing. I did everything > properly and saw "Client rejected by automatic spammer detection system". > What is that shit supposed to mean? I'm not a spammer. > > > Hi there, > > This usually means that you haven't completed the Google reCAPTCHA on the > registration page, or there was something wrong with your details. > > Can you confirm that you have completed the CAPTCHA? > > Cheers, > Ben > > > > -- > I'm using Tutanota - the end-to-end encrypted email service > > >
Re: Per project repository snapcraft files?
Hello, I guess that this email thread is about "Can we please add the file ".snapcraft.yaml" to KDE git repositories. I could build https://invent.kde.org/education/blinken as a snap file, install the snap file and run blinken correctly. Thanks. Details/steps: I use Kubuntu 23.04, as per https://snapcraft.io/docs/snapcraft-overview, I did: sudo snap install snapcraft --classic # (it installs snaps for snapcraft) mkdir ~/firstsnap snapcraft init Restart the computer such that the command "groups" will return "lxd". git clone https://invent.kde.org/education/blinken.git or kdesrc-build blinken cd /home/nmariusp/kde5/src/blinken/ snapcraft --debug sudo snap install blinken_23.08.0_amd64.snap --devmode blinken # ($PATH environment variable ends in "/snap/bin") On Thu, Aug 24, 2023 at 1:33 PM Ben Cooksley wrote: > On Thu, Aug 24, 2023 at 5:00 AM Albert Astals Cid wrote: > >> El dimecres, 23 d’agost de 2023, a les 18:29:10 (CEST), Scarlett Moore va >> escriure: >> > After some testing and various complicated options, the easiest I have >> > found is importing our github mirror in launchpad ( this avoids the >> > polling on kde servers ) and we can create our necessary snap recipes >> > and KDE infrastructure is unaffected save the already in place github >> > mirror. Launchpad does everything else ( building and uploading to >> > store ) I see no reason not to move forward as KDE infrastructure will >> > have much less involvement in the snap lifecycle aside from the >> > snapcraft files being in the application repository. As mentioned >> > before this will allow developers closer involvement with snap >> > developers. >> >> Honestly I'm still a bit lost on what is you are trying to do regarding >> Snap and the KDE repos :D >> > > I have to admit I am similarly confused. > > I thought this was originally about CI, which is why I proposed tying this > in through .gitlab-ci.yml. > Using that mechanism if this is really about final release builds doesn't > make much sense. > > Having a look at what was committed to Blinken's repository though, i'm > not sure there is much that would stop this being actual CI (assuming > someone got it working within Docker)? > > >> Are we going for CI or CD? >> >> CI -> snap is compiled on each commit and MR to make sure we don't break >> the snap build >> >> CD -> We have an almost-automated way of doing snap "release" builds. >> >> >> To give some examples: >> >> This is arianna's KDE flatpak CI >>https://invent.kde.org/graphics/arianna/-/jobs/1142328 >> It builds arianna using flatpak with each commit but the artifacts >> are "unused" >> >> >> This is Okular's KDE Windows CI >>https://invent.kde.org/graphics/okular/-/jobs/1142178 >> It builds each commit to make sure the Windows build doesn't get >> broken >> >> >> This is Okular's KDE Windows CD >>https://binary-factory.kde.org/job/Okular_Release_win64/ >> It builds release Okular nightly in a way that is a release build >> and can be easily uploaded to the Windows Store >> >> >> This is Okular flathub CD >>https://github.com/flathub/org.kde.okular >>https://buildbot.flathub.org/#/apps/org.kde.okular >> It is a convenient way to generate new builds each time a stable >> release happens >> >> >> I see you committed this >> https://invent.kde.org/education/blinken/-/blob/master/.snapcraft.yaml >> >> >> What is that going to give us? >> >> >> Cheers, >> Albert >> > > Cheers, > Ben > > >> >> >> > Thanks, >> > Scarlett >> > >> > On Sun, Aug 20, 2023 at 7:20 PM Justin Zobel >> wrote: >> > > I think there is a lot of misunderstanding here. >> > > >> > > In GitLab CI only test builds are done and artifacts are kept so >> people >> > > can test an AppImage or Flatpak without having to compile locally. >> > > >> > > Stable releases are done by the Release Team via scripts to tarballs. >> > > Flatpaks are done via Flathub and are done (usually) automatically via >> > > the Flatpak External Data Checker. >> > > >> > > Hopefully this clarifies the situation. >> > > >> > > On 21/8/23 08:48, Scarlett Moore wrote: >> > > > On Sun, Aug 20, 2023, 4:14 PM Julius Künzel >> > > > >> > > > wrote: >> > > > To me it seems this discussion is quite abstract and there are >> > > > several misunderstandings because not everybody knows every >> detail >> > > > of snap packaging and/or the KDE infrastructure (me neither). >> > > > >> > > > I understand that from an organizational perspective most people >> > > > like the idea of having the files in the repos, but have >> technical >> > > > doubts. Hence, I wonder whether it would be a good idea to take >> > > > one KDE app to try and showcase this suggestion? >> > > > >> > > > Cheers, >> > > > Julius >> > > > >> > > > Sounds like a great idea to me. >> > > > Scarlett >> > > > >> > > > 20.08.2023 17:55:24 Laura David Hurka > >: >> > > > > On Sunday, August 20, 2023 12:47:10 PM CEST Ben Cooksley >> wrote: >> > >
Add three additional rules to the KDE coding guidelines for CMake source code
Hello,
Can we please modify the KDE coding guidelines for CMake source code
https://community.kde.org/Policies/CMake_Coding_Style
Such that we do not allow the following three issues:
1. kconfig/src/core/CMakeLists.txt:36: Mismatching spaces inside ()
after command [whitespace/mismatch]:
"configure_file(config-kconfig.h.cmake
${CMAKE_CURRENT_BINARY_DIR}/config-kconfig.h )"
Notice that the opening parentheses is followed by zero spaces while
the closing parentheses has a space before it.
2. kconfig/CMakeLists.txt:74: Extra spaces between 'include' and its
() [whitespace/extra]:
"include (ECMPoQmTools)"
This is about not having whitespace between a "CMake command" and its "(".
Reasons: 90% of the lines from the cmake source code files from the
KDE project already respect this rule.
I cannot easily find a space between a cmake command and its "(" in
the documentation and tutorials from the CMake project e.g.
https://cmake.org/cmake/help/git-master/ ,
https://cmake.org/cmake/help/book/mastering-cmake/chapter/Writing%20CMakeLists%20Files.html
The cmake documentation about the cmake command "if" does not suggest
that a space is possible between "if" and its "(".
https://cmake.org/cmake/help/latest/command/if.html
cmake guidelines not from the cmake project tend to not use a space
between "if" and its "(". E.g.
https://learn.microsoft.com/en-us/vcpkg/contributing/cmake-guidelines
https://llvm.org/docs/CMakePrimer.html
There are cmake source code files from the KDE community which (in the
same file) use both styles e.g. "if(" and "if (".
https://invent.kde.org/utilities/kcalc/-/blob/master/CMakeLists.txt
The former project "kdeexamples" does not use space between a cmake
command and its "(".
https://invent.kde.org/unmaintained/kdeexamples/-/blob/ImprovedConfigDotCMakeFile/buildsystem/HowToInstallALibrary/CMakeLists.txt
3. kcalc/CMakeLists.txt:96: Line ends in whitespace [whitespace/eol]:
" kcalc_const_menu.cpp "
There is a space character after "kcalc_const_menu.cpp".
Thank you.
End of email, please ignore the rest of this email.
Technical details:
The cmake lint messages are from https://pypi.org/project/cmakelint/ .
I could not find a CMake source code guidelines web page from the CMake project.
The KDE coding guidelines for CMake source code
https://community.kde.org/Policies/CMake_Coding_Style already do not
allow the following issues:
1. kconfig/autotests/kconfig_compiler/CMakeLists.txt:8: Do not mix
upper and lower case commands [readability/mixedcase]:
"macro(GEN_KCFG_TEST_SOURCE _testName _srcs)
KCONFIG_ADD_KCFG_FILES(${_srcs} ${_testName}.kcfgc ${ARGN})
endmacro()"
https://community.kde.org/Policies/CMake_Coding_Style#Upper/lower_casing
says: "Upper/lower casing
Most important: use consistent upper- or lowercasing within one file !
In general, in KDE the all-lowercase style is preferred."
2. kconfig/KF6ConfigMacros.cmake:149: Expression repeated inside
endforeach; better to use only endforeach() [readability/logic]:
"endforeach(_current_FILE)"
https://community.kde.org/Policies/CMake_Coding_Style#End_commands
says: "To make the code easier to read, use empty commands for
endforeach(), endif(), endfunction(), endmacro() and endwhile(). Also,
use empty else() commands. "
This is also recommended by the CMake project
https://cmake.org/cmake/help/latest/command/if.html says "Per legacy,
the else() and endif() commands admit an optional
argument. If used, it must be a verbatim repeat of the argument of the
opening if command.". And the fact that
https://cmake.org/cmake/help/latest/command/if.html#synopsis is
different from https://cmake.org/cmake/help/v3.10/command/if.html#synopsis
3. kcalc/CMakeLists.txt:183: [whitespace/indent]:
" add_subdirectory( autotests )"
In this example file, most lines use 4 spaces indent, while this line
use 3 spaces indent.
https://community.kde.org/Policies/CMake_Coding_Style#Indentation says
"Use spaces for indenting, 2, 3 or 4 spaces preferably. Use the same
amount of spaces for indenting as is used in the rest of the file. Do
not use tabs."
If in a file has exactly 50% of of the indented lines using 3 spaces
and 50% of indented lines use 4 spaces, we should, in the future, use
4 spaces, because at least cmakelint leans towards having files
indented with 2 or 4 spaces.
