Hi, [...]
> One objective could be to move the surprise "left of removal" to the > point where builds are failing, in particular on team-feature > branches. > > Given a manifest and optional channel, with `guix build --dry-run` we > can obtain a list of unavailable packages. But we want to know 1) when > a substitute is unavailable and 2) the root cause, i.e. whether and > which of the package or dependencies is broken. And we cannot expect > users to continuously monitor branch state, so notifications would be > nice. That would be very nice indeed: that the responsible team for a package gets notified as soon as it is broken (on the master branch). -- Thanks, Maxim
