Felix Lechner <[email protected]> writes:
> Hi, > > On Sun, Mar 02 2025, Adam wrote: > >> all I needed to do: >> 1) get keyring branch; >> 2) specify path to my Guix copy without "file://" > > There are potentially two bugs: > > A) Documentation: Is the need for the keyring branch, while logical, > documented? How about the illogical (and non-existing) URI scheme? Nope. We have "(guix) Using a Custom Guix Channel" in the manual, but it doesn't talk about authentication. Authenticated personal forks are not documented at all. I have an open patch series that addresses this somewhat, but a fair number of people seem to think they shouldn't be; the argument seems to be that if we present this option, people will not be incentivised to contribute changes from their forks. Personally, I set up my fork specifically so that I could format my contributions as patches from the start, which removes the friction of adapting code from channel/config to patch; I already have 15-20 comments in my Guix Home/System configs like ';; TODO submit as patch', which I'll probably never get around to doing. It was suggested that I write a GCD to present my case and achieve consensus on this topic (well, actually it was suggested because the initial revision of my patch series added a new subcommand; I dropped that in the v2, but I still need consensus anyway...). I have yet to find the motivation to write it - we're talking about writing thousands of words summarizing the entire issue of authenticated forks, just so that I can have the patch series that I've already spent tens of hours on and am already using accepted upstream. Maybe I'll do it at some point, but it's not looking too likely in the near future. If anyone's interested in this issue, here is the latest revision of my patch series: https://yhetil.org/guix/[email protected]/ You should be able to find links to all previous discussions in the patch cover letters. > B) Diagnostics: Can the error message be improved to prevent the > recurrence of this issue on this mailing list? > > Somebody, please file them. Thanks! Potential third bug: every time I commit to and pull from my local fork, I get the 'fetching objects' and 'indexing objects' progress bars and it takes a long time, comparable to the time taken by the initial `guix pull`. This didn't happen when I was using %default-guix-channel. I suspect it may be doing a fresh clone of my local fork each time (though I'm not sure how I'd confirm this).
