On Wed, Oct 7, 2020, at 08:00, plageat@tut.by wrote:
It does not, because the source is pushed from SRPMs, not the internal RHEL git repositories.
Sure. but why don't push self-contained info at least? Especially while (I think) modulemd is stored internally somehow along with those SRPMs. I mean, for example:
https://git.centos.org/rpms/perl-DBD-Pg/commits/c8s-stream-3.7
pushed with 3 tags
imports/c8s-stream-3.7/perl-DBD-Pg-3.7.4-4.module+el8.3.0+6565+7d8e397c imports/c8s-stream-3.7/perl-DBD-Pg-3.7.4-4.module+el8.3.0+6565+907cf59b imports/c8s-stream-3.7/perl-DBD-Pg-3.7.4-4.module+el8.3.0+6565+c57d755d
Which are built with perl:5.24, perl:5.26 and perl:5.30? No chance to figure out. Those tags are almost useless info ATM.
Just import with something like:
imports/c8s-stream-3.7/perl-DBD-Pg-3.7.4-4.module+el8.3.0+6565+7d8e397c/perl:5.24
The same is for modulemd imports.
https://git.centos.org/modules/perl-DBD-Pg/commits/c8s-stream-3.7
Here tags are:
imports/c8s-stream-3.7/perl-DBD-Pg-3.7-8030020200313075823.56fce90f imports/c8s-stream-3.7/perl-DBD-Pg-3.7-8030020200313075823.98a3c9d0 imports/c8s-stream-3.7/perl-DBD-Pg-3.7-8030020200313075823.bde36347
Those 3 above are examples of TOTALLY USEFULL information without connected perl streams.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
It would seem simple at first glance but it really isn't. The push tooling (which creates those tags) separates the module RPM pushes and the module metadata pushes, it doesn't know much directly about the relationship between them.
--Brian