FWIW, with go 1.26 in unstable, I reverted these hacks and used a simple
B-D on golang-any (>> 2:1.25~) for Nebula.  Thanks all for ideas, maybe
this concern will come up in the future again, and then this can serve
as a useful source of ideas.

This could suggest that we should push 'golang-defaults' updates for new
upstreams into experimental early.  Then I could just have used the
"proper" approach from the beginning, putting Nebula into experimental
pending that everything is uploaded to unstable.

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to