Re: postgresql 6.5.3 vs. debian
Oliver Elphick wrote: w trillich wrote: that's somewhere else entirely! eureka! ls -F1 /usr/lib/postgresql/bin cleardbdir* createlang* destroylang* do.maintenance* initdb* initlocation* ipcclean* pg_dumpall* pg_encoding* pg_id* pg_passwd* pg_upgrade* pg_version* postgres* postgresql-dump* postgresql-startup* postmaster@ save_db_schema* vacuumdb* see? there's no createdb, no psql, no destroyuser... Aha; have you installed postgresql-client? I split the package, because it is possible to have the front-end on a different machine from the backend. However, postgresql ought to depend on postgresql-client. that sure looks promising... dang. i thought you had it for a minute. # apt-get install postgresql-client Reading Package Lists... Done Building Dependency Tree... Done Sorry, postgresql-client is already the newest version 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. (that 1 not upgraded is enlightenment, which is mucho coolio, but i'm not going for xwindows, i'm going for web server and dbms... maybe on my next machine when i'm wealthy and infamous...) It looks as though I have missed some dependencies somewhere. maybe 'suggests' as opposed to 'depends'? or, have only the pgsql-client pak install the psql/createdb/etc links? hmmm... thinking... yes, your dbms administrator will probably need to frob, tweak and munge on occasion, so psql (and friends) would most likely be standard toolbox for server machines; but for client machines they'd not need the server engine, so you're probably right--server depends on client, tho it seems odd at first glance. (p.s. where can i get psql and createdb and so forth?)
Re: postgresql 6.5.3 vs. debian
w trillich wrote: Oliver Elphick wrote: Aha; have you installed postgresql-client? I split the package, because it is possible to have the front-end on a different machine from the backend. However, postgresql ought to depend on postgresql-client. that sure looks promising... dang. i thought you had it for a minute. # apt-get install postgresql-client Reading Package Lists... Done Building Dependency Tree... Done Sorry, postgresql-client is already the newest version 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. (that 1 not upgraded is enlightenment, which is mucho coolio, but i'm not going for xwindows, i'm going for web server and dbms... maybe on my next machine when i'm wealthy and infamous...) It looks as though I have missed some dependencies somewhere. In fact, no: Package: postgresql Version: 6.5.3-18 Section: misc Priority: optional Architecture: i386 Depends: libc6 (= 2.1.2), libncurses5, libreadline4 (= 4.1),libpgsql2 (= 6.5.1), debianutils (= 1.7), procps (= 1.9), postgresql-client, procps (= 2.0) Suggests: libpgperl,libpgjava,libpgtcl,postgresql-doc,ecpg,postgresql-pl, postgresql-dev,postgresql-contrib,python-pygresql Conflicts: postgres95,libpq1,libpgtcl (= 6.4-0.1),postgresql-client (= 6.5.3-2) So the proper dependency is already there, (and so is the dependency on procps, which gave you trouble earlier). maybe 'suggests' as opposed to 'depends'? or, have only the pgsql-client pak install the psql/createdb/etc links? hmmm... thinking... yes, your dbms administrator will probably need to frob, tweak and munge on occasion, so psql (and friends) would most likely be standard toolbox for server machines; but for client machines they'd not need the server engine, so you're probably right--server depends on client, tho it seems odd at first glance. (p.s. where can i get psql and createdb and so forth?) I must say, you seem to have a right mess here! What happened to the packages you tried to produce with alien? Are they still lying around? If they are installed, purge them. Check that your current installation appears to be OK: `apt-get check'. Then try `apt-get --reinstall install postgresql-client libpgsql2 postgresql' -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 I sought the LORD, and he heard me, and delivered me from all my fears.Psalms 34:41
Re: postgresql 6.5.3 vs. debian
just like star wars, rebel fighters in the trench heading towards the exhaust port: almost there almost there the apt-get --reinstall worked really well. now there's something weird with the initlocation script, probably a setting i've got going someplace. as the initlocation script goes thru its arguments, looking for -u and so forth, it gives $PGALTDATA anything it can't figure out what else to do with: case $1 in snipsnip *) PGALTDATA=$1; ;; esac turns out, with my settings the whole bloomin' ENVIRONMENT get crammed into $PGALTDATA. this is bad because (here's a sh -xv `which initlocation` -u postgres trace): if [ ! -d $PGALTDATA ]; then echo Creating Postgres database system directory $PGALTDATA echo mkdir $PGALTDATA if [ $? -ne 0 ]; then exit 1; fi chown $POSTGRES_SUPERUSERNAME $PGALTDATA fi + '[' '!' -d PWD=/var/postgres/data LESSEDIT=%E '?lt+%lt.' %f VENDOR=intel PAGER=less REMOTEHOST=jonathon HZ=100 HOSTNAME=server HIS TFILESIZE=1000 'LESSOPEN=|' lesspipe %s VISUAL=vi LESS=-M-Q-s USER=root MACHTYPE=i386-pc-linux-gnu MAIL=/var/spool/mail/root EDITOR= vi LANG=C HOST=server LOGNAME=root SHLVL=3 GROUP=serensoft HUSHLOGIN=FALSE SHELL=/usr/bin/tcsh HOSTTYPE=i386 OSTYPE=linux-gnu HISTSI ZE=1000 TERM=vt220 HOME=/root PATH=/usr/lib/postgresql/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/ bin LESSCHARSET=latin1 _=/usr/bin/printenv ']' /usr/lib/postgresql/bin//initlocation: [: too many arguments if [ ! -d $PGALTDATA/base ]; then echo Creating Postgres database system directory $PGALTDATA/base echo mkdir $PGALTDATA/base if [ $? -ne 0 ]; then exit 1; fi chown $POSTGRES_SUPERUSERNAME $PGALTDATA/base fi + '[' '!' -d PWD=/var/postgres/data LESSEDIT=%E '?lt+%lt.' %f VENDOR=intel PAGER=less REMOTEHOST=jonathon HZ=100 HOSTNAME=server HIS TFILESIZE=1000 'LESSOPEN=|' lesspipe %s VISUAL=vi LESS=-M-Q-s USER=root MACHTYPE=i386-pc-linux-gnu MAIL=/var/spool/mail/root EDITOR= vi LANG=C HOST=server LOGNAME=root SHLVL=3 GROUP=serensoft HUSHLOGIN=FALSE SHELL=/usr/bin/tcsh HOSTTYPE=i386 OSTYPE=linux-gnu HISTSI ZE=1000 TERM=vt220 HOME=/root PATH=/usr/lib/postgresql/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/ bin LESSCHARSET=latin1 _=/usr/bin/printenv/base ']' /usr/lib/postgresql/bin//initlocation: [: too many arguments luckily it bombed, or it'd be creating all kinds of colorful filenames and subdirectories for me to dessimate by hand... not that big a deal, of course, in this instance, but maybe it's a situation to trap for? (i'm using tcsh, like any self- respecting ex-sysadmin would, of course.) --- just so you know: THANKS for being so understanding with me, i really appreciate it. this has been a hellacious ordeal, and it looks like i'm at the end of the tunnel, finally! i'm not feeling so snappish any more... you have the patience of a saint! (maybe you could spread it around? bottle it up and sell it?)
Re: postgresql 6.5.3 vs. debian--THE WINNER
i was beginning to think it'd never get to this: _/_/_/ _/_/_/_/ _/_/ _/_/ _/_/_/ _/ _/ _/_/_/ _/ _/ _/ _/_/ _/_/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/_/_/ _/_/ _/_/_/ _/ _/ _/ _/ _/ _/ _/_/ _/_/ _/ _/ _/ _/_/_/_/_/ _/ _/_/ _/_/ _/_/ _/_/_/ _/ postgresql 6.5.3 and debian-freeze walk out of the ring, hand-in-hand, virtually fondling one another! wedding bells! now i'm off to find why DBI::Pg broke... you folks have been great--especially Oliver (and Jeff and Keith and Edward and Eric and Bruce and Brian...) thanks! holy cow! WE *ARE* ##THERE##! yahoo*! *any resemblance to certain directories/search engines is purely coincidental and all respective copyrights are owned by the owners of the respective copyrights.
Re: postgresql 6.5.3 vs. debian
w trillich wrote: just like star wars, rebel fighters in the trench heading towards the exhaust port: almost there almost there the apt-get --reinstall worked really well. now there's something weird with the initlocation script, probably a setting i've got going someplace. WHY are you using initlocation? initdb is the command to use to create your database. I have never actually heard of anyone's using initlocation! Do you really need to have separate storage areas? as the initlocation script goes thru its arguments, looking for -u and so forth, it gives $PGALTDATA anything it can't figure out what else to do with: case $1 in snipsnip --location=*) PGALTDATA=`echo $1 | sed 's/^--pgdata=//'`; ;; -D) shift; PGALTDATA=$1; ;; *) PGALTDATA=$1; ;; esac Notice that it is taking one single parameter, so all the garbage below must have been in quotes. turns out, with my settings the whole bloomin' ENVIRONMENT get crammed into $PGALTDATA. this is bad because (here's a sh -xv `which initlocation` -u postgres trace): ... trace snipped ... not that big a deal, of course, in this instance, but maybe it's a situation to trap for? (i'm using tcsh, like any self- respecting ex-sysadmin would, of course.) Having been brought up on SysV, I regard csh as a snare and a delusion. How did it manage to put your environment onto the command line? Perhaps I should test for the parent process: if it is a csh derivative I will go off and sulk! :-) I can't really modify the script on the basis that users are likely to throw junk at it! This is a (postgres-)superuser program; the user is supposed to know what he's doing. just so you know: THANKS for being so understanding with me, i really appreciate it. this has been a hellacious ordeal, and it looks like i'm at the end of the tunnel, finally! i'm not feeling so snappish any more... Did you get any sleep last night? you have the patience of a saint! (maybe you could spread it around? bottle it up and sell it?) See sig. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 I sought the LORD, and he heard me, and delivered me from all my fears.Psalms 34:41
Re: postgresql 6.5.3 vs. debian--THE WINNER
(on-list again) On Thu, Apr 13, 2000 at 02:26:03PM -0500, w trillich wrote: kmself@ix.netcom.com wrote: (off list) While it's always rewarding to get something that was broken to work, it's usually more illuminating for the rest of the world to find out some details of *how* you fixed it. This is actually a valuable service of mailing lists and Usenet. exactly so. but i have the feeling that the original problem was quite that-- original--with me, due to my flailing around in the dark with only a few outdated HOWTOs over here and HTML manuals over there to guide me. a thousand monkeys at random will never churn out a single line of shakespeare, i now know for certain... You'd be surprised at how often this occurs. Outdated packages, confusion over package management tools, etc. Even from those of use who've used Unix for fscking ever (13 years), Linux for a while (4 years), and Debian long enough to know some warts (6 months). maybe i could summarize, in public, the important points i learned: rpm: bad dpkg: not as bad dselect: not bad apt-get: recommended and then a browse thru some of the --reinstall and --purge iterations. what do you think? That's actually a reasonably good summary -- flesh it out to maybe three times the length describing the problem, why various approaches were bad, and a command sequence that finally got things working. Advantage being that everything's in one place. I'm doing some DB installations myself, and was skimming your thread, but didn't have time (bandwidth to signal is getting really, really nuts) to read closely. A closing post summarizing the situation is a Good Thing (tm). (maybe mention the URL of a more current FAQ at the tail of the debian-user list, near the 'unsubscribe' tag? you may already post such a best periodically as some lists do--i've not been on here long enough to guess on that one.) Sorry -- FAQ for Debian, the List, or what? -- Karsten M. Self (kmself@ix.netcom.com) What part of Gestalt don't you understand? http://gestalt-system.sourceforge.net/
Re: postgresql 6.5.3 vs. debian
On Tue, Apr 11, 2000 at 03:21:20PM -0500, Jeff Noxon wrote: Why, pray tell, are you trying to install RedHat postgresql RPMs on a Debian system? Debian has postgresql 6.5.3 already, in frozen. What you are doing with RPMs is just asking for trouble. The easiest thing to do is just upgrade your whole system to frozen. If you can't, then set up apt (/etc/apt/sources.list) to access your nearest mirror and run apt-get install postgresql ... this should upgrade just postgresql and the parts of your system it depends on. Yes, and make sure you dump your old postgres database before upgrade. The newer postgresql uses a different binary format. On Tue, Apr 11, 2000 at 03:10:35PM -0500, w trillich wrote: aaugh! i'm having my fourth day of troubles trying to upgrade my 6.3 pgsql (came on the debian cd) to 6.5.3, and i'm hoping someone might have the insight i need to get over this hurdle... these are the postgres files i'd love to install: postgresql-6.5.3-3.i386.rpm or postgresql-devel-6.5.3-3.i386.rpm postgresql-perl-6.5.3-3.i386.rpm postgresql-server-6.5.3-3.i386.rpm postgresql-test-6.5.3-3.i386.rpm onto snip -- ¶ One·should·only·use·the·ASCII·characterset·when·compos » ing·email·messages.
Re: postgresql 6.5.3 vs. debian
aha. Jeff Noxon wrote: Why, pray tell, are you trying to install RedHat postgresql RPMs on a Debian system? Debian has postgresql 6.5.3 already, in frozen. What you are doing with RPMs is just asking for trouble. mostly because i didn't know any better... i tried to avoid it, really! i started with dselect, then tried munging directly with dpkg and then fell back to rpm. i'm a bit new at this, and i've got this paranoid fear of missing The One Settings file for every keystroke i enter... The easiest thing to do is just upgrade your whole system to frozen. If you can't, then set up apt (/etc/apt/sources.list) to access your nearest mirror and run apt-get install postgresql ... this should upgrade just postgresql and the parts of your system it depends on. no shit? pardon my grammar. wow. that sounds delightful. i haven't run across that yet in the mountains of documents i've looked through (four weeks and counting). thanks! hey everybody! check out this debian APT thing! cool!
Re: postgresql 6.5.3 vs. debian
to get me up-to-date on postgresql 6.5.3, Jeff Noxon recommended: # apt-get install postgresql [snip] Setting up postgresql (6.3.2-15) ... which is exactly the version i already had. i'd also recently installed perl 5.6, which was just replaced when i tried further and did # apt-get upgrade so now my perl scripts and cgi programs are mostly broken. for example-- Can't locate File/Spec.pm in @INC (@INC contains: /usr/lib/perl5/i386-linux/5.004 /usr/lib/perl5 /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl .) at /usr/local/lib/site_perl/DBI.pm line 531. i'll fix it--i kept the 5.6 perl around here somewhere. checking the apt-get manpage, i then tried # apt-get dselect-upgrade # apt-get dist-upgrade and # apt-get -f to fix whatever's broke... but at least i still have postgresql 6.3.2, that's a comfort... grr. can you 'splain, in really small, simple terms, so i can follow along, how to get 6.5 postgresql? -- |/|/|\ /| /|\ /| | | \http://www.flintschool.com/will/\| \| \ ---/ |\|\|\-\--/ |-/ |\-\--- /__|_|_|_\_\Flint School/__|/__|_\_\ \/ '76 to '80 \/ teQuest Te Vega
Re: postgresql 6.5.3 vs. debian
Keith G. Murphy wrote:
to get me up-to-date on postgresql 6.5.3, Jeff Noxon recommended:
# apt-get install postgresql
[snip]
Setting up postgresql (6.3.2-15) ...
which is exactly the version i already had.
It's probably because you were still pointing to 'stable' and got its
latest version of postgresql.
Add this line to your /etc/apt/sources.list:
deb ftp://ftp.debian.org/debian frozen main contrib non-free
Or wherever your favorite mirror is, just pointing it to frozen is the
important thing.
Then:
apt-get update --(*not* upgrade)
So your system will be aware of all the latest packages.
Now:
apt-get install postgresql
should work. I believe the upgrade process prompts you to be sure
you've dumped your former databases, but you might want to do it ahead
of time just to be sure...
holy mackerel! i can see! i can see!
i'm sure that two year from now, in the sanitarium, osmosis
would've kicked in and i'd have been able to know which
manpages to go to and which commands to configure... but for
now, i feel like i'm in a twisted maze of little passages,
all different.
mucho thanks!
===
of course, nothing can go perfectly smoothly--here's how it
ended:
# apt-get install postgresql
yada yada
Run postgresql-dump to dump the old database and to reload
it in the new format.
*** READ /usr/share/doc/postgresql/README.Debian.migration.gz FIRST! ***
The version 6.5 postmaster cannot be started until
this is done.
ps: unknown long option
usage: ps acehjlnrsSuvwx{ttty|#|O[-]u[-]U..} \
--sort:[-]key1,[-]key2,...
--help gives you this message
--version prints version information
so now i gotta figure out how to get the old postgres out
(there's no useful data, i could just ditch the /var/postgres/data
directory but i'm sure that'd break something, right) and then
get the new one in...
===
why did i try the *deb/*rpm method? why, i simply read
the documentation...
part of where i got misdirected, i suppose, was from
doc/debian/FAQ/debian-faq-10.html and others like it.
yank a *deb, it recommends, and then dpkg to install it.
document is probably from 1943 or so.
===
speaking of which, i'm looking at
doc/HOWTO/mini/Hard-Disk-Upgrade.html
to get a second hard drive going. is that
page up-to-date or should i look elsewhere?
Re: postgresql 6.5.3 vs. debian
Eric Hanchrow wrote: w == w trillich [EMAIL PROTECTED] writes: w aaugh! w i'd appreciate any direction... thanks (i've still got some hair w left, and would like to keep it). Would you consider upgrading to potato, and then installing postgresql 6.5.3 from potato? That way you don't have to deal with rpm's. I can vouch that * upgrading from slink to potato isn't difficult and * postgresql works fine on potato coming from the midwest, i used to think that a potato was something dan quayle never actually misspelled, and that farmers grew. what the hell is potato, in debian/linux context? i would consider almost anything, but not prior to knowledge of it...
Re: postgresql 6.5.3 vs. debian
On Wed, 12 Apr 2000, w trillich wrote: what the hell is potato, in debian/linux context? The name of the next release of Debian, also known as Debian 2.2 or frozen. later, Bruce
Re: postgresql 6.5.3 vs. debian
w trillich wrote:
of course, nothing can go perfectly smoothly--here's how it
ended:
# apt-get install postgresql
yada yada
Run postgresql-dump to dump the old database and to reload
it in the new format.
*** READ /usr/share/doc/postgresql/README.Debian.migration.gz FIRST! ***
The version 6.5 postmaster cannot be started until
this is done.
ps: unknown long option
usage: ps acehjlnrsSuvwx{ttty|#|O[-]u[-]U..} \
--sort:[-]key1,[-]key2,...
--help gives you this message
--version prints version information
You need to update procps, because the command line options of ps changed
a lot and postgresql's installation scripts use the new options.
After doing that, do `dpkg --pending --configure', which should pick up
postgresql and run its post-installation script again.
Then go and read the migration README, as recommended. (see above)
so now i gotta figure out how to get the old postgres out
(there's no useful data, i could just ditch the /var/postgres/data
directory but i'm sure that'd break something, right) and then
get the new one in...
That would destroy your data. If you have a backup in pg_dump format, you
could use that to restore.
===
why did i try the *deb/*rpm method? why, i simply read
the documentation...
part of where i got misdirected, i suppose, was from
doc/debian/FAQ/debian-faq-10.html and others like it.
yank a *deb, it recommends, and then dpkg to install it.
Yes, so far as it goes. However, doing it that way means you have to wait
to find out what its dependencies are and go and fetch the required
packages, and then the same again for them...
When you've finally got them all, `dpkg --pending --configure' will finish
the installation, unless you have unsatisfiable dependencies.
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
For the word of God is quick, and powerful, and
sharper than any twoedged sword, piercing even to
dividing soul and spirit, joints and marrow; and is a
discerner of the thoughts and intents of the heart.
Hebrews 4:12
Re: postgresql 6.5.3 vs. debian
okay. i removed postgresql.
i purged it. eradicated it from the system. gone.
then i did
# apt-get install postgresql
[snip] and halleleujah, everything went smoothly... until:
Starting PostgreSQL postmaster
ps: unknown long option
usage: ps acehjlnrsSuvwx{ttty|#|O[-]u[-]U..} \
--sort:[-]key1,[-]key2,...
--help gives you this message
--version prints version information
# su will
createdb will
Could not execv /usr/lib/postgresql/bin/createdb
psql
Could not execv /usr/lib/postgresql/bin/psql
ls -l `which createdb`
lrwxrwxrwx 1 root root 10 Apr 12 11:53
/usr/bin/createdb - pg_wrapper*
ls -l `which pg_wrapper`
-rwxr-xr-x 1 root root 4428 Apr 6 16:02 /usr/bin/pg_wrapper*
^D
# punt
punt: Command not found.
#
i know in my bones it shouldn't be this hard. i've obviously
mucked something somewhere.
anybody got a clue on how i can fix this?
if you're dying to help (not everyone at once) see the full transcript
of my apt-get at http://208.33.90.85/psql.txt in case that gives you
any clues. (i'm trying not to clutter up the list here.)
next thing i'll try is a whole
# apt-get dist-upgrade
and keep my fingers crossed...
Re: postgresql 6.5.3 vs. debian
Oliver Elphick wrote:
w trillich wrote:
# apt-get install postgresql
yada yada
ps: unknown long option
usage: ps acehjlnrsSuvwx{ttty|#|O[-]u[-]U..} \
--sort:[-]key1,[-]key2,...
--help gives you this message
--version prints version information
You need to update procps, because the command line options of ps changed
a lot and postgresql's installation scripts use the new options.
aha. i think i see light at the end of the tunnel.
# apt-get install procps
Reading Package Lists... Done
Building Dependency Tree... Done
1 packages upgraded, 0 newly installed, 0 to remove and 320 not upgraded.
yada yada
all went well. hopes are up.
After doing that, do `dpkg --pending --configure', which should pick up
postgresql and run its post-installation script again.
sounds easy.
# dpkg --pending --configure
#
hopes are down a tad. didn't seem to do anything! so i try
# dpkg --configure postgresql
dpkg: error processing postgresql (--configure):
package postgresql is not ready for configuration
cannot configure (current status `installed')
Errors were encountered while processing:
postgresql
hopes are back where they were.
maybe i'll deinstall and then reinstall (fifth
time's the charm)
Then go and read the migration README, as recommended. (see above)
when i get there, i will be sure to do so...
i sure appreciate all you folks giving suggestions, but
lemme tellya it's hard to keep the positive attitude!
i can tell that the debian arrangement is kick-ass... this
apt-get looks wonderful, much better than the rpm stuff
i've seen. IN THEORY. my encounters in practice are of
course tainted by all these blood-tipped strands of hair
all over the floor around my chair. (can't figure out
where they came from, either.)
Re: postgresql 6.5.3 vs. debian
champagne all around. i uninstalled postgresql. # dpkg -r postgresql i PURGED postgresql. # dpkg --purge postgresql i installed postgresql. # dpkg -i postgresql and no errors! drinks on me! so i enter createdb will Could not execv /usr/lib/postgresql/bin/createdb apparently the drinks are on me all right, i'm feeling soaked. -- |/|/|\ /| /|\ /| | | \http://www.flintschool.com/will/\| \| \ ---/ |\|\|\-\--/ |-/ |\-\--- /__|_|_|_\_\Flint School/__|/__|_\_\ \/ '76 to '80 \/ teQuest Te Vega
Re: postgresql 6.5.3 vs. debian
Why, pray tell, are you trying to install RedHat postgresql RPMs on a Debian system? Debian has postgresql 6.5.3 already, in frozen. What you are doing with RPMs is just asking for trouble. The easiest thing to do is just upgrade your whole system to frozen. If you can't, then set up apt (/etc/apt/sources.list) to access your nearest mirror and run apt-get install postgresql ... this should upgrade just postgresql and the parts of your system it depends on. Regards, Jeff On Tue, Apr 11, 2000 at 03:10:35PM -0500, w trillich wrote: aaugh! i'm having my fourth day of troubles trying to upgrade my 6.3 pgsql (came on the debian cd) to 6.5.3, and i'm hoping someone might have the insight i need to get over this hurdle... these are the postgres files i'd love to install: postgresql-6.5.3-3.i386.rpm or postgresql-devel-6.5.3-3.i386.rpm postgresql-perl-6.5.3-3.i386.rpm postgresql-server-6.5.3-3.i386.rpm postgresql-test-6.5.3-3.i386.rpm onto Linux 2.0.36 #2 Sun Feb 21 15:55:27 EST 1999 i586 unknown here's the group of error messages i run into when merely CONVERTING (via 'alien') the *.rpm's to *.deb's: dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/pg_dump': ` libreadline.so.3 = not found' dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/pg_dump': ` libhistory.so.3 = not found' dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/pg_id': ` libreadline.so.3 = not found' dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/pg_id': ` libhistory.so.3 = not found' dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/psql': `libreadline.so.3 = not found' dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp/usr/bin/psql': `libhistory.so.3 = not found' dpkg: /lib/libtermcap.so.2 not found. so i hopped on the web and searched for *.rpm's that would take care of filling in the missing holes: libtermcap-2.0.8-20.i386.rpm -- contains /lib/libtermcap.so.2.0.8 (to which i linked the sought-after libtermcap.2.0 via 'ln -s libtermcap.so.2.0.8 libtermcap.so.2.0' thinking that internal tweaks wouln't break the interface) readline-2.2.1-6.i386.rpm -- contains /usr/lib/libhistory.so.3.0 /usr/lib/libreadline.so.3.0 (which i linked to the sought-after filenames in similar fashion to the method i used for libtermcap) but doing so seems to not helped one iota, even after going into 'dselect' and choosing to update package info from the mounted directory where the *deb packages reside. nearly giving up, i tried using the RPM installer instead: # rpm -i libtermcap-2.0.8-20.i386.rpm failed dependencies: /etc/termcap is needed by libtermcap-2.0.8-20 /sbin/ldconfig is needed by libtermcap-2.0.8-20 /bin/sh is needed by libtermcap-2.0.8-20 ld-linux.so.2 is needed by libtermcap-2.0.8-20 libc.so.6 is needed by libtermcap-2.0.8-20 libc.so.6(GLIBC_2.0) is needed by libtermcap-2.0.8-20 libc.so.6(GLIBC_2.1) is needed by libtermcap-2.0.8-20 # rpm -i libtermcap-2.0.8-20.i386.rpm failed dependencies: /etc/termcap is needed by libtermcap-2.0.8-20 /sbin/ldconfig is needed by libtermcap-2.0.8-20 /bin/sh is needed by libtermcap-2.0.8-20 ld-linux.so.2 is needed by libtermcap-2.0.8-20 libc.so.6 is needed by libtermcap-2.0.8-20 libc.so.6(GLIBC_2.0) is needed by libtermcap-2.0.8-20 libc.so.6(GLIBC_2.1) is needed by libtermcap-2.0.8-20 i'd appreciate any direction... thanks (i've still got some hair left, and would like to keep it). [accidentally posted this to debian-devel this morning. whoops.]
