RPM Support

One can upload and import an erratum to an RPM repository with a call like the following:

POST /pulp/api/v2/repositories/my_repo_id/actions/import_upload/ HTTP/1.1
Host pulp.example.com
Content-Type: application/json; charset=UTF-8
[…]

{
    "unit_key": {"id": "my_erratum_id"},
    "unit_metadata": {
        "id": "my_erratum_id",
        "description": "Dummy advisory for testing purposes\n",
        "from": "nobody@redhat.com",
        "issued": "2014-09-24 00:00:00",
        "pkglist": [
            {
                "name": "RHSA-2014:1293",
                "packages": [
                    {
                        "arch": "noarch",
                        "epoch": "0",
                        "filename": "bear-4.1-1.noarch.rpm",
                        "name": "bear",
                        "release": "1",
                        "src": "bear-4.1-1.src.rpm",
                        "sum": [
                            "md5",
                            "37b48f6bbd1df40511f429e7fa16902a"
                        ],
                        "version": "4.1" 
                    }
                ],
                "short": "" 
            }
        ],
        "pushcount": "1",
        "reboot_suggested": false,
        "references": [
            {
                "href": "https://rhn.redhat.com/errata/RHSA-9999-0001.html",
                "id": null,
                "title": "RHSA-9999:0001",
                "type": "self" 
            }
        ],
        "release": "0",
        "rights": "Copyright 2014 Red Hat Inc",
        "severity": "Critical",
        "solution": "Eat sleep rave repeat\n",
        "status": "final",
        "summary": "This advisory solves nothing\n",
        "title": "Dummy advisory 1",
        "type": "security",
        "updated": "2014-09-24 00:00:00",
        "version": "1" 
    },
    "unit_type_id": "erratum",
    "upload_id": "my_upload_id" 
}

Pulp ignores the outermost release field. (The one with a value of "0".) When the repository containing the erratum is subsequently published, the generated updateinfo.xml field has no release field.