[solved] Re: Ghostscript8 portupgrade failure
On Sun, Dec 20, 2009 at 08:29:06PM -0700, Warren Block wrote: Don't know. I'd guess not cleaning the failed build out of the work dir with 'make clean', but portupgrade should do that automatically. It's built now. I just did: % cd /usr/ports/print/ghostscript8 % make deinstall % make distclean % make rmconfig Then, rebooted (not sure if that has had anything to do with the success of the build or not) Then: % cd /usr/ports/print/ghostscript8 % make install clean and that did it. Jamie pgpEg3ccUqBO0.pgp Description: PGP signature
Ghostscript8 portupgrade failure
Hi I've now got a different problem when trying to portupgrade ghostscript8 and the build fails with an error: (new compiler error). I had a problem with ghostscript the last time it need upgrading. I think then I removed it from the system and just built the new port. This time, I have a number of other ports that depend on it and pkg_delete ghostscript8 won't remove it because of the dependent ports. If I `pkg_delete -f` it and then rebuilt it from the ports tree will this cause problems with my system? Jamie pgpITnNZTme6m.pgp Description: PGP signature
Re: Ghostscript8 portupgrade failure
On Sun, 20 Dec 2009, Jamie Griffin wrote: I've now got a different problem when trying to portupgrade ghostscript8 and the build fails with an error: (new compiler error). I had a problem with ghostscript the last time it need upgrading. I think then I removed it from the system and just built the new port. This time, I have a number of other ports that depend on it and pkg_delete ghostscript8 won't remove it because of the dependent ports. The ghostscript8 problem has been fixed, so update your ports tree again and portupgrade will work. If I `pkg_delete -f` it and then rebuilt it from the ports tree will this cause problems with my system? Not necessary in this case, but if needed you can find out what portupgrade would have done by using the -n (noexecute) flag: portupgrade -nr ghostscript8 (On one system this showed portupgrade was only going to rebuild ghostscript anyway.) Afterwards you can manually rebuild those dependent ports in that order. For at least the problem port, do a plain 'make' first to be sure it can download and build before you get rid of the installed version. Once that completes successfully, do a 'make deinstall install' to delete the previous version and install the new one. The brute-force version of all this is portupgrade -rf ghostscript8 Depending on the port, that can force unecessary rebuilding of a lot of stuff. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ghostscript8 portupgrade failure
On Sun, Dec 20, 2009 at 03:03:09PM -0700, Warren Block wrote: The ghostscript8 problem has been fixed, so update your ports tree again and portupgrade will work. Hi Warren, thanks for the information. I just updated my ports tree and tried to build it again using make first, then portupgrade and both still fail with the same error. This link will show two screenshots i've taken which might help to show any other possible problems. http://www.koderize.com/kodedump/kodedump.html I've not yet tried pkg_delete -rf yet. I'd like to avoid having to rebuild loads of other ports if i can. Jamie pgpOcHTUGNCMr.pgp Description: PGP signature
Re: Ghostscript8 portupgrade failure
On Sun, 20 Dec 2009, Jamie Griffin wrote: On Sun, Dec 20, 2009 at 03:03:09PM -0700, Warren Block wrote: The ghostscript8 problem has been fixed, so update your ports tree again and portupgrade will work. Hi Warren, thanks for the information. I just updated my ports tree and tried to build it again using make first, then portupgrade and both still fail with the same error. This link will show two screenshots i've taken which might help to show any other possible problems. http://www.koderize.com/kodedump/kodedump.html Don't know. I'd guess not cleaning the failed build out of the work dir with 'make clean', but portupgrade should do that automatically. I've not yet tried pkg_delete -rf yet. I'd like to avoid having to rebuild loads of other ports if i can. portupgrade, not pkg_delete. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Wed, Dec 16, 2009 at 7:24 PM, Mark Linimon lini...@lonesome.com wrote: On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote: The maintainer, ruby@, is aware of this; a check of the PR database shows multiple open PRs, none critical but many serious going back six months and more. As an aside, the Severity and Priority fields have been so often abused as to have become meaningless. Although I still try to groom the db for critical ones, and thus try to get those some attention, I really don't think the committers pay much attention. (In general I think those should be reserved for data corruption and security.) The longer-term solution is to remove those as user-settable fields. This hard to understand given portupgrade is the recommended upgrade tool. Once the individual who was working on it gave it up to the mailing list, it became one of those everyone is responsible so no one is responsible problems. I don't have a recommended fix for this. Having said that, I have a ports tree as of a month ago and portupgrade was working ok for me. I don't have the cycles to go figure out where it fails to be able to fix it, sorry. mcl Thanks to everyone for the tips. I downgraded to portupgrade-2.4.6_2,2, and am able to update my ports/packages again. I had seen others commenting on portupgrade being broken in the past, but the ruby errors made me wonder if it was actually a ruby problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
portupgrade failure
Hello all,
I've been having this problem for a couple of months now, but I just
recently decided to try to fix it. I'm running FreeBSD 6.4, and if I
try to use portupgrade to upgrade something, I get an error (seems to
be the same for other ports):
# portupgrade -R squid
[Gathering depends for www/squid30 ./usr/local/sbin/portupgrade:878:in
`get_all_depends': private method `scan' called for #Set: {}
(NoMethodError)
from /usr/local/sbin/portupgrade:871:in `get_all_depends'
from /usr/local/lib/ruby/1.8/set.rb:195:in `each'
from /usr/local/lib/ruby/1.8/set.rb:195:in `each_key'
from /usr/local/lib/ruby/1.8/set.rb:195:in `each'
from /usr/local/sbin/portupgrade:870:in `get_all_depends'
from /usr/local/sbin/portupgrade:633:in `main'
from /usr/local/sbin/portupgrade:607:in `each'
from /usr/local/sbin/portupgrade:607:in `main'
from /usr/local/sbin/portupgrade:582:in `catch'
from /usr/local/sbin/portupgrade:582:in `main'
from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `call'
from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `parse_in_order'
from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `catch'
from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `parse_in_order'
from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `catch'
from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order'
from /usr/local/lib/ruby/1.8/optparse.rb:1248:in `order!'
from /usr/local/lib/ruby/1.8/optparse.rb:1241:in `order'
from /usr/local/sbin/portupgrade:559:in `main'
from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize'
from /usr/local/sbin/portupgrade:231:in `new'
from /usr/local/sbin/portupgrade:231:in `main'
from /usr/local/sbin/portupgrade:2213
The only other symptoms I can identify right now are related to the
following entries in my crontab:
0 2 * * 6 /usr/local/sbin/portsclean -DD
0 2 * * 5 /usr/local/sbin/portsclean -C
The e-mailed results simply say env: ruby: No such file or
directory. However, these commands seem to run fine from an
interactive shell (while logged in).
I also receive the same message at the end of the output for
/usr/sbin/portsnap cron update /usr/local/sbin/portsdb -u
/dev/null run from cron:
Removing old files and directories... done.
Extracting new files:
/usr/ports/MOVED
/usr/ports/Mk/bsd.sites.mk
/usr/ports/UPDATING
...lines deleted...
/usr/ports/x11/9menu/
/usr/ports/x11/evilvte/
/usr/ports/x11/nvidia-driver/
Building new INDEX files... done.
env: ruby: No such file or directory
Any help would be greatly appreciated.
Thanks,
Kevin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: #!/usr/bin/env ruby That should find and run ruby. Your /etc/crontab should have these lines: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin I also receive the same message at the end of the output for /usr/sbin/portsnap cron update /usr/local/sbin/portsdb -u /dev/null run from cron: portsdb is another ruby script. Same deal; cron running env can't find ruby. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
Hi, On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: Interestingly, my homemade port rebuild script is recently broken with similar symptoms, sans the dependencies on ruby. It's a very simple, low-level for i in `cat list` type script which recently has begun to fail repeatedly on gettext and autoconf dependencies on multiple machines, when I specifically have them set to be upon the first ports to build. More probably unrelated, but I thought I'd throw this out there just in case. Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
Glen Barber wrote: Hi, On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: Interestingly, my homemade port rebuild script is recently broken with similar symptoms, sans the dependencies on ruby. It's a very simple, low-level for i in `cat list` type script which recently has begun to fail repeatedly on gettext and autoconf dependencies on multiple machines, when I specifically have them set to be upon the first ports to build. More probably unrelated, but I thought I'd throw this out there just in case. Regards, I don't know if it's of any help, but I had a *somewhat* similar experience, I don't know if this will help, but I'll give it to you for what it's worth: I found in my environment, I had REINPLACE_CMD defined (seemed to be a good value), so (in my shell, tcsh) I removed the REINPLACE_CMD setting with unsetenv, and the problem disappeared. Use either env or printenv to scan your environment for anything to do with sed (as REINPLACE_CMD does) and try removing it. Oh, BTW, I can't seem to get the -l logfile option to portupgrade to work, any help on that would also be appreciated. I didn't use -L at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Wed, 16 Dec 2009, Warren Block wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: #!/usr/bin/env ruby That should find and run ruby. Your /etc/crontab should have these lines: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin And now that I tried a test with these manual paths, the same thing happens: # setenv PATH /etc:/bin:/sbin:/usr/bin:/usr/sbin # env ruby env: ruby: No such file or directory Doh. ruby and ruby18 are in /usr/local/bin. So it's working as designed. A reasonable way to fix this is to add :/usr/local/bin to the crontab path, but that may not be the right way to fix it. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Sat, Oct 4, 2008 at 5:02 AM, Patrick Lamaizière [EMAIL PROTECTED] wrote: Portupgrade is often confused with his database on upgrade. Delete /var/db/pkg/pkgdb.db and retry. May be you have to delete /usr/ports/INDEX-6.db too. Hmm. This does not inspire confidence in the tool. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On Mon, Oct 13, 2008 at 02:04:02PM -0400, Michael P. Soulier wrote: On Sat, Oct 4, 2008 at 5:02 AM, Patrick Lamaizière [EMAIL PROTECTED] wrote: Portupgrade is often confused with his database on upgrade. Delete /var/db/pkg/pkgdb.db and retry. May be you have to delete /usr/ports/INDEX-6.db too. Hmm. This does not inspire confidence in the tool. So don't use it? :-) There are alternatives like portmaster. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: So don't use it? :-) There are alternatives like portmaster. I suppose I prefer a single, reliable, supported tool for the system. portupgrade seems to be pushed the most in all of the documentation that I can find, so I went with it. Maybe I should dig into its guts and find out how it works. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On Mon, Oct 13, 2008 at 02:08:54PM -0400, Michael P. Soulier wrote: On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: So don't use it? :-) There are alternatives like portmaster. I suppose I prefer a single, reliable, supported tool for the system. portupgrade seems to be pushed the most in all of the documentation Yes, and I've always considered that a big disappointment, since portupgrade is written in Ruby (thus requiring knowledge of a separate language rather than C), and has its own dependency database (due to supposed limits of the standard /var/db/pkg database). When portupgrade breaks -- and believe it, it happens quite often, as a brief review of the freebsd-ports mailing list will show you -- it's a nightmare. I have to ask you: is this really worth it to you? You could use portmaster, which is a /bin/sh script that does not behave this way, and is maintained by a member of the FreeBSD developer community (Doug Barton). This would be a single reliable tool that does not rely on external dependencies. I strongly urge you to consider it. Do I use it? No, because I'm one of those I do everything by hand administrators who does things like rm -fr /usr/local ; pkg_delete -af and so on. But if I wanted a tool that managed things for me, I would very likely go with portmaster. Please note that I often get flamed for flaming portupgrade, and I would not be surprised if that occurred as a result of this mail either. I strongly advocate using whatever tool gets the job done (and if that's portupgrade, great!), but I see way too many portupgrade-related support posts on the freebsd-ports mailing list for me to ever consider it. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
Michael P. Soulier [EMAIL PROTECTED] wrote: On Mon, Oct 13, 2008 at 2:05 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: So don't use it? :-) There are alternatives like portmaster. I suppose I prefer a single, reliable, supported tool for the system. portupgrade seems to be pushed the most in all of the documentation that I can find, so I went with it. Maybe I should dig into its guts and find out how it works. Try portmanager; it has worked well for me. -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
Le Fri, 3 Oct 2008 13:26:33 -0400, Michael P. Soulier [EMAIL PROTECTED] a écrit : So, I recently upgraded from 5.5 to 6.3, and as such, ran a portupgrade -fa to rebuild my ports against 6.3. I just noticed this. === Cleaning for ruby-1.8.6.287,1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:dbm_hash in /var/db/pkg ... Any idea what would cause this? Portupgrade is often confused with his database on upgrade. Delete /var/db/pkg/pkgdb.db and retry. May be you have to delete /usr/ports/INDEX-6.db too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade failure
So, I recently upgraded from 5.5 to 6.3, and as such, ran a portupgrade -fa to rebuild my ports against 6.3. I just noticed this. === Cleaning for ruby-1.8.6.287,1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:dbm_hash in /var/db/pkg ... Inappropriate file type or format - /var/db/pkg/pkgdb; rebuild needed] [Rebuilding the pkgdb format:dbm_hash in /var/db/pkg ... - 366 packages found (-0 +366) 100200300.. done] /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:215:in `origin': Failed `Inappropriate file type or format' (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:205:in `origin' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:245:in `config_include?' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:215:in `config_ignore_moved?' from /usr/local/sbin/portupgrade:937:in `do_upgrade' from /usr/local/sbin/portupgrade:815:in `main' from /usr/local/sbin/portupgrade:811:in `each' from /usr/local/sbin/portupgrade:811:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2208 Any idea what would cause this? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein signature.asc Description: Digital signature
OpenEXR portupgrade failure
Hi, I'm trying to portupgrade my system and the only ones left are kde and OpenEXR. Apparently OpenEXR needs to be done as dependency for kde. But my portupgrade -R OpenEXR fail. Following is the error message, how can I solve this? /usr/bin/ld: warning: libIlmThread.so.4, needed by /usr/local/lib/libIlmImf.so, may conflict with libIlmThread.so.6 generalInterfaceExamples.o(.text+0x5da): In function `writeGZ2(char const*, half const*, float const*, int, int, Imath::BoxImath::Vec2int const)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' generalInterfaceExamples.o(.text+0x604): In function `writeGZ2(char const*, half const*, float const*, int, int, Imath::BoxImath::Vec2int const)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' generalInterfaceExamples.o(.text+0x797): In function `writeGZ1(char const*, half const*, float const*, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' generalInterfaceExamples.o(.text+0x7c1): In function `writeGZ1(char const*, half const*, float const*, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' generalInterfaceTiledExamples.o(.text+0x28c): In function `writeTiled1(char const*, Imf::Array2DGZ, int, int, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' generalInterfaceTiledExamples.o(.text+0x2b6): more undefined references to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' follow gmake[1]: *** [imfexamples] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/OpenEXR/work/openexr-1.6.0/IlmImfExamples' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/graphics/OpenEXR. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.1076.1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=OpenEXR-1.4.0 UPGRADE_PORT_VER=1.4.0 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! graphics/OpenEXR (OpenEXR-1.4.0) (linker error) --- Packages processed: 0 done, 1 ignored, 0 skipped and 1 failed Many thanks, Alain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenEXR portupgrade failure
On Saturday 17 November 2007 13:55:02 Alain G. Fabry wrote: Hi, I'm trying to portupgrade my system and the only ones left are kde and OpenEXR. Apparently OpenEXR needs to be done as dependency for kde. But my portupgrade -R OpenEXR fail. Following is the error message, how can I solve this? /usr/bin/ld: warning: libIlmThread.so.4, needed by /usr/local/lib/libIlmImf.so, may conflict with libIlmThread.so.6 generalInterfaceExamples.o(.text+0x5da): In function `writeGZ2(char const*, half const*, float const*, int, int, Imath::BoxImath::Vec2int const)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, : bool)' generalInterfaceExamples.o(.text+0x604): In function `writeGZ2(char const*, half const*, float const*, int, int, Imath::BoxImath::Vec2int const)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, : bool)' generalInterfaceExamples.o(.text+0x797): In function `writeGZ1(char const*, half const*, float const*, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, : bool)' generalInterfaceExamples.o(.text+0x7c1): In function `writeGZ1(char const*, half const*, float const*, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, : bool)' generalInterfaceTiledExamples.o(.text+0x28c): In function `writeTiled1(char const*, Imf::Array2DGZ, int, int, int, int)': : undefined reference to `Imf::Channel::Channel(Imf::PixelType, int, int, : bool)' generalInterfaceTiledExamples.o(.text+0x2b6): more undefined references to `Imf::Channel::Channel(Imf::PixelType, int, int, bool)' follow gmake[1]: *** [imfexamples] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/OpenEXR/work/openexr-1.6.0/IlmImfExamples' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/graphics/OpenEXR. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.1076.1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=OpenEXR-1.4.0 UPGRADE_PORT_VER=1.4.0 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! graphics/OpenEXR (OpenEXR-1.4.0) (linker error) --- Packages processed: 0 done, 1 ignored, 0 skipped and 1 failed Many thanks, Alain Read 20071008 entry in /usr/ports/UPDATING. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure [solved]
Ok, I found a solution. I had the same problem as described below. I am using portsnap so : # portsnap fetch # portsnap update # cd /usr/ports/sysutils/portupgrade # make deinstall; make install clean This will install version portupgrade-2.2.2_2,2 which corrects the bug. Sincerly yours. Le 1 févr. 07 à 07:37, FreeBSD MailingLists a écrit : I am having the same problem. I have tried the make fetchindex approach but it doesn't solve it for me. you mentioned something about /usr/ports/UPDATING, but was unable to find a relevant entry. can you please tell me the entry date that helped you with this problem? Thank you, Tomoki Taniguchi [EMAIL PROTECTED] ~]$portupgrade -rRviy f-prot clamav mail/mailscanner --- Session started at: Thu, 01 Feb 2007 15:04:14 +0900 [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 173 packages found (-1 +1) (...). done] ** No such installed package: mail/mailscanner [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 16413 port entries found . 1000.2000.3000.4000.5000.6000. 7000.8000.9000.1.11000.120 00.13000.14000.15000.16000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Thu, 01 Feb 2007 15:04:33 +0900 (consumed 00:00:18) /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:702:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:890:in `all_depends_list' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:809:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:823:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:827:in `sort_build!' from /usr/local/sbin/portupgrade:721:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ P Please consider your environmental responsibility before printing this e-mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
I am having the same problem. I have tried the make fetchindex approach but it doesn't solve it for me. you mentioned something about /usr/ports/UPDATING, but was unable to find a relevant entry. can you please tell me the entry date that helped you with this problem? Thank you, Tomoki Taniguchi [EMAIL PROTECTED] ~]$portupgrade -rRviy f-prot clamav mail/mailscanner --- Session started at: Thu, 01 Feb 2007 15:04:14 +0900 [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 173 packages found (-1 +1) (...). done] ** No such installed package: mail/mailscanner [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 16413 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Thu, 01 Feb 2007 15:04:33 +0900 (consumed 00:00:18) /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:702:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:890:in `all_depends_list' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:809:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:823:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:827:in `sort_build!' from /usr/local/sbin/portupgrade:721:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firefox portupgrade failure to compile, requested error listings
hello list! 5. Re: freebsd-questions Digest, Vol 110, Issue 20 (David Armour) Message: 5 WAS: * Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade84798.26 make From: Vizion [EMAIL PROTECTED] What were the lines before: gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' ... unfortunately, i only clipped the lines i did, trying to keep my message as short as possible. doh! i'm not sure where to locate the as i was waking up this morning, the thought that i could just as easily re-run the portupgrade firefox command that produced the error occurred... so i was delighted to see garrett cooper's recommendation to do so, further along in this digest. (Message 15. thanks garrett!) the (several) lines before 'gmake[1]: In file included from nsDNSService2.h:40, from nsDNSService2.cpp:38: nsHostResolver.h:95: error: ISO C++ forbids declaration of `PRAddrInfo' with no type nsHostResolver.h:95: error: expected `;' before '*' token nsHostResolver.h: In member function `PRBool nsHostRecord::HasResult() const': nsHostResolver.h:99: error: `addr_info' undeclared (first use this function) nsHostResolver.h:99: error: (Each undeclared identifier is reported only once for each function it appears in.) nsHostResolver.h: At global scope: nsHostResolver.h:209: error: `PRAddrInfo' has not been declared nsHostResolver.h:209: error: ISO C++ forbids declaration of `parameter' with no type nsDNSService2.cpp: In member function `virtual nsresult nsDNSRecord::GetCanonicalName(nsACString)': nsDNSService2.cpp:95: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:96: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:96: error: `PR_GetCanonNameFromAddrInfo' undeclared (first use this function) nsDNSService2.cpp: In member function `virtual nsresult nsDNSRecord::GetNextAddr(PRUint16, PRNetAddr*)': nsDNSService2.cpp:112: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:113: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:113: error: `PR_EnumerateAddrInfo' undeclared (first use this function) nsDNSService2.cpp: In member function `PRUint16 nsDNSService::GetAFForLookup(const nsACString)': nsDNSService2.cpp:528: error: `PR_AF_UNSPEC' undeclared (first use this function) gmake[4]: *** [nsDNSService2.o] Error 1 gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk/dns/src' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk/dns' gmake[2]: *** [libs] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade40821.26 make ** Fix the problem and try again. --- Build of www/firefox ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:36) --- Upgrade of www/firefox ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:36) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - lang/perl5.8 (perl-5.8.7) - converters/libiconv (libiconv-1.9.2_1) - graphics/jpeg (jpeg-6b_3) - devel/gettext (gettext-0.14.5) - devel/pkgconfig (pkgconfig-0.17.2) - textproc/libxml2 (libxml2-2.6.20_1) - print/freetype2 (freetype2-2.1.10_1) - graphics/png (png-1.2.8_2) - devel/glib20 (glib-2.6.6) - accessibility/atk (atk-1.9.1) - graphics/tiff (tiff-3.7.3) - devel/libIDL (libIDL-0.8.6) - textproc/expat2 (expat-1.95.8_3) - x11-fonts/fontconfig (fontconfig-2.2.3,1) - x11/xorg-libraries (xorg-libraries-6.8.2) - misc/hicolor-icon-theme (hicolor-icon-theme-0.5) - devel/popt (popt-1.7) - x11-fonts/libXft (libXft-2.1.7) - devel/desktop-file-utils (desktop-file-utils-0.10_2) - misc/gnomehier (gnomehier-2.0_7) - misc/shared-mime-info (shared-mime-info-0.16_1) - x11-fonts/bitstream-vera (bitstream-vera-1.10_1) - x11-fonts/xorg-fonts-encodings (xorg-fonts-encodings-6.8.2) - x11-fonts/xorg-fonts-truetype (xorg-fonts-truetype-6.8.2) - x11-toolkits/pango (pango-1.8.2) - x11-toolkits/gtk20 (gtk-2.6.10_1) ! www/firefox (firefox-1.0.4,1) (compiler error) --- Packages processed: 0 done, 26 ignored, 0 skipped and 1 failed --- Session ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:48) HTH. apologies if i've padded out this too much. i have virtually no idea what any of the stuff that fills the screen for 13:48 minutes means. file that all those screens of garbled text goes to either. i looked in /var/log, but i couldn't see anything that looked
Re: firefox portupgrade failure to compile, requested error listings
On Tuesday 06 September 2005 00:09, Yuan Jue wrote: hello list! 5. Re: freebsd-questions Digest, Vol 110, Issue 20 (David Armour) Message: 5 WAS: * Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade84798.26 make From: Vizion [EMAIL PROTECTED] What were the lines before: gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' ... unfortunately, i only clipped the lines i did, trying to keep my message as short as possible. doh! i'm not sure where to locate the as i was waking up this morning, the thought that i could just as easily re-run the portupgrade firefox command that produced the error occurred... so i was delighted to see garrett cooper's recommendation to do so, further along in this digest. (Message 15. thanks garrett!) the (several) lines before 'gmake[1]: In file included from nsDNSService2.h:40, from nsDNSService2.cpp:38: nsHostResolver.h:95: error: ISO C++ forbids declaration of `PRAddrInfo' with no type nsHostResolver.h:95: error: expected `;' before '*' token nsHostResolver.h: In member function `PRBool nsHostRecord::HasResult() const': nsHostResolver.h:99: error: `addr_info' undeclared (first use this function) nsHostResolver.h:99: error: (Each undeclared identifier is reported only once for each function it appears in.) nsHostResolver.h: At global scope: nsHostResolver.h:209: error: `PRAddrInfo' has not been declared nsHostResolver.h:209: error: ISO C++ forbids declaration of `parameter' with no type nsDNSService2.cpp: In member function `virtual nsresult nsDNSRecord::GetCanonicalName(nsACString)': nsDNSService2.cpp:95: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:96: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:96: error: `PR_GetCanonNameFromAddrInfo' undeclared (first use this function) nsDNSService2.cpp: In member function `virtual nsresult nsDNSRecord::GetNextAddr(PRUint16, PRNetAddr*)': nsDNSService2.cpp:112: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:113: error: 'class nsDerivedSafensHostRecord' has no member named 'addr_info' nsDNSService2.cpp:113: error: `PR_EnumerateAddrInfo' undeclared (first use this function) nsDNSService2.cpp: In member function `PRUint16 nsDNSService::GetAFForLookup(const nsACString)': nsDNSService2.cpp:528: error: `PR_AF_UNSPEC' undeclared (first use this function) gmake[4]: *** [nsDNSService2.o] Error 1 gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk/dns/src' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk/dns' gmake[2]: *** [libs] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla/netwerk' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade40821.26 make ** Fix the problem and try again. --- Build of www/firefox ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:36) --- Upgrade of www/firefox ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:36) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) - lang/perl5.8 (perl-5.8.7) - converters/libiconv (libiconv-1.9.2_1) - graphics/jpeg (jpeg-6b_3) - devel/gettext (gettext-0.14.5) - devel/pkgconfig (pkgconfig-0.17.2) - textproc/libxml2 (libxml2-2.6.20_1) - print/freetype2 (freetype2-2.1.10_1) - graphics/png (png-1.2.8_2) - devel/glib20 (glib-2.6.6) - accessibility/atk (atk-1.9.1) - graphics/tiff (tiff-3.7.3) - devel/libIDL (libIDL-0.8.6) - textproc/expat2 (expat-1.95.8_3) - x11-fonts/fontconfig (fontconfig-2.2.3,1) - x11/xorg-libraries (xorg-libraries-6.8.2) - misc/hicolor-icon-theme (hicolor-icon-theme-0.5) - devel/popt (popt-1.7) - x11-fonts/libXft (libXft-2.1.7) - devel/desktop-file-utils (desktop-file-utils-0.10_2) - misc/gnomehier (gnomehier-2.0_7) - misc/shared-mime-info (shared-mime-info-0.16_1) - x11-fonts/bitstream-vera (bitstream-vera-1.10_1) - x11-fonts/xorg-fonts-encodings (xorg-fonts-encodings-6.8.2) - x11-fonts/xorg-fonts-truetype (xorg-fonts-truetype-6.8.2) - x11-toolkits/pango (pango-1.8.2) - x11-toolkits/gtk20 (gtk-2.6.10_1) ! www/firefox (firefox-1.0.4,1) (compiler error) --- Packages processed: 0 done, 26 ignored, 0 skipped and 1 failed --- Session ended at: Mon, 05 Sep 2005 07:59:57 -0700 (consumed 00:13:48) HTH. apologies if i've padded out this too much. i have virtually no idea what any of the stuff that fills the screen for 13:48
Re: firefox portupgrade failure RESOLVED
Message: 32 Date: Tue, 6 Sep 2005 00:34:33 +0800 From: Yuan Jue [EMAIL PROTECTED] Have you upgraded the nspr port? I have almost the same problem when I didn't upgrade it to the newest version. without your message, i wouldn't have noticed nspr needs updating on my pkg_version listing. what does it do? i'll try updating it and see what happens. so does it work now? :) + www/firefox (firefox-1.0.4,1) # thanks for your help. For your information: Netscape Portable Runtime (NSPR) provides a platform-neutral API for system level and libc like functions. The API is used in the Mozilla thanks for the explanation. i can see why firefox might need that. i'm less clear why the port doesn't include it as a matter of course. my newbieness tends to need all the help i can get, if that makes any sense. regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade failure
Hi, I tried to upgrade firefox with portupgrade, but it fails with the following error: [EMAIL PROTECTED]# portupgrade firefox Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to generate INDEX! index generation error /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:482:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:634:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:822:in `all_depends_list' 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 Does anyone know what the problem is? Thanks, Marco -- U: There's a U -- a Unicorn! Run right up and rub its horn. Look at all those points you're losing! UMBER HULKS are so confusing. -- The Roguelet's ABC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On Sat, 08 Jan 2005 18:29:51 +0100 (CET), Marco Beishuizen [EMAIL PROTECTED] wrote: Hi, I tried to upgrade firefox with portupgrade, but it fails with the following error: [EMAIL PROTECTED]# portupgrade firefox Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to generate INDEX! index generation error /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:482:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:634:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:822:in `all_depends_list' 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 Does anyone know what the problem is? You may be able to make this problem go away by doing: # cd /usr/ports # make fetchindex -- Joshua Lokken Open Source Advocate ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On Sat, Jan 08, 2005 at 06:29:51PM +0100, Marco Beishuizen wrote: Hi, I tried to upgrade firefox with portupgrade, but it fails with the following error: [EMAIL PROTECTED]# portupgrade firefox Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to generate INDEX! index generation error /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:482:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:634:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:822:in `all_depends_list' 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 Does anyone know what the problem is? /usr/ports/UPDATING Kris pgpEcB7lsQK6G.pgp Description: PGP signature
Re: portupgrade failure
Marco Beishuizen wrote: Hi, I tried to upgrade firefox with portupgrade, but it fails with the following error: [EMAIL PROTECTED]# portupgrade firefox Updating the ports index ... Generating INDEX.tmp - please wait..^Cfailed to generate INDEX! index generation error /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:482:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:634:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:822:in `all_depends_list' 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 Does anyone know what the problem is? Thanks, Marco I had that problem and deleted and reinstalled ruby cured it for me. Sean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade failure
On stardate Sat, 8 Jan 2005, the wise Joshua Lokken entered: You may be able to make this problem go away by doing: # cd /usr/ports # make fetchindex Yes, this did the trick. I should have read /usr/ports/UPDATING though, because the answer was in it... Thanks for the answers. Marco -- Minnie Mouse is a slow maze learner. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Portupgrade failure: / filesystem full.... any suggestions short of full-scale re-install?
Hello, I'm not sure what's next: hedgehogs falling from the skies, perhaps? Mostly, I know I'm flailing around in the newbie waters, an otherwise straightforward 5.2.1 install (single user, desktop) gone horribly, horribly wrong. The story so far... I got through most of the sysinstall program without too many surprises. It's a new machine, 40G HD. Loosely following Mr. Lehey's configuration suggestions in Complete FreeBSD, / got 4G, swap 2G, and /home the rest. Among other things, I downloaded and installed the instant-workstation 1.0.3 port, in part because a presumably earlier version had worked fine last fall when I installed it on my wife's dual boot machine.[1] This time, although XFree86 -configure tested okay, i.e. grey screen with X in the middle, then Ctrl-Alt-Backspace to return to the CLI, I couldn't seem to configure X. I had it working a couple of times, but the mouse cursor was a 64x64 pixel barcode! Exiting seemed to cause the x-server the most trouble. The box locked up complaining primarily of unresolved symbols, although both Knoppix 3.4 and FreeSBIE's versions of x-windows work(ed) fine, booting from the CD drive. I see a note [2] suggesting the more current XFree86 4.4 version might work better with the SiS74x video card, which at that point, seemed the most likely candidate for FreeBSD incompatibility. More googling around and freebsd-questions digest traffic reading suggested cvsup and portupgrade, as a general tidying up strategy en route to updating to 4.4. [upmusic: theme from Jaws] Cvsupping seems to be chugging along for quite a while, but previous install on older machine also took the better part of a weekend, so I figure what the hell. A strong sense of fear and loathing began to develop, however, when filesystem full began in large numbers to scroll off the screen, late this past afternoon. A du -sk * showed relatively expected numbers next to most of the sub-directories, but /usr and /var showed 3 038 096 71 990 respectively! ??? /var/tmp seems to contain lots of 512K .bak files right underneath .tgz behemoths with the same name. I've seen messages suggesting deleting /tmp directories, as well as growfs, as a way to regain room to at least email log and error messages, but I'm also getting a little gunshy. Any suggestions, even starting over from scratch, would assist me greatly. Everything I've read so far suggests FreeBSD installs into _at most_ 5G, so what's going on??? If a more realistic cvsup/portupgrade manoevering room works out to 10G, maybe this message will help someone else. Thanks in advance. df (dave) armour at my real box dought calm! # not. [1] previous install, 5.0-RELEASE, admittedly in 18G, on dual-boot (Windows ME, with 10G) box. [2] The SiS driver author's site suggests XFree86 4.4.0 works more successfully with SiS74x series. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade failure: / filesystem full.... any suggestionsshort of full-scale re-install?
[EMAIL PROTECTED] wrote: Hello, I'm not sure what's next: hedgehogs falling from the skies, perhaps? Mostly, I know I'm flailing around in the newbie waters, an otherwise straightforward 5.2.1 install (single user, desktop) gone horribly, horribly wrong. The story so far... And what have you against hedgehogs? Or is it just that they might hurt if they hit you? I got through most of the sysinstall program without too many surprises. It's a new machine, 40G HD. Loosely following Mr. Lehey's configuration suggestions in Complete FreeBSD, / got 4G, swap 2G, and /home the rest. [snip rest of sad story] We love Mr. Lehey, of course, although my last attempt to get one of his books on Ebay went awry. However, I've read vinum(8) once, I think --- and found his website pretty interesting. ;-) That said, I wouldn't partition a drive in this way. Here's a report on the disks on my workstation: $df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 989M 149M 761M 16% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s1e 34G 17G 14G 56% /usr /dev/ad0s1d 989M 410M 500M 45% /var /dev/ad1s1d 180G 14G 152G 8% /backup //[EMAIL PROTECTED]/SHAREDDOCS 19G 15G 3.8G 80% /house Even allowing that the users in (/usr)/home on my system are using approximately 13GB, there's still 4GB in /usr, and another half GB in the root and /var filesystems, which in my case are seperate partitions. Most certainly in doing cvsup+buildworld+buildkernel and friends, you're going to take up space with /usr/src and /usr/obj. By installing the instant-workstation port, you're going to be filling up /usr/ports/distfiles and /usr/local. Fetch is probably holding temporary files open in either /tmp or /root, so it's not inconceivable that your / is up to its 4 GB maximum as /var, /tmp, and /usr are all in your root fs... Greg Lehey's recommendations have, AFAIK (but I'm no expert) never been the same as the ones recommended by /stand/sysinstall (and therefore the project??) However, generally there's nothing wrong with his ideas, and certainly he would know better than a peon like myself. BUT---IIRC, sometime in the last few months he was discussing this very issue on the lists, and mentioning that his thought on the subject had changed a bit (and perhaps he's changed his recommendations in a later edition?) As for what you might do ... one workaround might be to move some things like /usr/src, /usr/ports and /usr/obj to your big filesystem: $cd /usr $mv ports /home $ln -s /home/ports ports I don't think this would cause any problems, and might be a way to manage until later. I guess you could just do it that way permanently. There would be other options, too, of course... Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
