Bug 4868

Summary: dylan- release tarballs generated for meta-intel BSPs are wrong
Product: [Infrastructure] AutoBuilder Reporter: Tom Zanussi <tom.zanussi>
Component: autobuilderAssignee: Beth Flanagan <elizabeth.flanagan>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Undecided CC: elizabeth.flanagan, infras.ab.watcher, Infras.watcher, nitin.a.kamble, song.liu
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Tom Zanussi 2013-07-18 19:36:37 UTC 
Pointed out by a user on the Yocto ML:

https://lists.yoctoproject.org/pipermail/yocto/2013-July/017294.html

Users should be able to follow the instructions in the 'Usage Notes' section of the BSP's release notes on the website, but currently they can't because the directory structure bundled in the tarball doesn't match the release notes. i.e. the tarballs

It looks like there's a problem with the naming of the top-level directory in the tarball:

$ ls meta-crownbay
binary  common  conf  MAINTAINERS  meta-crownbay  meta-tlk  README

whereas after untarring, I should have been able to do:

$ ls meta-intel
binary  common  conf  MAINTAINERS  meta-crownbay  meta-tlk  README

It looks like previous releases had it right.

sugarbay also has the same problem, probably all the rest do too so should be checked.

Apparently this also is something that needs to be specifically spelled out in the release process.
Comment 1 Beth Flanagan 2013-07-18 22:13:28 UTC 
Currently regenerating tarballs. This was an issue with my release scripts. The immediate fix to to regenerate the tarballs (which is occurring now) and the md5sums. The longer term fix is to finish up the autobuilder buildstep for this (which has some bugs)
Comment 2 Beth Flanagan 2013-07-19 22:45:43 UTC 
Regenerated the tarballs. This is now fixed.