[01:09:19]
<Solrac> Catagarr-y
[01:48:07]
<Yunohost Git/Infra notifications> App fastapi rises from level 7 to 8 in job [#24464](https://ci-apps.yunohost.org/ci/job/24464) !
[08:50:49]
<Yunohost Git/Infra notifications> App agewasm rises from level 7 to 8 in job [#24362](https://ci-apps.yunohost.org/ci/job/24362) !
[08:58:04]
<Yunohost Git/Infra notifications> [nextcloud_ynh] luc38090 [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/831#issuecomment-3515656275) on [issue #831](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/831) v32: Im testing Nextcloud 32 on a test server: > yunohost app upgrade nextcloud -u https://github.com/YunoHost-Apps/nextcl...
[09:32:59]
<Yunohost Git/Infra notifications> App grav failed all tests in job [#24375](https://ci-apps.yunohost.org/ci/job/24375) !
[11:24:23]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3193](https://github.com/YunoHost/apps/pull/3193): Add OwnTracks to wishlist
[12:56:23]
<Yunohost Git/Infra notifications> [rustdesk-server_ynh] snmogl opened [issue #37](https://github.com/YunoHost-Apps/rustdesk-server_ynh/issues/37): /var/log/rustdesk-server isntalls with wrong file permissions?
[13:23:58]
<Yunohost Git/Infra notifications> [apps] tituspijean closed [pull request #3193](https://github.com/YunoHost/apps/pull/3193): Add OwnTracks to wishlist
[13:23:58]
<Yunohost Git/Infra notifications> [apps] tituspijean [commented](https://github.com/YunoHost/apps/pull/3193#issuecomment-3516920656) on [issue #3193](https://github.com/YunoHost/apps/pull/3193) Add OwnTracks to wishlist: Already packaged, merely marked as not working.
[13:24:01]
<Yunohost Git/Infra notifications> [apps] tituspijean deleted branch add-to-wishlist-owntracks
[13:32:48]
<eric_G> I am confused with this warning ` ! Using helper ynh_system_user_create is deprecated when using packaging v2 ... It is replaced by: the system_user resource` -> https://ci-apps-dev.yunohost.org/ci/job/14633
[13:34:01]
<eric_G> [https://doc.yunohost.org/en/dev/packaging/scripts/helpers\_v2.1 ](https://github.com/YunoHost/yunohost/blob/b91ab52deb47b942572790cc4b4b36b4b15ec365/helpers/helpers.v2.1.d/systemuser#L70)
[13:35:49]
<miro5001> Why not using the system user declared in the manifest?
[13:58:29]
<Salamandar> Whhy does this link open the github app on Android ? O.o
[13:59:01]
<Salamandar> And more precisely this
https://github.com/YunoHost/yunohost/blob/b91ab52deb47b942572790cc4b4b36b4b15ec365/helpers%2Fhelpers.v2.1.d%2Fsystemuser
[13:59:46]
<Salamandar> Aaaaaah eric g wrote a tricky message
[13:59:53]
<Aleks (he/him/il/lui)> :D
[14:00:56]
<Salamandar> https://github.com/yunohost-bot/borgserver_ynh/blob/auto-helpers-2.1/scripts%2Finstall#L29
The package manually creates a user
[14:01:44]
<Salamandar> But that's not the user for the app service, so the warning should be ignored
[14:02:01]
<Salamandar> Maybe we could have something like the pythonic # type : ignore but for our linter
[14:12:23]
<Aleks (he/him/il/lui)> on the one hand yes, but on the other hand it opens the door to people ignoring situation that shouldnt exist in the first place ... or not contributing to the core to address the underlying issue in some cases
but yeah
there is one way tho, but should i really share it ..
[14:14:57]
<Aleks (he/him/il/lui)> (CW cursed, bash gore) https://github.com/YunoHost-Apps/synapse\_ynh/blob/master/scripts/install#L212
[14:35:47]
<Salamandar> Well yes but actually no
[14:39:19]
<tituspijean[m]> *wait that's illegal*
[14:56:23]
<Aleks (he/him/il/lui)> https://i.imgflip.com/absl3l.jpg
[15:04:07]
<Yunohost Git/Infra notifications> [mastodon_ynh] yelvington [commented](https://github.com/YunoHost-Apps/mastodon_ynh/issues/534#issuecomment-3517337631) on [issue #534](https://github.com/YunoHost-Apps/mastodon_ynh/issues/534) Upgrade to 4.5.0 delivers 4.4.8 and 500 errors: Upgrade still failing, 4.4.8 to 4.50:
https://paste.yunohost.org/raw/eruyegateg
Bunch of warnings:
2025-11-10 23:43:02...
[17:34:10]
<Aleks (he/him/il/lui)> >If I rollback grav_ynh to their re-released 1.7.49.5 version, will the catalog follow the new repo HEAD even if the new version is lower?
hmmm assuming you make a new commit i would think yes
[17:34:11]
<tituspijean[m]> Grav's maintainers have just deleted their whole 1.7.50.x branch due to a bug.
If I rollback grav_ynh to their re-released 1.7.49.5 version, will the catalog follow the new repo HEAD even if the new version is lower?
(I'll ignore users who have already upgraded to v1.7.50.x, the bug is only about self-upgrade of the app, which is voluntary, hopefully)
[17:34:11]
<tituspijean[m]> (they will bump to v1.7.51.x once their bug is resolved, so future upgrades should be OK)
[17:34:11]
<Aleks (he/him/il/lui)> (meaning a revert is fine since a revert is a new commit, but a push --force after to reset / completely delete the commit is probably "eh")
[17:34:12]
<tituspijean[m]> I'm making a PR, so there will definitely be a new commit :)
[17:55:23]
<Cippr> Hello,
A modest contribution to review, nothing urgent :-)
https://github.com/YunoHost-Apps/rspamd_ynh/pull/24
[18:09:36]
<Cippr> Aleks (he/him/il/lui): Thanks !
[18:37:21]
<rodinux> Soo.. I ask for the link broken about builds images for new release 5.2.0 of mobilizon, they could fix it, but the link for the release before 5.1.5 is no more here also... 😨
[18:46:37]
<rodinux> oooh it comes back now, sorry for the noise...
[19:16:08]
<rodinux> Ok I realize they changed the link for the sources before it was `https://packages.joinmobilizon.org/` and now `https://packages.mobilizon.org/` they cut the `join` 🤯
[19:23:57]
<rodinux> In such case, could I edit the sources on a new version but also edit it on the master branch ? for in case an upgrade brakes the sources are correct ??
[19:27:39]
<rodinux> Humpff so all old releases can't be restored !! nice...
[19:27:46]
<Aleks (he/him/il/lui)> yeah ...
[19:28:29]
<Aleks (he/him/il/lui)> or does it ? supposedly during restore it doesn't need to re-fetch sources
[19:28:43]
<Aleks (he/him/il/lui)> (maybe?)
[19:31:27]
<rodinux> yes it does, I have try on a dev instance `5.1.5.ynh1` just upgrade to `5.1.5~ynh3` and the restore backup try fetch the source and brakes...
[19:32:41]
<rodinux> https://github.com/YunoHost-Apps/mobilizon_ynh/blob/c82f6d599109453c27b6d378f7e6e1d5c1a22410/scripts/upgrade#L76C1-L76C63
[19:40:14]
<rodinux> Ok, I have prepare a `5.1.5~ynh4` with the correct links in testing... I was thinking on editing master branch but it is stupid, if it brakes the restore will look for the backup package, not the git repository... I am right ?
[19:46:27]
<rodinux> Well I gonna merge it... hope there will be no desaster...
[19:52:31]
<rodinux> So, tipycally, in this repo the master branch is not protected... could you tell me the rules I need aplly... I need protect the master branch, isn't ?
[19:53:37]
<rodinux> They said add ruleset name ?
[19:54:57]
<rodinux> https://aria.im/_bifrost/v1/media/download/AfyjX-w2Yk2w002PG7aoKgKyxqtpZhLmIOdQ-W3m2zFLfB9qd5zzfs-4tehDuriJv50YirLnFq729YRdKKBQLr1CeaeaK0hAAG1hdHJpeC5vcmcveWNuRmNUamdTTklqRVppTndjQ3VwUlBE
[20:00:28]
<orhtej2> add ruleset protecting default branch and by pattern `testing`, restrict deletions, require PR (0 approvers), allow maintainers and org admins to bypass
[20:00:44]
<orhtej2> name can be whatever, including the word `whatever`
[20:01:19]
<orhtej2> (if you fail to allow org admins to bypass you'll break README hook)
[20:03:27]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T pushed to testing: Fix config panel ([511cedf2](https://github.com/YunoHost-Apps/synapse_ynh/commit/511cedf2895fecff97b78c77c1c8cec49fd9c2c0))
[20:07:13]
<rodinux> https://aria.im/_bifrost/v1/media/download/ARD3MF0bg-tP74EXih1XcdE-QM2Sp2mO5zpPbAYp2On6EXJH-st6sIjq01-l16W7ODr69RiqkT5lViYRHRrOAz1Ceaea3wewAG1hdHJpeC5vcmcvZXpGWmdzQWZMbnJrVkVWcUZWZElqeElP
[20:07:15]
<rodinux> Is it ok like this ?
[20:07:46]
<orhtej2> Change status to `Enabled`, the UI is trash for some reason
[20:08:11]
<orhtej2> enforce on default branch as well (there's an option like that in the dropdown)
[20:09:07]
<orhtej2> other than that looks like what I always use and accidentally bypass :P
[20:10:52]
<rodinux> Is it in `Add target` => `Include default branch` ?
[20:12:17]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3194](https://github.com/YunoHost/apps/pull/3194): Add Akkoma to wishlist
[20:14:36]
<rodinux> https://aria.im/_bifrost/v1/media/download/AYCeUnXyni7F_uoakOxqcvUAamOzZ7kJVriXXO48AH0-86yuXMUwAfn8EW-0vxVcOHvzVm23oSXqGsg2KGYT0axCeaebSyngAG1hdHJpeC5vcmcvQXJ4bGd2dWZEa0hiYml0ekdoWFlrbldo
[20:14:47]
<rodinux> seems this ?
[20:15:26]
<orhtej2> > <@rodinux:matrix.org> Capture d’écran du 2025-11-11 21-14-14.png
Lgtm
[20:15:43]
<orhtej2> You can always adjust as needed
[20:15:56]
<rodinux> I let the `Block forces pushed` ?
[20:16:10]
<orhtej2> create dummy pr, comment `!bump`, see if bot responds
[20:17:14]
<orhtej2> > <@rodinux:matrix.org> I let the `Block forces pushed` ?
Imo yes, these can be nasty
[20:20:31]
<rodinux> ok, something seems wrong, tryng a PR with testing said there are identical, it's wrong ??
[20:21:15]
<orhtej2> > <@rodinux:matrix.org> ok, something seems wrong, tryng a PR with testing said there are identical, it's wrong ??
master is up to date, edit a random file, test, then drop the pr
[20:21:33]
<rodinux> oh sorry, it's right, they have been merged...
[20:23:41]
<orhtej2> > <@rodinux:matrix.org> oh sorry, it's right, they have been merged...
Works: https://github.com/YunoHost-Apps/mobilizon_ynh/pull/224
[20:24:05]
<orhtej2> and it suggested pr ratherthan roflstomping testing by default
[20:24:39]
<rodinux> Ok nice 👍️
[20:41:20]
<rodinux> https://aria.im/_bifrost/v1/media/download/ATwkmioKuz5Xa8vxTT3nejJvBAHTOsq2F0888WFadxqDsNX04U9X-TY-WhkkIXdN_54EoWmMvqveZw2WAsOiz1RCeaec0rzAAG1hdHJpeC5vcmcvc3F4Y3ZTaHZSVHlyYVZFTHZsUXBCaGlW
[20:41:39]
<rodinux> well I think we gonna stop with this app... discussing on the matrix room they say me this...
[21:31:03]
<orhtej2> do you want to go synapse_ynh route or just drop `arm` support?
[21:33:06]
<orhtej2> arm64 is rbpi 3+
[21:36:18]
<rodinux> sorry, I don't understand... for now I have remove arm on a branch tests for mobilizon version 5.2.0. now the developpers told they will stop building sources images, so mobilizon will works only with docker if I have well understood ??
[21:37:23]
<orhtej2> you can build whatever's needed yourself
[21:37:58]
<orhtej2> cf https://github.com/YunoHost-Apps/synapse_python_build
[21:38:47]
<rodinux> yes it could be the alternative perhaps... now it is strange this app using elexir...
[21:39:07]
<orhtej2> how's that strange?
[21:39:32]
<orhtej2> I mean not the technology I'm familiar with but a technology nevertheless 🤷
[23:17:23]
<Yunohost Git/Infra notifications> [penpot_ynh] yunohost-bot opened [pull request #162](https://github.com/YunoHost-Apps/penpot_ynh/pull/162): Upgrade to v2.11.0
[23:25:27]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 30 pending update PRs
- 13 new apps PRs: bookstack, dagu, filebrowser, filerise, jackett, kimai2, n8n, penpot, rallly, retroarch, teampass, trilium, zwiicms
- 9 failed apps updates: element-call, fusion, headscale, jenkins, lidarr, litechat, loops, piped, sabnzbd
See the full log here: https://paste.yunohost.org/raw/efuferitud
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate
[23:47:21]
<Yunohost Git/Infra notifications> [apps] alexAubin [commented](https://github.com/YunoHost/apps/pull/3194#issuecomment-3519223576) on [issue #3194](https://github.com/YunoHost/apps/pull/3194) Add Akkoma to wishlist: Same situation as https://github.com/YunoHost/apps/pull/3185 , the app is flagged as "notworking" ... https://github.com...