[00:33:23]
<Yunohost Git/Infra notifications> App flood failed all tests in job [#31098](https://ci-apps.yunohost.org/ci/job/31098) :(
[05:28:21]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 58 pending update PRs
- 9 new apps PRs
- 4 failed apps updates: flood, fluffychat, mobilizon, screego
See the full log here: http://paste.yunohost.org/raw/unebewizuv
[07:42:23]
<florent[m]> The CI seems to be stopped, is it a known problem?
https://ci-apps-dev.yunohost.org/ci/
[08:11:39]
<orhtej2> > The CI seems to be stopped, is it a known problem?
> https://ci-apps-dev.yunohost.org/ci/
at least bookworm is chugging along: https://ci-apps-bookworm-dev.yunohost.org/ci/
[08:28:33]
<florent[m]> Yep, but I need to check whether both the distribution work with my package…
[08:37:42]
<Salamandar> Yes, there are some instabilities on the CI. I restarted the server, should fix the issue until it starts breaking again…
[08:52:55]
<florent[m]> > <@Salamandar:matrix.org> Yes, there are some instabilities on the CI. I restarted the server, should fix the issue until it starts breaking again…
Thank you!
[09:01:50]
<Yunohost Git/Infra notifications> App searxng goes down from level 6 to 1 in job [#31117](https://ci-apps.yunohost.org/ci/job/31117)
[09:51:27]
<florent[m]> Hmm, I had to restart my job:
```
Error: error sending init packet to server: failed to send packet: write unix @->/proc/self/fd/25/forkfile.sock: write: broken pipe
Error: read unix @->/var/lib/incus/unix.socket: i/o timeout
Error: Failed to begin transaction: context deadline exceeded
Error: Only running operations can be connected
Error: read unix @->/var/lib/incus/unix.socket: i/o timeout
Error: read unix @->/var/lib/incus/unix.socket: i/o timeout
```
[09:51:53]
<florent[m]> (For the record, not necessarily for an immediate action)
[09:57:27]
<orhtej2> the most immersion breaking thing is bookworm CI now pretty much always goes with `Test it, book it, worm it, technologic.`, skipping other responses. 1/10, would not test again
[10:32:01]
<florent[m]> Erf, new failures with the CI now… :/
[10:33:26]
<florent[m]> Sounds like a restart would be welcome (sorry for the inconvenience)
[11:24:52]
<eric_G> > the most immersion breaking thing is bookworm CI now pretty much always goes with `Test it, book it, worm it, technologic.`, skipping other responses. 1/10, would not test again
`use it, break it, fix it, trash it, change it, upgrade it, technologic`
[11:24:56]
<m606> > <@titus:pijean.ovh> I think you need to contact Github support for either case
is that a joke ? 👹
[11:25:41]
<orhtej2> > <@ericg:matrix.org> `use it, break it, fix it, trash it, change it, upgrade it, technologic`
even flows with the beat 🎶
[11:25:51]
<eric_G> original lyrics almost nailed it
[11:27:17]
<orhtej2> ```
Write it, cut it, paste it, save it
Load it, check it, quick – rewrite it
```
yup :)
[11:28:36]
<Salamandar> Yeah idk why the CI keeps breaking. Its behaviour is really weird.
[11:37:22]
<orhtej2> CI be like https://www.youtube.com/watch?v=5FjWe31S_0g&rco=1
[11:43:53]
<Yunohost Git/Infra notifications> [apps] ericgaspar merged [pull request #2613](https://github.com/YunoHost/apps/pull/2613): Add OJS to catalog
[11:43:53]
<Yunohost Git/Infra notifications> [apps] ericgaspar deleted branch ojs
[11:43:54]
<Yunohost Git/Infra notifications> [apps] ericgaspar pushed 1 commit to master: Add OJS to catalog (#2613) * Update apps.toml * Create ojs.png ([bd94e151](https://github.com/YunoHost/apps/commit/bd94e151d305f3d2769ebbeb3bc567d65e707e23))
[11:44:31]
<Yunohost Git/Infra notifications> [apps] yunohost-bot pushed 1 commit to master: Automatically add dates to the catalog files ([7731fd39](https://github.com/YunoHost/apps/commit/7731fd39e106716037a7df064ace336666252d3c))
[12:20:51]
<m606> > <@m606:matrix.org> is that a joke ? 👹
I guess I'm gonna try that, hope it will not mess with the catalog and all - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork
[12:30:04]
<m606> > <@m606:matrix.org> I guess I'm gonna try that, hope it will not mess with the catalog and all - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork
it seems it worked!
[13:03:24]
<tituspijean> @orhtej2:circledsquareroot.ovh whaaaat but I put like two other sentences in there :(
[13:03:43]
<tituspijean> and it's always putting this one? Damn dudes, we broke probabilities.
[13:05:57]
<tituspijean> @m606:matrix.orgIt was not a joke, that's what I did to remove some fork links for the YunoHost-Apps org (they became like 600 commits ahead 😅 ). Today I learned about that method you linked to, nice!
[13:15:07]
<orhtej2> > <@titus:pijean.ovh> @orhtej2:circledsquareroot.ovh whaaaat but I put like two other sentences in there :(
it actually uses other messages as well, I just didn't notice
[13:17:47]
<m606> > <@titus:pijean.ovh> @m606:matrix.orgIt was not a joke, that's what I did to remove some fork links for the YunoHost-Apps org (they became like 600 commits ahead 😅 ). Today I learned about that method you linked to, nice!
oh ok i thought you may have been sarcastic 😉
the mirror trick seems to work well and you even keep the artificially inflated number of contributors!
[13:18:31]
<m606> only the repo settings are to be configurated again
[13:18:59]
<m606> (it keeps the link with your local repo)
[13:20:55]
<m606> oh and important thing (not in my case for a new app) you loose all the issues and PR conversations (not the PR commits though). Not sure whether there is a way to back them up.
[13:44:03]
<m606> Can a non-commercial license be subject to YNH package? https://github.com/AykutSarac/jsoncrack.com/tree/main?tab=License-1-ov-file#readme
[13:45:07]
<m606> I mean "free non-commercial use only" license
[14:17:32]
<Yunohost Git/Infra notifications> App umami rises from level 1 to 8 in job [#31120](https://ci-apps.yunohost.org/ci/job/31120) !
[14:34:07]
<Yunohost Git/Infra notifications> [apps] zamentur created new branch add-nextcloud-signaling
[14:34:07]
<Yunohost Git/Infra notifications> [apps] zamentur pushed 1 commit to add-nextcloud-signaling: [add] Nextcloud Signaling ([934f2e27](https://github.com/YunoHost/apps/commit/934f2e27d66057d721d6a0917a7c1f31e666c578))
[14:34:35]
<Yunohost Git/Infra notifications> [apps] github-actions[bot] created new branch actions/toml
[14:34:35]
<Yunohost Git/Infra notifications> [apps] github-actions[bot] pushed 1 commit to actions/toml: :art: Format TOML with Taplo ([b3ff8608](https://github.com/YunoHost/apps/commit/b3ff8608eb2ddcb21266f308b8a52529f4f4cecc))
[14:34:36]
<Yunohost Git/Infra notifications> [apps] github-actions[bot] opened [pull request #2616](https://github.com/YunoHost/apps/pull/2616): Format TOML with Taplo
[14:34:44]
<Yunohost Git/Infra notifications> [apps] zamentur opened [pull request #2617](https://github.com/YunoHost/apps/pull/2617): [add] Nextcloud Signaling
[14:34:56]
<m606> And other question: when apps offer the choice of database backend - which one is to favor (PostgresSQL, SQLIte3, MariaDB) ? Is there any YNH preference order about that ?
[14:35:15]
<Yunohost Git/Infra notifications> [apps] OniriCorpe approved [pull request #2616](https://github.com/YunoHost/apps/pull/2616#pullrequestreview-2354707561) Format TOML with Taplo
[14:35:22]
<Yunohost Git/Infra notifications> [apps] OniriCorpe merged [pull request #2616](https://github.com/YunoHost/apps/pull/2616): Format TOML with Taplo
[14:35:26]
<Yunohost Git/Infra notifications> [apps] OniriCorpe pushed 1 commit to add-nextcloud-signaling: :art: Format TOML with Taplo ([553f356e](https://github.com/YunoHost/apps/commit/553f356e7493eac3db06c87a41891f7cbf41ea63))
[14:35:35]
<Yunohost Git/Infra notifications> [apps] OniriCorpe deleted branch actions/toml
[14:36:00]
<Émy - OniriCorpe> > <@m606:matrix.org> Can a non-commercial license be subject to YNH package? https://github.com/AykutSarac/jsoncrack.com/tree/main?tab=License-1-ov-file#readme
Yes
[14:36:44]
<Émy - OniriCorpe> Just use the `not-totally-free-upstream` anti feature
[14:38:10]
<Émy - OniriCorpe> > <@m606:matrix.org> And other question: when apps offer the choice of database backend - which one is to favor (PostgresSQL, SQLIte3, MariaDB) ? Is there any YNH preference order about that ?
AFAIK postgre should be the way
[14:45:41]
<Yunohost Git/Infra notifications> [apps] ericgaspar approved [pull request #2617](https://github.com/YunoHost/apps/pull/2617#pullrequestreview-2354737229) [add] Nextcloud Signaling
[14:45:49]
<Yunohost Git/Infra notifications> [apps] ericgaspar pushed 1 commit to master: [add] Nextcloud Signaling (#2617) * [add] Nextcloud Signaling * :art: Format TOML with Taplo --------- Co-authored-b... ([579c1a31](https://github.com/YunoHost/apps/commit/579c1a315f53d29842157dd255720ee3165054cc))
[14:45:50]
<Yunohost Git/Infra notifications> [apps] ericgaspar deleted branch add-nextcloud-signaling
[14:45:50]
<Yunohost Git/Infra notifications> [apps] ericgaspar merged [pull request #2617](https://github.com/YunoHost/apps/pull/2617): [add] Nextcloud Signaling
[14:46:13]
<Yunohost Git/Infra notifications> [apps] yunohost-bot pushed 1 commit to master: Automatically add dates to the catalog files ([b29ad1bd](https://github.com/YunoHost/apps/commit/b29ad1bd1caa33a009c4b8ce95408f0986733019))
[15:02:25]
<m606> > <@oniricorpe:im.emelyne.eu> Yes
https://yunohost.org/en/packaging_manifest
> license (str) : the license code of the upstream project. (Note that only apps based on free software will be accepted in the official YunoHost app catalog.). The license code should be a valid SPDX identified.
1. so it can be hosted by Yunhost-Apps but not put in the catalog, or will it enter it with the antifeature you mentioned ?
2. How to deal with SPDX with such "JSON CRACK license" https://github.com/AykutSarac/jsoncrack.com?tab=License-1-ov-file#readme
[15:04:47]
<Émy - OniriCorpe> > <@m606:matrix.org> https://yunohost.org/en/packaging_manifest
> > license (str) : the license code of the upstream project. (Note that only apps based on free software will be accepted in the official YunoHost app catalog.). The license code should be a valid SPDX identified.
>
> 1. so it can be hosted by Yunhost-Apps but not put in the catalog, or will it enter it with the antifeature you mentioned ?
> 2. How to deal with SPDX with such "JSON CRACK license" https://github.com/AykutSarac/jsoncrack.com?tab=License-1-ov-file#readme
Ah yes, it’s a known issue: https://github.com/YunoHost/issues/issues/2348
[15:06:57]
<Aleks (he/him/il/lui)> > <@m606:matrix.org> And other question: when apps offer the choice of database backend - which one is to favor (PostgresSQL, SQLIte3, MariaDB) ? Is there any YNH preference order about that ?
The preference is that people shouldnt really have to choose this because Yunohost is about simple one-click~ish installs with sane defaults. Actually if tomorrow we were to rewrite Yunohost from scratch, i would be in favor or uniformizing every possible apps to just use postgresql because fuck mysql and its tendency to self corrupt
[15:08:32]
<Aleks (he/him/il/lui)> (And also to further reduce the complexity i.e. database = postgres, period ... But then ofc some apps are like 'urr durr we dont support postgres' but that sounds like a red flag idk)
[15:09:26]
<m606> > <@oniricorpe:im.emelyne.eu> Ah yes, it’s a known issue: https://github.com/YunoHost/issues/issues/2348
thanks so it would be something like `LicenseRef-json-crack-license`
[15:09:27]
<Aleks (he/him/il/lui)> (Ah and then there's mongodb etc)
[15:19:05]
<m606> > <@Alekswag:matrix.org> (And also to further reduce the complexity i.e. database = postgres, period ... But then ofc some apps are like 'urr durr we dont support postgres' but that sounds like a red flag idk)
I can't personnally measure the technical differences' impact so far, but I just know [MariaDB got purchased last month by a Private Equity firm](https://www.theregister.com/2024/09/10/maria_db_buyout/) so that may bring uncertainty for FOSS projects based on it.
As for YNH, I understand from Emy & Aleks interventions we should favor Postgres unless not possible, which sounds reasonnable to me.
[15:21:13]
<m606> about technical differences - for instance those guys say SQLite3 is easier to launch/maintain (but I believe they talk in a Dockerization perspective): https://docs.pwpush.com/docs/installation/#storage-backends
[15:24:07]
<m606> > <@m606:matrix.org> thanks so it would be something like `LicenseRef-json-crack-license`
Should I add upsteam License file in the YNH repo?
[15:40:24]
<m606> > <@m606:matrix.org> Should I add upsteam License file in the YNH repo?
from https://reuse.software/spec-3.2/ as quoted in https://github.com/YunoHost/issues/issues/2348:
> Each License File MUST be placed in the LICENSES/ directory in the root of the Project. The name of the License File MUST be the SPDX License Identifier of the license followed by an appropriate file extension (example: LICENSES/GPL-3.0-or-later.txt). The License File MUST be in plain text format.
[15:47:06]
<Émy - OniriCorpe> > <@m606:matrix.org> about technical differences - for instance those guys say SQLite3 is easier to launch/maintain (but I believe they talk in a Dockerization perspective): https://docs.pwpush.com/docs/installation/#storage-backends
SQLite is easier, indeed, but YunoHost is doing all the tedious work, so… don’t care x)
[15:47:30]
<Émy - OniriCorpe> > <@m606:matrix.org> Should I add upsteam License file in the YNH repo?
Add your package license, not the upstream license
[15:55:11]
<m606> so nothing about upstream license apart from the manifest.toml even though it is not a well-known one, right ?
[15:55:21]
<m606> so nothing about upstream license apart from the manifest.toml and even though it is not a well-known one, right ?
[15:55:44]
<Émy - OniriCorpe> > <@m606:matrix.org> so nothing about upstream license apart from the manifest.toml and even though it is not a well-known one, right ?
Yup
[15:56:48]
<Émy - OniriCorpe> The package license is not related to the upstream license, so put your chosen license in the package repo, the upstream license code in the manifest and that’s all folx
[16:09:00]
<m606> I read in the 2.1 helpers doc that ynh_nodejs_install should be preceded by a global indicated Node JS version (I need Node >=18.x).
If I leave it as in this example what should I expect? https://github.com/YunoHost-Apps/audiobookshelf_ynh/blob/master/scripts/install#L11C1-L11C19
[16:12:51]
<m606> > <@m606:matrix.org> I read in the 2.1 helpers doc that ynh_nodejs_install should be preceded by a global indicated Node JS version (I need Node >=18.x).
> If I leave it as in this example what should I expect? https://github.com/YunoHost-Apps/audiobookshelf_ynh/blob/master/scripts/install#L11C1-L11C19
got it, in this is example $nodejs_version was defined in _common.sh
[16:17:32]
<m606> however I wonder in the case the YNH instance already has a Node version installed (say 22) - if I set `nodejs_version=18.1`, it will install 18.1 even though it would have been fine for my app to use upper version already installed ?
[16:18:19]
<Émy - OniriCorpe> > <@m606:matrix.org> however I wonder in the case the YNH instance already has a Node version installed (say 22) - if I set `nodejs_version=18.1`, it will install 18.1 even though it would have been fine for my app to use upper version already installed ?
Each package can install its node version
[16:20:01]
<m606> And there ain't no mechanism so far that can tell - "Ok you need anything from 18 and above, and as the system already has 22 installed, let's not install 18 but make you use 22 instead" ?
[16:20:11]
<Émy - OniriCorpe> Besides, this can be an issue, as it can use up a lot of hdd space and it’s not automatically purged by the system
[16:20:46]
<m606> yes that is my point on avoiding installing unecessary packages
[16:21:04]
<Aleks (he/him/il/lui)> > <@m606:matrix.org> And there ain't no mechanism so far that can tell - "Ok you need anything from 18 and above, and as the system already has 22 installed, let's not install 18 but make you use 22 instead" ?
i doubt node guarantees forward-compatibility or whatever it's called, otherwise we would just be installing the latest version and voila ?
[16:22:08]
<m606> > <@Alekswag:matrix.org> i doubt node guarantees forward-compatibility or whatever it's called, otherwise we would just be installing the latest version and voila ?
Ah this I don't know, I was just blindly believing upstream prerequisite stating : `Node.js (Version: >=18.x)`
[16:22:10]
<Aleks (he/him/il/lui)> (same thing as for PHP)
[16:22:25]
<Aleks (he/him/il/lui)> hmmm
[16:22:33]
<eric_G> and some apps are picky on the version used -> dodoc : node 20.17.0
[16:22:41]
<Aleks (he/him/il/lui)> yeah i doubt the upstream can guarantee that their code will work with any future version of node
[16:23:01]
<m606> so in my case I would just use node 18.1, right ?
[16:23:10]
<Aleks (he/him/il/lui)> just specify "18" and it will pick the latest 18.x
[16:23:35]
<m606> ok thanks
[18:39:40]
<Yunohost Git/Infra notifications> [apps] yunohost-bot pushed 1 commit to master: Automatically add dates to the catalog files ([b29ad1bd](https://github.com/YunoHost/apps/commit/b29ad1bd1caa33a009c4b8ce95408f0986733019))