Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 507844 - dev-python/pivy-9999 - failed to clone http://hg.sim.no/Pivy/default (No route to host)
Summary: dev-python/pivy-9999 - failed to clone http://hg.sim.no/Pivy/default (No rout...
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Michael Weber (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-16 18:47 UTC by Alec Ten Harmsel
Modified: 2018-11-25 10:38 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alec Ten Harmsel 2014-04-16 18:47:36 UTC
The ebuild tries to clone with mercurial from a dead link. It should (I believe) clone from https://bitbucket.org/Coin3D/pivy. There has been a lastrite request for pivy as development stopped a while ago, but it was RESOLVED WONTFIX.FreeCAD (media-gfx/freecad) still depends on pivy.

portage output:

>>> Emerging (1 of 3) dev-python/pivy-9999
>>> Unpacking source...
 * Cloning http://hg.sim.no/Pivy/default to /usr/portage/distfiles/hg-src/pivy/default
abort: error: No route to host
 * ERROR: dev-python/pivy-9999::gentoo failed (unpack phase):
 *   failed to clone http://hg.sim.no/Pivy/default
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_unpack
 *   environment, line 3413:  Called mercurial_src_unpack
 *   environment, line 2317:  Called mercurial_fetch
 *   environment, line 2297:  Called die
 * The specific snippet of code:
 *               die "failed to clone ${EHG_REPO_URI}"
 * 
 * If you need support, post the output of `emerge --info '=dev-python/pivy-9999::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/pivy-9999::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-python/pivy-9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/pivy-9999/temp/environment'.
 * Working directory: '/usr/portage/distfiles/hg-src/pivy'
 * S: '/var/tmp/portage/dev-python/pivy-9999/work/pivy-9999'

>>> Failed to emerge dev-python/pivy-9999, Log file:

>>>  '/var/tmp/portage/dev-python/pivy-9999/temp/build.log'
 * Messages for package dev-python/pivy-9999:
 * ERROR: dev-python/pivy-9999::gentoo failed (unpack phase):
 *   failed to clone http://hg.sim.no/Pivy/default
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_unpack
 *   environment, line 3413:  Called mercurial_src_unpack
 *   environment, line 2317:  Called mercurial_fetch
 *   environment, line 2297:  Called die
 * The specific snippet of code:
 *               die "failed to clone ${EHG_REPO_URI}"
 * 
 * If you need support, post the output of `emerge --info '=dev-python/pivy-9999::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/pivy-9999::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-python/pivy-9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/pivy-9999/temp/environment'.
 * Working directory: '/usr/portage/distfiles/hg-src/pivy'
 * S: '/var/tmp/portage/dev-python/pivy-9999/work/pivy-9999'
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2018-11-25 10:38:17 UTC
ENOSUCHPKG