package libc6-armel-cross 2.27-3ubuntu1cross1 failed to install/upgrade: unable to install new version of '/usr/arm-linux-gnueabihf/libsf/ld-2.27.so': No such file or directory

Bug #1802391 reported by Juan Pablo Pérez Lantes
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cross-toolchain-base (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

El error ocurre luego de reinciar la notebook

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc6-armel-cross 2.27-3ubuntu1cross1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Mon Nov 5 17:23:38 2018
Dependencies:

DuplicateSignature:
 package:libc6-armel-cross:2.27-3ubuntu1cross1
 Unpacking libc6-dev-armel-cross (2.27-3ubuntu1cross1.1) over (2.27-3ubuntu1cross1) ...
 dpkg: error processing archive /tmp/apt-dpkg-install-fRnMD9/260-libc6-dev-armel-cross_2.27-3ubuntu1cross1.1_all.deb (--unpack):
  unable to install new version of '/usr/arm-linux-gnueabihf/libsf/Mcrt1.o': No such file or directory
ErrorMessage: unable to install new version of '/usr/arm-linux-gnueabihf/libsf/ld-2.27.so': No such file or directory
InstallationDate: Installed on 2018-03-29 (224 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.6
SourcePackage: cross-toolchain-base
Title: package libc6-armel-cross 2.27-3ubuntu1cross1 failed to install/upgrade: unable to install new version of '/usr/arm-linux-gnueabihf/libsf/ld-2.27.so': No such file or directory
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Juan Pablo Pérez Lantes (jplantes) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cross-toolchain-base (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.