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

in last release where is drawio-x86_64-24.2.5.deb #1708

Closed
2 tasks done
lorens-osman-dev opened this issue Apr 29, 2024 · 3 comments
Closed
2 tasks done

in last release where is drawio-x86_64-24.2.5.deb #1708

lorens-osman-dev opened this issue Apr 29, 2024 · 3 comments
Assignees
Labels
blocked/upstream Blocked on upstream dependency

Comments

@lorens-osman-dev
Copy link

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
in release page there is no drawio-x86_64-24.2.5.deb package there is only arm64 ones but i tested the drawio-amd64-24.2.5.deb with size 91.7 MB and worked will on my machine i think there is a wrong naming there.

Describe the solution you'd like
just rename [drawio-amd64-24.2.5.deb 91.7MB ] to [drawio-x86_64-24.2.5.deb]

@m-mohamedin m-mohamedin added the blocked/upstream Blocked on upstream dependency label May 4, 2024
@m-mohamedin
Copy link
Contributor

@m-mohamedin
Copy link
Contributor

Hi,

When was the last time the file named x86_64. I've check our releases up to 2017 and all are named amd64

We got this reply from electron builder team:
"What version was this previously working on? I can try git diff-ing when time allows me to return to this project"

@lorens-osman-dev
Copy link
Author

Upon further reflection, I realized that I confused the terms arm64 and amd64 in my request. I mistakenly suggested renaming the drawio-amd64-24.2.5.deb package to drawio-x86_64-24.2.5.deb, not recognizing at the time that both terms refer to the same architecture and that the naming was indeed correct.

I understand that maintaining a project on GitHub involves dealing with a myriad of details and that clarity in communication is paramount. My intention was to contribute positively to the project, and I regret any confusion my error may have caused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/upstream Blocked on upstream dependency
Projects
None yet
Development

No branches or pull requests

2 participants