[rdo-dev] Reorganization of rdoinfo repository

[Alfredo Moralejo Alonso]

Hi,

Note that rdoinfo reorganization has surfaced an issue in distroinfo which
impacts rdopkg when used without local rdoinfo location. For example,
running:

rdopkg info <package name>

fails because it fail to download all data files. A patch has been already
proposed [1] which fixes it. Until done, you can workaround this issue by
cloning rdoinfo first and using local info option:

git clone https://github.com/redhat-openstack/rdoinfo
rdopkg info -l <full path to local rdoinfo> <package name>

Sorry for all the inconveniences this may cause you, we are working to get
the fix merged and a new released ASAP.

Regards,

Alfredo

[1] https://softwarefactory-project.io/r/#/c/14907/






On Wed, Jan 30, 2019 at 10:56 AM Alfredo Moralejo Alonso <
amoralej at redhat.com> wrote:

> Hi RDOers,
>
> Note that the rdoinfo reorganization has been merged and we are monitoring
> that everything keeps running as expected. Let us know if you observe any
> abnormal behavior.
>
> If you are using rdopkg, make sure you are using the latest released
> version (0.47.3) or you may find unexpected results in some cases.
>
> Best regards,
>
> Alfredo
>
>
>
> On Mon, Jan 28, 2019 at 1:00 PM Alfredo Moralejo Alonso <
> amoralej at redhat.com> wrote:
>
>> Hi,
>>
>> As discussed some weeks ago, we are reorganizing data files in rdoinfo
>> repository. The goals of this reorganization is to improve the CI and
>> management in gerrit, as discussed in [1]. After this reorganization:
>>
>> - rdo.yml and deps.yml contain all info but tags and buildsys.tags for
>> OpenStack packages and dependencies.
>> - tags (used by DLRN instances to identify what packages tu build in RDO
>> Trunk repos) information are stored in files under "tags" directory. There
>> is a file named <tag>.yml for eah tag.
>> - buildsys-tags (used to tag the backages in CBS and specify what builds
>> go to each CloudSIG repo) will be stored in a file named <buildsys-tag>.yml
>> under "buildsys-tags" directory.
>>
>> Note that after merging this change [2], when you need to update tags or
>> buildsys-tags to add new packages, new deps or propose updates, you need to
>> use the corresponding tag files instead of rdo.yml or deps.yml.
>>
>> Also note that, if you have some script or tool which parses rdo.yml or
>> deps.yml, you need to adapt it to this change. The recommended way to parse
>> rdoinfo is to use distroinfo [3], as it hides the actual distribution of
>> data in files. This change will not affect any tool using distroinfo.
>>
>> In the next dates we will update the documentation in RDO to reflect this
>> change.
>>
>> Don't hesitate to contact me on #rdo or using this mail list if you have
>> further questions or doubts.
>>
>> Best regards,
>>
>> Alfredo
>>
>> [1] https://review.rdoproject.org/etherpad/p/rdoinfo-reorg
>> [2] https://review.rdoproject.org/r/18563
>> [3] https://github.com/softwarefactory-project/distroinfo
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20190130/8b4180ab/attachment.html>