This is found by Wendy Vath when she did the RE build for s10u5_06. The following complains were found for SUNWj3rt:
I found this new message in our build logs on Saturday:
SPARC build log:
----------------
WARNING:
PKG=SUNWj3rt
ARCH=sparc
VERSION=1.3.1,REV=2001.05.06.07.06
Excessive number of deleted files: 104
WARNING: many deleted files found in the pkghistory.
x86 build log:
--------------
WARNING:
PKG=SUNWj3rt
ARCH=i386
VERSION=1.3.1,REV=2001.05.06.04.21
Excessive number of deleted files: 103
WARNING: many deleted files found in the pkghistory.
According to the /net/benet/benet/Packaging/pkg_history.txt, ph files should be provided to resolve the upgrade performance problem:
Large numbers of files (say, over 50) have been removed
from the file. If a large number of the files in the
package have become obsolete, it is better to remove the
entire package than to individually remove the obsolete
files. A PKGRM=yes entry should be supplied. If the
.pkghistory generation program discovers that 100 or more
files have been removed from the package and that a .ph
entry with PKGRM=yes for the package has NOT been supplied,
a warning will be printed during the generation of the
file. If this happens, Release Engineering will contact
the consolidation that delivered the package to determine
whether a .ph entry should have been supplied.
I found this new message in our build logs on Saturday:
SPARC build log:
----------------
WARNING:
PKG=SUNWj3rt
ARCH=sparc
VERSION=1.3.1,REV=2001.05.06.07.06
Excessive number of deleted files: 104
WARNING: many deleted files found in the pkghistory.
x86 build log:
--------------
WARNING:
PKG=SUNWj3rt
ARCH=i386
VERSION=1.3.1,REV=2001.05.06.04.21
Excessive number of deleted files: 103
WARNING: many deleted files found in the pkghistory.
According to the /net/benet/benet/Packaging/pkg_history.txt, ph files should be provided to resolve the upgrade performance problem:
Large numbers of files (say, over 50) have been removed
from the file. If a large number of the files in the
package have become obsolete, it is better to remove the
entire package than to individually remove the obsolete
files. A PKGRM=yes entry should be supplied. If the
.pkghistory generation program discovers that 100 or more
files have been removed from the package and that a .ph
entry with PKGRM=yes for the package has NOT been supplied,
a warning will be printed during the generation of the
file. If this happens, Release Engineering will contact
the consolidation that delivered the package to determine
whether a .ph entry should have been supplied.