On Sun, May 6, 2012 at 9:59 AM, Pierre Abbat <p...@phma.optus.nu> wrote: > On Wednesday, May 02, 2012 22:02:18 Justin Sherrill wrote: >> My preferred method, when binary packages aren't available, is to >> update /usr/pkgsrc to the appropriate release and then use >> pkg_rolling-replace to upgrade the packages I use. It'll take a >> little bit to build programs, but the amount of actual downtime will >> be minimal. You can say, "upgrade everything" using that, though it's >> more manageable if you tackle it major app by major app, in my >> opinion. You certainly have enough space to update. > > What do you count as downtime? When it's in the middle of rebuilding kde, and > I want to use kde, I consider kde down. I've been in that situation with > Source Mage, and I got kwrite windows with the toolbar icons totally mixed up. > > I'm running pkg_check before starting to rebuild, and I got this: > > WARNING: No graphics/kdegraphics4/Makefile - package moved or obsolete? > WARNING: No misc/kdeutils4/Makefile - package moved or obsolete? > WARNING: No mail/postfix-current/Makefile - package moved or obsolete? > WARNING: No x11/kdebase-runtime4/Makefile - package moved or obsolete? > WARNING: No x11/kdebase-workspace4/Makefile - package moved or obsolete? > WARNING: No x11/kdebase4/Makefile - package moved or obsolete? > WARNING: No x11/kdebindings4-python/Makefile - package moved or obsolete? > > The kde packages are still in wip (which I just updated); there is a > mail/postfix.
When packages get name changes, there's no automated way to transition. I assume what happened is postfix-current became postfix and some of the KDE packages were renamed. Looking at the kde4 meta-package, I don't see any of those listed as dependencies.
