Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 871450[details]
rhel7 comps patch
It's too late to make changes in source strings now (we may get more untranslated strings than we have now), but we should make the change in rhel-7.1.
My understanding is these strings are used as descriptions of the comps shown in e.g. the anaconda interface, or yum groupinfo.
These are actually sentence fragments and unless they're used to complete a sentence, or these changes are used to be consistent with some other existing use of periods ("."), they shouldn't get periods at the end.
I'd say opposite:
Descriptions are not sentence fragments, but whole sentences.
Some descriptions contain more sentences.
Also RPM %description(s) contain sentences and end with periods.
-> My preference is to use periods
Fedora comps are not consistent either:
* 97 descriptions with period
* 41 descriptions without
Yeah, the consistency issue makes this less clear. I'd say we should aim for consistency as much as possible, and the rules of good English will have to take a back seat in this case.
Comment 6Alexander Todorov
2014-10-31 10:36:20 UTC
As far as I can see all English descriptions in current comps.xml end with a period. Moving to VERIFIED.
# cat Server/x86_64/os/repodata/9546150dbf91698b58c42d7ee6fdbfa03019532e8509d810c65f23ac79511519-comps-Server.x86_64.xml | grep description | grep -v lang | grep -v "\.</description>"
<description/>
<description/>
#
There are two groups with empty description tags:
Anaconda Tools and Remote Desktop Clients
Let me know if you'd like me to open another bug for this issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2015-0524.html
Created attachment 871450 [details] rhel7 comps patch It's too late to make changes in source strings now (we may get more untranslated strings than we have now), but we should make the change in rhel-7.1.