Hello, since I tested this on my existing debian server, it's possible I forgot something, so do not hesitate to remind me some tips if you think I could missed it.
- Fil Lupin. ------- Original Message ------- On Wednesday, February 8th, 2023 at 12:13 AM, Fil Lupin via Replicant <[email protected]> wrote: > Hi Denis, > thank you for the doc fix. > > Yes, I did execute the source command before running repo sync. > > - Fil Lupin. > > PS: your key seems invalid > > ------- Original Message ------- > On Tuesday, February 7th, 2023 at 6:43 PM, Denis 'GNUtoo' Carikli > [email protected] wrote: > > > > > Hi, > > > > On Sun, 05 Feb 2023 23:15:41 +0000 > > Fil Lupin via Replicant [email protected] wrote: > > > > > gpg --keyserver keys.gnupg.net --recv-key \ > > > FB31DBA3AB8DB76A4157329F7651568F80374459 > > > > > > gpg: keyserver receive failed: No name > > > > I've now made a new release to fixed the GPG issue in the > > documentation along the way. > > > > > In addition, when executing repo sync, here is the error I got > > > --- > > > $ repo sync > > > Traceback (most recent call last): > > > > [...] > > > > > '/clone.bundle'TypeError: unsupported operand type(s) for +: > > > 'NoneType' and 'str' > > > > Did you run 'source /usr/local/bin/repo-env.sh' before 'repo sync'? > > > > Denis. > > _______________________________________________ > Replicant mailing list > [email protected] > https://lists.osuosl.org/mailman/listinfo/replicant _______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
