Mono 3.0 is available since nearly a month. It provides a lot of new stuff against 2.10. I recommend to update the rpm to mono 3.0.1 like suse did. There is a src.rpm for suse, but it does not fit to fedora yet. The src.rpm can be found here http://download.mono-project.com/archive/3.0.1/linux/x64/ There are some problems when building it. First i have to insert this line to the spec file, else will be problem like "no build id note found in ..." %define debug_package %{nil} also the first line does not do what is should do %{!?ext_man: %define ext_man .gz} I think it checks if ext_man is defined and if not it will be assigned to .gz, but it does not work. If you insert %define ext_man .gz manually, it work flawless. Also libgdiplus0 does not exist, but libgdiplus does. If you try to install them while you have the "old" mono-2.10 installed, there are some other problemsn like multilib version, cause one of the packages tries to install mono-core i686, what ever. This needs some investigation, but I think you will handle it right. Greetings, Marcel Hellwig
Created attachment 702553 [details] bash script for converting suse rpm to fed As more people starts watching this, I wrote a little script that will "convert" the suse src.rpm to a buildable fedora src.rpm. It's not perfect but it will do its job. The spec file in fact is really unfinished. There are no dependencies to gettext or automake. I hope the mono team will fix this soon. As long, here is a script. You can download the latest src.rpm from [0] and then just run ./make-fed-mono.sh {the-source-rpm} and then you will get a new created src rpm in your folder. You will need rpm2cpio, cpio and a rpmbuild setup for this.
Can we get any estimation when the upgrade to 3.0 (3.2 preferably) will be done?
It appears as though mono on fedora no longer has support behind it. There has been no updates since fedora 18 based on https://apps.fedoraproject.org/packages/mono/overview/ although the site does not list anything before FC18 based on the changing of the version between each release of fedora it is possible there have been no updates since FC15 mono-project lists 2.10 as "discontinued" as of July 24th, 2013 (see http://www.mono-project.com/Release_Notes_Mono_3.2 "Mono 3.2 was released on July 24th, 2013. Support for Mono versions 3.0 and 2.10 is been discontinued"). I have attempted to contact the package maintainers through the mailing list as well as direct emails. I received no response from the maintainers the two response I received from the mailing list indicate that people are just building their own. The new MonoDevelop requires an updated version of mono and the current version of MonoDevelop cannot open current Visual Studio projects. I am willing to take over maintaining mono but I don't even know where to start.
I have started to update mono to 3.2.3, but got stuck due to build failures for the arm architecture: https://koji.fedoraproject.org/koji/taskinfo?taskID=6207292 In any case, it would be great if you could help out with mono in Fedora. It would be highly appreciated to have more active co-maintainers! Are you already a Fedora packager? Basically the next step would be: get mono-core compiling on all architectures and consecutively rebuild and test all mono packages in rawhide. I'll attach a preliminary diff for mono.spec tomorrow.
I am not currently a Fedora packager but I am interested in becoming one. I have gone through the instructions here https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join to the point of Introduce yourself & Get Sponsored at which point I got confused as to what a "review request you have filed" and what being sponsored is? Is there an irc or mailing list to help people get up to speed with becoming a package maintainer?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.