Re: Problem updating Freebsd ver 6.2
Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). Up to know, I was unable to kill this error and, in consequence, my samba server is not working. Does anybody could help me to fix this problem? I don't know what else to do. Thanks in advance Read /usr/ports/UPDATING there is a significant change that may affect you and which in any case indicates it is a good time to update all ports: 20070318: AFFECTS: users of devel/gettext (ie: YOU) AUTHOR: [EMAIL PROTECTED] As a result of the upgrade to gettext-0.16.1, the shared library version of libintl has changed, so you will need to rebuild all ports that depend on gettext (ie: most of them, sorry) Partially upgrading can give some errors like the one you mention. Note: I don't say that your problem is caused by this upgrade, but you will resolve the problem and avoid future dependency problems if you update all ports. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org smime.p7s Description: S/MIME Cryptographic Signature
Re: Problem updating Freebsd ver 6.2
On Fri, 11 May 2007 01:45:47 -0500 WizLayer [EMAIL PROTECTED] wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. Yes, update your ports tree and then run: portmanager -u -l -p You can substitute the 'f' flag for the 'p' one if you want to redo the system. -- Gerard Fortune favors the lucky. signature.asc Description: PGP signature
Re: Problem updating Freebsd ver 6.2
Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Gerard Seibert [EMAIL PROTECTED] escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. Yes, update your ports tree and then run: portmanager -u -l -p You can substitute the 'f' flag for the 'p' one if you want to redo the system. -- Gerard Fortune favors the lucky. - Llama gratis a cualquier PC del mundo. Con una excelente calidad de sonido. Yahoo! Messenger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem updating Freebsd ver 6.2
On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Gerard Seibert [EMAIL PROTECTED] escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. Yes, update your ports tree and then run: portmanager -u -l -p You can substitute the 'f' flag for the 'p' one if you want to redo the system. Top posting is generally considered rude, just so you know... Any rate, your next option is to locate the missing library, figure out where your app thinks the library should be, and then ln to it so that your app sees the link... Any particular reason you're using portmanager (I haven't used it recently, but have had bad experiences with it in the past. I'm one of those who prefer portupgrade). Of course, I'm not saying this is a fault with portmanager. I honestly don't know. I was just wondering why you were using it (ie maybe it's been matured enough that I should check it out again). Don't know what else to tell you. WizLayer -- Life is better with a BSD. For more info, www.bsd.org. pgpajYes9Yvec.pgp Description: PGP signature
Re: Problem updating Freebsd ver 6.2
On Fri, 11 May 2007, Simon Castillo wrote: Hi Garret: Freebsd ver 6.2 Samba: from ver 3.0.23 to 3.0.24 gdm: From ver 2.16 to 2.18 Thanks Simon Garrett Cooper [EMAIL PROTECTED] escribió: Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). After the update, I starting having problems with my samba server and my gnome is no working anymore. After digging in the logs and found this error that seems to be the root cause: /libexec/ld-elf.so.1: Shared object libgnutls.so.13 not found, required by libcups.so.2 I started reading the blogs and mailing looking for a solution. So far what I tried was: - Update gnutils (based on http://wiki.archlinux.org/index.php/CUPS_Setup) - Uninstall and reinstall gnutils - Update ghostscript - Remove ghostscript-gnu and keep just gpl version (one of the blogs says that this is the latest one) - Uninstall cups - Reinstall cups - Reinstall samba - Re-run portmanager update Up to know, I was unable to kill this error and, in consequence, my samba server is not working. Does anybody could help me to fix this problem? I don't know what else to do. Thanks in advance Simon What version did you upgrade from? -Garrett Nothing special there that I can see, so I don't think that the problem is version related, but probably because portmaster doesn't go more than 1 leaf, as the other replying person said. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem updating Freebsd ver 6.2
On Fri, 11 May 2007 11:23:11 -0500 (CDT) Simon Castillo [EMAIL PROTECTED] wrote: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Assuming your ports tree is up to date, try running: pkgdb -Ffv See if that does anything unusual. -- Gerard She won' go Warp 7, Cap'n! The batteries are dead! signature.asc Description: PGP signature
Re: Problem updating Freebsd ver 6.2
Hi WizLayer: Nope, no particular reason to use portmanager. I guess I'll one more that suffer a bad experience. I don't see any other solution than re-install every thing again. Thanks Simon WizLayer [EMAIL PROTECTED] escribió: On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Gerard Seibert escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. Yes, update your ports tree and then run: portmanager -u -l -p You can substitute the 'f' flag for the 'p' one if you want to redo the system. Top posting is generally considered rude, just so you know... Any rate, your next option is to locate the missing library, figure out where your app thinks the library should be, and then ln to it so that your app sees the link... Any particular reason you're using portmanager (I haven't used it recently, but have had bad experiences with it in the past. I'm one of those who prefer portupgrade). Of course, I'm not saying this is a fault with portmanager. I honestly don't know. I was just wondering why you were using it (ie maybe it's been matured enough that I should check it out again). Don't know what else to tell you. WizLayer -- Life is better with a BSD. For more info, www.bsd.org. - ¿Quieres asombrarte? Conoce el nuevo Correo Yahoo! beta que incluye muchas herramientas que harán tu vida más sencilla. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem updating Freebsd ver 6.2
On Friday 11 May 2007 04:00:15 pm you wrote: WizLayer [EMAIL PROTECTED] escribió: On Friday 11 May 2007 11:23:11 am Simon Castillo wrote: Gerard Seibert escribió: On Fri, 11 May 2007 01:45:47 -0500 WizLayer wrote: I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. Yes, update your ports tree and then run: portmanager -u -l -p You can substitute the 'f' flag for the 'p' one if you want to redo the system. Hi Gerard: I tried your suggestion and I still have the same result. It updated couple more files, but the error (missing library) is still there. Any other suggestion? Thanks in advance Simon Top posting is generally considered rude, just so you know... Any rate, your next option is to locate the missing library, figure out where your app thinks the library should be, and then ln to it so that your app sees the link... Any particular reason you're using portmanager (I haven't used it recently, but have had bad experiences with it in the past. I'm one of those who prefer portupgrade). Of course, I'm not saying this is a fault with portmanager. I honestly don't know. I was just wondering why you were using it (ie maybe it's been matured enough that I should check it out again). Don't know what else to tell you. WizLayer Hi WizLayer: Nope, no particular reason to use portmanager. I guess I'll one more that suffer a bad experience. I don't see any other solution than re-install every thing again. Thanks Simon reinstalling everything isn't necessarily a bad thing. I do it on a regular basis on my experiment boxes... Or are you talking about the whole OS? That would be a bit extreme, I think. I'm using 6.2s right now and am not having any problems with it at all, and I cvsup and portupgrade fairly regular. Before depopulating pkgdb, try installing the portupgrade port, then cvsup, refetch the index file, and run your portupgrade -a. You can list the ports that need upgrading by using the 'portversion | grep | more' command. portupgrade will _only install those listed if you tell it to 'portupgrade -aRrv' If the problem still exists, and linking the file doesn't work, then mayhaps a reinstall of all the ports is necessary (I just don't see how unless you've specifically done something in your build options that put a ripple in the carpet). WizLayer -- Life is better with a BSD. For more info, www.bsd.org. pgpxQTxTVc3xX.pgp Description: PGP signature
Problem updating Freebsd ver 6.2
Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). After the update, I starting having problems with my samba server and my gnome is no working anymore. After digging in the logs and found this error that seems to be the root cause: /libexec/ld-elf.so.1: Shared object libgnutls.so.13 not found, required by libcups.so.2 I started reading the blogs and mailing looking for a solution. So far what I tried was: - Update gnutils (based on http://wiki.archlinux.org/index.php/CUPS_Setup) - Uninstall and reinstall gnutils - Update ghostscript - Remove ghostscript-gnu and keep just gpl version (one of the blogs says that this is the latest one) - Uninstall cups - Reinstall cups - Reinstall samba - Re-run portmanager update Up to know, I was unable to kill this error and, in consequence, my samba server is not working. Does anybody could help me to fix this problem? I don't know what else to do. Thanks in advance Simon - Do You Yahoo!? La mejor conexión a Internet y 2GB extra a tu correo por $100 al mes. http://net.yahoo.com.mx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem updating Freebsd ver 6.2
On Thursday 10 May 2007 11:24:31 pm Simon Castillo wrote: Hi all: I installed Freebsd ver 6.2 couple months ago in a Pentium III computer. I configured samba, gnome and couple other applications. Couple days ago I decided to update the ports. For this I use portmanager -u -l (after updating the port list). After the update, I starting having problems with my samba server and my gnome is no working anymore. After digging in the logs and found this error that seems to be the root cause: /libexec/ld-elf.so.1: Shared object libgnutls.so.13 not found, required by libcups.so.2 I started reading the blogs and mailing looking for a solution. So far what I tried was: - Update gnutils (based on http://wiki.archlinux.org/index.php/CUPS_Setup) - Uninstall and reinstall gnutils - Update ghostscript - Remove ghostscript-gnu and keep just gpl version (one of the blogs says that this is the latest one) - Uninstall cups - Reinstall cups - Reinstall samba - Re-run portmanager update Up to know, I was unable to kill this error and, in consequence, my samba server is not working. Does anybody could help me to fix this problem? I don't know what else to do. Thanks in advance Simon I could be wrong as I haven't used portmanager in a while (and that was only a short time)... I believe that by default, portmanager doesn't update dependencies more than a depth of 1 (maybe two?) unless you use the -p flag. Then it updates dependencies all the way back? A quick 'man portmanager' should verify this as I don't have it installed anymore. HTH, WizLayer -- Life is better with a BSD. For more info, www.bsd.org. pgplrcsJ7Grv5.pgp Description: PGP signature
