Sunday, March 17, 2024
apps@conference.yunohost.org
March
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
             

[00:23:01] <Yunohost Git/Infra notifications> App collabora rises from level 6 to 8 in job [#24481](https://ci-apps.yunohost.org/ci/job/24481) !
[00:42:20] <Yunohost Git/Infra notifications> App emoncms rises from level 6 to 8 in job [#24482](https://ci-apps.yunohost.org/ci/job/24482) !
[05:11:03] <Yunohost Git/Infra notifications> App simple-file-manager rises from level 6 to 7 in job [#24499](https://ci-apps.yunohost.org/ci/job/24499) !
[05:19:47] <Yunohost Git/Infra notifications> App element-call rises from level 6 to 7 in job [#24498](https://ci-apps.yunohost.org/ci/job/24498) !
[11:03:17] <Yunohost Git/Infra notifications> [wordpress_ynh] @tituspijean [commented](https://github.com/YunoHost-Apps/wordpress_ynh/issues/235#issuecomment-2002409080) on [issue #235](https://github.com/YunoHost-Apps/wordpress_ynh/issues/235) authldap plugin is deprecated: Since the link I provided does not explain at all ***why*** the extension was ever temporarily removed, I investigated a...
[11:03:17] <Yunohost Git/Infra notifications> [wordpress_ynh] @tituspijean closed [issue #235](https://github.com/YunoHost-Apps/wordpress_ynh/issues/235): authldap plugin is deprecated
[11:03:34] <Yunohost Git/Infra notifications> [wordpress_ynh] @tituspijean closed [pull request #236](https://github.com/YunoHost-Apps/wordpress_ynh/pull/236): Replace authldap with wpdirauth
[11:03:36] <Yunohost Git/Infra notifications> [wordpress_ynh] @tituspijean deleted branch ldap
[11:25:49] <Yunohost Git/Infra notifications> App prowlarr rises from level 6 to 8 in job [#24501](https://ci-apps.yunohost.org/ci/job/24501) !
[16:15:56] <anubister> https://yunohost.org/en/packaging_apps_resources#ports -> no way to open a range of ports?
[20:44:14] <Émy - OniriCorpe> > <anubister> https://yunohost.org/en/packaging_apps_resources#ports -> no way to open a range of ports?

why you would do that?
[20:53:45] <Émy - OniriCorpe> ports declared in the manifest should be declared alone, one per declaration, otherwise it would be tricky to use them in the package
```
main.default = 12345 -> "$port"
xmpp_client.default = 5222 -> "$port_xmpp"
```
[20:54:32] <tituspijean> there are some cases where apps might need to open random and multiple UDP ports, I'm thinking torrent ones for example
[20:54:50] <Émy - OniriCorpe> if you're not talking about packaging but server administration, use the yunohost cli for that:
```
yunohost firewall allow --help
usage: yunohost firewall allow {TCP,UDP,Both} port [-h] [-4] [-6] [--no-upnp] [--no-reload]

Allow connections on a port

positional arguments:
{TCP,UDP,Both} Protocol type to allow (TCP/UDP/Both)
port Port or range of ports to open
```
[20:55:40] <Émy - OniriCorpe> > <@titus:pijean.ovh> there are some cases where apps might need to open random and multiple UDP ports, I'm thinking torrent ones for example

that's an edge case and the argument is still valid: "otherwise it would be tricky to use them in the package"
[20:58:51] <Émy - OniriCorpe> we can still use `yunohost firewall allow` in a package with a loop, alongside `yunohost service add "$app" --description="service description" --needs_exposed_ports "$ports"`
note that you should NOT use the second command for UDP ports, because yunohost will report the port as not available on internet on the diagnosis tool
[20:59:06] <Émy - OniriCorpe> we can still use `yunohost firewall allow` in a package with a loop, alongside of `yunohost service add "$app" --description="service description" --needs_exposed_ports "$ports"`
note that you should NOT use the second command for UDP ports, because yunohost will report the port as not available on internet on the diagnosis tool
[21:01:04] <Émy - OniriCorpe> so my question is stil valid, what is the real usage? because it totally influences the answer
[21:52:43] <florent> Hello,
I need to be notified of new versions whose binary are not published on Github. It used to work with the autoupdater Github workflow, but with the manifest v2 I don't know how to do that:
https://github.com/YunoHost-Apps/elasticsearch8_ynh/blob/d557e6d2319a2e286f0db95e61cb5ed660a9d61a/manifest.toml#L36-L40

Can anyone help me?
[21:58:51] <Émy - OniriCorpe> > Hello,
> I need to be notified of new versions whose binary are not published on Github. It used to work with the autoupdater Github workflow, but with the manifest v2 I don't know how to do that:
> https://github.com/YunoHost-Apps/elasticsearch8_ynh/blob/d557e6d2319a2e286f0db95e61cb5ed660a9d61a/manifest.toml#L36-L40
>
> Can anyone help me?

it's because the bot can't found proper assets http://paste.yunohost.org/raw/xizevihuti
[22:00:14] <florent> > <@oniricorpe:im.emelyne.eu> it's because the bot can't found proper assets http://paste.yunohost.org/raw/xizevihuti

I saw that, I just don't know how to fix that
[22:01:10] <Émy - OniriCorpe> you can do something like that
```
autoupdate.asset.arm64 = "tar.gz"
autoupdate.asset.amd64 = "tar.gz"
```

so the bot should take the tar.gz asset attached to the tag, replace the sources links with that and open a PR
[22:01:33] <Émy - OniriCorpe> after that, you have to replace the links with the real sources and their checksum
[22:02:18] <Émy - OniriCorpe> maybe this would help you if it's merged https://github.com/YunoHost/apps/pull/2041
[22:04:56] <Émy - OniriCorpe> i would advise you to use `latest_github_release` instead wof `latest_github_tag`
so the bot will put [the link to the release](https://github.com/elastic/elasticsearch/releases/tag/v8.12.2) with the changelog and download link, and that will simplify your work
[22:06:54] <Émy - OniriCorpe> you can also still use a github workflow, we moved to a centralized auto updater because it's way easier to implement on many packages than GH worflows, but in some cases it's more relevant to use GH workflows
[22:09:38] <Salamandar> > <@oniricorpe:im.emelyne.eu> you can do something like that
> ```
> autoupdate.asset.arm64 = "tar.gz"
> autoupdate.asset.amd64 = "tar.gz"
> ```
>
> so the bot should take the tar.gz asset attached to the tag, replace the sources links with that and open a PR

better to do `".*\\.tar\\.gz$"` to ensure it's the file extension (although there is little chance it matches anything else)
[22:16:18] <Émy - OniriCorpe> > <@Salamandar:matrix.org> better to do `".*\\.tar\\.gz$"` to ensure it's the file extension (although there is little chance it matches anything else)

it's for garbage data tho x)
[22:30:32] <Yunohost Git/Infra notifications> [apps] @fflorent [commented](https://github.com/YunoHost/apps/pull/2041#issuecomment-2002639397) on [issue #2041](https://github.com/YunoHost/apps/pull/2041) Add DownloadPageAPI to the autoupdater to download from HTML web pages: FWIW, I would probably need that for elasticsearch8.
[22:30:42] <florent> Thanks, probably worth to follow your trick
[22:31:05] <florent> > <@oniricorpe:im.emelyne.eu> i would advise you to use `latest_github_release` instead wof `latest_github_tag`
> so the bot will put [the link to the release](https://github.com/elastic/elasticsearch/releases/tag/v8.12.2) with the changelog and download link, and that will simplify your work

Yep, I already changed that in testing
[22:41:47] <Émy - OniriCorpe> note that the bot runs on the main branch, so you should merge testing into master