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#40662 - [liteide] GOROOT set wrong in linux64.env

Attached to Project: Community Packages
Opened by Duane Voth (duanev) - Tuesday, 03 June 2014, 16:39 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 22 June 2014, 12:32 GMT
Task Type Bug Report
Category Upstream Bugs
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:
Any .go program built inside Liteide X22 that does an import "fmt" (or other system import) fails with:

cannot find package "fmt" in any of:
/home/duanev/go/src/pkg/fmt (from $GOROOT)
($GOPATH not set)

because GOROOT is set to $HOME/go in /usr/share/liteide/liteenv/linux*.env

GOROOT and PATH should not be set in linux*.env for the default installation.


Additional info:
* package version(s)
X22
* config and/or log files etc.


Steps to reproduce:
1) startup liteide
2) paste in some trivial go program:
----------------
package main

import "fmt"

func main() {
fmt.Printf("hello")
}
----------------
3) click "B"
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Sunday, 22 June 2014, 12:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  Implemented workaround, bug has been reported upstream.
Comment by Alexander F. Rødseth (xyproto) - Thursday, 05 June 2014, 22:05 GMT
Hi,

Thanks for reporting. This seems to be an upstream issue. Forwarded it to the liteide developers.

We can follow the progress here: https://github.com/visualfc/liteide/issues/201
Comment by Alexander F. Rødseth (xyproto) - Friday, 13 June 2014, 21:25 GMT
No reaction from upstream so far. Closing as "Upstream".
Comment by Alexander F. Rødseth (xyproto) - Sunday, 22 June 2014, 12:32 GMT
Upstream took to long, and it's an easy patch. The updated package should appear in "community" shortly.

Loading...