Dave and Alan:
I also manage to reproduce this with the sparc AI iso that RE
generates. I can provide access to the t4-2 if someone want to take a
look and root cause this further.
I did run the text-install in -d mode and hopefully can gather more info.
On 06/12/12 02:24 PM, Dave Miner wrote:
On 06/12/12 17:06, Alan Steinberg wrote:
On 06/12/12 11:58 AM, Dave Miner wrote:
On 06/12/12 14:28, Alan Steinberg wrote:
We just hit a bug where an obsolete package is still listed in the
system group packages. This causes the text install to fail, but
the AI
install apparently just skips it and doesn't report any issues. Is the
method by which the text install uses the group packages different
than
how AI uses them? Does AI do a check for a package's state?
-- Alan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
Interactive installs are always copying the contents of the booted
image; AI installs are installing packages directly. This means that
interactive installs have to uninstall media-specific content so that
the installed system doesn't try to act like an install image. That
should just be removing the packages system/install/media/internal and
system/install/text-install in this case.
Dave
I understand that the text install from media will install the packages
found in the ISO image, and a text install from the network would
install from the repository. Both of these fail due to the obsolete
package. The AI install succeeds, though. This is why I am thinking that
the text install and the AI create the list of installation packages
differently. AI must be detecting an obsolete package and removes it
from the list, while the text installer doesn't do this check, and
therefore fails to install the obsolete package. I'm looking for
validation on this thought, and whether one of these installation
methods should change to either fail at creation or fail at
installation.
No, a text install from network does not use a package repository at
all. It works the same as a text install from media, it just has a
different package set because the solaris-auto-install group is used,
rather than solaris-large-server.
I don't understand the root cause of the problem that's been observed
yet, honestly, but the package operation should be the same as what
happens on text installs from media.
Dave
-- Alan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss