portupgrade stale dependencies

On 10/27/05, Andrew P. <infofarmergmail.com> wrote:
> On 10/27/05, John DeStefano <john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

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

> On 10/27/05, Andrew P. <infofarmergmail.com> wrote:
>
>> On 10/27/05, John DeStefano <john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

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. <infofarmergmail.com> wrote:
> >> On 10/27/05, John DeStefano
<john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On 10/28/05, Michael C. Shultz <ringworm01gmail.com> 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. <infofarmergmail.com> wrote:
> > >> On 10/27/05, John DeStefano
<john.destefanogmail.com> 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-questionsfreebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"
>

I don't think that stale dependencies are an issue for
portupgrade as well, just add "-O" to the command-
line.
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Friday, October 28, 2005 3:25:14 AM, "Andrew
P." <infofarmergmail.com>
Subject: Re: portupgrade stale dependencies
Wrote these words of wisdom:

> On 10/28/05, Michael C. Shultz <ringworm01gmail.com> 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.
<infofarmergmail.com> wrote:
> > > >> On 10/27/05, John DeStefano
<john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On 10/28/05, Gerard Seibert <gerardseibercom.net> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Friday 28 October 2005 00:25, Andrew P. wrote:
> On 10/28/05, Michael C. Shultz <ringworm01gmail.com> 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.
<infofarmergmail.com> wrote:
> > > >> On 10/27/05, John DeStefano
<john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On 10/27/05, Michael C. Shultz <ringworm01gmail.com> 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. <infofarmergmail.com> wrote:
> > >> On 10/27/05, John DeStefano
<john.destefanogmail.com> 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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"