Keep consistency with man page
Details
Details
Diff Detail
Diff Detail
- Repository
- R365 kdesrc-build
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 10334 Build 10352: arc lint + arc unit
Comment Actions
You do have access, it's just that kdesrc-build moved to invent.k.o so you need to be using git@invent.kde.org:kde/kdesrc-build.git instead of whatever you're using as remote.
Comment Actions
Sorry. Do not know what to do and how it works. It seems there are no instructions on this on our wikis... I have changed git.kde.org into invent.kde.org but it does not work as well.
Landing revision 'D20174: Fix typo: dependend -> depended'...
BUILDS PASSED Harbormaster builds for the active diff completed successfully.
PUSHING Pushing changes to "origin/master".
Warning: Permanently added 'invent.kde.org,46.4.53.124' (ECDSA) to the list of known hosts.
Permission denied (publickey).
As the rules become stricter and stricter for almost no reason, can somebody commit this for me, please?
Comment Actions
As the rules become stricter and stricter for almost no reason
This is pure bullshit, the rules have not become stricter at all.
Comment Actions
Ok. Sorry. I just become more ignorant with time, and things just slip from my hands.
Can you commit this one letter for me? Thanks in advance.
Comment Actions
I have committed the doc fix (and maintained your authorship). I expect that we will be able to automatically migrate git modules to the new location if it is decided to use Gitlab for all KDE git repositories, but in the meantime it does require manually running some git commands.
The right sequence is probably something like:
git config --global --add url.https://invent.kde.org/kde/.insteadOf invent: git config --global --add url.git@invent.kde.org:kde/.pushInsteadOf invent: git remote set-url origin invent:kdesrc-build git remote -v # Should look like # origin https://invent.kde.org/kde/kdesrc-build (fetch) # origin git@invent.kde.org:kde/kdesrc-build (push) git fetch origin
The git-config commands add a new invent: URL prefix that Git can use, similar to the kde: you probably already have. This is available globally (I couldn't make it work as a local repository setting).
The git-remote commands are used to change the location Git is looking for source to the Gitlab. The second command shows what the updated setting is, which should look as indicated in the code block above.
The final command causes Git to make the first network update to Gitlab, which may give a warning about a forced update or a redirection to a new URL.