Skip site navigation (1) Skip section navigation (2)

FreeBSD GNOME Project: GNOME 2.32 Upgrading FAQ

Contents

  1. What is new in GNOME 2.32?
  2. How do I upgrade to GNOME 2.32?
  3. The upgrade failed; what do I do?
  4. List of known GNOME 2.32 problems and their solutions
  5. I have found a bug; whom should I alert?
  6. I want the fame and glory of the FreeBSD GNOME team! What can I do to participate?

Full Text

  1. What is new in GNOME 2.32?

    Although the canonical summary of new features can be found at http://library.gnome.org/misc/release-notes/2.32/

  2. How do I upgrade to GNOME 2.32?

    The answer is relatively simple:

    1. To build GNOME 2.32, you need to obtain the latest ports tree skeleton. This is most easily accomplished with portsnap(8) or CVSup. Simply obtain the latest ports tree, and you are ready to go.

      If you are a portupgrade(1) users, Then do the following:

      # pkgdb -fF
# pkg_deinstall -f0 gtkmm-2.20\* gtk-2.20\*
# portupgrade -aOW

      NOTE: it is recommended to run portupgrade -a to make sure you get all the necessary ports. The -W option simply makes things a bit faster by not doing a make clean after each port build.

      If you are a portmaster(8) user, make sure you have least 3.1 version. Then do the following:

      # pkg_delete -f gtkmm-2.20\* gtk-2.20\*
# portmaster -a

  3. The upgrade failed; what do I do?

    Unfortunately, this is not only possible, it is highly probable. There are many possible valid GNOME configurations, and even more invalid starting points. If the script fails, follow the instructions in the error message to let the FreeBSD GNOME team know about the failure.

    The majority of build failures will be dependency-related issues. One simple way to resolve the problem is to remove the offending port, re-run portupgrade or portmaster, and then reinstall the port when the upgrade process is complete.

  4. List of GNOME 2.32 problems and their solutions

    Although GNOME 2.32 is certainly the best release to date (of course), there are a couple regressions that slipped in, both in the GNOME code and in its implementation within FreeBSD. Some of the more visible issues are:

    • Clutter based applications like mutter and a number of gnome-games, will crash when using Software Rasterizer rendering. You can check it with glxinfo | grep render. A solution is being worked on.
    • Brasero has a bug that it crashes when creating new burn projects. Premade iso burning works as expected.
    • PackageKit where ported to FreeBSD. It does have some rough edges still.

  5. I have found a bug; whom should I alert?

    Please read the FreeBSD GNOME Project's documentation on reporting bugs.

  6. I want the fame and glory of being part of the FreeBSD GNOME team! What can I do to participate?

    Please read our list of ways to get involved!