Mono 4 issues and Mono 5

[Timotheus Pokorra]

Dear members of the Mono SIG group,

I have been working in the past week on building Mono 5 for Fedora Rawhide.

This has been made possible by the work of directhex, who fixed the build for Debian.
For details on his work see https://github.com/mono/mono/issues/7445

The discussion lives at https://bugzilla.redhat.com/show_bug.cgi?id=1436896

Unfortunately we are too late for the upcoming Fedora 30, since the change affects quite a
number of packages.
For Mono 4, we needed a bootstrap build, and filed it as a system wide change:
https://fedoraproject.org/wiki/Changes/Mono_4
I will prepare a similar change proposal for Mono 5 for Fedora 31.

Please can you look at the code, and evaluate if the package is properly built?
The source is still here:
https://github.com/tpokorra/mono-5.x-fedora/tree/master/mono-5.18
After the change proposal gets accepted, I would put it in the proper source control in
https://src.fedoraproject.org/rpms/mono
The package is built here: https://copr.fedorainfracloud.org/coprs/tpokorra/mono-5.18/

Another issue I want to bring up is the state of Mono 4 in Fedora 30.
I probably committed a mistake, by disabling the ppc64 builds for Mono due to a long
standing bug on that architecture.
I just did not want mono to be FTBFS for yet another Fedora release.
See the details here: https://bugzilla.redhat.com/show_bug.cgi?id=1588734
It seems, that now all packages depending on Mono cannot be built anymore, because they
still have ppc64 enabled.
What do you think, is this really a problem, and if yes, how can we resolve it?
In Rawhide, things should go back to normal as soon as Mono 5 has landed.
Should we consider porting Mono 5 back to Fedora 30 after the Fedora 30 release? But that
would contradict calling it a system wide change...
Or we disable ppc64 in Fedora 30 altogether? It should be available in Fedora 31 again.

Any suggestions and help in testing and evaluating are welcome!

All the best,
  Timotheus

[Radka Janekova]

Awesome Timotheus, thank you for all this work on mono!


+dotnet-sig for more eyes

Radka

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



On Thu, Feb 21, 2019 at 9:50 PM Timotheus Pokorra <mailinglists(a)tpokorra.de&gt;
wrote:

>  Dear members of the Mono SIG group,
>
>  I have been working in the past week on building Mono 5 for Fedora Rawhide.
>
>  This has been made possible by the work of directhex, who fixed the build
>  for Debian.
>  For details on his work see https://github.com/mono/mono/issues/7445
>
>  The discussion lives at
>  https://bugzilla.redhat.com/show_bug.cgi?id=1436896
>
>  Unfortunately we are too late for the upcoming Fedora 30, since the change
>  affects quite a number of packages.
>  For Mono 4, we needed a bootstrap build, and filed it as a system wide
>  change: https://fedoraproject.org/wiki/Changes/Mono_4
>  I will prepare a similar change proposal for Mono 5 for Fedora 31.
>
>  Please can you look at the code, and evaluate if the package is properly
>  built?
>  The source is still here:
>  https://github.com/tpokorra/mono-5.x-fedora/tree/master/mono-5.18
>  After the change proposal gets accepted, I would put it in the proper
>  source control in https://src.fedoraproject.org/rpms/mono
>  The package is built here:
>  https://copr.fedorainfracloud.org/coprs/tpokorra/mono-5.18/
>
>  Another issue I want to bring up is the state of Mono 4 in Fedora 30.
>  I probably committed a mistake, by disabling the ppc64 builds for Mono due
>  to a long standing bug on that architecture.
>  I just did not want mono to be FTBFS for yet another Fedora release.
>  See the details here: https://bugzilla.redhat.com/show_bug.cgi?id=1588734
>  It seems, that now all packages depending on Mono cannot be built anymore,
>  because they still have ppc64 enabled.
>  What do you think, is this really a problem, and if yes, how can we
>  resolve it?
>  In Rawhide, things should go back to normal as soon as Mono 5 has landed.
>  Should we consider porting Mono 5 back to Fedora 30 after the Fedora 30
>  release? But that would contradict calling it a system wide change...
>  Or we disable ppc64 in Fedora 30 altogether? It should be available in
>  Fedora 31 again.
>
>  Any suggestions and help in testing and evaluating are welcome!
>
>  All the best,
>    Timotheus
>
>  _______________________________________________
>  mono mailing list -- mono(a)lists.fedoraproject.org
>  To unsubscribe send an email to mono-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]
>

[Timotheus Pokorra]

Hello all,

On 21.02.19 22:41, Radka Janekova wrote:
>  Awesome Timotheus, thank you for all this work on mono! 
Thanks Radka!

>  I will prepare a similar change proposal for Mono 5 for Fedora 31.
Here is the change proposal. I hope I did not forget any important 
information.

https://fedoraproject.org/wiki/Changes/Mono_5

All the best,
   Timotheus

[Timotheus Pokorra]

Hello all,

It was suggested and agreed by FESCO, that we try to get Mono 5 even 
into Fedora 30.

https://pagure.io/fesco/issue/2105

We have now an update in Testing: 
https://bodhi.fedoraproject.org/updates/mono-5.18.1-2.fc30

We need urgent testing, so that we know if packages depending on Mono 
need to be rebuilt.

Thank you,

   Timotheus


On 02.03.19 06:59, Timotheus Pokorra wrote:
> Hello all,
>
> On 21.02.19 22:41, Radka Janekova wrote:
> > Awesome Timotheus, thank you for all this work on mono!
>
> Thanks Radka!
>
> > I will prepare a similar change proposal for Mono 5 for Fedora 31.
>
> Here is the change proposal. I hope I did not forget any important 
> information.
>
> https://fedoraproject.org/wiki/Changes/Mono_5
>
> All the best,
>   Timotheus
> _______________________________________________
> mono mailing list -- mono(a)lists.fedoraproject.org
> To unsubscribe send an email to mono-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]

[Dan Horák]

for the record - I've added Mono (the master branch) into our internal
CI system (for aarch64, armv7, ppc64, ppc64le, s390x, x86_64), so we
should be notified early when something breaks.


		Dan