New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Breaks instead of Conflicts when generating .deb packages #400

Closed
bigon opened this Issue Apr 5, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@bigon

bigon commented Apr 5, 2013

Hi,

When running "fpm -s gem -t deb sprockets" the generated .deb is using a versioned Conflicts. This is against a recent policy and Breaks should be used in that case. See the following lintian output:

I: rubygem-sprockets: conflicts-with-version rubygem-tilt (= 1.3.0)
N:
N: An earlier-than version clause is normally an indication that Breaks
N: should be used instead of Conflicts. Breaks is a weaker requirement
N: that provides the package manager more leeway to find a valid upgrade
N: path. Conflicts should only be used if two packages can never be
N: unpacked at the same time, or for some situations involving virtual
N: packages (where a version clause is not appropriate). In particular,
N: when moving files between packages, use Breaks plus Replaces, not
N: Conflicts plus Replaces.
N:
N: Refer to Debian Policy Manual section 7.4 (Conflicting binary packages
N: - Conflicts) for details.
N:
N: Severity: normal, Certainty: wild-guess
N:
N: Check: fields, Type: binary, udeb, source
N:

@jordansissel

This comment has been minimized.

Owner

jordansissel commented Apr 5, 2013

Fixed in master. thanks! :)

jordansissel added a commit that referenced this issue Apr 5, 2013

@jordansissel

This comment has been minimized.

Owner

jordansissel commented Apr 5, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment