[01:28:00]
<Yunohost Git/Infra notifications> App gitlist stays at level 1 in job [#14837](https://ci-apps.yunohost.org/ci/job/14837)
[04:08:47]
<Yunohost Git/Infra notifications> App jirafeau rises from level 6 to 8 in job [#14841](https://ci-apps.yunohost.org/ci/job/14841) !
[04:20:55]
<Yunohost Git/Infra notifications> App yunorunner failed all tests in job [#14842](https://ci-apps.yunohost.org/ci/job/14842) :(
[07:21:05]
<Yunohost Git/Infra notifications> Job [#14843](https://ci-apps.yunohost.org/ci/job/14843) for prettynoemiecms failed miserably :(
[08:53:47]
<tituspijean[m]> gotta auto-patch all these `password=pass` in the check_process filesd
[08:54:08]
<tituspijean[m]> or within yunorunner?
[10:19:25]
<Aleks (he/him/il/lui)> Zblerg yeah ... I thought i had set the corresponding setting to -1 ...
[10:49:02]
<Yunohost Git/Infra notifications> Job [#14843](https://ci-apps.yunohost.org/ci/job/14843) for prettynoemiecms failed miserably :(
[10:57:22]
<Aleks (he/him/il/lui)> > <@titus:pijean.ovh> or within yunorunner?
it's not trivial to fix in yunorunner because in this case it's an arg specified in check_process like any other arg ... or we could add a big ugly "if arg_name == password" but hmpf
[11:07:04]
<tituspijean[m]> autopatch it is, then 🙂
[11:09:47]
<tituspijean[m]> I'll do that over the weekend
[12:55:29]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @Jaxom99 [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/485#issuecomment-1500264306) on [issue #485](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/485) Upgrade fails due to moving data elsewhere and deleting the original directory: This workaround is also needed when restoring on a new server, at least for version 24.0.7~ynh1. Doing : mkdir /h...
[14:05:50]
<autra> I have a 502 on https://ci-apps.yunohost.org/ci it seems
[14:06:35]
<autra> hey \o things seems to have changed since last time I published diaspora : yunohost now automatically considers master as the release branch for apps, am I right?
[14:07:31]
<Aleks (he/him/il/lui)> uuh yeah that's the case since a long time ago i think ?
[14:08:21]
<Aleks (he/him/il/lui)> ci-apps is being moved to another server I think
[15:35:45]
<autra> Aleks (he/him/il/lui): yeah, I didn't release diaspora since a long time 😅 but also I keep forgetting these details. I should document it somewhere if not done already.
[15:35:51]
<autra> thanks for the heads up anyway
[15:38:21]
<Aleks (he/him/il/lui)> cf the small warning block at the end of https://github.com/yunohost/apps#how-to-add-your-app-to-the-application-catalog
[15:58:57]
<oufmilo[m]> hello everybody i hope everything is good for all
i want to know how it's possible to launch a command in a script and automatically say 'yes' after launch it
i don't know if you understand me ? ^^
[16:01:11]
<autra> ok perfect, now I just have to wait for the ci to come back to understand why it fell down to lvl 2 (I'm betting on job timeout, those ruby app sure take a long time to build)
[16:15:54]
<Aleks (he/him/il/lui)> > hello everybody i hope everything is good for all
> i want to know how it's possible to launch a command in a script and automatically say 'yes' after launch it
> i don't know if you understand me ? ^^
yes, using something like `your_comand <<< "yes"`
[16:17:42]
<Aleks (he/him/il/lui)> > <@autra:trancart.eu> ok perfect, now I just have to wait for the ci to come back to understand why it fell down to lvl 2 (I'm betting on job timeout, those ruby app sure take a long time to build)
hmmm but you just merged a PR which apparently was reported as level 8 by the CI ... shouldnt you just wait for the new level to propagate on the .toml ?
[16:32:14]
<oufmilo[m]> ``` $install_dir/venv/bin/python3 "$install_dir/manage.py" makemigrations --merge <<< "yes" ```
[16:32:34]
<oufmilo[m]> `$install_dir/venv/bin/python3 "$install_dir/manage.py" makemigrations --merge <<< "yes"`
like this ?
[16:32:36]
<autra> Yes, but diaspora was level 7 or 8 before, then fell down to level 2 without any reason (not even a commit on master). As the dev CI often fails because of timeouts, I wanted to check if it was the case with the official CI as well. Because I don't want the level to change randomly just because of timeouts...
[16:36:57]
<oufmilo[m]> > `$install_dir/venv/bin/python3 "$install_dir/manage.py" makemigrations --merge <<< "yes"`
>
> like this ?
i think it's ok like this ! thank you Aleks (he/him/il/lui)
[16:38:25]
<Aleks (he/him/il/lui)> (are you sure there isn't a `--yes` or `--force` or whatever option for makemigrations ?)
[16:39:27]
<oufmilo[m]> > <@Alekswag:matrix.org> (are you sure there isn't a `--yes` or `--force` or whatever option for makemigrations ?)
i'm looking for
[16:43:54]
<oufmilo[m]> i have `--skip-checks` maybe
[16:44:28]
<oufmilo[m]> i have `--skip-checks` maybe
i get try this one
[16:52:36]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @lapineige [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/376#issuecomment-1500458051) on [issue #376](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/376) Nginx rule for Rich Documents / CODE is missing a path for ARM64: Is this still an issue ?
[17:13:31]
<oufmilo[m]> doesn't work with `--skip-checks`
[17:16:56]
<Yunohost Git/Infra notifications> Job [#14851](https://ci-apps.yunohost.org/ci/job/14851) for pydio failed miserably :(
[17:20:23]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @lapineige opened [issue #565](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/565): Collabora built-in server install & configure fails
[17:21:14]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @lapineige edited [issue #565](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/565): Collabora built-in server install & configure fails
[17:21:25]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @lapineige edited [issue #565](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/565): Collabora built-in server install & configure fails
[18:28:13]
<Yunohost Git/Infra notifications> [nextcloud_ynh] @lapineige edited [issue #565](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/565): Collabora built-in server install & configure fails
[19:53:39]
<Yunohost Git/Infra notifications> App kodi failed all tests in job [#14853](https://ci-apps.yunohost.org/ci/job/14853) :(
[20:25:14]
<Yunohost Git/Infra notifications> App question2answer stays at level 2 in job [#14854](https://ci-apps.yunohost.org/ci/job/14854)
[21:47:10]
<Yunohost Git/Infra notifications> App radicale failed all tests in job [#14857](https://ci-apps.yunohost.org/ci/job/14857) :(
[22:56:46]
<Spok> Is it possible to reponen issue on github?
[22:57:47]
<Spok> googled it for myself: https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github
> you cannot re-open your own issues if a repo collaborator closed them