Re: Advice sought on Portmaster -Faf and deleted ports
Hi, I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, linux-base-fc4 has been deleted. terminating terminating terminating etc. So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? It should just work. Have you converted to pkgng? I dream of the day that the ports system will just work. I don't use binary packages, are you saying that pkgng will deal with this issue automatically? Thanks, Scott ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 Oct 2013, Scott Ballantyne wrote: I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, linux-base-fc4 has been deleted. terminating terminating terminating etc. That's correct. linux_base-fc4 is long gone (years), replaced by linux_base-f10. portmaster sees no way to upgrade that port, so evidently it quits. If you have ports that far out of date, the upgrade process is going to be long. Ports where the system does not know the replacement will have to be handled manually. So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? It should just work. Have you converted to pkgng? I dream of the day that the ports system will just work. I don't use binary packages, are you saying that pkgng will deal with this issue automatically? No, the concern was that you might have already converted to pkgng but still used the old package tools. ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 oct 2013, Warren Block wbl...@wonkity.com wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, linux-base-fc4 has been deleted. terminating terminating terminating etc. That's correct. linux_base-fc4 is long gone (years), replaced by linux_base-f10. portmaster sees no way to upgrade that port, so evidently it quits. I understand why portmaster quits that port. It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. If you have ports that far out of date, the upgrade process is going to be long. Ports where the system does not know the replacement will have to be handled manually. Actually, the last time I updated my ports was when I installed 9.0, and I used the portmaster 'nuke all ports' method I was trying to day. Since then, several dozen ports of been 'deleted' or 'renamed', not just the linux_base-fc4. Seems in the case of ports which have been renamed or replaced, this could in fact be simply automated in most cases. Best, Scott -- s...@ssr.com ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, Oct 14, 2013 at 6:35 PM, Scott Ballantyne s...@ssr.com wrote: I understand why portmaster quits that port. Because it has no choice. It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. So it should continue on and potentially build 1000's of ports with broken linking and dependencies? Portupgrade will do this if you tell it. Try it out and see what fun you can create. -- Adam Vande More ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 Oct 2013, Scott Ballantyne wrote: On Mon, 14 oct 2013, Warren Block wbl...@wonkity.com wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, linux-base-fc4 has been deleted. terminating terminating terminating etc. That's correct. linux_base-fc4 is long gone (years), replaced by linux_base-f10. portmaster sees no way to upgrade that port, so evidently it quits. I understand why portmaster quits that port. It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. Some of them. It could not update any ports that depend on missing ports, which conflicts with the -a meaning all. If you have ports that far out of date, the upgrade process is going to be long. Ports where the system does not know the replacement will have to be handled manually. Actually, the last time I updated my ports was when I installed 9.0, and I used the portmaster 'nuke all ports' method I was trying to day. Since then, several dozen ports of been 'deleted' or 'renamed', not just the linux_base-fc4. Seems in the case of ports which have been renamed or replaced, this could in fact be simply automated in most cases. I think it does handle renamed ports. Whether the ones it does not handle are due to missing functionality or because they are difficult or impossible to handle, don't know. ___ 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: Advice sought on Portmaster -Faf and deleted ports
Adam Vande More wrote: It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. So it should continue on and potentially build 1000's of ports with broken linking and dependencies? Portupgrade will do this if you tell it. Try it out and see what fun you can create. Not a single program on my system depended on that program being rebuilt. Portmaster should certainly refuse to rebuild anything that did, of course. ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon 14 Oct 2013 Warren Block wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: On Mon, 14 oct 2013, Warren Block wbl...@wonkity.com wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: Actually, the last time I updated my ports was when I installed 9.0, and I used the portmaster 'nuke all ports' method I was trying to day. Since then, several dozen ports of been 'deleted' or 'renamed', not just the linux_base-fc4. Seems in the case of ports which have been renamed or replaced, this could in fact be simply automated in most cases. I think it does handle renamed ports. Whether the ones it does not handle are due to missing functionality or because they are difficult or impossible to handle, don't know. Such was not my experience, Warren. And actually, a google search while I was trying to solve this turned up many reports of the same problem over the past years. ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, Oct 14, 2013 at 9:48 PM, Scott Ballantyne s...@ssr.com wrote: Adam Vande More wrote: It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. So it should continue on and potentially build 1000's of ports with broken linking and dependencies? Portupgrade will do this if you tell it. Try it out and see what fun you can create. Not a single program on my system depended on that program being rebuilt. And what about libs it may have left behind and other ports picking up faulty info? Then you build unsupported and faultly packages and complain to the list when something doesn't work. Just follow /usr/ports/UPDATING as advised instead of your shortcuts. Portmaster should certainly refuse to rebuild anything that did, of course. Exactly what it did. -- Adam Vande More ___ 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
Advice sought on Portmaster -Faf and deleted ports
Hi, I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. If the ports aren't in use, I have just deleted them, but for other things, such as libgsf-1.14.21_1, which is required by a dozen or more of my installed packages, it is not so easy. So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? Thanks! Scott -- s...@ssr.com ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Sun, 13 Oct 2013, Scott Ballantyne wrote: Hi, I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. What errors, exactly? So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? It should just work. Have you converted to pkgng? ___ 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: Re: # portmaster -r pixman fails with !#/bin/sh list too long
On 10/03/2013 20:28, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Is it vital to use the texlive ports you get via portshaker or could you switch to TEX_DEFAULT=texlive and use the texlive 2012 from official ports (which has a few huge instead of many tiny packages)? (If you want to switch, remove everything starting with texlive, check out a fresh ports tree without portshaker, since there is at least one port with the same name, and install print/texlive-full and maybe print/texlive-docs.) Cheers, Jan Henrik ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Thu, 3 Oct 2013, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Careful: -R has a different meaning with portmaster than it does with portupgrade. It does not mean recursive like lowercase -r. pkg_libchk from sysutils/bsdadminscripts can be used to detect installed ports that depend on missing libraries. From that, it may be possible to just give a list of all the ones that are missing pixman to portmaster. ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Fri, Oct 4, 2013 at 12:09 PM, Warren Block wbl...@wonkity.com wrote: On Thu, 3 Oct 2013, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Careful: -R has a different meaning with portmaster than it does with portupgrade. It does not mean recursive like lowercase -r. pkg_libchk from sysutils/bsdadminscripts can be used to detect installed ports that depend on missing libraries. From that, it may be possible to just give a list of all the ones that are missing pixman to portmaster. Dear all, It appears that using # portmaster -d -r pixman -x 'texlive-*-*' is doing the job :) I am keeping my fingers crossed and hope it comes through and succeeds! It stopped with libexo, but got that sorted out. Then stopped with mplayer*, but I am skipping it at this time. -x 'mplayer-*' and hope it succeeds, I'll then rebuild mplayer later if needed. Best Regards, Antonio ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Tue, Oct 1, 2013 at 8:46 AM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Antonio Olivares olivares14...@gmail.com writes:
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Try the '-R' again; it may get a bit farther each time.
You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.
Good luck.
Have tried that, but it rebuilds pixman, but then X bombs out blurting
out messages that libpixman.so is missing :(
I have tried to remove print/texlive-scheme-full; removed it, but then
run portmaster -R pixman, and portmaster -r pixman and the running of
it stops with message that !#/bin/sh .. argument too long and comes up
with texlive-?-?-_1 or similar. Have not been successful in
fixing this issue. I have 2 machines working and 2 not working
because of this. I am running out of ideas. Is there another way to
fix this issue manually, i.e, going to /usr/ports/x11/pixman and
rebuilding it there or have to go one by one?
Thanks for your advice and suggestions but I am not getting there :(
Best Regards,
Antonio
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares olivares14...@gmail.com writes: Dear folks, In updating ports I encounter above issue and cannot proceed. 20130929: AFFECTS: users of x11/pixman AUTHOR: zeis...@freebsd.org The library version of x11/pixman has changed, and portrevision has been bumped in all dependent ports. If you have external software that depends on pixman, this software needs to be recompiled. To recompile all software dependent on pixman, run: # portmaster -r pixman or # portupgrade -rf pixman The messages are that a pkg texlive-ub* and that #!/bin/sh list too long. I try to run # portmaster -d -r pixman -x 'texlive-*' but it still fails in the same place :( I continued with portmaster's -R option and got a lot further. You could try either that or the command line that portmaster suggests when it bails out. I am using texlive-freebsd from Romain Tartiere's googlecode page in case it is important. Please advice me so I can succeed to fix these issue. I lost X because I failed to read the /usr/src/UPDATING advice and then I realized that I overlooked this :( I don't think that texlive is relevant; if you continue the process instead of starting from scratch, you'll probably get farther. I'd prefer to actually debug the problem at its root, but it's the middle of the night and I don't seem to have enough brain cells awake to figure anything out. Good luck. ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
Dear Sir,
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Best Regards,
Antonio
On Tue, Oct 1, 2013 at 1:27 AM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Antonio Olivares olivares14...@gmail.com writes:
Dear folks,
In updating ports I encounter above issue and cannot proceed.
20130929:
AFFECTS: users of x11/pixman
AUTHOR: zeis...@freebsd.org
The library version of x11/pixman has changed, and portrevision has
been bumped in all dependent ports. If you have external software that
depends on pixman, this software needs to be recompiled.
To recompile all software dependent on pixman, run:
# portmaster -r pixman
or
# portupgrade -rf pixman
The messages are that a pkg texlive-ub* and that #!/bin/sh list
too long. I try to run
# portmaster -d -r pixman -x 'texlive-*'
but it still fails in the same place :(
I continued with portmaster's -R option and got a lot further. You
could try either that or the command line that portmaster suggests
when it bails out.
I am using texlive-freebsd from Romain Tartiere's googlecode page in
case it is important. Please advice me so I can succeed to fix these
issue. I lost X because I failed to read the /usr/src/UPDATING advice
and then I realized that I overlooked this :(
I don't think that texlive is relevant; if you continue the process
instead of starting from scratch, you'll probably get farther.
I'd prefer to actually debug the problem at its root, but it's the
middle of the night and I don't seem to have enough brain cells awake
to figure anything out.
Good luck.
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares olivares14...@gmail.com writes:
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Try the '-R' again; it may get a bit farther each time.
You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.
Good luck.
___
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
# portmaster -r pixman fails with !#/bin/sh list too long
Dear folks, In updating ports I encounter above issue and cannot proceed. 20130929: AFFECTS: users of x11/pixman AUTHOR: zeis...@freebsd.org The library version of x11/pixman has changed, and portrevision has been bumped in all dependent ports. If you have external software that depends on pixman, this software needs to be recompiled. To recompile all software dependent on pixman, run: # portmaster -r pixman or # portupgrade -rf pixman The messages are that a pkg texlive-ub* and that #!/bin/sh list too long. I try to run # portmaster -d -r pixman -x 'texlive-*' but it still fails in the same place :( I am using texlive-freebsd from Romain Tartiere's googlecode page in case it is important. Please advice me so I can succeed to fix these issue. I lost X because I failed to read the /usr/src/UPDATING advice and then I realized that I overlooked this :( Best Regards, Antonio ___ 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: Can I avoid the display of pkg-messages in portmaster?
On 05/12/2013 12:37 AM, Leslie Jensen wrote: I do some work on remote machines and sometimes I have a need to execute additional commands after for example a portmaster -a command. Normally I use the to separate commands but this does not work when portmaster displays pkg-messages. I cannot see in the portmaster manpage that there's a possibility to make the choice on displaying pkg-messages. Maybe a suggestion to further enhance portmaster in the future. To work around this I was thinking of maybe making a script that ran portmaster -a then a command to press space until one is sure that all messages has been displayed. On this I could need some help. My scripting skills are not that good. To avoid interaction when scripting or logging portmaster, in addition to the --no-confirm option, I usually set the following environment variables prior to invocation: BATCH=yes PAGER=cat The former should avoid any build-time port interaction (and mark the port BROKEN if it must, so I can deal with it manually); the latter causes portmaster to use 'cat' instead of 'more' to display the pkg-messages afterwards. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://www.fur.com/peace/ ___ 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
Can I avoid the display of pkg-messages in portmaster?
I do some work on remote machines and sometimes I have a need to execute additional commands after for example a portmaster -a command. Normally I use the to separate commands but this does not work when portmaster displays pkg-messages. I cannot see in the portmaster manpage that there's a possibility to make the choice on displaying pkg-messages. Maybe a suggestion to further enhance portmaster in the future. To work around this I was thinking of maybe making a script that ran portmaster -a then a command to press space until one is sure that all messages has been displayed. On this I could need some help. My scripting skills are not that good. Thanks /Leslie ___ 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
Are the procedure with portmaster exactly the same when one is using pkgng
I'm specifically thinking of the directories that has to be emptied or deleted. Thanks /Leslie Using portmaster to do a complete reinstallation of all your ports: 1. portmaster --list-origins ~/installed-port-list 2. Update your ports tree 3. portmaster -ty --clean-distfiles 4. portmaster --check-port-dbdir 5. portmaster -Faf 6. pkg_delete -a 7. rm -rf /usr/local/lib/compat/pkg 8. Back up any files in /usr/local you wish to save, such as configuration files in /usr/local/etc 9. Manually check /usr/local and /var/db/pkg to make sure that they are really empty 10. Re-install portmaster 11. portmaster `cat ~/installed-port-list` - ___ 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
Typo in portmaster man page?
When reading the portmaster man page I just came to wonder if this isn't a typo? [--force-config|-G] [-aftv] -F fetch distfiles only Shouldn't the -F be to the far left? Thanks /Leslie ___ 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: Typo in portmaster man page?
On 5/9/2013 3:25 AM, Leslie Jensen wrote: When reading the portmaster man page I just came to wonder if this isn't a typo? [--force-config|-G] [-aftv] -F fetch distfiles only Shouldn't the -F be to the far left? Thanks /Leslie It seems consistent with how the other feature modes are documented. (I'm not the original author on portmaster). Personally the manpage really confuses me. There's been bigger issues to tackle first though so I have not touched the manpage much. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Typo in portmaster man page?
On Thu, 09 May 2013 06:06:42 -0500 Bryan Drewery articulated: (I'm not the original author on portmaster). Personally the manpage really confuses me. There's been bigger issues to tackle first though so I have not touched the manpage much. You do realize that the man in manpage is an acronym for, Much About Nothing. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Typo in portmaster man page?
- Original Message - From: Jerry je...@seibercom.net To: FreeBSD freebsd-questions@freebsd.org Cc: Sent: Thursday, 9 May 2013 5:15 PM Subject: Re: Typo in portmaster man page? On Thu, 09 May 2013 06:06:42 -0500 Bryan Drewery articulated: (I'm not the original author on portmaster). Personally the manpage really confuses me. There's been bigger issues to tackle first though so I have not touched the manpage much. You do realize that the man in manpage is an acronym for, Much About Nothing. that interpretation of yours might be insulting to man page authors :( -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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
portmaster -- no execute command
Does portmaster have a --noexecute flag like portupgrade? Specifically, I want to run the following command and see exactly what would be updated / modified sans actually doing it. portmaster -o new_app old_app -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: portmaster -- no execute command
On Wed, 17 Apr 2013 16:34:24 -0400, Jerry wrote: Does portmaster have a --noexecute flag like portupgrade? Specifically, I want to run the following command and see exactly what would be updated / modified sans actually doing it. portmaster -o new_app old_app Is the -n option what you are looking for? From man portmaster: -n run through all steps, but do not make or install any ports This common flag seems to be allowed for installation via -o, according to the synopsis: portmaster [Common Flags] -o new port dir in /usr/ports installed port -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
stupid portmaster question
How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) ___ 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: stupid portmaster question
Just use -x switch portmaster -ad -x libreoffice 2013/3/25 Aryeh Friedman aryeh.fried...@gmail.com: How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) ___ 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 -- Demelier David ___ 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: stupid portmaster question
On 03/25/2013 10:40, Aryeh Friedman wrote: How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) ___ 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 -x libreoffice -- No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. ___ 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: stupid portmaster question
2013-03-25 10:40, Aryeh Friedman skrev: How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) ___ 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 Create the file +IGNOREME for all ports you want to ignore ;-) Example Touch /var/db/pkg/libreoffice-4.0.1_1/+IGNOREME /Leslie ___ 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: stupid portmaster question
How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) -x avoid building or updating ports that match this pattern. Can be specified more than once. If a port is not already installed the exclude pattern will be run against the directory name from /usr/ports. Is that what you are looking for? Anton ___ 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: stupid portmaster question
Aryeh Friedman aryeh.fried...@gmail.com writes: How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) Your direct question was already answered, but note that libreoffice is not broken overall, just with certain options that probably won't affect its operation for you. ___ 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: stupid portmaster question
On Mon, 25 Mar 2013 09:53:00 -0400, Lowell Gilbert wrote: Aryeh Friedman aryeh.fried...@gmail.com writes: How do I tell portmaster -ad to ignore certain ports because they are broken such as editors/libreoffice is currently marked as (I am sure this will change soon) Your direct question was already answered, but note that libreoffice is not broken overall, just with certain options that probably won't affect its operation for you. To amplify, the (main?) culprit is MERGELIBS. OP: If you are trying to upgrade, just do a 'make config' first and uncheck the option. ___ 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
Portmaster runs make config three times for some ports
I started off portmaster on a massive update on Thursday evening. Everything started off OK and I kept responding to all the make config screens until they were all finished and the compilation was well underway then went to bed and left it to get on with it. The next morning I discovered that things had progressed as far as starting to build en-apache-openoffice but it was sitting there with the config screen again despite having already gone through make config earlier. I clicked on OK and left it to get on with the compilation while I went away to get on with other things with just occasional checks to make sure it was still running. About 6 hours later when I checked it had completed the compilation and had started to install en-apache-openoffice but was waiting yet again with the config screen. Once again I clicked on OK and left things to continue. The job was still running last night and I expected to find it completed by this morning but on checking at 9:30 this morning I discovered that it had done the same thing with py27-gobject and had been sitting there with the config screen since shortly after midnight. Both openoffice and py27-gobject had gone through make config in the initial stage (I've checked the log file) but for some reason make config was repeated immediately before the compile and install stages. I invoked portmaster with: portmaster -r libffi -r boost-libs -r gnutls -r libtasn1 and these are the only options set in /usr/local/etc/portmaster.rc # Never search for stale distfiles to delete (-D) DONT_SCRUB_DISTFILES=Dopt # # Do not prompt the user for failed backup package creation PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package Any ideas how I can avoid this happening. -- Mike Clarke ___ 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: Portmaster runs make config three times for some ports
On 9 February 2013 05:45, Mike Clarke jmc-freeb...@milibyte.co.uk wrote: I started off portmaster on a massive update on Thursday evening. Everything started off OK and I kept responding to all the make config screens until they were all finished and the compilation was well underway then went to bed and left it to get on with it. The next morning I discovered that things had progressed as far as starting to build en-apache-openoffice but it was sitting there with the config screen again despite having already gone through make config earlier. I clicked on OK and left it to get on with the compilation while I went away to get on with other things with just occasional checks to make sure it was still running. About 6 hours later when I checked it had completed the compilation and had started to install en-apache-openoffice but was waiting yet again with the config screen. Once again I clicked on OK and left things to continue. The job was still running last night and I expected to find it completed by this morning but on checking at 9:30 this morning I discovered that it had done the same thing with py27-gobject and had been sitting there with the config screen since shortly after midnight. Both openoffice and py27-gobject had gone through make config in the initial stage (I've checked the log file) but for some reason make config was repeated immediately before the compile and install stages. I invoked portmaster with: portmaster -r libffi -r boost-libs -r gnutls -r libtasn1 and these are the only options set in /usr/local/etc/portmaster.rc # Never search for stale distfiles to delete (-D) DONT_SCRUB_DISTFILES=Dopt # # Do not prompt the user for failed backup package creation PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package Any ideas how I can avoid this happening. It's slow painful, but run through once with -n, to set all of your config options, then run it again with BATCH=YES set (though I don't know if it would be best to edit /etc/make.conf, set it in the environment, or pass it with -m) to avoid it asking again. -- -- ___ 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: portmaster + unknown dependency problem
On 20.11.2012 20:47, Laszlo Nagy wrote: I have a 8.2-STABLE system. Last port upgrade was about a year ago. (I know, this is bad.) I was trying to update all ports, by following the UPDATING file. As it turned out, some ports has been deprecated/deleted. I have a problem in particular with the py-bittornado-core port. I do not need it. So I have deleted it: # pkg_info | grep bittornado # Clearly, it is not installed. However, when I write in this command: # portmaster -a Then I get this error: === The net-p2p/py-bittornado-core port has been deleted: Has expired: Depends on the deprecated wx 2.4 === Aborting update Well, here is the question: why does it want to build a port that does not even exist in the ports tree? It was really deleted, there is no such thing as /usr/ports/net-p2p/py-bittornado-core . I have also tried to do this: # portmaster -a -x py-bittornado-core but it has exactly the same problem. Is this a stale dependency to a nonexistent port? How can I overcome this problem? Thanks, Laszlo ___ 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 make pkg_info | grep *bittornado* When it found this package, you can think about to delete it. When you have delete it or doesnt found it, make a portmaster --check-depends to solve depends. ___ 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
portmaster: hal-0.5.14_20 and xorg-server-1.7.7_6, 1 (re)installation fails
When running portmaster -d -w -r pcre because of the upgrade from pcre-8.31 to pcre-8.32 I encountered the following inconveniences: Upgrade to hal-0.5.14_20 failed with the message it needs intltool 0.40 which was installed at the time. First upgrading to intltool-0.41.1 solved this. When reinstalling xorg-server-1.7.7_6,1 with portmaster today: Making install in xkb mkdir: /usr/local/share/X11/xkb/compiled: No such file or directory mkdir: /usr/local/share/X11/xkb/compiled: No such file or directory So I checked /usr/local/share/X11/xkb/compiled and this is a symlink to /var/lib/xkb which did not exist at the time. I created /var/lib/xkb and the installation went fine then. There is one file installed in this location: README.compiled This worked, but is it the right solution? Does anyone know what changed maybe? This is on 9.1-RELEASE with a portstree just updated with portsnap. Previous versions of the ports were from about 20 days ago. Everything is installed the standard way. Just if someone runs into these issues these may be found in the list (or already have been solved in ports) Things like this do not happen too often. ___ 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
portmaster + unknown dependency problem
I have a 8.2-STABLE system. Last port upgrade was about a year ago. (I know, this is bad.) I was trying to update all ports, by following the UPDATING file. As it turned out, some ports has been deprecated/deleted. I have a problem in particular with the py-bittornado-core port. I do not need it. So I have deleted it: # pkg_info | grep bittornado # Clearly, it is not installed. However, when I write in this command: # portmaster -a Then I get this error: === The net-p2p/py-bittornado-core port has been deleted: Has expired: Depends on the deprecated wx 2.4 === Aborting update Well, here is the question: why does it want to build a port that does not even exist in the ports tree? It was really deleted, there is no such thing as /usr/ports/net-p2p/py-bittornado-core . I have also tried to do this: # portmaster -a -x py-bittornado-core but it has exactly the same problem. Is this a stale dependency to a nonexistent port? How can I overcome this problem? Thanks, Laszlo ___ 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
portmaster or ports (packaging) problem ?
Hi, I hit a problem today during a system update. There were two libxul ports: /usr/ports/www/libxul /usr/ports/www/libxul19 of which the last one was installed: /var/db/pkg/libxul-1.9.2.28_1/ There was a port to update which died on error: # portmaster icedtea-web ... === The dependency for www/libxul seems to be handled by libxul-1.9.2.28_1 ... === Found libxul-1.9.2.28_1, but you need to upgrade to libxul=10. *** [build-depends] Error code 1 ... # So, I had to manually deinstall www/libxul19 and install www/libxul and try again. # portmaster icedtea-web ... === The following actions will be taken if you choose to proceed: Upgrade icedtea-web-1.3_1 to icedtea-web-1.3.1 Install www/libxul ... # Is the portmaster to blame for not being smart enough and not taking steps of deinstalling www/libxul19 and installing www/libxul in one step ? jb ___ 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: portmaster or ports (packaging) problem ?
But theese are different packages (different names). since ports dont have any equivalent of debian provides flag it is impossible to figure it out in a safe way. 09-11-2012 19:19, jb jb.1234a...@gmail.com napisał(a): Hi, I hit a problem today during a system update. There were two libxul ports: /usr/ports/www/libxul /usr/ports/www/libxul19 of which the last one was installed: /var/db/pkg/libxul-1.9.2.28_1/ There was a port to update which died on error: # portmaster icedtea-web ... === The dependency for www/libxul seems to be handled by libxul-1.9.2.28_1 ... === Found libxul-1.9.2.28_1, but you need to upgrade to libxul=10. *** [build-depends] Error code 1 ... # So, I had to manually deinstall www/libxul19 and install www/libxul and try again. # portmaster icedtea-web ... === The following actions will be taken if you choose to proceed: Upgrade icedtea-web-1.3_1 to icedtea-web-1.3.1 Install www/libxul ... # Is the portmaster to blame for not being smart enough and not taking steps of deinstalling www/libxul19 and installing www/libxul in one step ? jb ___ 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: portmaster or ports (packaging) problem ?
uki ukaszg at gmail.com writes: But theese are different packages (different names). since ports dont have any equivalent of debian provides flag it is impossible to figure it out in a safe way. I have never built a port/package, so I could be wrong here. This paragraph seems to contain means to specify a dependency and built it if needed: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-depend.html for example 5.8.3 BUILD_DEPENDS aside from its primary meaning as a requirement for building *this* port, it could be used indirectly to build and install a dependent port :-) and this offer means to specify a minimal version of a dependency: 5.8.8 Minimal Version of a Dependency My point is, the logic/infrastrucutre already exists, just adopt it to next level of port/package management. jb ___ 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: portmaster options
On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: Hi, what is the diff between --index and --index-only According to man portmaster there are some options that control the behaviour regarding the use of INDEX: --no-index-fetch skip fetching the INDEX file --index use INDEX-[7-9] exclusively to check if a port is up to date --index-first use the INDEX for status, but double-check with the port --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. This means --index-only is to be used when using portmaster for binary installs without an installed ports collection. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: portmaster options
Polytropon freebsd at edvax.de writes: On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: Hi, what is the diff between --index and --index-only ... --index use INDEX-[7-9] exclusively to check if a port is up to date ... --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. This means --index-only is to be used when using portmaster for binary installs without an installed ports collection. Well, yes, BUT they seem to be redundant (that's why I asked). # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # ___ 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: portmaster options
jb jb.1234abcd at gmail.com writes: ... --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. ... And -PP|--packages-only option implies index only entry behavior, so there is redundancy here as well. Does anybody know where this --index-only option really matter ? jb ___ 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: portmaster options
On 10/12/2012 01:57 PM, jb wrote: jb jb.1234abcd at gmail.com writes: ... --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. ... And -PP|--packages-only option implies index only entry behavior, so there is redundancy here as well. Does anybody know where this --index-only option really matter ? jb Well /usr/local/sbin/portmaster is a _big_ shell script You could read through it to find the answer to your question This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: portmaster options
On Fri, 12 Oct 2012 11:34:17 + (UTC), jb wrote: Polytropon freebsd at edvax.de writes: On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: Hi, what is the diff between --index and --index-only ... --index use INDEX-[7-9] exclusively to check if a port is up to date ... --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. This means --index-only is to be used when using portmaster for binary installs without an installed ports collection. Well, yes, BUT they seem to be redundant (that's why I asked). # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # Did you test this with or _without_ an actually installed ports collection? If you don't have one installed, --index probably won't work. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: portmaster options
Polytropon freebsd at edvax.de writes: ... Well, yes, BUT they seem to be redundant (that's why I asked). # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # Did you test this with or _without_ an actually installed ports collection? If you don't have one installed, --index probably won't work. # mv /usr/ports /usr/ports-saved # portmaster -L --index-only | egrep '(ew|ort) version|total install' /tmp/d-85964-index/INDEX-9.bz2100% of 1619 kB 185 kBps === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps 00m00s Terminated # Well, the second entry outcome (with --index option) looks like a bug to me. jb ___ 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: portmaster options
On Fri, 12 Oct 2012 04:35:43 + (UTC) jb wrote: Hi, what is the diff between --index and --index-only From a *very* quick look, it appears that --index-only means don't use the the port-directory at all, so that the index file is downloaded into /tmp, and some checks and optimizations are skipped or done less efficiently. ___ 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: portmaster options
RW rwmaillists at googlemail.com writes: On Fri, 12 Oct 2012 04:35:43 + (UTC) jb wrote: Hi, what is the diff between --index and --index-only From a *very* quick look, it appears that --index-only means don't use the the port-directory at all, so that the index file is downloaded into /tmp, and some checks and optimizations are skipped or done less efficiently. ... # ls -al /usr/ports/ ... -rw-r--r-- 1 root wheel 26881412 Oct 12 07:47 INDEX-7 -rw-r--r-- 1 root wheel 26765446 Oct 12 07:47 INDEX-8 -rw-r--r-- 1 root wheel 26715339 Oct 12 13:28 INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2 ... # # find /tmp -name *INDEX* # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # find /tmp -name *INDEX* Nope :-) jb ___ 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: portmaster options
On Fri, 12 Oct 2012 13:42:10 + (UTC), jb wrote: RW rwmaillists at googlemail.com writes: On Fri, 12 Oct 2012 04:35:43 + (UTC) jb wrote: Hi, what is the diff between --index and --index-only From a *very* quick look, it appears that --index-only means don't use the the port-directory at all, so that the index file is downloaded into /tmp, and some checks and optimizations are skipped or done less efficiently. ... # ls -al /usr/ports/ ... -rw-r--r-- 1 root wheel 26881412 Oct 12 07:47 INDEX-7 -rw-r--r-- 1 root wheel 26765446 Oct 12 07:47 INDEX-8 -rw-r--r-- 1 root wheel 26715339 Oct 12 13:28 INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2 ... # # find /tmp -name *INDEX* # portmaster -L --index-only | egrep '(ew|ort) version|total install' === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # find /tmp -name *INDEX* Nope :-) But this? # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps 00m00s Terminated This is with --index and _no_ ports collection in the default location (example quoted from your message)... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: portmaster options
Polytropon freebsd at edvax.de writes: ... But this? # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps 00m00s Terminated This is with --index and _no_ ports collection in the default location (example quoted from your message)... The above (aborted ?) entry did not create any /tmp die files - this will be obvious below. I repeated the procedure once again, with extra tests. [root@localhost ~]# mv /usr/ports /usr/ports-saved [root@localhost ~]# ls -al /tmp/d d-49774-index/ dbus-VVS2cduIFg dbus-cgVqiePRiB dbus-pt6vB9UUJ6 dbus-4inUXwgfJ4 dbus-Y2iXdHF5tz dbus-fsMikdzeLa dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-ZGcPBBe763 dbus-o2yUi7puUT dbus-vT3uAQQB6U dbus-FEJgZRlX7B dbus-ZmBHPDrpWD dbus-oVPu6XWzrw dbus-zrcvtjVO62 dbus-KPYiGOw8UL dbus-c36HAD5e3q dbus-paXxX0f1fy [root@localhost ~]# ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 15:35 .. [root@localhost ~]# find /tmp -name *INDEX* [root@localhost ~]# portmaster -L --index-only | egrep '(ew|ort) version|total install' /tmp/d-93752-index/INDEX-9.bz2100% of 1619 kB 185 kBps === New version available: smartmontools-5.43_1 === 618 total installed ports === 1 has a new version available # ls -al /tmp/d d-49774-index/ dbus-FEJgZRlX7B dbus-Y2iXdHF5tz dbus-c36HAD5e3q dbus-o2yUi7puUT dbus-pt6vB9UUJ6 dbus-zrcvtjVO62 dbus-4inUXwgfJ4 dbus-KPYiGOw8UL dbus-ZGcPBBe763 dbus-cgVqiePRiB dbus-oVPu6XWzrw dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-VVS2cduIFg dbus-ZmBHPDrpWD dbus-fsMikdzeLa dbus-paXxX0f1fy dbus-vT3uAQQB6U # ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 16:00 .. [root@localhost ~]# find /tmp -name *INDEX* /tmp/INDEX-9 /tmp/INDEX-9.bz2 [root@localhost ~]# ls -al /tmp/*INDEX* -rw-r--r-- 1 root wheel 26715339 Oct 12 16:00 /tmp/INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 /tmp/INDEX-9.bz2 [root@localhost ~]# portmaster -L --index | egrep '(ew|ort) version|total install' Terminated [root@localhost ~]# ls -al /tmp/d d-49774-index/ dbus-VVS2cduIFg dbus-cgVqiePRiB dbus-pt6vB9UUJ6 dbus-4inUXwgfJ4 dbus-Y2iXdHF5tz dbus-fsMikdzeLa dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-ZGcPBBe763 dbus-o2yUi7puUT dbus-vT3uAQQB6U dbus-FEJgZRlX7B dbus-ZmBHPDrpWD dbus-oVPu6XWzrw dbus-zrcvtjVO62 dbus-KPYiGOw8UL dbus-c36HAD5e3q dbus-paXxX0f1fy [root@localhost ~]# ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 16:00 .. [root@localhost ~]# find /tmp -name *INDEX* /tmp/INDEX-9 /tmp/INDEX-9.bz2 [root@localhost ~]# ls -al /tmp/*INDEX* -rw-r--r-- 1 root wheel 26715339 Oct 12 16:00 /tmp/INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 /tmp/INDEX-9.bz2 [root@localhost ~]# rm /tmp/INDEX* [root@localhost ~]# find /tmp -name *INDEX* [root@localhost ~]# # portmaster -L --index | egrep '(ew|ort) version|total install' Terminated [root@localhost ~]# [root@localhost ~]# find /tmp -name *INDEX* [root@localhost ~]# jb ___ 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: portmaster options
jb jb.1234abcd at gmail.com writes: ... I have doubts about these options use, so I filed a PR#: http://www.freebsd.org/cgi/query-pr.cgi?pr=172651 jb ___ 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
portmaster options
Hi, what is the diff between --index and --index-only jb ___ 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
portmaster backup package
Hi, what to do with that backup package (-b option) after installation of new port failed ? jb ___ 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: portmaster backup package
On Mon, 8 Oct 2012 16:18:20 + (UTC), jb wrote: Hi, what to do with that backup package (-b option) after installation of new port failed ? Install it with pkg_add? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
Am 08/16/12 21:44, schrieb Garrett Cooper: On Thu, Aug 16, 2012 at 8:33 AM, Hartmann, O. ohart...@zedat.fu-berlin.de wrote: I ran into a very delicate and nasty situation. ... On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. I'm not drawing a correlation between this and unrelated coredumping processes. Me neither, I report this for completeness, since I'm not a OS developer, such a behaviour could hint/indicate people who are involved in the OS development, what is going on. Sorry when I'm trying to be too precise (precise as precise I can be without the exact terminology!). An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! Don't make delete-old-lib unless you have it moved off to compat directories, or have rebuilt everything using the new libarchive. I didn't! As I wrote before, this mess happened on ALL(!) freeBSD 10.0-CURRENT boxes in the very same way when I updated/reinstalled security/cyrus-sasl2. Moreover: I can reproduce this on all boxes. All my boxes use OpenLDAP as a backend with SASL2 enabled (not used so far). On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). truss the binaries to figure out exactly what's going wrong. I will try, but when this errative coredumps of binaries occur, nothing works properly that is using any kinf of dynamical loaded library! Only the binaries (static?) from /resucue/* do their work. A lot of this lost effort could be avoided (like others have posted on the list more than once), by having a centralized package distribution server, and by having VMs or jails and keeping snapshots with pre-upgrade state on the package building machine to avoid dead in the water scenarios like you're in right now. Yes, I'm working on this. it seems, that it becomes more relevant since I realized that FreeBSD suffers sometimes from misleaded ports or ports which suddenly are marked BROKEN and do not get compiled ... I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? I ran into this issue too a little while ago. I basically gave up on recovering a VM and nuked and repaved it using a LiveCD with a chroot, some cp -p'ing, etc. But yes.. it would be nice if I could have recovered the system at least with a static toolchain: cc, binutils [equivalent], mtree, install, etc. This is how I recovered the nasty broken box. The other one was easy to recover by reinstalling security/cyrus-sasl2. I'm quite sure that there is something very foul with something in LDAP or SASL2, since I can reproduce that proplem. I saw that rtdl-elf has got some quirks these days, I will try to go behind the date/version of the source tree when it was committed and check whether this is the problem. ... Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library iconv.3 does not exist. service ldconfig start ? Yes ... sorry ... in the heat of the fight I forgot ... but it doesn't make the problem go away. But most of the libs have never been touch! So what is the loader complaining about? ... I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, Simply
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 08/16/12 17:44, Glen Barber wrote: On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all portmaster -f apache-2.2 requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via There is pkg-static for recovering in this type of situation. Oh ... I'm new to pkg(ng). portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Is this a typo, or literal transcription? (The missing / between 'run' and 'ld-elf.so.hints', that is.) A typo, sorry. I had to type it from the screen of the broken box to the laptop. Error: shared library iconv.3 does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. Yes, I have been complaining about this for a while now... This is a so unneccessary issue. Why are people bothering themselfs with hiding a bit of information? If one isn't a cold-blood developer aware of all the neat knobs of FBSD and where to ask and where to look, a novice or not-so-well-informed guy like me run into frustration. The main page should have a hint present, where to find the newest stuff. Leaving the officiela page the way it is at the moment in this specific issue, it looks a bit unmaintained ... If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. If you can get booted into a recovery medium, you can mount /usr/src and /usr/obj from the hosed system, and should be able to installworld/installkernel into the hosed system with DESTDIR set. Glen I do this the very moment with the RELEASE CD I found at allbsd.org for the most recent FBSD 10.0-CURRENT as from 16.08.2012. I try to build the sources and install them into the mounted DESTDIR. Oliver ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Fri, Aug 17, 2012 at 09:44:40AM +0200, Hartmann, O. wrote: An installation failed due to pkg(ng) was missing libarchive.so via There is pkg-static for recovering in this type of situation. Oh ... I'm new to pkg(ng). No worries. It is a nice thing to know about, since after a big shlib bump during an upgrade, if all else is broken, you can still at least get /rescue stuff and pkg-static to upgrade third party software. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. If you can get booted into a recovery medium, you can mount /usr/src and /usr/obj from the hosed system, and should be able to installworld/installkernel into the hosed system with DESTDIR set. I do this the very moment with the RELEASE CD I found at allbsd.org for the most recent FBSD 10.0-CURRENT as from 16.08.2012. I try to build the sources and install them into the mounted DESTDIR. I have lately been creating memstick images for this exact type of thing. On -CURRENT and 9-STABLE, you can do: # make -C /usr/src buildworld buildkernel # make -C /usr/src/release NOSRC=yes NODOCS=yes NOPORTS=yes memstick Then take the resulting memory stick image to use for recovery. Glen ___ 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
HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all portmaster -f apache-2.2 requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library iconv.3 does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, oh ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all portmaster -f apache-2.2 requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via There is pkg-static for recovering in this type of situation. portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Is this a typo, or literal transcription? (The missing / between 'run' and 'ld-elf.so.hints', that is.) Error: shared library iconv.3 does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. Yes, I have been complaining about this for a while now... If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. If you can get booted into a recovery medium, you can mount /usr/src and /usr/obj from the hosed system, and should be able to installworld/installkernel into the hosed system with DESTDIR set. Glen ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 8/16/2012 10:33 AM, Hartmann, O. wrote: I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. http://pub.allbsd.org/FreeBSD-snapshots/ Bryan ___ 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
HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all portmaster -f apache-2.2 requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library iconv.3 does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, oh signature.asc Description: OpenPGP digital signature
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 11:33 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I ran into a very delicate and nasty situation. Please don't cross-post / double-post. Thanks, -Garrett ___ 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: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Thu, Aug 16, 2012 at 8:33 AM, Hartmann, O. ohart...@zedat.fu-berlin.de wrote: I ran into a very delicate and nasty situation. ... On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by install and/or mtree dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. I'm not drawing a correlation between this and unrelated coredumping processes. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! Don't make delete-old-lib unless you have it moved off to compat directories, or have rebuilt everything using the new libarchive. On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). truss the binaries to figure out exactly what's going wrong. A lot of this lost effort could be avoided (like others have posted on the list more than once), by having a centralized package distribution server, and by having VMs or jails and keeping snapshots with pre-upgrade state on the package building machine to avoid dead in the water scenarios like you're in right now. I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? I ran into this issue too a little while ago. I basically gave up on recovering a VM and nuked and repaved it using a LiveCD with a chroot, some cp -p'ing, etc. But yes.. it would be nice if I could have recovered the system at least with a static toolchain: cc, binutils [equivalent], mtree, install, etc. ... Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library iconv.3 does not exist. service ldconfig start ? But most of the libs have never been touch! So what is the loader complaining about? ... I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, Simply put: fix your infrastructure (as this isn't the first time you have complained about infrastructure issues on the MLs). A lot of these issues should not be issues if you set up your infrastructure properly to deal with building things only once, backup packages before installation, you had snapshots of your system, etc. This will help you avoid administration pain, and hopefully will result in less duplicated work. Cheers, -Garrett ___ 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
portmaster embarrassingly simple question (y- option)
=== Starting check for runtime dependencies === Gathering dependency list for archivers/unzip from ports === No dependencies for archivers/unzip === Installing package === Installation of archivers/unzip (unzip-6.0_1) succeeded === Delete unzip60.tar.gz? y/n [n] What option do I need to specify with -y to automatically answer those? I've tried --clean-distfiles, --clean-packages but it's not it. It usually happens when doing portmaster --packages-build --delete-build-only build. -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: portmaster embarrassingly simple question (y- option)
-d tells it to always delete old files without prompting. Thanks, Dean Weimer On Jul 3, 2012, at 5:29 AM, Jakub Lach jakub_l...@mailplus.pl wrote: === Starting check for runtime dependencies === Gathering dependency list for archivers/unzip from ports === No dependencies for archivers/unzip === Installing package === Installation of archivers/unzip (unzip-6.0_1) succeeded === Delete unzip60.tar.gz? y/n [n] What option do I need to specify with -y to automatically answer those? I've tried --clean-distfiles, --clean-packages but it's not it. It usually happens when doing portmaster --packages-build --delete-build-only build. -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: portmaster embarrassingly simple question (y- option)
On 07/03/2012 12:29 PM, Jakub Lach wrote: === Starting check for runtime dependencies === Gathering dependency list for archivers/unzip from ports === No dependencies for archivers/unzip === Installing package === Installation of archivers/unzip (unzip-6.0_1) succeeded === Delete unzip60.tar.gz? y/n [n] What option do I need to specify with -y to automatically answer those? Hi -d I've tried --clean-distfiles, --clean-packages but it's not it. It usually happens when doing portmaster --packages-build --delete-build-only build. Disclaimer: http://www.ose.nl/email ___ 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: portmaster embarrassingly simple question (y- option)
Hi Jakub, On Tue, Jul 3, 2012 at 12:45 PM, Dean E. Weimer dwei...@dweimer.net wrote: -d tells it to always delete old files without prompting. Thanks, Dean Weimer On Jul 3, 2012, at 5:29 AM, Jakub Lach jakub_l...@mailplus.pl wrote: === Starting check for runtime dependencies === Gathering dependency list for archivers/unzip from ports === No dependencies for archivers/unzip === Installing package === Installation of archivers/unzip (unzip-6.0_1) succeeded === Delete unzip60.tar.gz? y/n [n] What option do I need to specify with -y to automatically answer those? I've tried --clean-distfiles, --clean-packages but it's not it. It usually happens when doing portmaster --packages-build --delete-build-only build. usually I use: portmaster -dbg port -b create and keep a backup package of an installed port -g create a package of the new port -d always clean distfiles Best Regards Iqbal A. ___ 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: portmaster embarrassingly simple question (y- option)
Excellent, I knew I was missing something simple. Thanks! -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723916.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: portmaster embarrassingly simple question (y- option)
Now I see that I even used -d in my own portupdating wrapper, but forgot about it and it's meaning, embarrassing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723918.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: portmaster embarrassingly simple question (y- option)
On 03/07/2012 13:06, Bas Smeelen wrote:
On 07/03/2012 12:29 PM, Jakub Lach wrote:
What option do I need to specify with -y to automatically answer those?
-d
Add this to ${LOCALBASE}/etc/portmaster.rc
ALWAYS_SCRUB_DISTFILES=dopt
if that's something you're going to be doing all the time.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: Portmaster and update progress, suggestion.
2012-06-04 16:10, Leslie Jensen skrev: 2012-06-04 15:54, Warren Block skrev: % printf \033];Funny Title\007 Works! ___ 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 Can the reason for me not getting the title to change be that I very often use screen when updating ports? I've tried different combinations and I'm only able to get the title when I work locally. Screen and ssh does not change the title. My initial wish for some information about the build progress is still very much on the table. Thanks /Leslie ___ 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: Portmaster and update progress, suggestion.
On 06/06/2012 09:11, Leslie Jensen wrote:
My initial wish for some information about the build progress is still
very much on the table.
Try the attached patch. It essentially adds the progress info that is
being put in the TERM title to the in-line printout of the dependency
trail that was already there.
Let me know what you think,
Doug
--
This .signature sanitized for your protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf () {
+ echo -e \n\t${PM_PARENT_PORT}${1}
+
[ -n $PM_NO_TERM_TITLE ] return
case $TERM in cons*) return ;; esac
@@ -2283,7 +2285,7 @@
deps= (${dep_of_deps}/${num_of_deps})
if [ -n $PM_DEPTH ]; then
- echo ${PM_DEPTH} ${1#$pd/}
+ #echo ${PM_DEPTH} ${1#$pd/}
term_printf ${PM_DEPTH#* } ${1#$pd/}${deps}
else
[ -n $UPDATE_ALL ] term_printf ${1#$pd/}${deps}
@@ -2623,7 +2625,7 @@
[ -z $dep_of_deps ] dep_of_deps=0
export PM_PARENT_PORT num_of_deps dep_of_deps
- term_printf
+ #term_printf
}
if [ -n $PM_URB ]; then
@@ -2783,6 +2785,7 @@
numports=$(( $numports + 1 ))
init_term_printf $port ${numports}/${numports}
+ term_printf
($0 $ARGS $port) || update_failed=update_failed
. $IPC_SAVE
[ -n $update_failed ] fail Update for $port failed
@@ -2825,6 +2828,7 @@
num=$(( $num + 1 ))
init_term_printf $port ${num}/${numports}
+ term_printf
($0 $ARGS $port) || update_failed=update_failed
. $IPC_SAVE
[ -n $update_failed ] fail Update for $port failed
@@ -2978,6 +2982,7 @@
[ -n $DI_FILES ] (read_distinfos)
init_term_printf All
+ term_printf
ports_by_category
echo === Starting check of installed ports for available updates
___
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: Portmaster and update progress, suggestion.
On 06/06/2012 15:06, Doug Barton wrote:
On 06/06/2012 09:11, Leslie Jensen wrote:
My initial wish for some information about the build progress is still
very much on the table.
Try the attached patch.
Actually try this one instead. :)
--
This .signature sanitized for your protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf () {
+ case $1 in *\\*) echo -e \n\t${PM_PARENT_PORT}${1} ;; esac
+
[ -n $PM_NO_TERM_TITLE ] return
case $TERM in cons*) return ;; esac
@@ -2283,7 +2285,6 @@
deps= (${dep_of_deps}/${num_of_deps})
if [ -n $PM_DEPTH ]; then
- echo ${PM_DEPTH} ${1#$pd/}
term_printf ${PM_DEPTH#* } ${1#$pd/}${deps}
else
[ -n $UPDATE_ALL ] term_printf ${1#$pd/}${deps}
@@ -2527,19 +2528,16 @@
safe_exit
elif [ -n $PM_FIRST_PASS -a -z $PM_PACKAGES ]; then
echo === Initial dependency check complete for $portdir
- case $PM_DEPTH in *\\*) echo $PM_DEPTH ;; esac
else
echo === Dependency check complete for $portdir
- case $PM_DEPTH in
- *\\*) echo $PM_DEPTH ;;
- *) if [ $PM_PARENT_PORT = All ]; then
- local deps
- deps= (${dep_of_deps}/${num_of_deps})
- term_printf ${upg_port:-$portdir}${deps}
- else
- term_printf
- fi ;;
- esac
+
+ if [ $PM_PARENT_PORT = All ]; then
+ local deps
+ deps= (${dep_of_deps}/${num_of_deps})
+ term_printf ${upg_port:-$portdir}${deps}
+ else
+ term_printf
+ fi
fi
} # dependency_check()
___
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: Portmaster and update progress, suggestion.
2012-06-03 18:18, Warren Block skrev: On Sun, 3 Jun 2012, Warren Block wrote: On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. Oh, and xfce's Terminal has a preferences setting that can prevent dynamically-set titles from being displayed. ___ 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 I found that setting and changed it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? I'll test as soon as I've got the system up with X again. ___ 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: Portmaster and update progress, suggestion.
On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug -- This .signature sanitized for your protection ___ 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: Portmaster and update progress, suggestion.
2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from Terminal /Leslie ___ 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: Portmaster and update progress, suggestion.
2012-06-04 10:14, Leslie Jensen skrev: 2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from Terminal /Leslie ___ 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 After a restart of xfce I've got the Title to change, but I can only see the initial command ie portmaster All. /Leslie ___ 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: Portmaster and update progress, suggestion.
On Mon, 4 Jun 2012, Leslie Jensen wrote: 2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from Terminal Could be something in your prompt resetting it. Does % printf \033];Funny Title\007 change the title? ___ 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: Portmaster and update progress, suggestion.
2012-06-04 15:54, Warren Block skrev: % printf \033];Funny Title\007 Works! ___ 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: Portmaster and update progress, suggestion.
On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. ___ 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: Portmaster and update progress, suggestion.
On Sun, 3 Jun 2012, Warren Block wrote: On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. Oh, and xfce's Terminal has a preferences setting that can prevent dynamically-set titles from being displayed. ___ 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
Portmaster and update progress, suggestion.
I'm thinking about some kind of information on the build progress when one does larger updates like the newly recommendation in /usr/ports/UPDATING portmaster -r png- I myself have three machines with different capacity when it comes to building ports. How about a knobb one could choose that would give information after finishing building one port and before beginning on the next one, that would be something like: finishing foo port xx ports remaining or something in that order. At least it would informative for me to get an idea of how far in the process the machine is. Thanks /Leslie ___ 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: Portmaster and update progress, suggestion.
On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. hope this helps, Doug -- This .signature sanitized for your protection ___ 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: Portmaster and update progress, suggestion.
2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. hope this helps, Doug I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? Thanks /Leslie ___ 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
Portmaster Fetch
Hello, is there a chance that portmaster can be only fetch all Source which need update? I mean make fetch-recursiv has helped in the ports collection, when i think right, but can portmaster that with all packages they need update? Thanks for help. Regards Silvio ___ 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: Portmaster Fetch
On Mon, 28 May 2012 23:12:31 +0200, Silvio Siefke wrote: Hello, is there a chance that portmaster can be only fetch all Source which need update? I mean make fetch-recursiv has helped in the ports collection, when i think right, but can portmaster that with all packages they need update? Is portmaster -n (run through all steps, but do not make or install any ports) what you need? Maybe see man portmaster for more details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Portmaster Fetch
On 28 May 2012 14:12, Silvio Siefke siefke_lis...@web.de wrote: Hello, is there a chance that portmaster can be only fetch all Source which need update? I mean make fetch-recursiv has helped in the ports collection, when i think right, but can portmaster that with all packages they need update? portmaster -F -- Eitan Adler ___ 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
Preventing portmaster from using packages for specified ports
I'm happy to use the -P option to let portmaster use packages for most of my ports but there's a few that must be compiled from the port instead because I need to configure non default options, e.g. to enable GIMP plugin support in graphics/xsane Is there any way of forcing portmaster to never use packages for certain specified ports? -- Mike Clarke ___ 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: Preventing portmaster from using packages for specified ports
--On May 8, 2012 9:33:59 PM +0100 Mike Clarke jmc-freeb...@milibyte.co.uk wrote: I'm happy to use the -P option to let portmaster use packages for most of my ports but there's a few that must be compiled from the port instead because I need to configure non default options, e.g. to enable GIMP plugin support in graphics/xsane Is there any way of forcing portmaster to never use packages for certain specified ports? -- Would this work for you? From the manpage: For those who wish to be sure that specific ports are always compiled instead of being installed from packages the PT_NO_INSTALL_PACKAGE vari- able can be defined in the make(1) environment, perhaps in /usr/local/etc/ports.conf if using /usr/ports/ports-mgmt/portconf, or in /etc/make.conf. This setting is not compatible with the -PP/--packages-only option. pgpBUQ7LBK3b1.pgp Description: PGP signature
Re: Preventing portmaster from using packages for specified ports
On Tuesday 08 May 2012, John Webster wrote: Would this work for you? From the manpage: For those who wish to be sure that specific ports are always compiled instead of being installed from packages the PT_NO_INSTALL_PACKAGE vari- able can be defined in the make(1) environment, perhaps in /usr/local/etc/ports.conf if using /usr/ports/ports-mgmt/portconf, or in /etc/make.conf. This setting is not compatible with the -PP/--packages-only option. Yes, that looks like exactly what I need. I don't know how I missed it, I must have searched through the manpage several times and had a total blind spot for that paragraph - sorry for looking so dumb. -- Mike Clarke ___ 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: Preventing portmaster from using packages for specified ports
--On May 8, 2012 10:51:16 PM +0100 Mike Clarke jmc-freeb...@milibyte.co.uk wrote: On Tuesday 08 May 2012, John Webster wrote: Would this work for you? From the manpage: For those who wish to be sure that specific ports are always compiled instead of being installed from packages the PT_NO_INSTALL_PACKAGE vari- able can be defined in the make(1) environment, perhaps in /usr/local/etc/ports.conf if using /usr/ports/ports-mgmt/portconf, or in /etc/make.conf. This setting is not compatible with the -PP/--packages-only option. Yes, that looks like exactly what I need. I don't know how I missed it, I must have searched through the manpage several times and had a total blind spot for that paragraph - sorry for looking so dumb. -- Mike Clarke I know how that is, I've missed stuff in the manpages too. grin sorry for looking so dumb. Not dumb. You had a question and you asked it on freebsd-questions looking for an answer. That's smart in my book. That's what the list is for. Cheers, jw ___ 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
portmaster won't update libc.so.7
When I run:
portmaster -a --no-confirm
I get the error
Installing updates: chflags...///lib/libc.so.7: Operation not permitted
Changing chflags (presumably schg, but I tried the others) doesn't
appear to make any difference.
I'm not running any servers in jails.
Any ideas?
Thanks,
Jorge
--
Jorge Luis González list+free...@jorge.cc
http://www.jorge.cc/ * ftp://ftp.jorge.cc/{pub,incoming}
IRC: #vim satyriasis * XMPP: jl-sa...@jabber.org
GPG KEY - 0x4AD9C195 * ICBM: 42.592627, -72.588859
This email optimized for teletypes.
___
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
portmaster won't update libc.so.7
Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) Robert huff ___ 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: portmaster won't update libc.so.7
On Wed, 2 May 2012 10:03:44 -0400 Robert Huff roberth...@rcn.com wrote: Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) Robert huff My first question as well. This is highly irregular. -- Conrad J. Sabatier conr...@cox.net ___ 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: portmaster won't update libc.so.7
On Wed, 2 May 2012, Conrad J. Sabatier wrote: On Wed, 2 May 2012 10:03:44 -0400 Robert Huff roberth...@rcn.com wrote: Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) My first question as well. This is highly irregular. Some of the misc/compat ports install an old libc.so, but not in place of the real one. ___ 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: portmaster won't update libc.so.7
On 02.05.2012 14:59, Warren Block wrote: On Wed, 2 May 2012, Conrad J. Sabatier wrote: On Wed, 2 May 2012 10:03:44 -0400 Robert Huff roberth...@rcn.com wrote: Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) My first question as well. This is highly irregular. Some of the misc/compat ports install an old libc.so, but not in place of the real one. ___ 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 libc.so.7 is still current in 9.0, so none of the misc/compat ports should contain it, A quick search shows just that. #cd /usr/ports/misc #grep -H libc.so compat*/* compat4x/pkg-plist.freebsd5:%%LIBDIR%%/compat/libc.so.4 compat5x/Makefile:# NOTE: libc.so.5 is built with _PATH_LOCALE defined to compat5x/pkg-plist:@unexec chflags noschg %D/lib/compat/libc.so.5 compat5x/pkg-plist:lib/compat/libc.so.5 compat5x/pkg-plist:%%AMD64%%lib32/compat/libc.so.5 compat6x/pkg-plist.alpha:lib/compat/libc.so.6 compat6x/pkg-plist.amd64:lib/compat/libc.so.6 compat6x/pkg-plist.amd64:lib32/compat/libc.so.6 compat6x/pkg-plist.i386:lib/compat/libc.so.6 compat6x/pkg-plist.sparc64:lib/compat/libc.so.6 -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: portmaster best practices
Volodymyr Kostyrko wrote: [dd] NO_BACKUP means don't create a temporary package when deleting something. This is unsuitable for me as /usr/ports in my network is distributed via NFS ro. I also share /usr/ports via NFS ro, but I have defined PACKAGES=/var/tmp/packages in portmaster.rc to store backups of deleted packages, just in case. [dd] -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: portmaster best practices
Volodymyr Kostyrko wrote: If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Greatly depend on where am I. All my systems are staying up-to-date whereas when I'm visiting someones system I prefer to update only required pieces of software. Anyway if you tell portmaster to update port x it would try to update all ports it depends on. Does it often screw things up when updating dependencies (both ascending and descending ones)? Do you recommend to always update the ascending dependencies (portmaster -r) also? [dd] The better way of debugging such problems for me is pkg_libchk from sysutils/bsdadminscripts. I use sysutils/libchk when I have to, but it is a tedious manual job I would like to avoid. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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
