[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#974728: marked as done (vim-scripts: Document migration from vim-addon-manager handling to Vim's native "package" functionality)



Your message dated Sat, 27 Mar 2021 20:42:09 +0100
with message-id <c8b760ea-b535-41c0-1552-19e6ecd3a2aa@debian.org>
and subject line Re: Bug#974728: vim-scripts: Document migration from vim-addon-manager handling to Vim's native "package" functionality
has caused the Debian Bug report #974728,
regarding vim-scripts: Document migration from vim-addon-manager handling to Vim's native "package" functionality
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 owner@bugs.debian.org
immediately.)


-- 
974728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974728
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: wishlist
X-Debbugs-Cc: carnil@debian.org,jamessan@debian.org

Hi

The recent update of vim-scripts to unstable (and to be released with
bullseye) contains the following NEWS file:

----cut---------cut---------cut---------cut---------cut---------cut-----
vim-scripts (20201113) unstable; urgency=low

  The addons provided by this package are now managed by Vim's native
  "package" functionality rather than vim-addon-manager.  Please follow these
  steps to ensure a smooth upgrade:

  * Before upgrading, run "vam remove <addon>" for any addon in this package
    that has been installed with "vam install <addon>".  Adjust the command
    as necessary for system-wide installed addon.
  * After upgrading, add "packadd! <addon>" to your vimrc for any addon that
    you want to use.  The addon name can be found in the package description
    or the list of directories under /usr/share/vim-scripts.

  Using VCSCommand as an example:
  * "vam remove vcscommand" will remove the vim-addon-manager setup for the
    addon.
  * Adding "packadd! VCSCommand" to your vimrc will enable (neo)vim to find
    and use the addon.

 -- James McCoy <jamessan@debian.org>  Fri, 13 Nov 2020 22:48:17 -0500
----cut---------cut---------cut---------cut---------cut---------cut-----

Might it be worth of mentioning this in the release notes, so users
can prepare in advance to move this handling to vim's native package
functionality?

Regards,
Salvatore

--- End Message ---
--- Begin Message ---
Hi

On 27-03-2021 11:41, Justin B Rye wrote:
> Paul Gevers wrote:
>> I have prepared the attached change to the release notes, ready to push.
> 
> Only one niggle:
> 
>> +      The addons for <systemitem role="package">vim</systemitem>
>> +      historically provided by <systemitem
>> +      role="package">vim-scripts</systemitem> are now managed by Vim's
>> +      native <quote>package</quote> functionality rather than by
>> +      <literal>vim-addon-manager</literal>. Vim users should prepare
>           ^^^^^^^
> Since vim-addon-manager is in fact a (Debian) package, we could give
> it the appropriate markup.

Pushed.

> (Hurrah for sources.debian.org!)

Indeed.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---

Reply to: