Re: gdm / gdm3

[Walter Hurry <walterhurry@lavabit.com>]

On Mon, 10 Oct 2011 16:52:14 +0000, Camaleón wrote:

> On Mon, 10 Oct 2011 19:25:47 +0300, Victor Nitu wrote:
> 
>> Hello all!
> 
> Hi!
> 
> I'm creating a new thread because you have replied to a current one
> ("Re:
> a quick Q:about package") and thus hijacking it ;-)
>  
>> I just have caught an interesting observation on the gdm3 package. I
>> have two systems, both of them are vanilla Debian testing, installed in
>> different time frames. In fact, there are about 7-8 months between
>> them.
>> Both have all packages up-to-date, but yesterday I noticed a small
>> difference when booting my laptop - the package name for the display
>> manager on my laptop is simply gdm, while on my desktop PC is gdm3. I
>> also have a LMDE installation at home, on another machine, which also
>> have gdm3.
>> Why is this happening?
> 
> Could it be because in the meantime (the invertal between both
> installations) gdm was upgraded to gdm3 and so it was installed by
> default on a clean install.
> 
>> Are there any other packages in this situation,
>> and I should be aware of them?
> 
> There is no need to worry for that change unless you are having any
> problem. I'd say you can:
> 
> a) Keep gdm untill is supported by your system b) Upgrade to gdm3
> 
>> I mean, a lot of trouble can happen if some scripts won't work because
>> of the name of the packages / binary files; I was transferring them
>> freely between the two systems (by now).
>> Have you experienced anything similar? I must admit I haven't search
>> the bts (yet), because besides this peculiar gdm problem, I also want
>> to know if there are more packages like this.
> 
> "gdm" and "gdm3" are both valid options in squeeze so I guess they can
> coexist. There should be no need to make any change unless you system
> urges you to do it so :-?
> 
> P.S. Remember to turn off html when sending messages to the list.

I echo all that. To OP: If you are concerned about other package 
differences, one option would be to run dpkg -l on both machines, and 
compare the output.