Hugo Buddelmeijer <[email protected]> writes: > Yes you are right thanks; I got my guix versions mixed up. > > $ guix shell --pure guix -- \ > guix graph --path git-spice [email protected] > [email protected] > [email protected] > > I suppose guix time-machine is really necessary to use it properly with > multiple channels.
Well, you can use `guix edit ...` when you are not using the time-machine to be sure which are your current sources, I use that trick quite a lot actually. > I still get confused which Guix version I'm using when combining > ./pre-inst-env, shell, time-machine, etc. Maybe I'll write a definitive > cheat sheet some time. Yes, it's can get convoluted. > Hmm: > > • #12250 teams: Remove Divya Ranjan Pattanaik. 🕓 Scheduled in 19 days > > Maybe you could skip the P.R.s that do not actually deprecate/remove a > package? I think the we should stop using the `deprecation` labels for things that are not meant to be deprecations. Even if the PR doesn't drop a package, it's probably interesting to display if it's really related to a "deprecation". I would suggest not using the label for things that are not of that nature, such as adjusting team members. Going forward, it will be easier to develop more tools if we have clear uses of the different labels. Best regards, Sergio
