On 11/1/26 10:38, Sergio Pastor Pérez wrote:
Hugo Buddelmeijer <[email protected]> writes:

It printed the correct dependency; the detection was a false positive,
since that specific dependency was not going to be removed.

This is the output of 0.0.2, when ran on
49cdea04fcc93c7023e0a6b96384b1d1c0f34c86, the commit of #12231:

• #12073 Post merge go-team cleanups 2026/10. 🕓 Scheduled in 13 days
    ...
    - go-github-com-rogpeppe-go-internal-1.14
    ...

Affected packages (16):
• git-spice
    - go-github-com-rogpeppe-go-internal-1.14
• shfmt
    - go-github-com-rogpeppe-go-internal-1.14
...

None of the packages I checked are actually affected.

We must not be reading the same things, because those packages *are*
affected.
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.

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.

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?


Reply via email to