On Mon, Oct 11, 2010 at 16:36:09 +0200, Josselin Mouette wrote: > the following needs to be added to the release notes concerning GNOME. > > 1) You need to restart your session after the upgrades, otherwise > applications will start crashing. See #550313.
I guess this needs to be added to the 'upgrading' section? Care to work on a patch? > 2) Systems upgraded from lenny will keep GDM 2.20 installed. This > version will still be maintained for the squeeze cycle but it is the > last release to do so. Systems newly installed will get GDM 2.30 > instead. You can upgrade it by installing the "gdm3" package - only do > so with only one GNOME session open, or from the console. Settings will > not be migrated, but for a usual desktop system this action is enough. > > 3) (Not GNOME-specific, but still.) Specific permissions on devices are > granted automatically to the user currently logged on physically to the > system: video and audio devices, network roaming, power management, > device mounting. The cdrom, floppy, audio, video, plugdev and powerdev > groups are no longer useful. See the ConsoleKit documentation for more > information. > > 4) Most graphical programs requiring root permissions now rely on > PolicyKit to do so, instead of gksu. The recommended way to give a user > administrative rights is to add it to the "sudo" group. > I think Michael asked on d-devel what group name to use for this. Is "sudo" still what we're going with? For these three items, I currently have: <para> The GNOME Display Manager (GDM), is kept at version 2.20 for systems upgraded from &oldreleasename;. This version will still be maintained for the squeeze cycle but it is the last release to do so. Systems newly installed will get GDM 2.30 instead, provided by the <package>gdm3</package> package. Because of incompatibilities between both versions, this upgrade is not automatic, but it is recommended to install <package>gdm3</package> after the upgrade to &releasename;. This should be done from the console, or with only one open GNOME session. Note that settings from GDM 2.20 will <strong>not</strong> be migrated. For a standard desktop system, however, simply installing <package>gdm3</package> should be enough. </para> <para> Specific permissions on devices are granted automatically to the user currently logged on physically to the system: video and audio devices, network roaming, power management, device mounting. The cdrom, floppy, audio, video, plugdev and powerdev groups are no longer useful. See the <package>consolekit</package> documentation for more information. </para> <para> Most graphical programs requiring root permissions now rely on <ulink url="http://www.freedesktop.org/wiki/Software/PolicyKit";>PolicyKit</ulink> to do so, instead of <package>gksu</package>. The recommended way to give a user administrative rights is to add it to the "sudo" group. </para> corrections or wording improvements are welcome. > 5) (Pending fix of #530024.) If there is only one network interface > configured using DHCP, which is the usual case for desktop systems, it > will be handled by NetworkManager instead of ifupdown. Therefore the > usual ifup and ifdown commands will not work. Instead, the interface can > be managed using the NetworkManager frontends. See the NM documentation > for more information. > Is there any progress on that bug? > [ 6) Something has to be said about the Evolution upgrade. However it is > still being worked on to be a bit smoother, so it will wait. ] > Cc:ing the evo maintainers for their input, and hopefully patch. Cheers, Julien
signature.asc
Description: Digital signature
