# Renaming and repackaging beats
**URL:** https://discuss.elastic.co/t/renaming-and-repackaging-beats/223735
**Category:** Beats
**Created:** [March 16, 2020, 10:44am UTC](https://discuss.elastic.co/t/renaming-and-repackaging-beats/223735 "2020-03-16T10:44:25Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@stefws](https://discuss.elastic.co/u/stefws)
#### Post date: [March 16, 2020, 10:44am UTC](https://discuss.elastic.co/t/renaming-and-repackaging-beats/223735/1 "2020-03-16T10:44:26Z")
Am trying to repackaged renamed versions of eg. auditbeat and filebeat v.7.6.1 using the [FPM utility](https://fpm.readthedocs.io/en/latest/intro.html).
But I find that most properly rpmbuild adds in symlinks under /usr/lib/.build-id to the binaries in such pacakges and since it seems that the hash ids from the beat wrappers /usr/share/\*beat/bin/\*beat-god are the same, this generates a conflict on the thus same build id symlinks 😕
Any ideas to avoid rpmbuild including the build ids or howto generate unique for each wrapper?
PS! The reason behind repacking is that we're a hosting shop and we need/desire to avoid clashing with std. elastic packages used by our Tenants with our infrastructural usage for elastic beats, thus we'll like to be able to have multihomed beats installed on the same server.
---
### Author:  [@stefws](https://discuss.elastic.co/u/stefws)
#### Post date: [March 18, 2020, 9:38am UTC](https://discuss.elastic.co/t/renaming-and-repackaging-beats/223735/2 "2020-03-18T09:38:00Z")
adding these options to fpm did the trick:
```
--rpm-tag '%define _build_id_links none'
--rpm-tag '%undefine _missing_build_ids_terminate_build'
```
thanks to info found [here](https://gnu.wildebeest.org/blog/mjw/2017/06/30/fedora-rpm-debuginfo-improvements-for-rawhidef27/)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 15, 2020, 11:38am UTC](https://discuss.elastic.co/t/renaming-and-repackaging-beats/223735/3 "2020-04-15T11:38:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.