Openbravo Issue Tracking System - Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015152 | Modules | Central Repository | public | 2010-11-10 16:56 | 2020-04-13 10:56 |
| Reporter | marvintm | ||||
| Assigned To | alostale | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Review Assigned To | |||||
| Support ticket | |||||
| OBNetwork customer | |||||
| Regression introduced in release | |||||
| Summary | 0015152: When a module version in an instance doesn't exist in central repository, only that module version is considered "compatible" | ||||
| Description | Consider the following case: - An Openbravo instance contains the following modules: * Module A with version 1.0.0 * Module B with version 1.0.0, which depends on module A 1.0.0 - Central repository contains: * Module A with version 1.0.1 * Module B with versions 1.0.0, and 1.0.1 (version 1.0.1 depends on module A 1.0.1) Scan for updates will not find anything, because the module A version 1.0.0 doesn't exist in the central repository, and therefore will be the only version of module A considered compatible. | ||||
| Steps To Reproduce | |||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-11-10 16:56 | marvintm | New Issue | |||
| 2010-11-10 16:56 | marvintm | Assigned To | => alostale | ||
| 2020-04-13 10:56 | alostale | Severity | major => minor | ||
| There are no notes attached to this issue. |