On Mon, Jun 18, 2007 at 05:54:10PM +0200, Moritz Grimm wrote: > the changes to the pkg tools and ports infrastructure, while really great, > introduced possibly unintended side-effects. Running "pkg_add -F update -F > updatedepends -u", which I have been using for a long time to upgrade > packages without problems, no longer stops if an installed package cannot > be updated because of either ambiguities or missing packages (at least '-F > alwaysupdate' appears to be permanently in effect.)
This is something Theo demanded. He wants for updates to proceed even if some packages cannot be found. Take that specific beef with him. This does solve the very specific fringe case of third-party firmwares not stopping an update. > When I then upgraded my laptop to -current around Hackathon times, I > observed new behavior. During pkg_add -u, upgrades of the packages were > queued as "A, C, B", as usual. However, during the actual upgrade, > upgrading A failed because of a plist-related error/warning (sorry, I > don't remember the actual wording) - it couldn't read the plist of C-2, > which hadn't been upgraded, yet. Then, C and B were upgraded and after > rerunning pkg_add -u, A was upgraded as well. AFAIK this is new behavior > has something to do with the new make-plists-on-the-fly feature. Is this > intended, i.e. necessary? Looks like you run into a temporary bug (the plist-related error/warning that you don't remember), this makes all the rest of that specific discussion irrelevant... without knowing what was the contents of various +REQUIRING/+REQUIRED files before/after the update, I can't comment on what happened.
