# RPM names do not match their contents - recreating issue

**URL:** https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195
**Category:** Beats
**Tags:** filebeat
**Created:** [October 11, 2019, 9:15am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195 "2019-10-11T09:15:00Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Michael\_Madden](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_madden/32/46640_2.png) [@Michael\_Madden](https://discuss.elastic.co/u/Michael_Madden)
#### Post date: [December 22, 2019, 10:25pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/8 "2019-12-22T22:25:22Z")

</div>

Thanks again for reaching out. Our internal discussion has been concluded, and we agree that the RPM names do deviate from the standard. However, the risk associated with breaking things for a larger audience outweighs any reward from an update.

1. The current RPM names work fine for rpm/yum/dnf installations.
2. A [workaround](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents/193782/8) has been provided.

Please let us know if you have any questions.

---

_[View the full topic](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195)._