Skip to content

[BUG]: create a new release (v2.0.0) #749

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

Open
ghost opened this issue Mar 6, 2025 · 2 comments
Open

[BUG]: create a new release (v2.0.0) #749

ghost opened this issue Mar 6, 2025 · 2 comments
Labels
bug Something isn't working keep open Do NOT close automatically.

Comments

@ghost
Copy link

ghost commented Mar 6, 2025

Which version of the application are you using?

1.9.1-ce

Description of the bug

We need to be prepared to do it when it happens. Potential additions:

  • we can add a x86 package for macOS (if the release happens in the short term);
  • (temporarily?) change the false to true in macOS script to save dynamic libraries inside the tarball.

Everything is working fine (we recently tested it for 1.9.1).


[EDITED]

Do 32bits binaries

  • PPC: impossible to build; NO
  • Windows: extremely hard to build; NO
  • i386: I have to use Ubuntu 18LTS; YES [1]
  • armhf: it is becoming unnatural, but it is easy; YES [1]

[1] if the release happens in the short term:

Anyway, it works. Testing:

Version: 1.9.0-jumbo-1+bleeding-a7cbe621cd 2025-03-05 05:44:36 +0100
Build: linux-gnueabihf 32-bit armv7l NEON AC OMP
[...]

Testing: crypt, generic crypt(3) [?/32]... (8xOMP) PASS
All 430 formats passed self-tests
[...]

-------------------------------------------
###  Performed 15 tests in 563 seconds  ###
-------------------------------------------
----------------- armv7l ------------------
-------------------------------------------
Version: 1.9.0-jumbo-1+bleeding-a7cbe621cd 2025-03-05 05:44:36 +0100
Build: linux-gnu 32-bit i686 AVX2 AC OMP
[...]

Testing: crypt, generic crypt(3) [?/32]... (4xOMP) PASS
All 430 formats passed self-tests
[...]

-------------------------------------------
###  Performed 15 tests in 545 seconds  ###
-------------------------------------------
----------------- i686 --------------------
-------------------------------------------

The bleeding "release"

To be able to run the deployment tests [1] I will use the bleeding tag, so the release normally called bleeding will be removed (at least for a while)[2].

[1] new packages (from new sources) will be introduced;
[2] the documentation is clear that bleeding is NOT a real release, it's just a tool for use in testing.

@ghost ghost added the bug Something isn't working label Mar 6, 2025
@ghost ghost self-assigned this Mar 6, 2025
@ghost
Copy link
Author

ghost commented Mar 11, 2025

If the release happens in the short term, we can fulfill all the requests made in this issue.

Image

@github-actions github-actions bot added the O: stale Stale issue or PR label Apr 8, 2025
@ghost ghost added keep open Do NOT close automatically. and removed O: stale Stale issue or PR labels Apr 8, 2025
@ghost ghost deleted a comment from github-actions bot Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working keep open Do NOT close automatically.
Projects
None yet
Development

No branches or pull requests

0 participants