Monday, May 06, 2024
apps@conference.yunohost.org
May
Mon Tue Wed Thu Fri Sat Sun
    1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
   
             

[01:58:04] <Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:

- 59 pending update PRs
- 9 new apps PRs
- 6 failed apps updates: bazarr, elasticsearch8, firefly-iii, focalboard, tvheadend, vikunja

See the full log here: http://paste.yunohost.org/raw/gakinahato
[03:06:40] <Yunohost Git/Infra notifications> App phpipam goes down from level 8 to 6 in job [#26184](https://ci-apps.yunohost.org/ci/job/26184)
[03:56:15] <limezy> Hi all, I have a small problem when trying to fix the borgwarehouse app
[03:56:26] <limezy> https://ci-apps-dev.yunohost.org/ci/job/15593
[03:56:42] <limezy> I get a linter warning because I'm storing data in /home/$app
[03:57:46] <limezy> I have managed to create a symlink from /home/$app to /home/yunohost.app/$app, but I still get the warning
[03:59:05] <limezy> It seems that there are only two options for that app to get level 7
* Either we change the CI rules for this exceptional case
* Either I have to patch the sources of the upstream app to use /home/yunohost.app/$app everytime instead of /home/$app
It's doable but quite heavy for the app maintener to update the patch at every release...
[03:59:08] <limezy> Any other idea ?
[04:00:05] <limezy> Thanks for your help !
[04:00:36] <limezy> Of course it's wrong practice, but it has to be that way because the dev of borgwarehouse has written the whole app this way. It's hardcoded and you can't change it
[04:50:05] <Émy - OniriCorpe> It’s not hardcoded, for example: https://github.com/Ravinou/borgwarehouse/blob/938595f86a831c678bffdb2436813d517ae5f57d/helpers/shells/deleteRepo.sh#L16
It’s the $home environment variable, the code will only define an empty $home variable to “/home/borgwarehouse” but if the variable is not empty, it will use its value
But yes it’s not documented
[04:57:57] <Émy - OniriCorpe> If you fix the package, I advise you to warn the users about the path change using a doc/PRE_UPGRADE.d/{fixed_version_number-ynhx}.md
[04:59:54] <Émy - OniriCorpe> https://yunohost.org/packaging_app_doc#pre-post-install-notes-pr
[05:17:51] <limezy> You are right, thanks for the heads-up
[05:32:19] <limezy> > <@oniricorpe:im.emelyne.eu> If you fix the package, I advise you to warn the users about the path change using a doc/PRE_UPGRADE.d/{fixed_version_number-ynhx}.md

I should also put a migration logic maybe...
[05:32:48] <limezy> I'm currently trying to build a solid backup system for my servers, borg seems nice but quite hard to use...
[05:44:56] <tituspijean> I have to go to work, so I have no time to fix the commit history mess over at https://github.com/YunoHost-Apps/phpldapadmin_ynh
Can someone have a look? Merging testing into master shows the whole commit history, not only the last few commits.
[07:39:29] <Yunohost Git/Infra notifications> Job [#26181](https://ci-apps.yunohost.org/ci/job/26181) for matrix-puppet-discord failed miserably :(
[07:43:51] <Yunohost Git/Infra notifications> Job [#26194](https://ci-apps.yunohost.org/ci/job/26194) for mstream failed miserably :(
[07:51:04] <Yunohost Git/Infra notifications> App wekan goes down from level 8 to 1 in job [#26193](https://ci-apps.yunohost.org/ci/job/26193)
[08:21:35] <ChriChri> If I look at my apps settings I find that **app** and **id** are the **same** values. Is this correct?
I'd have expected that one reflects the name of the app and the other this instances name of that app if installed multiple times.
[08:38:07] <tituspijean> `$app` and `$id` are indeed the same. First instance of an app will be called `foo` and, subsequent ones `foo__x` (with x starting from 2)
[09:37:19] <thatoo> Hello
I'd like to add something to interrupt the install script to see the state of installation at some point.
I know I can ask to keep installation as it is when it fails thanks to `sudo yunohost app install -n` . I'm looking for adding a command in the script to make it fail at the desired point.
[10:44:30] <ChriChri> Hm, I'd have expected that there'd be a variable that contains the name of the app from the catalog which is for all instances the same - like in my case just 'flohmarkt'.
[10:44:42] <ChriChri> > <@chrichri:librem.one> Hm, I'd have expected that there'd be a variable that contains the name of the app from the catalog which is for all instances the same - like in my case just 'flohmarkt'.

Is there one?
[12:00:28] <Aleks (he/him/il/lui)> just write `flohmarkt` literally ? 😬
[12:02:15] <Aleks (he/him/il/lui)> otherwise there's `$YNH_APP_ID` but honestly just write literally the name of the app, it's not like it's going to change, or if it changes name it's just a recursive `sed` and voila
[12:06:47] <ChriChri> > <@Alekswag:matrix.org> otherwise there's `$YNH_APP_ID` but honestly just write literally the name of the app, it's not like it's going to change, or if it changes name it's just a recursive `sed` and voila

I thought about that and until now decided against it, because I'm planning to split of a 'flohmarkt-development_ynh' which would be exactly the same, but follow HEAD on the flohmarkt git automatically.
I thougt the more I can re-use the better.
Is there a reason I shouldn't use `YNH_APP_ID`?
[12:08:35] <Aleks (he/him/il/lui)> just unecessary complexity i'd say but meh idk ... also because i dont think any app really use it and i was maybe thinking about removing it some day idk 😅
[12:11:41] <tituspijean> > 'flohmarkt-development_ynh' which would be exactly the same, but follow HEAD on the flohmarkt git automatically.

isn't that the job of the autoupdater, which creates appropriate branches in the package repo?
[12:11:41] <Aleks (he/him/il/lui)> (yeah i was wondering about the same thing, tracking HEAD doesnt really fit into YunoHost packaging paradigm because ideally we're supposed to be explicit about the version installed, and there are many implications about yunohost advertising upgrade or not, and also what happens if the upstream suddently realease a major upgrade which requires specific migration etc)
[12:13:50] <Aleks (he/him/il/lui)> however there are use case where it would be nice to have such a flow, though i don't know how to handle all the technicalities such that it's "clean and smooth"

Typically when you are the dev of a rolling-release software and you want it to basically follow git. We have several example on Yunohost infra such as yunorunner, the app store, app generator, app dashboard etc. But also people using for example my_webapp_ynh or flask_ynh and you basically want to "git pull" sometimes
[12:14:06] <Aleks (he/him/il/lui)> Though the "git pull" could also be a button in the config panel of the app
[12:14:13] <Aleks (he/him/il/lui)> (I'm brainstorming out loud)
[12:48:00] <ChriChri> Well, I haven't looked at automatically tracking head, yet. But for a packaging variant meant to be for testers and maybe developers even this would be nice. For normal packages I think automatically updating to the latest version is not a good service for people using the package. In my understanding of this there should be some testing always before making something available to the public.
[12:49:53] <Aleks (he/him/il/lui)> Well uh yes but it's not like this testing takes a super long time and testing is here to uh, having at least a basic check that things ain't gonna explode x_x
[14:19:26] <Yunohost Git/Infra notifications> [apps] yunohost-bot created new branch add-to-wishlist-retronas
[14:19:26] <Yunohost Git/Infra notifications> [apps] yunohost-bot pushed 1 commit to add-to-wishlist-retronas: Add RetroNAS to wishlist ([e0f81ada](https://github.com/YunoHost/apps/commit/e0f81ada80491315fe4058ca5b15b2a548d6680b))
[14:19:28] <Yunohost Git/Infra notifications> [apps] yunohost-bot labeled Wishlist on [pull request #2297](https://github.com/YunoHost/apps/pull/2297): Add RetroNAS to wishlist
[14:19:32] <Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #2297](https://github.com/YunoHost/apps/pull/2297): Add RetroNAS to wishlist
[15:38:04] <Yunohost Git/Infra notifications> App pihole rises from level 6 to 8 in job [#26197](https://ci-apps.yunohost.org/ci/job/26197) !
[18:48:02] <Yunohost Git/Infra notifications> [apps] OniriCorpe [commented](https://github.com/YunoHost/apps/pull/2297#issuecomment-2096651659) on [issue #2297](https://github.com/YunoHost/apps/pull/2297) Add RetroNAS to wishlist: 😬 > WARNING Security > > Due to the nature of retro computing, many of the tools and protocols used in this project a...
[18:48:38] <Yunohost Git/Infra notifications> [apps] OniriCorpe [commented](https://github.com/YunoHost/apps/pull/2297#issuecomment-2096651659) on [issue #2297](https://github.com/YunoHost/apps/pull/2297) Add RetroNAS to wishlist: 😬 > WARNING Security > > Due to the nature of retro computing, many of the tools and protocols used in this project a...
[18:48:55] <Yunohost Git/Infra notifications> [apps] OniriCorpe labeled opinion needed on [pull request #2297](https://github.com/YunoHost/apps/pull/2297): Add RetroNAS to wishlist
[18:49:04] <Yunohost Git/Infra notifications> [apps] OniriCorpe merged [pull request #2296](https://github.com/YunoHost/apps/pull/2296): Translations update from Weblate for readme-generator
[19:33:57] <Yunohost Git/Infra notifications> Job [#26199](https://ci-apps.yunohost.org/ci/job/26199) for weblate failed miserably :(
[19:36:22] <Aleks (he/him/il/lui)> >error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.

restarted
[19:41:10] <Yunohost Git/Infra notifications> [apps] dependabot[bot] pushed 1 commit to dependabot/pip/tools/app_generator/werkzeug-3.0.3: Bump werkzeug from 3.0.1 to 3.0.3 in /tools/app_generator Bumps [werkzeug](https://github.com/pallets/werkzeug) from 3.... ([ddf3a765](https://github.com/YunoHost/apps/commit/ddf3a76547c04d6d0c9fc00a4da101cfaa1ce49b))
[19:41:10] <Yunohost Git/Infra notifications> [apps] dependabot[bot] created new branch dependabot/pip/tools/app_generator/werkzeug-3.0.3
[19:41:11] <Yunohost Git/Infra notifications> [apps] dependabot[bot] labeled dependencies on [pull request #2298](https://github.com/YunoHost/apps/pull/2298): Bump werkzeug from 3.0.1 to 3.0.3 in /tools/app_generator
[19:41:14] <Yunohost Git/Infra notifications> [apps] dependabot[bot] opened [pull request #2298](https://github.com/YunoHost/apps/pull/2298): Bump werkzeug from 3.0.1 to 3.0.3 in /tools/app_generator
[21:49:43] <tituspijean> So you can use the `home` key in the manifest: https://yunohost.org/en/packaging_apps_resources#properties-4
[21:53:07] <Yunohost Git/Infra notifications> App weblate rises from level 6 to 7 in job [#26199](https://ci-apps.yunohost.org/ci/job/26199) !
[21:53:11] <Yunohost Git/Infra notifications> [apps] dependabot[bot] created new branch dependabot/pip/tools/app_generator/jinja2-3.1.4
[21:53:11] <Yunohost Git/Infra notifications> [apps] dependabot[bot] pushed 1 commit to dependabot/pip/tools/app_generator/jinja2-3.1.4: Bump jinja2 from 3.1.3 to 3.1.4 in /tools/app_generator Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.3 to ... ([6397ef07](https://github.com/YunoHost/apps/commit/6397ef074dfaf90f478baeb0b258d85a79577844))
[21:53:12] <Yunohost Git/Infra notifications> [apps] dependabot[bot] labeled dependencies on [pull request #2299](https://github.com/YunoHost/apps/pull/2299): Bump jinja2 from 3.1.3 to 3.1.4 in /tools/app_generator
[21:53:18] <Yunohost Git/Infra notifications> [apps] dependabot[bot] opened [pull request #2299](https://github.com/YunoHost/apps/pull/2299): Bump jinja2 from 3.1.3 to 3.1.4 in /tools/app_generator
[22:05:59] <tituspijean> > <@titus:pijean.ovh> I have to go to work, so I have no time to fix the commit history mess over at https://github.com/YunoHost-Apps/phpldapadmin_ynh
> Can someone have a look? Merging testing into master shows the whole commit history, not only the last few commits.

Thanks eric!
[22:09:09] <Yunohost Git/Infra notifications> App weblate rises from level 6 to 7 in job [#26200](https://ci-apps.yunohost.org/ci/job/26200) !
[22:12:25] <Yunohost Git/Infra notifications> [apps] alexAubin pushed 1 commit to master: Bump jinja2 from 3.1.3 to 3.1.4 in /tools/app_generator (#2299) Bumps [jinja2](https://github.com/pallets/jinja) from 3... ([028507dc](https://github.com/YunoHost/apps/commit/028507dc9bfc6628a9bb66365b2299ba0e5c89b1))
[22:12:25] <Yunohost Git/Infra notifications> [apps] alexAubin deleted branch dependabot/pip/tools/app_generator/jinja2-3.1.4
[22:12:26] <Yunohost Git/Infra notifications> [apps] alexAubin merged [pull request #2299](https://github.com/YunoHost/apps/pull/2299): Bump jinja2 from 3.1.3 to 3.1.4 in /tools/app_generator
[23:09:47] <Yunohost Git/Infra notifications> App immich goes down from level 7 to 6 in job [#26201](https://ci-apps.yunohost.org/ci/job/26201)