CentOS - Aug 2018 - How do I actaully get the current sources from centos-git?

Hi,

I am trying to retrieve the srpm for the latest centos-release pacakge
from centos-git by following the instructions @ https://wiki.centos.org/Sources.

If I run the following commands:
git clone  https://git.centos.org/git/rpms/centos-release.git
cd centos-release/
git checkout c7
~/centos-git-common/get_sources.sh

Everything completes without error. The problem is that the sources that get
downloaded are not for 1804.

(vgeppetto2 pts21) $ ll SOURCES/ SPECS/
SOURCES/:
total 28
-rw-rw-r--. 1 mock mock  1584 Aug  6 08:19 1000-centos-release-cr.patch
-rw-rw-r--. 1 mock mock   264 Aug  6 08:19 85-display-manager.preset
-rw-rw-r--. 1 mock mock  2439 Aug  6 08:19 90-default.preset
-rw-rw-r--. 1 mock mock 12799 Aug  6 08:20 centos-release-7-1.1503.tar.gz

SPECS/:
total 8
-rw-rw-r--. 1 mock mock 6471 Aug  6 08:19 centos-release.spec
(vgeppetto2 pts21) $grep "define upstream_rel"
SPECS/centos-release.spec
%define upstream_rel 7.3
(vgeppetto2 pts21) $

So if I am reading things correctly, it looks like the SOURCES are for 1503 
and the spec file is for 1611.

Can someone please explain to me how to actually get the current SOURCES
and SPEC for centos-release-7-5.1804.1 from centos git?

To be clear I know I can get the srpm from vault but I would like to understand
how to work centos git.

Regards,

-- 
Tom			me at tdiehl.org

On 06/08/18 15:15, me at tdiehl.org wrote:
> Hi,
> 
> I am trying to retrieve the srpm for the latest centos-release pacakge
> from centos-git by following the instructions @
> https://wiki.centos.org/Sources.
> 
> If I run the following commands:
> git clone? https://git.centos.org/git/rpms/centos-release.git
> cd centos-release/
> git checkout c7
> ~/centos-git-common/get_sources.sh
> 
> Everything completes without error. The problem is that the sources that
> get
> downloaded are not for 1804.
> 
> (vgeppetto2 pts21) $ ll SOURCES/ SPECS/
> SOURCES/:
> total 28
> -rw-rw-r--. 1 mock mock? 1584 Aug? 6 08:19 1000-centos-release-cr.patch
> -rw-rw-r--. 1 mock mock?? 264 Aug? 6 08:19 85-display-manager.preset
> -rw-rw-r--. 1 mock mock? 2439 Aug? 6 08:19 90-default.preset
> -rw-rw-r--. 1 mock mock 12799 Aug? 6 08:20 centos-release-7-1.1503.tar.gz
> 
> SPECS/:
> total 8
> -rw-rw-r--. 1 mock mock 6471 Aug? 6 08:19 centos-release.spec
> (vgeppetto2 pts21) $grep "define upstream_rel"
SPECS/centos-release.spec
> %define upstream_rel 7.3
> (vgeppetto2 pts21) $
> 
> So if I am reading things correctly, it looks like the SOURCES are for
> 1503 and the spec file is for 1611.
> 
> Can someone please explain to me how to actually get the current SOURCES
> and SPEC for centos-release-7-5.1804.1 from centos git?
> 
> To be clear I know I can get the srpm from vault but I would like to
> understand
> how to work centos git.
> 
> Regards,
> 
I'll let Johnny comment on that but normally (if he has rights to push
to Sources) he's supposed to git commit & push to git and also push
binary sources to git.centos.org/sources/

But iirc, he reported that he had issues pushing to that area, so only
way to retrieve it was to use the src.rpm pkg pushed to vault.centos.org

-- 
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab

-------------- 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/attachments/20180807/118c5d99/attachment-0001.sig>

On 08/06/2018 08:15 AM, me at tdiehl.org wrote:
> Hi,
> 
> I am trying to retrieve the srpm for the latest centos-release pacakge
> from centos-git by following the instructions @
> https://wiki.centos.org/Sources.
> 
> If I run the following commands:
> git clone? https://git.centos.org/git/rpms/centos-release.git
> cd centos-release/
> git checkout c7
> ~/centos-git-common/get_sources.sh
> 
> Everything completes without error. The problem is that the sources that
> get
> downloaded are not for 1804.
> 
> (vgeppetto2 pts21) $ ll SOURCES/ SPECS/
> SOURCES/:
> total 28
> -rw-rw-r--. 1 mock mock? 1584 Aug? 6 08:19 1000-centos-release-cr.patch
> -rw-rw-r--. 1 mock mock?? 264 Aug? 6 08:19 85-display-manager.preset
> -rw-rw-r--. 1 mock mock? 2439 Aug? 6 08:19 90-default.preset
> -rw-rw-r--. 1 mock mock 12799 Aug? 6 08:20 centos-release-7-1.1503.tar.gz
> 
> SPECS/:
> total 8
> -rw-rw-r--. 1 mock mock 6471 Aug? 6 08:19 centos-release.spec
> (vgeppetto2 pts21) $grep "define upstream_rel"
SPECS/centos-release.spec
> %define upstream_rel 7.3
> (vgeppetto2 pts21) $
> 
> So if I am reading things correctly, it looks like the SOURCES are for
> 1503 and the spec file is for 1611.
> 
> Can someone please explain to me how to actually get the current SOURCES
> and SPEC for centos-release-7-5.1804.1 from centos git?
> 
> To be clear I know I can get the srpm from vault but I would like to
> understand
> how to work centos git.
> 
> Regards,
> 
The issue is specifically with the ability to push sources to
git.centos.org in the shadow cache.

I can't do that in the current setup, only Red Hat RCM can.  I can push
text into git, but not binary files to shadow cache.

The only package impacted is centos-release, because it is the only
package that we actually change the tarball and where I would need to
push to shadow cache.

If I push the spec changes, but not the shadow cache changes, it renders
centos-release not buildable.

We are working on an update whereby I will be able to push the changes
to git.centos.org .. when we get that in place, I will maintain
centos-release there like all the other packages.

In the mean time, we have a 'unified centos-release' here in git (for
all c7 arches):

https://github.com/CentOS/sig-core-AltArch/tree/master/centos-release

You will still need to download the SRPM to get the tarball.

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/attachments/20180815/f349c65d/attachment-0001.sig>

Hi Johnny,

On Wed, 15 Aug 2018 johnny at centos.org wrote:
> The issue is specifically with the ability to push sources to
> git.centos.org in the shadow cache.
> 
> I can't do that in the current setup, only Red Hat RCM can.  I can push
> text into git, but not binary files to shadow cache.
> 
> The only package impacted is centos-release, because it is the only
> package that we actually change the tarball and where I would need to
> push to shadow cache.
> 
> If I push the spec changes, but not the shadow cache changes, it renders
> centos-release not buildable.
> 
> We are working on an update whereby I will be able to push the changes
> to git.centos.org .. when we get that in place, I will maintain
> centos-release there like all the other packages.
> 
> In the mean time, we have a 'unified centos-release' here in git
(for
> all c7 arches):
> 
> https://github.com/CentOS/sig-core-AltArch/tree/master/centos-release
> 
> You will still need to download the SRPM to get the tarball.
Thanks for the update.

Will there be some kind of announcement when you are able to push to
git.centos.org?

Regards,

-- 
Tom			me at tdiehl.org