[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Downtime for SVN - Action Required
From:       Nicolás_Alvarez <nicolas.alvarez () gmail ! com>
Date:       2020-04-20 23:17:06
Message-ID: CANPC-tv2Kd9TLvFPkkXKQWksbo4zfOrWkS7mgZFUKhMNS+Aj+g () mail ! gmail ! com
[Download RAW message or body]

Translations are still in SVN, they have not moved to Git. We only
moved the SVN repository to a different server, and integrated SVN ssh
key management with the GitLab website.

-- 
Nicolás

El lun., 20 de abr. de 2020 a la(s) 19:56, Agron Selimaj
(as9902613@gmail.com) escribió:
> 
> Guys I just need a little clarification for submitting translated file to the \
> gitlab repository. 
> My first question is - is the migration over and can I submit translated files?
> 
> Second, with SVN all I did was commit (of course after compiling and other tests). \
> Now with Git, I fork + clone, translate and then send a merge request? Right? Is \
> there a guide for submitting po files? 
> Third, I need a little git/kde geography. What path do I clone from, from git? Is \
> there an efficient path that concerns translations only or more specifically \
> albanian translations. 
> Thanks,
> //Agron
> 
> 
> 
> 
> On Sat, Apr 18, 2020 at 6:36 AM Nicolás Alvarez <nalvarez@kde.org> wrote:
> > 
> > El dom., 12 de abr. de 2020 a la(s) 05:57, Ben Cooksley
> > (bcooksley@kde.org) escribió:
> > > 
> > > Hi all,
> > > 
> > > As you may be aware, KDE is currently undertaking a migration to Gitlab.
> > > 
> > > As part of this, we also need to migrate our Subversion repository
> > > from the server it currently resides on to the new system that also
> > > hosts Gitlab. To simplify our systems we will also transition
> > > management of SSH keys to Gitlab when we do this.
> > > 
> > > It is intended at this time that we perform the migration of the
> > > Subversion repository next weekend.
> > > 
> > > We therefore need all holders of a Developer account, even if they
> > > only use our Subversion repository, to login to Gitlab and upload
> > > their SSH keys there.
> > > 
> > > Our Gitlab instance can be found at https://invent.kde.org/ and you
> > > should be able to login there using your KDE Identity
> > > (identity.kde.org) details.
> > > 
> > > Additionally, following this migration we will begin limiting access
> > > to the Subversion repository to those actively using it. The list of
> > > people whose access will be continued can be found at
> > > https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list
> > > 
> > > Should you still need access to the repository, but are not on the
> > > above list, please let us know by emailing sysadmin@kde.org.
> > > 
> > > If anyone has any questions on the above, please let us know.
> > 
> > Hi all,
> > 
> > I wanted to add that this server migration will also change the SSH
> > host keys for "svn.kde.org". After we switch servers, you will get the
> > nasty "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" message from
> > ssh when you use SVN. To avoid this, you should add the new keys to
> > your ~/.ssh/known_hosts. You don't need to wait for the server switch,
> > you can add it now (keeping both old and new keys in the file) and it
> > will Just Work.
> > 
> > I have added instructions for all these changes and the new ssh host
> > keys to the wiki:
> > https://community.kde.org/Infrastructure/Subversion/2020_Changes
> > 
> > --
> > Nicolás
> > KDE Sysadmin Team


[prev in list] [next in list] [prev in thread] [next in thread]