Bug 623430 – sys-cluster/teleport-2.2.1 : src/.../main.go:6:2: cannot find package gopkg.in/.../kingpin.v2 in any of:

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-07-02 08:24:22 UTC]

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-systemd_20170627-203711

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-6.3.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby21 *

[Comment 1 Toralf Förster 2017-07-02 08:24:25 UTC]

Created attachment 479312 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-07-02 08:24:29 UTC]

Created attachment 479314 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2017-07-02 08:24:32 UTC]

Created attachment 479316 [details]
environment

[Comment 4 Toralf Förster 2017-07-02 08:24:35 UTC]

Created attachment 479318 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2017-07-02 08:24:38 UTC]

Created attachment 479320 [details]
sys-cluster:teleport-2.2.1:20170702-010101.log

[Comment 6 Toralf Förster 2017-07-02 08:24:42 UTC]

Created attachment 479322 [details]
temp.tbz2

[Comment 7 Graeme Lawes 2017-07-02 13:52:36 UTC]

Opened PR to fix, but restrict tests: https://github.com/gentoo/gentoo/pull/5029

Test now successfully run, but some are failing.  I've set RESTRICT=test for now until upstream devs at Gravitational can fix it, is that the recommended course of action for failing tests?

[Comment 8 Michał Górny 2017-07-02 14:22:49 UTC]

(In reply to Graeme Lawes from comment #7)
> Test now successfully run, but some are failing.  I've set RESTRICT=test for
> now until upstream devs at Gravitational can fix it, is that the recommended
> course of action for failing tests?

Either that or disabling/removing (temporarily) the tests that fail. Of course, it's better to figure out if the failures might be valid or our fault first.

[Comment 9 Graeme Lawes 2017-07-02 14:39:22 UTC]

I see the same test failures when building outside of portage.

I have an open thread with Gravitational to investigate the failures, it's likely they will only be fixed in future versions.  I'll keep the RESTRICT=test in 2.2.0/2.2.1 and remove it from 9999, and remove it from future versions that include fixes.

[Comment 10 Michael Palimaka (kensington) 2017-09-02 15:21:41 UTC]

Thanks, PR merged.

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00bd2f9524ff99b2d17f1cc79c9d5b678e1576f7