Jump to content

Recommended Posts

Posted

I've been upgrading to the latest nightly mainline kernel every couple of weeks or so and had a problem today whilst updating linux-xenial-root-next-cubox-i

 

dpkg output throws an error :

 

root@JPCuboxi4:/boot# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-xenial-root-next-cubox-i
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/332 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 177105 files and directories currently installed.)
Preparing to unpack .../linux-xenial-root-next-cubox-i_5.32.170728_armhf.deb ...
Leaving 'diversion of /etc/mpv/mpv.conf to /etc/mpv/mpv-dist.conf by linux-xenial-root-next-cubox-i'
Unpacking linux-xenial-root-next-cubox-i (5.32.170728) over (5.32.170716) ...
dpkg: error processing archive /var/cache/apt/archives/linux-xenial-root-next-cubox-i_5.32.170728_armhf.deb (--unpack):
 trying to overwrite '/usr/bin/brcm_patchram_plus', which is also in package armbian-tools-xenial 5.27.170301
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: Generating /boot/initrd.img-4.12.3-cubox
update-initramfs: Converting to u-boot format
Errors were encountered while processing:
 /var/cache/apt/archives/linux-xenial-root-next-cubox-i_5.32.170728_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

This happens on both my cubox-i's. I tried to move brcm_patchram_plus but it still throws out the error. Any ideas ?!

Posted

Nightly builds are automated - for developers and testing - and sometimes things go wrong. Try updating once again in approximately 6 hours from now.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines