[MacPorts] #57457: Travis CI: Sometimes declared dependencies aren't installed
MacPorts
noreply at macports.org
Tue Jun 4 02:00:05 UTC 2019
#57457: Travis CI: Sometimes declared dependencies aren't installed
-----------------------------+---------------------
Reporter: ryandesign | Owner: admin@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: server/hosting | Version:
Resolution: | Keywords:
Port: |
-----------------------------+---------------------
Comment (by ryandesign):
In src/macports1.0/macports.tcl we have:
{{{
# Determine dependency types required for target
proc macports::_deptypes_for_target {target workername} {
switch -- $target {
}}}
{{{
install -
activate -
{} {
if {[global_option_isset ports_binary_only] ||
[$workername eval {registry_exists $subport $version
$revision $portvariants}]
|| (![global_option_isset ports_source_only] &&
[$workername eval {_archive_available}])} {
return "depends_lib depends_run"
} else {
return "depends_fetch depends_extract depends_patch
depends_build depends_lib depends_run"
}
}
}}}
If an archive hasn't already been downloaded, `[$workername eval
{_archive_available}]` uses curl to check if an archive is available on
the server. I think the problem is that the Travis network connection was
unavailable briefly—while we were running `port archivefetch` (all
attempts to download an archive failed) and when we started running `port
fetch` (the first distfile download attempt failed; the second one
succeeded). By the time we ran `port install` the network was back up so
it could see that an archive was available so it only added lib and run
dependencies, but by that point we had already marked the archivefetch
phase as complete so we tried a source build which failed because the
build dependencies weren't there.
--
Ticket URL: <https://trac.macports.org/ticket/57457#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list