Re: Breaks: instead of Conflicts: for transitional packages

[Lucas Nussbaum <lucas@lucas-nussbaum.net>]

On 19/06/11 at 19:59 -0700, Antonio Terceiro wrote:
> Hello all,
> 
> These days I noticed that we are using Conflicts: instead of Breaks: in
> our transitional packages, and we should change that. Among other
> reasons, using Breaks: instead of Conflicts: makes it easier for the
> package manager determinate a valid upgrade path. Using Breaks instead
> of Conflicts for transitional packages is also mandated by the newest
> version of the Debian policy, so that's the way to go.
> 
> I've just updated gen-ruby-trans-pkgs in gem2deb to do The Right Thing,
> and will upload a new version of gem2deb soon.
> 
> Please double check your packages and make sure your new ruby-foo
> `Breaks: libfoo-ruby, libfoo-ruby1.8` instead of Conflicts: (and make
> sure that's a versioned Breaks: in the same way we have done until now
> with versioned Conflicts:)

Hi,

Thanks for the change.

I'm wondering if we should implement a check for common mistakes (or old
practices now considered bad practices) directly in gem2deb.
This one is a candidate, and another one is the ruby1.8 |
ruby-interpreter dependency.

We could display a warning for now, which I would use to find all
affected packages by scanning the build logs, and then turn this into an
error later.

What do you think?

- Lucas