[00:54:04]
<Yunohost Git/Infra notifications> App tiki goes down from level 8 to 3 in job [#18772](https://ci-apps.yunohost.org/ci/job/18772)
[01:57:57]
<Yunohost Git/Infra notifications> [apps] @alexAubin pushed 1 commit to update_app_levels: diaspora back to level 8, regression was a tmp network glitch ([e968b1c0](https://github.com/YunoHost/apps/commit/e968b1c01102f10351fab655a531614cad47c5e7))
[01:58:13]
<Yunohost Git/Infra notifications> [apps] @alexAubin edited [pull request #1738](https://github.com/YunoHost/apps/pull/1738): Update app levels according to CI results
[06:35:03]
<Yunohost Git/Infra notifications> [apps] @ericgaspar pushed 1 commit to update_app_levels: Update apps.toml ([a5b171e5](https://github.com/YunoHost/apps/commit/a5b171e5c624c7c27889813cae70a3b66453a8b4))
[06:35:03]
<Yunohost Git/Infra notifications> [apps] @ericgaspar edited [pull request #1738](https://github.com/YunoHost/apps/pull/1738): Update app levels according to CI results
[07:57:34]
<Tag> Can we specify the value for a boolean install question in the manifest.toml ?
I want true to be "true" and not 1. I know about the yes= and no= but it seems to be valid only for config_panel.toml ?
[08:15:20]
<Aleks (he/him/il/lui)> Uuugh
[08:16:05]
<Aleks (he/him/il/lui)> Because the intent is to write the boolean into the file ?
[08:18:23]
<Aleks (he/him/il/lui)> naively i would add in \_common.sh another var derived from the true/false boolean with an if/else
[08:26:48]
<Tag> > <@Alekswag:matrix.org> Because the intent is to write the boolean into the file ?
That's it! conduit.toml was not happy with a 1 in place of "true" :p
[09:34:23]
<Tag> eric_G: about conduit_ynh, I am starting to think we only need one nginx config file, because the app doesn't need `/` path
[09:37:28]
<orhtej2> How does one remove contents of `$install_dir`? I see `ynh_setup_source` deletes the folder then restores it with right permissions using private helper, any way of replicating this behaviour other than yolocopying?
[09:38:25]
<Aleks (he/him/il/lui)> hmmm ynh_setup_source doesnt delete the folder (during upgrades) unless you're using --full-replace=1
[09:39:27]
<orhtej2> > <@Alekswag:matrix.org> hmmm ynh_setup_source doesnt delete the folder (during upgrades) unless you're using --full-replace=1
That's the behaviour I'm trying to replicate, yes
[09:39:36]
<orhtej2> But without seeing up sources
[09:40:04]
<orhtej2> I want to move app contents into a subdirectory
[09:41:45]
<Aleks (he/him/il/lui)> not sure to get the issue 😅 if you want to move content, use `mv` ? :p
[10:04:20]
<orhtej2> > <@Alekswag:matrix.org> not sure to get the issue 😅 if you want to move content, use `mv` ? :p
That's certainly an idea
[12:21:32]
<lapineige> Do we have an "example_ynh" but for yarn installs ?
[12:22:07]
<lapineige> I mean a very simple app that use it, I need an example because I can't remember how to manage yarn installs 😅
[12:26:06]
<orhtej2> > I mean a very simple app that needs it, I need an example because I can't remember how to manage yarn installs 😅
umami_ynh?
[12:26:55]
<lapineige> Very neat, thanks a lot 🤍
[12:28:38]
<orhtej2> > Very neat, thanks a lot 🤍
Actually there was one that installed yarn straight from manifest 🤔
[12:29:01]
<lapineige> which sounds great
[12:29:16]
<lapineige> manifest everything
[12:44:41]
<lapineige> I added this as an option for the app generator ™️ 🙂
[12:59:27]
<Salamandar> hmm don't want to stir a known issue, but wouldn't https://ci-apps.yunohost.org/ci/ benefit from having more than 1 runner ? 😅
[13:38:45]
<lapineige> Is there any \_HOSTNAME\_ parameter ?
[13:55:36]
<orhtej2> > Is there any __HOSTNAME__ parameter ?
What would you use it for
[13:55:55]
<lapineige> nevermind I realised it was a mistake
[13:56:29]
<orhtej2> https://github.com/YunoHost-Apps/roundcube_ynh/blob/master/conf/config.inc.php#L21C22-L21C52
[13:57:26]
<lapineige> An app ask for this:
```
"baseurl": "https://the-non-ynh-server.org",
"hostname": "the-non-ynh-server.org",
```
[13:57:30]
<lapineige> How can I provide both ?
[14:14:56]
<lapineige> Also is there an `autoupdate.strategy` parameter for Gitlab releases ?
[14:42:19]
<orhtej2> > Also is there an `autoupdate.strategy` parameter for Gitlab releases ?
latest_github_release as per https://yunohost.org/en/packaging_apps_resources#regarding-autoupdate
[14:42:44]
<lapineige> but for *Gitlab* ?
[14:43:06]
<orhtej2> > but for *Gitlab* ?
Ahh that I don't know
[14:54:53]
<lapineige> First app packaged with the App Generator ™️ 🎉 🚀
[14:59:11]
<lapineige> Lots of fixes included, and some significant improvements. I'm pushing that new version (0.6) online 😉 yologen.lapineige.fr
[16:11:46]
<lapineige> https://ci-apps-dev.yunohost.org/ci/job/9791
> WARNING cat: /etc/yunohost/psql: No such file or directory
Uh what's happening ? 🤔
[16:12:34]
<lapineige> PostgreSQL configured properly 🤔
https://github.com/YunoHost-Apps/gancio_ynh/blob/testing/manifest.toml#L106
[16:48:51]
<orhtej2> > https://ci-apps-dev.yunohost.org/ci/job/9791
> > WARNING cat: /etc/yunohost/psql: No such file or directory
>
> Uh what's happening ? 🤔
Have postgres listed as apt dependency
[16:49:13]
<orhtej2> You should have gotten liner warning on that
[16:49:28]
<orhtej2> Linter*
[16:52:55]
<orhtej2> https://github.com/YunoHost/package_linter/blob/cb892f1c4203f7a197369b37f6cbec68521a68ce/package_linter.py#L1969C23-L1969C23
[17:04:08]
<lapineige> > Have postgres listed as apt dependency
I always forget this one ! 😆
[17:04:25]
<lapineige> > You should have gotten liner warning on that
Then it's buggy
[17:04:59]
<lapineige> > You should have gotten liner warning on that
Oh I see it… but it's not a red one ! 🤔
[17:09:42]
<lapineige> Then I'll fix the generator 😄
[17:22:25]
<orhtej2> > Oh I see it… but it's not a red one ! 🤔
I'm just guessing that was the culprit, perhaps ci is just borked
[17:23:08]
<lapineige> That was it 🙂
[17:23:34]
<lapineige> I guess that will be fixed by provisioning postgresql package as well as the DB
[17:29:00]
<lapineige> 🆙 🙂 (in case it was hidden by the rest 🙂
[17:29:05]
<lapineige> 🆙 🙂 (in case it was hidden by the rest 🙂)
[17:40:09]
<orhtej2> > 🆙 🙂
https://framagit.org/les/gancio/-/blob/master/server/config.js?ref_type=heads#L42
[17:40:16]
<orhtej2> Just ignore it?
[17:41:02]
<orhtej2> Also what you're doing is not the author - intended way, wonder if it'll work
[17:41:46]
<orhtej2> They use `yarn add` which as I understand automatically generates the cong
[17:41:50]
<orhtej2> Conf*
[17:43:27]
<orhtej2> But I cannot figure out what it actually does and their plan with global installation looks terrible
[17:48:51]
<lapineige> > Just ignore it?
Oh, good catch !
Thanks !
[17:49:26]
<lapineige> > Also what you're doing is not the author - intended way, wonder if it'll work
what do you mean ?
[17:54:22]
<orhtej2> > what do you mean ?
https://gancio.org/install/debian
[17:55:02]
<orhtej2> Magic command is
`sudo yarn global add --network-timeout 1000000000 --silent https://gancio.org/latest.tgz`
[18:00:14]
<lapineige> Yeah, but we need to adapt this to Yunohost. 🤔
[18:00:28]
<lapineige> I supposed a simple yarn install after download the source would do it, but apparently not…
[18:00:44]
<lapineige> I know nothing about yarn so I don't know how to convert it
[18:01:53]
<lapineige> And now CI is failing with the service apparently. I can't figure out the correct syntax for https://github.com/YunoHost-Apps/gancio_ynh/blob/testing/conf/systemd.service#L11 (the previous try gave this https://ci-apps-dev.yunohost.org/ci/job/9798).
Maybe it's because it's not installed?
[18:13:15]
<lapineige> > They use `yarn add` which as I understand automatically generates the cong
but I want to specify the config file myself, else we would have to do some string_replace stuff… 😕
[19:59:05]
<tituspijean> I have just spent one hour trying to understand why the latest Flarum autoupdate was failing... somehow the source URL got replaced (flarum/flarum to flarum/framework): https://github.com/YunoHost-Apps/flarum_ynh/pull/220/files
[20:06:16]
<tituspijean> ooooh I've owned myself.
[20:07:23]
<tituspijean> the autoupdater checks for repo set in upstream.code, and guess which url I put in there...
[20:10:01]
<lapineige> https://this-wont-work.wtfishappening
[20:10:06]
<lapineige> https://this-wont-work.wtf/ishappening
[20:10:23]
<lapineige> https://this-wont-work.wtf/ishappening ? 😁
[21:12:52]
<lapineige> > And now CI is failing with the service apparently. I can't figure out the correct syntax for https://github.com/YunoHost-Apps/gancio_ynh/blob/testing/conf/systemd.service#L11 (the previous try gave this https://ci-apps-dev.yunohost.org/ci/job/9798).
> Maybe it's because it's not installed?
I tried to install it, it always help : in fact there were an 2 errors in the json, and there is no "install" action for yarn… only "build" and "start".
I'm trying the build step manually…
[21:13:14]
<lapineige> (I hate this NodeJS ecosystem, I never understand anything and no one explain it…)
[21:13:36]
<lapineige> (I hate this NodeJS ecosystem, I never understand anything and no one explain it… Admins are not supposed to be multi-languages devs…)
[21:16:21]
<lapineige> Oh and that shit calls `nuxt`, whatever it is… but `/bin/sh: 1: nuxt: not found`… https://ci-apps-dev.yunohost.org/ci/job/9806
It's found on my server…
[21:25:15]
<lapineige> Ok I've got it working on my server, I need to figure out how to reproduce this…
[21:48:28]
<orhtej2> > (I hate this NodeJS ecosystem, I never understand anything an no one explain it…
This
[21:49:41]
<orhtej2> > Oh and that shit calls `nuxt`, whatever it is… but `/bin/sh: 1: nuxt: not found`… https://ci-apps-dev.yunohost.org/ci/job/9806
> It's found on my server…
`yarn add nuxt`?
[21:49:57]
<lapineige> apparently it's not needed… not sure
[21:56:30]
<Yunohost Git/Infra notifications> [apps] @lapineige opened [pull request #1739](https://github.com/YunoHost/apps/pull/1739): add Gancio
[22:06:42]
<lapineige> Apparently it was 😆
[22:08:59]
<orhtej2> > Apparently it was 😆
how about
```
yarn
yarn build
```
as per https://framagit.org/les/gancio/-/blob/master/release.sh?ref_type=heads#L4 ?
[22:09:26]
<orhtej2> and, before you ask, I have no clue what parameterless `yarn` does :P
[22:10:50]
<orhtej2> > Running `yarn` with no command will run `yarn install`, passing through any provided flags.
[22:14:05]
<lapineige> Now I have: https://ci-apps-dev.yunohost.org/ci/job/9811
```
142392 INFO DEBUG - ╭──────────────────────────────────────────────────────────────────────────────╮│ ││ ✖ Nuxt Fatal Error ││ ││ Error: ││ ││ Vue packages version mismatch: ││ ││ - vue@3.3.4 ││ - vue-server-renderer@2.7.14 ││ ││ This may cause things to work incorrectly. Make sure to use the same ││ version for ││ both. ││ ││ │╰──────────────────────────────────────────────────────────────────────────────╯
142392 INFO DEBUG -
```
[22:14:28]
<lapineige> (Oh great that look is completly borken…)
[22:14:58]
<lapineige> > > Running `yarn` with no command will run `yarn install`, passing through any provided flags.
So I need to do the install (that doesn't exist apparently ??) before the build ? wtf…
[22:15:36]
<lapineige> > how about
>
> ```
> yarn
> yarn build
> ```
>
> as per https://framagit.org/les/gancio/-/blob/master/release.sh?ref_type=heads#L4 ?
That script is here to publish a new version, not to install it, right ?
[22:16:15]
<orhtej2> > So I need to do the install (that doesn't exist apparently ??) before the build ? wtf…
install is yarn's built-in I believe
[22:17:06]
<orhtej2> > That script is here to publish a new version, not to install it, right ?
yeah but I would assume installation of yarn package is more or less unzipping of archive so likely this properly builds runnable deployment, then zips it and pushes to registry. Is there harm in giving it a shot?
[22:18:12]
<lapineige> I'm on it 🙂
[22:33:10]
<lapineige> no luck
[22:37:27]
<lapineige> I don't understand why it works on my server (because I have other Node stuff installed, such as Calckey ?) and not in the CI
[22:52:25]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @twiguard [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/561#issuecomment-1732426525) on [issue #561](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/561) Nexcloud install fails: Username is invalid because files already exist for this user: If you had NC installed in the before, the /home/yunohost.app/nextcloud/ dir can sometimes be left sitting there. You sh...