| Anonymous | Login | 2024-12-21 23:47 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0004862 | ClearOS | public | 2015-09-03 11:02 | 2019-05-17 04:40 | |||||
| Reporter | NickH | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | tweak | Reproducibility | always | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.1.0 Beta 3 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0004862: Update exclude list for clearos-epel | ||||||||
| Description | The exclude list for clearos-epel is very different between 6.x and 7.x (apart from wildcards) and at a minimum openvpn is missing from the 7.x exclude list. This has already caused a couple of mis-installations as clearos-epel is enabled by default. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0001942) user2 2015-09-04 10:24 |
Hi Nick, Short reply: OpenVPN does not need to be in the exclude list in 7. Did something go wrong? Are there any other apps not behaving? Long reply: The new Koji build system necessitated a change in the way we handle upstream (e.g. EPEL). In ClearOS 6, we exclude all ClearOS-related packages in EPEL just so that we can control the upgrade cycle. For example, when EPEL releases a new openvpn package, it automatically lands in the ClearOS 6 clearos-test repository. From there, it gets promoted to: 1) clearos-updates-testing: QA/dog food 2) clearos-updates: Community Edition 3) clearos-verified-updates: Professional Edition It's still the unmodified EPEL openvpn package, but the release timing is controlled. It's different in ClearOS 7. For the Community Edition, the EPEL repo will be enabled by default. For Home and Business Editions, we have separate EPEL an CentOS verified repos where we control the release cycle. So when a new openvpn package from EPEL comes along, the process in 7 is different: 1) clearos-epel-testing: QA/dog food 2) clearos-epel: Community Edition 3) clearos-epel-verified: Home and Business Editions So in 6, we have _both_ the modified EPEL RPMS along with the unmodified RPMS listed in the exclude list. In 7, we only need to list the modified EPEL RPMS in the exclude list. Clear as mud. |
|
(0011981) NickH (developer) 2019-05-17 04:40 |
See comments. Not applicable. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-09-03 11:02 | NickH | New Issue | |
| 2015-09-04 09:50 | user2 | Status | new => confirmed |
| 2015-09-04 09:50 | user2 | Status | confirmed => acknowledged |
| 2015-09-04 10:24 | user2 | Note Added: 0001942 | |
| 2019-05-17 04:40 | NickH | Note Added: 0011981 | |
| 2019-05-17 04:40 | NickH | Status | acknowledged => closed |
| 2019-05-17 04:40 | NickH | Resolution | open => won't fix |
|
Issue History |