Spec URL: http://people.redhat.com/caolanm/mythes/mythes-pl.spec SRPM URL: http://people.redhat.com/caolanm/mythes/mythes-pl-1.4-1.fc9.src.rpm Description: Polish Thesaurus, splits out the mythes thesaurus from openoffice.org as an independently updateable package
Packaging looks Ok to me. rpmlint is silent. APPROVED.
New Package CVS Request ======================= Package Name: mythes-pl Short Description: Polish Thesaurus Owners: caolanm Branches: devel InitialCC: Cvsextras Commits: yes
cvs done.
built
------- Comment From sachinp.com 2010-07-20 04:36 EDT------- This problem can be recreated with snap7. /boot cannot be created on a lvm partition. ------- Comment From gmuelas.com 2010-07-27 10:02 EDT------- (In reply to comment #16) > These changes made by dcantrell. > Bugzilla comment added: > Using zipl_helper.device-mapper from the s390utils package, we can possibly > support /boot on LVM on s390 via anaconda. This is a feature request as we > have never done this in the past, so moving this to 6.1 for consideration. > > Bugzilla summary changed from 'Cannot mount /boot partition on LVM logical > group.' to 'RFE: Cannot mount /boot partition on LVM logical group.' > > Flag(s) 'devel_ack?, qa_ack?' added > > https://bugzilla.redhat.com/show_bug.cgi?id=618376 Hi David, till today I thought that s390 was the only arch. that had this restricted, but it seems that in other archs. was also restricted due to grub, correct? In any case, I do not think that it is necessary to do more checks that you do now (were there any checks till now to know at partitioner time if the zipl was going to be succesfull at the end, with something like zipl --dry-run ?), that is now that zipl support device mapper, it will support to have /boot on LVM, assuming that the installer allows it. That helper script is used by zipl, but the user and/or anaconda does not need to use it. As for the fix to allow /boot on LVM, you know much better anaconda code than I do, but maybe I would suggest looking under: platform.py def checkBootRequest(self, req): # can't have bootable partition on LV if req.type == "lvmlv": errors.append(_("Bootable partitions cannot be on a logical volume.")) and maybe add "and !s390" with proper sintax. Regarding RHEL 6.0 or 6.1 is your call to decide if you consider that too risky now or not, and if it does not go in to RHEL 6.0 we will request it for 6.1. Hope it helps, Gonzalo. ------- Comment From mgrf.com 2010-09-08 08:02 EDT------- Hello Red Hat, While a fix for this is in work for RHEL6.1, this issue should have a short entry in RHEL6 release notes Proposal for R6 release notes - until fix avail. with R6.1 ================== Cause The /boot partition cannot be created and mounted on an LVM logical volume. Result The Linux system cannot be booted or IPLed from an LVM logical volume. Workaround Create the /boot partition on a DASD or SCSI volume. Consequence n/a (same as result) ========================== ------- Comment From htengshe.com 2010-09-24 00:33 EDT------- (In reply to comment #28) > These changes made by rlerch. > Diffed Contents: > @@ -1,2 +1,2 @@ > -When setting up mount points during the RHEL 6 installation on System z, you > must use a non-LVM volume for /boot. The RHEL 6 installer currently does not > support having the /boot volume on a logical volume. If you need to have the > /boot volume on a logical volume, you can do so manually after the installation > on RHEL on System z. Please check zipl > +The installer currently does not support having the /boot volume on a logical > volume on the on System z architecture. Consequently, when setting up mount > points during installation, the /boot volume cannot be a LVM volume. Manual > configuration after installation is required if the /boot volume is to be on a > logical volume. Refer to the zipl > -documentation.+documentation for further information. > > https://bugzilla.redhat.com/show_bug.cgi?id=618376 +The installer currently does not support having the /boot volume on a logical volume on System z architecture. Consequently, when setting up mount points during installation, the /boot volume cannot be a LVM volume. Manual configuration after installation is required if the /boot volume is to be on a logical volume. Refer to the zipl -documentation.+documentation for further information. on the on System z architecture Please remove extra "on the" ------- Comment From htengshe.com 2011-02-22 02:26 EDT------- Checked on RHEL6.1 early build. The problem is still not fixed.
Created attachment 488517 [details] /boot Not listed in Mount point Dropdown
Created attachment 488518 [details] Anaconda Log Rhel6.0 beta2
Created attachment 488519 [details] anaconda-tb-SYNGeBEtXfQc.xml