cups upgrade went pear shaped
 

Hi again, must stop saying that. Well, I was doing a cups upgrade to help with printer problems. The version I had was 1.1.23-i486-4.
Slackware had a newer version so I opted for an upgrade. The newer version is 1.2.10-i486-1. The install seemed to go ok until I tried to start cups. The diagnostic code that came up was "libgnutils.so.13" Cannot open shared object file - doesn't exist bla,bla,. I know that cups has later upgrades - opted for the slackware one to minimize problems-Ha,Ha.

Why am I getting this error code?
As always, appreciate a little help with this one.

bookie

P.S. I think I'm going senile.

Because you grabbed the binary package out of current? Use
the source package, run the build-script and then it should
be all sweet. In fact, I grabbed the source package for cups
1.2.11 today, replaced the source in the slack-source with
that and edited the build-script to use 1.2.11 instead just
today :} ... all well with the world.


Cheers,
Tink

update success
 

Thanks Tinkster, you took the words right out of my mouth. I looked at cups and downloaded the 1.2.11. I have always had a bit of a problem when the files don't end in tgz. It is easy with the pkgtool when installing the tgz files - one doesn't have to worry about where they end up.
Well, because it was a source file - and me trying to be a smart arse - I created a file in src
mkdir /usr/src/cups
called it cups for ease of finding the file ok. Moved the file from desktop to cups
mv Desktop/cups-1.2.11-source.tar.gz /usr/src/cups
This went ok I then tared the file
cd /usr/src/cups
/usr/src/cups# tar -xvzf cups-1.2.11-source.tar.gz

This also went ok. I then cd into the cups directory and started the install according to cups install file
cd cups-1.2.11
cups-1.2.11#./configure
This went ok. I then run make and make install all without problems. My cups is working fine - but, sorry, I'm getting to the point. Thought I'd check the package handler to see if it was in the list. No dice. Obviously when we run pkginstall tgz it puts all the files where they should be and one can find them in the package handler.
Can you tell me where I should put the files from start to finish. I accept this is all part of the learning process - it's just that I would like to put all my files, as root, where they should be before going back to user. I haven't been so successful in removing the tar files after installation using the command console? End up sending them to the trash bin as a last result!!

Sorry to be so long winded - just like to do everything right from word go.

If you just compile CUPS from source you loose the configuration,
the files will end-up in the /usr/local directory.

I (again) recommend using the source package with build-script
from Slackware-current.
Re-pack your 1.2.11 package:
Move the new cups-1.2.11-source.tar.bz2 into the directory
that wget created for you .../source/a/cups/ ... cd there.

Edit cups.Slackbuild, find 1.2.10 and replace it with 1.2.11

su root
sh cups.Slackbuild
installpkg /tmp/cups-1.2.11*tgz



Cheers,
Tink

update
 

Thanks Tinkster, been a little busy with re-installing slackware 11. I will use your info a little later. I will post eventually - when everything else is up and running again.

Until then - thanks again.

bookie

Re - cups problems
 

Hi Tinkster, I must confess that I tried to use your info - using wget - didn't have any luck at all. I tried my mirrors close to me - they couldn't find anything?! I even tried to find slackbuild no dice. I finally went to slackware and took the tgz file from current. I then used the upgradepkg tool and installed the file. After reboot cupsd couldn't start there was a problem with the lidbus-1.so3 no file or directory!! I would really like to understand why the upgradepkg cannot upgrade cups? Sorry to be a pain. I appreciate all you have tried to do for me - just cannot seem to understand what I'm doing wrong.

Would you like to try again? I now have cups 1.2.11 installed. My package manager confirms that. I am certain it is a case, as you say of updating some info - it's just the how is the bit that escapes me.

bookie

Because new dependencies have been introduced in current
that your old install doesn't satisfy. Which is where the
source comes in.
http://slackware.cs.utah.edu/pub/sla...source/a/cups/

Get the stuff (everything but the actual cups-source, cups-1.2.11-source.tar.bz2)
from there. Put it in a directory, edit the build-script (cups.SlackBuild) to
point at your newly created 1.2.12 tar.bz2.



Cheers,
Tink

update
 

Thanks Tinkster, sorry to say I so not follow what you are trying to say. What directory do I move these packages to? How do I edit cups slackbuild? Please don't worry - I am not cut out for linux -too much to learn. Going back to windows. Don't like windows, but one doesn't have to spend days, weeks, trying to understand the most basic of commands.

Thanks again.
bookie

Sorry Tinkster
 

Sorry Tinkster - bit tetchy today. Broke a tooth yesterday - costs a fortune here in Sweden!! Anyway, doing a re-install and will have cups-1.1.23-i486-4 on the computer that I would like to upgrade to the latest or next latest. I have downloaded the source file from slackware-current cups- 1-2-11-source.tar.bz and is now currently on the desktop. I work as root when installing and then return to user afterwards. Ihave spent so much time on this my girlfriend is losing her patience. I have tried everything your have written - even though I don't really understand. I cannot get any where!! If I can't find a straight forward version of installing from scratch or upgrading that I can understand - then I will have to go back to windows. Run build script??? replace the source in slackware source??? Nothing makes any sense. Getting really fedup with re-installing because of lack of knowledge.
If you don't want to help, then I will understand. I only wish I could understand what you have said already?!!

I am a novice and can´t understand all the dialogue. It is why we are called newbies.

bookie

Realistically you can use ANY directory to do this. Commonly I'll
work in /tmp or my users ~/tmp ... as for the editing: the script
is a plain ASCII file, any editor (not word processor) will do.
kate, emacs, nano, vi .... whatever blows your skirt. I'm tempted
to re-build my package and run that all under script so you can
*see* what I did.


Cheers,
Tink


P.S.: You won't learn to swim if you avoid water.

update
 

Hi Tinkster, I feel like some one who is about to learn to ride a bike. We all know that it is easy when you know how - it's the learning that doesn't always go according to plan.
It is hard for some one who "can" to imagine the frustration that someone else can feel who "can't". Am I making sense? I am hoping that there will come a time when I can ride my bike and can help others that can't. Some times I can't see the wood for the trees. If you are willing to try something else, then I am very grateful. Let's just say that you have been riding your bike for quite some time and I have a long way to go.

If you wont give up, then how can I?



P.s. Glad to see you have a sense of humor.
Thanks
bookie

That's a nice comparison, and even though I've been using
Linux for quite some time now I can still remember my initial
frustration when I moved over from OS/2. :}

That's the spirit, mate. Hang in there. And if you're happy
to wait until Sunday or Monday I'm happy to do the "script" thing.
I won't be able to do it today, too much other stuff to do.
script (in case you haven't guessed it or looked it up) allows you
to record *ALL* steps that you're taking in a shell.



Cheers,
Tink

Thanks Tinkster
 

Just post when you have the time. I have other issues to deal with.

bookie

PS
What do you mean you have a lot to do to day? My day is almost over. 22:45 in the evening here in Sweden.

Saturday morning in NZ ;}

Shopping, washing, vacuuming and other cleaning activities, .... I'm
on and off the browser between loads of washing atm :}


Cheers,
Tink

Hi Tinkster
 

Well, please don't think that I am impatient, but I started the upgrade process by configuring, make, and make installing to see if there was something I missed. I couldn't see any thing, so I un-installed. Obviously some thing went wrong with that because the standard version of cups doesn't want to work now. I will leave it to you have more time - don't relish the idea of re-installing slackware again- Need to learn how to deal with problems at ground level!!

bookie
PS Not much into house work at the mo.