subject:"Re\: portupgrade problem"

Craig Deal [EMAIL PROTECTED] writes:

 I installed portupgrade from packages today. Whenever I run portupgrade
 -arR or pkgdb -uvF I get the following message:
 
 /libexec/ld-elf.so.1: Shared object libcrypt.so.3 not found, required by
 ruby18
 
 I'm not sure what to do from here. I have ruby-1.8.2_4 and
 ruby18-bdb1-0.2.2 installed from packages also. Any suggestions on what to
 do from here?

Wild guess: you installed a 6.0 package on a 5.4 system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Portupgrade problem

2005-10-19 Thread Craig Deal

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Lowell Gilbert
 Sent: Wednesday, October 19, 2005 1:39 PM
 To: Craig Deal
 Cc: freebsd-questions@freebsd.org
 Subject: Re: Portupgrade problem

 Craig Deal [EMAIL PROTECTED] writes:

  I installed portupgrade from packages today. Whenever I run 
  portupgrade -arR or pkgdb -uvF I get the following message:

  /libexec/ld-elf.so.1: Shared object libcrypt.so.3 not found, 
  required by ruby18

  I'm not sure what to do from here. I have ruby-1.8.2_4 and 
  ruby18-bdb1-0.2.2 installed from packages also. Any 
 suggestions on 
  what to do from here?

 Wild guess: you installed a 6.0 package on a 5.4 system.
 ___

Is that possible using pkg_add -r portupgrade?

Craig

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

Re: Portupgrade problem

Craig Deal [EMAIL PROTECTED] writes:

  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Lowell Gilbert
  Sent: Wednesday, October 19, 2005 1:39 PM
  To: Craig Deal
  Cc: freebsd-questions@freebsd.org
  Subject: Re: Portupgrade problem

  Craig Deal [EMAIL PROTECTED] writes:

   I installed portupgrade from packages today. Whenever I run 
   portupgrade -arR or pkgdb -uvF I get the following message:

   /libexec/ld-elf.so.1: Shared object libcrypt.so.3 not found, 
   required by ruby18

   I'm not sure what to do from here. I have ruby-1.8.2_4 and 
   ruby18-bdb1-0.2.2 installed from packages also. Any 
  suggestions on 
   what to do from here?

  Wild guess: you installed a 6.0 package on a 5.4 system.
  ___

 Is that possible using pkg_add -r portupgrade?

It shouldn't be.  It looks like it can happen if you upgrade pkg_add
or the kernel without the other, and occasional bugs do slip in.

What does uname -a tell you?  [This is almost always a good thing to
include in your questions.]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

Lowell Gilbert [EMAIL PROTECTED] writes:

 Craig Deal [EMAIL PROTECTED] writes:
 
   
  
   -Original Message-
   From: [EMAIL PROTECTED] 
   [mailto:[EMAIL PROTECTED] On Behalf Of 
   Lowell Gilbert
   Sent: Wednesday, October 19, 2005 1:39 PM
   To: Craig Deal
   Cc: freebsd-questions@freebsd.org
   Subject: Re: Portupgrade problem
   
   Craig Deal [EMAIL PROTECTED] writes:
   
I installed portupgrade from packages today. Whenever I run 
portupgrade -arR or pkgdb -uvF I get the following message:

/libexec/ld-elf.so.1: Shared object libcrypt.so.3 not found, 
required by ruby18

I'm not sure what to do from here. I have ruby-1.8.2_4 and 
ruby18-bdb1-0.2.2 installed from packages also. Any 
   suggestions on 
what to do from here?
   
   Wild guess: you installed a 6.0 package on a 5.4 system.
   ___
  
  
  Is that possible using pkg_add -r portupgrade?
 
 It shouldn't be.  It looks like it can happen if you upgrade pkg_add
 or the kernel without the other, and occasional bugs do slip in.
 
 What does uname -a tell you?  [This is almost always a good thing to
 include in your questions.]

Oh, yes:  and sysctl kern.osreldate?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

Craig Deal [EMAIL PROTECTED] writes:

  -Original Message-
  From: Lowell Gilbert [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, October 19, 2005 2:40 PM
  To: freebsd-questions@freebsd.org
  Cc: Craig Deal
  Subject: Re: Portupgrade problem

  Lowell Gilbert [EMAIL PROTECTED] writes:

   Craig Deal [EMAIL PROTECTED] writes:

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf 
  Of Lowell 
 Gilbert
 Sent: Wednesday, October 19, 2005 1:39 PM
 To: Craig Deal
 Cc: freebsd-questions@freebsd.org
 Subject: Re: Portupgrade problem

 Craig Deal [EMAIL PROTECTED] writes:

  I installed portupgrade from packages today. Whenever I run 
  portupgrade -arR or pkgdb -uvF I get the following message:

  /libexec/ld-elf.so.1: Shared object libcrypt.so.3 not found, 
  required by ruby18

  I'm not sure what to do from here. I have ruby-1.8.2_4
  and ruby18-bdb1-0.2.2 installed from packages also. Any
  suggestions on what to do from here?

 Wild guess: you installed a 6.0 package on a 5.4 system.
 ___

Is that possible using pkg_add -r portupgrade?

   It shouldn't be.  It looks like it can happen if you upgrade pkg_add 
   or the kernel without the other, and occasional bugs do slip in.

   What does uname -a tell you?  [This is almost always a good thing to 
   include in your questions.]

  Oh, yes:  and sysctl kern.osreldate?

 FreeBSD mx1.acspros.com 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May  8
 10:21:06 UTC 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

 kern.osreldate: 504000

Well, those should definitely be fetching the 5.4-RELEASE packages.

How did you install ruby?  
That's the program (as opposed to portupgrade) that's trying to link
to the wrong library, and the version you have installed is not the
one you would have gotten from the 5.4-RELEASE packages.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Portupgrade problem

2005-10-19 Thread Craig Deal

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Lowell Gilbert
 Sent: Wednesday, October 19, 2005 3:15 PM
 To: Craig Deal; freebsd-questions@freebsd.org
 Subject: Re: Portupgrade problem

 Craig Deal [EMAIL PROTECTED] writes:

   -Original Message-
   From: Lowell Gilbert [mailto:[EMAIL PROTECTED]
   Sent: Wednesday, October 19, 2005 2:40 PM
   To: freebsd-questions@freebsd.org
   Cc: Craig Deal
   Subject: Re: Portupgrade problem

   Lowell Gilbert [EMAIL PROTECTED] writes:

Craig Deal [EMAIL PROTECTED] writes:

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf
   Of Lowell
  Gilbert
  Sent: Wednesday, October 19, 2005 1:39 PM
  To: Craig Deal
  Cc: freebsd-questions@freebsd.org
  Subject: Re: Portupgrade problem

  Craig Deal [EMAIL PROTECTED] writes:

   I installed portupgrade from packages today. 
 Whenever I run 
   portupgrade -arR or pkgdb -uvF I get the 
 following message:

   /libexec/ld-elf.so.1: Shared object libcrypt.so.3 not 
   found, required by ruby18

   I'm not sure what to do from here. I have ruby-1.8.2_4
   and ruby18-bdb1-0.2.2 installed from packages also. Any 
   suggestions on what to do from here?

  Wild guess: you installed a 6.0 package on a 5.4 system.
  ___

 Is that possible using pkg_add -r portupgrade?

It shouldn't be.  It looks like it can happen if you upgrade 
pkg_add or the kernel without the other, and occasional 
 bugs do slip in.

What does uname -a tell you?  [This is almost always a good 
thing to include in your questions.]

   Oh, yes:  and sysctl kern.osreldate?

  FreeBSD mx1.acspros.com 5.4-RELEASE FreeBSD 5.4-RELEASE #0: 
 Sun May  8
  10:21:06 UTC 2005
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

  kern.osreldate: 504000

 Well, those should definitely be fetching the 5.4-RELEASE packages.

 How did you install ruby?  
 That's the program (as opposed to portupgrade) that's trying 
 to link to the wrong library, and the version you have 
 installed is not the one you would have gotten from the 
 5.4-RELEASE packages.

That could be the problem. I used pkg_add
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages.. for some of the
packages, in order to get the most current version. I may have used the
wrong ftp folder on one of the them. Is
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/ or using
pkg_add -r the most current packages for ver. 5.4? If so, I think I will
just start over with a clean install.

Thanks for help.

Craig 

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

Re: Portupgrade problem

2005-04-08 Thread Micheal Patterson

- Original Message - 
From: Aperez [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Sent: Friday, April 08, 2005 1:23 PM
Subject: Portupgrade problem

 Hi

 I am having the following problem when I try to upgrade my ports:

 portupgrade -arR
 cd: can't cd to /usr/ports/multimedia/nautilus-media
 Port directory not found: multimedia/nautilus-media
 !multimedia/nautilus-media (nautilus-media-0.8.0_4) (port directory error)

 I checked in /usr/ports/multimedia and of course there is not such
 directory.

 Is there a way I can fix this?

 Thanks

Is your ports tree current via cvs? If not, I'd update the tree, then
rebuild portupgrade and see how that works for you.

--

Micheal Patterson
Senior Communications Systems Engineer
405-917-0600

Confidentiality Notice:  This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.

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

Re: Portupgrade problem

2005-04-08 Thread Sergei Gnezdov

On 2005-04-08, Aperez [EMAIL PROTECTED] wrote:
 Hi

 I am having the following problem when I try to upgrade my ports:

 portupgrade -arR
 cd: can't cd to /usr/ports/multimedia/nautilus-media
 Port directory not found: multimedia/nautilus-media
 !multimedia/nautilus-media (nautilus-media-0.8.0_4) (port directory error)

 I checked in /usr/ports/multimedia and of course there is not such 
 directory.

From /usr/ports/UPDATING

20050312:
  AFFECTS: all users who have glib/gtk/gnome libraries installed
  AUTHOR: [EMAIL PROTECTED] and the FreeBSD gnome team

  Gnome has been upgraded to 2.10 and gtk/glib to 2.6.
  DO NOT USE portupgrade(1) to update any gnome or gtk
  or any port that depends on them. Using portupgrade
  will cause problems and you will have to manually
  upgrade ports.  Please use the gnome_upgrade.sh
  script from
http://www.FreeBSD.org/gnome/gnome_upgrade.sh




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

Re: portupgrade problem

2004-11-16 Thread Kent Stewart

On Tuesday 16 November 2004 11:50 am, Brian W. wrote:
   I've been having this problem for about a week now.  I've already
 deinstalled and reinstalled the ruby, rubybdb and portupgrade ports, what
 else can I look at?  The below process takes at least an hour, its a
 k62-450. The no such user problem doesn't occur until a lot of time has
 gone by.

 # portupgrade -aP
 Updating the ports index ... Generating INDEX.tmp - please wait..id: www:
 no such user
 Makefile, line 21: warning: /usr/bin/id -u www returned non-zero status
   Done.
 done
 [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11959 port
 entries found
 .1000.2000.3000.4000.5000/u
sr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault
 ruby 1.8.2 (2004-07-29) [i386-freebsd4]

 Abort (core dumped)


There is a bug in the hashing routine. It was fixed in the active branches, 
i.e., RELENG_5 and not RELEMG_5_2. For a machine of that speed, I would 
probably do a make fetchindex. The last I read, it was bzip2'ed and is a 
600KB file. You would have to fetch it after every cvsup of ports-all. If it 
is bzip2'ed, you will have to uncompress it.

This has been anwered 100's of times. Other solutions can be found in the 
archives.

Kent
-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade problem in freebsd 4.10

2004-11-13 Thread Kevin D. Kinsey, DaleCo, S.P.

[EMAIL PROTECTED] wrote:
Things worked fine until last upgrade (this morning). Now I get the following
errors:
pc1# !?upgr
portupgrade -ra
Updating the ports index ... Generating INDEX.tmp - please wait..tkscanfax-1.02: 
/usr/ports/japanese/tk80 non-existent -- dependency list incomplete
=== comms/tkscanfax failed
*** Error code 1
1 error


Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection.  (INDEX builds are
not supported with partial or out-of-date ports collections -- in
particular, if you are using cvsup, you must cvsup the ports-all
collection, and have no refuse files.)  If that is the case, then
report the failure to [EMAIL PROTECTED] together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and WITH/WITHOUT settings).
Note: the latest pre-generated version of INDEX may be fetched
automatically with make fetchindex.

*** Error code 1
-
My refuse file has:
ports/japanese
---
Is the above error an indication that the new portupgrade tool now requires 
that I download the japanese port - or is there another workaround ?

Alan
 


It looks as if you've really answered your own question.
Two Japanese ports are runtime dependencies for tkscanfax:
--
[EMAIL PROTECTED]/usr/ports]
# make search name=tkscanfax
Port:   tkscanfax-1.02
Path:   /usr/ports/comms/tkscanfax
Info:   Tcl/Tk frontend for fax scan/receive/send program (command is tkfax)
Maint:  [EMAIL PROTECTED]
B-deps:
R-deps: XFree86-libraries-4.4.0_1 expat-1.95.8 fontconfig-2.2.3,1 
freetype2-2.1.7_3
imake-4.4.0 ja-tcl-8.0.5_1 ja-tk-8.0.5_2 perl-5.8.5 pkgconfig-0.15.0_1

And your setup violates this clause:
INDEX builds are not supported with partial or out-of-date ports collections -- 
in
particular, if you are using cvsup, you must cvsup the ports-all
collection, and have no refuse files.
You can draw your own conclusions.  I guess a couple of good questions
might be 1] when did I install tkscanfax? and 2] at that time, was there
a runtime dependency on these japanese ports, or was it added later?
Kevin Kinsey
DaleCo, S.P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade problem in freebsd 4.10

2004-11-13 Thread atk2

Ok thanks for the detail response.  I guess my confusion came from several
places - the handbook explicity gives an example where you can refuse 
ports that aren't relevant to your environment (i refuse several such as
japanese, chinese)...

Can you explain (if you know off hand) why make fetchindex would fix the
problem (it did without adding the ports)?

As a side but unrelated question it seems that recent updates to the port
colleciton (such as mozilla, mplayer and netscape) have bad values (either
size of time stamps) for the objects they are to fetch - do you know why
this is happening (aka is it specific to me?)

thanks,
Alan

  ||From [EMAIL PROTECTED]  Sat Nov 13 05:49:41 2004

  ||[EMAIL PROTECTED] wrote:

  ||Things worked fine until last upgrade (this morning). Now I get the 
following
  ||errors:
  ||
  ||pc1# !?upgr
  ||portupgrade -ra
  ||Updating the ports index ... Generating INDEX.tmp - please 
wait..tkscanfax-1.02: 
  || /usr/ports/japanese/tk80 non-existent -- dependency list 
incomplete
  ||=== comms/tkscanfax failed
  ||*** Error code 1
  ||1 error
  ||
  ||
  ||*** Error code 1
  ||-
  ||
  ||My refuse file has:
  ||ports/japanese
  ||---
  ||
  ||Is the above error an indication that the new portupgrade tool now 
requires 
  ||that I download the japanese port - or is there another workaround ?
  ||
  ||Alan
  ||  
  ||


  ||It looks as if you've really answered your own question.

  ||Two Japanese ports are runtime dependencies for tkscanfax:
  
||--
  ||[EMAIL PROTECTED]/usr/ports]
  ||# make search name=tkscanfax
  ||Port:   tkscanfax-1.02
  ||Path:   /usr/ports/comms/tkscanfax
  ||Info:   Tcl/Tk frontend for fax scan/receive/send program (command is tkfax)
  ||Maint:  [EMAIL PROTECTED]
  ||B-deps:
  ||R-deps: XFree86-libraries-4.4.0_1 expat-1.95.8 fontconfig-2.2.3,1 
  ||freetype2-2.1.7_3
  ||imake-4.4.0 ja-tcl-8.0.5_1 ja-tk-8.0.5_2 perl-5.8.5 pkgconfig-0.15.0_1


  ||And your setup violates this clause:

  ||INDEX builds are not supported with partial or out-of-date ports 
collections -- in
  ||particular, if you are using cvsup, you must cvsup the ports-all
  ||collection, and have no refuse files.


  ||You can draw your own conclusions.  I guess a couple of good questions
  ||might be 1] when did I install tkscanfax? and 2] at that time, was there
  ||a runtime dependency on these japanese ports, or was it added later?

  ||Kevin Kinsey
  ||DaleCo, S.P.


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

Re: portupgrade problem in freebsd 4.10

2004-11-13 Thread Kevin D. Kinsey, DaleCo, S.P.

[EMAIL PROTECTED] wrote:
Ok thanks for the detail response.  I guess my confusion came from several
places - the handbook explicity gives an example where you can refuse 
ports that aren't relevant to your environment (i refuse several such as
japanese, chinese)...

 

Hmm.  I wonder if we should consider mentioning that you don't want
to do this if you intend to make index ... I'll mention it on doc@ and see
what comes up.
Can you explain (if you know off hand) why make fetchindex would fix the
problem (it did without adding the ports)?
 

Yes.  make fetchindex downloaded a copy of the complete index database
from one of the ftp servers, thus bypassing the problem of makeing it on
your box.
As a side but unrelated question it seems that recent updates to the port
colleciton (such as mozilla, mplayer and netscape) have bad values (either
size of time stamps) for the objects they are to fetch - do you know why
this is happening (aka is it specific to me?)
thanks,
Alan
 

Hmm.  Is that local modification time does not match remote?
If you have downloads from fetch that have been interrupted (as
I do sometimes at home where I have a slow and occasionally unreliable
ppp link), you can fix that one by deleting the aborted files from 
/usr/ports/distfiles
and running make install or make install clean (or whatever) again.

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

Re: portupgrade problem

2004-10-11 Thread Matthew Seaman

On Mon, Oct 11, 2004 at 04:05:17PM +0100, Vince Hoffman wrote:
 Hi all,
   Got a port upgrade problem here, ruby is dumping core during a 
 portsdb -uU (and thus any time it tries to update the portsdb.
 only noticed it today but i did upgrade ruby recently so i tried following 
 the emergency recovery part in /usr/port/UPDATING and did
 pkg_delete portupgrade-\*
 pkg_delete -r ruby-\*
 then cd /usr/ports/sysutils/portupgrade
 make install clean
 
 but no joy, i still get the same error 
 -cut portupgrade error test--
 [EMAIL PROTECTED] [/root/cvsup-files] [13:59] 
 #portsdb -uU
 Updating the ports index ... Generating INDEX.tmp - please wait..test: : 
 unexpected operator
 Warning: Duplicate INDEX entry: freeciv-gtk2-1.14.1
 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.2
 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5
  Done.
 done
 [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11732 port 
 entries found 
 .1000.2000.3000.4000.5000.6000.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587:
  
 [BUG] Bus Error
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort (core dumped)
 --end of port upgrade error text--
 
 uname -a
 
 FreeBSD lobster.unsane.co.uk 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9 #2: 
 Fri Sep 17 21:45:48 BST 2004 
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/UNSANE  i386
 
 (14:40:05 ~) 0 $ ruby -v
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 any suggestions welcome

Gawd.  Not this *again*.  Did you try searhing the web at all?

   
http://freebsd.rambler.ru/srch?words=%5BBUG%5D+Bus+Error+%3E+ruby+1.8.2+%282004-07-29%29+%5Bi386-freebsd5%5D+solutionset=freebsd
 

Anyhow, a work-around is to:

% setenv PORTS_DBDRIVER=bdb1_hash

and then do all your portupgrade stuff as usual.  

The problem is with the bdb1_btree functions in the base system.  A
fix has been committed to HEAD, RELENG_4 and RELENG_5.  It won't be
applied to RELENG_5_2, so either you're going to have to extract the
patch yourself and apply it manually, or you can upgrade to one of the
5.3-BETAs.


http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?r1=1.5r2=1.7

Cheers,

Matthew 

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpSRzLsCzIuN.pgp
Description: PGP signature

Re: portupgrade problem

2004-10-11 Thread Vince Hoffman


On Mon, 11 Oct 2004, Matthew Seaman wrote:
On Mon, Oct 11, 2004 at 04:05:17PM +0100, Vince Hoffman wrote:
Hi all,
Got a port upgrade problem here, ruby is dumping core during a
portsdb -uU (and thus any time it tries to update the portsdb.
SNIP lots of info
any suggestions welcome
Gawd.  Not this *again*.  Did you try searhing the web at all?
  http://freebsd.rambler.ru/srch?words=%5BBUG%5D+Bus+Error+%3E+ruby+1.8.2+%282004-07-29%29+%5Bi386-freebsd5%5D+solutionset=freebsd
Doh no, since i try and read as much of -questions and -current I 
thought I would have caught it on the lists ;)
Thanks for the help (again)

Vince
Anyhow, a work-around is to:
   % setenv PORTS_DBDRIVER=bdb1_hash
and then do all your portupgrade stuff as usual.
The problem is with the bdb1_btree functions in the base system.  A
fix has been committed to HEAD, RELENG_4 and RELENG_5.  It won't be
applied to RELENG_5_2, so either you're going to have to extract the
patch yourself and apply it manually, or you can upgrade to one of the
5.3-BETAs.
   
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?r1=1.5r2=1.7
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
 Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Portupgrade problem, possible pkgdb problem?

2004-10-07 Thread Mire, John

I'm still getting this error after a cvsup+buildworld, a make fetchindex and
I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?:

test# uname -v
FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct  6 17:13:13 CDT 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST 
test# cd /usr/ports
test# make fetchindex
Receiving INDEX-5 (5881230 bytes): 100%
5881230 bytes transferred in 16.9 seconds (339.01 kBps)
test# portupgrade -R sudo
[Failed `Inappropriate file type or format'] [Updating the portsdb
format:bdb1_btree in /usr/ports ... - 11735 port entries found
.1000.2000.3000.4000.5000.60
00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
:587: [BUG] Bus Error
ruby 1.8.2 (2004-07-29) [i386-freebsd5]

Abort (core dumped)
test# rm /var/db/pkg/pkgdb.db
test# portupgrade -R sudo
[Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages
found (-0 +54) .. done]
[Failed `Inappropriate file type or format'] [Updating the portsdb
format:bdb1_btree in /usr/ports ... - 11735 port entries found
.1000.2000.3000.4000.5000.60
00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
:587: [BUG] Bus Error
ruby 1.8.2 (2004-07-29) [i386-freebsd5]

Abort (core dumped)
test#  


--
Ethernet (n): something used to catch the etherbunny

John Mire: [EMAIL PROTECTED]Network Administration
318-675-5434  LSU Health Sciences Center - Shreveport 

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer. 



 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Matthew Seaman
 Sent: Sunday, September 26, 2004 4:14 AM
 To: Matt Navarre
 Cc: [EMAIL PROTECTED]
 Subject: Re: Portupgrade problem, possible pkgdb problem?
 
 On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote:
  On Saturday 25 September 2004 05:13, Alex de Kruijff wrote:
 
   It could be a problem with the DBDriver. You could try this:
   Edit /root/.cs...
   and add
   PORTS_DBDRIVER=bdb1_hash
   PKG_DBDRIVER=bdb1_hash
 
  Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz 
 it isn't in this 
  case, it fails gracefully.
 
 The core dump is seen with portsdb(1) trying to create
 /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere
 that ruby uses bdb1_btree files.  pkgdb(1) occasionally going a bit
 funny is a problem that's been known about for some time; usually just
 deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out.
 However, I don't think anyone had ever tracked down the root cause of
 the problem.  Then the portsdb coredumping thing came along, and it
 seems an obvious conclusion that the same thing might be affecting
 both programs.
 
 Note that a fix for the bdb1_btree problem has been in HEAD for a few
 weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago.
 So an alternative fix could be cvsup+buildworld.  Unfortunately, I
 don't think the fix will be applied to any of the existing 4.x-RELEASE
 or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when
 that comes out, and it's pretty easy to do if you want to patch things
 yourself.
  
  I'll go ahead and try this, but I suspect that the 
 /var/db/pkg info for 
  gnucash or one of it's dependancies got horked up. We'll see.
  
   Then execute this in your shell also. Then do:
   pkgdb -u  portsdb -u  portupgrade -R gnucash
 
 Yup.  That should ensure you get a clean install of gnucash and all of
 its dependencies.
 
   Cheers,
 
   Matthew
 
 -- 
 Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
   Savill Way
 PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
 Tel: +44 1628 476614  Bucks., 
 SL7 1TH UK
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem, possible pkgdb problem?

2004-10-07 Thread Matthew Seaman

On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote:
 I'm still getting this error after a cvsup+buildworld, a make fetchindex and
 I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?:
 
 test# uname -v
 FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct  6 17:13:13 CDT 2004
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST 
 test# cd /usr/ports
 test# make fetchindex
 Receiving INDEX-5 (5881230 bytes): 100%
 5881230 bytes transferred in 16.9 seconds (339.01 kBps)
 test# portupgrade -R sudo
 [Failed `Inappropriate file type or format'] [Updating the portsdb
 format:bdb1_btree in /usr/ports ... - 11735 port entries found
 .1000.2000.3000.4000.5000.60
 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
 :587: [BUG] Bus Error
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort (core dumped)
 test# rm /var/db/pkg/pkgdb.db
 test# portupgrade -R sudo
 [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages
 found (-0 +54) .. done]
 [Failed `Inappropriate file type or format'] [Updating the portsdb
 format:bdb1_btree in /usr/ports ... - 11735 port entries found
 .1000.2000.3000.4000.5000.60
 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
 :587: [BUG] Bus Error
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort (core dumped)
 test#  

The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not
RELENG_5_2.

However, you can extract it from cvs and apply it yourself by hand if
you aren't in a position to upgrade right now -- see:


http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?r1=1.5r2=1.7

(Remember that you'll have to re-apply that patch each time you
cvsup(1) your src)

Otherwise just use one of the variations on:

setenv PORTS_DBDRIVER=bdb1_hash

as a workaround.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpRm4klv3Ptz.pgp
Description: PGP signature

Re: Portupgrade problem, possible pkgdb problem?

2004-10-07 Thread Mire, John

Thanks, guess it's time to use the work around, the env setting worked fine.





--
Ethernet (n): something used to catch the etherbunny

John Mire: [EMAIL PROTECTED]Network Administration
318-675-5434  LSU Health Sciences Center - Shreveport 


-Original Message-
From: Matthew Seaman [EMAIL PROTECTED]
To: Mire, John [EMAIL PROTECTED]
CC: Matt Navarre [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Sent: Thu Oct 07 12:41:17 2004
Subject: Re: Portupgrade problem, possible pkgdb problem?

On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote:
 I'm still getting this error after a cvsup+buildworld, a make fetchindex
and
 I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?:
 
 test# uname -v
 FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct  6 17:13:13 CDT 2004
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST 
 test# cd /usr/ports
 test# make fetchindex
 Receiving INDEX-5 (5881230 bytes): 100%
 5881230 bytes transferred in 16.9 seconds (339.01 kBps)
 test# portupgrade -R sudo
 [Failed `Inappropriate file type or format'] [Updating the portsdb
 format:bdb1_btree in /usr/ports ... - 11735 port entries found

.1000.2000.3000.4000.5000.60

00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
 :587: [BUG] Bus Error
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort (core dumped)
 test# rm /var/db/pkg/pkgdb.db
 test# portupgrade -R sudo
 [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages
 found (-0 +54) ..
done]
 [Failed `Inappropriate file type or format'] [Updating the portsdb
 format:bdb1_btree in /usr/ports ... - 11735 port entries found

.1000.2000.3000.4000.5000.60

00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb
 :587: [BUG] Bus Error
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort (core dumped)
 test#  

The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not
RELENG_5_2.

However, you can extract it from cvs and apply it yourself by hand if
you aren't in a position to upgrade right now -- see:

 
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?
r1=1.5r2=1.7

(Remember that you'll have to re-apply that patch each time you
cvsup(1) your src)

Otherwise just use one of the variations on:

setenv PORTS_DBDRIVER=bdb1_hash

as a workaround.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem, possible pkgdb problem?

2004-09-26 Thread Matthew Seaman

On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote:
 On Saturday 25 September 2004 05:13, Alex de Kruijff wrote:

  It could be a problem with the DBDriver. You could try this:
  Edit /root/.cs...
  and add
  PORTS_DBDRIVER=bdb1_hash
  PKG_DBDRIVER=bdb1_hash

 Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this 
 case, it fails gracefully.

The core dump is seen with portsdb(1) trying to create
/usr/ports/INDEX.db -- however, the underlying bug can affect anywhere
that ruby uses bdb1_btree files.  pkgdb(1) occasionally going a bit
funny is a problem that's been known about for some time; usually just
deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out.
However, I don't think anyone had ever tracked down the root cause of
the problem.  Then the portsdb coredumping thing came along, and it
seems an obvious conclusion that the same thing might be affecting
both programs.

Note that a fix for the bdb1_btree problem has been in HEAD for a few
weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago.
So an alternative fix could be cvsup+buildworld.  Unfortunately, I
don't think the fix will be applied to any of the existing 4.x-RELEASE
or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when
that comes out, and it's pretty easy to do if you want to patch things
yourself.
 
 I'll go ahead and try this, but I suspect that the /var/db/pkg info for 
 gnucash or one of it's dependancies got horked up. We'll see.
 
  Then execute this in your shell also. Then do:
  pkgdb -u  portsdb -u  portupgrade -R gnucash

Yup.  That should ensure you get a clean install of gnucash and all of
its dependencies.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpVii1Bm2YMS.pgp
Description: PGP signature

Re: Portupgrade problem, possible pkgdb problem?

2004-09-25 Thread Matt Navarre

On Saturday 25 September 2004 02:35, Matt Navarre wrote:
 I'm trying to upgrade gnucash, but portupgrade is choking:

 reichlieu# portupgrade -R gnucash
 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot
 convert nil into String (PkgDB::DBError)
 from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in
 `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each'
 from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from
 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from
 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from
 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from
 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from
 /usr/local/sbin/portupgrade:674:in `main'
 from /usr/local/sbin/portupgrade:207:in `initialize'
 from /usr/local/sbin/portupgrade:207:in `new'
 from /usr/local/sbin/portupgrade:207:in `main'
 from /usr/local/sbin/portupgrade:1845

 It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't
 report anything that seems like it would cause portupgrade to bomb. There's
 a duplicate origin for cdrtools, but that doesn't seem to pertain.

 Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will
 pkgdb -u recreate pkgdb.db?

Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same 
problem. Odd thing is that so far gnucash is the only installed package that 
generates this error. I suppose I can pkg_delete it and try reinstalling.

 Thanks,
 Matt

-- 
We all enter this world in the same way: naked, screaming,
 and soaked in blood. But if you live your life right, that kind
 of thing doesn't have to stop there. -- Dana Gould
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem, possible pkgdb problem?

2004-09-25 Thread Alex de Kruijff

On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote:
 On Saturday 25 September 2004 02:35, Matt Navarre wrote:
  I'm trying to upgrade gnucash, but portupgrade is choking:
 
  reichlieu# portupgrade -R gnucash
  /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot
  convert nil into String (PkgDB::DBError)
  from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in
  `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each'
  from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from
  /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from
  /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from
  /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from
  /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from
  /usr/local/sbin/portupgrade:674:in `main'
  from /usr/local/sbin/portupgrade:207:in `initialize'
  from /usr/local/sbin/portupgrade:207:in `new'
  from /usr/local/sbin/portupgrade:207:in `main'
  from /usr/local/sbin/portupgrade:1845
 
  It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't
  report anything that seems like it would cause portupgrade to bomb. There's
  a duplicate origin for cdrtools, but that doesn't seem to pertain.
 
  Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will
  pkgdb -u recreate pkgdb.db?
 
 Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same 
 problem. Odd thing is that so far gnucash is the only installed package that 
 generates this error. I suppose I can pkg_delete it and try reinstalling.

It could be a problem with the DBDriver. You could try this:
Edit /root/.cs...
and add
PORTS_DBDRIVER=bdb1_hash
PKG_DBDRIVER=bdb1_hash

Then execute this in your shell also. Then do:
pkgdb -u  portsdb -u  portupgrade -R gnucash

-- 
Alex

Articles based on solutions that I use:
http://www.kruijff.org/alex/FreeBSD/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem, possible pkgdb problem?

2004-09-25 Thread Matt Navarre

On Saturday 25 September 2004 05:13, Alex de Kruijff wrote:
 On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote:
  On Saturday 25 September 2004 02:35, Matt Navarre wrote:
   I'm trying to upgrade gnucash, but portupgrade is choking:
  
*snip*
  
   It looks like the pkgdb has something wrong with it, but pkgdb -Fu
   doesn't report anything that seems like it would cause portupgrade to
   bomb. There's a duplicate origin for cdrtools, but that doesn't seem to
   pertain.
  
   Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it?
   Will pkgdb -u recreate pkgdb.db?
 
  Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the
  same problem. Odd thing is that so far gnucash is the only installed
  package that generates this error. I suppose I can pkg_delete it and try
  reinstalling.

 It could be a problem with the DBDriver. You could try this:
 Edit /root/.cs...
 and add
 PORTS_DBDRIVER=bdb1_hash
 PKG_DBDRIVER=bdb1_hash
Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this 
case, it fails gracefully.

I'll go ahead and try this, but I suspect that the /var/db/pkg info for 
gnucash or one of it's dependancies got horked up. We'll see.

 Then execute this in your shell also. Then do:
 pkgdb -u  portsdb -u  portupgrade -R gnucash

-- 
We all enter this world in the same way: naked, screaming,
 and soaked in blood. But if you live your life right, that kind
 of thing doesn't have to stop there. -- Dana Gould
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade problem

2004-06-03 Thread Lowell Gilbert

Jarrod Wageman [EMAIL PROTECTED] writes:

 when running portversion -v -l  Nothing returns so I assume this
 means no errors, but, after cvsup -v -L 2 supfile updating the index
 and the database of ports, and then running portupgrade -a (which
 after reading the man page I assume
 
 that it updates all out dated ports) nothing happens, ssh -V returns
 3.6p1 which is an old version, and nothing else will update. I have
 read through the ports guide in the handbook and after reading through
 that and following the steps I get to make buildworld and I cannot
 make buildworld. I want to test the freeBSD evironment and it's
 serving capabilities and I have heard nothing but good things about
 it. Thanks for your time.

ssh is in the base system, not normally installed as a port, and on
-STABLE that would give you OpenSSH_3.5p1 FreeBSD-20030924.  The
openssh port is currently at 3.6.1, and the openssh-portable port is
3.8.1p1.  Check where your current ssh command is coming from before
deciding whether and how to update it.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-10 Thread Andreas Davour


I wanted to send my heartfelt thanks to all who chimed in with helpful
suggestions on my portupgrade problem.

I have now learned that ports-all is proably the best option for a
ports-supfile, and I'll have to look into the issue about a refuse file
instead when I want to limit the selection.

I have also learnt the importance of running 'portsdb -Uu' after
upgrading.

Now I think I know how to do these things and after another upgrade I
think I'm ready to at least do the cvsup part using cron.

Once again, many thanks!

/andreas

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

Re: Portupgrade problem

2004-04-10 Thread Martin Hudec

You're welcome :).


Cheers,

Martin

On Sat, Apr 10, 2004 at 04:51:10PM +0200 or thereabouts, Andreas Davour wrote:
 
 I wanted to send my heartfelt thanks to all who chimed in with helpful
 suggestions on my portupgrade problem.
 
 I have now learned that ports-all is proably the best option for a
 ports-supfile, and I'll have to look into the issue about a refuse file
 instead when I want to limit the selection.
 
 I have also learnt the importance of running 'portsdb -Uu' after
 upgrading.
 
 Now I think I know how to do these things and after another upgrade I
 think I'm ready to at least do the cvsup part using cron.
 
 Once again, many thanks!

-- 
=--
:
:. kind regards
:.. Martin Hudec
:.:
:.: :m: +421.907.303393
:.: :@: [EMAIL PROTECTED]
:.: :w: http://www.aeternal.net

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

Re: Portupgrade problem

2004-04-10 Thread Kent Stewart

On Saturday 10 April 2004 07:51 am, Andreas Davour wrote:
 I wanted to send my heartfelt thanks to all who chimed in with
 helpful suggestions on my portupgrade problem.

 I have now learned that ports-all is proably the best option for a
 ports-supfile, and I'll have to look into the issue about a refuse
 file instead when I want to limit the selection.

 I have also learnt the importance of running 'portsdb -Uu' after
 upgrading.

Since you will now be running portsdb -uU, you should refuse 
ports/INDEX[-5]. This dependis on whether you are running 4.x or [-5] 
if you are running 5.x. You are going to recreate the INDEX file and it 
takes a long time to redownload even over a 100Mbps network. Since you 
have recreated your INDEX file, cvsup will download it everytime you 
cvsup ports-all. The refuse saves you from re-downloading a don't need 
5 MB file.


 Now I think I know how to do these things and after another upgrade I
 think I'm ready to at least do the cvsup part using cron.

The hardest part of a cron job is finding that magic time after the hour 
that never fails because your cvsup-mirror is over committed. The 
mirrors always update on the hour and you have to wait at least 10 
minutes for the mirror to finish its cvsup. If you don't, you are 
getting data from the mirror's previous update. 

I currently schedule my local mirror update at 25 minutes after the 
hour. It has been more than 2 days since the update failed. All mirrors 
are not created equal. When something major like  FreeBSD 4.10 is 
released, there is no magic time and you will probably find that the 
cronjob frequently fails for around a day.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-10 Thread Chuck Swiger

Kent Stewart wrote:
On Saturday 10 April 2004 07:51 am, Andreas Davour wrote:
Now I think I know how to do these things and after another upgrade I
think I'm ready to at least do the cvsup part using cron.
The hardest part of a cron job is finding that magic time after the hour 
that never fails because your cvsup-mirror is over committed. The 
mirrors always update on the hour and you have to wait at least 10 
minutes for the mirror to finish its cvsup. If you don't, you are 
getting data from the mirror's previous update. 
Try something like:

	cvsup /etc/ports-supfile  portsdb -Uu

...as your cron job, or else put the commands into a script which you run from 
cron.  The second command will run once the first command is finished, so you 
don't need to worry about the cvsup not finishing before doing the portsdb.

[ I don't see a need to automaticly update the ports tree every hour from a 
cvsup mirror: doing so creates 24 cvsup sessions per day per machine.  Isn't 
once a day frequent enough?  :-) ]

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

On Saturday 10 April 2004 12:05 pm, Chuck Swiger wrote:
Kent Stewart wrote:
On Saturday 10 April 2004 07:51 am, Andreas Davour wrote:
Now I think I know how to do these things and after another upgrade
I think I'm ready to at least do the cvsup part using cron.

The hardest part of a cron job is finding that magic time after the
hour that never fails because your cvsup-mirror is over committed.
The mirrors always update on the hour and you have to wait at least
10 minutes for the mirror to finish its cvsup. If you don't, you
are getting data from the mirror's previous update.

Try something like:

cvsup /etc/ports-supfile portsdb -Uu

...as your cron job, or else put the commands into a script which you
run from cron. The second command will run once the first command is
finished, so you don't need to worry about the cvsup not finishing
before doing the portsdb.

[ I don't see a need to automaticly update the ports tree every hour
from a cvsup mirror: doing so creates 24 cvsup sessions per day per
machine. Isn't once a day frequent enough? :-) ]

I do it twice and cvsup my mirror about every 4 hours. My cronjob fires
off uports. It is

ruby# cat uports
#! /bin/sh
export
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin
cd /root/cvsup
cvsup -g -L 2 ports-supfile 21 | tee /var/log/build/ports_cvsup.log

cd /var/log/build

# Now convert the log to html`
cvsuplog ports_cvsup.log ports-`date +%Y%m%d-%H%M`.html

# Now update the index pages.
cd /usr/ports
#
# make bzip2 backup and save 4 old ones for the days when make index
# is broken
#
rm INDEX.3.bz2
mv INDEX.2.bz2 INDEX.3.bz2
mv INDEX.1.bz2 INDEX.2.bz2
mv INDEX.0.bz2 INDEX.1.bz2
bzip2 -c INDEX INDEX.0.bz2
#
# make new INDEX
#
make index 21 | tee /var/log/build/make-index-`date
+%Y%m%d-%H%M`.log
portsdb -u

I could do the thing but I want the log more than I care if it runs
or not. I could cut back on some of the tee but I see mail after it
runs.

Kent

--
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-10 Thread Chuck Swiger

Kent Stewart wrote:
On Saturday 10 April 2004 12:05 pm, Chuck Swiger wrote:
[ ... ]
I could do the  thing but I want the log more than I care if it runs 
or not. I could cut back on some of the tee but I see mail after it 
runs.
That's OK-- the  thing is mostly useful within a one-liner anyway.  Your 
script already has explicit sequencing of lines anyway and does a few more 
useful things, besides.  :-)

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

Re: Portupgrade problem

2004-04-10 Thread Kent Stewart

On Saturday 10 April 2004 01:17 pm, Chuck Swiger wrote:
 Kent Stewart wrote:
  On Saturday 10 April 2004 12:05 pm, Chuck Swiger wrote:

 [ ... ]

  I could do the  thing but I want the log more than I care if it
  runs or not. I could cut back on some of the tee but I see mail
  after it runs.

 That's OK-- the  thing is mostly useful within a one-liner
 anyway.  Your script already has explicit sequencing of lines anyway
 and does a few more useful things, besides.  :-)

FWIW, the mirror is on a slower machine that 6 other computers use. The 
INDEX files are only built on an AMD 2400+. They are ftp'ed to the 
other machines where I only do the cvsup and create the logs. 

The other machines are only cvsup'ed when necessary. They may go for 
several weeks. When the ports are updated, they are updated from 
packages created on ruby and shared on the other 4.x computers..

I try to keep ruby in such a state that if someone has problems building 
a port, I can test build it on an up todate system. The logs let me 
come close to pin pointing who broke things if it was the committer. 
Cvsuplog makes that easier because it creates an HTML link to the 
cvsweb cgi for the file that was changed.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-09 Thread Kevin D. Kinsey, DaleCo, S.P.

Andreas Davour wrote:

Hi!

I just decided to take a deep breath and cvsup some fresh ports. Now,
having done that I have run 'portupgrade -ar' and constantly found it to
stop some problems.
Some ports have failed and been flagged as configure error or install
error. Then I have tried to do a manual install of those ports and found
that a make deinstall; make reinstall have worked, just like the port
instructed me to do when it failed. I found it strange that portupgrade
didn't do that for me.
Having done that I restarted portupgrade and it would proceed a bit before
stumbling to a halt again.
Now I have reached the end of what I can fix manually, though. For some
reason portupgrade stubbornly complains that:
** Listing the failed packages (*:skipped / !:failed)
   ! accessibility/atk (atk-1.4.1_1)   (port directory error)
And it is correct in that there *is* no accessibility/atk port in my new
cvsup'ed ports tree. But why is it then telling me it needs it!?
Can I get the atk ports from somewhere? Is it really needed? Why has it
dissapeared and why is it still mentioned as a dependency then?
If anyone can shed some light on those matters, then I'm all ears. I can't
get a new version of Firefox to compile without atk so I'm very interested
in getting this to work.
I have run 'pkgdb -F' and tried to remove the dependecy, but have not
succeeded. I'm not even sure it would be wise to do it...
Help?

/andreas

 

It is best to have a ports tree that contains almost
everything except foreign languages when using BSD on
a workstation or in a desktop environment --- there are
so many dependancies.
That said, you haven't told us how old your ports tree
is; please look at /usr/ports/UPDATING and note that
in the last few months there have been a couple of big
issues, namely new versions of expat and gettext, IIRC,
that affect many, many of the commonly used 3rd party
sw packages/ports.
Kevin Kinsey
Daleco, S.P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

On Friday 09 April 2004 11:55 am, Andreas Davour wrote:
 Hi!

 I just decided to take a deep breath and cvsup some fresh ports. Now,
 having done that I have run 'portupgrade -ar' and constantly found it
 to stop some problems.

 Some ports have failed and been flagged as configure error or
 install error. Then I have tried to do a manual install of those
 ports and found that a make deinstall; make reinstall have worked,
 just like the port instructed me to do when it failed. I found it
 strange that portupgrade didn't do that for me.

 Having done that I restarted portupgrade and it would proceed a bit
 before stumbling to a halt again.

 Now I have reached the end of what I can fix manually, though. For
 some reason portupgrade stubbornly complains that:

 ** Listing the failed packages (*:skipped / !:failed)
 ! accessibility/atk (atk-1.4.1_1)   (port directory
 error)

 And it is correct in that there *is* no accessibility/atk port in my
 new cvsup'ed ports tree. But why is it then telling me it needs it!?

 Can I get the atk ports from somewhere? Is it really needed? Why has
 it dissapeared and why is it still mentioned as a dependency then?

 If anyone can shed some light on those matters, then I'm all ears. I
 can't get a new version of Firefox to compile without atk so I'm very
 interested in getting this to work.

 I have run 'pkgdb -F' and tried to remove the dependecy, but have not
 succeeded. I'm not even sure it would be wise to do it...

 Help?

Firefox depends on gtk-2.4.0, which depends on atk. All of these 
problems relate back to updating dependancies of glib-2.4.0.

The question at this point is what you updated and the order. If you 
were starting out clean, a portupgrade -rR glib would have done most of 
this but I wouldn't bet money. I eventually did a -rf glib to get 
things built cleanly.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

On Fri, 9 Apr 2004, Andrew L. Gould wrote:

 On Friday 09 April 2004 01:55 pm, Andreas Davour wrote:
[snip]
  If anyone can shed some light on those matters, then I'm all ears. I can't
  get a new version of Firefox to compile without atk so I'm very interested
  in getting this to work.
 
  I have run 'pkgdb -F' and tried to remove the dependecy, but have not
  succeeded. I'm not even sure it would be wise to do it...

 Did you remember to execute 'pkgdb -Uu' after cvsup and before portupgrade?

So be quite frank, I have no idea! I think I followed all instructions
quite litterally. But portupgrade was mentioned in the handbook and the
cookbook examples I found on the web differed somewhat. I no longer
remembered if I did a 'pkgdb -Uu' or not.

I there any telltale signs showing in the narrative in my first post that
indicates I forgot it? Is it recommendable I run it now then?

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

Re: Portupgrade problem

2004-04-09 Thread Kevin D. Kinsey, DaleCo, S.P.

Andreas Davour wrote:

Hi!

And it is correct in that there *is* no accessibility/atk port in my new
cvsup'ed ports tree. But why is it then telling me it needs it!?
 

Because it's a dependancy of about 538 distinct
ports, at least one of which you must have
installed
GNOME, perhaps 

Kevin Kinsey

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

Re: Portupgrade problem

2004-04-09 Thread Martin Hudec

Hello,

I am using portupgrade -airR for a long long time without any signs
of trouble :), just for few days I am observing a message from portaudit
regarding of upgrading my Midnight Commander that due to bug in mc (as do
portaudit say) there will be no upgrade :). I thought that that bug was
fixed in 4.6.0_9 version, but portaudit still complains..


Cheers,


Martin

On Fri, Apr 09, 2004 at 12:12:47PM -0700 or thereabouts, Kent Stewart wrote:
 The question at this point is what you updated and the order. If you 
 were starting out clean, a portupgrade -rR glib would have done most of 
 this but I wouldn't bet money. I eventually did a -rf glib to get 
 things built cleanly.

-- 
=--
:
:. kind regards
:.. Martin Hudec
:.:
:.: :m: +421.907.303393
:.: :@: [EMAIL PROTECTED]
:.: :w: http://www.aeternal.net

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

Re: Portupgrade problem

On Fri, 9 Apr 2004, Kevin D. Kinsey, DaleCo, S.P. wrote:

 It is best to have a ports tree that contains almost
 everything except foreign languages when using BSD on
 a workstation or in a desktop environment --- there are
 so many dependancies.

So I thought. I edited away everything that was exotic languages ports and
kept the rest.

 That said, you haven't told us how old your ports tree
 is; please look at /usr/ports/UPDATING and note that
 in the last few months there have been a couple of big
 issues, namely new versions of expat and gettext, IIRC,
 that affect many, many of the commonly used 3rd party
 sw packages/ports.

Stupid me. I had 5.2-RELEASE installed, and did a cvsup 4 days ago. I have
followed all the instructions in the UPDATING file.

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

Re: Portupgrade problem

2004-04-09 Thread Martin Hudec

Hi Andreas,

don't you really have atk in /usr/ports/accessibility/atk directory?
Perhaps look into ports-supfile.. do you have there ports-all enabled?

cheers,


Martin

On Fri, Apr 09, 2004 at 08:55:04PM +0200 or thereabouts, Andreas Davour wrote:
 And it is correct in that there *is* no accessibility/atk port in my new
 cvsup'ed ports tree. But why is it then telling me it needs it!?
 
 Can I get the atk ports from somewhere? Is it really needed? Why has it
 dissapeared and why is it still mentioned as a dependency then?

-- 
=--
:
:. kind regards
:.. Martin Hudec
:.:
:.: :m: +421.907.303393
:.: :@: [EMAIL PROTECTED]
:.: :w: http://www.aeternal.net

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

Re: Portupgrade problem

On Fri, 9 Apr 2004, Kent Stewart wrote:

 Firefox depends on gtk-2.4.0, which depends on atk. All of these
 problems relate back to updating dependancies of glib-2.4.0.

Ok, that at least explains why atk seems so important.

 The question at this point is what you updated and the order. If you
 were starting out clean, a portupgrade -rR glib would have done most of
 this but I wouldn't bet money. I eventually did a -rf glib to get
 things built cleanly.

Well, I started out with a clean 5.2-RELEASE and did cvsup 4 days ago. I
don't remember seeing glib being upgraded, but I guess I could always try
to '-rf glib' if it is a problem.

It still don't tell me why I have no directory for atk, though...

/andreas

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

Re: Portupgrade problem

On Fri, 9 Apr 2004, Kevin D. Kinsey, DaleCo, S.P. wrote:

 Andreas Davour wrote:

 Hi!
 
 And it is correct in that there *is* no accessibility/atk port in my new
 cvsup'ed ports tree. But why is it then telling me it needs it!?

 Because it's a dependancy of about 538 distinct
 ports, at least one of which you must have
 installed

 GNOME, perhaps 

538!!

Well, I haven't installed GNOME, but some other port might depend on some
GNOME component, I guess.

That sounds like an important port. I don't understand why I wasn't
getting it when I cvsup'ed then. Is there a line the the ports-supfile
which should read 'ports-accessibility'? Maybe I should add it and cvsup
again.

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

Re: Portupgrade problem

On Fri, 9 Apr 2004, Martin Hudec wrote:

 Hi Andreas,

   don't you really have atk in /usr/ports/accessibility/atk directory?

No.

 Perhaps look into ports-supfile.. do you have there ports-all enabled?

No, I have it commented out, since I left all the individual ports
collections in there instead, except for arabic, hebrew and some other
exotic languages.

Could it be I have made such a basic mistake as to not cvsup'ed a vital
dependedcy?! I kind of figured the newly cvsup'ed port of cvsup would have
included a new example file of ports-supfile if that had been the problem.

One should never *expect* a computer to do something I guess.

Would something strange happen now if I added a line for
'ports-accessability' in my ports-supfile and tried to cvsup again?

I guess I *really* should do a pkgdb -Uu then?

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

Re: Portupgrade problem

2004-04-09 Thread Erik Trulsson

On Fri, Apr 09, 2004 at 09:34:09PM +0200, Andreas Davour wrote:
 On Fri, 9 Apr 2004, Martin Hudec wrote:
 
  Hi Andreas,
 
  don't you really have atk in /usr/ports/accessibility/atk directory?
 
 No.
 
  Perhaps look into ports-supfile.. do you have there ports-all enabled?
 
 No, I have it commented out, since I left all the individual ports
 collections in there instead, except for arabic, hebrew and some other
 exotic languages.

That was a bad idea, since new collections are added from time to time.
If you really feel the need to avoid fetching some ports-categories it
is better to use a refuse file instead.
Personally I stopped doing even that some time ago, since some make
targets require a complete ports tree.
Unless you are seriously short on diskspace I would strongly recommend
using 'ports-all' to a complete ports tree.

 
 Could it be I have made such a basic mistake as to not cvsup'ed a vital
 dependedcy?! I kind of figured the newly cvsup'ed port of cvsup would have
 included a new example file of ports-supfile if that had been the problem.

It does seem as if your ports-supfile is at fault, yes.

 
 One should never *expect* a computer to do something I guess.
 
 Would something strange happen now if I added a line for
 'ports-accessability' in my ports-supfile and tried to cvsup again?

Probably not.

 
 I guess I *really* should do a pkgdb -Uu then?

-- 
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

On Friday 09 April 2004 12:34 pm, Andreas Davour wrote:
 On Fri, 9 Apr 2004, Martin Hudec wrote:
  Hi Andreas,
 
  don't you really have atk in /usr/ports/accessibility/atk
  directory?

 No.

  Perhaps look into ports-supfile.. do you have there ports-all
  enabled?

 No, I have it commented out, since I left all the individual ports
 collections in there instead, except for arabic, hebrew and some
 other exotic languages.

 Could it be I have made such a basic mistake as to not cvsup'ed a
 vital dependedcy?! I kind of figured the newly cvsup'ed port of cvsup
 would have included a new example file of ports-supfile if that had
 been the problem.

 One should never *expect* a computer to do something I guess.

 Would something strange happen now if I added a line for
 'ports-accessability' in my ports-supfile and tried to cvsup again?

 I guess I *really* should do a pkgdb -Uu then?

You have to remember the INDEX is created by make and when you leave 
items out, things can go to hell very quickly. If you want an real 
INDEX, you cvsup ports-all and don't refuse anymore than ports/INDEX.

You never know when a new dependancy has been added that depends on 
something you don't think is important. Ports-all keeps you on top of 
it.

Kent

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

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-09 Thread Lowell Gilbert

Andreas Davour [EMAIL PROTECTED] writes:

 That sounds like an important port. I don't understand why I wasn't
 getting it when I cvsup'ed then. Is there a line the the ports-supfile
 which should read 'ports-accessibility'? Maybe I should add it and cvsup
 again.

There probably wasn't such a category when you created your supfile,
but there is now.  For the complete list, see
/usr/share/examples/cvsup/ports-supfile on a recently updated system
(or check cvsweb).  

I find it easier to to use the ports-all category, and then use a
refuse file for the categories I *don't* want.  That way new
categories are added by default, rather than left out by default.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-09 Thread Kevin D. Kinsey, DaleCo, S.P.

Andreas Davour wrote:

On Fri, 9 Apr 2004, Martin Hudec wrote:

 

Could it be I have made such a basic mistake as to not cvsup'ed a vital
dependedcy?! I kind of figured the newly cvsup'ed port of cvsup would have
included a new example file of ports-supfile if that had been the problem.
One should never *expect* a computer to do something I guess.

Would something strange happen now if I added a line for
'ports-accessability' in my ports-supfile and tried to cvsup again?
 

Your supfile must predate 1/24/2004, when the accessibility
category was added.  See:
http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/cvsup/ports-supfile

If you've updated your source tree, a new copy should be in
/usr/src/share/examples/cvsup/.  If you've done a recent installworld
then it'd also be in /usr/share/examples/cvsup/.  Lastly, but not leastly,
you could grab the latest version from:
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/share/examples/cvsup/ports-supfile?rev=1.31content-type=text/plain

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

Re: Portupgrade problem

2004-04-09 Thread Matthew Seaman

On Fri, Apr 09, 2004 at 08:55:04PM +0200, Andreas Davour wrote:

 ** Listing the failed packages (*:skipped / !:failed)
 ! accessibility/atk (atk-1.4.1_1)   (port directory error)
 
 And it is correct in that there *is* no accessibility/atk port in my new
 cvsup'ed ports tree. But why is it then telling me it needs it!?

You need to cvsup(1) again -- the accessibility/atk port is definitely
in the tree now:

% ls -la accessibility/atk/
total 11
drwxr-xr-x   3 root  wheel   512 Apr  5 09:49 ./
drwxr-xr-x  12 root  wheel   512 Apr  2 09:58 ../
-rw-r--r--   1 root  wheel   776 Apr  5 09:49 Makefile
-rw-r--r--   1 root  wheel   107 Apr  5 09:49 distinfo
drwxr-xr-x   2 root  wheel   512 Apr  5 09:49 files/
-rw-r--r--   1 root  wheel   252 Apr  5 09:49 pkg-descr
-rw-r--r--   1 root  wheel  4202 Apr  5 09:49 pkg-plist

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature

Re: Portupgrade problem

2004-04-09 Thread Robert Huff


Andreas Davour writes:

  Well, I started out with a clean 5.2-RELEASE and did cvsup 4 days
  ago. I don't remember seeing glib being upgraded, but I guess I
  could always try to '-rf glib' if it is a problem.

And on that day, your karma really sucked.
GNOME-of-the-myriad-compoments-which-are-used-by-non-GNOME-things
had a red flag day upgrade (2.4 - 2.6) right around then.  To
unbreak a whole bunch of ports, one had to do the whole GNOME
rebuild.  (Which, though time sunsuming,  was surprisingly painless
for something of that size.)


Robert Huff


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

Re: Portupgrade problem

2004-04-09 Thread Gary Kline

On Fri, Apr 09, 2004 at 09:14:07PM +0200, Andreas Davour wrote:
 On Fri, 9 Apr 2004, Andrew L. Gould wrote:
 
  On Friday 09 April 2004 01:55 pm, Andreas Davour wrote:
 [snip]
   If anyone can shed some light on those matters, then I'm all ears. I can't
   get a new version of Firefox to compile without atk so I'm very interested
   in getting this to work.
  
   I have run 'pkgdb -F' and tried to remove the dependecy, but have not
   succeeded. I'm not even sure it would be wise to do it...
 
  Did you remember to execute 'pkgdb -Uu' after cvsup and before portupgrade?
 
 So be quite frank, I have no idea! I think I followed all instructions
 quite litterally. But portupgrade was mentioned in the handbook and the
 cookbook examples I found on the web differed somewhat. I no longer
 remembered if I did a 'pkgdb -Uu' or not.
 
 I there any telltale signs showing in the narrative in my first post that
 indicates I forgot it? Is it recommendable I run it now then?
 
 /andreas


If I can offer a practical tip re cvsu'ing and running 'pkgdb
-Uu', why not script it and run it out of cron?  That's how I
make sure tht my ports tree is neat nd clean.

When I do a portupgrade, my script runs pkgdb -F as a first
steps.  ...Just my dime's worth.

cheers!

gary


-- 
   Gary Kline [EMAIL PROTECTED]   www.thought.org Public service Unix

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

Re: Portupgrade problem

On Fri, 9 Apr 2004, Gary Kline wrote:

   If I can offer a practical tip re cvsu'ing and running 'pkgdb
   -Uu', why not script it and run it out of cron?  That's how I
   make sure tht my ports tree is neat nd clean.

Well, when I have succeeded in doing a portupgrade by hand I think that
might be an option. I must feel confident that it works before I dare
script it by cron.

One thing confuses me, though. I refers to 'pkgdb -Uu', but the man page
for that program don't mention a -U flag. There is another program called
'portsdb' that have both a -u and a -U flag. Which one am I supposed to
use. Both?

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

Re: Portupgrade problem

On Friday 09 April 2004 01:00 pm, Gary Kline wrote:
 On Fri, Apr 09, 2004 at 09:14:07PM +0200, Andreas Davour wrote:
  On Fri, 9 Apr 2004, Andrew L. Gould wrote:
   On Friday 09 April 2004 01:55 pm, Andreas Davour wrote:
 
  [snip]
 
If anyone can shed some light on those matters, then I'm all
ears. I can't get a new version of Firefox to compile without
atk so I'm very interested in getting this to work.
   
I have run 'pkgdb -F' and tried to remove the dependecy, but
have not succeeded. I'm not even sure it would be wise to do
it...
  
   Did you remember to execute 'pkgdb -Uu' after cvsup and before
   portupgrade?
 
  So be quite frank, I have no idea! I think I followed all
  instructions quite litterally. But portupgrade was mentioned in the
  handbook and the cookbook examples I found on the web differed
  somewhat. I no longer remembered if I did a 'pkgdb -Uu' or not.
 
  I there any telltale signs showing in the narrative in my first
  post that indicates I forgot it? Is it recommendable I run it now
  then?
 
  /andreas

   If I can offer a practical tip re cvsu'ing and running 'pkgdb
   -Uu', why not script it and run it out of cron?  That's how I
   make sure tht my ports tree is neat nd clean.

I run a cvsup of ports-all on a machine I usually use for testing. If 
something breaks down, I have the other machines to recover it from. I 
log everything and convert it into html using Ben Smithurst's cvsuplog. 
Then, I upade my INDEX[-5] and INDEX.db; however, before I build the 
new INDEX, I convert the current INDEX into a bzip2'ed file and keep 3 
backups. A major disaster building INDEX is easily overcome by 
unzipping one of the backups and the appropriate INDEX.


   When I do a portupgrade, my script runs pkgdb -F as a first
   steps.  ...Just my dime's worth.


My dimes worth is that I won't run anything in a cronjob that may 
require an answer from me. I also don't run pkgdb -F until portupgrade 
tells me to do that. Since it updates the information when it is doing 
upgrades, you only need to do it when it really has to be done.

Kent


-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

On Friday 09 April 2004 01:08 pm, Andreas Davour wrote:
 On Fri, 9 Apr 2004, Gary Kline wrote:
  If I can offer a practical tip re cvsu'ing and running 'pkgdb
  -Uu', why not script it and run it out of cron?  That's how I
  make sure tht my ports tree is neat nd clean.

 Well, when I have succeeded in doing a portupgrade by hand I think
 that might be an option. I must feel confident that it works before I
 dare script it by cron.

 One thing confuses me, though. I refers to 'pkgdb -Uu', but the man
 page for that program don't mention a -U flag. There is another
 program called 'portsdb' that have both a -u and a -U flag. Which one
 am I supposed to use. Both?


You figured out the right one. I frequently mix the 2 up but only one 
has the -uU option :). I use make index instead of portsdb -u but 
portsdb now uses make index to build INDEX[-5]. So my way isn't 
different any more.

I also forgot to add that I use a cronjob to do the cvsup but I do it 
twice a day.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

On Friday 09 April 2004 01:31 pm, Kent Stewart wrote:
 On Friday 09 April 2004 01:08 pm, Andreas Davour wrote:
  On Fri, 9 Apr 2004, Gary Kline wrote:
 If I can offer a practical tip re cvsu'ing and running 'pkgdb
 -Uu', why not script it and run it out of cron?  That's how I
 make sure tht my ports tree is neat nd clean.
 
  Well, when I have succeeded in doing a portupgrade by hand I think
  that might be an option. I must feel confident that it works before
  I dare script it by cron.
 
  One thing confuses me, though. I refers to 'pkgdb -Uu', but the man
  page for that program don't mention a -U flag. There is another
  program called 'portsdb' that have both a -u and a -U flag. Which
  one am I supposed to use. Both?

 You figured out the right one. I frequently mix the 2 up but only one
 has the -uU option :). I use make index instead of portsdb -u but
 portsdb now uses make index to build INDEX[-5]. So my way isn't
 different any more.

One more correction. It is portsdb -U to build the INDEX. I do use 
portsdb -u to build INDEX.db.

Kent

 I also forgot to add that I use a cronjob to do the cvsup but I do it
 twice a day.

 Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Portupgrade problem

2004-04-09 Thread Gary Kline

On Fri, Apr 09, 2004 at 01:19:47PM -0700, Kent Stewart wrote:
 On Friday 09 April 2004 01:00 pm, Gary Kline wrote:
  On Fri, Apr 09, 2004 at 09:14:07PM +0200, Andreas Davour wrote:
   On Fri, 9 Apr 2004, Andrew L. Gould wrote:
On Friday 09 April 2004 01:55 pm, Andreas Davour wrote:
  
   [snip]
  
 
 I run a cvsup of ports-all on a machine I usually use for testing. If 
 something breaks down, I have the other machines to recover it from. I 
 log everything and convert it into html using Ben Smithurst's cvsuplog. 
 Then, I upade my INDEX[-5] and INDEX.db; however, before I build the 
 new INDEX, I convert the current INDEX into a bzip2'ed file and keep 3 
 backups. A major disaster building INDEX is easily overcome by 
 unzipping one of the backups and the appropriate INDEX.
 

(Wisdom personified)

 
  When I do a portupgrade, my script runs pkgdb -F as a first
  steps.  ...Just my dime's worth.
 
 
 My dimes worth is that I won't run anything in a cronjob that may 
 require an answer from me. I also don't run pkgdb -F until portupgrade 
 tells me to do that. Since it updates the information when it is doing 
 upgrades, you only need to do it when it really has to be done.
 

To clear things up a bit, my upgrade scripts are not cron'd.
--Experience is a solid teacher.--  One script does basically
a portupgrade -ia, the other simply a -a; either way I have to
sit thru the pkgdb -F. The rest of the scripts do 
portclean and leave a log of what needs to be upgraded.

gary


-- 
   Gary Kline [EMAIL PROTECTED]   www.thought.org Public service Unix

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

Re: Portupgrade problem