Your message dated Sun, 05 Feb 2023 17:24:53 +0300
with message-id <5575541.VhMoeNhUju@barberry>
and subject line Re: vim-ultisnips: I could not do "vam remove -w ultisnips"
has caused the Debian Bug report #982166,
regarding vim-ultisnips: I could not do "vam remove -w ultisnips"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
982166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982166
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vim-ultisnips
Version: 3.1-3.1
Severity: important
Dear Maintainer,
As you might know issue, #810929, I also met same bug in this packge.
Then I got another trouble. I just remove vim-ultisnips temporary.
```
root@Odayla:/home/yabuki# vam remove -w ultisnips
Info: removing installed addon 'ultisnips' from /var/lib/vim/addons
Traceback (most recent call last):
11: from /usr/bin/vam:2:in `<main>'
10: from /usr/bin/vam:2:in `load'
9: from /usr/bin/vim-addon-manager:282:in `<top (required)>'
8: from /usr/lib/ruby/vendor_ruby/vim/addon_manager.rb:54:in `remove'
7: from /usr/lib/ruby/vendor_ruby/vim/addon_manager.rb:54:in `each'
6: from /usr/lib/ruby/vendor_ruby/vim/addon_manager.rb:55:in `block in
remove'
5: from
/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/legacy.rb:88:in `remove'
4: from /usr/lib/ruby/2.7.0/set.rb:328:in `each'
3: from /usr/lib/ruby/2.7.0/set.rb:328:in `each_key'
2: from
/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/legacy.rb:88:in `block in
remove'
1: from
/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/legacy.rb:104:in `rmdirs'
/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/legacy.rb:104:in `delete': Is
a directory @ apply2files - /var/lib/vim/addons/pythonx/UltiSnips
(Errno::EISDIR)
```
then
```
vam status
# Name User Status System Status
airline installed removed
airline-themes installed installed
asciidoc installed removed
ctrlp removed removed
editexisting installed removed
fugitive installed removed
jinja installed removed
justify removed removed
latex-suite installed removed
matchit removed removed
powerline installed removed
snippets removed installed
ultisnips removed broken
```
I did not expect status turns broken.
FYI: UltiSnips directory is missing.
```
LANG=C ls -la /var/lib/vim/addons/pythonx/UltiSnips/
total 0
drwxr-xr-x 1 root root 60 Feb 7 14:11 .
drwxr-xr-x 1 root root 46 Dec 5 20:59 ..
drwxr-xr-x 1 root root 1912 Dec 14 19:09 __pycache__
drwxr-xr-x 1 root root 68 Feb 7 14:11 snippet
drwxr-xr-x 1 root root 22 Feb 7 14:11 text_objects
```
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vim-ultisnips depends on:
ii python3 3.9.1-1
ii python3-pynvim [vim-python3] 0.4.2-1
ii vim-addon-manager 0.5.10
ii vim-gtk3 [vim-python3] 2:8.2.2434-1
ii vim-nox [vim-python3] 2:8.2.2434-1
Versions of packages vim-ultisnips recommends:
ii vim-snippets 1.0.0-7
vim-ultisnips suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.2-1
Since the vim-ultisnips package does not provide a registry for the obsoleted
Vim addon manager, there can be no more errors with the vam utility. And I
think the bug may be considered as closed.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
