Bug#734164: console-data: should conflict with console-setup

2014-03-03 Thread Anton Zinoviev
Sorry for the late responce. On Tue, Feb 11, 2014 at 10:07:26PM +0100, Michael Schutte wrote: > > I see, thanks for elaborating. This does sound appealing, but what > should happen in an upgrade if the package into which we move the > conffiles (IMHO this should be console-setup) is not installe

Bug#734164: console-data: should conflict with console-setup

2014-02-11 Thread Michael Schutte
On Mon, Feb 10, 2014 at 02:54:45PM +0200, Anton Zinoviev wrote: > On Sun, Feb 09, 2014 at 12:12:31PM +0100, Michael Schutte wrote: > > I'm not sure if I understand this point. Would you like to keep these > > old configuration files? > > Not at all. It's just that the idea of leaving behind the

Bug#734164: console-data: should conflict with console-setup

2014-02-10 Thread Anton Zinoviev
On Sun, Feb 09, 2014 at 12:12:31PM +0100, Michael Schutte wrote: > > I'm not sure if I understand this point. Would you like to keep these > old configuration files? Not at all. It's just that the idea of leaving behind the modified legacy conffiles unowned never occurred to me. Since there i

Bug#734164: console-data: should conflict with console-setup

2014-02-09 Thread Michael Schutte
Hey, On Tue, Feb 04, 2014 at 08:37:08PM +0200, Anton Zinoviev wrote: > I am not sure I understand entirely the relations between various > console-related packages. There are too many of them - console-setup, > console-data, console-common, kbd (not to mention the obsoleted > console-tools and

Bug#734164: console-data: should conflict with console-setup

2014-02-04 Thread Anton Zinoviev
On Sun, Feb 02, 2014 at 11:54:43AM +0100, Michael Schutte wrote: > > * The kbd init script offers several things that console-setup > doesn't, namely the option to configure different fonts on different > consoles, the possibility to modify the keymap through a sed script, > the conf

Bug#734164: console-data: should conflict with console-setup

2014-02-02 Thread Michael Schutte
Hey, On Sat, Jan 11, 2014 at 07:42:34PM +0200, Anton Zinoviev wrote: > > anyway, i don't know whether i'm talking about console-data at all at > > this point, because things are such a mess. it's where i configured my > > keymap, in any case. previously. > > > > open /etc/init.d/kbd and look for

Bug#734164: console-data: should conflict with console-setup

2014-01-11 Thread Anton Zinoviev
On Sat, Jan 11, 2014 at 05:56:25PM +0100, Oswald Buddenhagen wrote: > > anyway, i don't know whether i'm talking about console-data at all at > this point, because things are such a mess. it's where i configured my > keymap, in any case. previously. > > open /etc/init.d/kbd and look for HAVE_SETU

Bug#734164: console-data: should conflict with console-setup

2014-01-11 Thread Oswald Buddenhagen
On Sat, Jan 11, 2014 at 06:48:24PM +0200, Anton Zinoviev wrote: > Console-setup doesn't break console-data for the following reasons: > > 2. console-setup can be configured not to overwrite the configuration of > console-data. > nobody talked about overwriting. the phrase was "made ineffective".

Bug#734164: console-data: should conflict with console-setup

2014-01-11 Thread Anton Zinoviev
On Sat, Jan 11, 2014 at 01:09:51PM +0100, Oswald Buddenhagen wrote: > > On Sat, Jan 11, 2014 at 01:27:39PM +0200, Anton Zinoviev wrote: > > This is what I would do if I was in your position: [...] > > > your proposal is completely useless to users in my position. > > console-setup *does* break c

Bug#734164: console-data: should conflict with console-setup

2014-01-11 Thread Oswald Buddenhagen
anton, On Sat, Jan 11, 2014 at 01:27:39PM +0200, Anton Zinoviev wrote: > This is what I would do if I was in your position: [...] > your proposal is completely useless to users in my position. console-setup *does* break console-data, because its mere presence makes the debconf setup of console-d

Bug#734164: console-data: should conflict with console-setup

2014-01-11 Thread Anton Zinoviev
On Thu, Jan 09, 2014 at 07:06:22AM +0100, Christian PERRIER wrote: > > So, well, I'm very tempted to re-reassign the bug and then immediately > fix this myself in c-s git. Well, go agead! :) Since a long time I am not interested in arguing. > Breaks and Provides are the right way to handle a t

Bug#734164: console-data: should conflict with console-setup

2014-01-08 Thread Christian PERRIER
Quoting Anton Zinoviev (an...@lml.bas.bg): > I agree. I am not against removing c-d. What I don't like is to abuse > 'Breaks' and 'Provides' inapropriately. We must not force our way to > the users, they have the right to install c-d even if the package is > removed from the archive. The nu

Bug#734164: console-data: should conflict with console-setup

2014-01-08 Thread Anton Zinoviev
reassign 734164 console-data retitle 734164 The package doesn't make obvious to the users that it is deprecated in favour of console-setup thanks On Sun, Jan 05, 2014 at 08:38:32AM +0100, Christian PERRIER wrote: > > Well, that's long overdue. A way to really get rid of c-d is probably > to have

Bug#734164: console-data: should conflict with console-setup

2014-01-04 Thread Christian PERRIER
reassign 734164 console-setup retitle 734164 Please add Breaks and Provides to really replace console-data thanks Quoting Oswald Buddenhagen (oswald.buddenha...@gmx.de): > Package: console-data > Version: 1.12-3 > Severity: normal > > console-data appears to be mostly deprecated in favor of conso

Bug#734164: console-data: should conflict with console-setup

2014-01-04 Thread Oswald Buddenhagen
Package: console-data Version: 1.12-3 Severity: normal console-data appears to be mostly deprecated in favor of console-setup, and is overridden by the latter if it is installed. this isn't exactly obvious without reading through the scripts, and leads to problems like bug #626680, ubuntu bug 5218