Saturday, February 25, 2023
dev@conference.yunohost.org
February
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
         
             

[06:30:15] <Yunohost Git/Infra notifications> [YunoHost documentation] [🔴 Down] Request failed with status code 500
[06:31:17] <Yunohost Git/Infra notifications> [YunoHost documentation] [✅ Up] 200 - OK
[07:04:40] <Bram[m]> Euh, y quelqu'un qui utilise l'instance de demo pour se faire plein de comptes wtf sur des sites de dev libre, c'est normal ?
[09:13:20] <Yunohost Git/Infra notifications> [issues] @eauchat closed [issue #1890](https://github.com/YunoHost/issues/issues/1890): Many dyndns error mails, and resolv.dnsmasq.conf gets modified automatically, due to VPNclient stuff
[09:13:24] <Yunohost Git/Infra notifications> [issues] @eauchat [commented](https://github.com/YunoHost/issues/issues/1890#issuecomment-1445037542) on [issue #1890](https://github.com/YunoHost/issues/issues/1890) Many dyndns error mails, and resolv.dnsmasq.conf gets modified automatically, due to VPNclient stuff: Ok, well the issue hasnt shown up again, so I guess thats fully resolved :) 👍
[12:59:10] <Yunohost Git/Infra notifications> [yunohost-admin] @yunohost-bot opened [pull request #510](https://github.com/YunoHost/yunohost-admin/pull/510): Translations update from Weblate
[13:21:27] <Yunohost Git/Infra notifications> [issues] @zamentur labeled :space_invader: bug on [issue #2162](https://github.com/YunoHost/issues/issues/2162): Trouble with spamhaus marking mail as spam
[13:21:27] <Yunohost Git/Infra notifications> [issues] @zamentur opened [issue #2162](https://github.com/YunoHost/issues/issues/2162): Trouble with spamhaus marking mail as spam
[13:22:28] <Yunohost Git/Infra notifications> [issues] @zamentur edited [issue #2162](https://github.com/YunoHost/issues/issues/2162): Trouble with spamhaus marking mail as spam
[13:32:51] <Yunohost Git/Infra notifications> [issues] @alexAubin [commented](https://github.com/YunoHost/issues/issues/2161#issuecomment-1445121437) on [issue #2161](https://github.com/YunoHost/issues/issues/2161) [manifest v2] data_dir not fully deprovisionned: Yes this is the expected behavior, no we cant really guarantee that the new app will work and pick up the existing file...
[13:33:05] <Yunohost Git/Infra notifications> [issues] @alexAubin closed [issue #2161](https://github.com/YunoHost/issues/issues/2161): [manifest v2] data_dir not fully deprovisionned
[15:02:33] <Yunohost Git/Infra notifications> [yunohost] @alexAubin pushed 1 commit to dev: misc: automatic get rid of /etc/profile.d/check_yunohost_is_installed.sh when yunohost is postinstalled ([20e8805e](https://github.com/YunoHost/yunohost/commit/20e8805e3b60178df804b1acc4714f9d4e754572))
[15:15:20] <Yunohost Git/Infra notifications> 🏗️ Starting build for yunohost/11.1.11.2+202302251515 for bullseye/unstable/all ...
[15:16:40] <Yunohost Git/Infra notifications> ✔️ Completed build for yunohost/11.1.11.2+202302251515 for bullseye/unstable/all.
[15:28:04] <Yunohost Git/Infra notifications> [issues] @eauchat [commented](https://github.com/YunoHost/issues/issues/2143#issuecomment-1445142301) on [issue #2143](https://github.com/YunoHost/issues/issues/2143) Excessive warning on .well-known mail autoconfig for domain: On my side, I noticed the issue because I was trying for the first time to make use of the feature to disable email for ...
[17:57:50] <Yunohost Git/Infra notifications> [issues] @eauchat opened [issue #2163](https://github.com/YunoHost/issues/issues/2163): Old ssh ports not closed after changing ssh port
[17:57:50] <Yunohost Git/Infra notifications> [issues] @eauchat labeled :space_invader: bug on [issue #2163](https://github.com/YunoHost/issues/issues/2163): Old ssh ports not closed after changing ssh port
[17:58:45] <Yunohost Git/Infra notifications> [issues] @eauchat [commented](https://github.com/YunoHost/issues/issues/2163#issuecomment-1445170224) on [issue #2163](https://github.com/YunoHost/issues/issues/2163) Old ssh ports not closed after changing ssh port: As a matter of fact, the port 22 also remains open after those two successive ssh port modifications.
[21:59:33] <Yunohost Git/Infra notifications> [yunohost] @yunohost-bot opened [pull request #1614](https://github.com/YunoHost/yunohost/pull/1614): Translations update from Weblate
[22:27:14] <Yunohost Git/Infra notifications> [issues] @alexAubin [commented](https://github.com/YunoHost/issues/issues/2163#issuecomment-1445218431) on [issue #2163](https://github.com/YunoHost/issues/issues/2163) Old ssh ports not closed after changing ssh port: (Yes port 22 is kept opened, i think the reasoning was that we didnt want people to mistakenly close / change port 22 an...
[22:34:58] <Yunohost Git/Infra notifications> [issues] @eauchat [commented](https://github.com/YunoHost/issues/issues/2163#issuecomment-1445219430) on [issue #2163](https://github.com/YunoHost/issues/issues/2163) Old ssh ports not closed after changing ssh port: Not so sure I understand what you mean. If ssh port is changed you wont be able to connect using port 22, otherwise wha...
[22:46:03] <tituspijean[m]> Small note, while trying to optimize API calls to Github, I discovered that the JSON catalog does not have the key `packaging_format: 2` for apps using the new format.
[23:13:43] <Spok> (the other 4 don't seem to use auto update)