Re: Portmanager Status Report Gone - Fixed.
--As of January 15, 2012 10:09:06 AM -0500, freebsd-questions@freebsd.org is alleged to have said: I was trying out portmaster to see if it worked better than my current tool of choice for keeping my ports up to date (portmanager) and when I went back to portmanager I can no longer get it to give me a 'Port Status Report', or to update anything. It just collects the installed port data, and stops. Any ideas on what I may have messed up? I'd like to upgrade my ports to the latest versions before upgrading to 9.0 (and I'd want portmanager working afterwards to help me fix any port-related problems that come up.) I'm on 8.2. --As for the rest, it is mine. Not really 'solved' in that I still don't know what the problem was, but running portupgrade once fixed it. (I let it upgrade a couple of ports, but not all of them.) Leaving this here for whomever has this problem next. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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
Portmanager Status Report Gone
I was trying out portmaster to see if it worked better than my current tool of choice for keeping my ports up to date (portmanager) and when I went back to portmanager I can no longer get it to give me a 'Port Status Report', or to update anything. It just collects the installed port data, and stops. Any ideas on what I may have messed up? I'd like to upgrade my ports to the latest versions before upgrading to 9.0 (and I'd want portmanager working afterwards to help me fix any port-related problems that come up.) I'm on 8.2. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: Portmanager Status Report Gone
On Sun, 15 Jan 2012 10:09:06 -0500 Daniel Staal articulated: I was trying out portmaster to see if it worked better than my current tool of choice for keeping my ports up to date (portmanager) and when I went back to portmanager I can no longer get it to give me a 'Port Status Report', or to update anything. It just collects the installed port data, and stops. Any ideas on what I may have messed up? I'd like to upgrade my ports to the latest versions before upgrading to 9.0 (and I'd want portmanager working afterwards to help me fix any port-related problems that come up.) I'm on 8.2. Exactly how are you invoking portmanager? Usually, just give it it the -s flag will get you a list of port and there status as you probably know. If you just want to update everything before updating FreeBSD itself, I would suggest running it as: portmanager -u -l -p -y Obviously, update your ports tree prior to running that command. At the very least, you will end up with a log file telling you what failed to update properly. I use portmanager myself because it just works when other port management tools fail. -- 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: Portmanager Status Report Gone
--As of January 15, 2012 10:33:32 AM -0500, Jerry is alleged to have said: Exactly how are you invoking portmanager? Usually, just give it it the -s flag will get you a list of port and there status as you probably know. Yep. I have that in a weekly cron command, so I know what's out of date. ;) Basically, any way I invoke portmanager is showing the problem: If I invoke with -s, the status doesn't show. If I invoke with -u, it doesn't upgrade anything. Either way the result is the same: It gathers all the data on the ports (at least to 1), and then prints the header for the next section and quits, without actually doing anything. If you just want to update everything before updating FreeBSD itself, I would suggest running it as: portmanager -u -l -p -y Obviously, update your ports tree prior to running that command. At the very least, you will end up with a log file telling you what failed to update properly. The problem is that it's not *getting* to the updating, somehow. It gathers all the info on what it needs to know for the updating, and then stops. No error message, no output, no log, just stop. Running that command (or any other) doesn't result in portmanager actually *doing* anything. Here is the last four lines of output of a `portmanager -u -l`: 1 sane-backends-1.0.22 /graphics/sane-backends Port Status Report The log noted two broken ports (geany-plugins, both times). No other output. I use portmanager myself because it just works when other port management tools fail. This has been my experience as well. ;) The one thing I don't like about it is that it tends to need someone to watch it: If a port has changed it's config options, or added a new dependency that I haven't configured before, it will pull up the config screen and wait for input. I'd heard some of the other port management tools went and did that all at the beginning, which would mean I wouldn't have to sit and watch the screen as much. Unfortunatly, they appear to have more annoying behaviors. (portmaster tended to die on the smallest problem, where portmanager would have just logged a failure and gone on.) I'm mostly happy with portmanager. I just want it *back.* Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: Portmanager Status Report Gone
On Sun, 15 Jan 2012 11:48:55 -0500 Daniel Staal articulated: Well, you might try and deinstall and then reinstall portmanager. Perhaps something got corrupted, although I don't know why that might have happened. I have BATCH=yes set in the /etc/make.conf file to avoid receiving those annoying config screens. Of course that does require you to insure that your ports are configured the way you want them prior to updating them. I don't find it a problem; however, others might. By the way, how do you update your ports tree? Perhaps something got corrupted there. I use portsnap myself, so you could use it to just create a new tree thereby over writing the old one. Just a thought. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Psychiatrists say that one out of four people are mentally ill. Check three friends. If they're OK, you're it. ___ 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: Portmanager Status Report Gone
--As of January 15, 2012 12:25:47 PM -0500, Jerry is alleged to have said: Well, you might try and deinstall and then reinstall portmanager. Perhaps something got corrupted, although I don't know why that might have happened. No joy. Worth a try though. ;) My suspicion is that it's a permissions issue someplace, somehow: I was trying portmaster in it's 'run as wheel, sudo to root when needed' mode, and it kept throwing permissions errors at me which I fixed for a while. (Before reverting to just running it as root.) Of course, I'm running *portmanager* as root, so... (Both under sudo, and from root's cron.) I have BATCH=yes set in the /etc/make.conf file to avoid receiving those annoying config screens. Of course that does require you to insure that your ports are configured the way you want them prior to updating them. I don't find it a problem; however, others might. Interesting. I'll keep that in mind. Something to take a look at once I've gotten this solved. ;) By the way, how do you update your ports tree? Perhaps something got corrupted there. I use portsnap myself, so you could use it to just create a new tree thereby over writing the old one. Just a thought. I have csup set to run once a week in cron. I don't think that corrupted anything: `portmanager -s -y` ran fine before I ran portmaster, and I didn't update the tree in between. But blowing away the tree and re-creating it is starting to sound like something worth a try. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: Portmanager Status Report Gone
On Sun, 15 Jan 2012 13:01:23 -0500 Daniel Staal articulated: I have csup set to run once a week in cron. I don't think that corrupted anything: `portmanager -s -y` ran fine before I ran portmaster, and I didn't update the tree in between. But blowing away the tree and re-creating it is starting to sound like something worth a try. You don't have to manually erase the tree. I believe that: portsnap fetch extract is all you need to do to replace the ports tree with a fresh copy. It won't hurt anything since it doesn't touch the configuration files. -- 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: Portmanager Status Report Gone
--As of January 15, 2012 3:35:20 PM -0500, Jerry is alleged to have said: You don't have to manually erase the tree. I believe that: portsnap fetch extract is all you need to do to replace the ports tree with a fresh copy. It won't hurt anything since it doesn't touch the configuration files. --As for the rest, it is mine. Done, and it didn't fix my problem. Something's obviously gone seriously weird with my system. What would happen if I did blow away the config files? What's the minimum necessary for my system to be able to manage it's ports collection? I really don't want to reinstall from scratch over this (If nothing else, it's my main fileserver. I've got backups, but that would take ages.), but I'm thinking rebuilding my ports database from bare bones sounds like it might be a good idea. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: portmanager status?
On Thu, Jan 19, 2006 at 08:44:09PM -0800, Micah wrote: Craig Deal wrote: I just ran portmanager -s and it said that it has been removed from the ports collection. The MOVED file said sysutils/portmanager||2006-01-19|Author withdrew permission to distribute. Does this mean it will not be available any more, or is this temporary? Does anyone have a recommendation for a replacement for a novice user. Portmanager was very easy to use and I never had a problem with it. Thanks, Craig Check out http://portmanager.sunsite.dk/preface.html I have decided to remove portmanager from the FreeBSD ports tree because I do not get along with the people in charge of FreeBSD ports. Sounds pretty permanent to me. Someone else might take over development..assuming it was under an open source license, there's nothing the author can do to stop them. Kris pgplCcaLFzGCp.pgp Description: PGP signature
Re: portmanager status?
On Thu, Jan 19, 2006 at 08:44:09PM -0800, Micah wrote: Craig Deal wrote: I just ran portmanager -s and it said that it has been removed from the ports collection. The MOVED file said sysutils/portmanager||2006-01-19|Author withdrew permission to distribute. Does this mean it will not be available any more, or is this temporary? Does anyone have a recommendation for a replacement for a novice user. Portmanager was very easy to use and I never had a problem with it. Thanks, Craig Check out http://portmanager.sunsite.dk/preface.html I have decided to remove portmanager from the FreeBSD ports tree because I do not get along with the people in charge of FreeBSD ports. Sounds pretty permanent to me. Use portupgrade. Eww... :) portupgrade with its ruby dependency? Actually portmanager was/is a very good replacement for portupgrade, lightweight, C-based, and its author was pretty helpful in the past providing quick fixes and help on [EMAIL PROTECTED] HTH, Micah Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager status?
Micah wrote: Check out http://portmanager.sunsite.dk/preface.html I have decided to remove portmanager from the FreeBSD ports tree because I do not get along with the people in charge of FreeBSD ports. Sounds pretty permanent to me. Use portupgrade. The web site in question seems to have been updated to state that portmanager will remain in (return to?) the FreeBSD ports collection. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portmanager status?
I just ran portmanager -s and it said that it has been removed from the ports collection. The MOVED file said sysutils/portmanager||2006-01-19|Author withdrew permission to distribute. Does this mean it will not be available any more, or is this temporary? Does anyone have a recommendation for a replacement for a novice user. Portmanager was very easy to use and I never had a problem with it. Thanks, Craig ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager status?
On 1/19/06, Kris Kennaway [EMAIL PROTECTED] wrote: Try portupgrade. It's what most people use. Kris Thanks, I'll give it a try. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager status?
Craig Deal wrote: I just ran portmanager -s and it said that it has been removed from the ports collection. The MOVED file said sysutils/portmanager||2006-01-19|Author withdrew permission to distribute. Does this mean it will not be available any more, or is this temporary? Does anyone have a recommendation for a replacement for a novice user. Portmanager was very easy to use and I never had a problem with it. Thanks, Craig Check out http://portmanager.sunsite.dk/preface.html I have decided to remove portmanager from the FreeBSD ports tree because I do not get along with the people in charge of FreeBSD ports. Sounds pretty permanent to me. Use portupgrade. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
