dev-dotnet/nuget-2.8.{1,3} fails to emerge

[zetok]

emerge --info & build.log → https://gist.github.com/zetok/80ab119cd159bdb90e16

[Cynede]

Mono, Version 2.10.9.0

this mono version is way to old, I will update ebuild

Thank you for report

[zetok]

Still fails to build with mono 3.2.8: https://gist.github.com/zetok/64ccb33bb9acc767ae01

[Cynede]

@zetok strange about WARNING: Error: NameResolutionFailure

[Cynede]

May you try this before running emerge

certmgr -ssl -m https://go.microsoft.com
certmgr -ssl -m https://nugetgallery.blob.core.windows.net
certmgr -ssl -m https://nuget.org

If this will help then I will add it to ebuild

[zetok]

$ certmgr -ssl -m https://go.microsoft.com
Mono Certificate Manager - version 3.2.8.0
Manage X.509 certificates and CRL from stores.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.


X.509 Certificate v3
   Issued from: C=IE, O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root
   Issued to:   C=US, S=Washington, L=Redmond, O=Microsoft Corporation, OU=Microsoft IT, CN=Microsoft IT SSL SHA2
   Valid from:  2013-12-19 20:07:32
   Valid until: 2017-12-19 20:06:55
   *** WARNING: Certificate signature is INVALID ***
Import this certificate into the CA store ?

Is this really ok?

[zetok]

Also, wouldn't adding that to ebuild conflict with FEATURES="network-sandbox"?

[Cynede]

yes, it's strange http://www.mono-project.com/docs/faq/security/

[Cynede]

@zetok may you also try it with mono 3.12.1

[zetok]

Will try with 3.12.1

[zetok]

strange about WARNING: Error: NameResolutionFailure

actually it's not strange; anything that tries to use network when emerging stuff fails when network-sandbox is set

Since ebuild doesn't appear to do this, i.e.:

src_compile() {
#   xbuild Build/Build.proj /p:Configuration=Release /p:TreatWarningsAsErrors=false /tv:4.0 /p:TargetFrameworkVersion="v${FRAMEWORK}" /p:Configuration="Mono Release" /t:GoMono || die
    source ./build.sh || die
}

proper solution would be to bug upstream / patch source to not use network when building

[zetok]

still fails to emerge with mono-3.12.1-r1

[Cynede]

@zetok yes, seems like something is wrong with certificates there but I wonder why this problem appears only for you...

[zetok]

FEATURES="${FEATURES} -network-sandbox" emerge -avt1 nuget

↑ works.

proper solution would be to bug upstream / patch source to not use network when building

It really shouldn't use network when building…

[kentfredric]

Still happening with nuget 2.8.3 + mono 3.12.1

That it appears to be fetching content during installation is very bad.

<somepath>Build/Build.proj: error : Command 
'mono <somepath>NuGet.exe restore -source "https://www.nuget.org/api/v2/"'
 exited with code: 1.  

As is all this:

                Unable to find version '4.1.1309.0919' of package 'Moq'.
                Unable to find version '2.2.1.4' of package 'Ninject'.
                Unable to find version '1.9.2' of package 'xunit'.
                Unable to find version '1.9.2' of package 'xunit.extensions'.
                Unable to find version '1.2.2' of package 'elmah'.
                Unable to find version '1.2.2' of package 'elmah.corelibrary'.
                Unable to find version '1.0.0.0' of package 'Microsoft.Web.Infrastructure'.
                Unable to find version '3.0.0.15' of package 'Ninject'.
                Unable to find version '1.2' of package 'RouteMagic'.
                Unable to find version '2.0.2' of package 'WebActivatorEx'.

[ArsenShnurkov]

I see xUnit in the list of dependencies - https://github.com/gentoo/dotnet/issues/110

[Cynede]

may you try with this https://github.com/gentoo/dotnet/commit/d30863fb33c5ab0cdd7d587918a5c22eb9bc6203 and recent mono bump, reopen please if it will happen again

[zetok]

Please reopen, it's still reproducible with dev-dotnet/nuget-2.8.3