From dave@dajobe.org Tue Feb 1 21:10:51 2005 From: dave@dajobe.org (Dave Beckett) Date: Tue, 1 Feb 2005 21:10:51 +0000 Subject: [Pkg-mono-devel] list test message Message-ID: <20050201211051.687755c7@hedwig.dajobe.org> Just checking this list is working, some mail seems to have disappeared. Dave From b.delfos@wanadoo.nl Thu Feb 3 21:31:28 2005 From: b.delfos@wanadoo.nl (Bas Delfos) Date: Thu, 3 Feb 2005 22:31:28 +0100 Subject: [Pkg-mono-devel] No application found for /aspnet/ Message-ID: <20050203213134.40BB525477@smtp6.wanadoo.nl> This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C50A40.1AA1E750 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I have installed mod_mono on Apache2 (Sarge). Did all the instructions as on the page, but get an "The page cannot be found" error in my browser when I navigate to the index.aspx. In my apache2 log i found the following error: No application found for /aspnet/ Anyone know a solution? Thanks, Bas. ------=_NextPart_000_0000_01C50A40.1AA1E750 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello,
 
I have = installed=20 mod_mono on Apache2 (Sarge).
Did = all the=20 instructions as on the page, but get an "The page cannot be found" error = in my=20 browser when I navigate to the index.aspx.
 
In my = apache2 log i=20 found the following error: No application found for = /aspnet/
 
Anyone = know a=20 solution?
 
Thanks,
Bas.
------=_NextPart_000_0000_01C50A40.1AA1E750-- From b.delfos@wanadoo.nl Fri Feb 4 19:08:04 2005 From: b.delfos@wanadoo.nl (Bas Delfos) Date: Fri, 4 Feb 2005 20:08:04 +0100 Subject: [Pkg-mono-devel] RE: No application found for /aspnet/ Message-ID: <20050204190811.12F0010D29@smtp5.wanadoo.nl> Hello, I found the solution!! The problem was that the following line was missing in the /etc/mono-server/mono-server-hosts.conf MonoApplications "/aspnet:/var/www/aspnet" After restarting Apache2 the problem was solved. /etc/mono-server/mono-server-hosts.conf now looks like this: MonoUnixSocket /tmp/.mod_mono_server MonoServerPath /usr/share/dotnet/bin/mod-mono-server.exe AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx MonoApplicationsConfigDir /etc/mono-server MonoPath /usr/share/dotnet/lib:/usr/lib: MonoApplications "/aspnet:/var/www/aspnet" # start /etc/mono-server/conf.d/aspnet/10_aspnet Alias /aspnet "/var/www/aspnet" SetHandler mono DirectoryIndex index.aspx # end /etc/mono-server/conf.d/aspnet/10_aspnet Thanks, Bas. Van: Bas Delfos [mailto:b.delfos@wanadoo.nl] Verzonden: donderdag 3 februari 2005 22:31 Aan: 'pkg-mono-devel@lists.alioth.debian.org' Onderwerp: No application found for /aspnet/ Hello, I have installed mod_mono on Apache2 (Sarge). Did all the instructions as on the page, but get an "The page cannot be found" error in my browser when I navigate to the index.aspx. In my apache2 log i found the following error: No application found for /aspnet/ Anyone know a solution? Thanks, Bas. From jaret@aberlorn.com Tue Feb 8 05:12:06 2005 From: jaret@aberlorn.com (jaret) Date: Mon, 07 Feb 2005 23:12:06 -0600 Subject: [Pkg-mono-devel] mod_mono, apache2 and 503 Service Temporarily Unavailable error Message-ID: <42084A26.6060406@aberlorn.com> Hello all... I hope I am on the right list... If not, my apologies and just point me in the right direction. I installed the latest and greatest pkg from When attempting to retrieve an aspx file from lynx of firefox, I've been getting a 503 Service Temp Unavailable error. Happens with localhost and from outside my firewall. Mono compiles. I can browse web-pages. But no aspx/mono server related. Any ideas what's going on? Permissions are root. Appears that way across the board for mono and apache. netstat -an | grep LISTEN shows: tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN unix 2 [ ACC ] STREAM LISTENING 597 /var/run/apache2/cgisock Following other posts, I tried to run the mod server where it creates a socket in /tmp/ and then change r/w permissions. Sure, a daemon appears but same 503 error results... even when I change MonoUnixSocket /.tmp/mod_mono_server to MonoUnixSocket /tmp/mod_mono_server For now I'm not really sure what's going on and throwing it out to you all to see if you had any ideas. I used these sources for packages: deb http://mirrors.rcn.net/debian/ sid main deb http://debian.pablo.com.mx ./ # for libapache2-mod-mono Here's the file setup: From mod_mono.load LoadModule mono_module /usr/lib/apache2/modules/mod_mono.so From mod_mono.conf AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx DirectoryIndex index.aspx # Include the web application definitions generated by mono-server-update.conf Include /etc/mono-server/mono-server-hosts.conf From mono-server-hosts.conf # Default configuration, don't edit it! MonoUnixSocket /.tmp/mod_mono_server MonoServerPath /usr/share/dotnet/bin/mod-mono-server.exe AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx MonoApplicationsConfigDir /etc/mono-server MonoPath /usr/share/dotnet/lib:/usr/lib: # start /etc/mono-server/conf.d/asp.net-examples/10_asp.net-examples Alias /samples "/usr/share/asp.net-demos/asp" SetHandler mono DirectoryIndex index.aspx # end /etc/mono-server/conf.d/asp.net-examples/10_asp.net-examples # start /etc/mono-server/conf.d/aspnet/10_aspnet Alias /aspnet "/var/www/aspnet" SetHandler mono DirectoryIndex index.aspx # end /etc/mono-server/conf.d/aspnet/10_aspnet Thanks, Jaret From jaret@aberlorn.com Tue Feb 8 05:22:18 2005 From: jaret@aberlorn.com (jaret) Date: Mon, 07 Feb 2005 23:22:18 -0600 Subject: [Pkg-mono-devel] Re: mod_mono, apache2 and 503 Service Temporarily Unavailable error In-Reply-To: <42084A26.6060406@aberlorn.com> References: <42084A26.6060406@aberlorn.com> Message-ID: <42084C8A.60600@aberlorn.com> And, yes, like the former email poster, I did try adding to mono-server-hosts.conf: MonoApplications "/aspnet:/var/www/aspnet" But had the same results... jaret wrote: > Hello all... I hope I am on the right list... If not, my apologies and > just point me in the right direction. > > I installed the latest and greatest pkg from When attempting to > retrieve an aspx file from lynx of firefox, I've been getting a 503 > Service Temp Unavailable error. Happens with localhost and from > outside my firewall. Mono compiles. I can browse web-pages. But no > aspx/mono server related. Any ideas what's going on? > > Permissions are root. Appears that way across the board for mono and > apache. > > netstat -an | grep LISTEN shows: > tcp 0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > unix 2 [ ACC ] STREAM LISTENING 597 > /var/run/apache2/cgisock > > Following other posts, I tried to run the mod server where it creates > a socket in /tmp/ and then change r/w permissions. Sure, a daemon > appears but same 503 error results... even when I change > MonoUnixSocket /.tmp/mod_mono_server to MonoUnixSocket > /tmp/mod_mono_server > > For now I'm not really sure what's going on and throwing it out to you > all to see if you had any ideas. > > I used these sources for packages: > deb http://mirrors.rcn.net/debian/ sid main > deb http://debian.pablo.com.mx ./ # for libapache2-mod-mono > > Here's the file setup: > > From mod_mono.load > LoadModule mono_module /usr/lib/apache2/modules/mod_mono.so > > From mod_mono.conf > AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx > DirectoryIndex index.aspx > # Include the web application definitions generated by > mono-server-update.conf > Include /etc/mono-server/mono-server-hosts.conf > > From mono-server-hosts.conf > # Default configuration, don't edit it! > > MonoUnixSocket /.tmp/mod_mono_server > MonoServerPath /usr/share/dotnet/bin/mod-mono-server.exe > AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config > .ascx > MonoApplicationsConfigDir /etc/mono-server > MonoPath /usr/share/dotnet/lib:/usr/lib: > # start /etc/mono-server/conf.d/asp.net-examples/10_asp.net-examples > Alias /samples "/usr/share/asp.net-demos/asp" > > SetHandler mono > > DirectoryIndex index.aspx > > > # end /etc/mono-server/conf.d/asp.net-examples/10_asp.net-examples > # start /etc/mono-server/conf.d/aspnet/10_aspnet > Alias /aspnet "/var/www/aspnet" > > SetHandler mono > > DirectoryIndex index.aspx > > > # end /etc/mono-server/conf.d/aspnet/10_aspnet > > > Thanks, > > Jaret > From abyss@pathcom.com Thu Feb 10 07:58:16 2005 From: abyss@pathcom.com (Chris Capon) Date: Thu, 10 Feb 2005 02:58:16 -0500 Subject: [Pkg-mono-devel] mono-xsp: Process has not been started. Message-ID: <420B1418.1010106@pathcom.com> I am trying to get the xsp server to deliver pages. After installing mono-xsp and monodoc-http, the error message below is returned to the web browser. When I try to install my own aspx pages (nice simple ones with only HTML) I get the same error. Here are the mono packages I have installed, all of them at the current Debian testing level. All packages have been removed and reinstalled again, but the problem remains. mono-gac mono-jay mono-mcs mono-utils monodevelop monodoc monodoc-base monodoc-browser monodoc-http monodoc-manual mono-common mono-jit libmono0 mono-assemblies-arch mono-assemblies-base mono-xsp This has also been tried under Apache using mono-apache-server but the same error occurs with it too. Is something else supposed to be started ahead of time? What process is the message refering to? Thanks in advance, Chris. Server error in '/monodoc' application ------------------------------------------------------------------------ *Description: *Error processing request. *Error Message: *HTTP 500. *Stack Trace: * || System.InvalidOperationException: Process has not been started. in <0x0003b> System.Diagnostics.Process:get_ExitCode () in <0x00050> (wrapper remoting-invoke-with-check) System.Diagnostics.Process:get_ExitCode () in <0x002bd> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch (System.CodeDom.Compiler.CompilerParameters,string[]) in <0x0044a> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDomBatch (System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit[]) in <0x00050> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDom (System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit) in <0x00171> System.Web.Compilation.CachingCompiler:Compile (System.Web.Compilation.BaseCompiler) in <0x002ea> System.Web.Compilation.BaseCompiler:GetCompiledType () in <0x00251> System.Web.Compilation.AspGenerator:GetCompiledType () in <0x00036> System.Web.UI.PageParser:CompileIntoType () in <0x00018> System.Web.UI.TemplateControlParser:GetCompiledInstance () in <0x00050> System.Web.UI.PageParser:GetCompiledPageInstance (string,string,System.Web.HttpContext) in <0x00011> System.Web.UI.PageHandlerFactory:GetHandler (System.Web.HttpContext,string,string,string) in <0x0034e> System.Web.HttpApplication:CreateHttpHandler (System.Web.HttpContext,string,string,string) in <0x0011f> CreateHandlerState:Execute () in <0x00084> StateMachine:ExecuteState (System.Web.HttpApplication/IStateHandler,bool&) From abyss@pathcom.com Fri Feb 11 06:43:52 2005 From: abyss@pathcom.com (Chris Capon) Date: Fri, 11 Feb 2005 01:43:52 -0500 Subject: [Pkg-mono-devel] mono-xsp: Process has not been started. In-Reply-To: <420B1418.1010106@pathcom.com> References: <420B1418.1010106@pathcom.com> Message-ID: <420C5428.3030206@pathcom.com> There is a solution to this problem but I believe a fix should be applied to the mono-xsp package (and possibly mono-apache-server). User "www-data" does not have write permissions to it's home directory. The original failure is caused by mono-xsp not being able to run the mcs compiler. When launching mono-xsp from /etc/init.d, it is run as the default user set in /etc/default/mono-xsp which is "www-data". This user is not able to launch the mcs compiler. You can test this by "su www-data" and try to run mcs. The executable mcs is in the search path, but it needs to create a folder called .wapi in the user's home directory for temporary files. The "www-data" user's home directory is /var/www for which it has no write permissions. Either /var/www needs write permissions for user "www-data", or a new home directory must be assigned. My solution was to create a folder /var/www/.wapi and set "www-data" as it's owner. This allowed it to compile .aspx pages and everything worked again. Chris. Chris Capon wrote: > I am trying to get the xsp server to deliver pages. After installing > mono-xsp and monodoc-http, the error message below is returned to the > web browser. > > When I try to install my own aspx pages (nice simple ones with only > HTML) I get the same error. > > Here are the mono packages I have installed, all of them at the > current Debian testing level. All packages have been removed and > reinstalled again, but the problem remains. > > mono-gac > mono-jay > mono-mcs > mono-utils > monodevelop > monodoc > monodoc-base > monodoc-browser > monodoc-http > monodoc-manual > mono-common > mono-jit > libmono0 > mono-assemblies-arch > mono-assemblies-base > mono-xsp > > This has also been tried under Apache using mono-apache-server but the > same error occurs with it too. > > Is something else supposed to be started ahead of time? What process > is the message refering to? > > Thanks in advance, > Chris. > > > > Server error in '/monodoc' application > > ------------------------------------------------------------------------ > *Description: *Error processing request. > > *Error Message: *HTTP 500. > > *Stack Trace: * || > > System.InvalidOperationException: Process has not been started. > in <0x0003b> System.Diagnostics.Process:get_ExitCode () > in <0x00050> (wrapper remoting-invoke-with-check) > System.Diagnostics.Process:get_ExitCode () > in <0x002bd> > Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch > (System.CodeDom.Compiler.CompilerParameters,string[]) > in <0x0044a> > Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDomBatch > (System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit[]) > > in <0x00050> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDom > (System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit) > > in <0x00171> System.Web.Compilation.CachingCompiler:Compile > (System.Web.Compilation.BaseCompiler) > in <0x002ea> System.Web.Compilation.BaseCompiler:GetCompiledType () > in <0x00251> System.Web.Compilation.AspGenerator:GetCompiledType () > in <0x00036> System.Web.UI.PageParser:CompileIntoType () > in <0x00018> System.Web.UI.TemplateControlParser:GetCompiledInstance () > in <0x00050> System.Web.UI.PageParser:GetCompiledPageInstance > (string,string,System.Web.HttpContext) > in <0x00011> System.Web.UI.PageHandlerFactory:GetHandler > (System.Web.HttpContext,string,string,string) > in <0x0034e> System.Web.HttpApplication:CreateHttpHandler > (System.Web.HttpContext,string,string,string) > in <0x0011f> CreateHandlerState:Execute () > > in <0x00084> StateMachine:ExecuteState > (System.Web.HttpApplication/IStateHandler,bool&) > > > > _______________________________________________ > Pkg-mono-devel mailing list > Pkg-mono-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-mono-devel > From miguel@novell.com Sun Feb 13 05:31:36 2005 From: miguel@novell.com (Miguel de Icaza) Date: Sun, 13 Feb 2005 00:31:36 -0500 Subject: [Pkg-mono-devel] Mono packaging on Debian. Message-ID: <1108272696.5808.182.camel@linux.site> Hello, I am mailing you because you seem to be involved in the Mono packaging for Debian. I apologize if I have reached you by mistake. The other day I was on the #ubuntu channel with a few folks trying to debug a few problems, and a few things were brought to my attention. I have read the document here: http://wiki.debian.net/?MonoConventions I do not know how much of this document has been implemented, so my comments might be incorrect. Please correct me if I am wrong. And wanted to discuss a few things: * Working together There are some important elements from that web page that we have integrated into Mono itself rendering some of your local changes un-necessary. I would like to get some feedback directly from you on the kinds of things that you are doing, so we can incorporate those into Mono proper reducing the per-distribution specific patches. * First There is a phenomenon: Mono 1.1.4 is now more stable, more reliable and better tested than Mono 1.0.xx ever was. Starting with this release (packages will be officially made available on Monday) we will recommend users to move to Mono 1.1.4 and abandon the 1.0.xx series, as we consider the 1.0.xx very buggy in contrast and has several limitations. * Executables We have moved all of the Mono executables from $prefix/bin and placed them in $prefix/lib/mono/VERSION, so there are no longer .exe files lying in $prefix/bin. This should address various of the needs that you have, in particular this means that we always have scripts in $prefix/bin so there is no need to create new ones. * FHS There are some problems with your assumptions and the way you have laid out packages. The ideal situation is for you guys to not make any changes to the locations that Mono is using. * /usr/share/dotnet This is a bad name for a number of reasons. First of all `dotnet' is a registered trademark. Second, we have worked really hard to make sure that we have two stacks: the Mono stack and the .NET stack, and you guys sticking a `dotnet' in the name will not help with perception from people. Third, this is the most important one: although *today* *most* of the DLL libraries that we ship are cross-platform, there is no guarantee that this will continue. Not only it is not a guarantee for Mono, but it is not a guarantee for third-party assemblies, these in particular are even more prone to include per-OS/per-architecture bytecode (Xsharp is one example, but the pattern is now used by various projects). This means that the code should not be in $prefix/share for any reason. The dlls should not be considered shareable across platforms. Fourth, it breaks Ahead-of-Time compilation: AOT requires a shared object living next to the assembly with native code (another reason that `share' wont work). By putting the stuff in 'share' you are making the code effectively non-shareable. * The use of /usr/bin/cli The command line options for `mono' and `mint' are different (and even Rotor's clix uses different options), if you are going to use a /usr/bin/cli, this should not be a symlink, this should be a new shell program that knows how to properly pass command line options to all possible environments. `Mono' is not like `java' in that the runtime arguments are fairly standard. In Mono there is no effort to do this, and we recommend that you do not try to isolate it. Miguel. From darren@winsper.org.uk Sun Feb 13 11:26:10 2005 From: darren@winsper.org.uk (Darren Winsper) Date: Sun, 13 Feb 2005 11:26:10 +0000 Subject: [Pkg-mono-devel] Mono packaging on Debian. In-Reply-To: <1108272696.5808.182.camel@linux.site> References: <1108272696.5808.182.camel@linux.site> Message-ID: <1108293971.32271.4.camel@localhost.localdomain> --=-Z1gdHMawU6bWeQps+jjr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-02-13 at 00:31 -0500, Miguel de Icaza wrote: =20 > * First >=20 > There is a phenomenon: Mono 1.1.4 is now more stable, more > reliable and better tested than Mono 1.0.xx ever was. How much is 1.1.4 going to differ from 1.2? Keep in mind that while 1.0 is quite old, it's at least not a moving target. --=20 "I will never apologize for the United States.|http://www.winsper.org.uk I don't care what the facts are." |ICQ: 8899775 --George W. Bush |Jabber & MSN: |darren@winsper.org.uk --=-Z1gdHMawU6bWeQps+jjr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCDzlS6wjBfQFSWs0RAqW5AKCGMTYGdvjpaHZo/3uDSd/20AeUjACdExro W6UbD+kVBDS/HXTpLZon/Yc= =SfuW -----END PGP SIGNATURE----- --=-Z1gdHMawU6bWeQps+jjr-- From meebey@meebey.net Fri Feb 18 11:25:34 2005 From: meebey@meebey.net (Mirco Bauer) Date: Fri, 18 Feb 2005 12:25:34 +0100 Subject: [Pkg-mono-devel] Re: [Pkg-mono-group] libgtk-cil package In-Reply-To: <1108718927.8120.7.camel@ebichu> References: <1108718927.8120.7.camel@ebichu> Message-ID: <1108725934.1764.6.camel@flyinghorse> --=-RKRb07qo9Iix0yodAkEj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Currently we are only packaging the stable branch of Mono and Gtk#, we have plans (yes only plans yet) to package Mono 1.1 and Gtk# 1.9 for experimental. Though you can use _third party_ gtk# 1.9 debian packages.=20 I heard at least 2 reports saying those packages work, but we can _not_ guaranty anything! here the URL: http://www.ilrt.bristol.ac.uk/people/cmdjb/2004/muine/devel/ On Fri, 2005-02-18 at 07:28 -0200, Rafael Jannone wrote: > Hi! >=20 > I'd like to know when you guys will release a newer version of > libgtk-cil, since the one in sid is lacking several interesting features > (like "Gtk.Action" for instance). >=20 > Also, if a newer package is too unstable to enter even sid, I'd like to > know where could I grab an experimental version of some kind. >=20 > Thanks a lot for helping Debian, you guys rock! :) >=20 > ps: I searched this: [1], and didn't find libgtk-cil in there, so that's > why I'm asking. >=20 > [1] http://packages.debian.org/experimental/allpackages >=20 --=20 Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=3Dget&search=3D0xEEF946C8 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d s-:+ a-- C++ UL++++$ P L++$>+++$ E- W+++$ N o? K- w++>! O---- M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y? ------END GEEK CODE BLOCK------ --=-RKRb07qo9Iix0yodAkEj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iQEVAwUAQhXQrnEn5avu+UbIAQKiUQgApTIHthdAKuthuygTHxGSk0bds4kNN0CM y0BjrBhxQiyQRrii652zbMz79eGXbtdPE8fULpHGIraugf/Fx4MA7xUp9p0w5Llr nYBUyuWv5NpaqdsmHd+Vijf8xRxNrt4fFHqvG4cbObsybrESo7ImPMXL5dgI9SK6 vCY4WR2/ACbQUNXBUowR5uET7CtyJrt/cwcTDJRexndW2/Tj+cwsoZCAdMTsZSx0 V5ZQ8AyaO3ciRK6b6Y2xsdFqKixw5ZdMgWmizoLQQ8r2/D2y2VadXt9Pyu1Y6bJh aWMPVGBc5a8LN5kZxMiVazYjhZZxFt+s9rfbh7TueiDjUMYNg+ysrQ== =JKsg -----END PGP SIGNATURE----- --=-RKRb07qo9Iix0yodAkEj-- From panmanphil@yahoo.com Fri Feb 18 14:42:05 2005 From: panmanphil@yahoo.com (Philip Nelson) Date: Fri, 18 Feb 2005 06:42:05 -0800 (PST) Subject: [Pkg-mono-devel] Re: [Pkg-mono-group] libgtk-cil package In-Reply-To: <1108725934.1764.6.camel@flyinghorse> Message-ID: <20050218144205.45823.qmail@web14206.mail.yahoo.com> --- Mirco Bauer wrote: > Currently we are only packaging the stable branch of Mono and Gtk#, we > have plans (yes only plans yet) to package Mono 1.1 and Gtk# 1.9 for > experimental. Was there any response to Miguel's suggestion that the 1.14 version *is* the stable branch? I know I posted a question here about a bug that had already been fixed, but was still broken in the sid release. > Though you can use _third party_ gtk# 1.9 debian packages. As I am mostly based on sarge (agnula distro), but found installing the mono release from sid was no problem, I would also like to know about other debs. I have had a similar conversation in the agnula community and would like to add my 2 cents here. Agnula is an audio focused distribution. Like the mono paths, the audio development rate is considerably faster than the base debian rate. In a sense, everything is moving all the time and in those situations, old is almost never *stable*. The mostly new release *is* the most stable, and the most featureful. I really think mono is in exactly this position. The agnula solution is a debian custom distribution, which is probably not the right solution for mono. But since there are few if any dependencies in debian on mono at this time, there is little risk to moving up the release chain as quickly as possible. ===== Philip - http://blogs.xcskiwinn.org/panmanphil "There's a difference between righteous anger and just being crabby" - Barbara From meebey@meebey.net Sat Feb 19 12:18:44 2005 From: meebey@meebey.net (Mirco Bauer) Date: Sat, 19 Feb 2005 13:18:44 +0100 Subject: [Pkg-mono-devel] The Mono Debian Plan [was Re: Mono packaging on Debian.] In-Reply-To: <1108272696.5808.182.camel@linux.site> References: <1108272696.5808.182.camel@linux.site> Message-ID: <1108815524.7574.13.camel@redbull.qnetp.net> --=-cIpI1/81adfA+xZDeUQh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I talked about this posting with Miguel via IRC, I prefer one short interactive discussion. I will write a quick response here anyhow for the readers of this mailing list, the result of the discussion with Miguel leads me to a new plan which you can find here: http://wiki.debian.net/?MonoDebianPlan (comments are welcome). On Sun, 2005-02-13 at 00:31 -0500, Miguel de Icaza wrote: > Hello,=20 > ... > * Working together >=20 > There are some important elements from that web page that we > have integrated into Mono itself rendering some of your local > changes un-necessary. > =20 > I would like to get some feedback directly from you on the kinds > of things that you are doing, so we can incorporate those into > Mono proper reducing the per-distribution specific patches. I fully agree here, we tried a few times to get in contact with mono developer but failed for several reasons. > =20 > * First >=20 > There is a phenomenon: Mono 1.1.4 is now more stable, more > reliable and better tested than Mono 1.0.xx ever was. >=20 > Starting with this release (packages will be officially made > available on Monday) we will recommend users to move to=20 > Mono 1.1.4 and abandon the 1.0.xx series, as we consider the > 1.0.xx very buggy in contrast and has several limitations. We plan (see the plan) to package Mono 1.1.x >=20 > * Executables >=20 > We have moved all of the Mono executables from $prefix/bin and > placed them in $prefix/lib/mono/VERSION, so there are no longer > .exe files lying in $prefix/bin. >=20 > This should address various of the needs that you have, in > particular this means that we always have scripts in > $prefix/bin so there is no need to create new ones. This is done since Mono 1.1.3, we really appreciate this change. >=20 > * FHS >=20 > There are some problems with your assumptions and the way you > have laid out packages. The ideal situation is for you guys > to not make any changes to the locations that Mono is using. >=20 > * /usr/share/dotnet >=20 > This is a bad name for a number of reasons. >=20 > First of all `dotnet' is a registered trademark. probably .NET is a registered trademark, dotnet maybe not, though this naming this be avoided, yes >=20 > Second, we have worked really hard to make sure that we have two > stacks: the Mono stack and the .NET stack, and you guys sticking > a `dotnet' in the name will not help with perception from > people. it's a directory base name like is /usr/share/java too >=20 > Third, this is the most important one: although *today* *most* > of the DLL libraries that we ship are cross-platform, there is > no guarantee that this will continue. >=20 > Not only it is not a guarantee for Mono, but it is not a > guarantee for third-party assemblies, these in particular are > even more prone to include per-OS/per-architecture bytecode > (Xsharp is one example, but the pattern is now used by various > projects). >=20 > This means that the code should not be in $prefix/share for > any reason. The dlls should not be considered shareable across > platforms. ok this one is a showstopper, we considered CIL assemblies are in any case arch-indep. >=20 > Fourth, it breaks Ahead-of-Time compilation: AOT requires a > shared object living next to the assembly with native code > (another reason that `share' wont work). By putting the=20 > stuff in 'share' you are making the code effectively > non-shareable. this is another big issue, which we must solve, breaking potential and important features is a no go. >=20 > * The use of /usr/bin/cli >=20 > The command line options for `mono' and `mint' are different > (and even Rotor's clix uses different options), if you are going > to use a /usr/bin/cli, this should not be a symlink, this should > be a new shell program that knows how to properly pass command > line options to all possible environments. >=20 > `Mono' is not like `java' in that the runtime arguments are > fairly standard. In Mono there is no effort to do this, and we > recommend that you do not try to isolate it. /usr/bin/cli can be used but must not be used, if the program can run on any runtime without specific runtime parameters (most programs don't need any) then it can call /usr/bin/cli, if a program depends on the mono runtime for whatever reason (like special parameters) it can always call /usr/bin/mono directly. >=20 > Miguel. >=20 > _______________________________________________ > Pkg-mono-devel mailing list > Pkg-mono-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-mono-devel --=20 Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=3Dget&search=3D0xEEF946C8 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d s-:+ a-- C++ UL++++$ P L++$>+++$ E- W+++$ N o? K- w++>! O---- M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y? ------END GEEK CODE BLOCK------ --=-cIpI1/81adfA+xZDeUQh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iQEVAwUAQhcupHEn5avu+UbIAQKzzwf/Ul0tPeA4EW3JWLfNpae9PyBzmudnveim Ebar0sjsdYQE866b4uDPcgZ+U37joczC2q+E8nc1zwbOkqk7CnCJ31/Sn8xfwLkQ dE9ZQazSs6fO1msJWfN20HMLw3DP6Qt6oJkQ6Mu+XYBxQJmPabXxp+Adt39GYtEE B+xesWENo7zmCym4BwQ+lneEdQKF3YEMxKDaIt9PAlfxWsCwxdAoWbiJgtNopTCJ dRlgz4zW/lI2Ovzp6JrzbQEQC184PRBmeRo+rOlkcXUCYinF7np8Mza3O8t+VbNB 0lkWPtJJjuvd+hcQsFbHQ25qcArqfMwWis7EBdg8YKw1gZzVEEh9Rg== =0BbK -----END PGP SIGNATURE----- --=-cIpI1/81adfA+xZDeUQh-- From dave@dajobe.org Sat Feb 26 23:16:58 2005 From: dave@dajobe.org (Dave Beckett) Date: Sat, 26 Feb 2005 23:16:58 +0000 Subject: [Pkg-mono-devel] Experimental gtk-sharp2 unstable packages Message-ID: <1109459818.8762.4.camel@hedwig.dajobe.org> I've been packaging these for some time in order that Muine could build against them. As discussed on #debian-mono, I've now renamed the source package to gtk-sharp2-unstable and added the "unstable" word liberally across the descriptions to give hints to people. I was thinking of uploading these to experimental in a day or two unless there are some particular problems. Later on if/when it gets accepted to the archive, it could migrate into a gtk-sharp2 source package name when the stable 2.0.0 release happens. The packages are at http://download.dajobe.org/debian/experimental/ Cheers Dave From phuegelm@uni-osnabrueck.de Sun Feb 27 14:02:22 2005 From: phuegelm@uni-osnabrueck.de (Philipp Huegelmeyer) Date: Sun, 27 Feb 2005 15:02:22 +0100 Subject: [Pkg-mono-devel] mon packages for sarge Message-ID: <1109512942.4503.5.camel@localhost.localdomain> Hi, I have packaged some mono packages for sarge from scratch. You can find the packages and aditional informations at http://linuxrepos.info/sarge-mono/ Cheers, Philipp H=FCgelmeyer From brandon@smarterits.com Sun Feb 27 16:32:16 2005 From: brandon@smarterits.com (Brandon Hale) Date: Sun, 27 Feb 2005 11:32:16 -0500 Subject: [Pkg-mono-devel] mon packages for sarge In-Reply-To: <1109512942.4503.5.camel@localhost.localdomain> References: <1109512942.4503.5.camel@localhost.localdomain> Message-ID: <1109521936.10276.1.camel@localhost.localdomain> On Sun, 2005-02-27 at 15:02 +0100, Philipp Huegelmeyer wrote: >Hi, > >I have packaged some mono packages for sarge from scratch. You can find >the packages and aditional informations at >http://linuxrepos.info/sarge-mono/ Hi, nice work. Can I suggest that you updated f-spot to 0.0.9-3, I worked around a bug relating to an unversioned import of libexif (you can reproduce by clicking View - Exif data with the libexif-dev package uninstalled). Thanks, Brandon Hale From brandon@smarterits.com Sun Feb 27 16:39:39 2005 From: brandon@smarterits.com (Brandon Hale) Date: Sun, 27 Feb 2005 11:39:39 -0500 Subject: [Pkg-mono-devel] mon packages for sarge In-Reply-To: <1109512942.4503.5.camel@localhost.localdomain> References: <1109512942.4503.5.camel@localhost.localdomain> Message-ID: <1109522379.10276.7.camel@localhost.localdomain> On Sun, 2005-02-27 at 15:02 +0100, Philipp Huegelmeyer wrote: >Hi, > >I have packaged some mono packages for sarge from scratch. You can find >the packages and aditional informations at >http://linuxrepos.info/sarge-mono/ > Oh, sorry to reply again. Where did you get that tomboy package? It's rather.. messy. If you take a look at the .diff.gz, you'll see that its full of autotools "leftovers", and a few other things that look out of place. I have also packaged tomboy, which is available in Ubuntu Hoary, and I'd dare to say it is a bit cleaner than this one. Once the Mono Conventions updates are sorted out, I intend to look for a sponsor for my package in Debian. Thanks, Brandon Hale From phuegelm@uos.de Sun Feb 27 17:29:24 2005 From: phuegelm@uos.de (=?ISO-8859-1?Q?Philipp_H=FCgelmeyer?=) Date: Sun, 27 Feb 2005 18:29:24 +0100 Subject: [Pkg-mono-devel] mon packages for sarge In-Reply-To: <1109521936.10276.1.camel@localhost.localdomain> References: <1109512942.4503.5.camel@localhost.localdomain> <1109521936.10276.1.camel@localhost.localdomain> Message-ID: <40ae5dc9a469e0b2993123af614259a1@uos.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 27.02.2005 um 17:32 schrieb Brandon Hale: > On Sun, 2005-02-27 at 15:02 +0100, Philipp Huegelmeyer wrote: >> Hi, >> >> I have packaged some mono packages for sarge from scratch. You can >> find >> the packages and aditional informations at >> http://linuxrepos.info/sarge-mono/ > > Hi, nice work. > Can I suggest that you updated f-spot to 0.0.9-3, I worked around a > bug relating to an unversioned import of libexif (you can reproduce by > clicking View - Exif data with the libexif-dev package uninstalled). > > Thanks, > Brandon Hale > From the page: The naming sheme is Packagename-((Original-Number)-1).hygl.(Number-Of-Build) to let mono fit in, when it will be released for testing. So the package is based on f-spot 0.0.9-3 :). I just found the tomboy package via www.apt-get.org and rebuild it. It was realy not working out that well, perhaps I will have a look at your package tomorrow and switch. Thanks, Philipp Huegelmeyer Universitaet Osnabrueck Tel: 0541-969-6510 (Buero)Zentrum VirtUOS Fax: 0541-969-16511 Schlossstrasse 9 D-49069 - - - ------------------------------------------------------------------ pgp-fingerprint: D008 BB2B 0B48 80EC CDF0 CBF0 D665 8CFF 63D9 DF8A - - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD4DBQFCIgNW1mWM/2PZ34oRAn9EAJdxZ55p+mmYX5kxun8HhQS19mUnAJwOJlJb JfYjW09xsGB5uUhBqatv1w== =Jx9o - - -----END PGP SIGNATURE----- Philipp Huegelmeyer Universitaet Osnabrueck Tel: 0541-969-6510 (Buero)Zentrum VirtUOS Fax: 0541-969-16511 Schlossstrasse 9 D-49069 - - ------------------------------------------------------------------ pgp-fingerprint: D008 BB2B 0B48 80EC CDF0 CBF0 D665 8CFF 63D9 DF8A - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCIgNv1mWM/2PZ34oRApH/AJsGoVZlwnQUw6Myj90i29yIQEtQLACggbjS YTdcDvwSbpM285r3jYNzzRE= =YnGw - -----END PGP SIGNATURE----- Philipp Huegelmeyer Universitaet Osnabrueck Tel: 0541-969-6510 (Buero)Zentrum VirtUOS Fax: 0541-969-16511 Schlossstrasse 9 D-49069 - ------------------------------------------------------------------ pgp-fingerprint: D008 BB2B 0B48 80EC CDF0 CBF0 D665 8CFF 63D9 DF8A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCIgN01mWM/2PZ34oRAi+uAJ9dXMpfPFHrjISWIo3+81wtgTshLwCeL/gl mjVBYJA3f+43ttiAZ7WwAxc= =y48f -----END PGP SIGNATURE-----