Re: [scl.org] RHSCL package replacing RHEL package
Hi Remi, On 01/25/2018 03:30 PM, Remi Collet wrote: > On a simple "yum update" > > javapackages-tools from rhel-server-rhscl-6-rpms > replace > jpackage-utils from rhel-6-server-rpms. > > Is that expected ? Thanks for reporting this, it is definitely not expected - non-SCL-ized package javapackages-tools should not be included in RHSCL channels. I'll investigate why it is tagged in brew [1] and whether we can have it removed from the next release. [1] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=328857 -- Mikolaj Izdebski Senior Software Engineer, Red Hat IRC: mizdebsk ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Bootstrapping devtoolset?
On 12/06/2016 02:48 PM, Stefan Ring wrote: > On Tue, Dec 6, 2016 at 12:05 PM, Mikolaj Izdebski wrote: >> Java collections were typically bootstrapped by using older packages >> from other collections or from RHEL. Specifically, rh-java-common was >> built using maven30 RPMs and maven30 was built using RHEL 7 content. >> >> CentOS bootstraps SCLs by using external repositories with prebuilt >> RPMs, like this one: >> http://cbs.centos.org/koji/externalrepoinfo?extrepoID=11 > > Unfortunately I cannot see what’s inside this repository or some > siblings I've tried (access denied). Does it basically contain the > same packages as the final sclo repo or are there some hand-tweaked > packages aimed at getting through a bootstrap? I don't know, I don't have access either. Bug I guess these could be RHSCL packages. > I guess that bootstrapping was a manual process with lots of dirty > hacks and workarounds ;). Is this a good impression of how it went? Oh yes :) And it still required using pre-built binaries from older releases or products. -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Bootstrapping devtoolset?
On 12/06/2016 11:54 AM, Stefan Ring wrote: > Is there a method for bootstrapping devtoolset (-3, -4)? I used to be > able to build everything in a mock for devtoolset-2, but for the newer > ones I find that they seem to have cyclic build dependencies where > most builds want to pull in everything that would only be available > after the successful build (currently stuck at rh-java-common). > > How was the bootstrapping done? Java collections were typically bootstrapped by using older packages from other collections or from RHEL. Specifically, rh-java-common was built using maven30 RPMs and maven30 was built using RHEL 7 content. CentOS bootstraps SCLs by using external repositories with prebuilt RPMs, like this one: http://cbs.centos.org/koji/externalrepoinfo?extrepoID=11 -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
