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
On Tue, Nov 28, 2017 at 1:47 PM, Jiri Novak wrote:
> Hi,
>
> according to this (
> https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/
> ), I'm trying to create my own extension of the rh-python36, though
> doesn't build:
>
> +
On Tue, Nov 28, 2017 at 2:40 PM, Jiri Novak wrote:
> Hi
>
> I need to add more libraries to rh-python36, which would require using
> rh-python36-build package and I've been told it is wring and I should do
> my own SCL.
>
> then I need to make the application use the
On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak wrote:
> Hello,
>
> I'm currently trying to port python app to use rh-python36 SCL (built
> using mock+rpmbuild), I've managed to make it build correctly in the scl
> paths (and using python3 for the packages that need it during
> What else is the right way to make RPM adding more libraries available
> when in scl enable rh-python36 bash?
Create your own mirror of rh-python36 and just add your packages to it?
___
SCLorg mailing list
SCLorg@redhat.com
On Mon, Jul 27, 2020 at 12:23 PM Jonathan MERCIER wrote:
>
> Dear I tried to build a container both with docker and buildah and got the
> same message error from gitlab-ci
>
> ---> https://gitlab.com/jonathan-dlang/scl_metapackage/-/jobs/657306213
No access rights.
> $ scl load