To avoid any confusion and further questions, I'm marking the noble task
as Won't fix.
The error comes from the preinst of the base-files version being
installed, not the one already on the system. Noble's base-files preinst
(13ubuntu10 to 13ubuntu10.5) has no dangling-symlink check, so noble's
own base-files updates can never fail this way.
The failures reported here happen when a noble system is upgraded to a
newer release whose preinst has the check. The original report is noble
-> plucky, and plucky is now EOL.
The fix therefore goes into the releases noble users upgrade to, which
currently are resolute and stonking (SRUs) and tenacious (devel)
** Also affects: base-files (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: base-files (Ubuntu Noble)
Status: New => Won't Fix
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131303
Title:
package base-files 13ubuntu10.2 failed to install/upgrade: new base-
files package pre-installation script subprocess returned error exit
status 1: /lib32 is a dangling symbolic link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2131303/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
