[EPEL-devel] [EPEL] #26: EPEL should enforce erratum title length

EPEL epel-trac at fedorahosted.org
Fri Jan 2 19:00:28 UTC 2015


#26: EPEL should enforce erratum title length
-----------------------------+----------------------------
  Reporter:  stbenjam        |      Owner:  epel-wranglers
      Type:  defect          |     Status:  new
  Priority:  critical        |  Milestone:
 Component:  Policy problem  |    Version:
Resolution:                  |   Keywords:  errata
-----------------------------+----------------------------

Comment (by barnabycourt):

 Hi, perhaps I can shed some light from Pulp's perspective.  When we sync
 an errata from a repository (such as epel), we parse all the properties of
 the errata.  To facilitate searching we index the "id", "title",
 "version", "release", "type", "status", "updated", "issued", "severity",
 and "references" fields.  Since Pulp uses Mongo internally we have a hard
 limit on index keys of 1024 bytes
 (http://docs.mongodb.org/manual/reference/limits/).

 Most of the time erratum titles are along the lines of "NetworkManager bug
 fix and enhancement update".  This bug was opened because in a few cases
 we have found the entire package list used for the title, eg. <title
 >"trytond-account-1.8.0-3.el6,trytond-account-be-1.8.0-3.el6,trytond-
 account-de-skr03-1.8.0-3.el6,trytond-account-invoice-1.8.0-3.el6,trytond-
 account-invoice-history-1.8.0-3.el6,trytond-account-invoice-line-
 standalone-1.8.0-3.el6,trytond-account-product-1.8.0-3.el6,trytond-
 account-statement-1.8.0-3.el6,trytond-analytic-
 account-1.8.0-3.el6,...</title>

 As smooge said, this could ban an issue with a misunderstanding of
 terminology.  What is the intended purpose of the <title> element within a
 given <update>?

-- 
Ticket URL: <https://fedorahosted.org/epel/ticket/26#comment:12>
EPEL <https://fedoraproject.org/wiki/EPEL>
Extra Packages for Enterprise Linux


More information about the epel-devel mailing list