Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement correct architecture naming convention #91

Closed
Tracked by #110
AlexRuiz7 opened this issue Dec 26, 2023 · 0 comments · Fixed by #112
Closed
Tracked by #110

Implement correct architecture naming convention #91

AlexRuiz7 opened this issue Dec 26, 2023 · 0 comments · Fixed by #112
Assignees
Labels
level/task Task issue type/enhancement Enhancement issue

Comments

@AlexRuiz7
Copy link
Member

Description

The wazuh-indexer packages follow the naming convention defined in https://github.com/wazuh/internal-devel-requests/issues/187:

<SubsystemName>_<VersionNumber>-<Revision>_{<OSName>-<OSVersion>_}<Architecture>_<GitReference>.<PackageType>

As architecture, the expected values are:

  • RPM: x86_64, aarch64
  • DEB: amd64, arm64

Currently, the packages use x64 or amd64 as architecture identifier, independently of the distribution.

We need to update the package generation process to use the right values depending on the architecture and distribution.

@AlexRuiz7 AlexRuiz7 added level/task Task issue type/enhancement Enhancement issue labels Dec 26, 2023
@wazuhci wazuhci moved this to Backlog in Release 4.9.0 Dec 26, 2023
@f-galland f-galland self-assigned this Jan 5, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 4.9.0 Jan 5, 2024
@f-galland f-galland linked a pull request Jan 9, 2024 that will close this issue
7 tasks
@wazuhci wazuhci moved this from In progress to Pending review in Release 4.9.0 Jan 10, 2024
@wazuhci wazuhci moved this from Pending review to In review in Release 4.9.0 Jan 10, 2024
@wazuhci wazuhci moved this from In review to Done in Release 4.9.0 Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/enhancement Enhancement issue
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants