c7-devtoolset-11 repo missing from buildlogs.centos.org

General support questions
Post Reply
NickH
Posts: 20
Joined: 2018/03/14 15:26:12

c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by NickH » 2022/06/30 09:21:26

Do you know why the above repo is missing from https://buildlogs.centos.org/ and how I go about getting it added?

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by TrevorH » 2022/06/30 10:27:30

Because it's in the production repo? I see it in centos-sclo-rh
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

NickH
Posts: 20
Joined: 2018/03/14 15:26:12

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by NickH » 2022/06/30 10:46:50

From what I've seen all package groups are in their own individual repos so devtoolset-7 -8, -9 and so on all have their own individual repos whether they are current or not. So https://buildlogs.centos.org/centos/7/s ... ackages/d/ contains all devtoolset- packages as well as them being individually in their own repos. The same goes for all the other build packages such as llvm-toolset-7.0 (which is the currently released latest package and not any of the later llvm-toolset-9/10/11 that appear in the top level of buildlogs.centos.org)

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by TrevorH » 2022/06/30 11:07:15

No, buildlogs is where stuff goes before it's tested. It's referred to in the .repo files via a special -testing repo and shouldn't be used most of the time unless you are specifically testing something that hasn't been released yet. The real thing is in the centos-sclo-rh repo.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

NickH
Posts: 20
Joined: 2018/03/14 15:26:12

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by NickH » 2022/06/30 11:18:14

Hmm. It looks like my distro (ClearOS), fir its build system has always pulled from its packages from buildlogs, perhaps as a way of limiting the packages available in the build system. Can I ask where do you exactly mean by the "centos-sclo-rh repo". I presume not https://buildlogs.centos.org/centos/7/sclo.

Sorry, but I am inheriting a set up that I need to reverse engineer to get devtoolset-11 added to it.

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by TrevorH » 2022/06/30 14:26:34

It's the repo you get when you install centos-release-scl-rh-2-3.el7.centos.noarch and/or centos-release-scl-2-3.el7.centos.noarch

Buildlogs is not particularly safe to use. Nothing is signed on there, it's most likely full of things that should have been deleted or experimental. It is included in some of the SIG provided .repo files as a way to get to content that has not yet been released for real but they are all in repos called something -testing to make it clear that you're using unsupported stuff.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

NickH
Posts: 20
Joined: 2018/03/14 15:26:12

Re: c7-devtoolset-11 repo missing from buildlogs.centos.org

Post by NickH » 2022/06/30 15:09:56

Thanks. I dug further into it after I replied. It looks like I may need to do a bit of a revamp of the build system. It is like the initial creator wanted to finely tune the packages available in koji rather than use all SCL packages and I am not sure why. It also makes life difficult as the build system koji config does not match the mock config the clients have. This means you can build something locally and then submit it to koji where it may fail. To me it is a bit barking mad.

Post Reply