Re: problem with installing new ports

2002-12-20 Thread Kliment Andreev
 please let me know if i MUST hold a connection to the
 internet during the installations.if so, is there a
 way to avoid that connection?

Download the tarball into /usr/ports/distfiles. 

Then do

# cd /usr/ports/audio/mpeg123
# make all install clean 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: problem with installing new ports

2002-12-20 Thread David S. Jackson
On Fri, Dec 20, 2002 at 09:23:01AM -0800 Ali Nasseh [EMAIL PROTECTED] wrote:
 hi,
 i run freebsd 4.5 stable and when i try to install a
 new port like mpg123 it fails.
 my command to system and it's response is here:
[...]

  mpg123-0.59r-pl1.tar.gz doesn't seem to exist in
 /usr/ports/distfiles/.

This is an important directory for ports!

mpg123-0.59r-pl1.tar.gz is the name of the tarball it cannot find.

  Attempting to fetch from
 http://www.mpg123.de/mpg123/.
  Attempting to fetch from
 http://www-ti.informatik.uni-tuebingen.de/~hippm/mpg123/.
  Attempting to fetch from
 ftp://ftp.tu-clausthal.de/pub/unix/audio/mpg123/.
  Attempting to fetch from
 http://ftp.tu-clausthal.de/pub/unix/audio/mpg123/.
  Attempting to fetch from
 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
  Couldn't fetch it - please try to retrieve this
  port manually into /usr/ports/distfiles/ and try
 again.
 *** Error code 1
 
 Stop in /usr/ports/audio/mpg123.
 *** Error code 1

[...]

 please let me know if i MUST hold a connection to the
 internet during the installations.if so, is there a
 way to avoid that connection?

Um, yes, you do need to be connected, unless you already have the
required tarballs in /usr/ports/distfiles.

 --thank you for any help

Your ports system was trying to remotely fetch a mpg123 tarball.  (There
are several tarballs here, actually, since there are patches to apply.)
It couldn't find one at the proper revision level (4.5-stable will be a
little behind the times, probably).  All you need to do is find the
proper version of mpg123 from an ftp site somewhere and copy it to
/usr/ports/distfiles.

step 1:  cat /usr/ports/audio/mpg123/distinfo. | sed 's/^.*(\(.*\)).*$/\1/g'
This should return about four filenames.

step 2:  google search for the exact tarball name uncovered from the
previous command.  It should be found at 
http://www.mpg123.de/cgi-bin/sitexplorer.cgi?/mpg123/

step 3:  copy said tarballs to /usr/ports/distfiles and try making the
port again.

Also, see the handbook (www.freebsd.org/handbook/) and read the chapter
about the ports system.

-- 
David S. Jackson[EMAIL PROTECTED]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The best way to make a fire with two sticks is to
make sure one of them is a match.  -- Will Rogers

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: problem with installing new ports

2002-12-20 Thread Shane Kinney
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 20 Dec 2002, David S. Jackson wrote:

 step 2:  google search for the exact tarball name uncovered from the
 previous command.  It should be found at
 http://www.mpg123.de/cgi-bin/sitexplorer.cgi?/mpg123/

 step 3:  copy said tarballs to /usr/ports/distfiles and try making the
 port again.

This method will work just fine, however:  Please be aware that
if you do not continue to update your ports tree, eventually the same
problem will happen to every port you attempt to install.  The problem
will also arise that when you go to the site to download the tarball
and you notice that there is a newer version that contains bug fixes,
security patches or general performance/enhancements.  If you get the
new version rather than the version that is specified in your Makefile,
you will have MD5 Checksum issues.

It is still in your and your computers best interst to update your ports
tree, keeping you safe from other nasty issues.  :)  Good luck.

~Shane
pgp key: http://www.freebsdhackers.net/pgp
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE+A2yQtGSLUf7ussURAs9VAJwJKzg43u8Lu5ob28ossHF636wQSwCfVqNm
nsOx/x2xqSCo8QpqZAuUiFc=
=qVRc
-END PGP SIGNATURE-

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: problem with installing new ports

2002-12-20 Thread Daniel Schrock




If there is an easier way to make pkgdb -F complete its job successfully
and not terminate with errors, I'm all ears by the way.  :-)



I'm not too sure on this one.  I don't really use any of the `pkg'
utilities ;)  Someone else might be able to help with that.



well... if your package db has gotten way out of sync with your ports 
collection, it creates a nightmare that only time and effort will fix.
You have a couple options, both equally suck, but have their merits as well.

option 1:  find the new dependancies or delete the dependancy if it no 
longer exists... once completed, use `portversion -l ''` to see which 
installed ports have newer versions available.  use portupgrade to get 
them current.  takes forever but usually works...just be careful when 
changing dependancies,

option 2:  remove as many old ports as possible, especically if they are 
not used/needed much and get your collection down to a small level, then 
move up to option 1.  This method is easier, but not necessarily an 
option on many systems. its nice for workstations and cleaning the 
system out, not so good if a production box that requires all ports that 
are installed...


once pkgdb -F can be run without errors, cvsup, use `portsdb -Uu` then 
check for old ports using `portversion -l ''`.

from this point on, you should have a clean system.  to keep it clean, 
either always run pkgdb -F after installing a port, or always use 
`portinstall -N` to install your ports, which will update pkgdb on its 
own...

portupgrade is pretty much an all or nothing port... if you use it 
religiously, its great... if you forget about it, its a hassle later on 
down the road.

its a great port but works best on fresh installs... its a little harder 
to deal with if you have already installed a lot of ports.


just my $.02

.daniel.schrock


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


Re: problem with installing new ports

2002-12-20 Thread David S. Jackson
On Fri, Dec 20, 2002 at 04:30:24PM -0600 Daniel Schrock [EMAIL PROTECTED] wrote:
 well... if your package db has gotten way out of sync with your ports 
 collection, it creates a nightmare that only time and effort will fix.
 You have a couple options, both equally suck, but have their merits as well.
 
 option 1:  find the new dependancies or delete the dependancy if it no 
 longer exists... once completed, use `portversion -l ''` to see which 
 installed ports have newer versions available.  use portupgrade to get 
 them current.  takes forever but usually works...just be careful when 
 changing dependancies,
 
 option 2:  remove as many old ports as possible, especically if they are 
 not used/needed much and get your collection down to a small level, then 
 move up to option 1.  This method is easier, but not necessarily an 
 option on many systems. its nice for workstations and cleaning the 
 system out, not so good if a production box that requires all ports that 
 are installed...
 
 once pkgdb -F can be run without errors, cvsup, use `portsdb -Uu` then 
 check for old ports using `portversion -l ''`.
 
 from this point on, you should have a clean system.  to keep it clean, 
 either always run pkgdb -F after installing a port, or always use 
 `portinstall -N` to install your ports, which will update pkgdb on its 
 own...
 
 portupgrade is pretty much an all or nothing port... if you use it 
 religiously, its great... if you forget about it, its a hassle later on 
 down the road.
 
 its a great port but works best on fresh installs... its a little harder 
 to deal with if you have already installed a lot of ports.

This has been one of the most helpful and practical pieces of advice I
have ever gotten from this terrific list.  Thank You!  I'll start
planning this operation.  (Option 2 first, then Option 1.)

(The portsdb is really still a mystery to me, and after letting it get
so far out of synch as it is, I hope that I too can have a clean system
again without reinstalling from scratch!)

The advice above seems so good that I didn't trim it; I hope someone
else can get as much help out of it as I have and therefore felt it's
worth leaving intact.  :-)

-- 
David S. Jackson[EMAIL PROTECTED]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Life is divided into the horrible and the miserable.
-- Woody Allen, Annie Hall

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message