some problems with the suse rpms

Hi, a friend of mine tried to install midgard on a plain SuSE 9.2
system. He had the following problems:

* If you install from a bought version of SuSE the ImageMagic version
used is ImageMagick-6.0.7-4.4.
* In the same way, the php-version is 4.3.8-8

I suggest that we try to set the versionnumbers not as what is the
latest and greatest version but what is needed. Thus we can avoid issues
like these in the future.

Tarjei
--

-- 
Tarjei Huse <tarjei@...>

Regarding tigris

Greetings!

Looks like comments like these are becoming an everyday matter:

[12:50] torben: "the operation timed out when contacting 
midcom.tigris.org" *grumblinginhisthreedaybeard*
[12:50] jval: I was just about to ask if tigris is down again

So, it starts to be clear we need to get out of there. Some quick
thoughts:

* Switching from CVS to Subversion running on the m-p.org server
* Switching to OpenPSA Support for bug tracking
* How about mailing lists? Now tigris hosts bug tracker and commit
   lists
* If we host the services ourselves we need to mirror them between
   the different Midgard companies

Lets talk about this in the Helsinki Workshop.

/Bergie

--

-- 
Henri Bergius                           Henri.Bergius@...
Consultant Partner                      Tel: +358-20-198 6032
Nemein Oy                               http://www.nemein.com/

installation problems

dear all

most of my time spent to install the midgard using YUM always facing this kind of problems.
i dont really know what it cause.. is there any best way to install midgard ..

thanks :

for your ref:

Performing the following to resolve dependencies:
  Install: ImageMagick.i386 0:6.2.0.7-2.fc3
  Install: midgard-apache2.i386 0:1.6.3-1
  Install: midgard-core.i386 0:1.6.3-1
  Install: midgard-data.noarch 0:1.6.3-2
  Install: midgard-php4.i386 0:1.6.3-1.1
  Install: php-mbstring.i386 0:4.3.10-3.2
  Update: php.i386 0:4.3.10-3.2
  Update: php-devel.i386 0:4.3.10-3.2
  Update: php-ldap.i386 0:4.3.10-3.2
  Update: php-mysql.i386 0:4.3.10-3.2
  Update: php-odbc.i386 0:4.3.10-3.2
  Update: php-pear.i386 0:4.3.10-3.2
  Update: php-pgsql.i386 0:4.3.10-3.2
Is this ok [y/N]: y
Downloading Packages:
midgard-1.6.3-1.noarch.rp 100% |=========================| 6.8 kB    00:00
midgard-data-1.6.3-2.noar 100% |=========================| 4.3 MB    00:02
midgard-apache2-1.6.3-1.i 100% |=========================|  42 kB    00:00
midgard-php4-1.6.3-1.1.i3 100% |=========================| 131 kB    00:00
midgard-core-1.6.3-1.i386 100% |=========================| 119 kB    00:00

Re: installation problems

Hi,

> most of my time spent to install the midgard using YUM always facing this kind of problems.
> i dont really know what it cause.. is there any best way to install midgard ..
Seems like you are trying this on Fedora Core 3, right? Exact distro
name makes it easier to help :)

> warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 4f2a6fd2
> public key not available for //var/cache/yum/updates-released/packages/ImageMagi ck-6.2.0.7-2.fc3.i386.rpm
This is not a Midgard issue, but a YUM issue. In order for YUM to
verify the package signatures, you will have to import the signing GPG
keys for these RPM packages.

In your case I would suggest to run

# rpm --import /usr/share/doc/fedora-release-*/RPM-GPG-KEY*

To install the Midgard packages via RPM, please see the Fedora install
instructions:
http://www.midgard-
project.org/documentation/installation/distros/fedora.html

With kind regards,
Daniel S. Reichenbach
--

-- 
blog - http://people.best-off.org/~dsr/
gpg  - http://people.best-off.org/~dsr/gpg.asc
work - http://www.best-off.org/

RE: installation problems

hi 

it works, and midgard is served up. thanks.

-----Original Message-----
From: Daniel S. Reichenbach [mailto:dsr@...]
Sent: Wed 4/6/2005 1:48 PM
To: dev@...
Subject: Re: [midgard-dev] installation problems

Hi,

> most of my time spent to install the midgard using YUM always facing this kind of problems.
> i dont really know what it cause.. is there any best way to install midgard ..
Seems like you are trying this on Fedora Core 3, right? Exact distro
name makes it easier to help :)

> warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 4f2a6fd2
> public key not available for //var/cache/yum/updates-released/packages/ImageMagi ck-6.2.0.7-2.fc3.i386.rpm
This is not a Midgard issue, but a YUM issue. In order for YUM to
verify the package signatures, you will have to import the signing GPG
keys for these RPM packages.

In your case I would suggest to run

# rpm --import /usr/share/doc/fedora-release-*/RPM-GPG-KEY*

To install the Midgard packages via RPM, please see the Fedora install
instructions:

Access by peer

Hi. 

I have a problem cant access the midgard from other pc in LAN network.
I used the IP or servername but the page display is default Apache page.
not the midgard cms even i ve created the virtual host name.

thanks in advance.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: Access by peer

Hello,

Nazri Bin Abdullah wrote:
> Hi. 
> 
> I have a problem cant access the midgard from other pc in LAN network.
> I used the IP or servername but the page display is default Apache page.
> not the midgard cms even i ve created the virtual host name.

Does your host-table entries match with the Apache VirtualHost
configuration?

If you have VirtualHost configured with an IP (i.e. 192.168.0.1),
your MySQL host-table should have record with name=192.168.0.1.

Please send us your VirtualHost configuration (hide any passwords)
and your host-table description ("select * from host;"), and then
tell us which URL-address you're trying to reach from the other PC.

> thanks in advance.

Cheers!

   //Henri

--

-- 
Henri Kaukola			Henri.Kaukola@...
Consultant			Tel: +358-20-198 6037
Nemein Oy			http://www.nemein.com

RE: Access by peer

here i enclosed localhost_80 file from vhost and data from table host

thanks 

-----Original Message-----
From: Henri Kaukola [mailto:henri.kaukola@...]
Sent: Thu 4/7/2005 2:56 PM
To: dev@...
Subject: Re: [midgard-dev] Access by peer

Hello,

Nazri Bin Abdullah wrote:
> Hi. 
> 
> I have a problem cant access the midgard from other pc in LAN network.
> I used the IP or servername but the page display is default Apache page.
> not the midgard cms even i ve created the virtual host name.

Does your host-table entries match with the Apache VirtualHost
configuration?

If you have VirtualHost configured with an IP (i.e. 192.168.0.1),
your MySQL host-table should have record with name=192.168.0.1.

Please send us your VirtualHost configuration (hide any passwords)
and your host-table description ("select * from host;"), and then
tell us which URL-address you're trying to reach from the other PC.

Re: Access by peer

Hi,

> I have a problem cant access the midgard from other pc in LAN network.
> I used the IP or servername but the page display is default Apache page.
> not the midgard cms even i ve created the virtual host name.
If you are running the default Fedora Core installation, you will have
your firewall configured to block any external access and thus you can
not access the httpd service from anywhere but localhost. In order to
enable access, please run

# system-config-security

on the command-line. There you can allow access to port 80 and thus
you should be able to access your Midgard pages from other systems.

With kind regards,
Daniel S. Reichenbach
--

-- 
blog - http://people.best-off.org/~dsr/
gpg  - http://people.best-off.org/~dsr/gpg.asc
work - http://www.best-off.org/

RE: Access by peer

is it system-config-securitylevel. if then
i had disabled my system firewall.

-----Original Message-----
From: Daniel S. Reichenbach [mailto:dsr@...]
Sent: Thu 4/7/2005 3:20 PM
To: dev@...
Subject: Re: [midgard-dev] Access by peer

Hi,

> I have a problem cant access the midgard from other pc in LAN network.
> I used the IP or servername but the page display is default Apache page.
> not the midgard cms even i ve created the virtual host name.
If you are running the default Fedora Core installation, you will have
your firewall configured to block any external access and thus you can
not access the httpd service from anywhere but localhost. In order to
enable access, please run

# system-config-security

on the command-line. There you can allow access to port 80 and thus
you should be able to access your Midgard pages from other systems.

With kind regards,
Daniel S. Reichenbach
--

-- 
blog - http://people.best-off.org/~dsr/
gpg  - http://people.best-off.org/~dsr/gpg.asc