https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c2 --- Comment #2 from Duncan Mac-Vicar 2011-12-07 11:57:03 UTC --- I fixed it for openSUSE 12.1 as well. Actually it is very bad that devel:languages:go go package is tracking something newer than the 60.x release as until Go1 it will be a moving target and no package will ever build. Very basic stuff like os.Error was changed. If users want to contribute packages, they will have a hard time building them against a moving target. I recommend to keep devel:languages:go with r60.x until Go1 is released. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c4 --- Comment #4 from Bernhard Wiedemann 2011-12-07 13:00:08 CET --- This is an autogenerated message for OBS integration: This bug (735288) was mentioned in https://build.opensuse.org/request/show/95719 12.1 / go -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c5 --- Comment #5 from Sascha Peilicke 2011-12-07 13:20:43 UTC --- Thanks for spotting that. I accepted your request to d:l:g and forwarded to Factory. (In reply to comment #2)

Actually it is very bad that devel:languages:go go package is tracking something newer than the 60.x release as until Go1 it will be a moving target and no package will ever build. Very basic stuff like os.Error was changed. Yep, currently a lot in d:l:g is broken. Until now, this was the case for almost every Go update we made.

If users want to contribute packages, they will have a hard time building them against a moving target. I recommend to keep devel:languages:go with r60.x until Go1 is released. Graham and me are still able to port stuff that got broke in the meantime, so

But waiting for upstream packages to adjust wont happen. Some upstream packages aren't developed any further, others immediately catch the most recent changes from Go. Thus we're fixing them one by one and submit stuff upstream. there's no real issue here yet. Go is a moving target and will be even after Go1, such is Factory. Thus, I submitted a whole bunch of Go packages to 12.1 in order to have a stable version. I agree, once Go1 is there, we may want to change that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c7 --- Comment #7 from Duncan Mac-Vicar 2011-12-07 16:18:11 UTC --- (In reply to comment #5)

Graham and me are still able to port stuff that got broke in the meantime, so there's no real issue here yet. Go is a moving target and will be even after Go1, such is Factory. Thus, I submitted a whole bunch of Go packages to 12.1 in order to have a stable version. I agree, once Go1 is there, we may want to change that.

One way to minimize the effort is to simply to run gofix ./ in the %prep or %build section. If you update the compiler and a library is not yet updated, it will be fixed automatically. This could be even standard in the %go_make_install macro. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c9 --- Comment #9 from Duncan Mac-Vicar 2011-12-08 09:44:18 UTC --- (In reply to comment #8)

You haven't used it yet, I guess? I agree with you, it used to catch most cases

Yes I used it.

but wasn't updated much recently, even the boldest moves (like the mentioned os.Error or template pkg) aren't taken care of. Nope, porting remains a manual task.

Not true /usr/share/go/src/cmd/gofix/error.go /usr/share/go/src/cmd/gofix/template.go For me the only stuff it did not handle correctly was deprecating container/vector and something related to FileWalker.

...

This could be even standard in the %go_make_install macro. Won't help, see above.

Anyways, waiting for Go1 is not an option, but waiting for the next major release (like r60.4) and not updating to weekly releases (happened only once in a while anyways) may be worth giving a try. How does that sound to you?

For the few packages I am adding to my home project, most of them are not working with weekly. I am adding a gofix ./, and if they work with weekly then, I will submit to d:l:g. I don't expect to package anything that does not build with weekly doing the port myself anyways. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=735288 https://bugzilla.novell.com/show_bug.cgi?id=735288#c11 Duncan Mac-Vicar changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bbrunner@suse.com --- Comment #11 from Duncan Mac-Vicar 2011-12-20 15:04:41 UTC --- Can I close this already? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=735288 SMASH SMASH changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:planned:update | -- You are receiving this mail because: You are on the CC list for the bug.