Debian Package Tracker
Register | Log in
Subscribe

vim

Vi IMproved - enhanced vi editor

Choose email to subscribe with

general
  • source: vim (main)
  • version: 2:9.0.0135-1
  • maintainer: Debian Vim Maintainers (DMD)
  • uploaders: James McCoy [DMD]
  • arch: all any
  • std-ver: 4.6.0
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2:8.0.0197-4+deb9u3
  • o-o-sec: 2:8.0.0197-4+deb9u7
  • oldstable: 2:8.1.0875-5
  • stable: 2:8.2.2434-3+deb11u1
  • testing: 2:9.0.0135-1
  • unstable: 2:9.0.0135-1
versioned links
  • 2:8.0.0197-4+deb9u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:8.0.0197-4+deb9u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:8.1.0875-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:8.2.2434-3+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:9.0.0135-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • vim (40 bugs: 0, 20, 20, 0)
  • vim-athena (1 bugs: 0, 1, 0, 0)
  • vim-common (6 bugs: 0, 2, 4, 0)
  • vim-doc (1 bugs: 0, 0, 1, 0)
  • vim-gtk3 (3 bugs: 0, 1, 2, 0)
  • vim-gui-common
  • vim-motif
  • vim-nox (4 bugs: 0, 3, 1, 0)
  • vim-runtime (34 bugs: 0, 17, 17, 0)
  • vim-tiny (1 bugs: 0, 1, 0, 0)
  • xxd
action needed
A new upstream version is available: 9.0.0194 high
A new upstream version 9.0.0194 is available, you should consider packaging it.
Created: 2022-08-04 Last update: 2022-08-14 04:34
64 security issues in buster high

There are 64 open security issues in buster.

10 important issues:
  • CVE-2022-2124: Buffer Over-read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2125: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2126: Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2129: Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2207: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2288: Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.
  • CVE-2022-2522: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0060.
  • CVE-2022-2571: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0101.
  • CVE-2022-2580: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0102.
  • CVE-2022-2598: Undefined Behavior for Input to API in GitHub repository vim/vim prior to 9.0.0100.
54 issues postponed or untriaged:
  • CVE-2021-3872: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3903: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3927: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3928: (needs triaging) vim is vulnerable to Use of Uninitialized Variable
  • CVE-2021-3968: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3973: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3974: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-3984: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-4019: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-4069: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4166: (needs triaging) vim is vulnerable to Out-of-bounds Read
  • CVE-2021-4192: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4193: (needs triaging) vim is vulnerable to Out-of-bounds Read
  • CVE-2022-0156: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2022-0158: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2022-0213: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2022-0261: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0318: (needs triaging) Heap-based Buffer Overflow in vim/vim prior to 8.2.
  • CVE-2022-0319: (needs triaging) Out-of-bounds Read in vim/vim prior to 8.2.
  • CVE-2022-0351: (needs triaging) Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0359: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0361: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0368: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0392: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim prior to 8.2.
  • CVE-2022-0393: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0407: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0408: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0413: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0417: (needs triaging) Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0443: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0554: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0572: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0629: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0685: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418.
  • CVE-2022-0696: (needs triaging) NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4428.
  • CVE-2022-0714: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436.
  • CVE-2022-0729: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440.
  • CVE-2022-0943: (needs triaging) Heap-based Buffer Overflow occurs in vim in GitHub repository vim/vim prior to 8.2.4563.
  • CVE-2022-1154: (needs triaging) Use after free in utf_ptr2char in GitHub repository vim/vim prior to 8.2.4646.
  • CVE-2022-1381: (needs triaging) global heap buffer overflow in skip_range in GitHub repository vim/vim prior to 8.2.4763. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1420: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774.
  • CVE-2022-1616: (needs triaging) Use after free in append_command in GitHub repository vim/vim prior to 8.2.4895. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1619: (needs triaging) Heap-based Buffer Overflow in function cmdline_erase_chars in GitHub repository vim/vim prior to 8.2.4899. This vulnerabilities are capable of crashing software, modify memory, and possible remote execution
  • CVE-2022-1621: (needs triaging) Heap buffer overflow in vim_strncpy find_word in GitHub repository vim/vim prior to 8.2.4919. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1720: (needs triaging) Buffer Over-read in function grab_file_name in GitHub repository vim/vim prior to 8.2.4956. This vulnerability is capable of crashing the software, memory modification, and possible remote execution.
  • CVE-2022-1785: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.4977.
  • CVE-2022-1851: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1897: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1898: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1942: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1968: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2000: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2285: (needs triaging) Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0.
  • CVE-2022-2304: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.
Created: 2022-07-04 Last update: 2022-08-06 09:01
67 security issues in bullseye high

There are 67 open security issues in bullseye.

10 important issues:
  • CVE-2022-2124: Buffer Over-read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2125: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2126: Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2129: Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2207: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2288: Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.
  • CVE-2022-2522: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0060.
  • CVE-2022-2571: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0101.
  • CVE-2022-2580: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0102.
  • CVE-2022-2598: Undefined Behavior for Input to API in GitHub repository vim/vim prior to 9.0.0100.
57 issues left for the package maintainer to handle:
  • CVE-2021-3872: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3903: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3927: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3928: (needs triaging) vim is vulnerable to Use of Uninitialized Variable
  • CVE-2021-3968: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3973: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-3974: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-3984: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-4019: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-4069: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4136: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2021-4166: (needs triaging) vim is vulnerable to Out-of-bounds Read
  • CVE-2021-4173: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4187: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4192: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2021-4193: (needs triaging) vim is vulnerable to Out-of-bounds Read
  • CVE-2022-0156: (needs triaging) vim is vulnerable to Use After Free
  • CVE-2022-0158: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2022-0213: (needs triaging) vim is vulnerable to Heap-based Buffer Overflow
  • CVE-2022-0261: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0318: (needs triaging) Heap-based Buffer Overflow in vim/vim prior to 8.2.
  • CVE-2022-0319: (needs triaging) Out-of-bounds Read in vim/vim prior to 8.2.
  • CVE-2022-0351: (needs triaging) Access of Memory Location Before Start of Buffer in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0359: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0361: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0368: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0392: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim prior to 8.2.
  • CVE-2022-0393: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0407: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0408: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0413: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0417: (needs triaging) Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0443: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0554: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0572: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0629: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-0685: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4418.
  • CVE-2022-0696: (needs triaging) NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4428.
  • CVE-2022-0714: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436.
  • CVE-2022-0729: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440.
  • CVE-2022-0943: (needs triaging) Heap-based Buffer Overflow occurs in vim in GitHub repository vim/vim prior to 8.2.4563.
  • CVE-2022-1154: (needs triaging) Use after free in utf_ptr2char in GitHub repository vim/vim prior to 8.2.4646.
  • CVE-2022-1381: (needs triaging) global heap buffer overflow in skip_range in GitHub repository vim/vim prior to 8.2.4763. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1420: (needs triaging) Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774.
  • CVE-2022-1616: (needs triaging) Use after free in append_command in GitHub repository vim/vim prior to 8.2.4895. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1619: (needs triaging) Heap-based Buffer Overflow in function cmdline_erase_chars in GitHub repository vim/vim prior to 8.2.4899. This vulnerabilities are capable of crashing software, modify memory, and possible remote execution
  • CVE-2022-1621: (needs triaging) Heap buffer overflow in vim_strncpy find_word in GitHub repository vim/vim prior to 8.2.4919. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution
  • CVE-2022-1720: (needs triaging) Buffer Over-read in function grab_file_name in GitHub repository vim/vim prior to 8.2.4956. This vulnerability is capable of crashing the software, memory modification, and possible remote execution.
  • CVE-2022-1785: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.4977.
  • CVE-2022-1851: (needs triaging) Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1897: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1898: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1942: (needs triaging) Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-1968: (needs triaging) Use After Free in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2000: (needs triaging) Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
  • CVE-2022-2285: (needs triaging) Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0.
  • CVE-2022-2304: (needs triaging) Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.

You can find information about how to handle these issues in the security team's documentation.

Created: 2022-07-04 Last update: 2022-08-06 09:01
15 bugs tagged patch in the BTS normal
The BTS contains patches fixing 15 bugs, consider including or untagging them.
Created: 2022-07-27 Last update: 2022-08-14 05:04
Fails to build during reproducibility testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2020-10-30 Last update: 2022-08-14 00:32
version in VCS is newer than in repository, is it time to upload? normal
vcswatch reports that this package seems to have a new changelog entry (version 2:9.0.0135-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:
commit 8ea90f0d4371a562888b8373f7940856c3dfef8b
Author: James McCoy <jamessan@debian.org>
Date:   Mon Aug 8 20:15:02 2022 -0400

    Add Recommends: xxd to vim-common
    
    This better reflects what would be provided by an upstream install, but
    allows users to remove it if they don't need it.
    
    Signed-off-by: James McCoy <jamessan@debian.org>

commit 9171291eac12ec9edd3071d3fd0ec706b246395a
Author: James McCoy <jamessan@debian.org>
Date:   Mon Aug 8 20:05:48 2022 -0400

    Start new changelog
    
    Signed-off-by: James McCoy <jamessan@debian.org>
Created: 2022-08-09 Last update: 2022-08-09 02:33
lintian reports 95 warnings normal
Lintian reports 95 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2022-01-01 Last update: 2022-07-30 12:17
AppStream hints: 2 warnings normal
AppStream found metadata issues for packages:
  • vim-common: 1 warning
  • vim-gui-common: 1 warning
You should get rid of them to provide more metadata about this software.
Created: 2020-06-01 Last update: 2020-06-01 01:13
Build log checks report 1 warning low
Build log checks report 1 warning
Created: 2022-02-19 Last update: 2022-04-29 21:34
Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2020-02-26 10:50
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.1 instead of 4.6.0).
Created: 2022-05-11 Last update: 2022-08-04 08:36
testing migrations
  • This package will soon be part of the auto-perl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
news
[rss feed]
  • [2022-08-06] vim 2:9.0.0135-1 MIGRATED to testing (Debian testing watch)
  • [2022-08-03] Accepted vim 2:9.0.0135-1 (source) into unstable (James McCoy)
  • [2022-06-20] Accepted vim 2:8.0.0197-4+deb9u7 (source) into oldoldstable (Markus Koschany)
  • [2022-05-16] Accepted vim 2:8.0.0197-4+deb9u6 (source) into oldoldstable (Markus Koschany)
  • [2022-04-23] vim 2:8.2.4793-1 MIGRATED to testing (Debian testing watch)
  • [2022-04-21] Accepted vim 2:8.2.4793-1 (source) into unstable (James McCoy)
  • [2022-04-04] Accepted vim 2:8.2.4659-1 (all amd64 source) into unstable, unstable (Debian FTP Masters) (signed by: James McCoy)
  • [2022-03-19] Accepted vim 2:8.1.0875-5+deb10u2 (source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Debian FTP Masters) (signed by: James McCoy)
  • [2022-03-11] Accepted vim 2:8.0.0197-4+deb9u5 (source) into oldoldstable (Markus Koschany)
  • [2022-01-10] Accepted vim 2:8.0.0197-4+deb9u4 (source) into oldoldstable (Anton Gladky)
  • [2022-01-06] vim 2:8.2.3995-1 MIGRATED to testing (Debian testing watch)
  • [2022-01-03] Accepted vim 2:8.2.3995-1 (source) into unstable (James McCoy)
  • [2021-12-24] Accepted vim 2:8.1.0875-5+deb10u1 (source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Debian FTP Masters) (signed by: James McCoy)
  • [2021-12-05] Accepted vim 2:8.2.2434-3+deb11u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: James McCoy)
  • [2021-11-02] vim 2:8.2.3565-1 MIGRATED to testing (Debian testing watch)
  • [2021-10-30] Accepted vim 2:8.2.3565-1 (source) into unstable (James McCoy)
  • [2021-10-06] vim 2:8.2.3455-2 MIGRATED to testing (Debian testing watch)
  • [2021-10-03] Accepted vim 2:8.2.3455-2 (source) into unstable (James McCoy)
  • [2021-09-30] Accepted vim 2:8.2.3455-1 (source) into unstable (James McCoy)
  • [2021-03-12] vim 2:8.2.2434-3 MIGRATED to testing (Debian testing watch)
  • [2021-03-12] vim 2:8.2.2434-3 MIGRATED to testing (Debian testing watch)
  • [2021-03-02] Accepted vim 2:8.2.2434-3 (source) into unstable (James McCoy)
  • [2021-02-20] Accepted vim 2:8.2.2434-2 (source) into unstable (James McCoy)
  • [2021-02-02] vim 2:8.2.2434-1 MIGRATED to testing (Debian testing watch)
  • [2021-01-31] Accepted vim 2:8.2.2434-1 (source) into unstable (James McCoy)
  • [2021-01-20] vim 2:8.2.2367-1 MIGRATED to testing (Debian testing watch)
  • [2021-01-20] vim 2:8.2.2367-1 MIGRATED to testing (Debian testing watch)
  • [2021-01-17] Accepted vim 2:8.2.2367-1 (source) into unstable (James McCoy)
  • [2021-01-15] Accepted vim 2:8.2.2344-2 (source) into unstable (James McCoy)
  • [2020-10-30] vim 2:8.2.1913-1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 106 107
  • RC: 0
  • I&N: 55
  • M&W: 49
  • F&P: 2 3
  • patch: 15
links
  • homepage
  • lintian (0, 95)
  • buildd: logs, checks, clang, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • l10n (-, 99)
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2:8.2.5166-0ubuntu1
  • 187 bugs (6 patches)
  • patches for 2:8.2.5166-0ubuntu1

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing