Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1333040

Summary: Update toolchain image "prefix" to match other RHSCL images
Product: Red Hat Developer Toolset Reporter: Miloš Prchlík <mprchlik>
Component: devtoolset-4-toolchain-containerAssignee: Marek Polacek <mpolacek>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: DTS 4.1 RHEL 7CC: mcermak
Target Milestone: rc   
Target Release: 4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: devtoolset-4-toolchain-docker-4-10.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-31 10:46:07 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-05-04 14:41:56 UTC 
Description of problem:

As of now, devtoolset-4-toolchain-rhel7 image with DTS 4.1 packages is being labeled as "rhscl/devtoolset-4..." which is the only exception among existing RHSCL packages, the rest is being named "rhscl_beta/...". We can expect at least one rebuild, to create a image using signed DTS packages, I'd be good to get its prefix to sync with other RSHCL images, whaever the value may be at the time, by updating Dockerfile's 'LABEL Name="..."' directive.


Version-Release number of selected component (if applicable):

devtoolset-4-toolchain-docker-4-9.5



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Marek Polacek 2016-05-06 12:24:32 UTC 
Done.
Comment 3 Miloš Prchlík 2016-05-17 12:26:40 UTC 
As of RC, prefix is back to "rhscl/", replacing Beta's "rhscl_beta/". AFAICT, the current state is the correct one, therefore, for image rhscl/devtoolset-4-toolchain-rhel7:4-10.3, switching to VERIFIED.
Comment 5 errata-xmlrpc 2016-05-31 10:46:07 UTC 
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://access.redhat.com/errata/RHBA-2016:1181