[01:56:15]
<Yunohost Git/Infra notifications> App geoquest rises from level 7 to 8 in job [#24847](https://ci-apps.yunohost.org/ci/job/24847) !
[02:11:43]
<Yunohost Git/Infra notifications> App helloworld stays at level 4 in job [#24850](https://ci-apps.yunohost.org/ci/job/24850)
[07:37:34]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: remove old systemd config on migration ([af715219](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/af715219ac5cbf5f0c3ecc4ccd5c662a92c9a87c))
[07:49:59]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: update .env file on upgrade ([d0c0a38e](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/d0c0a38ec27a4ecef8b2d3fe8ebb6ee9588b9ab0))
[09:14:06]
<kayou> https://github.com/YunoHost-Apps/docusaurus_ynh/blob/08ce0336c398f4ca670312aecbe64ef9a80e2241/manifest.toml#L58
https://github.com/YunoHost-Apps/docusaurus_ynh/blob/08ce0336c398f4ca670312aecbe64ef9a80e2241/manifest.toml#L10
oupsie
[09:14:13]
<kayou> why there is no autoupdate anyway? 🤔
[09:15:14]
<Thomas> > <@kayou:matrix.org> why there is no autoupdate anyway? 🤔
Because it's not in the catalog yet I think
[09:16:09]
<kayou> hoo
[09:16:47]
<kayou> Since we are using Docusaurus for the YNH document, I thought it would be
[09:51:09]
<Salamandar> well actually there's no real reason to package docusaurus
[09:51:11]
<Salamandar> it's static pages
[09:51:42]
<Salamandar> maybe if we packaged a cron that checked a git repo every X time and did a rebuild, why not…
[09:52:03]
<Salamandar> but the best / simplest setup is a my_webapp + ftp or rsync to upload the files from the CI
[10:36:41]
<kayou> how is managed docusaurus upgrade then? (is it even usefull to upgrade it?)
[10:57:38]
<orhtej2> > <@Salamandar:matrix.org> but the best / simplest setup is a my_webapp + ftp or sshfs to upload the files from the CI
We packaged Pelican and Zola 🤷
[10:57:38]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: handle archives with ynh_read_manifest ([24c2e6d9](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/24c2e6d98c2671e771dbb80511f28d9dbbb8c8e9))
[11:06:01]
<Thomas> Does someone understand why I’ve _common.sh: line 24: ynh_read_manifest: command not found?
https://ci-apps-dev.yunohost.org/ci/job/14887
https://github.com/YunoHost-Apps/jellyfin_ynh/blob/24c2e6d98c2671e771dbb80511f28d9dbbb8c8e9/scripts/_common.sh#L24
[11:51:41]
<ewilly> > <@thovi98:matrix.org> Does someone understand why I’ve _common.sh: line 24: ynh_read_manifest: command not found?
> https://ci-apps-dev.yunohost.org/ci/job/14887
> https://github.com/YunoHost-Apps/jellyfin_ynh/blob/24c2e6d98c2671e771dbb80511f28d9dbbb8c8e9/scripts/_common.sh#L24
Due to the sourcing order in install script: common.sh is soyrced before the helpet
[11:54:12]
<Thomas> So if I change it to
source /usr/share/yunohost/helpers
source _common.sh
it should work?
[11:54:16]
<Thomas> Thanks I’ll try
[11:55:53]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: change sourcing order to have helpers first ([7c284800](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/7c2848006e3b9b370d75e12e7ee2b74a4a71a543))
[12:04:16]
<Thomas> Yeah it works! Thanks! But the CI doesn't like that and shows a warning 🙃
[12:11:20]
<Salamandar> Uuuuuuh all that stuff should be in a function, not bare in the common file
[12:11:38]
<Salamandar> you're doing a curl each time the common.sh is sourced (so on remove, change_url etc)
[12:11:51]
<Salamandar> and that would solve the inclusion order too
[12:14:19]
<Thomas> Oooh yes ok ok, I understand I’ll change that, thanks
[12:25:39]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: move package installation/upgrade in a function ([9797beda](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/9797beda9f5da901f006ab3d51bc8cb03ec466e2))
[14:11:11]
<Yunohost Git/Infra notifications> [syncthing_ynh] geckods [commented](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156#issuecomment-3558273482) on [issue #156](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156) feature request: improve documentation on using foulders (safely) outside /home/yunohost.app/syncthing/: I did this and it seems to be working for me:
# Create a group that both you and the syncthing user can share
sudo gro...
[14:11:30]
<Yunohost Git/Infra notifications> [syncthing_ynh] geckods [commented](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156#issuecomment-3558273482) on [issue #156](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156) feature request: improve documentation on using foulders (safely) outside /home/yunohost.app/syncthing/: I did this and it seems to be working for me:
# Create a group that both you and the syncthing user can share
sudo ...
[15:02:21]
<Yunohost Git/Infra notifications> [syncthing_ynh] geckods [commented](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156#issuecomment-3558273482) on [issue #156](https://github.com/YunoHost-Apps/syncthing_ynh/issues/156) feature request: improve documentation on using foulders (safely) outside /home/yunohost.app/syncthing/: I did this and it seems to be working for me:
# Create a group that both you and the syncthing user can share
sudo ...
[15:39:32]
<eric_G> There is this user making multiple PR translating `DESCRIPTION.md` to Portuguese (pt_BR). I told him that it wasn't the right place to make translation (I don't know where to contribute those translations...) -> https://github.com/YunoHost-Apps/wordpress_ynh/pull/259
[15:41:41]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to postgresql_reboot: Update manifest.toml ([515f0779](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/515f07799935eed84aeafe3890a7390de0a8aab2))
[15:42:39]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to postgresql_reboot: Update manifest.toml ([0fe02a0f](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/0fe02a0ff04494610e48b33e9c3f874567f1724e))
[15:42:40]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to postgresql_reboot: Merge branch postgresql_reboot of https://github.com/YunoHost-Apps/nextcloud_ynh into postgresql_reboot ([1c674067](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/1c674067947f3e6baa18caa9895b353b81cf4a73))
[15:43:02]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to testing: Update manifest.toml ([a56e653d](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/a56e653db21b00fe35c0c7fb50861a51c04ce3ef))
[15:43:07]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar opened [pull request #841](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/841): Testing
[15:43:29]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to testing: Testing (#833) * Update ADMIN.md: update advice to open shell + add a note on how to promote a user to admin * Update ... ([4c9942cc](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/4c9942cc837a46d5f12e9514813b91a6d8a8da7d))
[15:43:32]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to testing: Merge branch master into testing ([497efd5a](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/497efd5a0f0308558a5a9eb330f3b8d47b28c2f7))
[15:43:42]
<Aleks (he/him/il/lui)> merf yeah maybe that's because i wrote in the new translation doc page about app translations ... https://doc.yunohost.org/dev/translation/ ... also saying that the current flow for app translation isnt great but yeah it's gonna be hell if too many people start contributing too many translations in apps i suppose ...
[15:44:25]
<Aleks (he/him/il/lui)> (right now I'm not even sure if `pt_BR` matches the nomenclature that YunoHost is using internally for locales, it may just be only `pt` ....)
[15:46:16]
<kayou> https://github.com/YunoHost-Apps/nextcloud_ynh/blob/497efd5a0f0308558a5a9eb330f3b8d47b28c2f7/manifest.toml#L10
UwU I'm not maintaining anything :/
[15:46:59]
<Salamandar> yeah we're regularly questioning the existence of this field
[15:47:02]
<Salamandar> no one ever updates it
[15:47:16]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Update manifest.toml ([6da18c68](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/6da18c68b0653ec98b0c160b0716cf0aa4858d3a))
[15:47:37]
<Salamandar> and that is just a risk of humans being spammed / harassed
[15:47:42]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Testing (#833) * Update ADMIN.md: update advice to open shell + add a note on how to promote a user to admin * Update ... ([4c9942cc](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/4c9942cc837a46d5f12e9514813b91a6d8a8da7d))
[15:47:44]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Update manifest.toml ([a56e653d](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/a56e653db21b00fe35c0c7fb50861a51c04ce3ef))
[15:47:45]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Auto-update READMEs ([d2b04e92](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/d2b04e9267dddebc0c9b3f9fad5f8993131bde40))
[15:47:46]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Merge branch master into testing ([497efd5a](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/497efd5a0f0308558a5a9eb330f3b8d47b28c2f7))
[15:47:47]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to 32: Merge branch testing into 32 ([32d49022](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/32d49022a1e642ef1759953d395e6dba094973f3))
[15:47:59]
<Aleks (he/him/il/lui)> very much in favor of burning it and having a discussion about what it means to be "maintainer" and alternative, more flexible/smooth way of handling "who may be interested in helping maintaining this app" or something idk
[15:49:01]
<kayou> feel free to remove me :)
[16:01:54]
<eric_G> but you will be blamed if Nextcloud is broken 😶🌫️
[16:24:26]
<miro5001> I asked a while ago about having the maintainership for an app (joomla if I remember correctly) here, because I have contributed in the package and I use it, so I know how it works and how to handle its administration and easily fix its issues.
[16:34:12]
<Aleks (he/him/il/lui)> concretely we have no proper maintainership system,
- anybody with access to the repo can add its name in the `maintainers` list in `manifest.toml`,
- plenty of times people just put their name kind of "by default" without any plan to babysit this app in particular (because too much things in life etc and you can't realistically babysit more than a handful of apps)
- it's easy to be enthusiast about an app when packaging it for the first time, therefore you add your name in `maintainers`, but then life goes on and fast-forward 3 months later you may not care about it as much as initially (which is fine, again, life etc) but then pretty much nobody will think about coming back and removing one's name from the `maintainers` key, and because this kind of situation happens for too many apps, the `maintainers` key is essentially meaningless
- people may randomly come fix / clean / improve a specific app but don't want to commit to being flagged as "maintainer" even though, for a short period of time, they effectively are ... increasing a bit more the meaningless-ness of the `maintainers` key
- some people ***do*** explicit commit to specific app, in specific cases, and want to actively review and accept other people's contribution ... and for this there's no proper mechanism to track this considering the `maintainers` key is meaningless, so it's just like ... "people know" (or don't know) that \<specific app> is handled by \<specific person>
[16:45:02]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3208](https://github.com/YunoHost/apps/pull/3208): Add wishthis to wishlist
[16:53:38]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar merged [pull request #841](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/841): Testing
[16:53:39]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed to master: Testing (#841) ([18abdaf8](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/18abdaf81f41c376db689a3ea6fcae33d304d1cc))
[16:53:44]
<Thomas> > <@Alekswag:matrix.org> concretely we have no proper maintainership system,
>
> - anybody with access to the repo can add its name in the `maintainers` list in `manifest.toml`,
> - plenty of times people just put their name kind of "by default" without any plan to babysit this app in particular (because too much things in life etc and you can't realistically babysit more than a handful of apps)
> - it's easy to be enthusiast about an app when packaging it for the first time, therefore you add your name in `maintainers`, but then life goes on and fast-forward 3 months later you may not care about it as much as initially (which is fine, again, life etc) but then pretty much nobody will think about coming back and removing one's name from the `maintainers` key, and because this kind of situation happens for too many apps, the `maintainers` key is essentially meaningless
> - people may randomly come fix / clean / improve a specific app but don't want to commit to being flagged as "maintainer" even though, for a short period of time, they effectively are ... increasing a bit more the meaningless-ness of the `maintainers` key
> - some people ***do*** explicit commit to specific app, in specific cases, and want to actively review and accept other people's contribution ... and for this there's no proper mechanism to track this considering the `maintainers` key is meaningless, so it's just like ... "people know" (or don't know) that \<specific app> is handled by \<specific person>
There was the idea of adding CODEOWNERS at some point I think?
[16:56:32]
<Salamandar> there was
[16:57:21]
<Salamandar> but that's still one file per repo
[16:58:31]
<Aleks (he/him/il/lui)> yes i suppose, maybe, to me the biggest question is : it's easy to design something where people can declare themselves as maintainers, the question is rather how do you "remove" people from it ... i mean if we want an explicit list of "maintainer" system (in the manifest or CODEOWNERS or whatev) that contains meaningful info, it means that when reading the info, people except things such as some sort of responsiveness when opening issues or pull request or being able to ask for code review, idk
so how do we formalize what it means to be "maintainer" etc, and automatically remove names that are not active anymore on the package (again not trying to be like "shaming", it's not the point, the point is that the info should be meaningful)
[17:00:14]
<Aleks (he/him/il/lui)> personally I don't have much hope in a formal maintainership system where people have to put their name in front of a bunch of responsabilities and whatever, I'm more into some sort of liquid, loose system where "maintainership" is semi-automatic like based on who was active on the repo in the last 6 months, which member of the "regular contributors" github team have starred the app on the catalog, that kind of thing ...
[17:02:31]
<Salamandar> And that is closer to what's been happening historically on yunohost-apps
[17:04:44]
<Aleks (he/him/il/lui)> yeah, imho it should be less like "maintainership" and more like "technical members of the YunoHost-Apps org **interested** and/or de-facto active on this app"
[17:10:40]
<Thomas> But then there is also the question of how many reviews there should have (or the time without review) for technical/popular apps
[17:18:21]
<Salamandar> Ah we could indeed have a branch protection rule for some apps
[17:18:28]
<Salamandar> minimum 1 review
[17:23:40]
<Aleks (he/him/il/lui)> Hmpf we had this kind of stuff in the past where we tried to formalize number of reviews and stuff honestly it was just a bureaucratic nightmare i just lost my mind 2 or 3 years about that kind of crap
[17:24:32]
<Aleks (he/him/il/lui)> Maybe it may be worth for specific app like Nextcloud but even then i'm not convinced because then fixing typo or other obvious fixes turn into a fullton of crap
[17:29:54]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: more precise env variables and explicitely remove old debs during migration ([29cab9db](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/29cab9db333d88f8a29d9c9e6b0e578eab8de002))
[17:43:27]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: recreate user after deleting old deps ([df676406](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/df676406148e39b08361578a3c4ed29345f48588))
[17:58:48]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: typo ([10cbf0c8](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/10cbf0c87339f9e4d2731a5e656c057dd86f08f7))
[18:17:45]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: don’t remove jellyfin-server deps ([73767f68](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/73767f68e686ae5fd22ac3dc8f5b0b187eee82ee))
[18:24:05]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: nor jellyfin-web ([ebdcb54a](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/ebdcb54ab2193af16ce3e5fdc706ecfd3ce3ae54))
[18:32:35]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: don’t remove dependencies ([2f52e4ea](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/2f52e4ea64d51c4935f888e8e5e78ae2936c23a9))
[19:00:53]
<Yunohost Git/Infra notifications> [jellyfin_ynh] Thovi98 pushed to ynh-structure: ffmpeg as argument directly in service to be sure it’s the chosen binary ([367b09fb](https://github.com/YunoHost-Apps/jellyfin_ynh/commit/367b09fbc1043eb8877556393f44ac69ebdc9893))
[19:14:04]
<kayou> I remember that, spending 2h to review PRs each days is something :')
[20:14:30]
<thomas> Hi all, I’m using this command in an upgrade script:
`ynh_app_setting_set_default --key=smtp_encryption --value="$(ynh_read_var_in_file --file=$install_dir/.env --key=MAIL_ENCRYPTION)"`
The thing is, with Laravel, to use tls encryption the key in .env must be like this: `MAIL_ENCRYPTION=null`
Problem,when I run the command then in settings.yml I will get `smtp_encryption: YNH_NULL` while I would need it to be `smtp_encryption: null`
As a result, when I run `ynh_write_var_in_file --file=$install_dir/.env --key=MAIL_ENCRYPTION --value="$(ynh_app_setting_get --key=smtp_encryption)"` a little later in the upgrade script, I’m getting `MAIL_ENCRYPTION=YNH_NULL` in .env, which is not what I need.
Is there any way I could have `ynh_app_setting_set_default` writing the "null" string rather that changing it to "YNH_NULL"?
[20:27:31]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 10 commits to postgresql_reboot ([1c674067947f...1857da873699](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/1c674067947f...1857da873699))
[20:27:31]
<miro5001> Why not hardcoding it in env file and drop all setting process
[20:30:09]
<miro5001> MAIL_ENCRYPTION=TLS
[20:48:01]
<thomas> > Why not hardcoding it in env file and drop all setting process
I thought that offering the ssl solution rather than tls for people who would only have access to that kind of encryption would be nice. Honestly I don’t know much about encryption protocols, so if you tell me that ssl encryption is now completely deprecated, then yeah, I guess I can save the trouble.
[21:12:07]
<miro5001> In the yunohost email client documentation, it is recommended to use TLS for smtp. I just googled and the first result I got : TLS is the successor of the outdated ssl for smtp.
[22:03:10]
<Aleks (he/him/il/lui)> thomas: please share the link to the code because YNH_NULL is rather something related / coming from the config panel logic, cf for example this snippet https://github.com/YunoHost/yunohost/blob/dev/helpers/helpers.v2.1.d/config#L35-L36 which suggests that if you have `bind=null` in the config panel then the value might be set to YNH_NULL or idk that may not be the only explanton
[22:11:35]
<Yunohost Git/Infra notifications> App rallly goes down from level 8 to 7 in job [#24864](https://ci-apps.yunohost.org/ci/job/24864)
[23:19:01]
<Yunohost Git/Infra notifications> [mastodon_ynh] yunohost-bot opened [pull request #538](https://github.com/YunoHost-Apps/mastodon_ynh/pull/538): Upgrade to v4.5.2
[23:30:15]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 35 pending update PRs
- 11 new apps PRs: code-server, commafeed, fab-manager, filerise, immich, jackett, kimai2, limesurvey, mastodon, nodebb, readeck
- 10 failed apps updates: calibreweb-automated, element-call, fluffychat, fusion, lidarr, litechat, loops, quizzes, radarr, sabnzbd
See the full log here: https://paste.yunohost.org/raw/aboxukugak
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate