Trouble with upgrading ports...

[Eric Schuele]

Hello,

I am having difficulty upgrading ports on all my freebsd 5.3-stable
machines. They all have been cvsup'd and built within the last few days.

But for the last week, maybe two... something strange has been (not)
happening. Portversion no longer correctly reports what ports need
updating. But if I do a 'portupgrade -arR', the appropriate things get
upgraded.... and then later it says they 'succeed' the port!?! It feels
like the INDEX is not getting update at all, or something.

I have a script (attached) to update my system sources. I then
portupgrade, or buildworld whenever I feel like it. It has ben working
fine for quite sometime. Maybe the script is bad and I was bound to
mess my machines up. Not sure.

Either way... If I delete my INDEX and then 'make fetchindex'... things
don't resolve themselves. I'm really not sure where the problem is. I
was hoping someone could point me in the right direction. Below is an
example of the behavior I am seeing. This is happening on three
machines (all using the same scripts... and me).

fangorn# cd /usr/ports
fangorn# rm INDEX-5
fangorn# rm INDEX.db
fangorn# make fetchindex
INDEX-5.bz2 100% of 614 kB 366 kBps
fangorn# portsdb -u
[Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 12376 port
entries found
..........1000.........2000.........3000.........4 000.........5000.........6000.........7000........ .8000.........9000.........10000.........11000.... .....12000...
...... done]
fangorn# portversion -v -L "="
ImageMagick-6.1.9.4 > succeeds port (port has 6.1.9.2)
bitstream-vera-1.10_1 > succeeds port (port has 1.10)
docbook-xsl-1.68.1 > succeeds port (port has 1.68.0)
dri-6.2.1,2 > succeeds port (port has 6.2_2,2)
emacs-21.3_4 > succeeds port (port has 21.3_3)
gnutls-1.0.24_1 > succeeds port (port has 1.0.24)
libfpx-1.2.0.11 > succeeds port (port has 1.2.0.9_1)
fangorn# portupgrade -narR
---> Session started at: Sun, 20 Feb 2005 22:25:46 -0600
** No need to upgrade 'dagrab-0.3.5_1' (>= dagrab-0.3.5_1). (specify -f
to force)
<snip>
** No need to upgrade 'gkrellm-2.2.4_1' (>= gkrellm-2.2.4_1). (specify
-f to force)
---> Listing the results (+:done / -:ignored / *:skipped / !:failed)
- audio/dagrab (dagrab-0.3.5_1)
- textproc/xmlcatmgr (xmlcatmgr-2.2)
<snip>
- graphics/imlib2 (imlib2-1.1.2_1)
+ devel/libast (libast-0.5_1) <--- This DOES need upgrade
- textproc/jade (jade-1.2.1_9)
- www/firefox (firefox-1.0_7,1)
- x11-wm/fluxconf (fluxconf-0.9.7_1)
- sysutils/gkrellm2 (gkrellm-2.2.4_1)
---> Packages processed: 1 done, 168 ignored, 0 skipped and 0 failed
---> Session ended at: Sun, 20 Feb 2005 22:26:18 -0600 (consumed 00:00:32)
fangorn# exit

Everything that portversion reports as suceeding the ports, DOES. But
it shouldn't since the script updates the ports and THEN upgrades those
installed. Portupgrade correctly realizes that devel/libast requires an
upgrade... portversion does not.

I've looked in the past posts, handbook, man pages, UPDATING, various
READMEs.... but really not sure what I'm looking for at this point.

Thanks in advance.
--
Regards,
Eric

#!/bin/sh

# Get all new source!
echo
echo "------------------------------------------------"
echo "Grabbing source, docs, and ports..."
echo "------------------------------------------------"
cvsup -g -L 1 /root/update/my-supfile

echo
echo "------------------------------------------------"
echo "Updating documentation..."
echo "------------------------------------------------"
cd /usr/doc
export DOC_LANG=en_US.ISO8859-1
echo "Output to /dev/null..."
make install > /dev/null
echo "Done with docs."

echo
echo "------------------------------------------------"
echo "Updating ports index..."
echo "------------------------------------------------"
cd /usr/ports
make fetchindex
portsdb -u

echo
echo "------------------------------------------------"
echo "Checking package registry..."
echo "------------------------------------------------"
pkgdb -F

echo
echo "------------------------------------------------"
echo "Cleaning port distfiles..."
echo "------------------------------------------------"
portsclean -CDD

echo
echo "------------------------------------------------"
echo "Fetching distfiles for ports..."
echo "------------------------------------------------"
portupgrade -aFR

echo
echo "------------------------------------------------"
echo "Take note of the following ports..."
echo "------------------------------------------------"
portversion -v -L "="

echo
echo "------------------------------------------------"
echo "Feel free to build world or update your ports!"
echo "Finished at `/bin/date`."
echo "------------------------------------------------"
echo

[Michael C. Shultz]

On Sunday 20 February 2005 09:00 pm, Eric Schuele wrote:

> Hello,
>
> I am having difficulty upgrading ports on all my freebsd 5.3-stable
> machines. They all have been cvsup'd and built within the last few
> days.
>
> But for the last week, maybe two... something strange has been (not)
> happening. Portversion no longer correctly reports what ports need
> updating. But if I do a 'portupgrade -arR', the appropriate things
> get upgraded.... and then later it says they 'succeed' the port!?!
> It feels like the INDEX is not getting update at all, or something.
>
> I have a script (attached) to update my system sources. I then
> portupgrade, or buildworld whenever I feel like it. It has ben
> working fine for quite sometime. Maybe the script is bad and I was
> bound to mess my machines up. Not sure.
>
> Either way... If I delete my INDEX and then 'make fetchindex'...
> things don't resolve themselves. I'm really not sure where the
> problem is. I was hoping someone could point me in the right
> direction. Below is an example of the behavior I am seeing. This is
> happening on three machines (all using the same scripts... and me).
>
> fangorn# cd /usr/ports
> fangorn# rm INDEX-5
> fangorn# rm INDEX.db
> fangorn# make fetchindex
> INDEX-5.bz2 100% of 614 kB 366
> kBps fangorn# portsdb -u
> [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 12376
> port entries found
> .........1000.........2000.........3000.........40 00.........5000....
>.....6000.........7000.........8000.........9000. ........10000........
>.11000.........12000... ..... done]
> fangorn# portversion -v -L "="
> ImageMagick-6.1.9.4 > succeeds port (port has 6.1.9.2)
> bitstream-vera-1.10_1 > succeeds port (port has 1.10)
> docbook-xsl-1.68.1 > succeeds port (port has 1.68.0)
> dri-6.2.1,2 > succeeds port (port has 6.2_2,2)
> emacs-21.3_4 > succeeds port (port has 21.3_3)
> gnutls-1.0.24_1 > succeeds port (port has 1.0.24)
> libfpx-1.2.0.11 > succeeds port (port has 1.2.0.9_1)
> fangorn# portupgrade -narR
> ---> Session started at: Sun, 20 Feb 2005 22:25:46 -0600
> ** No need to upgrade 'dagrab-0.3.5_1' (>= dagrab-0.3.5_1). (specify
> -f to force)
> <snip>
> ** No need to upgrade 'gkrellm-2.2.4_1' (>= gkrellm-2.2.4_1).
> (specify -f to force)
> ---> Listing the results (+:done / -:ignored / *:skipped / !:failed)
> - audio/dagrab (dagrab-0.3.5_1)
> - textproc/xmlcatmgr (xmlcatmgr-2.2)
> <snip>
> - graphics/imlib2 (imlib2-1.1.2_1)
> + devel/libast (libast-0.5_1) <--- This DOES need upgrade
> - textproc/jade (jade-1.2.1_9)
> - www/firefox (firefox-1.0_7,1)
> - x11-wm/fluxconf (fluxconf-0.9.7_1)
> - sysutils/gkrellm2 (gkrellm-2.2.4_1)
> ---> Packages processed: 1 done, 168 ignored, 0 skipped and 0 failed
> ---> Session ended at: Sun, 20 Feb 2005 22:26:18 -0600 (consumed
> 00:00:32) fangorn# exit
>
> Everything that portversion reports as suceeding the ports, DOES.
> But it shouldn't since the script updates the ports and THEN upgrades
> those installed. Portupgrade correctly realizes that devel/libast
> requires an upgrade... portversion does not.
>
> I've looked in the past posts, handbook, man pages, UPDATING, various
> READMEs.... but really not sure what I'm looking for at this point.
>
> Thanks in advance.

sysutils/portmanager can upgrade those ports and does not need the INDEX
file to do so.

-Mike

[Kris Kennaway]

On Sun, Feb 20, 2005 at 11:00:37PM -0600, Eric Schuele wrote:

> Hello,
>
> I am having difficulty upgrading ports on all my freebsd 5.3-stable
> machines. They all have been cvsup'd and built within the last few days.
>
> But for the last week, maybe two... something strange has been (not)
> happening. Portversion no longer correctly reports what ports need
> updating. But if I do a 'portupgrade -arR', the appropriate things get
> upgraded.... and then later it says they 'succeed' the port!?! It feels
> like the INDEX is not getting update at all, or something.

Correct: the machine that builds fetchindex hasn't been getting cvs
updates since last week some time. I'm in the process of trying to
fix this. In the meantime, you can build your own index ('make
index') if you need to update, but this is quite resource-intensive.

Kris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCGWxGWry0BWjoQKURAsPSAKCPYxGBVM/mstH8B42fb69iTj+i2wCfa/cv
3ukg7khdHpSi3CQazyNLCcg=
=3vXq
-----END PGP SIGNATURE-----

[Rob]

Kris Kennaway wrote:>

> Correct: the machine that builds fetchindex hasn't
> been getting cvs updates since last week some time.
> I'm in the process of trying to fix this.
> In the meantime, you can build your own index
> ('make index') if you need to update, but this is
> quite resource-intensive.

I always generated the INDEX file myself (yes, it's
indeed resource and time consuming).

When I encountered trouble some time ago, I learned
from this mailing list that I can use "make
fetchindex" and that this is actually better.

I then frequently encounter following problem:
Since I am in Korea, I used cvsup.kr.freebsd.org for
cvsup-ing my ports. However, the 'make fetchindex'
dowloads the INDEX file from elsewhere, which may
not be in sync with my Korean cvsup host.
So I get conflicts when checking port versions and
upgrading outdated ports.

To solve this problem, I now always sync my ports
with one of the main cvsup hosts:
cvsup[n].freebsd.org.
So the Korean freeBSD hosts have become useless to
me.

Am I doing something wrong?

Rob.



__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
[url]http://mobile.yahoo.com/maildemo[/url]