http://bugzilla.suse.com/show_bug.cgi?id=1114209 http://bugzilla.suse.com/show_bug.cgi?id=1114209#c5 --- Comment #5 from Aleksa Sarai <asarai@suse.com> --- (In reply to Jeff Kowalczyk from comment #3)
What sequence of events will happen before OBS builds of the updated go metapackage start clearing the 'unresolvable' error?
Does each affected SUSE/openSUSE distribution make and accept request(s) to update a package in preparation for a release milestone, then when the next full release lands (date TBD) OBS updates its repositories?
Or, do the distributions have configured repositories of in-development packages that will be seen by OBS during builds?
For the main distributions, they'd need to be accepted everywhere. However, practically speaking, by submitting to Factory and SLE it will get auto-forwarded to Leap (in most cases -- @Jordi, is this true of the Go packages?). But individual projects can add the repository to OBS so that it's built on top of devel:languages:go -- this is what we do for Virtualization:containers (from memory). But I've already included the devel:languages:go change into SLE, because we needed it for Docker (we should probably have a discussion over how the hand-off to you for maintaining Go within SLE should work -- historically the container team has done this). -- You are receiving this mail because: You are on the CC list for the bug.