Moonfire Games

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: mono and apache  (Read 6495 times)

kaliban555

  • 100 point character
  • **
  • Status: 0
  • Posts: 3
    • View Profile
mono and apache
« on: September 18, 2006, 09:03:47 AM »

Hello, sorry for disturbing this forum, but I feel I can
find here the developer of the "mono for debian" packages.

Some months ago I've developed an application on a debian/testing box.
(and that machine was no more updated) adding the
"deb http://debian.meebey.net/ ./" line to /etc/apt/sources.list

Now, after some time, I've build up the production machine...
I tried for about two days to get the dependencies working,
but had no way...for example, by now I try :

apt-get install mono-common
The following packages have unmet dependencies.
  mono-common: Depends: libglib2.0-0 (>= 2.12.0) but 2.10.3-3 is to be installed
E: Broken packages

and the same for many other packages...

In particulare I need to get working the libapache-mod-mono package...

There is any hope to make it work under the debian-testing ?
I can't reinstall the machine, it's already in production environment...

thank you and best regards




Logged

D. Moonfire

  • Divinity +N
  • 300 point character
  • *****
  • Status: 0
  • Posts: 309
    • View Profile
    • WWW
Re: mono and apache
« Reply #1 on: September 20, 2006, 05:23:17 AM »
From what I know, meebey's repository is built against Debian unstable, which is probably what you don't want. I would say your best bet is to either remove meebey's repository or use your pin file to include only the Debian unstable stuff you need.

And with the thundering silence here, don't worry about posting. :) That's what it is here for.
Logged

kaliban555

  • 100 point character
  • **
  • Status: 0
  • Posts: 3
    • View Profile
Re: mono and apache
« Reply #2 on: September 20, 2006, 10:39:32 PM »
From what I know, meebey's repository is built against Debian unstable, which is probably what you don't want. I would say your best bet is to either remove meebey's repository or use your pin file to include only the Debian unstable stuff you need.

And with the thundering silence here, don't worry about posting. :) That's what it is here for.

First of all, thank you for replying =)

newbie reply : "never used pin file" ... I'm just looking at the docs !
(i just hope not to get the entire unstable libs...)


addendum: I've installed with your advice the needed packages (libapache2-mono-mono, etc.)
BUT still when I start apache2 I get :

[Thu Sep 21 10:02:40 2006] [notice] caught SIGTERM, shutting down
[Thu Sep 21 10:02:43 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Thu Sep 21 10:02:43 2006] [notice] LDAP: SSL support unavailable
[Thu Sep 21 10:02:43 2006] [error] Failed running '/usr/lib/pkgconfig/../../bin/mod-mono-server --filename /tmp/mod_mono_server_default --applications /euwebmaker:/var/www/euwebmaker --nonstop (null) (null) (null) (null) (null) (null) (null)'. Reason: No such file or directory
[Thu Sep 21 10:02:43 2006] [error] Failed running '/usr/lib/pkgconfig/../../bin/mod-mono-server --filename /tmp/mod_mono_server_default --applications /euwebmaker:/var/www/euwebmaker --nonstop (null) (null) (null) (null) (null) (null) (null)'. Reason: No such file or directory
[Thu Sep 21 10:02:43 2006] [notice] Apache/2.0.55 (Debian) mod_mono/1.1.17 PHP/4.4.2-1.1 configured -- resuming normal operations
[Thu Sep 21 10:02:43 2006] [error] Failed running '/usr/lib/pkgconfig/../../bin/mod-mono-server --filename /tmp/mod_mono_server_default --applications /euwebmaker:/var/www/euwebmaker --nonstop (null) (null) (null) (null) (null) (null) (null)'. Reason: No such file or directory
[Thu Sep 21 10:02:43 2006] [error] Failed running '/usr/lib/pkgconfig/../../bin/mod-mono-server --filename /tmp/mod_mono_server_default --applications /euwebmaker:/var/www/euwebmaker --nonstop (null) (null) (null) (null) (null) (null) (null)'. Reason: No such file or directory
[Thu Sep 21 10:02:43 2006] [error] Failed running '/usr/lib/pkgconfig/../../bin/mod-mono-server --filename /tmp/mod_mono_server_default --applications /euwebmaker:/var/www/euwebmaker --nonstop (null) (null) (null) (null) (null) (null) (null)'. Reason: No such file or directory



I've checked the files, they are all in place...
where could I get a log of what is doing the mono "machine" ?



Kind Regards!

« Last Edit: September 20, 2006, 11:58:47 PM by kaliban555 »
Logged

D. Moonfire

  • Divinity +N
  • 300 point character
  • *****
  • Status: 0
  • Posts: 309
    • View Profile
    • WWW
Re: mono and apache
« Reply #3 on: September 21, 2006, 07:02:33 AM »
You have libapache2-mod-mono, do you also have mono-apache-server (ASP.NET 1.1) or mono-apache-server2 (for ASP.NET 2.0) also installed?

Pin files are pretty easy to use. What I do is this.

Run "apt-get update;apt-get upgrade" and make sure you don't have anything to upgrade. The Debian repository are set up pretty easily for that. The file you look at is /etc/apt/preferences. You can add unstable and pin it very low with something like this:

Code: [Select]
Package: *
Pin: release o=Debian,a=unstable
Pin-Priority: 1

You need to update your /etc/apt/sources.list file:

Code: [Select]
deb ftp://ftp.us.debian.org/debian unstable main contrib non-free
d

When you do an "apt-get update;apt-get upgrade" you should not see hundreds of packages that need to update. If you see it, the pin wasn't right and I probably gave you a slightly wrong direction.

Once you have it set up like that, you have two options. The best one is to just install the minimum you need for mod-mono.

"apt-get install libapache2-mod-mono/unstable mono-server" or something like that. Really pay attention to what it wants to install then. You might need to add a few more packages as part of the apt-get install.

I haven't used testing in a LONG time, so I'm not sure of the exact impact.
Logged

kaliban555

  • 100 point character
  • **
  • Status: 0
  • Posts: 3
    • View Profile
Re: mono and apache
« Reply #4 on: September 21, 2006, 01:49:15 PM »

hello, at last it worked out =)

what was lastly wrong was the version of mono-apache-server
(1.1.15 instead of 1.1.17)

finally it's all ok!!

now...return to code =)


kind regards !
Logged
Pages: [1]   Go Up
« previous next »