[SERVER-11110] some enterprise and community subpackages on redhat do not conflict Created: 09/Oct/13 Updated: 11/Jul/16 Resolved: 14/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Ernie Hershey |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
centOS 64bit |
||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | Linux | ||||
| Participants: | |||||
| Description |
|
All enterprise subpackages should conflict with all community subpackages (including metapackages). Some of the pairings between a community and enterprise package do not conflict, however. For example, "sudo yum install mongodb-enterprise-unstable-tools" followed by "sudo yum install mongodb-org-unstable-server" does not cause a conflict. The following combinations are the ones that should conflict but do not:
|
| Comments |
| Comment by David Storch [ 15/Oct/13 ] |
|
I reran the test script and verified that all rpm packages properly conflict with one another. |
| Comment by auto [ 12/Oct/13 ] |
|
Author: {u'username': u'ehershey', u'name': u'Ernie Hershey', u'email': u'ernie.hershey@10gen.com'}Message: |
| Comment by Ernie Hershey [ 11/Oct/13 ] |
|
I just reproduced the problem and see incorrect output (blank) from this command: "rpmquery --conflicts mongodb-enterprise-unstable-server" I'm still digging. |
| Comment by Ernie Hershey [ 11/Oct/13 ] |
|
The breaks/conflicts stuff should still be fixed. Also it's weird that those conflicts would fail with everything else working. I'll take a look but I wonder if it could be oddities in the package names or in test.sh? |
| Comment by David Storch [ 11/Oct/13 ] |
|
Almost everything is green for the rpm packages! I'm still seeing two test failures for conflicts between enterprise packages and mongo-10gen:
On Ubuntu, all of the conflict-related tests still fail because of breaks vs. conflicts. |
| Comment by Ernie Hershey [ 11/Oct/13 ] |
|
New packages are up and should have all the right conflicts now. |
| Comment by David Storch [ 11/Oct/13 ] |
|
Great, thanks for your hard work ernie.hershey@10gen.com. Let me know when new packages are up. |
| Comment by Ernie Hershey [ 11/Oct/13 ] |
|
I saw that too and I think I found the problem - just a typo. I'm working On Oct 11, 2013, at 8:46, "David Storch (JIRA)" <jira@mongodb.org> wrote: David Storch<https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.storch>commented This appears to be partially resolved in the latest packages. The new
The following cases have been fixed:
This message is automatically generated by JIRA. |
| Comment by David Storch [ 11/Oct/13 ] |
|
This appears to be partially resolved in the latest packages. The new complete list of failures is:
The following cases have been fixed:
|
| Comment by Ernie Hershey [ 10/Oct/13 ] |
|
I think it should all stay together. Hopefully it's just one fix! |
| Comment by David Storch [ 10/Oct/13 ] |
|
There is a similar issue in which some of the new split rpm packages do not conflict with the old packages. Everything conflicts as expected with mongo-10gen-server, but there are some subpackages which do not conflict with mongo-10gen. The specific list of failures is below:
ernie.hershey@10gen.com, let me know if this should be split off into a separate ticket. |