Re: Build: win64: Package 'mingw-w64-dev' has no installation candidate

Re: Build: win64: Package 'mingw-w64-dev' has no installation candidate
From: Roy Osherove @ 2015-09-27  8:37 UTC (permalink / raw)
  To: Bitcoin Dev

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

Hi All
As part of trying to learn more about the bitcoin builds, I am trying to
recreate the travis CI build system using TeamCity.
Some of the builds work fine, but the windows builds seem to be having a
problem with getting mingw dev:

[08:31:21][Step 3/3] E: Package 'mingw-w64-dev' has no installation
candidate

I'm using the same exports env vars as the travis script, and actually
using the travis script inside teamcity , incuding adding the PPA for the
mingw packages.

The PPA seems to be importing fine during the build:
[Step 3/3] gpg: keyring `/tmp/tmp_nolyfrh/secring.gpg' created
[08:30:48][Step 3/3] gpg: keyring `/tmp/tmp_nolyfrh/pubring.gpg' created
[08:30:48][Step 3/3] gpg: requesting key F9CB8DB0 from hkp server
keyserver.ubuntu.com
[08:30:48][Step 3/3] gpg: /tmp/tmp_nolyfrh/trustdb.gpg: trustdb created
[08:30:48][Step 3/3] gpg: key F9CB8DB0: public key "Launchpad PPA for
Ubuntu Wine Team" imported
[08:30:48][Step 3/3] gpg: no ultimately trusted keys found
[08:30:48][Step 3/3] gpg: Total number processed: 1
[08:30:48][Step 3/3] gpg: imported: 1 (RSA: 1)

Any ideas why this seems to be working on travis and not on the teamcity
build agent?
The agent is running inside  docker image based on ubuntu.

The full log of the failed build can be found at :
http://btcdev.osherove.com:8111/viewLog.html?tab=buildLog&buildTypeId=Bitcoin_BuildWin64&buildId=332#_state=103&focus=242

same problem appears in win32 build.
there are the env vars:

NameValue passed to buildenv.BASE_OUTDIR%system.teamcity.build.checkoutDir%
env.BITCOIN_CONFIG--enable-gui --enable-reduce-exportsenv.BOOST_TEST_RANDOM
%build.number%env.CCACHE_COMPRESS1env.CCACHE_SIZE100Menv.CCACHE_TEMPDIR
/tmp/.ccache-tempenv.GOALdeployenv.HOSTx86_64-w64-mingw32env.MAKEJOBS-j2
env.PACKAGESnsis gcc-mingw-w64-x86-64 g++-mingw-w64-x86-64
binutils-mingw-w64-x86-64 mingw-w64-dev wine1.7 bcenv.PPAppa:ubuntu-wine/ppa
env.PYTHON_DEBUG1env.RUN_TESTStrueenv.SDK_URL
https://bitcoincore.org/depends-sources/sdksenv.WINEDEBUG

-- 
Thanks,

Roy Osherove

   - *@RoyOsherove* <https://twitter.com/RoyOsherove>
   - Read my new book *Notes to a Software Team Leader
<http://TeamLeadSkills.com>*
   - Or *my new course* about Beautiful Builds <http://courses.osherove.com>
and Continuous Delivery
   - +1-201-256-5575
    - Timezone: Eastern Standard Time (New York)

[-- Attachment #2: Type: text/html, Size: 12711 bytes --]

 permalink raw reply	[|nested]


  
From: Roy Osherove @ 2015-09-29  6:09 UTC (permalink / raw)
  To: Joseph Bisch;  Bitcoin Dev

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

Ah, I didn't notice, thanks!

On Mon, Sep 28, 2015 at 7:23 PM, Joseph Bisch <joseph.bisch@gmail•com>
wrote:

> Hi Roy,
>
> It looks like your TeamCity setup is using Ubuntu Trusty to perform
> the build. Travis CI is using Ubuntu Precise instead[0]. The
> mingw-w64-dev package is only available in Precise[1]. It looks like
> that package was split into mingw-w64-x86-64-dev and
> mingw-w64-i686-dev, so those are what have to be used with Ubuntu
> Trusty.
>
> [0] - http://docs.travis-ci.com/user/ci-environment/
> [1] - http://packages.ubuntu.com/precise/mingw-w64-dev
> [2] - http://packages.ubuntu.com/trusty/mingw-w64-x86-64-dev
> [3] - http://packages.ubuntu.com/trusty/mingw-w64-i686-dev
>
> Cheers,
> Joseph
>



-- 
Thanks,

Roy Osherove

   - *@RoyOsherove* <https://twitter.com/RoyOsherove>
   - Read my new book *Notes to a Software Team Leader
<http://TeamLeadSkills.com>*
   - Or *my new course* about Beautiful Builds <http://courses.osherove.com>
and Continuous Delivery
   - +1-201-256-5575
    - Timezone: Eastern Standard Time (New York)

[-- Attachment #2: Type: text/html, Size: 2125 bytes --]

 permalink raw reply	[|nested]