hi, it seems the src.rpms are missing from: http://vault.centos.org/7.5.1804/os/Source/SPackages/ on the other hand 7.5 missing from the centos git too. eg. tha last commit to the centos-release rpm is from 2017 januar: https://git.centos.org/summary/rpms!centos-release.git is there any place where we can found the source of centos? regards.
On 10/05/18 12:30, Farkas Levente wrote:
hi, it seems the src.rpms are missing from: http://vault.centos.org/7.5.1804/os/Source/SPackages/ on the other hand 7.5 missing from the centos git too. eg. tha last commit to the centos-release rpm is from 2017 januar: https://git.centos.org/summary/rpms!centos-release.git is there any place where we can found the source of centos? regards.
As for each release, we give priority to binary content, to let people update. It usually takes ~2 to 3 days for the mirror network to stabilize and so then be able to feed the vault and debuginfo nodes.
Don't forget that all this happens on community donated machines to the CentOS Project, so I'd like to thank again all those sponsors for the node[s]/bandwidth they give to host our content infra.
For the record, during this release we had some network peaks up to 8.4Gbit/s (aggregated bandwidth usage between all those donated nodes) so that external mirrors could get content. That's also why we have to wait for the release itself and announce.
Now that 7.5.1804 is "live", Johnny will push the src.rpm soon to vault.centos.org and debuginfo pkgs to debuginfo.centos.org
We'll have soon to find some new spots to host those nodes btw (lack of HDD space and bandwidth)
Now back to the centos-release src.rpm question , our builders are pushing raw builds (so untested/unsigned) to public location(including build logs, mock config used, etc), so you can find centos-release here : https://buildlogs.centos.org/c7.1804.00.x86_64/centos-release/ )
Hope that this answers your question
On 05/10/2018 01:41 PM, Fabian Arrotin wrote:
Now back to the centos-release src.rpm question , our builders are pushing raw builds (so untested/unsigned) to public location(including build logs, mock config used, etc), so you can find centos-release here : https://buildlogs.centos.org/c7.1804.00.x86_64/centos-release/ )
Hope that this answers your question
that's all correct and i also find the it in buildlog, but why don't you use git.centos.org for this (and may be other) packages?
On 05/10/2018 07:00 AM, Farkas Levente wrote:
On 05/10/2018 01:41 PM, Fabian Arrotin wrote:
Now back to the centos-release src.rpm question , our builders are pushing raw builds (so untested/unsigned) to public location(including build logs, mock config used, etc), so you can find centos-release here : https://buildlogs.centos.org/c7.1804.00.x86_64/centos-release/ )
Hope that this answers your question
that's all correct and i also find the it in buildlog, but why don't you use git.centos.org for this (and may be other) packages?
The shadow cache content (binary files like tarballs) for git.centos.org is written to by Red Hat as part of their release process when they release packages for RHEL. The CentOS core team (usually me, sometimes one of the other members) can edit the text files (change specs, add patches, etc.) .. BUT .. we can't push binary files directly to the shadow cache.
This means that packages that are not actually produced as part of RHEL (ie, centos-* packages) have to be added out of the normal process. That is, I have to give them to someone and have them manually inject them into the the stream, as I can not actually push the tarballs to git.centos.org.
Since they are available via buildlogs, and then also vault, that is not normally a priority compared to the other pieces of the release process.
This subset of packages is very few (that is, CentOS core content that does not originate from RHEL Source code), in fact it is usually only the centos-release package. Or it would be centos-bookmarks or centos-logos or centos-indexhtml .. if those would change (they usually do not).
-
Fabian Arrotin -
Farkas Levente -
Johnny Hughes