Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37651 - [go] The example of use message gets displayed after every upgrade of the package

Attached to Project: Community Packages
Opened by Wieland Hoffmann (Mineo) - Tuesday, 05 November 2013, 10:57 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 05 November 2013, 19:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I don't think that's really necessary. You either use the go tools and set up the environment variables after first installation or you don't use $GOPATH etc. and really don't care about it. But telling me how to set up the environment variables every single time the package gets upgraded doesn't help me.


Additional info:
* package version(s) 1.1.2-4
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Tuesday, 05 November 2013, 19:03 GMT
Reason for closing:  Fixed
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 05 November 2013, 13:48 GMT
Hi, thanks for reporting. I will fix this.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 05 November 2013, 19:03 GMT
Fixed this in subversion, the message will not appear at the next upgrade of the go package.

Loading...