In the expected place for srpms for RHEL7 there is a README
ftp.redhat.org:/redhat/linux/enterprise/7Server/en/os/README
It's contents are
---------------------------------------------------------------------------- Current sources for Red Hat Enterprise Linux 7 have been moved to the following location:
https://git.centos.org/project/rpms ----------------------------------------------------------------------------
Who/what is populating this area?
How are updates to packages handled? Do they go straight to https://git.centos.org/project/rpms/ as the updates are published by RedHat?
Does CentOS modify any of these packages?
Since it is implied that this "represents" the "srpm" for a given RHEL package (given the above README from ftp.redhat.com) how do I know it has not been tampered with?
-Connie Sieh
On 06/10/2014 11:58 PM, Connie Sieh wrote:
In the expected place for srpms for RHEL7 there is a README
ftp.redhat.org:/redhat/linux/enterprise/7Server/en/os/README
It's contents are
Current sources for Red Hat Enterprise Linux 7 have been moved to the following location:
https://git.centos.org/project/rpms
Who/what is populating this area?
Questions about RHEL and what / how they do their thing need to be sent their way.
How are updates to packages handled? Do they go straight to https://git.centos.org/project/rpms/ as the updates are published by RedHat?
Does CentOS modify any of these packages?
our process in centos.org starts with the git repos, just as anyone else's would be.
Since it is implied that this "represents" the "srpm" for a given RHEL package (given the above README from ftp.redhat.com) how do I know it has not been tampered with?
same way as any other code, you'll need to build and work with your level of trust here. This is the code we are consuming, if you need and want signed content, we will be publishing signed srpms as a part of the CentOS release process, you might prefer to track that instead.
regards
On 06/10/2014 06:58 PM, Connie Sieh wrote:
In the expected place for srpms for RHEL7 there is a README
ftp.redhat.org:/redhat/linux/enterprise/7Server/en/os/README
It's contents are
Current sources for Red Hat Enterprise Linux 7 have been moved to the following location:
https://git.centos.org/project/rpms
Who/what is populating this area?
How are updates to packages handled? Do they go straight to https://git.centos.org/project/rpms/ as the updates are published by RedHat?
Does CentOS modify any of these packages?
Since it is implied that this "represents" the "srpm" for a given RHEL package (given the above README from ftp.redhat.com) how do I know it has not been tampered with?
If you look at the GIT activity log it is pretty easy to see how updates are coming to GIT by looking at the 0-day pushes.
Carl.
On 06/10/2014 08:49 PM, Carl Trieloff wrote:
If you look at the GIT activity log it is pretty easy to see how updates are coming to GIT by looking at the 0-day pushes.
How do I find all of those?
Pat
On 06/11/2014 08:59 AM, Pat Riehecky wrote:
On 06/10/2014 08:49 PM, Carl Trieloff wrote:
If you look at the GIT activity log it is pretty easy to see how updates are coming to GIT by looking at the 0-day pushes.
How do I find all of those?
https://git.centos.org/activity/
or better, just git clone and then do cmd line on your local repo.
Carl.
On 06/11/2014 08:18 AM, Carl Trieloff wrote:
On 06/11/2014 08:59 AM, Pat Riehecky wrote:
On 06/10/2014 08:49 PM, Carl Trieloff wrote:
If you look at the GIT activity log it is pretty easy to see how updates are coming to GIT by looking at the 0-day pushes.
How do I find all of those?
https://git.centos.org/activity/
or better, just git clone and then do cmd line on your local repo.
That url shows all activity for all repos. I'm just looking for the RHEL 7 sources.
https://git.centos.org/project/rpms
is a closer URL, but this requires me to go through all the repos, apparently, by hand.
Is there any tooling I can use to get this in an automated, "scriptable" manner?
Pat
Gitblit offers an API that should permit you to list repos easily enough: http://gitblit.com/rpc.html
It seems pretty trivial to use, e.g.: https://git.centos.org/rpc?req=LIST_REPOSITORIES
You should be able to use that to clone all of the repos and then use some combination of 'git fetch' and 'git log' to get the activity logs. Or use the RSS feeds for each repo, if you prefer. TIMTOWTDI.
This seems like a significant improvement, since you no longer have to diff the ftp 'ls' output -- there are actual machine-consumable feeds and APIs to use.
On Wed, Jun 11, 2014 at 9:28 AM, Pat Riehecky riehecky@fnal.gov wrote:
On 06/11/2014 08:18 AM, Carl Trieloff wrote:
On 06/11/2014 08:59 AM, Pat Riehecky wrote:
On 06/10/2014 08:49 PM, Carl Trieloff wrote:
If you look at the GIT activity log it is pretty easy to see how
updates
are coming to GIT by looking at the 0-day pushes.
How do I find all of those?
https://git.centos.org/activity/
or better, just git clone and then do cmd line on your local repo.
That url shows all activity for all repos. I'm just looking for the RHEL 7 sources.
https://git.centos.org/project/rpms
is a closer URL, but this requires me to go through all the repos, apparently, by hand.
Is there any tooling I can use to get this in an automated, "scriptable" manner?
Pat
-- Pat Riehecky
Scientific Linux developer http://www.scientificlinux.org/
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 06/11/2014 02:47 PM, Chris St. Pierre wrote:
Gitblit offers an API that should permit you to list repos easily enough: http://gitblit.com/rpc.html
It seems pretty trivial to use, e.g.: https://git.centos.org/rpc?req=LIST_REPOSITORIES
You should be able to use that to clone all of the repos and then use some combination of 'git fetch' and 'git log' to get the activity logs. Or use the RSS feeds for each repo, if you prefer. TIMTOWTDI.
This seems like a significant improvement, since you no longer have to diff the ftp 'ls' output -- there are actual machine-consumable feeds and APIs to use.
and there are federation opportunities as well, so its possible for people to bring up and run their own git mirrors for the repos they care about ( and are public ).
- KB
So, in order to custom rebuild a distro from git repos, one should: Extract the list of repos Clone *all* the git repos locally, and switch to the right branch run get_sources.sh in all the repos then run rpmbuild -bs *.spec in the right directory, for each repo.
I am sure there is/should be a slightly more efficient way than that. How about a repo that contains all the non-binary sources for all the packages?
Masoud
On Wed, Jun 11, 2014 at 8:05 AM, Karanbir Singh mail-lists@karan.org wrote:
On 06/11/2014 02:47 PM, Chris St. Pierre wrote:
Gitblit offers an API that should permit you to list repos easily enough: http://gitblit.com/rpc.html
It seems pretty trivial to use, e.g.: https://git.centos.org/rpc?req=LIST_REPOSITORIES
You should be able to use that to clone all of the repos and then use some combination of 'git fetch' and 'git log' to get the activity logs. Or use the RSS feeds for each repo, if you prefer. TIMTOWTDI.
This seems like a significant improvement, since you no longer have to diff the ftp 'ls' output -- there are actual machine-consumable feeds and APIs to use.
and there are federation opportunities as well, so its possible for people to bring up and run their own git mirrors for the repos they care about ( and are public ).
- KB
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 06/11/2014 11:12 AM, Masoud Sharbiani wrote:
So, in order to custom rebuild a distro from git repos, one should: Extract the list of repos Clone *all* the git repos locally, and switch to the right branch run get_sources.sh in all the repos then run rpmbuild -bs *.spec in the right directory, for each repo.
I am sure there is/should be a slightly more efficient way than that. How about a repo that contains all the non-binary sources for all the packages?
Once we release a CentOS RPM that we build into a tree, the SRPM that goes along with it will be signed and released into the applicable Source directory exactly as we do it now. For people who want to wait for that, they can. If, on the other hand, someone wants to grab the source directly from here .. they can do that as well.
Once kernel.org has a kernel for release, they publish it ... before that time you are free to grab stuff out of their git tree if you want. Our process is identical to that.
People can clone as many or as few things as they want and do whatever they want to with it. They can access it in many different ways.
On 06/11/2014 11:12 AM, Masoud Sharbiani wrote:
So, in order to custom rebuild a distro from git repos, one should: Extract the list of repos Clone *all* the git repos locally, and switch to the right branch run get_sources.sh in all the repos then run rpmbuild -bs *.spec in the right directory, for each repo.
I am sure there is/should be a slightly more efficient way than that. How about a repo that contains all the non-binary sources for all the packages?
And BTW .. what you described is EXACTLY how "I" am doing right now. I checked out the repos and I am going through them and deciding what needs to be built right now (that is different than the RC). That is EXACTLY how CentOS will be produced from this code.
What you see here is what we (the CentOS team) have to work with. What we develop as a community to make this easier is how it will get easier. That's how open source community projects work. That is what everyone wanted ... CentOS to be completely open with how we build and what we use. That is what we are doing.
If YOU want to make something easier ... do what Pat is doing and look at the centos-git-common tree, figure out a better way to do something and submit code to make it work.
YOU have EXACTLY what we have ... we are building from there too.
Thanks, Johnny Hughes
Fyi - I have entered an upstream bug requesting that srpms continue to be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
Others may wish to visit the bug and provide additional comments.
Kay
Am 13.06.2014 21:39, schrieb Kay Williams:
Fyi - I have entered an upstream bug requesting that srpms continue to be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
That bug is allready private :)
On Friday, June 13, 2014 12:42 PM, Christoph Galuschka wrote:
Am 13.06.2014 21:39, schrieb Kay Williams:
Fyi - I have entered an upstream bug requesting that srpms continue
to
be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
That bug is allready private :)
Here is the text. Perhaps others can submit separate bugs. Or perhaps others will know of a better channel to submit feedback to upstream, not sure. Maybe twitter? :-)
============================================================================ ===
Description of problem:
For previous versions of RHEL, SRPMS were available for download from http://ftp.redhat.com/redhat/linux/enterprise/...
For RHEL 7, a README.TXT file in these locations states:
----------
Current sources for Red Hat Enterprise Linux 7 have been moved to the following location:
https://git.centos.org/project/rpms
-----------
This change is problematic for a number of reasons:
1. The new location does not provide sources in SRPM format. Instead, source code is available from git repositories.
2. Obtaining sources from git repositories is more cumbersome than working with srpms. First git must be installed. Then the repository cloned. At this point a small subset of the sources is downloaded (typically the spec files and patches). An additional utility (get_sources.sh) must be downloaded and used to obtain the remaining sources.
Compare this to downloading an srpm and running 'rpm -i .." to obtain the sources.
3. Sources from the centos git repositories are not guaranteed to be 'pristine'. CentOS changes source code for a number of packages. While it is possible to filter out the CentOS changes, this is an extra step. It seems appropriate for Red Hat (in the spirit of open source) to provide pristine sources.
4. Many tools exist today for working with srpms. For example, srpms can be easily queried and downloaded using yum in a manner very similar to rpms. These tools allow organizations to download, patch and rebuild software, e.g. to fix bugs or add features. On a broader scale, such tools allow third parties to create custom Linux distribution based on Red Hat sources.
Because of the substantial differences between SRPMs and git repositories, new tools will need to be written, and existing tools will need to be significantly rewritten.
Git repositories do have some advantages, and, over the long run, the git model may well be preferable to the SRPM model. Certainly, git repos make sense as a companion to srpms.
In the short run, however, the abrupt removal of srpms creates a great deal of (seemingly unnecessary) pain and confusion for the community.
Please consider making srpms available again, at least for some period of time. This allows tools to be updated and an orderly transition to occur.
In addition, it would be useful to see a statement from Red Hat on the reasoning behind the change. This would reduce confusion, as well as suspicion that Red Hat desires to make it harder to access source code.
On Friday, June 13, 2014 12:42 PM, Christoph Galuschka wrote:
Am 13.06.2014 21:39, schrieb Kay Williams:
Fyi - I have entered an upstream bug requesting that srpms continue
to
be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
That bug is allready private :)
A couple of folks have sent private email asking to be cc'd on the bug, which allows viewing and (I think) posting comments. I am happy to do that for anyone who is interested. Send me an email.
Also, thanks for Karston Wade who has requested that the bug be made public. Hopefully that can happen.
Kay
On Friday, June 13, 2014 6:47 PM, Kay Williams wrote:
On Friday, June 13, 2014 12:42 PM, Christoph Galuschka wrote:
Am 13.06.2014 21:39, schrieb Kay Williams:
Fyi - I have entered an upstream bug requesting that srpms continue
to
be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
That bug is allready private :)
Also, thanks for Karston Wade who has requested that the bug be made public. Hopefully that can happen.
The bug is now public. Apparently a workflow rule was automatically marking all RHEL7 bugs as private.
Last I talked to my SE, they had to make private the default since logs, etc could potentially contain sensitive information. They didn't want to expose themselves to litigation because someone accidentally uploaded a script with their root password (or worse) in it. :-)
Matt On Jun 13, 2014 11:30 PM, "Kay Williams" kay@deployproject.org wrote:
On Friday, June 13, 2014 6:47 PM, Kay Williams wrote:
On Friday, June 13, 2014 12:42 PM, Christoph Galuschka wrote:
Am 13.06.2014 21:39, schrieb Kay Williams:
Fyi - I have entered an upstream bug requesting that srpms continue
to
be posted at ftp.redhat.com. See https://bugzilla.redhat.com/show_bug.cgi?id=1109401
That bug is allready private :)
Also, thanks for Karston Wade who has requested that the bug be made public. Hopefully that can happen.
The bug is now public. Apparently a workflow rule was automatically marking all RHEL7 bugs as private.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Fyi – the bug at https://bugzilla.redhat.com/show_bug.cgi?id=1109401 has been marked “NOT A BUG”.
But if folks would like to express an opinion, there is a quick yes/no survey they can take.
Take the survey: https://www.surveymonkey.com/s/TNXZP9H
View the results: https://www.surveymonkey.com/results/SM-HZ8KLSD8/
Feel free to forward the survey. Perhaps if there is enough support Red Hat will reconsider. :-)
I do like the idea of having one package per repo. It is similar to what Fedora has and that I've used when taking a fedora package for EL6. I think the disadvantage is evident only when wanting to build all packages at the same time.
Kaj
Sent from my iPad
On 11 Jun 2014, at 19:13, Masoud Sharbiani <masoud.sharbiani@gmail.commailto:masoud.sharbiani@gmail.com> wrote:
So, in order to custom rebuild a distro from git repos, one should: Extract the list of repos Clone *all* the git repos locally, and switch to the right branch run get_sources.sh in all the repos then run rpmbuild -bs *.spec in the right directory, for each repo.
I am sure there is/should be a slightly more efficient way than that. How about a repo that contains all the non-binary sources for all the packages?
Masoud
On Wed, Jun 11, 2014 at 8:05 AM, Karanbir Singh <mail-lists@karan.orgmailto:mail-lists@karan.org> wrote: On 06/11/2014 02:47 PM, Chris St. Pierre wrote:
Gitblit offers an API that should permit you to list repos easily enough: http://gitblit.com/rpc.html
It seems pretty trivial to use, e.g.: https://git.centos.org/rpc?req=LIST_REPOSITORIES
You should be able to use that to clone all of the repos and then use some combination of 'git fetch' and 'git log' to get the activity logs. Or use the RSS feeds for each repo, if you prefer. TIMTOWTDI.
This seems like a significant improvement, since you no longer have to diff the ftp 'ls' output -- there are actual machine-consumable feeds and APIs to use.
and there are federation opportunities as well, so its possible for people to bring up and run their own git mirrors for the repos they care about ( and are public ).
- KB
-- Karanbir Singh +44-207-0999389tel:%2B44-207-0999389 | http://www.karan.org/ | twitter.com/kbsinghhttp://twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.orgmailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.orgmailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Jun 11, 2014 at 6:47 AM, Chris St. Pierre < chris.a.st.pierre@gmail.com> wrote:
Gitblit offers an API that should permit you to list repos easily enough: http://gitblit.com/rpc.html
It seems pretty trivial to use, e.g.: https://git.centos.org/rpc?req=LIST_REPOSITORIES
You should be able to use that to clone all of the repos and then use some combination of 'git fetch' and 'git log' to get the activity logs. Or use the RSS feeds for each repo, if you prefer. TIMTOWTDI.
This seems like a significant improvement, since you no longer have to diff the ftp 'ls' output -- there are actual machine-consumable feeds and APIs to use.
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
-Jeff
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
On 06/11/2014 03:49 PM, Karanbir Singh wrote:
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
I'm working on some tools to do this now, what's the best way to get them into centos-git-common?
On 06/11/2014 09:51 PM, Bonnie King wrote:
On 06/11/2014 03:49 PM, Karanbir Singh wrote:
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
I'm working on some tools to do this now, what's the best way to get them into centos-git-common?
send them here to the list, use the same process Pat has been using. Peer review for free! and everyone working with these souces sees the change
Here's a quick script to list repos for a given "project path". Needs simplejson and requests python modules.
On 06/11/2014 03:55 PM, Karanbir Singh wrote:
On 06/11/2014 09:51 PM, Bonnie King wrote:
On 06/11/2014 03:49 PM, Karanbir Singh wrote:
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
I'm working on some tools to do this now, what's the best way to get them into centos-git-common?
send them here to the list, use the same process Pat has been using. Peer review for free! and everyone working with these souces sees the change
On Wed, 11 Jun 2014, Karanbir Singh wrote:
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
What about the tools that are already in use in the current c7 rebuild. Can those be made available?
-Connie Sieh
On 06/11/2014 09:53 PM, Connie Sieh wrote:
On Wed, 11 Jun 2014, Karanbir Singh wrote:
On 06/11/2014 09:33 PM, Jeff Sheltren wrote:
Has anyone scripted this already (list repos, git clone them all, grab all sources)? I'm lazy, or busy, or something, and would love to easily clone these all locally.
sure, happy to host these sort of scripts in centos-git-common, although to be fair, the CEntOS SRPMS will be online shortly, people can always just track that right ?
What about the tools that are already in use in the current c7 rebuild. Can those be made available?
they already are. What bit are we missing ?
also, I believe you guys have the lorax and pungi scripts done - I've not started on those as yet, share ?
- KB
-
Bonnie King -
Carl Trieloff -
Chris St. Pierre -
Christoph Galuschka -
Connie Sieh -
Jeff Sheltren -
Johnny Hughes -
Kaj Niemi -
Karanbir Singh -
Kay Williams -
Masoud Sharbiani -
Matthew Hyclak -
Pat Riehecky