This is not a top-post. It is a new thread which introduces an older problem and copies parts of previous posts in an attempt to clarify the situation so a generous SuSE guru can help me - and perhaps others? I need to update subversion and apache2 on SuSE 9.1 and after downloading patches YOU doesn't offer the current versions. My plan A is to buy SuSE 9.3 and hope they are up to date in there. Being in a hurry I don't want to wait for 9.3. Plan B is to start again somehow. I tried a week or so ago and didn't succeed following Graham Smith's advice (9 March 2005 - Re: [SLE] Make yast repository)
Have a look at this article in the sdb. Generating YaST Installation Sources http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html
Any help gratefully received. As mentioned previously I'm new at all this. This is what I posted back then ...
However, I'm having trouble with genIS_PLAINcache ...
I have downloaded direct from SuSE
from ... ftp://ftp.suse.org/pub/projects/apache/apache2/9.1-i386/
the following RPMs ... apache2-2.0.53-4.1.i586.rpm apache2-devel-2.0.53-4.1.i586.rpm apache2-doc-2.0.53-4.1.i586.rpm apache2-example-pages-2.0.53-4.1.i586.rpm apache2-mod_auth_mysql-2.8.1-1.1.i586.rpm apache2-mod_perl-2.0.0-1.1.i586.rpm apache2-mod_python-3.1.3-37.4.i586.rpm apache2-prefork-2.0.53-4.1.i586.rpm apache2-worker-2.0.53-4.1.i586.rpm libapr0-2.0.53-4.1.i586.rpm neon-0.24.7-4.1.i586.rpm neon-devel-0.24.7-4.1.i586.rpm subversion-1.1.3-7.1.i586.rpm subversion-devel-1.1.3-7.1.i586.rpm subversion-doc-1.1.3-7.1.i586.rpm subversion-perl-1.1.3-7.1.i586.rpm subversion-python-1.1.3-7.1.i586.rpm subversion-server-1.1.3-7.1.i586.rpm subversion-tools-1.1.3-7.1.i586.rpm
They are in /root/samba_share/install_kits/suse_9.1_dvd/suse/new-i586 (feel free to constructively criticise my choice of download destination in a separate thread)
I followed the instructions listed at the link below (reproduced here) - except for what I believe is an error ...
cd /srv/www/htdocs/suse/RPMS/ genIS_PLAINcache -f -r . gzip genIS_PLAINcache
When I pointed YaST to that directory it barfed and went away with an error message too quick to read.
Thanks for any help Mike
If I'm understanding you correctly, there are 2 issues. Getting new apache and subversion than 9.1 doesn't have. Letting YOU do the update. Were you able to get the newer versions installed and working without YOU? (configure, make, make install, etc.) and then having trouble making the new rpm's? I myself have never played with making rpm's, let alone update rpm's that YOU would recognize. If these are the case I would get it working first, so you can move on, and then see if 9.3 doesn't have the same versions that you wanted to goto anyway. B-) On Wednesday 16 March 2005 03:53 pm, Mike Dewhirst wrote:
This is not a top-post. It is a new thread which introduces an older problem and copies parts of previous posts in an attempt to clarify the situation so a generous SuSE guru can help me - and perhaps others?
I need to update subversion and apache2 on SuSE 9.1 and after downloading patches YOU doesn't offer the current versions.
My plan A is to buy SuSE 9.3 and hope they are up to date in there. Being in a hurry I don't want to wait for 9.3.
Plan B is to start again somehow. I tried a week or so ago and didn't succeed following Graham Smith's advice (9 March 2005 - Re: [SLE] Make yast repository)
Have a look at this article in the sdb. Generating YaST Installation Sources http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html
Any help gratefully received. As mentioned previously I'm new at all this.
Brad Bourn wrote:
If I'm understanding you correctly, there are 2 issues.
Getting new apache and subversion that 9.1 doesn't have.
Only one. Just getting subversion up to 1.1.3 and apache to 2.0.53
Letting YOU do the update.
I just wanted you to know I have tried a couple of ways to do it. I don't really care about YOU or YaST because they don't seem to do the job. If they worked for me I'd be moving on already.
Were you able to get the newer versions installed and working without YOU? (configure, make, make install, etc.) and then having trouble making the new rpm's?
No. I wouldn't know where to start with configure, make, etc. I went down the rpm road after seeing Graham Smith's post. It seemed like it would contribute to getting YaST to ork for me.
I myself have never played with making rpm's, let alone update rpm's that YOU would recognize.
Now you tell me ...
If these are the case I would get it working first,
That is what I'd love to do. Where do I start?
so you can move on, and then see if 9.3 doesn't have the same versions that you wanted to goto anyway.
I'm sure 9.3 will be up to date with everything. I'm an optimist :) Thanks Brad Mike
B-)
On Wednesday 16 March 2005 03:53 pm, Mike Dewhirst wrote:
This is not a top-post. It is a new thread which introduces an older problem and copies parts of previous posts in an attempt to clarify the situation so a generous SuSE guru can help me - and perhaps others?
I need to update subversion and apache2 on SuSE 9.1 and after downloading patches YOU doesn't offer the current versions.
My plan A is to buy SuSE 9.3 and hope they are up to date in there. Being in a hurry I don't want to wait for 9.3.
Plan B is to start again somehow. I tried a week or so ago and didn't succeed following Graham Smith's advice (9 March 2005 - Re: [SLE] Make yast repository)
Have a look at this article in the sdb. Generating YaST Installation Sources http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html
Any help gratefully received. As mentioned previously I'm new at all this.
Ok, noooooo problem! hehehehe This is VERY generic and I haven't messed with either package, but here is generally what happens. If your on a 32-bit machine, all the better. first thing (don't be scared!) get the tar.gz of the SOURCE for both packages. extract the source tar zxvf program.tar.gz then you should see a dir program-1.2.3 or similar go into that directory and look for a file called INSTALL first, or README second. they should tell you literally what to do, most likely it will be run configure (this will check that you have what is needed to compile and install the software) It will mostly likely error out and tell you you need this or that. Install what it needs from Yast. You might even need to install some gnu make stuff to get this far. Once you can get configure to work, it will tell you (it = configure) what you need to do to build and install. most likely will be make (build) then make install (copy files to userland and setup environment) Once you do these a few times, it will become allot less confusing. Wait till you get to a 64-bit SuSE machine and try to install something from source that never new about 64-bit environments before...... (fun, fun) Hope this helps B-) On Wednesday 16 March 2005 04:34 pm, Mike Dewhirst wrote:
That is what I'd love to do. Where do I start?
The Wednesday 2005-03-16 at 16:45 -0700, Brad Bourn wrote:
then
make install (copy files to userland and setup environment)
Never do that. Call "checkinstall" instead: it creates an rpm file that keeps your rpm database happy (meaning that Yast knows about you meddling with things :-p ) Of course, the correct way would be to create an spec file and build the rpm, but... we are not developpers, are we? ;-) -- Cheers, Carlos Robinson
Comments interspersed. Brad Bourn wrote:
first thing (don't be scared!) get the tar.gz of the SOURCE for both packages. extract the source tar zxvf program.tar.gz
then you should see a dir program-1.2.3 or similar go into that directory and look for a file called INSTALL first, or README second.
they should tell you literally what to do, most likely it will be
run configure (this will check that you have what is needed to compile and install the software)
Make that ./configure (otherwise you'll get the mysterious message "Command not found" although the file is clearly there) (snip)
make (build)
then
make install (copy files to userland and setup environment)
It is much better to install "checkinstall" first (from the SuSE disk) and replace the last step by checkinstall This will build you an rpm that you can install in the usual way so you will maintain system integrity. Best regards, -- Jos van Kan www.josvankan.tk
participants (4)
-
Brad Bourn
-
Carlos E. R.
-
Jos van Kan
-
Mike Dewhirst