Can someone review some spec files for me?
by Stephen Shaw
These are the spec files that we are using to build rpms for openSUSE.
I was wondering if someone won't mind looking at them since I've
never build packages for fedora. There packages require mono 2.4 so
I'm hoping to be able to provide packages for fedora 11. Some of the
specs don't have versions on them. That's because these files are
stored in our trunk and the versions get set when we branch and tag.
Thanks!
Stephen
http://anonsvn.mono-project.com/viewvc/trunk/uia2atk/build/specs/
14 years, 10 months
mono-2.4 and ppc64 status
by Toshio Kuratomi
Mono-2.4 has been built for ppc64 in F11 and devel. So people should be
able to start rebuilding packages to include ppc64 as well as the other
arches. There's a few wrinkles to watch out for:
1) Packages with dependencies will have to be built in dependency order.
For instance, a lot of packages depend on the gtk-sharp2 bindings and
those haven't been built yet.
2) Because of the imminent release of F11 we're in a freeze state. This
means getting dependencies into the Fedora11 buildroot will require
people to request tagging explicitly. This also means that if you
rebuild your package for F11 with ppc64 support and later you have to
get this package tagged into the release, all of the packages it depends
on will need to be tagged in as well (otherwise your ppc64 build will
have broken deps).
With these in mind, I'd recommend people start rebuilding their mono
packages on ppc64 in the devel branch. Keep track of the dependency
chain you encounter. Then perform your builds in the Fedora 11 branch
as updates after the release. I'm not a mono-sig member, though, so if
you guys decide something else makes sense, just be sure to come up with
a plan so we don't release with a bunch of broken dependencies.
-Toshio
14 years, 11 months
monodevelop debugger addins RPMS for F10 ready!!!
by buhochilenoi＠gmail.com
Hi guys:
First post to the list, so my name is Mauricio Henriquez and I write
from Chile.
Currently me and my Univ are concern about the poor mono/monodevelop
support in Fedora (specially for the current stable fedora 10 release,
incoming releases seems to have more updated packages). So we take the
last packages for F10 plus the monodevelop-debugger-mdb and gdb packages
from opensuse, fix and solve severall issues and finally build allmost
all again fro f10, currently my machine have a running copy of
monodevelop plus the debugger addins installed all by rpms and working
fine...
So, let me know how can I send you the .spec and sources used to build
the debugger addins and also other taks that I can help, don't know much
about koji but I know the basic step for manually build or rebuild rpm
packages...
Cheers to all.
Mauricio
15 years
broken dependencies?
by Paul Lange
hey,
some time ago I got a mail from the fedora build system:
flickrnet has broken dependencies in the development tree:
On ppc:
flickrnet-2.1.5-1.fc11.ppc requires mono(System.Web) = 0:2.0.0.0
flickrnet-2.1.5-1.fc11.ppc requires mono(System.Xml) = 0:2.0.0.0
flickrnet-2.1.5-1.fc11.ppc requires mono(mscorlib) = 0:2.0.0.0
flickrnet-2.1.5-1.fc11.ppc requires mono(System) = 0:2.0.0.0
Please resolve this as soon as possible.
Is Mono not longer available on ppc?
Any help is appreciated. Thanks.
Paul
15 years
Introduction
by Huzaifa Sidhpurwala
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
I am a new member of the fedora-mono sig, and i would like to take over
the gnome-do-plugins bug review as Paul Lange does not seem to have
time to further work on this.
I work at Red Hat in IT and currently in fedora i do the following
- - Co-editor for FWN
- - Fedora Infra. sysadmin
- - Maintain a few packages in fedora.
- --
Regards,
Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas)
IT Desktop Team Lead.
Global Help Desk, Pune (India)
Phone: +91 20 4005 7322 (UTC +5.5)
GnuPG Fingerprint:
3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFJ0fftzHDc8tpb2uURAgOGAJ9RyzzNmAUOEXhmGKzYMBnI5i6phwCcCw2d
6yNqYCVf+2LP8/6Uxm+GTuk=
=S25c
-----END PGP SIGNATURE-----
15 years
