/etc/gdm/gdm.conf* transition not managed well

[geofft]

We have the following code in gdm-config's debian/rules:

ifneq ($(NEW_GDM),y)
    DEB_TRANSFORM_FILES_debathena-gdm-config += \
        ${GDM_CONFFILE}
    DEB_DIVERT_FILES_debathena-gdm-config += \
        /usr/share/gdm/BuiltInSessions/default.desktop.debathena
endif

However, nothing explicitly undiverts ${GDM_CONFFILE} on upgrade to new-GDM.

[jdreed]

I'd like to kill off old-gdm while doing this too. I propose doing so, and changing debathena-gdm's Depends to:

Depends: gdm3 | gdm (>= 2.25.2~)

Anyone forsee a problem with that? This means Squeeze users clinging to gdm2 will get forced to gdm3. I'm not convinced that's a problem.

[jdreed]

Meh, committed in r25904 anyway. I still want explicit approval or rejection of my proposal to kill gdm2 with fire.

[jdreed]

To clarify, the only supported release it's still possible to run old-gdm on is Squeeze. Squeeze also has the 'gdm3' package. So Squeeze users who either explicitly selected old-gdm, or didn't care, are the only group blocking us from killing gdm2.

[kaduk]

Replying to jdreed:

To clarify, the only supported release it's still possible to run old-gdm on is Squeeze. Squeeze also has the 'gdm3' package. So Squeeze users who either explicitly selected old-gdm, or didn't care, are the only group blocking us from killing gdm2.

sysd_stats shows 38 machines counterlogging as squeeze last month (and 3 lenny!); I'd be more comfortable doing this if we could check athinfo packages on them to get a sense for whether they have gdm at all. (I mostly expect them to be headless servers.)