Mono - Do we have a maintainer?

[Radka Janekova]

Hi,

mono-devel packages are far behind upstream, and the mono-sig seems
unresponsive as whole. This leads me to a question, do we have a maintainer
for mono?

I can take a look at it within the next month or two if there really isn't
anyone else...

Regards,
Radka

------------------------------
*Radka Janeková*
.NET Engineer, Red Hat
*radka.janek(a)redhat.com <radka.janek(a)redhat.com&gt;*
IRC: radka | Freenode: Rhea

[Manas Mangaonkar]

Hey,

incase this has been abandoned,i can take this up.I recently published my
first package --> KernelHighperf
<https://copr.fedorainfracloud.org/coprs/pac23/High_Performance_Clear_LInu...
and
would love to work on something else and gain more experience as a
packager.

On Wed, Aug 15, 2018 at 3:46 PM, Radka Janekova <radka.janek(a)redhat.com&gt;
wrote:

>  Hi,
>
>  mono-devel packages are far behind upstream, and the mono-sig seems
>  unresponsive as whole. This leads me to a question, do we have a maintainer
>  for mono?
>
>  I can take a look at it within the next month or two if there really isn't
>  anyone else...
>
>  Regards,
>  Radka
>
>  ------------------------------
>  *Radka Janeková*
>  .NET Engineer, Red Hat
>  *radka.janek(a)redhat.com <radka.janek(a)redhat.com&gt;*
>  IRC: radka | Freenode: Rhea
>
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.
>  fedoraproject.org/message/TXJJWGDMTDHBBA3IPSA2NTXJB66D6P26/
>
>

[Peter Lemenkov]

Hello All!

2018-08-15 12:16 GMT+02:00 Radka Janekova <radka.janek(a)redhat.com&gt;:
>  Hi,
>
>  mono-devel packages are far behind upstream, and the mono-sig seems unresponsive as
> whole. This leads me to a question, do we have a maintainer for mono?
>
>  I can take a look at it within the next month or two if there really isn't anyone
> else... 
Sounds like a plan!

-- 
With best regards, Peter Lemenkov.

[Michael Cronenworth]

On 08/15/2018 05:16 AM, Radka Janekova wrote:
>  mono-devel packages are far behind upstream, and the mono-sig seems unresponsive 
>  as whole. This leads me to a question, do we have a maintainer for mono?
>
>  I can take a look at it within the next month or two if there really isn't anyone 
>  else... 
Radka,

Yes, mono is behind, but it isn't a simple reason. The way mono is bootstrapped and 
compiled has changed starting with version 5.0. The Roslyn compiler is now the 
default and requires bootstrapping from binary-only sources provided by upstream. 
This is a no-no in Fedora. There was an effort by a team in Red Hat to package the 
binary sources, but that team seems to be disbanded. Recently Mono has allowed the 
MCS compiler again and that has lead to an almost-ready update by community 
contributors.

Follow along here: https://bugzilla.redhat.com/show_bug.cgi?id=1436896

Thanks,
Michael

[Florian Weimer]

On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
>  The Roslyn compiler is now the default and requires bootstrapping
> from 
>  binary-only sources provided by upstream. This is a no-no in Fedora. 
Are you sure about that?  Ocaml does it as well.

Thanks,
Florian

[Michael Cronenworth]

On 08/15/2018 08:55 AM, Florian Weimer wrote:
>  Are you sure about that?  Ocaml does it as well.
>
>  Thanks,
>  Florian  
The guidelines allow an initial bootstrap from binaries, but subsequent builds are 
supposed to build from source. The problem is that we can't build without the 
binaries at all. The Roslyn compiler requires the "msbuild" tool, which
hasn't been 
successfully built from source.

I don't have the time to lend, but if others are willing to step in that would be
great.

[Rex Dieter]

Michael Cronenworth wrote:

>  On 08/15/2018 08:55 AM, Florian Weimer wrote:
> > Are you sure about that?  Ocaml does it as well.
> >
> > Thanks,
> > Florian
>  
>  The guidelines allow an initial bootstrap from binaries, but subsequent
>  builds are supposed to build from source. The problem is that we can't
>  build without the binaries at all. The Roslyn compiler requires the
>  "msbuild" tool, which hasn't been successfully built from source. 
OK, so the real reason is that bootstrapping step was never completed 100%

-- rex

[Omair Majid]

* Michael Cronenworth <mike(a)cchtml.com&gt; [2018-08-15 10:19]:
>  On 08/15/2018 08:55 AM, Florian Weimer wrote:
>  > Are you sure about that?  Ocaml does it as well.
>  
>  The guidelines allow an initial bootstrap from binaries, but subsequent
>  builds are supposed to build from source. The problem is that we can't build
>  without the binaries at all. The Roslyn compiler requires the "msbuild"
>  tool, which hasn't been successfully built from source.
>  
>  I don't have the time to lend, but if others are willing to step in that would be
> great. 
It's possible to build msbuild (and .NET Core) from source here:
https://github.com/dotnet/source-build/

But then there's the recursive problem of building all those binary
(nuget) packages that source-build needs, from source.

We are working on trying to improve .NET Core (including msbuild) and
bring it to a point where it can be added to Fedora proper, but it's a
fairly long term goal.

Omair

-- 
PGP Key: B157A9F0 (http://pgp.mit.edu/)
Fingerprint = 9DB5 2F0B FD3E C239 E108  E7BD DF99 7AF8 B157 A9F0

[Dan Horák]

On Mon, 20 Aug 2018 17:13:42 -0400
Omair Majid <omajid(a)redhat.com&gt; wrote:

>  * Michael Cronenworth <mike(a)cchtml.com&gt; [2018-08-15 10:19]:
>  > On 08/15/2018 08:55 AM, Florian Weimer wrote:
>  > > Are you sure about that?  Ocaml does it as well.
>  > 
>  > The guidelines allow an initial bootstrap from binaries, but
>  > subsequent builds are supposed to build from source. The problem is
>  > that we can't build without the binaries at all. The Roslyn
>  > compiler requires the "msbuild" tool, which hasn't been
>  > successfully built from source.
>  > 
>  > I don't have the time to lend, but if others are willing to step in
>  > that would be great.
>  
>  It's possible to build msbuild (and .NET Core) from source here:
>  https://github.com/dotnet/source-build/
>  
>  But then there's the recursive problem of building all those binary
>  (nuget) packages that source-build needs, from source.
>  
>  We are working on trying to improve .NET Core (including msbuild) and
>  bring it to a point where it can be added to Fedora proper, but it's a
>  fairly long term goal. 
a nice thing on Mono is that it is fully multi-arch, supporting all
Fedora arches. Won't be multi-arch problem for msbuild or .NET Core?


		Dan

[Omair Majid]

* Dan Horák <dan(a)danny.cz&gt; [2018-08-22 03:55]:
>  a nice thing on Mono is that it is fully multi-arch, supporting all
>  Fedora arches. Won't be multi-arch problem for msbuild or .NET Core? 
Oh. Right, that would be a problem. .NET Core upstream essentially
supports x86_64 only. arm-hfp, aarch64 and x86 are supported to some
extent. Every other platform is pretty much unsupported.

Thanks,
Omair

-- 
PGP Key: B157A9F0 (http://pgp.mit.edu/)
Fingerprint = 9DB5 2F0B FD3E C239 E108  E7BD DF99 7AF8 B157 A9F0

[Gerald Henriksen]

On Wed, 22 Aug 2018 13:59:51 -0400, you wrote:

> * Dan Horák <dan(a)danny.cz&gt; [2018-08-22 03:55]:
> > a nice thing on Mono is that it is fully multi-arch, supporting all
> > Fedora arches. Won't be multi-arch problem for msbuild or .NET Core?
>
> Oh. Right, that would be a problem. .NET Core upstream essentially
> supports x86_64 only. arm-hfp, aarch64 and x86 are supported to some
> extent. Every other platform is pretty much unsupported. 
As of .Net Core 2.1 Arm32 is officially supported.

https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1/

[Miro Hrončok]

On 15.8.2018 15:55, Florian Weimer wrote:
>  On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
> > The Roslyn compiler is now the default and requires bootstrapping from 
> > binary-only sources provided by upstream. This is a no-no in Fedora.
>  
>  Are you sure about that?  Ocaml does it as well. 
See also: https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Richard W.M. Jones]

On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
>  On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
>  >The Roslyn compiler is now the default and requires bootstrapping
>  >from binary-only sources provided by upstream. This is a no-no in
>  >Fedora.
>  
>  Are you sure about that?  Ocaml does it as well. 
Actually I've been meaning to fix this for a really long time.
It should be a simple matter of copying %{_bindir}/ocaml and
%{_bindir}/ocamllex into boot/ before building.  (Of course
the package will then BuildRequire ocaml).

Could you file a bug so I don't forget about this?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

[Jonathan Underwood]

On Fri, 17 Aug 2018 at 19:58, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:

>  On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
>  > On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
>  > >The Roslyn compiler is now the default and requires bootstrapping
>  > >from binary-only sources provided by upstream. This is a no-no in
>  > >Fedora.
>  >
>  > Are you sure about that?  Ocaml does it as well.
>
>  Actually I've been meaning to fix this for a really long time.
>  It should be a simple matter of copying %{_bindir}/ocaml and
>  %{_bindir}/ocamllex into boot/ before building.  (Of course
>  the package will then BuildRequire ocaml).
>
>  Could you file a bug so I don't forget about this?
>
>  
https://bugzilla.redhat.com/show_bug.cgi?id=1619749

OCaml bootstrapping (was: Re: Mono - Do we have a maintainer?)

[Richard W.M. Jones]

On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
>  On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
>  >The Roslyn compiler is now the default and requires bootstrapping
>  >from binary-only sources provided by upstream. This is a no-no in
>  >Fedora.
>  
>  Are you sure about that?  Ocaml does it as well. 
Ignore the previous message, I've fixed this now.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

[Pavel Zhukov]

Michael Cronenworth <mike(a)cchtml.com&gt; writes:

>  On 08/15/2018 05:16 AM, Radka Janekova wrote:
> >
> > mono-devel packages are far behind upstream, and the mono-sig seems
> > unresponsive as whole. This leads me to a question, do we have a
> > maintainer for mono?
> >
> > I can take a look at it within the next month or two if there really
> > isn't anyone else...
>
>  Radka,
>
>  Yes, mono is behind, but it isn't a simple reason. The way mono is
>  bootstrapped and compiled has changed starting with version 5.0. The
>  Roslyn compiler is now the default and requires bootstrapping from
>  binary-only sources provided by upstream. This is a no-no in
>  Fedora. 
https://fedoraproject.org/wiki/Packaging_Committee?rd=Packaging:Committee...

>
> Follow along here: https://bugzilla.redhat.com/show_bug.cgi?id=1436896
>
> Thanks,
> Michael
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail].o...

[Timotheus Pokorra]

Hello all,

>  Yes, mono is behind, but it isn't a simple reason. The way mono
> is
>  bootstrapped and compiled has changed starting with version 5.0. The
>  Roslyn compiler is now the default and requires bootstrapping from
>  binary-only sources provided by upstream. This is a no-no in Fedora.
>  There was an effort by a team in Red Hat to package the binary
>  sources, but that team seems to be disbanded. Recently Mono has
>  allowed the MCS compiler again and that has lead to an almost-ready
>  update by community contributors.
>  
>  Follow along here: https://bugzilla.redhat.com/show_bug.cgi?id=1436896 
We are trying to still compile with the mono compiler rather than Roslyn 
by using the configuration parameter:
   --with-csc=mcs
I was told that by mono upstream some months ago, and I commented that 
here:
https://bugzilla.redhat.com/show_bug.cgi?id=1436896#c69

I have just packaged Mono 5.14.0.177 in my copr:
https://copr.fedorainfracloud.org/coprs/tpokorra/mono-5.14/

You can find the sources of the SPEC file and the patches here:
https://github.com/tpokorra/mono-5.x-fedora/tree/master/mono-5.14

I have updated the bug, and the comment tells the problematic lines.
https://bugzilla.redhat.com/show_bug.cgi?id=1436896#c91

I don't know the next steps.

Help is always welcome!

All the best,
Timotheus



----------------------------------------------------------------
Diese Nachricht wurde versandt mit Webmail von www.tbits.net.
This message was sent using webmail of www.tbits.net.