So im going to be lazy and start throwing everything in here. From what I know of mono there are a few ebuilds to be updated to 2.8 libgdiplug mono xsp
Created attachment 249825 [details, diff] libgdiplus-2.8.patch diff from 2.7.6-r1 So here is libgdiplus. Builds but untested further than that
Created attachment 249826 [details, diff] mono-2.8.ebuild.patch from 2.6.7
Created attachment 249828 [details, diff] files/mono-2.8-libdir.patch
Currently ive only had time to test that these build (and not a very good test at that) Therefore pacho feel free to continue if you have time. i'll be leaving this for tonight but will attempt to do more over the weekend if noone else picks it up.
OK, thanks a lot :-), will look at this when I have time for it
*** Bug 340043 has been marked as a duplicate of this bug. ***
Bumped dev-dotnet/libgdiplus dev-lang/mono dev-lang/mono-basic www-apache/mod_mono dev-dotnet/xsp about the only thing left is dev-util/mono-tools
(In reply to comment #7) > about the only thing left is dev-util/mono-tools also dev-util/mono-debugger needs bumping
I've just installed mono-2.8 from portage tree. Unable to find monodis util: sectoid@dagon ~ $ equery f mono | grep monodis sectoid@dagon ~ $ sectoid@dagon ~ $ equery u mono [ Legend : U - flag is set in make.conf ] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for dev-lang/mono-2.8: U I - - hardened : activate default security enhancements for toolchain (gcc, glibc, binutils) - - minimal : Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features) - + moonlight : Generate Moonlight 2.1 assemblies - + profile4 : Include partial support for C# 4.0 and some of the upcoming .NET 4.0 APIs. - - xen : Make mono generate code that is considerably faster on xen VMs but slightly slower on for normal systems.
*** Bug 340237 has been marked as a duplicate of this bug. ***
*** Bug 340239 has been marked as a duplicate of this bug. ***
*** Bug 340241 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > I've just installed mono-2.8 from portage tree. Unable to find monodis util: It depends on the moonlight USE, if you disable it you'll get monodis. It is an upstream "feature". see https://bugzilla.novell.com/show_bug.cgi?id=641005 and http://github.com/mono/mono/blob/master/configure.in#L2499
Created attachment 250031 [details] mono-tools-2.8.ebuild
Created attachment 250033 [details, diff] mono-tools html renderers patch
Created attachment 250035 [details] mono-debugger-2.8.ebuild
ebuild and pathces I've added are all heavily based on portage's version (2.6.x and 9999 versions) so credit goes to original authors. I've dropped already upstream applied patches and modified needed one to make it apply correctly. hope this helps somebody ps. I think now the only one missing is gluezilla-2.8
(In reply to comment #17) > ps. I think now the only one missing is gluezilla-2.8 > Good news. No gluezilla-2.8 (yet)
Created attachment 250069 [details, diff] Patch to enable support for features usually disabled with moonlight use flag. Ok so this patch enables monodis as well as a few other things as well. I haven't tested whether is actually works yet as im attempting to figure out the reason for the original behavior.
*** Bug 340151 has been marked as a duplicate of this bug. ***
tman, why mark bug #340151 as a duplicate? The bug is not about bumping, but a problem compiling mono?
(In reply to comment #19) > Created an attachment (id=250069) [details] > Patch to enable support for features usually disabled with moonlight use flag. > > Ok so this patch enables monodis as well as a few other things as well. > > I haven't tested whether is actually works yet as im attempting to figure out > the reason for the original behavior. > I cannot test this now but, before committing it, would be better to know why people want monodis even with USE="-moonlight" :-)
(In reply to comment #22) > I cannot test this now but, before committing it, would be better to know why > people want monodis even with USE="-moonlight" :-) > Looks like it's due bug 340365, sorry for the noise
(In reply to comment #18) > Good news. No gluezilla-2.8 (yet) > [ebuild UD] dev-dotnet/libgdiplus-2.6.7-r1 [2.8] [ebuild UD] dev-lang/mono-2.6.7 [2.8] [ebuild R ] dev-dotnet/gluezilla-2.6 after emerge -1a dev-dotnet/gluezilla Should a bug with this issue be filed or did I missed something?
(In reply to comment #24) > (In reply to comment #18) > > > Good news. No gluezilla-2.8 (yet) > > > > [ebuild UD] dev-dotnet/libgdiplus-2.6.7-r1 [2.8] > [ebuild UD] dev-lang/mono-2.6.7 [2.8] > [ebuild R ] dev-dotnet/gluezilla-2.6 > > after emerge -1a dev-dotnet/gluezilla > > Should a bug with this issue be filed or did I missed something? > Just bumped gluezilla so that problem above should be fixed. Please open a new one if the problem persists.
I still have the trouble, see bug #341779
*** Bug 341779 has been marked as a duplicate of this bug. ***
Pacho a new bug has been opened due to comment #25. Bug 340045 is a tracker as specified in the subject, so this is not a mistake. Bug reopened until it will get fixed, I am trying to investigate the issue on my side.
No, we are using this bug also for bumps (well, it was originally opened for so, but I later converted it also in a tracker as some problems were arising with the new ebuilds even when bump of all packages wasn't finished) , if it hasn't been bumped is simply because we haven't had enough time, but having splitted bugs for each ebuild pending a bump won't help to get it bumped earlier
Roger out, if I can do anything let me know.
FYI and to help the follow up of this bug: dev-lang/mono:0 (dev-lang/mono-2.6.7, ebuild scheduled for merge) pulled in by =dev-lang/mono-2.6* required by (dev-dotnet/gluezilla-2.6-r1, ebuild scheduled for merge) (and 25 more)
(In reply to comment #31) > Roger out, if I can do anything let me know. > Would be nice to provide, if possible, an ebuild diff to install gluezilla-2.8 based on 2.6 one :-)
According to the Mono project website there is no "gluezilla 2.8" but 2.6. I'm playing around to try to guess why a dependency is put on Mono 2.6.7 by portage, so far the reason is a bit nebular to me.
It's true: http://ftp.novell.com/pub/mono/sources-stable/ You bug was valid then, will reopen if and reassign, thanks a lot and sorry a lot for the inconvenience :-(
No troubles Pacho :-D Thanks for having reopened it btw.
Mono 2.10 is out! -- Mono 2.10 is an update to Mono 2.8 based on the master branch of github, it is not a minor upgrade to 2.8. Mono 2.10 was released on February 15th. Release Notes Mono 2.10 http://www.mono-project.com/Release_Notes_Mono_2.10
Version bump to 2.10 request => See bug #355325
Will close this one (we now have 2.10)