You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
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:
Everything is working fine (we recently tested it for 1.9.1).
Do 32bits binaries
[1] if the release happens in the short term:
Anyway, it works. Testing:
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.The text was updated successfully, but these errors were encountered: