Re: Portmanager - not working after ports change
On Mon, 5 Feb 2007 09:14:16 -0800 (PST) White Hat [EMAIL PROTECTED] wrote: There was a change in the ports system - /usr/ports/UPDATING 20070205 - which now renders portmanager unable to run correctly. While it is possible to update a single port; i.e., portmanager /path/to-port/, if I attempt to do a general ports update; i.e., portmanager -u, I receive the following error message: percentDone-=0 = 100 - ( 100 * ( oldPortsDbQTY-=6 / oldPortsDbTOTALIZER-=6 )) cd: can't cd to /usr/ports/sysutils/portmanager rBsdPortMkPatch 0.4.1_7 error: bsd.port.mk /usr/ports/Mk unable to restored from back up cp /usr/local/share/portmanager/bsd.port.mk-BACKUP /usr/ports/Mk/bsd.port.mk I tried deinstalling portmanager and then installing it from its new port directory; however, that failed to alleviate the problem. Has anyone else experienced this problem, and perhaps have a solution? Probably it's just that someone need to patch it to change sysutils/portmanager to ports-mgmt/portmanager in the source. As a workaround try linking portmanager's new port directory to where its old one was. As there will be a MOVED entry it's probably best to use it with the new origin, but make sure portmanager is up-to-date before running it on multiple ports, it wont be able to detect a self-update, and it doesn't like to do that as part of a general ports' update. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmanager - not working after ports change
On Tuesday February 06, 2007 at 08:19:27 (AM) RW wrote: Probably it's just that someone need to patch it to change sysutils/portmanager to ports-mgmt/portmanager in the source. As a workaround try linking portmanager's new port directory to where its old one was. As there will be a MOVED entry it's probably best to use it with the new origin, but make sure portmanager is up-to-date before running it on multiple ports, it wont be able to detect a self-update, and it doesn't like to do that as part of a general ports' update. I reported this problem around 10 am. yesterday. Sometime around 2 pm. a patch was submitted. An updated version of 'portmanager' was in the port's system by 4 pm. Personally, I consider that a rather quick fix. Yes, you will have to do a regular 'make install' to get the newer version installed. You have to do a 'make deinstall' to remove the older version first though. -- Gerard Mail from '@gmail' is rejected and/or discarded here. Don't waste your time! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmanager - not working after ports change
On Tue, 06 Feb 2007 08:37:15 -0500 Gerard Seibert [EMAIL PROTECTED] wrote: I reported this problem around 10 am. yesterday. Sometime around 2 pm. a patch was submitted. An updated version of 'portmanager' was in the port's system by 4 pm. Personally, I consider that a rather quick fix. I see it has a maintainer now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Portmanager - not working after ports change
There was a change in the ports system - /usr/ports/UPDATING 20070205 - which now renders portmanager unable to run correctly. While it is possible to update a single port; i.e., portmanager /path/to-port/, if I attempt to do a general ports update; i.e., portmanager -u, I receive the following error message: percentDone-=0 = 100 - ( 100 * ( oldPortsDbQTY-=6 / oldPortsDbTOTALIZER-=6 )) cd: can't cd to /usr/ports/sysutils/portmanager rBsdPortMkPatch 0.4.1_7 error: bsd.port.mk /usr/ports/Mk unable to restored from back up cp /usr/local/share/portmanager/bsd.port.mk-BACKUP /usr/ports/Mk/bsd.port.mk I tried deinstalling portmanager and then installing it from its new port directory; however, that failed to alleviate the problem. Has anyone else experienced this problem, and perhaps have a solution? Thanks! -- White Hat [EMAIL PROTECTED] Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmanager - not working after ports change
White Hat wrote: There was a change in the ports system - /usr/ports/UPDATING 20070205 - which now renders portmanager unable to run correctly. While it is possible to update a single port; i.e., portmanager /path/to-port/, if I attempt to do a general ports update; i.e., portmanager -u, I receive the following error message: percentDone-=0 = 100 - ( 100 * ( oldPortsDbQTY-=6 / oldPortsDbTOTALIZER-=6 )) cd: can't cd to /usr/ports/sysutils/portmanager rBsdPortMkPatch 0.4.1_7 error: bsd.port.mk /usr/ports/Mk unable to restored from back up cp /usr/local/share/portmanager/bsd.port.mk-BACKUP /usr/ports/Mk/bsd.port.mk I tried deinstalling portmanager and then installing it from its new port directory; however, that failed to alleviate the problem. Has anyone else experienced this problem, and perhaps have a solution? Thanks! i recommend switching to portmaster. its actively maintained and a lot better than portmanager ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmanager - not working after ports change
On Monday February 05, 2007 at 01:33:25 (PM) Eric wrote: i recommend switching to portmaster. its actively maintained and a lot better than portmanager I tried portmaster once, and found it slower and not as through as portmanager at fully updating a system. I just discovered the same problem as the OP reported. I filled a PR on it immediately as well as notifying the port maintainer. -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmanager - not working after ports change
Gerard Seibert wrote: On Monday February 05, 2007 at 01:33:25 (PM) Eric wrote: i recommend switching to portmaster. its actively maintained and a lot better than portmanager I tried portmaster once, and found it slower and not as through as portmanager at fully updating a system. I just discovered the same problem as the OP reported. I filled a PR on it immediately as well as notifying the port maintainer. when was the last time you used it? its had several great updates recently. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
