Re: Portupgrade not handling dependencies
Hi, There are few steps I may suggest to you: 1. Update CVS, i.e. use cvsup -L 2 -g 2. cd /usr/ports make fetchindex 3. portsdb -fr pkgdb -Ffv 4. portupdate -v -i -a -y If the same problem still exists there is a not so clean step to make: 1. cd multimedia/ffmpeg 2. FORCE_PKG_REGISTER=yes make install clean 3. portsdb -fr pkgdb -Ffv 4. portupdate -v -i -a -y Repeat the above for every mismatched port. I know, it is not clean, but once you fix all necessary ports - there will be no problems in the future :) Regards, Ivailo Tanusheff Deputy Head of IT Department ProCredit Bank (Bulgaria) AD Eric Sheesley eshee...@shadowlair.com Sent by: owner-freebsd-questi...@freebsd.org 08.07.2009 04:09 To b. f. bf1...@googlemail.com, freebsd-questions@FreeBSD.org cc Subject Re: Portupgrade not handling dependencies Actually, the bsdpan package is not the issue here. I was aware it wouldn't update that(no port for this perl module yet anyway). If you notice, it doesn't proceed to install ffmpeg, i force it to(highlighted by ): ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) ** %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) It should upgrade ffmpeg automatically, but doesn't and that is the issue. b. f. wrote: On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote: Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' I see. In the default /usr/local/etc/pkgtools.conf, there is a sample line (not commented out) that places any port that matches the glob bsdpan-* in HOLD_PKGS, meaning that portupgrade will refuse to handle it. Presumably this is so users can manage their own local tree of Perl ports that aren't in the regular ports tree. I don't do this, so I'm not familiar with how the two interact. But portupgrade seems to have done the right thing here: in the snippet you gave us, it ignored bsdpan-Acme-Damn and proceeded to begin building ffmpeg after updating libtheora -- the only problem seems to be that in the intermediate summary it lists ffmpeg, erroneously, as having been skipped -- but that seems to just be a cosmetic problem, because it then proceeds to start updating it. If later on it refuses to update it, then you've got a problem. In that case, you should try running pkgdb -L pkgdb -F to make sure that your pkgdb is in good shape, and then try your updates again. You might also try instead something like: portupgrade -ax bsdpan-* If that doesn't work, then you may either have to rip out your bsdpan-* ports, or just use a another tool for updating -- portmaster, for example. Or you can roll your own. b. ___ 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 ___ 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 not handling dependencies
b. f. wrote: But I have seen portupgrade something and then a subsequent run shows this port as being 'newer' than the version it's supposed to be. I've [snip] also noticed a few times it seemed like it was upgrading the same version(s) over again. I just chalked this up to the ports system being in a state of I've never seen this without an f,r, or R flag. Out of curiosity, do you remember the ports involved? Since everything built, installed, and ran correctly I never really payed it much attention. Some time ago, maybe a month or two back, it seemed like Apache 2 and PHP5 were getting rebuilt more often than I was used to seeing in the past. I just figured the ports were getting fine tuned on an almost daily basis and just chalked it up to that. But there was a time or two that Apache updated to the same version a few days in a row. After a few iterations it stopped. One example just occurred on my dev web server at home yesterday. I did not see pdflib-7.0.3 listed as needing updating when I ran portversion. Yet when I did portupgrade -a for the couple of others which did need updating I also got pdflib-7.0.3 upgraded to pdflib-7.0.4, even though I did not see it listed by portversion. So now if I run portsdb -uF pkgdb -u portversion it will indicate an next to pdflib. Since it has caused no problem of any kind I don't worry about it. Usually when an oddity like this surfaces and I repeat my csup/portsdb/pkgdb and portversion run a day, or two, or three, later it just takes care of itself. Just an oddity which doesn't seem to be harmful. I just figure it's the ports system existing in a fluid state and until or unless something breaks I'm not concerned. -Mike ___ 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 not handling dependencies
I've been running Freebsd for several years on one of my primary public facing servers. Currently the server is running Freebsd 7.2. Up until about 2 weeks ago portupgrade always seemed to upgrade ports in the correct order so that any dependencies were built first, allowing all ports to be upgraded properly in one run. For the past 2 weeks though I have to run portupgrade 2-3 times every time I have more than one update because at least 1 port fails due to a dependency(which is seemingly upgraded after it tries to upgrade the other port). What the heck is going on and how do I fix it? Thanks, Eric ___ 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 not handling dependencies
For the past 2 weeks though I have to run portupgrade 2-3 times every time I have more than one update because at least 1 port fails due to a dependency(which is seemingly upgraded after it tries to upgrade the other port). What the heck is going on and how do I fix it? We obviously can't help you without more information. What ports are failing? What are the dependencies that are out of sequence? What OPTIONS are you using with all of these? Have you overidden anything via pkgtools.conf? Is you ports tree up-to-date, and intact? b. ___ 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 not handling dependencies
Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' As seen above, libtheora built and installed just fine, but ffmpeg was skipped for some reason. I ran portupgrade -a again and all worked fine. This ways also occuring when I ran portupgrade -arR. Ports tree is updated with cvsup each night. I don't believe I've overridden anything, most especially not in the past 2 weeks when this all started happening. The above is just one example of it happening. It happens almost everyday there is more than one port to upgrade(and different ports each time of course). Thanks again, Eric b. f. wrote: For the past 2 weeks though I have to run portupgrade 2-3 times every time I have more than one update because at least 1 port fails due to a dependency(which is seemingly upgraded after it tries to upgrade the other port). What the heck is going on and how do I fix it? We obviously can't help you without more information. What ports are failing? What are the dependencies that are out of sequence? What OPTIONS are you using with all of these? Have you overidden anything via pkgtools.conf? Is you ports tree up-to-date, and intact? b. ___ 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 not handling dependencies
On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote: Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' I see. In the default /usr/local/etc/pkgtools.conf, there is a sample line (not commented out) that places any port that matches the glob bsdpan-* in HOLD_PKGS, meaning that portupgrade will refuse to handle it. Presumably this is so users can manage their own local tree of Perl ports that aren't in the regular ports tree. I don't do this, so I'm not familiar with how the two interact. But portupgrade seems to have done the right thing here: in the snippet you gave us, it ignored bsdpan-Acme-Damn and proceeded to begin building ffmpeg after updating libtheora -- the only problem seems to be that in the intermediate summary it lists ffmpeg, erroneously, as having been skipped -- but that seems to just be a cosmetic problem, because it then proceeds to start updating it. If later on it refuses to update it, then you've got a problem. In that case, you should try running pkgdb -L pkgdb -F to make sure that your pkgdb is in good shape, and then try your updates again. You might also try instead something like: portupgrade -ax bsdpan-* If that doesn't work, then you may either have to rip out your bsdpan-* ports, or just use a another tool for updating -- portmaster, for example. Or you can roll your own. b. ___ 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 not handling dependencies
Actually, the bsdpan package is not the issue here. I was aware it wouldn't update that(no port for this perl module yet anyway). If you notice, it doesn't proceed to install ffmpeg, i force it to(highlighted by ): ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) ** %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) It should upgrade ffmpeg automatically, but doesn't and that is the issue. b. f. wrote: On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote: Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' I see. In the default /usr/local/etc/pkgtools.conf, there is a sample line (not commented out) that places any port that matches the glob bsdpan-* in HOLD_PKGS, meaning that portupgrade will refuse to handle it. Presumably this is so users can manage their own local tree of Perl ports that aren't in the regular ports tree. I don't do this, so I'm not familiar with how the two interact. But portupgrade seems to have done the right thing here: in the snippet you gave us, it ignored bsdpan-Acme-Damn and proceeded to begin building ffmpeg after updating libtheora -- the only problem seems to be that in the intermediate summary it lists ffmpeg, erroneously, as having been skipped -- but that seems to just be a cosmetic problem, because it then proceeds to start updating it. If later on it refuses to update it, then you've got a problem. In that case, you should try running pkgdb -L pkgdb -F to make sure that your pkgdb is in good shape, and then try your updates again. You might also try instead something like: portupgrade -ax bsdpan-* If that doesn't work, then you may either have to rip out your bsdpan-* ports, or just use a another tool for updating -- portmaster, for example. Or you can roll your own. b. ___ 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 not handling dependencies
2009/7/8 Eric Sheesley eshee...@shadowlair.com Well, it has been happening with just about every port(no specific ones) that have a dependency which is also being built. An example from today: === Registering installation for libtheora-1.0_1 === Cleaning for libtheora-1.0_1 --- Cleaning out obsolete shared libraries [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages found (-0 +1) . done] --- Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a requisite package 'libtheora-1.0' () failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - (bsdpan-Acme-Damn-0.04) * multimedia/ffmpeg (ffmpeg-2008.07.27_10) %portupgrade -a --- Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user (specify -f to force) --- Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11' (multimedia/ffmpeg) --- Building '/usr/ports/multimedia/ffmpeg' As seen above, libtheora built and installed just fine, but ffmpeg was skipped for some reason. I ran portupgrade -a again and all worked fine. This ways also occuring when I ran portupgrade -arR. Ports tree is updated with cvsup each night. I don't believe I've overridden anything, most especially not in the past 2 weeks when this all started happening. The above is just one example of it happening. It happens almost everyday there is more than one port to upgrade(and different ports each time of course). Thanks again, Eric Try to run portsdb -F everytime after cvsup is done. I might be wrong, but it works for me without any problems. -- With best regards, Vladislav Prokofyev ___ 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 not handling dependencies
On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote: Actually, the bsdpan package is not the issue here. I was aware it wouldn't update that(no port for this perl module yet anyway). If you notice, it doesn't proceed to install ffmpeg, i force it to(highlighted by ): Yes, I was too hasty. So this happens with ports other than libtheora, ports that you have no problem installing manually, with make deinstall make clean install make clean? And there is never any descriptive message given? Unknown Build Error or Unknown Install Error or the like? If so, you could try forcibly rebuilding portupgrade and it's dependencies, and see if that fixes the problem. If it doesn't, and you think that your ports tree and INDEX file are okay, there may be a problem with your package database -- /var/db/pkg by default. In which case you may have to clean everything out and rebuild, if you can't find the problem. There have been other problems reported with portupgrade, but it works fine for me, so I think the issue is peculiar to your system. b. ___ 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 not handling dependencies
Prokofyev Vladislav wrote: snip] As seen above, libtheora built and installed just fine, but ffmpeg was skipped for some reason. I ran portupgrade -a again and all worked fine. This ways also occuring when I ran portupgrade -arR. Ports tree is updated with cvsup each night. I don't believe I've overridden anything, most especially not in the past 2 weeks when this all started happening. The above is just one example of it happening. It happens almost everyday there is more than one port to upgrade(and different ports each time of course). Thanks again, Eric Try to run portsdb -F everytime after cvsup is done. I might be wrong, but it works for me without any problems. What I do is this: csup -L 2 portsdb -uF pkgdb -u portversion And take a peek to see what needs upgrading. Then I just do portupgrade -a and generally most of the time it does OK. I have noticed that it seems to be smoother with less hiccups when run more often so as to only need to update a few at a time rather than waiting until a whole lot of stuff needs updating. The reason I do it in the sequence I do is I believe this way the package database and the INDEX stay in sync. I have noticed some odd behaviors in the last 3 months, or so. So far no catastrophe. But I have seen portupgrade something and then a subsequent run shows this port as being 'newer' than the version it's supposed to be. I've also noticed a few times it seemed like it was upgrading the same version(s) over again. I just chalked this up to the ports system being in a state of flux and it hasn't actually led to any problems so I've just ignored it. -Mike ___ 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 not handling dependencies
But I have seen portupgrade something and then a subsequent run shows this port as being 'newer' than the version it's supposed to be. I've portsdb -Fu runs `make fetchindex`, grabbing the INDEX* file from whatever server you've told it to go to, and then rebuilds/updates the portsdb from that. So it's possible that with your csup you've obtained a port that is newer than the one recorded in the INDEX* file, when it was built on the remote server with an older ports tree some time ago. This is usually harmless. If it causes problems, and you can't wait for a fresh INDEX* file to be built remotely, or you have a modified ports tree that departs from the usual one so much that it makes sense to have your own INDEX*, then you can run make index in /usr/ports, or wherever your PORTSDIR is, and then portsdb -u. This is usually a lengthy process, unless you've stripped out large parts of your ports tree. also noticed a few times it seemed like it was upgrading the same version(s) over again. I just chalked this up to the ports system being in a state of I've never seen this without an f,r, or R flag. Out of curiosity, do you remember the ports involved? b. ___ 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
