From: John Soo <jsoo1@asu.edu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41604@debbugs.gnu.org
Subject: bug#41604: guix pull impossible after rebasing a local repository
Date: Fri, 29 May 2020 19:26:32 -0700 [thread overview]
Message-ID: <87ftbinoo7.fsf@asu.edu> (raw)
In-Reply-To: <CAJ3okZ0kUQRPcxx9oexdCHFdJnAV19KQQGXZuiikut6wrKT2Cw@mail.gmail.com> (zimoun's message of "Fri, 29 May 2020 20:39:23 +0200")
Hello,
zimoun <zimon.toutoune@gmail.com> writes:
> Is "guix pull --commit=1444040933 --allow-downgrades" not working for you?
Yeah guix pull --commit=1444040933 --allow-downgrades failed.
> What do you mean? An option for you or an option of "guix pull"?
> Ah my bad, it is "--roll-back". The double "--roll-back" and
> "--rollback" options is only allowed with "guix package". Thank you
> for the notification. :-)
Ah, nice! roll-back helped me work around the problem. Very helpful,
thanks!
> Hehe! Dangerous zone. :-)
I think I found that out, haha!
> Personally, I keep clean ~/.config/guix/current by always pulling from
> origin/master.
> Then I have, as you, a local clone where I rebase, commit etc. But I
> only pull to another profile than the default one, to avoid similar
> situations as you currently are. ;-)
>
> /path/to/what-i-mean/bin/guix pull --url=/pah/local/clone
> --branch=kikoo -p /path/to/next
>
> and I have some channels files under ~/.config/guix/ to simply some
> regular, e.g.,
>
> guix pull -C ~/.config/guix/extra.scm -p /path/to/extra
> /tmp/extra/bin/guix install foo -p /tmp/test
>
> And so "guix pull" always works.
> Anyway! :-)
Nice! I like the idea of having a "next" profile.
I guess that makes me wonder what the desired specification is.
There is a lot of problem space to explore. As a user I would want to
be able to take my local patches as "the real truth".
Because guix has a linear git history, that means the user needs to
always rebase. Often I have patches open for months that I am currently
testing and working on. It would be convenient for me to be able to guix
pull into my default user profile.
On the other hand, as you point out, using a hash that disappears from
the git history is dangerous. The git history no longer tracks the guix
pull history and then there may exist pulls in history that may never be
recoverable.
There seems to be some existing support for the rebasing into the
default profile since branches are allowed as references in the channels
configuration. Has the rebase use case been discussed before? Oh, also,
history items can be deleted in other places with --delete-generations
and friends. I am not sure what to classify this problem, bug or
something else.
What do you think?
- John
next prev parent reply other threads:[~2020-05-30 2:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 16:38 bug#41604: guix pull impossible after rebasing a local repository John Soo
[not found] ` <handler.41604.B.159077032116756.ack@debbugs.gnu.org>
2020-05-29 16:41 ` bug#41604: Acknowledgement (guix pull impossible after rebasing a local repository) John Soo
2020-05-29 16:52 ` bug#41604: guix pull impossible after rebasing a local repository zimoun
2020-05-29 17:10 ` John Soo
2020-05-29 17:44 ` zimoun
2020-05-29 18:22 ` John Soo
2020-05-29 18:39 ` zimoun
2020-05-30 2:26 ` John Soo [this message]
2020-05-30 10:45 ` zimoun
2020-05-30 16:18 ` Arne Babenhauserheide
2020-05-31 5:04 ` John Soo
2020-06-01 16:48 ` zimoun
2020-06-01 17:28 ` John Soo
2020-06-01 16:35 ` zimoun
2020-06-03 9:28 ` Ludovic Courtès
2020-06-03 13:44 ` John Soo
2020-06-03 15:13 ` Ludovic Courtès
2020-06-04 14:11 ` John Soo
2020-06-05 1:44 ` zimoun
2020-06-05 16:13 ` Ludovic Courtès
2020-06-05 1:23 ` zimoun
2020-06-05 16:17 ` Ludovic Courtès
2020-06-05 17:51 ` zimoun
2020-06-07 21:16 ` Ludovic Courtès
2020-06-07 22:25 ` zimoun
2020-06-07 23:52 ` John Soo
2020-06-10 14:51 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftbinoo7.fsf@asu.edu \
--to=jsoo1@asu.edu \
--cc=41604@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.