Ticket #976 (closed defect: fixed)

Opened 10 years ago

Last modified 9 years ago

debathena-gdm-config doesn't handle Debian gdm3 package

Reported by: geofft Owned by: bbaren
Priority: high Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version: debathena-gdm 1.0, debathena-gdm-config 1.39, debathena-pam-config 1.2.1, debathena-network-manager-config 1.3, debathena-kiosk 1.4.8
Upstream bug:

Description

Ubuntu put what we call "new GDM" in the gdm package, starting from version 2.25. Debian, deciding that it was eventually going to be part of GNOME 3, put it in the gdm3 package and kept a gdm package around with "old GDM". We only ever tested this on Ubuntu. This causes the following immediate problem on Debian:

geofft@leveret:~$ aptitude -s install debathena-login-graphical
[...]                                                          
The following packages have unmet dependencies:                
  gdm3: Conflicts: gdm but 2.20.11-4 is to be installed.       
The following actions will resolve these dependencies:         
                                                               
     Remove the following packages:                            
1)     gdm3                                                    
2)     gnome                                                   
3)     gnome-desktop-environment                               

The less immediate problem is that our build infrastructure conditionalizes on gdm package version, but on Debian, both gdm and gdm3 exist. One answer (probably the easier one) is to substvar in our gdm dependency, and on Debian where gdm3 exists, set NEW_GDM and set the substvar to gdm3, and simply not support old-gdm on Debian releases that include new-gdm. (This is analogous to what we are forced to do on Ubuntu.) If someone wants to be particularly ambitious, they could try making multiple binary packages debathena-gdm-config and debathena-gdm3-condig.

Change History

comment:1 Changed 10 years ago by geofft

  • Owner set to geofft
  • Status changed from new to accepted

comment:2 Changed 9 years ago by bbaren

  • Owner changed from geofft to bbaren
  • Status changed from accepted to assigned

After discussing this with geofft, we've decided it's appropriate to create a debathena-gdm metapackage, which depends on gdm in Ubuntu and pre-Wheezy Debian and on gdm3 elsewhere.

comment:3 Changed 9 years ago by jdreed

So, geofft commited r25396 which did some of this, but then NACK'd it, but then never reverted it. So this is a mess. "Yay".

comment:4 Changed 9 years ago by geofft

  • Status changed from assigned to committed

Fixed r25396 in r25623.

comment:5 Changed 9 years ago by jdreed

What's the status of this? WE need to build debathena-gdm and then rebuild gdm-config?

comment:6 Changed 9 years ago by jdreed

  • Status changed from committed to development
  • Fixed in version set to debathena-gdm 1.0, debathena-gdm-config 1.39

comment:7 Changed 9 years ago by jdreed

This also incorporates 1.38 (position the windows on the first monitor), and requires testing in lucid, natty, precise and squeeze, please.

comment:8 Changed 9 years ago by jdreed

r25729 moves our other packages that build-dep gdm to the new debathena-gdm

comment:9 Changed 9 years ago by jdreed

  • Fixed in version changed from debathena-gdm 1.0, debathena-gdm-config 1.39 to debathena-gdm 1.0, debathena-gdm-config 1.39, debathena-pam-config 1.2.1, debathena-network-manager-config 1.3

comment:10 Changed 9 years ago by jdreed

  • Fixed in version changed from debathena-gdm 1.0, debathena-gdm-config 1.39, debathena-pam-config 1.2.1, debathena-network-manager-config 1.3 to debathena-gdm 1.0, debathena-gdm-config 1.39, debathena-pam-config 1.2.1, debathena-network-manager-config 1.3, debathena-kiosk 1.4.8

comment:11 Changed 9 years ago by jdreed

People should, like, test this.

comment:12 Changed 9 years ago by jdreed

  • Status changed from development to proposed

comment:13 Changed 9 years ago by jdreed

  • Status changed from proposed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.