Re: [package - 103amd64-default][lang/mono] Failed for mono-5.2.0.215 in build

Hmmm, this is strange failure. This error name came up during testing. This may be a transient failure. Let's monitor the failures for more information... On Thursday, 1 February 2018 01:40:34 pkg-fall...@freebsd.org wrote: > CSC [net_4_x] Mono.CompilerServices.SymbolWriter.dll >

Mono 5.2.0.215 in ports!

/tag/mono/ [3] https://reviews.freebsd.org/D12440 On Tuesday, 30 January 2018 19:00:28 David Naylor wrote: > Author: dbn > Date: Tue Jan 30 19:00:27 2018 > New Revision: 460430 > URL: https://svnweb.freebsd.org/changeset/ports/460430 > > Log: > lang/mono: update to version 5

Re: Mono 5.2 patch and DotNet Core 2 update

On Thursday, 11 January 2018 21:48:27 Russell Haley wrote: > David. I assume MSBuild and Roslyn are in > progress? I haven't touched MSBuild and Roslyn. I want to get mono and linux-dotnet into Ports first. Speaking of mono: - I've updated the patch on Phabricator - distinfo has been fixed

Re: Mono 5.2 patch and DotNet Core 2 update

On Wednesday, 3 January 2018 21:46:39 Russell Haley wrote: > On Wed, Jan 3, 2018 at 11:41 AM, David Naylor <naylor.b.da...@gmail.com> wrote: > > On Tuesday, 2 January 2018 22:17:19 Aaron Havens wrote: > >> On Sun, Dec 31, 2017 at 12:31 AM, Russell Haley <russ.

Re: Update on porting mono 5

On Monday, 13 November 2017 23:11:03 David Naylor wrote: > In the interim, I tried my hand at my own exp-run [1][2][3]. And things > didn't go well (well the exp-run was a success, but the results...). > > It appears that somehow the assemblies are being delay signed during buil

Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

On Wednesday, 8 November 2017 22:59:56 Russell Haley wrote: > On Wed, Nov 8, 2017 at 10:15 AM, David Naylor <naylor.b.da...@gmail.com> wrote: > > On Wednesday, 27 September 2017 22:02:43 Russell Haley wrote: > >> +1 > >> I threw some comments on the open is

Re: Update on porting mono 5

On Thursday, 21 September 2017 22:20:54 David Naylor wrote: > Hi > > A quick update on the update to mono5. In theory everything should be > working (i.e. mono, monodevelop, etc). > > A review has also been created (so you can access the patch). Please tes

Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

On Wednesday, 27 September 2017 22:02:43 Russell Haley wrote: > +1 > I threw some comments on the open issues. Hi I hope the porting of .NET Core has been progressing. I must apologise, I have dropped the ball on updating mono. This will come with a working version of msbuild which I am sure

Re: DotNet Core 2.0 - Status Update

On Sunday, 24 September 2017 23:36:32 Russell Haley wrote: > Hey, > > *This is my understanding of what's going on and I am looking for > Tomas or Karel to correct or clarify. > > I've continued poking around on the build to little effect so far. > Tomas has said there is an update to the

Re: Update on porting mono 5

On Monday, 25 September 2017 23:35:04 Russell Haley wrote: > Sorry, hit send in gmail somehow. :-/ > > Hi David, > > So, point 1: I suck at patching. I'm going to re-attempt when I'm not > so tired with a fresh ports from svn. > > tldr; I think I failed to apply the patch, but the build started

Re: Update on porting mono 5

Hi A quick update on the update to mono5. In theory everything should be working (i.e. mono, monodevelop, etc). A review has also been created (so you can access the patch). Please test it. https://reviews.freebsd.org/D12440 Regards On 25 August 2017 at 21:41, David Naylor <naylor.b

Re: Update on porting mono 5

On Tuesday, 5 September 2017 13:09:14 Russell Haley wrote: > On Tue, Sep 5, 2017 at 12:25 PM, David Naylor <naylor.b.da...@gmail.com> wrote: > > On Saturday, 2 September 2017 07:40:28 Russell Haley wrote: > >> On Sat, Sep 2, 2017 at 4:55 AM, Robert Alegrid <eraleg...

Re: Update on porting mono 5

On Saturday, 2 September 2017 07:40:28 Russell Haley wrote: > On Sat, Sep 2, 2017 at 4:55 AM, Robert Alegrid wrote: > >>Another problem with nugets packages is that you only get binaries, > >>right? That means that is something goes really wrong, there is no way > >>to

Re: Update on porting mono 5

, welcome to the list. > I also just program as a hobby (and mostly on Windows at that), so that > should be taken in consideration as well. > > On Saturday, 2 September 2017 7:03 PM, Romain Tartière wrote: > >On Fri, Aug 25, 2017 at 09:41:43PM +0200, David Naylor wrote: > >

Re: Update on porting mono 5

On Saturday, 2 September 2017 11:03:59 Romain Tartière wrote: > On Fri, Aug 25, 2017 at 09:41:43PM +0200, David Naylor wrote: > > [2] A general discussion needs to be had around nuget packages. How do we > > consume them? > > > > i) as downloads with each port cont

Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

On Tuesday, 5 September 2017 20:52:10 David Naylor wrote: > On Monday, 4 September 2017 10:54:21 Geoffrey Huntley wrote: > > See https://www.youtube.com/watch?v=NHllisWOCpU and > > https://twitter.com/GeoffreyHuntley/status/904227946084294656 > > Hi Geoffrey > > It is

Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

On Monday, 4 September 2017 10:54:21 Geoffrey Huntley wrote: > See https://www.youtube.com/watch?v=NHllisWOCpU and > https://twitter.com/GeoffreyHuntley/status/904227946084294656 Hi Geoffrey It is great to hear there is more interest in finishing the port of .NET Core to FreeBSD (and, I hope,

Re: Update on porting mono 5

On Friday, 25 August 2017 12:54:02 Russell Haley wrote: > On Fri, Aug 25, 2017 at 12:41 PM, David Naylor <naylor.b.da...@gmail.com> wrote: > > On Tuesday, 15 August 2017 12:21:20 Romain Tartière wrote: > >> Hi David, > >> > >> On Tue, Aug 15, 20

Re: Update on porting mono 5

On Tuesday, 15 August 2017 12:21:20 Romain Tartière wrote: > Hi David, > > On Tue, Aug 15, 2017 at 09:11:57AM +0200, David Naylor wrote: > > Here is an update on porting mono 5: > > - mono: 5.1.0.1 (needs to be updated to 5.2, tests run) > > - msbuild: 15.3 (needs tes

Update on porting mono 5

Hi Here is an update on porting mono 5: - mono: 5.1.0.1 (needs to be updated to 5.2, tests run) - msbuild: 15.3 (needs tests ported and run, upstream bugs filed) - fsharp: 4.1.25 (WIP) - monodevelop: 7.0.1.24 (WIP) - gtksharp20: 2.12.45 (WIP) - avahi-sharp: 0.7 (not started) - bumping all

Re: Is there any reason Mono 5 is not yet available in ports?

On Friday, 7 July 2017 06:20:06 Paul Webster wrote: > I just wondered could not find anything on google I had created an initial port (see mailing list) for mono 5 and everything seemed to work. There does not appear to be any technical limitation. I (and the rest of the mono team) haven't

Mono updated to 4.6.2.7 and call to help with dotnet

Hi With commit r427247 the following updated are now in Ports: - Mono: 4.6.2.7 - MonoDevelop: 4.1.2.44 - FSharp: 4.0.1.20 - Gtk-Sharp20: 2.12.42 And, the call to help: We are trying to create a port for .NET Core [1] and there are various ways you could contribute: 1) Help investigate

Mono updated to 4.6.1.5

Hi With commit r424974 the following updates are now in Ports: - Mono: 4.6.1.5 - MonoDevelop: 6.1.1.15 (and now compiling/running) - FSharp: 4.0.1.15 - Mono-basic: 4.6 - GTK-Sharp20: 2.12.40 Note that gecko-sharp20 is now depreciated. If you use this port please let us know. And,

Re: state of devel/monodevelop ?

On Sunday, 23 October 2016 19:47:13 René Ladan wrote: > Hi, Hi > the devel/monodevelop port expired over half a year ago and is now > broken for more than a year. There are still two PRs against it (194915 > and 202067) so I didn't delete the port. Is there any intention to work > on these PRs?

Re: [exp - 103i386-default-build-as-user][lang/fsharp] Failed for fsharp-4.0.1.10 in build

On Tuesday, 18 October 2016 13:05:59 Romain Tartière wrote: > On Mon, Oct 17, 2016 at 07:52:24PM +, pkg-fall...@freebsd.org wrote: > > [ ... SNIP ... ] > Similar issue (System.Collections.Immutable not resolved, while it is > supposed to have been downloaded via Nugets) on all my poudriere

Suggestions for USES=mono

Hi I would like to suggest the following arguments be added to USES=mono: 1) nuget: to implement the nuget packaging code currently in lang/fsharp. This will allow for easier building of ports that have nuget dependencies. Existing users: lang/fsharp 2) lib: mark a port as using native

Re: [package - 101amd64-default][lang/referenceassemblies-pcl] Failed for referenceassemblies-pcl-4.6_1 in package

On Sunday, 16 October 2016 11:06:22 Romain Tartière wrote: > On Sat, Oct 15, 2016 at 03:55:00PM -0700, Russell Haley wrote: > > This is just a guess because I'm looking at this on my phone. The > > profiles for the missing files aren't in the list of --include > > parameters in the previous

Re: [exp - 103i386-default-build-as-user][lang/fsharp] Failed for fsharp-4.0.1.10 in build

Hi I am working on a fix for this. Regards On Sunday, 9 October 2016 19:51:54 pkg-fall...@freebsd.org wrote: > You are receiving this mail as a port that you maintain > is failing to build on the FreeBSD package build server. > Please investigate the failure and submit a PR to fix > build. >