Re: Portmaster ignoring +IGNOREME??
If I understand the problem correctly, the attached patch will fix it. Please confirm this for me when you can. That fixed it Doug - thanks for the quick response. Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Mark Ovens wrote: If I understand the problem correctly, the attached patch will fix it. Please confirm this for me when you can. That fixed it Doug - thanks for the quick response. Good news, thanks for testing it. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Doug, it's happened again: [...] === Updating package dependency entry for each dependent port === Re-installation of mjpegtools-1.9.0.r3 succeeded === Returning to check of ports depending on icu-3.8.1 === Launching child to update mozilla-1.7.13_3,2 icu-3.8.1 mozilla-1.7.13_3,2 === Port directory: /usr/ports/www/mozilla === This port is marked DEPRECATED === The mozilla team has shifted the development branch of mozilla to seamonkey, this port is outdated and has many vulnerabilities. Please consider using www/seamonkey or www/firefox instead. === If you are sure you can build it, remove the DEPRECATED line in the Makefile and try again. === Update for mozilla-1.7.13_3,2 failed === Aborting update === pkg-message for gnokii-0.6.22,1 [] It honoured the +IGNOREME during the recursive ``make config'' but failed during the build. In this case, unlike the last, it was using the same version of portmaster (2.1) throughout. The command I ran was: portmaster -BudRr icu-3.8.1/ The only common thing between the two instances of this happening is that a large number of ports were being rebuilt/upgraded. Is this significant? As this run took the best part of 24 hours it is a bit of a pain. The reason mozilla has a +IGNOREME is because it is only required by openoffice, which also has a +IGNOREME. The only workround I can think is to move the mozilla and openoffice directories out of /var/db/pkg while I run portmaster, then back again afterwards. This also highlights a potential problem with portmaster. because it prints out all the pkg-message files at the end, and the summary list, there is the potential for the reason for the abort to have scrolled out of the shell's scrollback buffer (it wasn't far off in this instance) thereby making it impossible to find out which port failed - in fact the only reason I knew that something had failed was because I knew that some Xorg stuff had to be rebuilt and it didn't appear in the summary. Can I suggest the following enhancements? 1. That portmaster reports the port that failed (and why, if possible) in the summary. 2. That the pkg-message file output it written to a file rather than the screen (with a message where the file is) to avoid the potential problem of any failures - and indeed some of the pkg-message output - being lost from the scrollback buffer. Maybe this could be an option rather than the standard behaviour? Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Doug Barton wrote: Mark Ovens wrote: Doug, it's happened again: It's impossible for me to debug this properly without knowing the command line options you used. I'm guessing from your description of the problem that you used at least -r and -u. I included the command line in my OP - portmaster -BudRr icu-3.8.1/ so yes, -r and -u It honoured the +IGNOREME during the recursive ``make config'' but failed during the build. If I understand the problem correctly, the attached patch will fix it. Please confirm this for me when you can. I'll try it and let you know - thanks for the quick response. This also highlights a potential problem with portmaster. because it prints out all the pkg-message files at the end, and the summary list, there is the potential for the reason for the abort to have scrolled out of the shell's scrollback buffer (it wasn't far off in this instance) If you don't use -u, there is a pause between the end of the failed build and the display of the pkg-message files. If you do use -u it's assumed that you are able to handle the consequences of doing so. I actually suggest that people stop using -u, and I am seriously considering just removing it. It doesn't do what people apparently think it should do, and it's caused way more trouble than it's worth. I was of the understanding that it assumed the default answer for any questions that were asked so, by using it, it didn't sit there forever waiting for an answer. I've just re-read the manpage and seen the note you put about -u. Am I correct in thinking then that if you use -d that it will have the same net effect as using -u - i.e. it won't ask questions? One other request. With ports like the Java JDK (and acroread IIRC) you have to agree to the licence before it will build. This appears to be in the source tarball - i.e. it runs when the archive is unpacked and is outside the control of the ports system and therefore utilities like portmaster. This is another pain because the build stops until you've answered the question. Would it be possible for a list of these ports to be built into portmaster so that if any are required it runs at least ``make extract'' once the tarball has been fetched to save having the upgrade stop which kind of defeats the object of running portmaster unattended. Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Mark Ovens wrote: Doug, it's happened again: It's impossible for me to debug this properly without knowing the command line options you used. I'm guessing from your description of the problem that you used at least -r and -u. It honoured the +IGNOREME during the recursive ``make config'' but failed during the build. If I understand the problem correctly, the attached patch will fix it. Please confirm this for me when you can. This also highlights a potential problem with portmaster. because it prints out all the pkg-message files at the end, and the summary list, there is the potential for the reason for the abort to have scrolled out of the shell's scrollback buffer (it wasn't far off in this instance) If you don't use -u, there is a pause between the end of the failed build and the display of the pkg-message files. If you do use -u it's assumed that you are able to handle the consequences of doing so. I actually suggest that people stop using -u, and I am seriously considering just removing it. It doesn't do what people apparently think it should do, and it's caused way more trouble than it's worth. Doug -- This .signature sanitized for your protection --- portmaster 2008/01/30 01:40:33 2.24 +++ portmaster 2008/02/11 23:17:35 @@ -1811,7 +1811,7 @@ fi ;; esac - elif [ -n $NO_RECURSIVE_CONFIG ]; then + elif [ -n $NO_RECURSIVE_CONFIG -o -n $URB_YES ]; then echo '' echo === $upg_port has an +IGNOREME file, ignoring echo '' ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Doug Barton wrote: I didn't see the first one, so it probably didn't hit the list. Both of your problems are almost certainly caused by running the old version first. Please repeat your -Baud run to make sure that portmaster 2.0 is handling +IGNOREME properly (it should), and then update apache and let us know if the +DISPLAY (pkg-message) file is displayed correctly. Thanks Doug, everything worked as expected this time. I like the summary that is now displayed when portmaster finishes - very useful. Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster ignoring +IGNOREME??
Mark Ovens wrote: Doug Barton wrote: I didn't see the first one, so it probably didn't hit the list. Both of your problems are almost certainly caused by running the old version first. Please repeat your -Baud run to make sure that portmaster 2.0 is handling +IGNOREME properly (it should), and then update apache and let us know if the +DISPLAY (pkg-message) file is displayed correctly. Thanks Doug, everything worked as expected this time. *phew* That means I only have one bug to fix, and I can release the update today. :) I like the summary that is now displayed when portmaster finishes - very useful. Thanks, although I have to say, it was a user who suggested that. I confess I have become rather lax in attributing ideas to those folks who suggest them, and to them I apologize. The record keeping got a little overwhelming when combined with all the changes in the 2.0 version. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
