vim (2:8.2.4793-1) unstable; urgency=medium
* Merge upstream patch v8.2.4793
-- James McCoy <[email protected]> Wed, 20 Apr 2022 20:23:54 -0400
vim (2:8.2.4659-1) unstable; urgency=medium
* Merge upstream patch v8.2.4659
+ 8.2.4151: reading beyond end of a line (Closes: #1004859, CVE-2022-0318)
+ autoload/phpcomplete.vim: Fix E565 error in omni-completion (Closes:
#1008710)
* Remove outdated NEWS and README.Debian entries
* README.Debian: Fix links to vim-policy
* Improve docs about purpose and effect of defaults.vim (Closes: #856273)
* Define system (g)vimrc location as /etc/vim/(g)vimrc, rather than
symlinking from /usr/share/vim/(g)vimrc -> /etc/vim/(g)vimrc.
* Replace vim-athena with vim-motif, Athena GUI deprecated upstream
* Remove lintian override for rgb.txt, removed upstream
* Declare compliance with Policy 4.6.0, no changes needed
* Remove vim-gtk transitional package
-- James McCoy <[email protected]> Sun, 03 Apr 2022 10:44:13 -0400
vim (2:8.2.3995-1) unstable; urgency=medium
* Merge upstream patch v8.2.3918
+ 8.2.3610: crash when ModeChanged triggered too early (Closes: #1001900,
CVE-2021-3968)
+ 8.2.3611: crash when using CTRL-W f without finding a file name (Closes:
#1001899, CVE-2021-3973)
+ 8.2.3612: using freed memory with regexp using a mark (Closes: #1001897,
CVE-2021-3974)
+ 8.2.3625: illegal memory access when C-indenting (Closes: #1001896,
CVE-2021-3984)
+ 8.2.3847: illegal memory access when using a lambda with an error
(Closes: #1002534, CVE-2021-4136)
+ autoload/zip.vim: Use URI syntax for pseudo-filename to avoid empty
buffer after 8.2.3468 (Closes: #1000767)
* Revert "Disable Test_very_large_count since it fails on 32-bit systems",
fixed upstream
-- James McCoy <[email protected]> Mon, 03 Jan 2022 17:57:10 -0500
同样对于tar:
tar (1.34+dfsg-1) unstable; urgency=medium
* New upstream version
-- Janos Lenart <[email protected]> Wed, 17 Feb 2021 09:55:26 +0000
tar (1.33+dfsg-1) unstable; urgency=medium
* New upstream version
* Removed unsafe escaping from mailcap-entry; closes: #982614
* Fixed trailing whitespaces in debian/{changelog,control,rules}
-- Janos Lenart <[email protected]> Fri, 12 Feb 2021 15:15:21 +0000
tar (1.32+dfsg-1) unstable; urgency=medium
* New upstream version; closes: #892273
* Huge thanks to Bdale for maintaining tar since 1995; closes: #973844
-- Janos Lenart <[email protected]> Fri, 20 Nov 2020 09:52:51 +0000
这实际上与 UNIX/Linux 无关,而与一般的软件更新有关!
xxd
实际上是来自 vim 工具的程序,所以很可能两者固有的东西已经更新vim
不是那么稳定——它是一个中型到大型的代码库,并且总是有需要修复的错误。人们想要功能,人们想要vim
在 Ubuntu 22.10 上工作,因此需要做很多工作。如果您查看 vim 的 git 历史,您会发现平均每天有超过 5 次更改使其成为 vim 的源代码。所以,是的:会有更新。我不是特别了解频繁,这有点主观......但即使一个工具的功能范围相当固定,也可能存在错误,即使没有更严格意义上的错误,也可能有错别字手册页和类似的东西。
vim
是一个相当大的、灵活的和可扩展的软件,正在积极开发中,因此功能和错误修复更新都会发生。tar
…嗯,至少,它偶尔会支持新的压缩格式,这需要新的命令行开关。而且,文件系统在文件元数据方面变得如此复杂,以至于有可能出现意外行为或功能请求。(我隐约记得多年前,几乎所有工具都产生了-Z
处理 SELinux 标签之类的选项。)你在看哪个分布?如果它是一个依赖于 Debian 软件包的发行版
unstable
,您可能会将每个小错误修复、功能添加和其他调整作为单独的更新。正如其他人提到的,
vim
两者xxd
都来自同一个源代码包。vim
因此,这里是Debian 不稳定源代码包更改日志中的三个最新条目:同样对于
tar
:您可以很容易地找到 Debian 的特定软件包变更日志:转到
https://packages.debian.org/unstable/<package name>
,您将获得软件包详细信息页面。然后转到右侧边栏并从那里选择“Debian Changelog”。如果您为
xxd
软件包执行此操作,您将xxd
照常看到软件包详细信息,但该页面上的“Debian 变更日志”链接将自动将您定向到vim
源代码包的变更日志,因为这是用于构建两者的源代码xxd
和vim
二进制包。