go-mono.eclass currently has support for svn based ebuilds. Due to mono migrating to github and shutting down there svn server. Any attempt to use these ebuild will fail with fetch errors ( can't connect to svn ). Believe the list of effected ebuilds is.... dev-dotnet/gluezilla-2.0.9999 dev-dotnet/gluezilla-2.4.9999 dev-dotnet/gluezilla-9999 dev-dotnet/libgdiplus-2.0.9999 dev-dotnet/libgdiplus-2.4.9999 dev-dotnet/libgdiplus-9999 dev-dotnet/xsp-2.0.9999 dev-dotnet/xsp-2.4.9999 dev-dotnet/xsp-9999 dev-lang/mono-2.0.9999 dev-lang/mono-2.4.9999 dev-lang/mono-9999 dev-lang/mono-basic-2.0.9999 dev-lang/mono-basic-2.4.9999 dev-lang/mono-basic-9999 dev-util/mono-debugger-2.0.9999 dev-util/mono-debugger-2.4.9999 dev-util/mono-debugger-9999 dev-util/mono-tools-2.0.9999 dev-util/mono-tools-2.4.9999 dev-util/mono-tools-9999 www-apache/mod_mono-2.0.9999 www-apache/mod_mono-2.4.9999 www-apache/mod_mono-9999 We can clean at least some of these maybe. otherwise go-mono.eclass will need to be updated.
*** Bug 336728 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > go-mono.eclass currently has support for svn based ebuilds. My original plan was to try to migrate it to git, but I need to find time to investigate about git (probably reviewing other eclasses and ebuilds already using it). > > Due to mono migrating to github and shutting down there svn server. Any > attempt to use these ebuild will fail with fetch errors ( can't connect to svn > ). > > Believe the list of effected ebuilds is.... > > dev-dotnet/gluezilla-2.0.9999 > dev-dotnet/gluezilla-2.4.9999 > dev-dotnet/gluezilla-9999 > dev-dotnet/libgdiplus-2.0.9999 > dev-dotnet/libgdiplus-2.4.9999 > dev-dotnet/libgdiplus-9999 > dev-dotnet/xsp-2.0.9999 > dev-dotnet/xsp-2.4.9999 > dev-dotnet/xsp-9999 > dev-lang/mono-2.0.9999 > dev-lang/mono-2.4.9999 > dev-lang/mono-9999 > dev-lang/mono-basic-2.0.9999 > dev-lang/mono-basic-2.4.9999 > dev-lang/mono-basic-9999 > dev-util/mono-debugger-2.0.9999 > dev-util/mono-debugger-2.4.9999 > dev-util/mono-debugger-9999 > dev-util/mono-tools-2.0.9999 > dev-util/mono-tools-2.4.9999 > dev-util/mono-tools-9999 > www-apache/mod_mono-2.0.9999 > www-apache/mod_mono-2.4.9999 > www-apache/mod_mono-9999 > > We can clean at least some of these maybe. otherwise go-mono.eclass will need > to be updated. > I also need time to clean all old mono ebuilds including 2.4.9999 and similar, leaving only 9999 ebuilds and latest.
Created attachment 249060 [details, diff] eclass to migrate existing *9999 ebuilds from using svn to git to retrieve source This is an initial. NON-TESTED. patch to the eclass. Use at your own risk.
Created attachment 249410 [details, diff] go-mono-eclass-git-support.patch
Ok so im farly confident that this patch will now (at least) support fetching from git for all *9999 ebuilds. Whether they build is up to the state of the branch etc. Pacho, if you test this doesn't break stable feel free to commit.
Created attachment 249413 [details] libgdiplus-9999.ebuild Thanks, I am now rebuilding stable mono to see if it still works (it should), but I have tried to adapt libgdiplus-9999.ebuild and it fails: * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-dotnet/libgdiplus-9999/temp/autoconf-14153.out * ERROR: dev-dotnet/libgdiplus-9999 failed: * Failed Running autoconf ! # cat /var/tmp/portage/dev-dotnet/libgdiplus-9999/temp/autoconf-14153.out ***** autoconf ***** ***** PWD: /var/tmp/portage/dev-dotnet/libgdiplus-9999/work/libgdiplus-9999/cairo ***** autoconf configure.in:29: error: possibly undefined macro: LT_CURRENT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:33: error: possibly undefined macro: LT_REVISION configure.in:38: error: possibly undefined macro: LT_AGE But this looks more like a problem not related at all with eclass, on the other hand, this makes me doubt about *9999* ebuilds viability :-/
(In reply to comment #6) > Created an attachment (id=249413) [details] > libgdiplus-9999.ebuild > >... > > But this looks more like a problem not related at all with eclass, on the other > hand, this makes me doubt about *9999* ebuilds viability :-/ > Try http://http://github.com/alistair/ironruby-overlay/tree/master/dev-dotnet/libgdiplus/ and http://http://github.com/alistair/ironruby-overlay/tree/master/dev-lang/mono/
*** Bug 339724 has been marked as a duplicate of this bug. ***
Should be solved now, thanks a lot Alistair :-) (in the near future I plan to drop all mono versions but latest stable and 9999, then, please move away from other versions)
