------- Comment From [email protected] 2016-03-31 08:32 EDT------- Hi Dimitri,
(In reply to comment #6) > Both s390-dasd and s390-zfcp are priority standard, and thus are always > installed in d-i. Whether they are installed automatically or later through anna is not relevant to the root problem. > > I do not think that creating two virtual provides, This is required to be automatically triggered by disk-detect to solve the "virtual dependency". Apart from the package dependency, the installer uses this dependency to define required pre-reqs in the installation workflow. That means, disk-detect provides harddrive- detection to detect disks for partitioning. The virtual dependency for s390-dasd, s390-zfcp provides dasd and zfcp disk detection. If both provide harddrive-detection, one is actually sufficient to proceed the installation. In the worst case, a user can only configure DASDs, but not zfcp. > and changing hw-detect from arch:all -> arch:any is required. I had to change this to any because of some build errors caused by the s390x-specific dependencies. > > The only effective changes are bumping up the XB-Installer-Menu-Item level, > which has already been done in Ubuntu for s390-dasd, but not for s390-zfcp. I think that this influences just how they appear in the list of installer menu (apart from the waypoints of the base-installer). > > Let me fix s390-zfcp installer priority, and i believe that would then > resolve the whole lot, i.e. dasd/zfcp will be auto-discovered if any are > present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559193 Title: disk-detect/s390-dasd/s390-zfcp: Restructure installer and put DASD and FCP configuration into disk detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1559193/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
