on the log above we see that the update-initramfs call is actually
catched by a trigger before the initial initrd can be generated.
sadly the postinst scripts try to copy the initrd around right in the next
step. to fix this, either
update-initramfs -c -k $version
needs to be run forcefully without trigger, or the copying of the initrd needs
to move to a later point at which it is guaranteed that an initrd exists at the
source location.
** Summary changed:
- cannot install linux-ti-omap4 3.5.0-209-omap4
+ linux-ti-omap4 generates the initial initrd to late for its own postinst
scripts
** Changed in: linux-meta-ti-omap4 (Ubuntu)
Importance: Undecided => High
** Also affects: linux-ti-omap4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-ti-omap4 (Ubuntu)
Importance: Undecided => High
** Changed in: linux-meta-ti-omap4 (Ubuntu)
Status: New => Invalid
** Also affects: linux-ti-omap4 (Ubuntu Quantal)
Importance: High
Status: New
** Also affects: linux-meta-ti-omap4 (Ubuntu Quantal)
Importance: High
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041607
Title:
linux-ti-omap4 generates the initial initrd to late for its own
postinst scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-ti-omap4/+bug/1041607/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
