[04:01:11]
<zanovis> What's the suggested method to grant access to syncthing to sync data with other services on the YNH server? Should we edit the permissions of the syncthing usergroup?
[07:35:41]
<Daniel> I have trouble with configuring email in ynh,
I logged in to my account using K9 and I try to send an email to myself:
Using me@example.com I try to send an email to me@example.com
(Ofc me@example.com is an example)
I get "Temporary lookup failure" error
In my diagnostic tools (aside of being blacklisted by 2 spam filters - I plan to resolve it after getting everything up) the only email-related problem is that my reverse dns on ipv4 is not set properly.
(The ipv4 problem is kinda weird, because I set my ipv4 public reverse dns to example.com and ynh diagnostic still sees the default linode setting (I use linode) - is it cached somewhere? The ipv6 works fine)
[07:38:06]
<lautre> DNS are cached.
See the time remaining for TTL with a DNS request like:
dig a example.com
[07:39:31]
<lautre> You should try to reach your server mail too, with ping or whatever.
If DNS are wrong, temporary set values in your /etc/hosts
[07:40:04]
<lautre> If you make testing, may be you should reduce TTL.
[07:58:58]
<Daniel> I rebooted it once again and it magically works (ipv4 part) - I set the rdns yesterday and it required another restart to work.
Email has the same issue.
In diagnostic panel I get info there are 100+ pending emails.
I am looking for some commandline tools to do local diagnostic, but I am not sure what ynh uses for email service.
[08:04:23]
<Daniel> ... actually I have to check if my domain provider is not forcing it's email-related dns on top of mine
[08:39:41]
<Daniel> Debugged postfix, the yunohost forum thread about the fix is a french wall of text, yay! (yea, my french ends on "comment ca va" 😅)
[08:44:48]
<Daniel> Problem solved, removing emailpouble solved the issue.
Now my problem is that I want a selfhosted tempmail service.
[10:32:28]
<Daniel> Forgot to link the forum thread
https://forum.yunohost.org/t/how-to-add-custom-dns-records-to-autodns-function/23494
[10:32:56]
<Daniel> Aleks (he/him/il/lui): (I assume you are the Aleks with cat avatar on the forum)
I suggest changing the 2nd echo to echo into ynh_stdreturn, because current echo into ynh_return doesn't work.
https://forum.yunohost.org/t/how-to-add-custom-dns-records-to-autodns-function/23494
[11:38:15]
<orhtej2> > <@danielduel:dduel.dev> Aleks (he/him/il/lui): (I assume you are the Aleks with cat avatar on the forum)
>
> I suggest changing the 2nd echo to echo into ynh_stdreturn, because current echo into ynh_return doesn't work.
>
> https://forum.yunohost.org/t/how-to-add-custom-dns-records-to-autodns-function/23494
the world is your oyster, this FOSS project is yours to patch ;) https://github.com/YunoHost/yunohost/blob/5110cd0800faf8f406fe1bc69cb91199f2674a20/helpers/logging#L326
[11:38:15]
<orhtej2> (although I'm not sure what bug are you running into and how you suggest to fix it)
[11:43:15]
<orhtej2> > <@danielduel:dduel.dev> Nonono maybe the edit didn't work out, I am talking about Aleks'es forum answer https://forum.yunohost.org/t/how-to-add-custom-dns-records-to-autodns-function/23494
> He did a small code snippet there and it wasn't clear why it doesn't work for a ynh newbie like me... and editing autodns is important if you are a dev and you have to cname your subdomains to places like vercel
ahh, don't mind me then ;)
[11:44:35]
<Daniel> > <@Alekswag:matrix.org> (still not clear to me why the proposed answer doesnt work)
YNH_RETURN doesn't exist, YNH_STDRETURN does.
[11:44:35]
<Daniel> orhtej2: ^
[11:44:35]
<Daniel> Nonono maybe the edit didn't work out, I am talking about Aleks'es forum answer https://forum.yunohost.org/t/how-to-add-custom-dns-records-to-autodns-function/23494
He did a small code snippet there and it wasn't clear why it doesn't work for a ynh newbie like me... and editing autodns is important if you are a dev and you have to cname your subdomains to places like vercel
[11:44:36]
<Aleks (he/him/il/lui)> well let me edit the post then 👍️
[11:44:38]
<Aleks (he/him/il/lui)> (still not clear to me why the proposed answer doesnt work)
[11:44:40]
<Daniel> 💛
[11:44:41]
<Aleks (he/him/il/lui)> i was confused because the end of the second line was cropped because it's too long etc
[11:44:46]
<Aleks (he/him/il/lui)> anyway thanks for the feedback
[11:44:52]
<Aleks (he/him/il/lui)> fixed
[11:44:55]
<Aleks (he/him/il/lui)> I was confused because you were mentionning `ynh_return` as it if was some function
[11:44:58]
<Aleks (he/him/il/lui)> ah :D
[11:45:01]
<Aleks (he/him/il/lui)> ah it's a typo on the second line, i see
[12:29:09]
<orhtej2> is it something on my end or YNH policy that I can `sudo -i` no problem but `sudo -u user command` refuses as I'm not entitled?
[12:30:56]
<Aleks (he/him/il/lui)> probably depends on which user you run it from
[12:31:23]
<orhtej2> > <@Alekswag:matrix.org> probably depends on which user you run it from
the one that's entitled to `sudo -i`, I can switch to root then run `sudo -u` no problem
[12:31:55]
<Aleks (he/him/il/lui)> yeah the sudo config probably allows to become root, but not another user, even though from root you can effectively become another user
[12:32:11]
<Aleks (he/him/il/lui)> doesnt seem related to ynh, that's what i would expect from sudo anywhere
[12:58:48]
<Daniel> > is it something on my end or YNH policy that I can `sudo -i` no problem but `sudo -u user command` refuses as I'm not entitled?
$ sudo su
# su user
[12:59:18]
<orhtej2> > <@danielduel:dduel.dev> $ sudo su
> # su user
I understand there's a workaround, I just don't understand why I need to jump the hoops :P
[13:00:00]
<Daniel> Oh I see, thought you want to f.e. get into postgre user
[13:02:53]
<Matt Brand> Is Trillium Notes broken for anyone else? My Trilium service fails to run, Says it was compiled against a different nodejs version using version 93, this version of nodejs requires version 108. For the life of me I can't figure out how to fix the issue.
[13:06:08]
<orhtej2> > <@itsc:matrix.org> Is Trillium Notes broken for anyone else? My Trilium service fails to run, Says it was compiled against a different nodejs version using version 93, this version of nodejs requires version 108. For the life of me I can't figure out how to fix the issue.
it worked and now is broken or this is fresh install? Did you upgrade prior to the app breaking?
[13:06:22]
<orhtej2> also what arch
[13:10:05]
<Matt Brand> It broke after an update. I've been looking into how to rebuild. YunoHost version: 11.2.4, Trilium Notes 0.60.4 on a debian VPS
[13:12:58]
<Daniel> (I see, they've downgraded the node from 20 to 18)
[13:13:15]
<orhtej2> > <@itsc:matrix.org> It broke after an update. I've been looking into how to rebuild. YunoHost version: 11.2.4, Trilium Notes 0.60.4 on a debian VPS
copy the pre-upgrade backup (or restore it) to get back to working state I guess, then make proper backup from the UI, then nuke install dir and force-upgrade I guess
[13:17:40]
<bob> I just want to say thank you to the team behind yunohost it's an awesome project, it works great out of the box, it's an amazing useful set of tools and a great learning experience!
[13:18:46]
<Daniel> Matt B thrand
I would suggest doing backup first, but:
If you feel particularly lucky...
You can go into /var/www/trilium switch node to 18 and running `npm i` there which will rebuild that dependency with current version
[13:19:22]
<Daniel> (I really love that my newlines are ignored here xD)
[13:21:23]
<orhtej2> > <@danielduel:dduel.dev> (I really love that my newlines are ignored here xD)
use MD syntax, use 2xnewline
like so
[13:25:01]
<Matt Brand> deleted the app, recovered with a pre-update backup. then will backup via app gui. Then will update again see if it breaks, if so I'll try the manual switch to node 18
[13:35:57]
<orhtej2> > <@itsc:matrix.org> deleted the app, recovered with a pre-update backup. then will backup via app gui. Then will update again see if it breaks, if so I'll try the manual switch to node 18
you'll need to upgrade from command line with `--force`, otherwise it'll just exit
[13:36:18]
<orhtej2> also-also consider deleting `/var/www/trilium/node_modules` to force rebuild
[13:36:30]
<orhtej2> ofc **AFTER THE BACKUP**
[17:43:37]
<marcus> At this rate https://github.com/YunoHost/issues/issues/2050 , when yunohost is compatible with Debian 12, it will already be the arrival of Debian 13!
As far as I can remember, yunohost has never taken so long to switch from one version of Debian to another 😕
[17:47:13]
<Aleks (he/him/il/lui)> Did you forget to read the first line of the thread ?
[17:50:01]
<tituspijean> Dear marcus, I encourage you to read about our past interactions on Github with the users Neustradamus and collector-ynh.
This kind of comments never ends well for the commenter, adds nothing contribution-wise, and only infuriates people who actually work on YunoHost.
There is a nice to-do list in there. If you are not willing to help, I will kindly ask you to STFU. :)
[17:52:01]
<tituspijean> And dont forget our general guideline on the matter: https://yunohost.org/en/community/faq#when-will-this-feature-be
[17:52:15]
<marcus> > <@titus:pijean.ovh> Dear marcus, I encourage you to read about our past interactions on Github with the users Neustradamus and collector-ynh.
> This kind of comments never ends well for the commenter, adds nothing contribution-wise, and only infuriates people who actually work on YunoHost.
>
> There is a nice to-do list in there. If you are not willing to help, I will kindly ask you to STFU. :)
It was just a simple remark on the state of the yunohost tool, my remark does not concern the developers. So there’s no point in getting offended!
[17:55:09]
<marcus> My observation is to say that given the current progress of yunohost's compatibility with Debian 12, and the integration of a transition from Debian 11 to Debian 12, yunohost risks being compatible with Debian 12 when the version is released. stable of Debian 13...
[17:57:27]
<Aleks (he/him/il/lui)> Your message did not contain anything constructive about Bookworm support, and you did not even care to read the first line of the very thread you are mentionning.
This was your last message containing that tone of "hurr durr herp derp this free software project that maintains hundred of packages is not up to date with something that got released 3 months ago", next message today or in months with that kind of tone from your part - or arguing about it supposedly not being "offensive" - will result in a ban, we have other things to do in our life that deal with users with that kind of shitty attitude, thank you
[17:58:52]
<isAAAc> > <@marcus78:matrix.org> My observation is to say that given the current progress of yunohost's compatibility with Debian 12, and the integration of a transition from Debian 11 to Debian 12, yunohost risks being compatible with Debian 12 when the version is released. stable of Debian 13...
It's better that it happens a little late and works than too early and ruins everything. What's your problem with yunohost not being compatible with debian12 yet?
[17:59:20]
<Aleks (he/him/il/lui)> That discussion is closed
[18:03:25]
<marcus> > <@Alekswag:matrix.org> Your message did not contain anything constructive about Bookworm support, and you did not even care to read the first line of the very thread you are mentionning.
>
> This was your last message containing that tone of "hurr durr herp derp this free software project that maintains hundred of packages is not up to date with something that got released 3 months ago", next message today or in months with that kind of tone from your part - or arguing about it supposedly not being "offensive" - will result in a ban, we have other things to do in our life that deal with users with that kind of shitty attitude, thank you
I read the first line of the thread carefully before giving my estimate here!
The first line of the thread concerned questions about the release date or other recurncies cited in the GitHUB thread. I did not in any way ask for the compatibility date, but I contributed by giving an estimate of when compatibility will end myself. You can take it into account or not, it's your business. But my comment didn't include any questions...
[18:05:36]
<Aleks (he/him/il/lui)> Well congratz for being unable to hide that you're collectroll bro
[20:45:58]
<lapineige> SealioningAsAService.people
[20:47:34]
<Aleks (he/him/il/lui)> nice, didn't know about that
[20:48:19]
<Aleks (he/him/il/lui)> https://fr.wikipedia.org/wiki/Sealioning
[20:49:02]
<lapineige> that's a very tricky and effective way to drain a lot of energy for no interresting outcome (on purpose or not).
[20:49:19]
<Aleks (he/him/il/lui)> sounds like the perfect description of our dear friend