build: master:7d22ef28e64de06b6238d0ef9b664c0bee6efa46 date: Feb 20 10:27 Auttobuilder repo: http://autobuilder.yoctoproject.org/pub/nightly/20130220-2/ builder: http://autobuilder.yoctoproject.org:8010/builders/nightly/builds/912 As the title says, the repodata folder is not created. Last build that has repodata: master-next: b99fc8445207a750ef70f1e20244074caf805272 date: Feb 16 23:49 Autobuilder repo: http://autobuilder.yoctoproject.org/pub/nightly/20130216-3/ builder: http://autobuilder.yoctoproject.org:8010/builders/nightly/builds/907
Update: I see the repodata folder was moved to rpm/<architecture> . Is this correct?
I'm not sure if this is correct for rpm generation, but the autobuilder just cp's whatever was created in the tmp/deploy/rpm directory. So, if this is incorrect behavior, this should end up as a bug against core and not the autobuilder.
This is an expected change. With the introduction of Smart, we now create an index per package architecture so that we don't have to re-create the whole index every time the list of package architectures changes (which can happen between two different images e.g. in the case of multilib). Are there test cases or anything else that rely upon this data being available? I'm not sure we should be copying it around.
There are no test cases in the master branch test plan that require the previous repodata structure. We ware not aware of the change and thus we filed a bug. I believe we can close as NOTABUG.
OK, marking as suggested. Thanks!
Verified as per above comments.