** Also affects: dpkg (Debian)
Importance: Undecided
Status: New
** Also affects: linux-base (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
and for linux-base
i moved /usr/bin/linux-update-symlinks to /usr/bin/linux-base-update-symlinks
and put
#! /bin/bash
set -e
BOOT_FS=$(df -P -h -T "/boot" | awk 'END{print $2}')
if [[ $BOOT_FS == vfat ]]
then
echo 'vfat does not support symlinks...'
echo 'doing nothing'
exit 0
else
This problem has 2 parts linux base and dpkg
for dpkg this patch fixes it
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-base (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "fix-boot-backup.patch"
Verified this is still happening installing linux-
image-5.15.0-56-generic_5.15.0-56.62_amd64. /etc/kernel-img.conf
workaround still does not work and computer is placed in the grub
command line after reboot.
--
You received this bug notification because you are a member of Kernel
Packages,
I just ran into this on a 18.04 LTS to 20.04 LTS upgrade
Note that I was actually able to use the /etc/kernel-img.conf workaround
with two properties:
do_symlinks = No
no_symlinks = Yes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This still happens with a 18.04 LTS to 20.04 LTS upgrade!
It's really surprising that a years old bug affecting a long term
support version is not yet handled or assigned. Needing to install from
scratch instead of having the LTS upgrade work means lost time and
significant loss of trust. Note,
Any news here?
After I dumped grub in order to use systemd-boot, I would like to mount
my EFI partition (FAT32) on /boot directly but continue to update my
kernels using apt.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Ubuntu 16.04
Unpacking linux-image-4.4.0-22-generic (4.4.0-22.40) over (4.4.0-22.39) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-image-4.4.0-22-generic_4.4.0-22.40_amd64.deb
(--unpack):
unable to make backup link of './boot/System.map-4.4.0-22-generic' before
installing
the same with linux-image-4.4.0-22-generic
I'm happy with efi boot and I don't need grub.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318951
Title:
kernel update fails with /boot on
Could this be a duplicate of #559127?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318951
Title:
kernel update fails with /boot on FAT32
Status in linux package in Ubuntu:
@wensveen I don't think so. I'm pretty sure that the other bug isn't
caused by a filesystem that doesn't support links
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318951
Title:
I had the same issue with kernel 3.13.0-40.69.
I could successfully update the kernel by editing the configuration file
/etc/kernel-img.conf as follows:
do_symlinks = no
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- kernel update to 3.13.0-24.47 fails
+ kernel update fails with /boot on FAT32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318951
Title:
kernel update fails
Am I understanding it correctly that the package script is trying to
create a symlink ( I am not that familiar with how Debian packages work,
so I haven't looked at it myself )? If this is the case, wouldn't it be
possible to fix this bug by not creating links on filesystems that don't
support
14 matches
Mail list logo
