|
|
发表于 2008-10-30 00:23:47
|
显示全部楼层
Post by MadGoat;1901167
Since losing wget support is the problem, emerge --fetchonly the new packages,
and *then* unmerge ss and com_err. Since the packages are already present, no
wget will be attempted.
After ss, com_err, and the old e2fsprogs are unmerged use --nodeps to emerge
just e2fsprogs-libs and the new e2fsprogs specifically. Otherwise, ss and
com_err will try to come back in as deps. e2fsprogs needs to be removed to deal
with the package collisions that would otherwise occur.
All of these changes should be done specifically to these packages in one short
session, and not as part of a larger "world" update. e2fsprogs supplies
libraries that, if absent, will prevent a large number of programs from
working, and will probably prevent reliable emerges of other packages.
Here are the steps:
1. emerge -NuDav --fetchonly world
2. emerge -C ss com_err e2fsprogs
3. emerge -NuDav --nodeps e2fsprogs-libs e2fsprogs
4. echo "sys-libs/com_err" >>/etc/portage/package.mask
5. echo "sys-libs/ss" >>/etc/portage/package.mask
6. echo "sys-libs/com_err-1.40.11" >>/etc/portage/profile/package.provided
7. echo "sys-libs/ss-1.40.11" >>/etc/portage/profile/package.provided
The last two are to prevent other packages such as app-crypt/mit-krb5 which
have runtime dependencies directly on com_err or ss.
Running revdep-rebuild afterward did not find any packages in need of updates.
此即我意,真详细呀! |
|