Re: When does a conflict become outdated?
In article <20040331141602.GB25147@kolon.mbp> firstname.lastname@example.org writes:
>Many old packages in Debian, have conflicts for specific version of
>packages that are pre-potato. Would it then be OK to submit a minor bug
>and tell the maintainer that the conflict could be removed?
>For example, the debconf package has Conflicts: menu (<= 2.1.3-1). But
>even potato has menu 2.1.5-10.1, so the conflict is not of much use
Instead of filing bugs (which should at most be wishlist), why don't
you submit a wishlist request to add a check to lintian and/or linda.
"Warning" is to strong for these, maybe they need a new level
"observation". The check is more likely to be added if you submit
Blars Blarson email@example.com
With Microsoft, failure is not an option. It is a standard feature.