Issue 126568 - AOO .deb packages should at least properly define it conflicts with existing packages in the Debian archive
Summary: AOO .deb packages should at least properly define it conflicts with existing ...
Status: UNCONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 4.1.1
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-05 07:29 UTC by bjoern.michaelsen
Modified: 2015-10-06 23:49 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description bjoern.michaelsen 2015-10-05 07:29:27 UTC 
AOO .deb packages try to install files that are part of other official packages in the Debian archive (e.g. /usr/bin/soffice). They should define proper conflicts as per Debian policy manual:

https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts

If this stays unfixed, unexperienced users will continue to run into troubles by installing the 3rd party AOO packages, likely resulting in a repeated emphasized recommendations to not install packages from outside the Debian archive (which is usually a bad idea for inexperienced users anyway).

see e.g. also: https://bugs.launchpad.net/ubuntu/+bug/1234968
Comment 1 mroe 2015-10-05 10:58:38 UTC 
The original issue describes the install of LO. LO grab its base from AOO. So if AOO change something and LO grab this again - what will happen?