Re: ports problem in an old system ver 4.9
On May 26, 2011, at 3:01 PM, David Banning wrote: I have an old FreeBSD 4.9 installation that I cannot upgrade. You've also got a FreeBSD installation which the ports tree does not support. I wanted to install something from the ports, but I am getting this error on almost every port; # make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for rsnapshot-1.3.1 /sbin/sha256: not found *** Error code 127 Stop in /usr/ports/sysutils/rsnapshot. I believe you can obtain a sha256 binary from GNU coreutils (although GNU calls it sha256sum), and then install it to /sbin. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports problem in an old system ver 4.9
On Thu, 26 May 2011 15:40:09 -0700 Chuck Swiger cswi...@mac.com wrote: On May 26, 2011, at 3:01 PM, David Banning wrote: I have an old FreeBSD 4.9 installation that I cannot upgrade. You've also got a FreeBSD installation which the ports tree does not support. I wanted to install something from the ports, but I am getting this error on almost every port; # make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for rsnapshot-1.3.1 /sbin/sha256: not found *** Error code 127 Stop in /usr/ports/sysutils/rsnapshot. I believe you can obtain a sha256 binary from GNU coreutils (although GNU calls it sha256sum), and then install it to /sbin. It's not drop-in replacement. The FreeBSD version sensibly just outputs the hash when hashing from stdin, but the gnu version prints a trailing -. It may be that the ports makefiles ignore the extra field, but it may require a wrapper script. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ports problem
Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Of course time will probably prove it to be an utterly boneheaded thing to do, but it seems to work for now. # mv /usr/X11R6 /usr/X11R6-2 # ln -s /usr/X11R6-2 /usr/X11R6 # make install Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. Of course time will probably prove it to be an utterly boneheaded thing to do, but it seems to work for now. # mv /usr/X11R6 /usr/X11R6-2 # ln -s /usr/X11R6-2 /usr/X11R6 # make install You should put it back and run the mergebase script. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
RW wrote: On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. I didn't read it that way. You're right though. I'll check out mergebase.sh, see if it does anything I need. Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
Adam J Richardson wrote: RW wrote: On Fri, 09 Nov 2007 13:39:28 + Adam J Richardson [EMAIL PROTECTED] wrote: Desmond Chapman wrote: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Hi Desmond, When I was faced with this error I did the obvious thing and created a symlink, then restarted the install. Surely the *obvious* thing was to follow the instructions and read UPDATING. I didn't read it that way. You're right though. I'll check out mergebase.sh, see if it does anything I need. From what I can see, ports used to respect the settings of X11BASE and LOCALBASE, but even though they are still supposed to do that, well, I can see from my own attempts here on my box, that they don't do that. I found a bunch of stuff that either assumed /usr/local, or got the install path by reading the pkgconfig .pc files. LONG time back, I showed folks that it was a fairly trivial (two code lines) thing that was needed to make the X11 stuff go wherever you wanted it to go, but those two lines were in the 'imake' shell wrapper, and folks felt that the imake wrapper was holy writ for some reason, and would not let me make any changes to it. Pity. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem
On Sun, 4 Nov 2007 12:30:07 + Desmond Chapman [EMAIL PROTECTED] wrote: Hello. I am having multiple problems with the ports collection # cd /usr/ports/ports-mgmt/portupgrade # make install clean [ build log removed for brevity ] === Registering installation for portupgrade-2.3.1,2 === Cleaning for portupgrade-2.3.1,2 # portsdb -Uu portsdb: Command not found. From the Handbook section 4.5.2 Installing Ports: Note: Some shells keep a cache of the commands that are available in the directories listed in the PATH environment variable, to speed up lookup operations for the executable file of these commands. If you are using one of these shells, you might have to use the rehash command after installing a port, before the newly installed commands can be used. This command will work for shells like tcsh. Use the hash -r command for shells like sh. Look at the documentation for your shell for more information. If you are using root's default shell, then rehash is probably what you want. # cd kdenetwork3 # make [ Log detail omitted ] === qt-copy-3.3.8_6 depends on file: /usr/local/libdata/xorg/libraries - not found ===Verifying install for /usr/local/libdata/xorg/libraries in /usr/ports/x11/xorg-libraries The following is probably causing the multiple problems you are seeing: /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 [ More log detail omitted ] I have done the cvsup, csup, portsnap, and followed the instructions ion /usr/ports/UPDATING. I get thses same results each time. How do i fix this? Any help would be appreciated. It appears that you missed the /usr/ports/UPDATING (entry of 20070519) or forgot to run the script. There is a script (mergebase.sh) to run which creates the symlink for /usr/X11R6 (as well as other things). It might be a good idea to review that UPDATING entry and see if there are other things that might apply. HTH, Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem with openssl-0.9.x
On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris pgp1WU4ARd8Ol.pgp Description: PGP signature
Re: Ports problem with openssl-0.9.x
Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i === openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/openssl. *** Error code 1 Stop in /usr/ports/net-mgmt/net-snmp. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade52117.1 make ** Fix the problem and try again. --- Skipping 'misc/kdeutils3' (kdeutils-3.4.2) because a requisite package 'net-snmp-5.2.1.2' (net-mgmt/net-snmp) failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! net-mgmt/net-snmp (net-snmp-5.2.1.2) (unknown build error) * misc/kdeutils3 (kdeutils-3.4.2) So while kde... may not be looking for it, net-snmp is. Perhaps this should be a more general question on what to do if/when various ports get out of sync and are trying to use other inconsistent packages. Thanks - Don Hayford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problem with openssl-0.9.x
On Tue, Dec 06, 2005 at 10:03:09PM -0500, Donald T Hayford wrote: Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i I believe you, but update your ports. Kris pgp3esmZQhGUh.pgp Description: PGP signature
Re: Ports problem with openssl-0.9.x
Kris Kennaway wrote: On Tue, Dec 06, 2005 at 10:03:09PM -0500, Donald T Hayford wrote: Kris Kennaway wrote: On Tue, Dec 06, 2005 at 07:26:37PM -0500, Donald T Hayford wrote: When trying to upgrade my ports I get the following message: openssl-stable-0.9.7i conflicts with installed package(s): openssl-beta-0.9.8a Several ports (like openoffice.org-2xxx) require the beta version, while kde and its minions are looking for the 0.9.7i version. Is there any simple way to resolve this conflict? kde no longer looks for the old version because of other inconsistencies that resulted. Kris Here is the bottom of the output for my attempt to build kdeutils-3.4.2 using portupgrade. === Installing for openssl-stable-0.9.7i I believe you, but update your ports. Kris I did have a problem with my ports that I don't fully understand, but .. oh well. I updated ports today and yesterday hoping to get rid of the problem. Apparently when I installed the openoffice.org-2 package OOo_2.0m142_FreeBSD60Intel_install_en-US.tbz, I slipped in a dependency on the beta version of openssl instead of the stable version called for. Don't know how. I fixed the problem by deinstalling the openssl-beta version, installing the openssl-stable version, and then running pkgdb -F to fix the incorrect dependencies that I generated. Thanks much for your help. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problem/question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today Peter Vereshagin had this to say: On Tue, 12 Jul 2005 15:28:05 -0500 (CDT) Denny White [EMAIL PROTECTED] wrote: to install cdrdao which is currently version 1.1.9, I believe, then failed, with message saying there's a vulnerability. There's a fixed my question about the lagtime between fix and inclusion. Meantime, still using burncd. Danny, it uses to be easy to fix the port yourself --- just correct distinfo and version in Makefile to correspond the upgraded source tarball. You should send a message to the port maintainer and your best should be to supply him/her with the upgraded port as a .tbz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for the answer. I went ahead did a make -DDISABLE_VULNERABILITIES install clean in /usr/ports/sysutils/cdrdao. After that, k3b installed without any problem. I cvsup ports on a regular basis, also watch the cvs mailing list. Hopefully, before too long, the port maintainer will fix the problem with cdrdao. I ran into the same thing last month with ruby. Just didn't have much of a handle on how long fixes usually take to show up in the src or ports tree once they're done. Thanks again. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC1Mqwy0Ty5RZE55oRAr47AKCM1jc36PsDYN+W7rSy6xxvv8G91QCeK3Kq aQpziLyDfPrq3n0TCgec/Lo= =SxCC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problem/question
On Tue, 12 Jul 2005 15:28:05 -0500 (CDT) Denny White [EMAIL PROTECTED] wrote: to install cdrdao which is currently version 1.1.9, I believe, then failed, with message saying there's a vulnerability. There's a fixed my question about the lagtime between fix and inclusion. Meantime, still using burncd. Danny, it uses to be easy to fix the port yourself --- just correct distinfo and version in Makefile to correspond the upgraded source tarball. You should send a message to the port maintainer and your best should be to supply him/her with the upgraded port as a .tbz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
