On Fri, Dec 11, 2020 at 11:39 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:

Am 11.12.20 um 15:07 schrieb Antal Nemeš:

...

Hi,

Will src.rpm packages be made available for Stream repositories?

Currently, I see only empty subdirs for 8-stream at https://vault.centos.org/centos/8-stream/

I haven't checked but take a look at git.centos.org (c8s tag) ...

There is *always* a potential mismatch between a git repo and the source actually used for building an RPM. SRPM's also have a gpg signature, git repos do not, and establishing provenance can be adventuresome. So can setting up the variety of git epos, along with the source tarballs, to assemble in a local compilation environment for local rpmbuild or mock.

So can stunning foolishness like the Fedora SRPM for chromium, which includes specific source files in the SRPM only if compiled on a specific operating system. I just noticed trying to backport Chromium 87 to CentOS 7.

Nico Kadel-Garcia

-- Leon

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

On 12/12/20 9:33 AM, Leon Fauster via CentOS-devel wrote:

Am 12.12.20 um 10:39 schrieb Nico Kadel-Garcia:

...

On Fri, Dec 11, 2020 at 11:39 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:

...

Am 11.12.20 um 15:07 schrieb Antal Nemeš:

...

Hi,

Will src.rpm packages be made available for Stream repositories?

Currently, I see only empty subdirs for 8-stream at https://vault.centos.org/centos/8-stream/

I haven't checked but take a look at git.centos.org (c8s tag) ...

There is *always* a potential mismatch between a git repo and the source actually used for building an RPM. SRPM's also have a gpg signature, git repos do not, and establishing provenance can be adventuresome. So can setting up the variety of git epos, along with the source tarballs, to assemble in a local compilation environment for local rpmbuild or mock.

So can stunning foolishness like the Fedora SRPM for chromium, which includes specific source files in the SRPM only if compiled on a specific operating system. I just noticed trying to backport Chromium 87 to CentOS 7.

Sure, I would also like to see such SRPMs but as you see it for C8, there are no SRPMs anymore on RedHat's ftp/http servers, the sources are consolidated in git now. Maybe someone from RH could highlight this aspect (C8S) here a bit more ...

Not sure what the question is .. but:

All packages, except the kernel because of secureboot, are built directly from git.centos.org from the c8s branch.

For example .. (just picking a build at random):

https://koji.mbox.centos.org/koji/buildinfo?buildID=15034

If you look at the Source Line .. you will see:

hhttps://git.centos.org/rpms/thermald#14acf460654c5788d9c7792f36fed45c7e00a38...

That is the exact source used to build this package set

If you want to create the SRPM .. you would: ======= git clone https://git.centos.org/rpms/thermald

cd thermald

git checkout 14acf460654c5788d9c7792f36fed45c7e00a387

into_srpm.sh

=======

You will then have the SRPM in the SRPMs dir of your git repo .. it will also be exploded and ready for you to use in SPECS and SOURCES to make changes.

If you do not have the git tools downloaded .. where into_srpm.sh comes from, you can get it from here:

git clone https://git.centos.org/centos-git-common

So, to clarify, we build Centos Linux 8 and CentOS Stream directly from git.centos.org and you can look at the bild and get the exact git commit id that was used on the build.

On 12/16/20 6:03 PM, Antal Nemeš wrote:

...

-----Original Message----- From: CentOS-devel centos-devel-bounces@centos.org On Behalf Of Johnny Hughes Sent: Tuesday, 15 December 2020 22:16 To: centos-devel@centos.org Subject: Re: [CentOS-devel] Centos Stream - src.rpms?

On 12/12/20 9:33 AM, Leon Fauster via CentOS-devel wrote:

...

Am 12.12.20 um 10:39 schrieb Nico Kadel-Garcia:

...

On Fri, Dec 11, 2020 at 11:39 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:

...

Am 11.12.20 um 15:07 schrieb Antal Nemeš:

...

Hi,

Will src.rpm packages be made available for Stream repositories?

Currently, I see only empty subdirs for 8-stream at https://vault.centos.org/centos/8-stream/

I haven't checked but take a look at git.centos.org (c8s tag) ...

There is *always* a potential mismatch between a git repo and the source actually used for building an RPM. SRPM's also have a gpg signature, git repos do not, and establishing provenance can be adventuresome. So can setting up the variety of git epos, along with the source tarballs, to assemble in a local compilation environment for local rpmbuild or mock.

So can stunning foolishness like the Fedora SRPM for chromium, which includes specific source files in the SRPM only if compiled on a specific operating system. I just noticed trying to backport Chromium 87 to CentOS 7.

Sure, I would also like to see such SRPMs but as you see it for C8, there are no SRPMs anymore on RedHat's ftp/http servers, the sources are consolidated in git now. Maybe someone from RH could highlight this aspect (C8S) here a bit more ...

Not sure what the question is .. but:

All packages, except the kernel because of secureboot, are built directly from git.centos.org from the c8s branch.

For example .. (just picking a build at random):

https://koji.mbox.centos.org/koji/buildinfo?buildID=15034

If you look at the Source Line .. you will see:

hhttps://git.centos.org/rpms/thermald#14acf460654c5788d9c7792f36fed45c 7e00a387

That is the exact source used to build this package set

If you want to create the SRPM .. you would:

git clone https://git.centos.org/rpms/thermald

cd thermald

git checkout 14acf460654c5788d9c7792f36fed45c7e00a387

into_srpm.sh

=======

You will then have the SRPM in the SRPMs dir of your git repo .. it will also be exploded and ready for you to use in SPECS and SOURCES to make changes.

If you do not have the git tools downloaded .. where into_srpm.sh comes from, you can get it from here:

git clone https://git.centos.org/centos-git-common

So, to clarify, we build Centos Linux 8 and CentOS Stream directly from git.centos.org and you can look at the bild and get the exact git commit id that was used on the build.

1. For Centos Stream, will this be a formal method for obtaining src.rpms, or will src.rpms be made available on vault.centos.org?
2. Does this procedure work for modular packages as well?
3. Does koji store all builds or is there an age cutoff? Will I be able to follow the src.rpm build process for a package built a year ago?

I'm sure src rpms will also be available in the future, once all the hardware and mirrors are in place (we can not support downloading directl off our main koji machine that controls all the builds.

But in our build system, the SRPMS are built literally on the fly, from the commitid out of git. We do not use srpms directly, we build from the git repo.

On Sat, Dec 26, 2020 at 12:28 AM Tetsuo Handa from-centos@i-love.sakura.ne.jp wrote:

On 2020/12/16 6:16, Johnny Hughes wrote:

...

All packages, except the kernel because of secureboot, are built directly from git.centos.org from the c8s branch.

For example .. (just picking a build at random):

https://koji.mbox.centos.org/koji/buildinfo?buildID=15034

I'm waiting for telnet-0.17-75.el8 to be released because one of RHEL customers needs it. While I can find it at https://koji.mbox.centos.org/koji/buildinfo?buildID=14800 , the download link https://koji.mbox.centos.org/pkgs/packages/telnet/0.17/75.el8/x86_64/telnet-... is "HTTP 403 Forbidden". That keeps me away from helping QA using my environment. If the customer can download telnet-server-0.17-75.el8.x86_64.rpm , the customer would be able to help QA using the customer's environment.

It seems that any download link for *.rpm returns 403. Why?

Hi Tetsuo (熊猫さん),

Jim Perrin, who was a CentOS dev at that time, wrote in his post (1),

"A couple reasons for this. Just because things build doesn't mean they're ready. We sometimes need to iterate builds, and having people pulling packages direct from the build system makes supporting this challenging, especially if they have a matching NVR build that's not the right one. The packages may or may not be signed yet, depending on when someone tries to pull from koji. We'd prefer people wait for the actual release when we're sure everything is right. Lastly, the builders aren't on mirrored systems, so there's a bandwidth cost from people attempting to pull directly. The administrative block solves all 3 of these issues."

Regarding telnet, dnf seems to find it on my test CStream box:

$ sudo dnf list telnet-server Last metadata expiration check: 1:02:53 ago on Sat 26 Dec 2020 10:07:12 AM PST. Available Packages telnet-server.x86_64 1:0.17-75.el8 Stream-AppStream

Akemi / toracat

(1) https://lists.centos.org/pipermail/centos-devel/2019-October/036167.html