We can check the code:
root@j:~# grep File.exist /usr/lib/ruby/vendor_ruby/vim/addon_manager.rb
if File.exists? tagfile
if File.exist? override_file
FileUtils.rm override_file if File.exist? override_file
As suggested by the error, "exists" is likely wrong and "exist" is good.
This has been deprecated for ages and now finally removed:
- https://bugs.ruby-lang.org/issues/17391
There is a fix in newer releases already.
-
https://salsa.debian.org/vim-team/vim-addon-manager/-/commit/e4034fc5907c6af0f2e2e08baa85a015e7302447
That was done for newer Ruby3.2, but the way this works on upgrades
means that we might execute the old code with the new Ruby.
Instead of going for complex pkg ordering changes we could just apply
the same change to Jammy so that upgraders do not hit that making them
fall out of do-release-upgrade.
** Package changed: vim-pathogen (Ubuntu) => vim-addon-manager (Ubuntu)
** Also affects: vim-addon-manager (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: vim-addon-manager (Ubuntu Jammy)
Status: New => Triaged
** Changed in: vim-addon-manager (Ubuntu)
Status: Confirmed => Fix Released
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs