Comment 15 for bug 424511

Hi,

> Hmmm, I'm not convinced there. The old version's postrm script doesn't unregister schema's. Schema's are unregistered on upgrade by the old versions prerm script, before the new versions files are unpacked.

Yes, you are right, it is my mistake.

> The schemas are then re-registered by the new versions postinst script. By this stage, the files of gnome-session and gnome-session-bin should already be unpacked.

This is not true in my case as you could see in my dpkg.log. Note that gnome-session.schemas is moved from package gnome-session to gnome-session-bin. Gnome-session-bin was unpacked and configured before old gnome-session is upgraded. Gnome-session-bin brings gnome-session.schemas and it is registered by postint script. In this stage, gnome-session.schemas is still registered by old gnome-session. Double registration is no problem.

During upgrading gnome-session from old version with gnome-session.schemas to new version without gnome-session.schemas, gnome-session.schemas is unregistered by old prerm, but not registered by new postinst script.

The result of this process is that gnome-session.schemas is not registered although schemas was twice registered and once unregistered.

In fact I do not understood why there is no conflict when both old gnome-session and new gnome-session-bin are unpacked at the some time and both contains own gnome-session.schemas.

Thanks