This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu54.2
---
flash-kernel (3.0~rc.4ubuntu54.2) vivid; urgency=medium
* Cherry pick from Debian: Succeed but do nothing when run on an
unknown machine which was booted via EFI. (LP: #1517582)
-- dann frazier Wed, 09 D
This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu55.1
---
flash-kernel (3.0~rc.4ubuntu55.1) wily; urgency=medium
* Cherry pick from Debian: Succeed but do nothing when run on an
unknown machine which was booted via EFI. (LP: #1517582)
-- dann frazier Wed, 09 De
This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu49.7
---
flash-kernel (3.0~rc.4ubuntu49.7) trusty; urgency=medium
* Cherry pick from Debian: Succeed but do nothing when run on an
unknown machine which was booted via EFI. (LP: #1517582)
-- dann frazier Wed, 09
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582
Title:
flash-kernel causes postinsts to fail when it happens to be installed
on an unsupported system
To man
I verified for trusty, vivid, and wily. Setting to verification-done
for these three releases.
** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-done-vivid
verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bu
Hello Newell, or anyone else affected,
Accepted flash-kernel into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.0~rc.4ubuntu54.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
And also verify for trusty too...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582
Title:
flash-kernel causes postinsts to fail when it happens to be installed
on an unsupported system
To ma
** Changed in: flash-kernel (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: flash-kernel (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: flash-kernel (Ubuntu Wily)
Status: New => Confirmed
** Changed in: flash-kernel (Ubuntu Trusty)
Assignee: Newell Jense
** Changed in: flash-kernel (Ubuntu Wily)
Assignee: (unassigned) => Newell Jensen (newell-jensen)
** Changed in: flash-kernel (Ubuntu Vivid)
Assignee: (unassigned) => Newell Jensen (newell-jensen)
** Changed in: flash-kernel (Ubuntu Trusty)
Assignee: (unassigned) => Newell Jensen (
** Description changed:
- For xgene-2 soc on EFI system, flash-kernel is failing:
+ For xgene-2 soc on UEFI system, flash-kernel is failing with:
+ root@(none):/# apt-get --reinstall install linux-image-4.2.0-1-arm64; echo $?
+ Reading package lists... Done
+ Building dependency tree
+ Reading
** Also affects: flash-kernel (Ubuntu Xenial)
Importance: Undecided
Assignee: Newell Jensen (newell-jensen)
Status: Fix Released
** Also affects: flash-kernel (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: flash-kernel (Ubuntu Vivid)
Importance: Und
well, it would just be consistent with the rest of the distro, build
system, etc to use the env var, but given that debian accepted and
uploaded the patch already, we'll get it anyway with the next upstream
sync, so indeed go ahead :)
--
You received this bug notification because you are a member
We do support arm64 UEFI systems for server and for those, there's no
use case for flash-kernel to do anything. It does commonly get installed
though. Though flash-kernel-installer knows not to make d-i install it
on arm*/efi systems, it does tend to get installed via other mechanisms.
curtin image
It should be noted that the upstream patch does not make it so you
cannot enable a UEFI system. The patch works like this:
If the machine is found to be unsupported (i.e. is not added to the
all.db file for supported or no-op), it then checks if the system is EFI
and if it is, it prints a warning
i dont know if it will make sense to run f-k on a UEFI system, i can
tell you once we support one ;)
in any case there is a mechanism to make f-k skip all f-k calls ever.
that didnt work in your case, which i "fixed" (in quotes because the var
lives in three places now, it should be moved into mai
This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu56
---
flash-kernel (3.0~rc.4ubuntu56) xenial; urgency=medium
* make the package postinst respect FLASH_KERNEL_SKIP (LP: #1517582)
-- Oliver Grawert Wed, 25 Nov 2015 21:12:16 +0100
** Changed in: flash-kernel (Ubunt
It seems to me that the mere installation of an installable package -
even if it isn't useful on the platform - shouldn't start breaking
kernel upgrades. And users shouldn't be expected to know that there's a
magic envvar they have to set to to avoid it.
The question is - does it ever make sense t
I already filed a bug and patch to the upstream Debian flash-kernel
yesterday:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806171
** Bug watch added: Debian Bug tracker #806171
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806171
--
You received this bug notification because you are
i just uploaded http://paste.ubuntu.com/13506065/ to xenial ... in case
someone wants to SRU that to wily ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582
Title:
flash-kernel causes postins
this is actually a different issue to the one from the original bug description
...
here it is flash-kernels postinst itself that gets executed and there is indeed
a bug ...
the variable is respected everywhere else (i.e. in
/etc/kernel/postinst.d/zz-flash-kernel or /etc/initramfs/post-update.d
Trying the export as was mentioned (I believe in the correct way):
root@(none):/# export FLASH_KERNEL_SKIP=1
root@(none):/# apt-get --reinstall install linux-image-4.2.0-1-arm64; echo $?
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 n
(also note that there are UEFI based arm systems, the patch would break
them)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582
Title:
flash-kernel causes postinsts to fail when it happens to be
please make sure your build tool properly exports FLASH_KERNEL_SKIP=1 to
the environment, flash-kernel has the right mechanics builtin since
years, your environment needs to provide the right settings for it, this
isnt a flash-kernel bug ...
** Changed in: flash-kernel (Ubuntu)
Status: In P
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Newell Jensen (newell-jensen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517582
Title:
flash-kernel causes postinsts to fail w
I tested this change with MAAS and this gets us past the flash-kernel
error.
** Changed in: flash-kernel (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/151758
The following should fix the issue of flash-kernel, could anyone give a test in
MAAS?
diff --git a/functions b/functions
index 97bbdd9..e753054 100644
--- a/functions
+++ b/functions
@@ -429,6 +429,10 @@ fi
kfile_suffix=$(get_kfile_suffix "$kfile")
if ! check_supported "$machine"; then
+
26 matches
Mail list logo
