-
Notifications
You must be signed in to change notification settings - Fork 3
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
Corrupt source for /var/cache/yunohost/download/listmonk/app.tar.gz #19
Comments
I have no clue why this is happening. @ericgaspar can you look into this? #10 |
Should be fixed on testing |
J'ai essayé de la re-installer et erreur! |
ah! at list the shasum is correct. @navanchauhan if you don't mind following this up from here |
Perfect. Looks like an error in the app installation, something that I can actually fix now |
@JacquelinDV this seems to be a memory issue, can you tell what hardware you are running this on? Use this format please: Context
|
Context:
- Hardware: *Raspberry Pi 3B at home *
- YunoHost version: 11.1. 7
- Are you in a special context or did you perform some particular
tweaking on your YunoHost instance?: *no *
Le jeu. 16 févr. 2023, 22:52, Navan Chauhan ***@***.***> a
écrit :
… @JacquelinDV <https://github.com/JacquelinDV> this seems to be a memory
issue, can you tell what hardware you are running this on? Use this format
please:
Context
- Hardware: *VPS bought online / Old laptop or computer / Raspberry Pi
at home / Internet Cube with VPN / Other ARM board / ...*
- YunoHost version: x.x.x
- Are you in a special context or did you perform some particular
tweaking on your YunoHost instance?: *no / yes*
- If yes, please explain:
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMJETMOBDDX2TQERGIMV3D3WX2OTNANCNFSM6AAAAAAUPN34GY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Looks like it’s running out of memory, let me try adding an option to increase swap space in the install script Best,NavanOn Feb 17, 2023, at 1:15 PM, JacquelinDV ***@***.***> wrote:
Context:
- Hardware: *Raspberry Pi 3B at home *
- YunoHost version: 11.1. 7
- Are you in a special context or did you perform some particular
tweaking on your YunoHost instance?: *no *
Le jeu. 16 févr. 2023, 22:52, Navan Chauhan ***@***.***> a
écrit :
@JacquelinDV <https://github.com/JacquelinDV> this seems to be a memory
issue, can you tell what hardware you are running this on? Use this format
please:
Context
- Hardware: *VPS bought online / Old laptop or computer / Raspberry Pi
at home / Internet Cube with VPN / Other ARM board / ...*
- YunoHost version: x.x.x
- Are you in a special context or did you perform some particular
tweaking on your YunoHost instance?: *no / yes*
- If yes, please explain:
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMJETMOBDDX2TQERGIMV3D3WX2OTNANCNFSM6AAAAAAUPN34GY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
We definitely should rely (once available) to a ARM binary build upstream |
Definitely. Building from source is really resource intensive
…On Fri, 17 Feb 2023 at 13:53, Éric Gaspar ***@***.***> wrote:
We definitely should rely (once available
<knadh/listmonk#544>) to a ARM binary build
upstream
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7BHQGW256O323E7HMQPBLWX7QN3ANCNFSM6AAAAAAUPN34GY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Bonjour, |
I just don't think your Pi is powerful enough to compile Listmonk. I will try and move the builds for Listmonk to a CI so you don't have to compile it, or directly contribute upstream to get builds available. |
As soon as my PR gets accepted upstream, it will solve this issue |
should be fixed in master |
I have re-try to install FileMonk after a period to permit a cache update with a 11.1.5 yunohost system on a pi 3B+ ssd and the result is always the same (see the (https://paste.yunohost.org/raw/bulocarihu)) log file) with the following explanation :
2023-02-02 20:21:35,979: DEBUG - ++ wget --tries 3 --no-dns-cache --timeout 900 --no-verbose --output-document=/var/cache/yunohost/download/listmonk/app.tar.gz https://github.com/knadh/listmonk/archive/refs/tags/v2.2.0.tar.gz
2023-02-02 20:21:37,266: DEBUG - + out='2023-02-02 20:21:37 URL:https://codeload.github.com/knadh/listmonk/tar.gz/refs/tags/v2.2.0 [1717969] -> "/var/cache/yunohost/download/listmonk/app.tar.gz" [1]'
2023-02-02 20:21:37,271: DEBUG - + sha256sum --check --status
2023-02-02 20:21:37,312: DEBUG - ++ sha256sum /var/cache/yunohost/download/listmonk/app.tar.gz
2023-02-02 20:21:37,314: DEBUG - ++ cut '--delimiter= ' --fields=1
2023-02-02 20:21:37,352: DEBUG - ++ du -hs /var/cache/yunohost/download/listmonk/app.tar.gz
2023-02-02 20:21:37,354: DEBUG - ++ cut '--delimiter= ' --fields=1
2023-02-02 20:21:37,377: DEBUG - + ynh_die '--message=Corrupt source for /var/cache/yunohost/download/listmonk/app.tar.gz: Expected e3f1cc89972cafaab78cda38be54ab3fc115fd7846e2e7dae1b19fff002e1c77 but got 6eef831f7ceef80624ae69cd7020504344410d0f8015a0e150b88d324894ca8d (size: 1,7M /var/cache/yunohost/download/listmonk/app.tar.gz).'
2023-02-02 20:21:37,460: DEBUG - + ynh_exit_properly
2023-02-02 20:21:37,468: WARNING - Corrupt source for /var/cache/yunohost/download/listmonk/app.tar.gz: Expected e3f1cc89972cafaab78cda38be54ab3fc115fd7846e2e7dae1b19fff002e1c77 but got 6eef831f7ceef80624ae69cd7020504344410d0f8015a0e150b88d324894ca8d (size: 1,7M /var/cache/yunohost/download/listmonk/app.tar.gz).
2023-02-02 20:21:38,001: DEBUG - + ynh_clean_setup
2023-02-02 20:21:38,004: DEBUG - + true
2023-02-02 20:21:39,015: ERROR - Impossible d'installer listmonk : Une erreur est survenue dans le script d'installation de l'application
it seems due to a bad version loaded (2.2.0 et non 2.3.0)!
The text was updated successfully, but these errors were encountered: