divoplade writes:
> Le vendredi 09 avril 2021 à 15:52 +0200, Ricardo Wurmus a écrit :
>> I’m saying that for public
>> channels it’s the wrong workflow as it results in rewritten history.
>
> My channels aren’t public (they are git repos on the file system), but
> I fail to understand how it ma
Le vendredi 09 avril 2021 à 15:52 +0200, Ricardo Wurmus a écrit :
> I’m saying that for public
> channels it’s the wrong workflow as it results in rewritten history.
My channels aren’t public (they are git repos on the file system), but
I fail to understand how it makes a difference. Maybe the
mis
divoplade writes:
> Hello,
>
> Le vendredi 09 avril 2021 à 14:21 +0200, Ricardo Wurmus a écrit :
>> > I have a couple of channels that get rebased constantly.
>>
>> This seems like a broken workflow. Why would they be rebased
>> constantly, which results in rewritten history?
>
> Sorry, I don
Hello,
Le vendredi 09 avril 2021 à 14:21 +0200, Ricardo Wurmus a écrit :
> > I have a couple of channels that get rebased constantly.
>
> This seems like a broken workflow. Why would they be rebased
> constantly, which results in rewritten history?
Sorry, I don’t know how to respond to that. Of
divoplade writes:
> I have a couple of channels that get rebased constantly.
This seems like a broken workflow. Why would they be rebased
constantly, which results in rewritten history?
--
Ricardo
Dear guix,
I have a couple of channels that get rebased constantly. Is there a way
to tell guix that a channel allows downgrades, in a way that can also
be used by the unattended upgrade service? Also, if a package has a
git-fetch origin, the daemon will check that future versions are direct
desce
