** Description changed: + [ Impact ] + + * The code in vim-addon-manager is ok with ruby3.0 as in Jammy. + But on the upgrade to Noble the ruby3.2 there will execute + some of the pre-removal and that hits an issue due to a + now removed method. + + * The fix for that is upstream (native package in Debian) + And was available [1]. + We instead could go into a solution based on ensuring upgrade + dependencies and ordering so that pre-rm would still run with + the old ruby. But that could cause circular dependencies, + would be way more complex to test and would still break + if people use new ruby versions from off-archive. + + [1]: https://salsa.debian.org/vim-team/vim-addon- + manager/-/commit/e4034fc5907c6af0f2e2e08baa85a015e7302447 + + [ Test Plan ] + + * There might be more complex ways to test, but I found the way I + encountered the issue the best to test - which is upgrading from + Jammy to Noble + * 1. get a clean Jammy system e.g. a LXD guest + * 2. install vim-addon-manager and an addon + $ apt install vim-addon-manager vim-airline + * 3. upgrade to Noble + $ do-release-upgrade + + [ Where problems could occur ] + + * Exist and Exists used to do the same since the deprecation in 2013. + What comes to mind is a ruby so old it does not know about the new yet. + But that isn't a real new issue as other code in vim-addon-manager + already uses the new "Exist" - so that would fail already. + + * Another source of issues might be if the change was wrong, but since + it is functionally equivalent it is essentially a search and replace + which isn't the most complex change. + + [ Other Info ] + + * This isn't new at all, the deprecation is of Ruby2.1 (2013) and + had to happen at some point. + + * In terms of severity this isn't the most evil bug that ever existed. + After all just re-running dist-upgrade does resolve it as the code in + noble is fine then. + But it breaks developers that use heavy mods in vim, which is a large + user group that we'd like to not break on upgrades. Furthermore any + "fall out of release upgrade" is a rather negative impact IMHO. + And finally the initial error message is a bit misleading (comes from + no pre-rm being there anymore, but the problem is as outlined old + code vs new language runtime). + + ---- + + 1 - Ubuntu Version Description: Ubuntu 22.04.4 LTS Release: 22.04 - 2 - Package name and version vim-pathogen: - Installed: 2.4-5 - Candidate: 2.4-5 - Version table: - *** 2.4-5 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu jammy/universe i386 Packages - 100 /var/lib/dpkg/status + Installed: 2.4-5 + Candidate: 2.4-5 + Version table: + *** 2.4-5 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu jammy/universe i386 Packages + 100 /var/lib/dpkg/status 3 & 4 - expectation and reality Upgrading 22.04 LTS to 24.04 LTS via do-release-upgrade, expecting an upgrade or left alone during the process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: vim-pathogen 2.4-5 ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Aug 30 21:52:28 2024 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2016-11-08 (2853 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - dpkg 1.22.6ubuntu6.1 - apt 2.7.14build2 + dpkg 1.22.6ubuntu6.1 + apt 2.7.14build2 SourcePackage: vim-pathogen Title: package vim-pathogen 2.4-5 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to noble on 2024-08-31 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078541 Title: package vim-pathogen 2.4-5 failed to install/upgrade: there is no script in the new version of the package - giving up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim-addon-manager/+bug/2078541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
