Re: portupgrade stale dependencies

[Andrew P.]

On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
 On 10/30/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
   On 10/29/05, Andrew P. [EMAIL PROTECTED] wrote:
On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:

 Needless to say, this process wasn't much fun.  What can I do to keep
 this from happening again?  What can/can't I safely include in cron to
 automate database and index maintenance?

   
cvsup or portsnap, then portsdb -uUF. Work under
any circumstances, leave you with updated ports
tree and indexes.
  
   If I were to continue to use portsnap, which arguments can I safely
   add to /etc/crontab? I know portsnap cron should be safe, but if I
   want to completely automate the update process (not for installing
   packages, but for keeping the ports tree, database, and indexes
   current), should I also add an entry for portsnap update and
   portsdb -uUF?
  
   
You can also try portupgrade -aF (prefetches
needed files to speed up manual upgrade at a later
time) and portsclean -DP (removes sources and
packages which become outdated due to ports
tree updates).
   
  
   Would you also recommend cron entries for these two commands?
  
   I used to use a cron job to run cvsup, and I'd like to implement a
   better, more complete automated solution, so I don't tangle up my
   system's packages and dependencies again.
  
 
  I think the best way is to create a shell script, like this:
 
  #!/bin/sh
  /usr/local/sbin/portsnap cron  \
  /usr/local/sbin/portsnap update  \
  /usr/local/sbin/portsdb -uUF  \
  /usr/local/sbin/portupgrade -aF  \
  /usr/local/sbin/portsclean -DP
 

 Perfect... I had everything but the  conditionals... thanks!

 
  and run it at an hour, when you're most unlikely to
  perform any kind of port upgrading. As portsnap
  manpage warns, if both portsnap (in the process
  of update) and portupgrade ever happen to access
  the same directory at once, it might ruin your
  ports tree. You'll have to do portsnap extract
  after that. You can leave out portsclean and run
  it manually, because it can create some load
  (which is not desirable on a production server).
 
  I run this script daily at 8-9 in the morning (I usually
  start messing with servers after 11). It never failed,
  and it always keeps everything up-to-date.
 

 My server is not production, as it's just my personal web/database
 server; I'm the only one who would be running any updates.  So I
 should be okay with this procedure, and I'll manually update any ports
 of note.

 Just one problem I saw thus far, with portsclean I think...

 Cleaning out /usr/ports/packages...
 cd: can't cd to /usr/ports/packages/All
 find: /usr/ports/packages: No such file or directory

 Would this be related to one of the advanced topics you mentioned
 earlier about pkgtools.conf? ;)  Do I need to define some variables?
 I would guess the directory error to have been caused by a combination
 of the variables PORTSDIR (which looks okay at /usr/ports) and
 PACKAGES (which seems to need a /packages dir beneath PORTSDIR ?).

 Thanks,
 ~John


No, it's not advanced at all :-) You just don't have the
directory. Create it, if you want to. When you run
make package or portupgrade -p something, a
package is created in your current directory, unless
/usr/ports/packages exists. If it does, the package
is created there, and some hierarchy is kept, too.
So it's convenient to have that dir, if you ever use
packages.

Of course, /usr/ports/packages is just the default.
You can change PACKAGES to whatever you like.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
 On 10/31/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
   On 10/30/05, Andrew P. [EMAIL PROTECTED] wrote:
On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
 On 10/29/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:
  
   Needless to say, this process wasn't much fun.  What can I do to 
   keep
   this from happening again?  What can/can't I safely include in 
   cron to
   automate database and index maintenance?
  
 
  cvsup or portsnap, then portsdb -uUF. Work under
  any circumstances, leave you with updated ports
  tree and indexes.

 If I were to continue to use portsnap, which arguments can I safely
 add to /etc/crontab? I know portsnap cron should be safe, but if I
 want to completely automate the update process (not for installing
 packages, but for keeping the ports tree, database, and indexes
 current), should I also add an entry for portsnap update and
 portsdb -uUF?

 
  You can also try portupgrade -aF (prefetches
  needed files to speed up manual upgrade at a later
  time) and portsclean -DP (removes sources and
  packages which become outdated due to ports
  tree updates).
 

 Would you also recommend cron entries for these two commands?

 I used to use a cron job to run cvsup, and I'd like to implement a
 better, more complete automated solution, so I don't tangle up my
 system's packages and dependencies again.

   
I think the best way is to create a shell script, like this:
   
#!/bin/sh
/usr/local/sbin/portsnap cron  \
/usr/local/sbin/portsnap update  \
/usr/local/sbin/portsdb -uUF  \
/usr/local/sbin/portupgrade -aF  \
/usr/local/sbin/portsclean -DP
   
  
   Perfect... I had everything but the  conditionals... thanks!
  
   
and run it at an hour, when you're most unlikely to
perform any kind of port upgrading. As portsnap
manpage warns, if both portsnap (in the process
of update) and portupgrade ever happen to access
the same directory at once, it might ruin your
ports tree. You'll have to do portsnap extract
after that. You can leave out portsclean and run
it manually, because it can create some load
(which is not desirable on a production server).
   
I run this script daily at 8-9 in the morning (I usually
start messing with servers after 11). It never failed,
and it always keeps everything up-to-date.
   
  
   My server is not production, as it's just my personal web/database
   server; I'm the only one who would be running any updates.  So I
   should be okay with this procedure, and I'll manually update any ports
   of note.
  
   Just one problem I saw thus far, with portsclean I think...
  
   Cleaning out /usr/ports/packages...
   cd: can't cd to /usr/ports/packages/All
   find: /usr/ports/packages: No such file or directory
  
   Would this be related to one of the advanced topics you mentioned
   earlier about pkgtools.conf? ;)  Do I need to define some variables?
   I would guess the directory error to have been caused by a combination
   of the variables PORTSDIR (which looks okay at /usr/ports) and
   PACKAGES (which seems to need a /packages dir beneath PORTSDIR ?).
  
   Thanks,
   ~John
  
 
  No, it's not advanced at all :-) You just don't have the
  directory. Create it, if you want to. When you run
  make package or portupgrade -p something, a
  package is created in your current directory, unless
  /usr/ports/packages exists. If it does, the package
  is created there, and some hierarchy is kept, too.
  So it's convenient to have that dir, if you ever use
  packages.
 
  Of course, /usr/ports/packages is just the default.
  You can change PACKAGES to whatever you like.
 
 Thanks Andrew.  You're right: that's not advanced, even for me!  If
 that dir needs to have a specific set of permissions, please let me
 know; otherwise, I think I'm all set, aside from asking where I might
 read more about the ports/packages system that what's in the handbook
 and man pages.

 Thanks again for your help.
 ~John


The default (755) permissions should be ok.

The ultimate (more or less) ports/packages
documentation consists of:

ports(7)
make(1)
pkg_add(1)
pkg_create(1)
pkg_delete(1)
pkg_info(1)
pkg_version(1)

/usr/ports/Mk/*

The Porter's Handbook
The FreeBSD Handbook (Packages and Ports)

pib(1), portaudit(1), portcheckout(1), portlint(1)
portupgrade(1), etc - depending on what tools
you have installed.

ports@ mailing list archives and various makefiles
throughout the system are also valuable sources
of documentation.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL 

Re: portupgrade stale dependencies

[John DeStefano]

On 10/29/05, Andrew P. [EMAIL PROTECTED] wrote:
 On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:
 
  Needless to say, this process wasn't much fun.  What can I do to keep
  this from happening again?  What can/can't I safely include in cron to
  automate database and index maintenance?
 

 cvsup or portsnap, then portsdb -uUF. Work under
 any circumstances, leave you with updated ports
 tree and indexes.

If I were to continue to use portsnap, which arguments can I safely
add to /etc/crontab? I know portsnap cron should be safe, but if I
want to completely automate the update process (not for installing
packages, but for keeping the ports tree, database, and indexes
current), should I also add an entry for portsnap update and
portsdb -uUF?


 You can also try portupgrade -aF (prefetches
 needed files to speed up manual upgrade at a later
 time) and portsclean -DP (removes sources and
 packages which become outdated due to ports
 tree updates).


Would you also recommend cron entries for these two commands?

I used to use a cron job to run cvsup, and I'd like to implement a
better, more complete automated solution, so I don't tangle up my
system's packages and dependencies again.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
 On 10/29/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:
  
   Needless to say, this process wasn't much fun.  What can I do to keep
   this from happening again?  What can/can't I safely include in cron to
   automate database and index maintenance?
  
 
  cvsup or portsnap, then portsdb -uUF. Work under
  any circumstances, leave you with updated ports
  tree and indexes.

 If I were to continue to use portsnap, which arguments can I safely
 add to /etc/crontab? I know portsnap cron should be safe, but if I
 want to completely automate the update process (not for installing
 packages, but for keeping the ports tree, database, and indexes
 current), should I also add an entry for portsnap update and
 portsdb -uUF?

 
  You can also try portupgrade -aF (prefetches
  needed files to speed up manual upgrade at a later
  time) and portsclean -DP (removes sources and
  packages which become outdated due to ports
  tree updates).
 

 Would you also recommend cron entries for these two commands?

 I used to use a cron job to run cvsup, and I'd like to implement a
 better, more complete automated solution, so I don't tangle up my
 system's packages and dependencies again.


I think the best way is to create a shell script, like this:

#!/bin/sh
/usr/local/sbin/portsnap cron  \
/usr/local/sbin/portsnap update  \
/usr/local/sbin/portsdb -uUF  \
/usr/local/sbin/portupgrade -aF  \
/usr/local/sbin/portsclean -DP

and run it at an hour, when you're most unlikely to
perform any kind of port upgrading. As portsnap
manpage warns, if both portsnap (in the process
of update) and portupgrade ever happen to access
the same directory at once, it might ruin your
ports tree. You'll have to do portsnap extract
after that. You can leave out portsclean and run
it manually, because it can create some load
(which is not desirable on a production server).

I run this script daily at 8-9 in the morning (I usually
start messing with servers after 11). It never failed,
and it always keeps everything up-to-date.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/30/05, Andrew P. [EMAIL PROTECTED] wrote:
 On 10/31/05, John DeStefano [EMAIL PROTECTED] wrote:
  On 10/29/05, Andrew P. [EMAIL PROTECTED] wrote:
   On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:
   
Needless to say, this process wasn't much fun.  What can I do to keep
this from happening again?  What can/can't I safely include in cron to
automate database and index maintenance?
   
  
   cvsup or portsnap, then portsdb -uUF. Work under
   any circumstances, leave you with updated ports
   tree and indexes.
 
  If I were to continue to use portsnap, which arguments can I safely
  add to /etc/crontab? I know portsnap cron should be safe, but if I
  want to completely automate the update process (not for installing
  packages, but for keeping the ports tree, database, and indexes
  current), should I also add an entry for portsnap update and
  portsdb -uUF?
 
  
   You can also try portupgrade -aF (prefetches
   needed files to speed up manual upgrade at a later
   time) and portsclean -DP (removes sources and
   packages which become outdated due to ports
   tree updates).
  
 
  Would you also recommend cron entries for these two commands?
 
  I used to use a cron job to run cvsup, and I'd like to implement a
  better, more complete automated solution, so I don't tangle up my
  system's packages and dependencies again.
 

 I think the best way is to create a shell script, like this:

 #!/bin/sh
 /usr/local/sbin/portsnap cron  \
 /usr/local/sbin/portsnap update  \
 /usr/local/sbin/portsdb -uUF  \
 /usr/local/sbin/portupgrade -aF  \
 /usr/local/sbin/portsclean -DP


Perfect... I had everything but the  conditionals... thanks!


 and run it at an hour, when you're most unlikely to
 perform any kind of port upgrading. As portsnap
 manpage warns, if both portsnap (in the process
 of update) and portupgrade ever happen to access
 the same directory at once, it might ruin your
 ports tree. You'll have to do portsnap extract
 after that. You can leave out portsclean and run
 it manually, because it can create some load
 (which is not desirable on a production server).

 I run this script daily at 8-9 in the morning (I usually
 start messing with servers after 11). It never failed,
 and it always keeps everything up-to-date.


My server is not production, as it's just my personal web/database
server; I'm the only one who would be running any updates.  So I
should be okay with this procedure, and I'll manually update any ports
of note.

Just one problem I saw thus far, with portsclean I think...

Cleaning out /usr/ports/packages...
cd: can't cd to /usr/ports/packages/All
find: /usr/ports/packages: No such file or directory

Would this be related to one of the advanced topics you mentioned
earlier about pkgtools.conf? ;)  Do I need to define some variables? 
I would guess the directory error to have been caused by a combination
of the variables PORTSDIR (which looks okay at /usr/ports) and
PACKAGES (which seems to need a /packages dir beneath PORTSDIR ?).

Thanks,
~John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/29/05, John DeStefano [EMAIL PROTECTED] wrote:

 Needless to say, this process wasn't much fun.  What can I do to keep
 this from happening again?  What can/can't I safely include in cron to
 automate database and index maintenance?


cvsup or portsnap, then portsdb -uUF. Work under
any circumstances, leave you with updated ports
tree and indexes.

You can also try portupgrade -aF (prefetches
needed files to speed up manual upgrade at a later
time) and portsclean -DP (removes sources and
packages which become outdated due to ports
tree updates).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Eric F Crist]

On Oct 28, 2005, at 7:31 PM, John DeStefano wrote:

cd /usr/ports/www/apache20  make deinstall  make clean  make
reinstall

See what happens.




Talk about strange:

# cd /usr/ports/www/apache20/
# make deinstall
===  Deinstalling for www/apache20
===   apache not installed, skipping

# make -V PKGNAME
apache-2.0.55

# pkg_info | grep apache
apache-2.0.48   Version 2 of the extremely popular Apache http  
server


# apachectl -v
Server version: Apache/2.0.48
Server built:   Nov 19 2003 22:44:21






OK.  the try

#make install

what happens?
-
Eric F Crist
Secure Computing Networks
http://www.secure-computing.net



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Eric F Crist]

I ended up deinstalling that apache installation (which I was not keen
on doing), and installing the apache20 port (which was the same
version (2.0.55) as the apache2 port ?), and, thankfully, it's
working fine.  I'm also now able to run both 'pkgdb -F'and 'portsdb
-Uu' without ANY errors (except for a few 'Duplicate INDEX entry'
warnings).

Needless to say, this process wasn't much fun.  What can I do to keep
this from happening again?  What can/can't I safely include in cron to
automate database and index maintenance?

Thanks to all.


What I do for critical system ports is a manual upgrade.  I have  
never trusted any of the port management tools.  I suggest you pay  
attention to bugtracker and some other sites.  When you see a  
compelling reason to upgrade, do it manually.  The process I use is  
what I described in an earlier post:


#cd /usr/ports/port-to-upgrade  make deinstall
#make install

#restart whatever port I just upgraded

HTH

-
Eric F Crist
Secure Computing Networks
http://www.secure-computing.net



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
 On Thursday 27 October 2005 18:49, Eric F Crist wrote:
  On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
   On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
   On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
   After clearing out the ports, updating ports (with portsnap) and
   source, and rebuilding the system and kernel... it seemed the
   ultimate
   problem was actually a dependency of the package to apache1.3.
   After I
   ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
   but
   I still had trouble installing ports.
 
  At this point, what usually works for me is to:
 
  #cd /usr  rm -rf ./ports
 
  #mkdir ./ports  cvsup /root/ports-supfile
 
  The above will delete your ENTIRE ports tree, provided it's kept in /
  usr/ports and as long as you use cvsup (and your ports supfile is /
  root/ports-supfile as mine is).  When a whole bunch of ports stop
  working, I find this is the easiest thing to do.
 
  The other thing I do is run a cron job every week that updates, via
  cvsup, the ports tree.  About once a year I perform the above, mostly
  to clean out the crap.  Re-downloading your entire ports tree will be
  quicker if you don't use the ports-all tag and actually define which
  port segments you are interested in.  For example, there's no real
  reason to download all the x11/kde/gnome crap if you're doing this on
  a headless server that isn't going to serve X.
 
  HTH

 Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
 I may be a bit biased but I reaaly think John D. should try running
 portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
 issue for portmanager.

 -Mike

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]


I don't think that stale dependencies are an issue for
portupgrade as well, just add -O to the command-
line.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re[2]: portupgrade stale dependencies

[Gerard Seibert]

On Friday, October 28, 2005 3:25:14 AM, Andrew P. [EMAIL PROTECTED]
Subject: Re: portupgrade stale dependencies
Wrote these words of wisdom:

 On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
  On Thursday 27 October 2005 18:49, Eric F Crist wrote:
   On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
After clearing out the ports, updating ports (with portsnap) and
source, and rebuilding the system and kernel... it seemed the
ultimate
problem was actually a dependency of the package to apache1.3.
After I
ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
but
I still had trouble installing ports.
  
   At this point, what usually works for me is to:
  
   #cd /usr  rm -rf ./ports
  
   #mkdir ./ports  cvsup /root/ports-supfile
  
   The above will delete your ENTIRE ports tree, provided it's kept in /
   usr/ports and as long as you use cvsup (and your ports supfile is /
   root/ports-supfile as mine is).  When a whole bunch of ports stop
   working, I find this is the easiest thing to do.
  
   The other thing I do is run a cron job every week that updates, via
   cvsup, the ports tree.  About once a year I perform the above, mostly
   to clean out the crap.  Re-downloading your entire ports tree will be
   quicker if you don't use the ports-all tag and actually define which
   port segments you are interested in.  For example, there's no real
   reason to download all the x11/kde/gnome crap if you're doing this on
   a headless server that isn't going to serve X.
  
   HTH
 
  Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
  I may be a bit biased but I reaaly think John D. should try running
  portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
  issue for portmanager.
 
  -Mike
 
 I don't think that stale dependencies are an issue for
 portupgrade as well, just add -O to the command-
 line.

* REPLY SEPARATOR *
On 10/11/2005 5:29:42 PM, Gerard Replied:

Personally, I feel that portmanager does a much better job of updating
without the problems that seem to crop up so often using portupgrade.

Just my 2¢.

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Re[2]: portupgrade stale dependencies

[Andrew P.]

On 10/28/05, Gerard Seibert [EMAIL PROTECTED] wrote:

 Personally, I feel that portmanager does a much better job of updating
 without the problems that seem to crop up so often using portupgrade.


I've always been scared off by the comparatively
young age of portmanager. Besides, portupgrade
comes with a set of useful tools, like cvsweb
browser.

But the fat ruby dependency and some other things
make me want something else. I'd be glad to see
a perl-based ports management system. Maybe
I'll write one some day :-)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Friday 28 October 2005 00:25, Andrew P. wrote:
 On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
  On Thursday 27 October 2005 18:49, Eric F Crist wrote:
   On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
After clearing out the ports, updating ports (with portsnap) and
source, and rebuilding the system and kernel... it seemed the
ultimate
problem was actually a dependency of the package to apache1.3.
After I
ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
but
I still had trouble installing ports.
  
   At this point, what usually works for me is to:
  
   #cd /usr  rm -rf ./ports
  
   #mkdir ./ports  cvsup /root/ports-supfile
  
   The above will delete your ENTIRE ports tree, provided it's kept in /
   usr/ports and as long as you use cvsup (and your ports supfile is /
   root/ports-supfile as mine is).  When a whole bunch of ports stop
   working, I find this is the easiest thing to do.
  
   The other thing I do is run a cron job every week that updates, via
   cvsup, the ports tree.  About once a year I perform the above, mostly
   to clean out the crap.  Re-downloading your entire ports tree will be
   quicker if you don't use the ports-all tag and actually define which
   port segments you are interested in.  For example, there's no real
   reason to download all the x11/kde/gnome crap if you're doing this on
   a headless server that isn't going to serve X.
  
   HTH
 
  Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
  I may be a bit biased but I reaaly think John D. should try running
  portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
  issue for portmanager.
 
  -Mike
 

 I don't think that stale dependencies are an issue for
 portupgrade as well, just add -O to the command-
 line.


From portupgrade's man page:

   -O
 --omit-check   Omit sanity checks for dependencies.  By default,
portupgrade checks if all the packages to upgrade
have consistent dependencies, though it takes
extra time to calculate dependencies.  If you are
sure you have run ``pkgdb -F'' in advance, you can
specify this option to omit the sanity checks.

Seems to be a caveat to the -O command.  What happens if pkgdb -F
isn't run first?

-Mike

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Friday 28 October 2005 05:53, John DeStefano wrote:
 On 10/27/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
  On Thursday 27 October 2005 18:49, Eric F Crist wrote:
   On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
After clearing out the ports, updating ports (with portsnap) and
source, and rebuilding the system and kernel... it seemed the
ultimate
problem was actually a dependency of the package to apache1.3.
After I
ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
but
I still had trouble installing ports.
  
   At this point, what usually works for me is to:
  
   #cd /usr  rm -rf ./ports
  
   #mkdir ./ports  cvsup /root/ports-supfile
  
   The above will delete your ENTIRE ports tree, provided it's kept in /
   usr/ports and as long as you use cvsup (and your ports supfile is /
   root/ports-supfile as mine is).  When a whole bunch of ports stop
   working, I find this is the easiest thing to do.
  
   The other thing I do is run a cron job every week that updates, via
   cvsup, the ports tree.  About once a year I perform the above, mostly
   to clean out the crap.  Re-downloading your entire ports tree will be
   quicker if you don't use the ports-all tag and actually define which
   port segments you are interested in.  For example, there's no real
   reason to download all the x11/kde/gnome crap if you're doing this on
   a headless server that isn't going to serve X.
  
   HTH
 
  Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
  I may be a bit biased but I reaaly think John D. should try running
  portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
  issue for portmanager.
 
  -Mike

 Biased indeed. ;)  I tried it, and it did work for some ports, but not
 all.  Here's the report output of a second run-through:

 status report finished
 
 percentDone-=16 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=10 /
 TOTAL_outOfDatePortsDb-=12 ) )
 checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
 acroread-5.08 that needs to be updated first
 upgrade 0.3.0_0 info: ignoring scrollkeeper-0.3.12_1,1, reason: failed
 during (2) make
 upgrade 0.3.0_0 info: ignoring cups-pstoraster-7.07, reason: failed
 during (2) make
 checkForOldDepencies 0.3.0_0 skip: eog2-2.2.1 has a dependency
 scrollkeeper-0.3.12_1,1 that needs to be updated first
 checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
 acroread-5.08 that needs to be updated first
 upgrade 0.3.0_0 info: ignoring emacs-21.3, reason: failed during (2) make
 upgrade 0.3.0_0 info: ignoring gconf-editor-2.4.0,1, reason: performed
 (6) emergancy restore
 upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2)
 make checkForOldDepencies 0.3.0_0 skip: gnomeuserdocs2-2.0.6_1 has a
 dependency scrollkeeper-0.3.12_1,1 that needs to be updated first
 upgrade 0.3.0_0 info: ignoring acroread-5.08, reason: marked FORBIDDEN
 
 update of ports collection complete with either some errors, ignored
 ports or both

A few suggestions:

If you want to update acroread-5.08 you should do that one manually
because it is FORBIDDEN, there is probably an overide switch, I don't
know what it is.  You can also just comment out the FORBIDDEN line in
acroread-5.08's Makefile.  Note ports are marked FORBIDDEN  because
they have security problems

I'm not sure about cups-pstoraster-7.07 builds but  scrollkeeper-0.3.14_1,1 
builds on my system, try pkg_delete -f scrollkeeper-0.3.12_1,1 then
rerun portmanager -u and hopefully you will be down to just 
cups-pstoraster-7.07 failing. You'll have to figure out its problem on your 
own or contact the maintainer for help.

-Mike


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/27/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
 On Thursday 27 October 2005 18:49, Eric F Crist wrote:
  On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
   On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
   On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
   After clearing out the ports, updating ports (with portsnap) and
   source, and rebuilding the system and kernel... it seemed the
   ultimate
   problem was actually a dependency of the package to apache1.3.
   After I
   ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
   but
   I still had trouble installing ports.
 
  At this point, what usually works for me is to:
 
  #cd /usr  rm -rf ./ports
 
  #mkdir ./ports  cvsup /root/ports-supfile
 
  The above will delete your ENTIRE ports tree, provided it's kept in /
  usr/ports and as long as you use cvsup (and your ports supfile is /
  root/ports-supfile as mine is).  When a whole bunch of ports stop
  working, I find this is the easiest thing to do.
 
  The other thing I do is run a cron job every week that updates, via
  cvsup, the ports tree.  About once a year I perform the above, mostly
  to clean out the crap.  Re-downloading your entire ports tree will be
  quicker if you don't use the ports-all tag and actually define which
  port segments you are interested in.  For example, there's no real
  reason to download all the x11/kde/gnome crap if you're doing this on
  a headless server that isn't going to serve X.
 
  HTH

 Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
 I may be a bit biased but I reaaly think John D. should try running
 portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
 issue for portmanager.

 -Mike

Biased indeed. ;)  I tried it, and it did work for some ports, but not
all.  Here's the report output of a second run-through:

status report finished

percentDone-=16 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=10 /
TOTAL_outOfDatePortsDb-=12 ) )
checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
acroread-5.08 that needs to be updated first
upgrade 0.3.0_0 info: ignoring scrollkeeper-0.3.12_1,1, reason: failed
during (2) make
upgrade 0.3.0_0 info: ignoring cups-pstoraster-7.07, reason: failed
during (2) make
checkForOldDepencies 0.3.0_0 skip: eog2-2.2.1 has a dependency
scrollkeeper-0.3.12_1,1 that needs to be updated first
checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
acroread-5.08 that needs to be updated first
upgrade 0.3.0_0 info: ignoring emacs-21.3, reason: failed during (2) make
upgrade 0.3.0_0 info: ignoring gconf-editor-2.4.0,1, reason: performed
(6) emergancy restore
upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2) make
checkForOldDepencies 0.3.0_0 skip: gnomeuserdocs2-2.0.6_1 has a
dependency scrollkeeper-0.3.12_1,1 that needs to be updated first
upgrade 0.3.0_0 info: ignoring acroread-5.08, reason: marked FORBIDDEN

update of ports collection complete with either some errors, ignored
ports or both
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
 On Friday 28 October 2005 05:53, John DeStefano wrote:
  On 10/27/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
   On Thursday 27 October 2005 18:49, Eric F Crist wrote:
On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
 On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
 On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
 After clearing out the ports, updating ports (with portsnap) and
 source, and rebuilding the system and kernel... it seemed the
 ultimate
 problem was actually a dependency of the package to apache1.3.
 After I
 ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
 but
 I still had trouble installing ports.
   
At this point, what usually works for me is to:
   
#cd /usr  rm -rf ./ports
   
#mkdir ./ports  cvsup /root/ports-supfile
   
The above will delete your ENTIRE ports tree, provided it's kept in /
usr/ports and as long as you use cvsup (and your ports supfile is /
root/ports-supfile as mine is).  When a whole bunch of ports stop
working, I find this is the easiest thing to do.
   
The other thing I do is run a cron job every week that updates, via
cvsup, the ports tree.  About once a year I perform the above, mostly
to clean out the crap.  Re-downloading your entire ports tree will be
quicker if you don't use the ports-all tag and actually define which
port segments you are interested in.  For example, there's no real
reason to download all the x11/kde/gnome crap if you're doing this on
a headless server that isn't going to serve X.
   
HTH
  
   Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
   I may be a bit biased but I reaaly think John D. should try running
   portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non
   issue for portmanager.
  
   -Mike
 
  Biased indeed. ;)  I tried it, and it did work for some ports, but not
  all.  Here's the report output of a second run-through:
 
  status report finished
  
  percentDone-=16 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=10 /
  TOTAL_outOfDatePortsDb-=12 ) )
  checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
  acroread-5.08 that needs to be updated first
  upgrade 0.3.0_0 info: ignoring scrollkeeper-0.3.12_1,1, reason: failed
  during (2) make
  upgrade 0.3.0_0 info: ignoring cups-pstoraster-7.07, reason: failed
  during (2) make
  checkForOldDepencies 0.3.0_0 skip: eog2-2.2.1 has a dependency
  scrollkeeper-0.3.12_1,1 that needs to be updated first
  checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
  acroread-5.08 that needs to be updated first
  upgrade 0.3.0_0 info: ignoring emacs-21.3, reason: failed during (2) make
  upgrade 0.3.0_0 info: ignoring gconf-editor-2.4.0,1, reason: performed
  (6) emergancy restore
  upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2)
  make checkForOldDepencies 0.3.0_0 skip: gnomeuserdocs2-2.0.6_1 has a
  dependency scrollkeeper-0.3.12_1,1 that needs to be updated first
  upgrade 0.3.0_0 info: ignoring acroread-5.08, reason: marked FORBIDDEN
  
  update of ports collection complete with either some errors, ignored
  ports or both

 A few suggestions:

 If you want to update acroread-5.08 you should do that one manually
 because it is FORBIDDEN, there is probably an overide switch, I don't
 know what it is.  You can also just comment out the FORBIDDEN line in
 acroread-5.08's Makefile.  Note ports are marked FORBIDDEN  because
 they have security problems

 I'm not sure about cups-pstoraster-7.07 builds but  scrollkeeper-0.3.14_1,1
 builds on my system, try pkg_delete -f scrollkeeper-0.3.12_1,1 then
 rerun portmanager -u and hopefully you will be down to just
 cups-pstoraster-7.07 failing. You'll have to figure out its problem on your
 own or contact the maintainer for help.

 -Mike

After tons of manual deinstalling, upgrading, tinkering, etc. (I
wanted to script everything I did, but at this point the audit trail
would have been about a GB in size), I am down to a single outdated
port:

status report finished

percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
TOTAL_outOfDatePortsDb-=1 ) )
upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2) make

update of ports collection complete with either some errors, ignored
ports or both


Unfortunately, this is the most crucial of all, and ironically the one
about which I've been asking since the beginning.  As I mentioned
earlier, upgrading this port bails consistently with a C callout to
PEM_F_DEF_CALLBACK.  I'd really like to get this port updated, not
only to 

Re: portupgrade stale dependencies

[Eric F Crist]

status report finished
== 
==

percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
TOTAL_outOfDatePortsDb-=1 ) )
upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during  
(2) make
-- 
--

update of ports collection complete with either some errors, ignored
ports or both


Unfortunately, this is the most crucial of all, and ironically the one
about which I've been asking since the beginning.  As I mentioned
earlier, upgrading this port bails consistently with a C callout to
PEM_F_DEF_CALLBACK.  I'd really like to get this port updated, not
only to finally complete this insane goose chase of updating, but
because I know that apache-2.0.48 is chock full of vulerabilities.






cd /usr/ports/www/apache20  make deinstall  make clean  make  
reinstall


See what happens.


-
Eric F Crist
Secure Computing Networks
http://www.secure-computing.net



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Fwd: Re: portupgrade stale dependencies

[Michael C. Shultz]

--  Forwarded Message  --

Subject: Re: portupgrade stale dependencies
Date: Friday 28 October 2005 15:02
From: Michael C. Shultz [EMAIL PROTECTED]
To: John DeStefano [EMAIL PROTECTED]

On Friday 28 October 2005 13:29, John DeStefano wrote:
 On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
  On Friday 28 October 2005 05:53, John DeStefano wrote:
   On 10/27/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
On Thursday 27 October 2005 18:49, Eric F Crist wrote:
 On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
  On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
  After clearing out the ports, updating ports (with portsnap)
  and source, and rebuilding the system and kernel... it seemed
  the ultimate
  problem was actually a dependency of the package to apache1.3.
  After I
  ran 'pkgdb -F' and fixed this dependency to point to
  apache2.1, but
  I still had trouble installing ports.

 At this point, what usually works for me is to:

 #cd /usr  rm -rf ./ports

 #mkdir ./ports  cvsup /root/ports-supfile

 The above will delete your ENTIRE ports tree, provided it's kept in
 / usr/ports and as long as you use cvsup (and your ports supfile is
 / root/ports-supfile as mine is).  When a whole bunch of ports stop
 working, I find this is the easiest thing to do.

 The other thing I do is run a cron job every week that updates, via
 cvsup, the ports tree.  About once a year I perform the above,
 mostly to clean out the crap.  Re-downloading your entire ports
 tree will be quicker if you don't use the ports-all tag and
 actually define which port segments you are interested in.  For
 example, there's no real reason to download all the x11/kde/gnome
 crap if you're doing this on a headless server that isn't going to
 serve X.

 HTH
   
Replacing /usr/ports won't fix his problems, they reside in
/var/db/pkg. I may be a bit biased but I reaaly think John D. should
try running portmanager -u (ports/sysutils/portmanager).  Stale
dependencies is a non issue for portmanager.
   
-Mike
  
   Biased indeed. ;)  I tried it, and it did work for some ports, but not
   all.  Here's the report output of a second run-through:
  
   status report finished
   ===
  = percentDone-=16 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=10 /
   TOTAL_outOfDatePortsDb-=12 ) )
   checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
   acroread-5.08 that needs to be updated first
   upgrade 0.3.0_0 info: ignoring scrollkeeper-0.3.12_1,1, reason: failed
   during (2) make
   upgrade 0.3.0_0 info: ignoring cups-pstoraster-7.07, reason: failed
   during (2) make
   checkForOldDepencies 0.3.0_0 skip: eog2-2.2.1 has a dependency
   scrollkeeper-0.3.12_1,1 that needs to be updated first
   checkForOldDepencies 0.3.0_0 skip: apsfilter-7.2.6 has a dependency
   acroread-5.08 that needs to be updated first
   upgrade 0.3.0_0 info: ignoring emacs-21.3, reason: failed during (2)
   make upgrade 0.3.0_0 info: ignoring gconf-editor-2.4.0,1, reason:
   performed (6) emergancy restore
   upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2)
   make checkForOldDepencies 0.3.0_0 skip: gnomeuserdocs2-2.0.6_1 has a
   dependency scrollkeeper-0.3.12_1,1 that needs to be updated first
   upgrade 0.3.0_0 info: ignoring acroread-5.08, reason: marked FORBIDDEN
   ---
  - update of ports collection complete with either some errors, ignored
   ports or both
 
  A few suggestions:
 
  If you want to update acroread-5.08 you should do that one manually
  because it is FORBIDDEN, there is probably an overide switch, I don't
  know what it is.  You can also just comment out the FORBIDDEN line in
  acroread-5.08's Makefile.  Note ports are marked FORBIDDEN  because
  they have security problems
 
  I'm not sure about cups-pstoraster-7.07 builds but
  scrollkeeper-0.3.14_1,1 builds on my system, try pkg_delete -f
  scrollkeeper-0.3.12_1,1 then rerun portmanager -u and hopefully you will
  be down to just
  cups-pstoraster-7.07 failing. You'll have to figure out its problem on
  your own or contact the maintainer for help.
 
  -Mike

 After tons of manual deinstalling, upgrading, tinkering, etc. (I
 wanted to script everything I did, but at this point the audit trail
 would have been about a GB in size), I am down to a single outdated
 port:

 status report finished
 
 percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
 TOTAL_outOfDatePortsDb-=1 ) )
 upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during (2)
 make

Re: portupgrade stale dependencies

[John DeStefano]

On 10/28/05, Eric F Crist [EMAIL PROTECTED] wrote:
  status report finished
  ==
  ==
  percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
  TOTAL_outOfDatePortsDb-=1 ) )
  upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during
  (2) make
  --
  --
  update of ports collection complete with either some errors, ignored
  ports or both
 
 
  Unfortunately, this is the most crucial of all, and ironically the one
  about which I've been asking since the beginning.  As I mentioned
  earlier, upgrading this port bails consistently with a C callout to
  PEM_F_DEF_CALLBACK.  I'd really like to get this port updated, not
  only to finally complete this insane goose chase of updating, but
  because I know that apache-2.0.48 is chock full of vulerabilities.
 
 
 


 cd /usr/ports/www/apache20  make deinstall  make clean  make
 reinstall

 See what happens.


Talk about strange:

# cd /usr/ports/www/apache20/
# make deinstall
===  Deinstalling for www/apache20
===   apache not installed, skipping

# make -V PKGNAME
apache-2.0.55

# pkg_info | grep apache
apache-2.0.48   Version 2 of the extremely popular Apache http server

# apachectl -v
Server version: Apache/2.0.48
Server built:   Nov 19 2003 22:44:21
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Friday 28 October 2005 17:31, John DeStefano wrote:
 On 10/28/05, Eric F Crist [EMAIL PROTECTED] wrote:
   status report finished
   ==
   ==
   percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
   TOTAL_outOfDatePortsDb-=1 ) )
   upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during
   (2) make
   --
   --
   update of ports collection complete with either some errors, ignored
   ports or both
  
  
   Unfortunately, this is the most crucial of all, and ironically the one
   about which I've been asking since the beginning.  As I mentioned
   earlier, upgrading this port bails consistently with a C callout to
   PEM_F_DEF_CALLBACK.  I'd really like to get this port updated, not
   only to finally complete this insane goose chase of updating, but
   because I know that apache-2.0.48 is chock full of vulerabilities.
 
  cd /usr/ports/www/apache20  make deinstall  make clean  make
  reinstall
 
  See what happens.

 Talk about strange:

 # cd /usr/ports/www/apache20/
 # make deinstall
 ===  Deinstalling for www/apache20
 ===   apache not installed, skipping

 # make -V PKGNAME
 apache-2.0.55

 # pkg_info | grep apache
 apache-2.0.48   Version 2 of the extremely popular Apache http server

 # apachectl -v
 Server version: Apache/2.0.48
 Server built:   Nov 19 2003 22:44:21
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]

Try
ls /var/db/pkg/a*
any apache versions in there?

-Mike



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Friday 28 October 2005 19:51, John DeStefano wrote:
 On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
  On Friday 28 October 2005 17:31, John DeStefano wrote:
   On 10/28/05, Eric F Crist [EMAIL PROTECTED] wrote:
 status report finished
 ===
=== ==
 percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
 TOTAL_outOfDatePortsDb-=1 ) )
 upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during
 (2) make
 ---
--- --
 update of ports collection complete with either some errors,
 ignored ports or both


 Unfortunately, this is the most crucial of all, and ironically the
 one about which I've been asking since the beginning.  As I
 mentioned earlier, upgrading this port bails consistently with a C
 callout to PEM_F_DEF_CALLBACK.  I'd really like to get this port
 updated, not only to finally complete this insane goose chase of
 updating, but because I know that apache-2.0.48 is chock full of
 vulerabilities.
   
cd /usr/ports/www/apache20  make deinstall  make clean  make
reinstall
   
See what happens.
  
   Talk about strange:
  
   # cd /usr/ports/www/apache20/
   # make deinstall
   ===  Deinstalling for www/apache20
   ===   apache not installed, skipping
  
   # make -V PKGNAME
   apache-2.0.55
  
   # pkg_info | grep apache
   apache-2.0.48   Version 2 of the extremely popular Apache http
   server
  
   # apachectl -v
   Server version: Apache/2.0.48
   Server built:   Nov 19 2003 22:44:21
   ___
   freebsd-questions@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to
   [EMAIL PROTECTED]
 
  Try
  ls /var/db/pkg/a*
  any apache versions in there?
 
  -Mike

 Yep: it was 2.0.48

 I ended up deinstalling that apache installation (which I was not keen
 on doing), and installing the apache20 port (which was the same
 version (2.0.55) as the apache2 port ?), and, thankfully, it's
 working fine.  I'm also now able to run both 'pkgdb -F'and 'portsdb
 -Uu' without ANY errors (except for a few 'Duplicate INDEX entry'
 warnings).

 Needless to say, this process wasn't much fun.  What can I do to keep
 this from happening again?  What can/can't I safely include in cron to
 automate database and index maintenance?

 Thanks to all.

Pardon my bias agan ;) but I'd recommend only updating with portmanager.
From cron I'd just run a cvsupdate and portmanager -s  /root/portmanager.log.
Review the log from time toi time and when you see something that should be 
updated run portmanager -u manually.  Some ports do not do well being built 
from cron so will save you much trouble to do the updates manually.  As far 
as the INDEX goes, portmanager doesn't require it, but other utilies do so 
maybe add a make fetch index to cron as well.

Congradulations on getting everything fixed BTW.

-Mike



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/28/05, Michael C. Shultz [EMAIL PROTECTED] wrote:
 On Friday 28 October 2005 17:31, John DeStefano wrote:
  On 10/28/05, Eric F Crist [EMAIL PROTECTED] wrote:
status report finished
==
==
percentDone-=0 = 100 - ( 100 * ( QTY_outOfDatePortsDb-=1 /
TOTAL_outOfDatePortsDb-=1 ) )
upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed during
(2) make
--
--
update of ports collection complete with either some errors, ignored
ports or both
   
   
Unfortunately, this is the most crucial of all, and ironically the one
about which I've been asking since the beginning.  As I mentioned
earlier, upgrading this port bails consistently with a C callout to
PEM_F_DEF_CALLBACK.  I'd really like to get this port updated, not
only to finally complete this insane goose chase of updating, but
because I know that apache-2.0.48 is chock full of vulerabilities.
  
   cd /usr/ports/www/apache20  make deinstall  make clean  make
   reinstall
  
   See what happens.
 
  Talk about strange:
 
  # cd /usr/ports/www/apache20/
  # make deinstall
  ===  Deinstalling for www/apache20
  ===   apache not installed, skipping
 
  # make -V PKGNAME
  apache-2.0.55
 
  # pkg_info | grep apache
  apache-2.0.48   Version 2 of the extremely popular Apache http server
 
  # apachectl -v
  Server version: Apache/2.0.48
  Server built:   Nov 19 2003 22:44:21
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to
  [EMAIL PROTECTED]

 Try
 ls /var/db/pkg/a*
 any apache versions in there?

 -Mike

Yep: it was 2.0.48

I ended up deinstalling that apache installation (which I was not keen
on doing), and installing the apache20 port (which was the same
version (2.0.55) as the apache2 port ?), and, thankfully, it's
working fine.  I'm also now able to run both 'pkgdb -F'and 'portsdb
-Uu' without ANY errors (except for a few 'Duplicate INDEX entry'
warnings).

Needless to say, this process wasn't much fun.  What can I do to keep
this from happening again?  What can/can't I safely include in cron to
automate database and index maintenance?

Thanks to all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:

...snip...


 After clearing out the ports, updating ports (with portsnap) and
 source, and rebuilding the system and kernel... it seemed the ultimate
 problem was actually a dependency of the package to apache1.3. After I
 ran 'pkgdb -F' and fixed this dependency to point to apache2.1, but
 I still had trouble installing ports.

 'portsdb -Uu' would not run, so I ran 'make fetchindex' and
 'portupdate -a'.  From what I've read, this _should_ create an index
 and update all out-of-date ports and their dependencies, but it never
 has worked for me.  I just tried this combination again, and it
 (again) punts during portupdate.  This time, 38 ports were skipped and
 7 failed, the first failure being a strange compiler error in updating
 from apache-2.0.48.

 I've been fighting with ports for long enough now to have become a bit
 frustrated with them.  If you have any thoughts or suggestions on how
 to troubleshoot them, please pass them on.

 Thanks,
 ~John


Do not fix dependencies if you're not sure that they
are really broken. Don't use apache21 unless 2.0
is absolutely inappropriate. The proper way to change
dependencies from apache1 to apache2 is to add
WITH_APACHE2=true to /etc/make.conf (or to
/usr/local/etc/pkgtools.conf, but that's an advanced
topic).

If you have portsdb utility, don't use make fetchindex,
just add -F to portsdb: portsdb -uUF will work fine.

You cann add -k to portupgrade, so that it doesn't
skip ports (but it won't fix the failed ones).

John, you'll have to spend a few hours reading
ports documentation before you find them really
great (which they really are).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
 On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
 
  After clearing out the ports, updating ports (with portsnap) and
  source, and rebuilding the system and kernel... it seemed the ultimate
  problem was actually a dependency of the package to apache1.3. After I
  ran 'pkgdb -F' and fixed this dependency to point to apache2.1, but
  I still had trouble installing ports.
 
  'portsdb -Uu' would not run, so I ran 'make fetchindex' and
  'portupdate -a'.  From what I've read, this _should_ create an index
  and update all out-of-date ports and their dependencies, but it never
  has worked for me.  I just tried this combination again, and it
  (again) punts during portupdate.  This time, 38 ports were skipped and
  7 failed, the first failure being a strange compiler error in updating
  from apache-2.0.48.
 
  I've been fighting with ports for long enough now to have become a bit
  frustrated with them.  If you have any thoughts or suggestions on how
  to troubleshoot them, please pass them on.
 
  Thanks,
  ~John
 

 Do not fix dependencies if you're not sure that they
 are really broken. Don't use apache21 unless 2.0
 is absolutely inappropriate. The proper way to change
 dependencies from apache1 to apache2 is to add
 WITH_APACHE2=true to /etc/make.conf (or to
 /usr/local/etc/pkgtools.conf, but that's an advanced
 topic).

I wasn't really looking to upgrade to apache21, just to update my
version (2.0.48) to any more current port, since other ports keep
barking about it being out-of-date.

I added the WITH_APACHE2=true parameter, but when I try to upgrade
my apache port, it seems to still be looking to the wrong version:
...Upgrading 'apache-2.0.48' to 'apache-2.1.4' (www/apache21)

This process attempts to build and then consistently fails with the
same error, which seems to my untrained eye like a C function error in
httpd:

ssl_engine_pphrase.c: In function `ssl_pphrase_Handle_CB':
ssl_engine_pphrase.c:684: error: `PEM_F_DEF_CALLBACK' undeclared
(first use in this function)
ssl_engine_pphrase.c:684: error: (Each undeclared identifier is
reported only once
ssl_engine_pphrase.c:684: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha.
*** Error code 1

Stop in /usr/ports/www/apache21.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade38050.3 make
** Fix the problem and try again.


Apparently, this is an OpenSSL-related bug, and there's a patch
availavble for it somewhere ?  Is there a way to fix this without
applying a patch?

 If you have portsdb utility, don't use make fetchindex,
 just add -F to portsdb: portsdb -uUF will work fine.

portsdb -uU wasn't working for me for a while, but I finally got it
going last night. Kris maintained that I should use make fetchindex
instead of portsdb -uU before running portupgrade -a, at least
until my package installation dependencies were in better condition,
at which time I could resume using portsdb -uU.  Problem is,
portupgrade -a still isn't working to update all installed packages
(most, but not all), regardless of whether it is preceded by portsdb
-uU or portupgrade -a.

 You cann add -k to portupgrade, so that it doesn't
 skip ports (but it won't fix the failed ones).

 John, you'll have to spend a few hours reading
 ports documentation before you find them really
 great (which they really are).

I have no problem with reading as much documentation as I can find.
Aside from the handbook (Chapter 4, which is a nice overview) and man
pages (which are great for quick and complete reference), what else
would you recommend for gaining a more detailed understanding?  And I
do already agree that the port system is great, even with all the
trouble I'm having.

Thanks.

~John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Eric F Crist]

On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:


On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:


On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:



After clearing out the ports, updating ports (with portsnap) and
source, and rebuilding the system and kernel... it seemed the  
ultimate
problem was actually a dependency of the package to apache1.3.  
After I
ran 'pkgdb -F' and fixed this dependency to point to apache2.1,  
but

I still had trouble installing ports.



At this point, what usually works for me is to:

#cd /usr  rm -rf ./ports

#mkdir ./ports  cvsup /root/ports-supfile

The above will delete your ENTIRE ports tree, provided it's kept in / 
usr/ports and as long as you use cvsup (and your ports supfile is / 
root/ports-supfile as mine is).  When a whole bunch of ports stop  
working, I find this is the easiest thing to do.


The other thing I do is run a cron job every week that updates, via  
cvsup, the ports tree.  About once a year I perform the above, mostly  
to clean out the crap.  Re-downloading your entire ports tree will be  
quicker if you don't use the ports-all tag and actually define which  
port segments you are interested in.  For example, there's no real  
reason to download all the x11/kde/gnome crap if you're doing this on  
a headless server that isn't going to serve X.


HTH
___
Eric F Crist  I am so smart, S.M.R.T!
Secure Computing Networks  -Homer J Simpson

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Thursday 27 October 2005 18:49, Eric F Crist wrote:
 On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
  On 10/27/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/27/05, John DeStefano [EMAIL PROTECTED] wrote:
  After clearing out the ports, updating ports (with portsnap) and
  source, and rebuilding the system and kernel... it seemed the
  ultimate
  problem was actually a dependency of the package to apache1.3.
  After I
  ran 'pkgdb -F' and fixed this dependency to point to apache2.1,
  but
  I still had trouble installing ports.

 At this point, what usually works for me is to:

 #cd /usr  rm -rf ./ports

 #mkdir ./ports  cvsup /root/ports-supfile

 The above will delete your ENTIRE ports tree, provided it's kept in /
 usr/ports and as long as you use cvsup (and your ports supfile is /
 root/ports-supfile as mine is).  When a whole bunch of ports stop
 working, I find this is the easiest thing to do.

 The other thing I do is run a cron job every week that updates, via
 cvsup, the ports tree.  About once a year I perform the above, mostly
 to clean out the crap.  Re-downloading your entire ports tree will be
 quicker if you don't use the ports-all tag and actually define which
 port segments you are interested in.  For example, there's no real
 reason to download all the x11/kde/gnome crap if you're doing this on
 a headless server that isn't going to serve X.

 HTH

Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
I may be a bit biased but I reaaly think John D. should try running 
portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non 
issue for portmanager.

-Mike

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/18/05, John DeStefano [EMAIL PROTECTED] wrote:
 On 10/15/05, Andrew P. [EMAIL PROTECTED] wrote:
  On 10/16/05, John DeStefano [EMAIL PROTECTED] wrote:
   I'm trying to use portupgrade to update my installed ports. I ran into
   trouble with dependencies with ImageMagick and xorg-libraries, and I then
   followed the suggestion in UPDATING to delete XFree86 the imake-4 
   packages,
   and install the full xorg port.
  
   After all that, I got more dependency errors:
   'Stale dependency: aalib-1.4.r5_1 -- imake-4.3.0_1 -- manually run 'pkgdb
   -F' to fix, or specify -O to force.'
  
   'pkgdb -O' returned an invalid option error, and 'pkgdb -o aalib-1.4.r5_1'
   returned 'graphics/aalib'. I then ran 'pkgdb -F' to try and fix this (and
   many, many other) stale dependencies, but the error I got when trying to 
   run
   portupgrade afterward simply changed the stale dependency error to '
   aalib-1.4.r5_1 -- XFree86-libraries-4.3.0_6'.
  
   How does one get around these dependency errors without destroying a 
   system?
   Any good resources on dealing with this? I keep reading that I should just
   run 'pkgdb -F' but that only gets one so far.
  
   Thanks,
   ~John
   ___
  
  
 
  If you don't have a whole free week, consider
  deinstalling every port on your system (with
  pkg_deinstall preferably), installing cvsup,
  updating your ports tree, installing portupgrade,
  and portinstalling all the ports you really need.
  That should only take a couple of days :-)
 

 You're not kidding... between fixing these dependencies, trying to
 upgrade the ports, fixing more dependencies, upgrading ports, etc. ad
 nausem, I'm literally on my 9th straight day (obviously I don't mean
 24/7... I have a day job and something of a life) of trying to get
 through this process.

 And all this just because I wanted to install mbstring (so phpMyadmin
 would stop barking about it), and I needed to perform some simple
 updates first...

 Any pointers, alternatives, etc., would be appreciated.

 BTW, I can no longer automatically update my ports list (I mean with
 'portsdb -Uu' instead of fetching a premade index) due to a
 chinese/acroread-chsfont failed error.  I see via Google that this
 port was removed due to a security vulnerability, but I don't know
 how to remove it from my system, and UPDATING doesn't seem to mention
 it.  Help?

 Thanks,
 ~John


Either cvsup or portsnap extract should remove it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[John DeStefano]

On 10/15/05, Andrew P. [EMAIL PROTECTED] wrote:
 On 10/16/05, John DeStefano [EMAIL PROTECTED] wrote:
  I'm trying to use portupgrade to update my installed ports. I ran into
  trouble with dependencies with ImageMagick and xorg-libraries, and I then
  followed the suggestion in UPDATING to delete XFree86 the imake-4 packages,
  and install the full xorg port.
 
  After all that, I got more dependency errors:
  'Stale dependency: aalib-1.4.r5_1 -- imake-4.3.0_1 -- manually run 'pkgdb
  -F' to fix, or specify -O to force.'
 
  'pkgdb -O' returned an invalid option error, and 'pkgdb -o aalib-1.4.r5_1'
  returned 'graphics/aalib'. I then ran 'pkgdb -F' to try and fix this (and
  many, many other) stale dependencies, but the error I got when trying to run
  portupgrade afterward simply changed the stale dependency error to '
  aalib-1.4.r5_1 -- XFree86-libraries-4.3.0_6'.
 
  How does one get around these dependency errors without destroying a system?
  Any good resources on dealing with this? I keep reading that I should just
  run 'pkgdb -F' but that only gets one so far.
 
  Thanks,
  ~John
  ___
 
 

 If you don't have a whole free week, consider
 deinstalling every port on your system (with
 pkg_deinstall preferably), installing cvsup,
 updating your ports tree, installing portupgrade,
 and portinstalling all the ports you really need.
 That should only take a couple of days :-)


You're not kidding... between fixing these dependencies, trying to
upgrade the ports, fixing more dependencies, upgrading ports, etc. ad
nausem, I'm literally on my 9th straight day (obviously I don't mean
24/7... I have a day job and something of a life) of trying to get
through this process.

And all this just because I wanted to install mbstring (so phpMyadmin
would stop barking about it), and I needed to perform some simple
updates first...

Any pointers, alternatives, etc., would be appreciated.

BTW, I can no longer automatically update my ports list (I mean with
'portsdb -Uu' instead of fetching a premade index) due to a
chinese/acroread-chsfont failed error.  I see via Google that this
port was removed due to a security vulnerability, but I don't know
how to remove it from my system, and UPDATING doesn't seem to mention
it.  Help?

Thanks,
~John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re[2]: portupgrade stale dependencies

[Gerard Seibert]

On Saturday, October 15, 2005 9:21:00 PM, Andrew P. [EMAIL PROTECTED]
Subject: Re: portupgrade stale dependencies
Wrote these words of wisdom:

 On 10/16/05, John DeStefano [EMAIL PROTECTED] wrote:
  I'm trying to use portupgrade to update my installed ports. I ran into
  trouble with dependencies with ImageMagick and xorg-libraries, and I then
  followed the suggestion in UPDATING to delete XFree86 the imake-4 packages,
  and install the full xorg port.
 
  After all that, I got more dependency errors:
  'Stale dependency: aalib-1.4.r5_1 -- imake-4.3.0_1 -- manually run 'pkgdb
  -F' to fix, or specify -O to force.'
 
  'pkgdb -O' returned an invalid option error, and 'pkgdb -o aalib-1.4.r5_1'
  returned 'graphics/aalib'. I then ran 'pkgdb -F' to try and fix this (and
  many, many other) stale dependencies, but the error I got when trying to run
  portupgrade afterward simply changed the stale dependency error to '
  aalib-1.4.r5_1 -- XFree86-libraries-4.3.0_6'.
 
  How does one get around these dependency errors without destroying a system?
  Any good resources on dealing with this? I keep reading that I should just
  run 'pkgdb -F' but that only gets one so far.
 
  Thanks,
  ~John
 
 
 If you don't have a whole free week, consider
 deinstalling every port on your system (with
 pkg_deinstall preferably), installing cvsup,
 updating your ports tree, installing portupgrade,
 and portinstalling all the ports you really need.
 That should only take a couple of days :-)


* REPLY SEPARATOR *
On 10/11/2005 5:29:42 PM, Gerard Replied:

I certainly hope that this is not a production machine. Taking the
system out of service for a few days would certainly suck.

Personally, I have run into this dependency problem before, and have
just learned to ignore it. Eventually, it just seems to go away. Since I
started using portmanager instead of portupgrade, I have been able to
just ignore these problems.

IMHO, this entire dependency problem is something that needs serious
work. It would seem that there has to be a better way to keep these
dependencies synchronized without user intervention.

Just my 2¢.

-- 
Gerard Seibert
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

portupgrade stale dependencies

[John DeStefano]

I'm trying to use portupgrade to update my installed ports. I ran into
trouble with dependencies with ImageMagick and xorg-libraries, and I then
followed the suggestion in UPDATING to delete XFree86 the imake-4 packages,
and install the full xorg port.

After all that, I got more dependency errors:
'Stale dependency: aalib-1.4.r5_1 -- imake-4.3.0_1 -- manually run 'pkgdb
-F' to fix, or specify -O to force.'

'pkgdb -O' returned an invalid option error, and 'pkgdb -o aalib-1.4.r5_1'
returned 'graphics/aalib'. I then ran 'pkgdb -F' to try and fix this (and
many, many other) stale dependencies, but the error I got when trying to run
portupgrade afterward simply changed the stale dependency error to '
aalib-1.4.r5_1 -- XFree86-libraries-4.3.0_6'.

How does one get around these dependency errors without destroying a system?
Any good resources on dealing with this? I keep reading that I should just
run 'pkgdb -F' but that only gets one so far.

Thanks,
~John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade stale dependencies

[Andrew P.]

On 10/16/05, John DeStefano [EMAIL PROTECTED] wrote:
 I'm trying to use portupgrade to update my installed ports. I ran into
 trouble with dependencies with ImageMagick and xorg-libraries, and I then
 followed the suggestion in UPDATING to delete XFree86 the imake-4 packages,
 and install the full xorg port.

 After all that, I got more dependency errors:
 'Stale dependency: aalib-1.4.r5_1 -- imake-4.3.0_1 -- manually run 'pkgdb
 -F' to fix, or specify -O to force.'

 'pkgdb -O' returned an invalid option error, and 'pkgdb -o aalib-1.4.r5_1'
 returned 'graphics/aalib'. I then ran 'pkgdb -F' to try and fix this (and
 many, many other) stale dependencies, but the error I got when trying to run
 portupgrade afterward simply changed the stale dependency error to '
 aalib-1.4.r5_1 -- XFree86-libraries-4.3.0_6'.

 How does one get around these dependency errors without destroying a system?
 Any good resources on dealing with this? I keep reading that I should just
 run 'pkgdb -F' but that only gets one so far.

 Thanks,
 ~John
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]



If you don't have a whole free week, consider
deinstalling every port on your system (with
pkg_deinstall preferably), installing cvsup,
updating your ports tree, installing portupgrade,
and portinstalling all the ports you really need.
That should only take a couple of days :-)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]