FAQ
The structure of the build repos on buildlogs.centos.org are as follows:


RC and GA build trees:
c7.00.02/
c7.00.03/
c7-00.04/


CentOS 7 Extras:
c7-extras/


CentOS 7 Plus:
c7-plus/ <==Not there yet, will be when we build the plus kernel
later today


CentOS 7 Updates:
c7-updates/


So, everything that goes on the CentOS 7 ISOs (and are the same versions
as the RHEL7 GA release) will come from c7.00.02, c7.00.03, and c7-00.04
(except the actual secureboot signed content that KB mentioned earlier).


Anything that is an updated package form those on the ISOs will come
from c7-updates.


The centos/ directory is the actual testing tree(s) for the open qa
process and will eventually go away once we have a GA release ..
however, the build repos (which are actually the staged repos used for
building the packages via mock) and listed above will remain
indefinitely to show the RPMs, SRPMs, and logs from mock used to produce
CentOS 7.


Thanks,
Johnny Hughes


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.centos.org/pipermail/centos-devel/attachments/20140624/6fc445e1/attachment.bin

Search Discussions

  • Lamar Owen at Jun 24, 2014 at 5:07 pm

    On 06/24/2014 12:39 PM, Johnny Hughes wrote:
    ...
    The centos/ directory is the actual testing tree(s) for the open qa
    process and will eventually go away once we have a GA release ..
    however, the build repos (which are actually the staged repos used for
    building the packages via mock) and listed above will remain
    indefinitely to show the RPMs, SRPMs, and logs from mock used to produce
    CentOS 7.
    Thanks for the info, the openness, and the updates.
  • Anssi Johansson at Jun 27, 2014 at 12:30 am

    24.6.2014 19.39, Johnny Hughes kirjoitti:
    CentOS 7 Updates:
    c7-updates/

    This may be obvious to most of you, but I just remembered that I can
    define additional repositories in the installer. If you are doing
    netinstalls straight from buildlogs, defining the updates repo (
    http://buildlogs.centos.org/c7-updates/ ) in the installer will save you
    a bit of bandwidth as you don't need to download the outdated packages.


    This worked like a charm, and even the per repository proxy setup worked
    fine. I needed to use a proxy for the buildlogs server, because my test
    box is IPv6-only and the buildlogs server is IPv4-only.
  • Johnny Hughes at Jun 27, 2014 at 6:12 pm

    On 06/26/2014 07:30 PM, Anssi Johansson wrote:
    24.6.2014 19.39, Johnny Hughes kirjoitti:
    CentOS 7 Updates:
    c7-updates/
    This may be obvious to most of you, but I just remembered that I can
    define additional repositories in the installer. If you are doing
    netinstalls straight from buildlogs, defining the updates repo (
    http://buildlogs.centos.org/c7-updates/ ) in the installer will save you
    a bit of bandwidth as you don't need to download the outdated packages.

    This worked like a charm, and even the per repository proxy setup worked
    fine. I needed to use a proxy for the buildlogs server, because my test
    box is IPv6-only and the buildlogs server is IPv4-only.

    It is also good to know that the add repo setup works as designed ..not
    the case in previous versions.


    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: signature.asc
    Type: application/pgp-signature
    Size: 198 bytes
    Desc: OpenPGP digital signature
    Url : http://lists.centos.org/pipermail/centos-devel/attachments/20140627/656f096d/attachment.bin

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcentos-devel @
categoriescentos
postedJun 24, '14 at 4:39p
activeJun 27, '14 at 6:12p
posts4
users3
websitecentos.org
irc#centos

People

Translate

site design / logo © 2021 Grokbase