make sure source is obtainable for uec kernel images
Bug #444605 reported by
Scott Moser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| vm-builder (Ubuntu) |
Fix Released
|
Medium
|
Scott Moser | ||
| Karmic |
Fix Released
|
Medium
|
Scott Moser | ||
Bug Description
the uec-images build output currently contains a kernel and ramdisk for easy use bundling by the end user.
We need to make sure that the source that created these images can be obtained (per gpl requirement).
This may require some changes to the ec2-automated-
| Changed in vm-builder (Ubuntu): | |
| assignee: | nobody → Scott Moser (smoser) |
| importance: | Undecided → Medium |
| Changed in vm-builder (Ubuntu Karmic): | |
| milestone: | none → ubuntu-9.10 |
| Changed in vm-builder (Ubuntu Karmic): | |
| status: | New → Triaged |
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| Changed in vm-builder (Ubuntu Karmic): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
The uec build output has 2 kernels and 2 initrd per arch (1 set for uec, 1 set for ec2). There is information available for each that indicates the pedigree.
a.) the manifest file for the build : the kernels come from a package inside of the image, and all packages and versions are listed here
b.) the kernel-info.txt file : this file has explicit information on where each kernel/initrd file came from.
For b, an example:
karmic-
karmic-
karmic-
karmic-
The above tab-delimited content represents:
- file name in the build output
- original file name in the image
- arch
- package from which the file came (for initrd, this is the kernel package)
- package version
That should provide us with plenty of information to get the source for a given image.