Am Donnerstag, dem 16.01.2025 um 00:01 +0100 schrieb Tomas Volf:
> Liliana Marie Prikler writes:
>
> > I think you're making this more complicated than it needs to be.
> > checkout, authenticate, rebase*, merge* ought to have you covered.
> >
> > * you can authenticate after these if you're par
Liliana Marie Prikler writes:
> I think you're making this more complicated than it needs to be.
> checkout, authenticate, rebase*, merge* ought to have you covered.
>
> * you can authenticate after these if you're paranoid
>
>> We could create a script to do all the steps for us, but if and wh
Ok that fixed it.
The issue was this one line. Thanks for showing me your example. Shepherd's
logs showed gpg-agent launching fine. I just had the incorrect file-append
incantation. Presumably pinentry is a symbol inside of the
home-environment.services.service context.
;; incorrect
(pinentry-pro
On Mon, Jan 13, 2025 at 01:10:11PM -0800, Andy Tai wrote:
> Hi, I run into a situation where every time I do
>
> guix pull
>
> the guix command seg faults. I think this was due to a change last year
> that was causing the guix command to crash and then a quick note was issued
> from the guix tea
Hi,
Am Mittwoch, dem 15.01.2025 um 15:48 + schrieb 45mg:
> The idea of authentication is that once you trust the channel
> introduction, you can be sure that everything you pull after that is
> authentic. The introduction only needs to be trusted once. If you're
> bumping the introduction ever
i haven't read the entire thread [sorry], but with that in mind here's how i'm
solving this:
i have various branches where i keep my not-yet-merged work. i also have a
script that creates/overwrites a branch (called 'attila', starting at the tag
'attila-baseline') and cherry picks everything in
Hi Liliana!
Liliana Marie Prikler writes:
> For most use cases, this is a non-issue. Assuming you are a single
> committer to your fork, you can always rebase your changes on top of
> Guix (if you're willing to bump the introductory commit)
The idea of authentication is that once you trust the
Tomas Volf <~@wolfsden.cz> writes:
> Since the home-gpg-agent-service-type does not set the `extend' field, I
> conclude the service cannot be extended.
>
> However the fact that it does not signal an error is (in my opinion) a
> bug and you should report it.
Thanks for jogging my memory! I belie
> *Troubleshooting*
>
> I've tried all the commands I can think of to launch the gpg agent. It's
> just not happening.
>
> guix home reconfigure home-config.scm
> gpg --list-keys
> gpgconf --kill gpg-agent
>
> herd status shows that the gpg-agent service has started.
>
> herd status
> Started:
> +
Am Dienstag, dem 14.01.2025 um 04:21 + schrieb 45mg:
> --8<---cut here---start->8---
> When authenticating merge commits, intersection of authorized keys
> from all parents is used. That is fine in Guix proper, since all
> involved commits are under the contr
10 matches
Mail list logo
