Re: dist-upgrade (from potato to woody) snag
will writes: seeing lots of this during an apt-get dist-upgrade from potato to woddy today: yada snip Setting up libxslt1 (1.0.16-0.1) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). Setting up libreadline4 (4.2a-5) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). Setting up libssl0.9.6 (0.9.6c-2.woody.1) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). yada snip 1) is this an unimportant side-effect that can be ignored? 2) is it fixable? i toyed with oracle 8i for about half a day and then went postgresql instead. is that the 'oracle' being referred to? if so, what's it got to do with ldconfig? If you are no longer using the libraries in /usr/oracle/lib and it is listed in /etc/ld.so.conf, then you may want to remove the listing of it in /utc/ld.so.conf. If apt-get is running ldconfig after it updates libraries (which it looks like it is) and /usr/orace/lib is listed in the dynamic linker's configuration file, /etc/ld.so.conf, then ldconfig is checking that library to help set-up the dynamic library sub-system and apparently there is something wrong with libvbj30ssl.so. I suggest removing /usr/oracle/lib from /etc/ld.so.conf and then re-running ldconfig. Elizabeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (from potato to woody) snag
On Sun, Nov 24, 2002 at 10:14:37PM -0600, will trillich wrote: seeing lots of this during an apt-get dist-upgrade from potato to woddy today: yada snip Setting up libxslt1 (1.0.16-0.1) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). okay, on the theory that apt-get dist-upgrade is a bit like a rolling pin where each iteration smooths out some more bumps (hey, it's worked like that before) i'm doing other iterations and still get the Setting up console-tools-libs (0.2.3-23.3) ... /sbin/ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). stuff but now i also see a new oddness: Setting up console-tools (0.2.3-23.3) ... Installing new version of config file /etc/console-tools/config ... dhelp_parse: no title found for directory graphics dhelp_parse: no title found for directory net dhelp_parse: no title found for directory system dhelp_parse: no title found for directory tools dhelp_parse: no title found for directory dhelp_parse: no title found for directory graphics dhelp_parse: no title found for directory net dhelp_parse: no title found for directory tools dhelp_parse: no title found for directory dhelp_parse: no title found for directory graphics dhelp_parse: no title found for directory net dhelp_parse: no title found for directory system dhelp_parse: no title found for directory tools dhelp_parse: no title found for directory Looking for keymap to install: us Loading /etc/console/boottime.kmap.gz dhelp_parse: no title found for directory graphics dhelp_parse: no title found for directory net dhelp_parse: no title found for directory tools dhelp_parse: no title found for directory dhelp_parse: no title found for directory graphics dhelp_parse: no title found for directory net dhelp_parse: no title found for directory system dhelp_parse: no title found for directory tools dhelp_parse: no title found for directory eh? is this making me skip important config dialogs? - i also noticed on the first iteration that the standard file command hadn't been installed, and was tripping up some of the install process. apparently it was downloaded and installed mid-process somewhere, because it's there now... at start of first apt-get dist-upgrade, it was # whereis file file: and (gladly, after first iteration of dist-upgrade) it's now # whereis file file: /usr/bin/file /usr/share/man/man1/file.1.gz -- I use Debian/GNU Linux version 2.2; Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown DEBIAN NEWBIE TIP #11 from Will Trillich [EMAIL PROTECTED] : Which COMMANDS pertain to xyz? Try apropos xyz, info xyz, and man -k xyz. Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (from potato to woody) snag
On Sun, Nov 24, 2002 at 10:32:03PM -0600, Elizabeth Barham wrote: will writes: seeing lots of this during an apt-get dist-upgrade from potato to woddy today: yada snip Setting up libxslt1 (1.0.16-0.1) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). Setting up libreadline4 (4.2a-5) ... ldconfig: /usr/oracle/lib/libvbj30ssl.so is not a shared object file (Type: 768). yada snip 1) is this an unimportant side-effect that can be ignored? 2) is it fixable? If you are no longer using the libraries in /usr/oracle/lib and it is listed in /etc/ld.so.conf, then you may want to remove the listing of it in /utc/ld.so.conf. i never in a billion years would have thought it was that easy. even if i'm the one who added /usr/oracle/lib to the ld.so.conf file myself lo these many moons ago, i've spawned a whole new personality since then... thanks for the tip! much help there. I suggest removing /usr/oracle/lib from /etc/ld.so.conf and then re-running ldconfig. and what took you so long? it was nearly 18 minutes before my question was fully and completely answered. :) (last time i called microso~1 i was on hold for twice that long!) debian rocks. linux rules. -- I use Debian/GNU Linux version 2.2; Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown DEBIAN NEWBIE TIP #125 from Colin Watson [EMAIL PROTECTED] : Ever wondered about confirming WHAT CPU, KERNEL OR DEBIAN VERSION YOU HAVE? It's easy: cat /proc/cpuinfo There's lots of other neat stuff under /proc, too. (You guessed it -- man proc will tell you more.) For kernel and Debian data, try uname -a cat /etc/debian_version Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade from potato to woody
On Sat, Jul 21, 2001 at 09:17:27PM +0100, Graham Ward wrote: | I just tried to upgrade my system from potato to woody. I believe | these are the correct steps: | | (1) replace potato with woody everywhere in /etc/apt/sources.list | (2) apt-get update | (3) apt-get dist-upgrade. These are good. | When I do step (3), I see (among other things) the message | | | WARNING: The following essential packages will be removed | This should NOT be done unless you know exactly what you are doing! | sysvinit util-linux (due to sysvinit) | 544 packages upgraded, 87 newly installed, 36 to remove and 6 not upgraded. | Need to get 348MB of archives. After unpacking 173MB will be used. | You are about to do something potentially harmful | | | On the face of it, removing sysvinit looks like a bad idea, so I | stopped at this point. Has something gone horribly wrong with my | set-up, or is this in fact harmless? Yeah, you kinda want to have an init on the system :-) (without it you won't be able to boot). It is possible (but I'm not looking at packages.debian.org right now) that sysvinit isn't in testing. I recommend putting potato in sources.lst after woody. apt is smart enough to get just the latest version of the packages. This way you will get the new stuff that is in testing, but you won't lose stuff that is in potato but not woody. HTH, -D
dist-upgrade from potato to woody
Hi all, I just tried to upgrade my system from potato to woody. I believe these are the correct steps: (1) replace potato with woody everywhere in /etc/apt/sources.list (2) apt-get update (3) apt-get dist-upgrade. When I do step (3), I see (among other things) the message WARNING: The following essential packages will be removed This should NOT be done unless you know exactly what you are doing! sysvinit util-linux (due to sysvinit) 544 packages upgraded, 87 newly installed, 36 to remove and 6 not upgraded. Need to get 348MB of archives. After unpacking 173MB will be used. You are about to do something potentially harmful On the face of it, removing sysvinit looks like a bad idea, so I stopped at this point. Has something gone horribly wrong with my set-up, or is this in fact harmless? Thanks in advance for any guidance. Cheers, Graham
Re: dist-upgrade from potato to woody
On Sat, Jul 21, 2001 at 09:17:27PM +0100, Graham Ward wrote: I just tried to upgrade my system from potato to woody. I believe these are the correct steps: (1) replace potato with woody everywhere in /etc/apt/sources.list (2) apt-get update (3) apt-get dist-upgrade. When I do step (3), I see (among other things) the message WARNING: The following essential packages will be removed This should NOT be done unless you know exactly what you are doing! sysvinit util-linux (due to sysvinit) 544 packages upgraded, 87 newly installed, 36 to remove and 6 not upgraded. Need to get 348MB of archives. After unpacking 173MB will be used. You are about to do something potentially harmful On the face of it, removing sysvinit looks like a bad idea, so I stopped at this point. Has something gone horribly wrong with my set-up, or is this in fact harmless? If you go ahead you system will most likely be hosed. Why aren't you using dselect? Both the dpkg and apt-get manual suggest you use dselect as a frontend to manage the package selections. For complex operations like distribution upgrades, you should really always use dselect. Here's what I would do in your current situation, I've added step (-1) to get your system back to its initial state: (-1) reset the available database to stable: place back potato everywhere in /etc/apt/sources.list and run: dpkg --clear-avail (0) prepare for the upgrade by running: dselect update select in the select screen, verify that you have no current unresolved dependencies and that your package selections are sane, eg all packages marked for installation are installed and at their latest versions. (1) replace potato with woody everywhere in /etc/apt/sources.list (2) update available list and verify the new dependencies by running: dselect update select In the selections screen, don't add new packages yourself, just press enter and let dselect ponder on the current selections. As there have been some replacements in packages and some changed dependencies between packages, dselect will prompt you with a list of packages involved in an unresolved dependency. Investigate the suggestions by dselect and accept these if reasonable. (3) download and install upgraded packages by running: dselect install Most dselect operations can also be done from the dselect main menu, which can be started by running dselect without command line arguments. Cheers, Joost
