Bug 1367352
Summary: | Many DTS-4 references in DTS-6 Dockerfiles | ||
---|---|---|---|
Product: | Red Hat Developer Toolset | Reporter: | Miloš Prchlík <mprchlik> |
Component: | devtoolset-meta | Assignee: | Marek Polacek <mpolacek> |
Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | DTS 6.0 RHEL 7 | CC: | hhorak, jakub, mnewsome, ohudlick, rzima |
Target Milestone: | alpha | ||
Target Release: | 6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | devtoolset-6-6.0-6.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-15 10:02:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miloš Prchlík
2016-08-16 09:10:28 UTC
(devtoolset-6-toolchain-docker wasn't needed for alpha so we have obsolete devtoolset-4 in the dockerfiles.) Related, which version schema should we use? We outlined some rules in #1333041, but what to use for DTS6? Currently, it's Version="4" Release="10.5" so should I go with Version="6" Release="1.0" ? (In reply to Marek Polacek from comment #2) > (devtoolset-6-toolchain-docker wasn't needed for alpha so we have obsolete > devtoolset-4 in the dockerfiles.) > > Related, which version schema should we use? We outlined some rules in > #1333041, but what to use for DTS6? > Currently, it's > Version="4" > Release="10.5" > so should I go with > Version="6" > Release="1.0" > ? I discussed it a bit with Honza Horak (well, I asked him for clarification, and I'm almost ashamed by calling that a "discussion" :), and you are correct. The scheme we adopted in DTS-4.1 times continues, and for DTS-6.0 Version="6", Release="1" are correct values. With every build done by you (or devels in general) Release += 1, until the whole DTS-6.0 is released, then - when such time comes - automatic rebuild caused by e.g. updated base rhel7 image will add ".<int>" to the Release value. (So, for example, we will have Release 1, 2, 3 and 4, where 4 is the Release value by the time DTS-6.0 is released, and every automated rebuild after that will produce Release 4.1, 4.2, 4.3, etc. For DTS-6.1, we're supposed to increment Release once again, starting with Version="6", Release="5", to keep NVR rising.) Adding a link to document provided by Honza as a official source for this: https://mojo.redhat.com/docs/DOC-1023066#jive_content_id_Labels Thanks a lot, so I'll go with Version="6" Release="1" (so without ".0" in Release). Hi Marek, this happens because nobody officially asked for such image support. Each new docker image needs its request in RCM system(JIRA queue). When it is there I can perform common tasks to prepare all necessities. Please follow official process as is described in "RHSCL Development Guide" - "Docker request & workflow" section. https://docs.engineering.redhat.com/display/RCM/RHSCL+Development+Guides Radek Verified for build devtoolset-6-dockerfiles-6.0-6.el7 - no obvious DTS4 references anymore, it's even possible to build images with these provided Dockerfile, and resulting images look very DTS6-ish. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2724.html |