[13:29:45]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar pushed 1 commit to testing: Update manifest.toml ([5ab42633](https://github.com/YunoHost-Apps/vaultwarden_ynh/commit/5ab426337d07fda807606232126524ed2dff4a92))
[13:29:55]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar opened [pull request #285](https://github.com/YunoHost-Apps/vaultwarden_ynh/pull/285): Testing
[13:41:27]
<@chrichri:ween.de> CI does not support 12.x, yet? https://ci-apps-bullseye-dev.yunohost.org/ci/job/22174
[13:45:11]
<tituspijean> @chrichri:ween.dewrong website :) https://ci-apps-dev.yunohost.org/ci/job/6327
[13:45:54]
<tituspijean> (the bot still posts tests for both bullseye and bookworm)
[13:47:44]
<@chrichri:ween.de> ```
788 ERROR This app requires YunoHost >= 12.0.10 but current installed version is 12.0.9.2
Error: Installation failed.
Peak RAM usage during this test: 32MB
RAM usage diff after test: 6MB
Disk usage diff after test: 50.9MB
--- FAIL ---
Info: This log is now available via https://paste.yunohost.org/raw/akigawotuv
Working time for this test: 28 seconds (13:32:28 UTC)
============================================
[Test 3/6] Multi-instance installations
============================================
Error: All installs failed, therefore the following tests cannot be performed...
--- FAIL ---
```
but it seems it only tested bullseye and then gave up...
[13:52:48]
<Salamandar> > <@chrichri:ween.de> ```
> 788 ERROR This app requires YunoHost >= 12.0.10 but current installed version is 12.0.9.2
> Error: Installation failed.
> Peak RAM usage during this test: 32MB
> RAM usage diff after test: 6MB
> Disk usage diff after test: 50.9MB
>
> --- FAIL ---
>
> Info: This log is now available via https://paste.yunohost.org/raw/akigawotuv
> Working time for this test: 28 seconds (13:32:28 UTC)
>
> ============================================
> [Test 3/6] Multi-instance installations
> ============================================
>
> Error: All installs failed, therefore the following tests cannot be performed...
>
> --- FAIL ---
> ```
> but it seems it only tested bullseye and then gave up...
> current installed version is 12.0.9.2
The CI might be a little out of date
[14:14:20]
<@chrichri:ween.de> O.k. - thanks - I thought I could have missed some changes like e.g. `!testme v12`or something like that...
[14:17:44]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar merged [pull request #285](https://github.com/YunoHost-Apps/vaultwarden_ynh/pull/285): Testing
[15:54:18]
<m606> > <@miro5001:matrix.org> Use DISCLAIMER.md file like here https://github.com/YunoHost-Apps/homer_ynh/blob/5a0f900f49f68aa860a76cb0500831c93598b465/doc/DISCLAIMER.md?plain=1#L1
I can't find track of DISCLAIMER.md in [the doc](https://doc.yunohost.org/en/packaging_app_doc). It is displayed only in the README and not in the catalog/installation process (which I'd like to avoid) ?
[17:54:59]
<miro5001> I've never used it but there is a wiki in the github repos
[17:56:17]
<miro5001> You can make the needed pages there and add a link at the bottom of the readme "for contributers"
[17:56:37]
<m606> > <@m606:matrix.org> I can't find track of DISCLAIMER.md in [the doc](https://doc.yunohost.org/en/packaging_app_doc). It is displayed only in the README and not in the catalog/installation process (which I'd like to avoid) ?
(BTW no app using disclaimer.md seems to be included in app catalog - https://github.com/search?q=org%3AYunoHost-Apps+path%3Adisclaimer.md&type=code)
[17:58:00]
<m606> > <@miro5001:matrix.org> You can make the needed pages there and add a link at the bottom of the readme "for contributers"
That's a good idea
[18:11:01]
<Aleks (he/him/il/lui)> DISCLAIMER.md is legacy stuff which was introduce in late packaging v1
[18:11:02]
<Aleks (he/him/il/lui)> and got replaced by DESCRIPTION.md, PRE_INSTALL.md and ADMIN.md
[18:19:46]
<m606> would a PR adding a condition [there](https://github.com/YunoHost/apps_tools/blob/0b1977c764f693522aabc12b7d1e5126d5ce4218/autoupdate_app_sources/autoupdate_app_sources.py#L238 ) to check whether a file named `app_ynh/.github/PULL_REQUEST_TEMPLATE_AUTOUPDATE.md` exists and if so append it to `commit_msg` be considered in order to allow customization of yunobot PR's body content ?
[18:20:55]
<Aleks (he/him/il/lui)> uuuh maybe but what's the use case you're thinking of ?
[18:22:46]
<m606> > <@m606:matrix.org> Hello, I wonder - where would be the good place to add notes on specific tricks for a specific package for future maintenance (be it done by me who forget stuffs everytime, or potential other maintainer)?
the one linked here
[18:24:46]
<m606> basically remind of all steps for for an app which systematically requires more steps than just merging autoupdate PR to master
[18:26:15]
<Aleks (he/him/il/lui)> hmmmokay sounds legit but can you be a bit more specific like which app and specific step are you thinking about ? 😬
[18:28:50]
<m606> jsoncrack_ynh
here are the instructions I've drafted so far to give you the full context
```
### Note related to JSON Crack package's maintenance
This package is compiled using Github infrastructure in order to remove most of the antifeatures from upstream app (ad for premium version, Google Analytics support, file size limitations) in accordance with its free license for personnal use.
**That makes the package different to update from maintainer's perspective than other packages**. Indeed, before merging any autoupdater PR by yunobot to master branch, note that Yunnorunner's greenlight is meaningless before you do the following:
1. Check upstream commits diff and make sure `/scripts/build` is still up to date. If this is not the case or if you don't know, you'll have to test the current build (cf. step 2) or create a version for testing purposes (cf. `ynh-build-on-push-to-testing.yml` workflow) to know whether something has to be changed.
2. Check the Actions tab - a build action should be successful. If not, you will have to investigate what was broken in the build script or in Github workflow file and fix it. You can then build it the app on demand by enabling the workflow `ynh-build-on-push-to-testing.yml` and pushing a change to the `testing` branch.
3. Check [Release section](https://github.com/YunoHost-Apps/jsoncrack_ynh/releases) - a new release should be created with the built app archive attached. If it looks fine, give appropriate date tag and title to the release and publish it as the latest release. If not, you will have to create the release and/or attach the correct new archive manually.
4. Check the PR created by the autoupdater, a commit to update `manifest.toml` (`url` and `sha256` at `[resources.sources.ynh_build]`) should have been generated. If not, save the link to the new release's archive, download the latter, compute its SHA256 sum and udpate manually the manifest with those values.
Then only you can test the PR with Yunorunner (`!testme`), and eventually merge it to `master` branch on success.
```
I'd put them in a shorter way as steps in autoupdate PR, and link to a wiki entry giving the full detail above for instance.
[18:30:18]
<m606> Note that this method could actually be adopted by more apps (I'll see to it after it is fully debugged with this app), in particular NPM apps that could be built by Github Infra.
[18:30:54]
<Aleks (he/him/il/lui)> sounds legit but i wouln't place that stuff in `.github/PULL_REQUEST_TEMPLATE_AUTOUPDATE.md` because it doesnt really have any relation to github itself and more to yunohost's autoupdater which is somewhat forge-agnostic, maybe we could have something like eeeeh MAINTENANCE.md at the root of the repo ? idk
[18:31:25]
<Aleks (he/him/il/lui)> ah the relation to github is the workflow i suppose
[18:31:41]
<Aleks (he/him/il/lui)> but in a general sense that's specific to this app
[18:33:49]
<m606> yes, ok, MAINTENANCE.md sounds fine to me. In root folder ? In `/doc` ? (although not exactly doc - doc would be the link to the wiki instructions, or what could be added to README.md)
[18:35:09]
<Aleks (he/him/il/lui)> i'd say in the root folder (maybe doc would be a better place idk, but right now any .md file in doc/ not named PRE/POST\_INSTALL/UGRADE will be understood as "another piece of admin documentation similar to ADMIN.md" which is kind of an underused feature but anyway that would be confusing for admin to see packaging-related info in there)
[18:35:29]
<m606> > <@Alekswag:matrix.org> i'd say in the root folder (maybe doc would be a better place idk, but right now any .md file in doc/ not named PRE/POST\_INSTALL/UGRADE will be understood as "another piece of admin documentation similar to ADMIN.md" which is kind of an underused feature but anyway that would be confusing for admin to see packaging-related info in there)
I agree, this I wanted to avoid
[18:48:33]
<m606> thinking twice about it - MAINTENANCE.md or AUTOUPDATE.md (since it will serve only autoupdate purpose in the implementation in autoupdater.py I was considering)?
[18:50:02]
<wgrav> So I'm trying to transfer my app to the YunoHost-Apps organization but GitHub says I don't have permission to create repos there, how do I get access?
[18:52:44]
<m606> > <@wgrav:matrix.org> So I'm trying to transfer my app to the YunoHost-Apps organization but GitHub says I don't have permission to create repos there, how do I get access?
Hello, I believe you can link to your package here and an admin will check it and come to you to grant your account with appropriate permissions to Yunohost-Apps organization
[18:53:52]
<wgrav> Then in that case here's my package:
https://github.com/WGrav01/esphome_ynh
[19:03:14]
<Yunohost Git/Infra notifications> [freshrss_ynh] lapineige pushed 1 commit to master: fixed greader.php path (#196) + fix hooks php version (#199) (#200) * fixed greader.php path (#196) * Update upgrade ... ([89eba515](https://github.com/YunoHost-Apps/freshrss_ynh/commit/89eba515ccb96f1602b8332af483daf20654e3bf))
[19:03:14]
<Yunohost Git/Infra notifications> [freshrss_ynh] lapineige merged [pull request #200](https://github.com/YunoHost-Apps/freshrss_ynh/pull/200): fixed greader.php path (#196) + fix hooks php version (#199)
[19:52:53]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar created new branch cleaning
[19:53:02]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar pushed 1 commit to cleaning: cleaning ([4aac200f](https://github.com/YunoHost-Apps/freshrss_ynh/commit/4aac200f9e0bed2e7a2ec9901fda5ff883517d41))
[20:02:14]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar closed [issue #198](https://github.com/YunoHost-Apps/freshrss_ynh/issues/198): The Yunohost webadmin page for the FreshRSS app gives you a wrong URL to put in the client app
[20:02:15]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar [commented](https://github.com/YunoHost-Apps/freshrss_ynh/issues/198#issuecomment-2631952071) on [issue #198](https://github.com/YunoHost-Apps/freshrss_ynh/issues/198) The Yunohost webadmin page for the FreshRSS app gives you a wrong URL to put in the client app: fixed with #199
[20:02:31]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar closed [issue #193](https://github.com/YunoHost-Apps/freshrss_ynh/issues/193): Failed requirements while upgrading to 1.24.3 ynh1
[20:08:19]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar pushed 1 commit to cleaning: cleaning ([756a0fff](https://github.com/YunoHost-Apps/freshrss_ynh/commit/756a0fffe3901817b482bc6e39aeee2fd34bd2cd))
[20:11:45]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar pushed 1 commit to cleaning: Revert "cleaning" This reverts commit 756a0fffe3901817b482bc6e39aeee2fd34bd2cd. ([b7bc0415](https://github.com/YunoHost-Apps/freshrss_ynh/commit/b7bc04157bc8aa0369e5a977f2666fce70bc9ce2))
[20:17:12]
<Yunohost Git/Infra notifications> [freshrss_ynh] ericgaspar pushed 1 commit to testing: Update manifest.toml ([e0734fb2](https://github.com/YunoHost-Apps/freshrss_ynh/commit/e0734fb211cacd601b83648334dbb6d505e73f8d))
[21:29:03]
<Yunohost Git/Infra notifications> [synapse_ynh] der-bender opened [issue #513](https://github.com/YunoHost-Apps/synapse_ynh/issues/513): Update failed
[21:29:44]
<Yunohost Git/Infra notifications> [synapse_ynh] der-bender edited [issue #513](https://github.com/YunoHost-Apps/synapse_ynh/issues/513): Update failed
[21:51:52]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #2797](https://github.com/YunoHost/apps/pull/2797): Add Inboxen to wishlist
[21:51:54]
<Yunohost Git/Infra notifications> [apps] yunohost-bot labeled Wishlist on [pull request #2797](https://github.com/YunoHost/apps/pull/2797): Add Inboxen to wishlist
[21:52:53]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T [commented](https://github.com/YunoHost-Apps/synapse_ynh/issues/513#issuecomment-2632163925) on [issue #513](https://github.com/YunoHost-Apps/synapse_ynh/issues/513) Update failed: Hello,
2025-02-03 15:36:40,181: DEBUG - + mv -t /home/yunohost.app/synapse /home/yunohost.app/matrix-synapse/media
...
[22:02:25]
<Yunohost Git/Infra notifications> [synapse_ynh] der-bender [commented](https://github.com/YunoHost-Apps/synapse_ynh/issues/513#issuecomment-2632203850) on [issue #513](https://github.com/YunoHost-Apps/synapse_ynh/issues/513) Update failed: No, I changed nothing - well, that may be half the truth: Couldnt install synapse at first and thus opened #511, but I ...
[23:24:44]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 20 pending update PRs
- 9 new apps PRs
- 8 failed apps updates: appflowy, benevalibre, elabftw, gitlab-runner, lemmy, owncast, stremio, zoraxy
See the full log here: https://paste.yunohost.org/raw/ecikixolip