在 2020/10/21 上午2:54, Holger Wansing 写道:
Hi,
xiao sheng wen (肖盛文) <atzli...@sina.com> wrote:
在 2020/10/19 下午10:57, Holger Wansing 写道:
We should better remove the whole content about those packages, right?
It's a easy way to fix this bug.
It is of no use for Debian users anyway, if they no longer can install the
corresponding packages.
In stable, the Debian user can install some packages come from oldstable.
In oldstable, the Debian user also can install some packages come from
stable.
Of course, as an experienced user/developer you can do everything.
But that is not the scope of this document.
As one reference manual book, keep more info is valued.
For example:
One experienced user can know the way of that install old package from
oldstable,
but he perhaps didn't know the package ldm.
The knowledge about Debian is very wide scope.
The oldstable still has many Debian user use it.
There are package has the state like: in oldstable, not in stable, not
in testing.
But perhaps some day, this package can into testing again.
Is this package need to remove?
(If they still have the packages installed, let's say on an oldstable
system, then they should read the debian-reference for *oldstable*.)
The debian-reference is also publish on the www.debian.org, It's for all Debian
OS Release version(Debian 9,10,11, etc,.).
No, I think this is not correct.
In common.ent you find the definition, what is the current stable, or the
current testing.
That way, every version of the debian-reference has its target releases
(stable, testing), for what it matches.
common.ent is only record the current state of Debian releases.
Although the deb package of debian-reference is static in Debian stable
releases,
but debian-reference also has public to www.debian.org, the content can
dynamic update in need.
And the most people find the debian-reference in the website, It's the
major way.
IMO it makes it unnecessarily complicated, if you want to keep the content
valid for all Debian releases.
If things change, you would be forced to say "you find that in file xxxyyy,
if you are running Jessie, or in file abcdef, if you are running Buster.
And we are planning to change that again for Bullseye".
And there is no need for such logic: if you want to find how the situation
was for an old Debian release, you can always look in an old version of
the debian-reference. It's always there.
There is only one version of the debian-reference in d.o now.
If split it for different target releases (stable, testing) in d.o,
perhaps is a better way, I'm not sure.
In this bug, "NOT_FOUND" only find in pkgsize.ent,
It affect the package to display the pkgsize, the patch can fix it,
it's not very complicated.
Holger
--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x339240CB
