Re: portmanager endlessly looping in x11
On 08/26/10 01:17, jhell wrote: On 08/25/2010 21:27, Chuck Robey wrote: I have an interesting thing here: I seem to have found an endless loop in portmanager. It's *entirely* possible that I'm myself causing this, so I'll explain, and if you can come up with any hints, I'll be happy to test them, because I really do like using portmanager. CC:The maintainer of ports-mgmt/portmanager is a good start. Maybe He/She can give you some insight of the working of portmanager. I am not sure how portmanager keeps the package database up to date but sometimes dependencies can get messed up in the database that can cause a loop and if not handled correctly by the upgrade process can cause a lot of grief. In portmaster you could be using --check-depends and in portupgrade you could use -Ffu but you don't seem to be using any of the suggested ports-mgmt upgrade utilities so good luck. ``emphasis on portmaster'' -- written by dougb@, so you know it works!. The problem I saw, I'm pretty sure is caused by a discrepancy (in portmanager) between how deeply it looks for dependencies versus how deeply it looks it looks to decide to actually rebuild those discovered dependencies. Merely noting the need to rebuild seems not to be the same thing as actually doing it. It found things maybe 3 levels deep, but if it's less than 2 levels down, it won't rebuild it, it'll merely realize that it *should* do it. I switched to using portmaster (this looks alike, I'm making no mistake tho, moved from portmanager to portmaster) which doesn't seem to have this uneveness, so while it takes a whole lot longer to work than portmanager (it uses slow but sure shell utils for it's databases) it really does a far more reliable job of things. You could get to rely on it. It sure took me a good while to track down the reasons that portmanager was fixing on, in deciding that something was out of date, and the frustration was sufficient to cause me to forgive the way that portmaster is much more slow. One really big irritation was how portmanager would rebuild something completely successfully 3 times, but since it would fail its dependency scans, it never would recognize that any of those looping apps had been rebuilt. Very puzzling, until I realized about the dependency problems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmanager endlessly looping in x11
On Wed, 08 Sep 2010 17:41:32 -0400 Chuck Robey chu...@telenix.org articulated: On 08/26/10 01:17, jhell wrote: On 08/25/2010 21:27, Chuck Robey wrote: I have an interesting thing here: I seem to have found an endless loop in portmanager. It's *entirely* possible that I'm myself causing this, so I'll explain, and if you can come up with any hints, I'll be happy to test them, because I really do like using portmanager. CC:The maintainer of ports-mgmt/portmanager is a good start. Maybe He/She can give you some insight of the working of portmanager. I am not sure how portmanager keeps the package database up to date but sometimes dependencies can get messed up in the database that can cause a loop and if not handled correctly by the upgrade process can cause a lot of grief. In portmaster you could be using --check-depends and in portupgrade you could use -Ffu but you don't seem to be using any of the suggested ports-mgmt upgrade utilities so good luck. ``emphasis on portmaster'' -- written by dougb@, so you know it works!. The problem I saw, I'm pretty sure is caused by a discrepancy (in portmanager) between how deeply it looks for dependencies versus how deeply it looks it looks to decide to actually rebuild those discovered dependencies. Merely noting the need to rebuild seems not to be the same thing as actually doing it. It found things maybe 3 levels deep, but if it's less than 2 levels down, it won't rebuild it, it'll merely realize that it *should* do it. I switched to using portmaster (this looks alike, I'm making no mistake tho, moved from portmanager to portmaster) which doesn't seem to have this uneveness, so while it takes a whole lot longer to work than portmanager (it uses slow but sure shell utils for it's databases) it really does a far more reliable job of things. You could get to rely on it. It sure took me a good while to track down the reasons that portmanager was fixing on, in deciding that something was out of date, and the frustration was sufficient to cause me to forgive the way that portmaster is much more slow. One really big irritation was how portmanager would rebuild something completely successfully 3 times, but since it would fail its dependency scans, it never would recognize that any of those looping apps had been rebuilt. Very puzzling, until I realized about the dependency problems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Portmanager did have a nasty bug that involved looping. It was fixed ages ago though. Are you running the latest version; i.e., 0.4.1_9 on your system? Run portmanager -v to confirm. Without the '-p' option, portmanager only looks 1 level deep. with the '-p' option, it will search the entire dependency chain. I always use the '-p' option and never experience any problems described by you. -- Jerry ✌ freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmanager endlessly looping in x11
On 09/08/10 18:15, Jerry wrote: Portmanager did have a nasty bug that involved looping. It was fixed ages ago though. Are you running the latest version; i.e., 0.4.1_9 on your system? Run portmanager -v to confirm. Without the '-p' option, portmanager only looks 1 level deep. with the '-p' option, it will search the entire dependency chain. I always use the '-p' option and never experience any problems described by you. Not sure if the -p does that or not, but I *did* read (more than just a few times) about the -p (meaning pristine) option, and from the reading, it doesn't tell me that it might affect looping, and I didn't see anything about it in the man page. I didn't just try it and immediately mail, I tried to DTRT. Doesn't matter too much to me now, because I really love the fact that I did 4 *very* large (meaning lengthy dependency lists) ports, with 100% 1st-time accuracy, which means I will stay with portmaster for sure now. Also, because those ports are now all installed, and I don't want to take a few days to rebuild everything all over again. It looks like, in the default case, portmanager detects more problems than it deals with, which is not a desirable default action. It's probably a needed default action for some use case ... do you happen to know what that is? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmanager endlessly looping in x11
On Wed, 08 Sep 2010 17:41:32 -0400 Chuck Robey chu...@telenix.org wrote: I'm making no mistake tho, moved from portmanager to portmaster) which doesn't seem to have this uneveness, so while it takes a whole lot longer to work than portmanager (it uses slow but sure shell utils for it's databases) I don't know why people think portmanager is fast. It may be written in C, but in most upgrades it builds *many* more ports than portmaster or portupgrade would do. The point of a portmanager is to upgrade correctly with as little human intervention as is possible; and it sacrifices a lot of cpu cycles to that end. it really does a far more reliable job of things. Something it does, sometimes it doesn't. portmanager will handle a lot upgrades correctly even when instructions in UPDATING that are required for portmaster are ignored. With portupgrade I've had a few problems where the UPDATING entry was made after I updated the ports. These have been much more serious than harmless looping. One really big irritation was how portmanager would rebuild something completely successfully 3 times, but since it would fail its dependency scans, it never would recognize that any of those looping apps had been rebuilt. Very puzzling, until I realized about the dependency problems. I didn't follow what you were were saying, but portmanager has at least two features that can lead to looping. One is that it can rebuild ports when it detects a dynamic change in port dependencies. The other is when it tries to resolve conflicts by package deletion and iterative rebuilding. There are probably more. AFAIK it shouldn't actually loop endlessly because of its three-strikes database. In my experience portmanager goes through good and bad patches as the installed ports change and their dependencies evolve. Even when it's not completing successfully by it's own criteria, it usually does the job without leaving any real problems of its own making. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portmanager endlessly looping in x11
I have an interesting thing here: I seem to have found an endless loop in portmanager. It's *entirely* possible that I'm myself causing this, so I'll explain, and if you can come up with any hints, I'll be happy to test them, because I really do like using portmanager. What my goal is, is to update the qt4 port, but one of the dependencies it finds is x11/libX11 ... and two (the only 2) dependencies it finds unsatisfied for libX11 are x11/libXau and x11/libXtrans. Trouble is, it endlessly (and seemingly quite successfully) rebuilds both of these, but them can't seem to find either to mark them as satisfied (to move onlto building libX11). I tried to cd into both of these dirs and build them directly using make clean/package/clean, and it succeeds fine, but portmanager *still* can't get past them. My ports are up to date, no more than a week old, I use cvs to keep the sources nicely up to date. I'd really appreciate any suggestions you can offer. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmanager endlessly looping in x11
On 08/25/2010 21:27, Chuck Robey wrote: I have an interesting thing here: I seem to have found an endless loop in portmanager. It's *entirely* possible that I'm myself causing this, so I'll explain, and if you can come up with any hints, I'll be happy to test them, because I really do like using portmanager. What my goal is, is to update the qt4 port, but one of the dependencies it finds is x11/libX11 ... and two (the only 2) dependencies it finds unsatisfied for libX11 are x11/libXau and x11/libXtrans. Trouble is, it endlessly (and seemingly quite successfully) rebuilds both of these, but them can't seem to find either to mark them as satisfied (to move onlto building libX11). I tried to cd into both of these dirs and build them directly using make clean/package/clean, and it succeeds fine, but portmanager *still* can't get past them. My ports are up to date, no more than a week old, I use cvs to keep the sources nicely up to date. I'd really appreciate any suggestions you can offer. CC: The maintainer of ports-mgmt/portmanager is a good start. Maybe He/She can give you some insight of the working of portmanager. I am not sure how portmanager keeps the package database up to date but sometimes dependencies can get messed up in the database that can cause a loop and if not handled correctly by the upgrade process can cause a lot of grief. In portmaster you could be using --check-depends and in portupgrade you could use -Ffu but you don't seem to be using any of the suggested ports-mgmt upgrade utilities so good luck. ``emphasis on portmaster'' -- written by dougb@, so you know it works!. Regards, -- jhell,v ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
