>> Though I have had reports from confused users at work who say that “guix
>> upgrade” doesn’t necessarily help, and that they actually had to use
>> “guix install” on all packages again. I haven’t been able to confirm
>> this yet.

I had that problem, too. It’s why I switched to manifests: I could not
upgrade, but had to add more and more packages to the upgrade, maybe
choosing different versions to get them consistent.

I think that it was because guix upgrade keeps some version information,
so it might have too strict constraints when calculating the next
possible state.

Then I get something like "package conflict: dbus5 in profile and dbus4
pulled in by emacs". (not actual version numbers, this is just an example)

I’d like to have the situation where I can just say `guix upgrade emacs`
and guix calculates all affected packages recursively, resolving version
conflicts by itself to find the set of packages that need to be upgraded.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de