Hello,
we are discussing in this bug https://bugzilla.redhat.com/show_bug.cgi?id=1220138 the work that would be required to upgrade Mono in Epel.
I am aware that this is a major upgrade, and according to [1] it should be avoided. But Mono is that old in Epel7 already, so the discussion currently goes into the direction that an upgrade is better than nobody using Mono in Epel at all.
I would like to upgrade to the latest stable Mono version, which is 4.2 at the moment. That is in rawhide already, F23 has Mono 4.0.
What do people think on this list?
Do I need to create a Fesco ticket to request permission to upgrade Mono in Epel7, and to do a bootstrap similar to Mono 4 in Fedora [2]?
Thanks for any hints and suggestions, Timotheus
[1] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version_up... [2] https://fedorahosted.org/fpc/ticket/528
we are discussing in this bug https://bugzilla.redhat.com/show_bug.cgi?id=1220138 the work that would be required to upgrade Mono in Epel.
I am aware that this is a major upgrade, and according to [1] it should be avoided. But Mono is that old in Epel7 already, so the discussion currently goes into the direction that an upgrade is better than nobody using Mono in Epel at all.
It either needs to be upgraded or retired, I have no issues with it being upgraded.
I would like to upgrade to the latest stable Mono version, which is 4.2 at the moment. That is in rawhide already, F23 has Mono 4.0.
Is there a LTS release in the mono 4.x release?
What do people think on this list?
What's the future of Mono with an open source MS .Net core?
Do I need to create a Fesco ticket to request permission to upgrade Mono in Epel7, and to do a bootstrap similar to Mono 4 in Fedora [2]?
Well it would be Eesco, but personally I don't believe it's needed, it just needs to be properly co-ordinated.
Thanks for any hints and suggestions, Timotheus
[1] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version_up... [2] https://fedorahosted.org/fpc/ticket/528 _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.or...
Hello Peter,
I would like to upgrade to the latest stable Mono version, which is 4.2 at the moment. That is in rawhide already, F23 has Mono 4.0.
Is there a LTS release in the mono 4.x release?
Unfortunately no. There is just an alpha, a beta and a stable channel: http://developer.xamarin.com/releases/current/
What do people think on this list?
What's the future of Mono with an open source MS .Net core?
That is an interesting question. I found this article: http://thenewstack.io/the-opportunity-of-net-core-and-why-it-will-not-fade-a... It says that .Net core will not replace the .Net framework (which Mono tries to implement). Especially for desktop apps (Winforms, WPF) there is no replacement in .Net core. Though winforms is deprecated even in Mono but still works for basic things. WPF has never been implemented in Mono. KeePass uses winforms in Fedora. I wonder if MonoDevelop (GTK#) one day would build with .Net core, but I think that is still far in the future.
By the way, I have a copr repository to build dotnet core for Fedora: https://copr.fedoraproject.org/coprs/tpokorra/dotnet/ to have something similar as it works on https://dotnet.github.io/getting-started/ for Ubuntu 14.04. I have not actually used it, RC1 failed to build on Fedora a month ago when I tried first, but current git master builds now. Now there is still trouble during the installation phase because there is a nuget call. I will look into this another day...
Timotheus
Hello,
Just to give a heads up: I am now working on this upgrade to Mono 4.2. I will build the mono package and the depending packages in a BuildRoot Override, and submit them for testing. They will sit in testing for a couple of months, and hopefully when CentOS 7.3 is released (October or November???) we can submit the updated packages to Epel7. Are there any problems with that plan?
Is there a LTS release in the mono 4.x release?
Unfortunately no. There is just an alpha, a beta and a stable channel: http://developer.xamarin.com/releases/current/
Debian also has Mono 4.2 in Debian Stretch (Testing), so chances are that it will be included in the next stable release. https://packages.debian.org/search?keywords=mono-complete Ubuntu has Mono 4.2 in universe for Ubuntu 16.04 LTS, but that does not count for anything, because there is no guarantuee for maintenance of packages in universe. http://packages.ubuntu.com/search?keywords=mono-complete
Do I need to create a Fesco ticket to request permission to upgrade Mono in Epel7, and to do a bootstrap similar to Mono 4 in Fedora [2]?
Well it would be Eesco, but personally I don't believe it's needed, it just needs to be properly co-ordinated.
I guess this is the Epel SIG? Would you want to discuss the bootstrap build of Mono in Epel7, and exception to the Epel Update Policy? Please let me know if I should attend the meeting on coming Wednesday, 18:00 UTC in #fedora-meeting. I would then try to be there.
Thanks, Timotheus
On Fri, 26 Aug 2016 07:24:33 +0200 Timotheus Pokorra timotheus.pokorra@solidcharity.com wrote:
Hello,
Just to give a heads up: I am now working on this upgrade to Mono 4.2. I will build the mono package and the depending packages in a BuildRoot Override, and submit them for testing. They will sit in testing for a couple of months, and hopefully when CentOS 7.3 is released (October or November???) we can submit the updated packages to Epel7. Are there any problems with that plan?
Sounds reasonable to me.
I guess this is the Epel SIG? Would you want to discuss the bootstrap build of Mono in Epel7, and exception to the Epel Update Policy? Please let me know if I should attend the meeting on coming Wednesday, 18:00 UTC in #fedora-meeting. I would then try to be there.
If you like we can, but also we can just see if anyone thinks that is needed. ;) IMHO your plan is fine.
kevin
Hello,
just to give a quick update:
Just to give a heads up: I am now working on this upgrade to Mono 4.2. I will build the mono package and the depending packages in a BuildRoot Override, and submit them for testing. They will sit in testing for a couple of months, and hopefully when CentOS 7.3 is released (October or November???) we can submit the updated packages to Epel7. Are there any problems with that plan?
Last week in the meeting [1], it was suggested that I get a side tag from releng. I filed a ticket [2], but there have been some hickups. But now it is working. I am building now the new packages in the side tag, and will submit them to testing hopefully in the next couple of days, and then make an announcement.
All the best, Timotheus
[1] https://meetbot.fedoraproject.org/teams/epel/epel.2016-08-31-18.01.log.html [2] https://fedorahosted.org/rel-eng/ticket/6473
epel-devel@lists.fedoraproject.org
-
Kevin Fenzi -
Peter Robinson -
Timotheus Pokorra