From: zimoun <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-science@gnu.org
Subject: Re: Help! I messed up guix-past
Date: Sat, 10 Sep 2022 11:47:42 +0200 [thread overview]
Message-ID: <868rmr7e81.fsf@gmail.com> (raw)
In-Reply-To: <m1edwj7k5c.fsf@fastmail.net>
Hi Konrad,
On Sat, 10 Sep 2022 at 09:39, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> It's worse: I wasn't even aware of being a committer before all of this
> mess. I had started preparing my patches as I do for Guix, and then I
> looked for contributor instructions. Didn't find any, so I tried the
> standard Gitlab merge request workflow, given that I have an account
> on the forge. Then I discovered that my account doesn't allow forks, and
> that I was supposed to use another workflow doing merge requests from a
> branch. That produced a merge request assigned to myself, which isn't
> really useful. Up to that point, I was convinced that I needed someone
> else to validate my patches, as for Guix.
Maybe you had been granted on July 2020 at an hackathon [1].
1: https://hpc.guix.info/blog/2020/07/reproducible-research-hackathon-experience-report/
>> remove the problematic unsigned commit. Maybe you can do it yourself,
>> push force to go back at ecfb8af08eb8aa7d7b6a4b1edcc5fb1e177fa214.
>
> As Ricardo said, force push isn't considered good behavior normally.
> But if everyone agrees that it's the best way out, I'd be happy to do
> it.
I do not know. For now, nothing is “broken” and I get:
--8<---------------cut here---------------start------------->8---
$ cat /tmp/channels.scm
(cons*
(channel
(name 'past)
(url "https://gitlab.inria.fr/guix-hpc/guix-past.git")
(branch "master"))
%default-channels)
$ guix pull -C /tmp/channels.scm -p /tmp/trash
Updating channel 'past' from Git repository at 'https://gitlab.inria.fr/guix-hpc/guix-past.git'...
guix pull: warning: pulled channel 'past' from a mirror of https://gitlab.inria.fr/guix-hpc/guix-past, which might be stale
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
Building from these channels:
guix https://git.savannah.gnu.org/git/guix.git 4f134f2
past https://gitlab.inria.fr/guix-hpc/guix-past.git e9ccdb8
…
$ /tmp/trash/bin/guix show python2-scientific
name: python2-scientific
version: 2.9.4
…
-
-8<---------------cut here---------------end--------------->8---
> I'd prefer not to. I'd probably start my own channel instead. Or
> maintain an unauthenticated fork of guix-past. My goal is to get GPG out
> of my life. It's a major source of pain.
I agree. And I think that authentication is more burden for typical
“scientific tools” than a concrete solution of a real problem.
Cheers,
simon
next prev parent reply other threads:[~2022-09-10 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun
2022-09-09 16:10 ` Konrad Hinsen
2022-09-09 17:39 ` zimoun
2022-09-10 7:39 ` Konrad Hinsen
2022-09-10 9:47 ` zimoun [this message]
2022-09-10 16:20 ` Konrad Hinsen
2022-09-11 14:07 ` Ludovic Courtès
2022-09-11 15:19 ` Efraim Flashner
2022-09-12 6:16 ` Konrad Hinsen
2022-09-12 15:26 ` Ludovic Courtès
2022-09-13 8:58 ` Konrad Hinsen
2022-09-13 9:23 ` Ricardo Wurmus
2022-09-14 9:31 ` Konrad Hinsen
2022-09-10 10:27 ` Ludovic Courtès
2022-09-10 10:40 ` zimoun
2022-09-10 14:39 ` Ricardo Wurmus
2022-09-12 16:00 ` zimoun
2022-09-09 16:16 ` Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868rmr7e81.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-science@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).