trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2019

Re: [trinity-devel] Questions about metadata, versioning, and other tqt minutiae

From: Slávek Banko <slavek.banko@...>
Date: Wed, 1 Jan 2020 02:35:42 +0100
On Wednesday 01 of January 2020 00:51:33 E. Liddell wrote:
> On Fri, 27 Dec 2019 23:12:31 +0900
>
> "Michele Calgaro via trinity-devel" 
<trinity-devel@...> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > > Looks like the copy is all that's there right now.  I'll have to
> > > reread some documentation, since I mostly use mercurial rather than
> > > git, and register myself with the current system.
> >
> > See
> > https://wiki.trinitydesktop.org/TDE_Gitea_Workspace
> > for a short introductory guide to TGW. For git, there is plenty of
> > documentation available in the internet.
>
> Someone please explain to me like I'm five what this thing expects for
> credentials, because I keep getting this:
>
> # git push -u origin other/eapi7
> Username for 'https://scm.trinitydesktop.org': eliddell
> Password for 'https://eliddell@...':
> remote: invalid credentials
> fatal: Authentication failed for
> 'https://scm.trinitydesktop.org/gitea/TDE/tde-packaging-gentoo/'
>

Here's the simple reason: The TGW you need to push patches to is located at 
mirror.git.trinitydesktop.org, not scm.trinitydesktop.org. Although Gitea 
is now on scm.trinitydesktop.org, this instance is in read-only mode.

Therefore, you need to change the url for repository from 
https://scm.trinitydesktop.org/gitea/TDE/tde-packaging-gentoo/ to 
https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging-gentoo/

> (In other words, git is doing a very good job of reminding me why I use
> mercurial whenever I have the option.  Unfortunate that hg-git doesn't
> have very good support for branches.)
>

If this is the only problem, then using the git will be very cool :)

Note: I know it is a bit confusing when the primary GIT workspace is on a 
server whose name starts with mirror.git.. But that is unfortunately still 
due to Tim being unavailable and thus unable to set up DNS records. I 
firmly hope that this problem will also be resolved soon.

> E. Liddell
>

Cheers
-- 
Sl�vek

Attachments: