[Bug 1069062] Re: [dist-upgrade] Dangerous package "flash-kernel", manually removed, was automatically reinstalled by upgrade to Q

Forgács Gábor slylessystem at gmail.com
Thu Oct 24 06:55:07 UTC 2013


The package flash-kernel is a package which causes the flash partition
/dev/mmcblk0 to be unconditionally overwritten each time you install a
new kernel or module.  I have a multiboot setup with Android and Ubuntu
on my AC100, and load the kernel from a SD-card using Multiboot
installed in the rescue partition.  So I don't want my /dev/mmcblk0
overwritten (that would break my multiboot setup), I just want the
kernels to be put in /boot as usual (where Multiboot will find them).
Thus, I have uninstalled this package, which has had the desired effect
of not destroying my boot partition all the time.

However, when upgrading to quantal, dist-upgrade sneakily chose to
reverse my decision and reinstall this landmine of a package behind my
back (see also bug#1069059).  If I hadn't discovered it in time, it
would probably had destroyed my boot partition further down the upgrade
process.  As it were, I was unable to just uninstall it (the dpkg
database was locked by the upgrade in progress), so I took the
precaution of deleting the device node /dev/mmcblk0 instead...

Please respect my wishes to not have my partitions overwritten, and
don't automatically install packages which unconditonally do so.

Thanks.

** Changed in: update-manager (Ubuntu)
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/update-manager/+question/237945

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1069062

Title:
  [dist-upgrade] Dangerous package "flash-kernel", manually removed, was
  automatically reinstalled by upgrade to Q

Status in “update-manager” package in Ubuntu:
  Invalid

Bug description:
  The package flash-kernel is a package which causes the flash partition
  /dev/mmcblk0 to be unconditionally overwritten each time you install a
  new kernel or module.  I have a multiboot setup with Android and
  Ubuntu on my AC100, and load the kernel from a SD-card using Multiboot
  installed in the rescue partition.  So I don't want my /dev/mmcblk0
  overwritten (that would break my multiboot setup), I just want the
  kernels to be put in /boot as usual (where Multiboot will find them).
  Thus, I have uninstalled this package, which has had the desired
  effect of not destroying my boot partition all the time.

  However, when upgrading to quantal, dist-upgrade sneakily chose to
  reverse my decision and reinstall this landmine of a package behind my
  back (see also bug#1069059).  If I hadn't discovered it in time, it
  would probably had destroyed my boot partition further down the
  upgrade process.  As it were, I was unable to just uninstall it (the
  dpkg database was locked by the upgrade in progress), so I took the
  precaution of deleting the device node /dev/mmcblk0 instead...

  Please respect my wishes to not have my partitions overwritten, and
  don't automatically install packages which unconditonally do so.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1069062/+subscriptions



More information about the foundations-bugs mailing list