# 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:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [October 11, 2019, 9:15am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/1 "2019-10-11T09:15:00Z")

</div>

Creating new issue as the previous issue([RPM names do not match their contents](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents/193782)) was closed.

Do we have any update on this?

Best Regards,  
Akshat

---

<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: [October 11, 2019, 3:13pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/2 "2019-10-11T15:13:38Z")

</div>

Hello, thanks for the follow up. I've asked for an update on the internal discussion this morning. While this current issue impacts your workflow, there are some valid concerns that the potential for breaking something for a larger audience is high. I'll let you know as I get further updates.

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [November 4, 2019, 11:40am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/3 "2019-11-04T11:40:09Z")

</div>

Hello @Michael_Madden,

Please let me know if there was any further discussion on this.

Best Regards,  
Akshat

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [December 2, 2019, 7:00am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/4 "2019-12-02T07:00:55Z")

</div>

Hi,

Any update on this?

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [December 13, 2019, 12:03pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/5 "2019-12-13T12:03:31Z")

</div>

@Michael_Madden

Do we have any update on this?

Best Regards,  
Akshat

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [December 16, 2019, 6:21am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/6 "2019-12-16T06:21:43Z")

</div>

@jordansissel @Michael_Madden

Will this issue be fixed anytime soon? Is there any plan for this enhancement?

Best Regards,  
Akshat

---

<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 16, 2019, 2:36pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/7 "2019-12-16T14:36:18Z")

</div>

Hi Akshat, thanks for the reaching out. The internal discussion for this topic was never 100% resolved. I'll reach out again internally, and see if we can draw a conclusion.

I believe my earlier comment is still valid, but I'll double check.

> There are some valid concerns that the potential for breaking something for a larger audience is high.

Thanks.  
Michael

---

<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.

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [January 8, 2020, 5:57am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/9 "2020-01-08T05:57:03Z")

</div>

Thanks for your response.

> [@Michael\_Madden](#):
>
> the risk associated with breaking things for a larger audience outweighs any reward from an update.

Since we are also asked to change the RPM names for all elastic stack components by our customers, we would like to know what might be the potential risk involved in changing the RPM names?

Best Regards,  
Akshat

---

<div class="post-metadata">

### Author: ![akshatsharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshatsharma/32/84179_2.png) [@akshatsharma](https://discuss.elastic.co/u/akshatsharma)
#### Post date: [January 17, 2020, 6:10am UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/10 "2020-01-17T06:10:51Z")

</div>

@Michael_Madden could you please let us know about the risks that might be involved with this change? We'll have to plan our work based on it.

Best Regards,  
Akshat

---

<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: [January 18, 2020, 4:30pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/11 "2020-01-18T16:30:04Z")

</div>

Hello,

Thanks for reaching out. Our concerns revolve around how small, subtle changes often cause bigger issues. Here's an example where a small change in packaging Elasticsearch caused bigger issues.

> <https://github.com/elastic/elasticsearch/issues/49599>
>
> Hi,
> Your current download of elasticsearch-6.8.5.tar.gz with the shasum of a66773585c2195e22114922534f65069d669c774 has been generated in such a way that makes it incompatible...

Our packages are working internally and externally for the vast majority of our customers who use rpm, yum, dnf, apt, etc. There's a significant risk involved with introducing a change that would potentially address an issue for a small audience while likely creating new issues for a broader audience.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 15, 2020, 4:30pm UTC](https://discuss.elastic.co/t/rpm-names-do-not-match-their-contents-recreating-issue/203195/12 "2020-02-15T16:30:04Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
