Re: Incubating app (Git Klient)
El dissabte, 20 d’agost de 2022, a les 14:06:40 (CEST), Hamed Masafi va escriure: > Hello > As a longtime kde fan(since 3.4), I would love to contribute to this group. > I am developing a graphical client application for git. I think it is a > good option to enter the world of kde. > > Features of this program: > - The icon displays the files in the Gate folder according to their > status in Dolphin. > - For easier access to the right-click menu of files and folders, options > such as pull, push, delete, ignore, etc. have been added. > - Graph display of commits. > - General Git operations such as pull, push, fetch. > - Show branches and distance of commits from the reference branch. > - View files and file contents in each branch or commit. > - Compare files, folders, branches and commits in a graphical environment. > - Merge conflicting files in git. > - Management of remotes, tags. > - Auto-completion when writing a commit message. > - Markdown editor (written but not yet added to the main program) > - And some extra features. > > The source is available here: > https://github.com/HamedMasafi/GitKlient > > Currently, only I (Hamid Masafi) am working on the project. > This project is currently on GitHub, but it can be moved to any other > repository if approved by you. > > Please take a look at this repository and let me know what you think. I > look forward to hearing from you. It's' initial incubation phase is done, please contribute at https://invent.kde.org/sdk/gitklient Cheers, Albert > > Best regards > Hamed Masafi
Re: Cleaning up cdash.org integration, what to do, or any hidden usage still?
Hi Alex, thanks for the quick reply. :) Am Sonntag, 4. September 2022, 23:42:36 CEST schrieb Alexander Neundorf: > On Freitag, 2. September 2022 12:20:50 CEST Friedrich W. H. Kossebau wrote: > > we stumbled over some CTestConfig.cmake files in some of the KDE git > > repositories. Which seem to originate from a time where people worked on > > integration with cdash.org, that is a decade ago :) > > > > It seems though this integration no longer is maintained: > > > > * no KDE projects seem listed on cdash.org anymore: > > https://my.cdash.org/viewProjects.php?allprojects=1 > > > > * the KDEUtilsNightly.cmake seems to have found no counterpart in the ECM > > > > world. The only reference seen is the check for the presence of a > > CTestConfig.cmake file and the inclusion of the CTest module in that > > case. > > > > With KDE's deployment of first Jenkins and now Gitlab CI around the > > purpose > > of the integration with cdash.org also seems no longer needed, by what I > > understand? > > > > So can we state that this cdash integration is officially no longer done, > > and thus we can clean up any traces of it, for clean and non-confusing > > data > > & code? > > I think so. Okay. So with the former lead on these efforts having confirmed I consider this then officially a thing of the history, within KDE :) > > Are there any other things left to do to clean up this, besides the > > following? > > > > T1) Remove any remaining CTestConfig.cmake files from KDE repos. All such files should have been removed now or at least be target of a MR, by a research via lxr.kde.org and invent.kde.org. > > T2) Remove support in KDECMakeSettings for deal with CTestConfig.cmake > > files: > > https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/295 Discussion on-going, but should be resolved soon. > > T3) Add a note on the respective Wiki page about being outdated: > > https://techbase.kde.org/Development/CMake/DashboardBuilds Anyone can tell what the official way to tag a page as outdated/historic is on techbase? > sounds good, but I didn't check. So if anyone else knows about some related left-over, please point to it (or action up-on :) ). Cheers Friedrich
Re: Help with tarme.rb
On Mon, Sep 5, 2022 at 6:55 AM Tobias Leupold wrote: > > Am Montag, 5. September 2022, 00:19:24 CEST schrieb Tobias Leupold: > > Hi all, > > > > I have a small problem with creating release tarballs. I must have missed > > something?! > > > > Yesterday, I created a release tarball for both KPhotoAlbum and KGeoTag. I > > first tried to do this as I always did it: > > > > ./tarme.rb --origin trunk --version 5.9.0 kphotoalbum > > > > that gave me > > > > Traceback (most recent call last): > > 8: from ./tarme.rb:74:in `' > > 7: from ./tarme.rb:74:in `collect' > > 6: from ./tarme.rb:81:in `block in ' > > 5: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/ > > release.rb:66:in `get' > > 4: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/ > > release.rb:154:in `check_ci!' > > 3: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/ > > jenkins.rb:60:in `from_name_and_branch' > > 2: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/ > > jenkins.rb:23:in `get' > > 1: from /usr/lib64/ruby/2.7.0/net/http/response.rb:133:in > > `value' /usr/lib64/ruby/2.7.0/net/http/response.rb:124:in `error!': 302 > > "Found" (Net::HTTPRetriableError) > > > > Then, I had a look at the wiki and found "--origin stable". I used this, and > > the tarball was created. > > > > Too late, I noticed (thanks Heiko Becker for mailing me!!!) that no > > translations are included in neither tarball. > > > > As said, I must have missed something -- what's wrong?! > > > > Thanks for all help for a (after all those years still) junior dev not doing > > releases too often ... ;-) > > > > Cheers, Tobias > > I have not much clue about Ruby, but I just noticed that the problem seems to > originate from "jenkins.rb", where a connection to build.kde.org is > established. This URL is since recently redirected to metrics.kde.org/login > (due to the retirement of Jenkins I think). A fix for this is waiting for its pipeline to succeed. > Also, invent.kde.org/sysadmin/repo-metadata lists "trunk", "stable", > "stable_kf5" and "trunk_kf5" in i18n.json, whereas tarme.rb acceps (according > to "./tarme.rb --help") "trunk", "stable", "lts", "trunk_kde4" and > "stable_kde4". > > So ... is this a tarme.rb issue?! Nah, trunk and stable in the metadata are simply the legacy (kde4) names
