#archlinux32 | Logs for 2019-06-11

[00:31:58] -!- thePiGrepper has quit [Ping timeout: 246 seconds]
[02:38:25] -!- thePiGrepper has joined #archlinux32
[04:51:28] -!- quequotion has joined #archlinux32
[04:57:37] -!- thePiGrepper has quit [Ping timeout: 246 seconds]
[05:07:32] -!- thePiGrepper has joined #archlinux32
[05:24:14] -!- DCyrax has quit [Read error: Connection reset by peer]
[05:25:40] -!- isacdaavid has joined #archlinux32
[06:05:58] -!- eschwartz has joined #archlinux32
[06:10:40] -!- thePiGrepper has quit [Ping timeout: 248 seconds]
[07:03:10] -!- thePiGrepper has joined #archlinux32
[08:48:33] -!- quequotion has quit [Quit: quequotion]
[08:56:25] -!- buildmaster has quit [Remote host closed the connection]
[08:57:01] -!- buildmaster has joined #archlinux32
[08:57:05] <buildmaster> !rq buildmaster
[08:57:05] <phrik> buildmaster: <buildmaster> I might be insane, but never confused ... ;-)
[09:38:35] -!- bill-auger has quit [Ping timeout: 248 seconds]
[09:38:56] -!- bill-auger has joined #archlinux32
[11:08:16] -!- thePiGrepper has quit [Ping timeout: 246 seconds]
[11:30:55] -!- abaumann has joined #archlinux32
[11:30:55] <buildmaster> Hi abaumann!
[11:30:55] <buildmaster> !rq abaumann
[11:30:56] <phrik> buildmaster: <abaumann> canary no. 2 is back on testing. :-)
[11:33:03] -!- quequotion has joined #archlinux32
[12:47:52] -!- isacdaavid has quit [Ping timeout: 272 seconds]
[13:00:25] -!- quequotion has quit [Quit: quequotion]
[13:25:56] -!- abaumann has quit [Quit: leaving]
[14:52:55] -!- eschwartz has quit [Quit: A random quit message]
[15:20:26] -!- quequotion has joined #archlinux32
[15:41:20] -!- thePiGrepper has joined #archlinux32
[18:38:59] -!- quequotion has quit [Quit: quequotion]
[18:50:58] -!- ofara_ has quit [Ping timeout: 258 seconds]
[19:04:13] -!- thePiGrepper has quit [Ping timeout: 245 seconds]
[19:23:41] -!- chub has joined #archlinux32
[19:24:22] <chub> hallo, I'm having a problem getting tinc@connection_name working, after a reboot. The service is enabled. I can start it with tinc@service_name and it works, but not after a reboot. Any ideas?
[19:29:21] -!- abaumann has joined #archlinux32
[19:29:21] <buildmaster> Hi abaumann!
[19:29:21] <buildmaster> !rq abaumann
[19:29:22] <phrik> buildmaster: <abaumann> yeah. real servers don't grow on trees. ;-)
[19:29:26] <abaumann> hi chub
[19:29:32] <chub> hi abaumann
[19:29:40] <abaumann> never used tinc, did you check what 'systemctl status tincd' is telling you?
[19:30:10] <chub> abaumann, Unit tincd.service could not be found.
[19:30:34] <chub> however, if I do systemctl status tinc@network_name I get feedback
[19:30:44] <abaumann> I see only a /usr/lib/systemd/system/tinc.service
[19:30:51] <abaumann> no tincd.service
[19:31:06] <chub> active (running), however, it only runs when I manually log on and start it using systemctl start tinc@network_name
[19:31:27] <chub> then the specific network_name service starts
[19:31:45] <abaumann> 'systemctl reenable tinc.service' 'systemctl reenable tinc@network_name.service'
[19:31:55] <chub> let me try that
[19:32:11] <abaumann> though I wonder how this can get lost..
[19:32:17] <abaumann> ..otoh we talk about systemd :->
[19:32:54] <chub> okay I ran those commands
[19:32:59] <chub> I guess the only way now is to reboot
[19:33:05] <abaumann> yeah.
[19:33:21] <chub> alright, rebooting, thanks. will join again to see what happened
[19:33:27] <abaumann> ok
[19:33:40] -!- chub has quit [Quit: Leaving]
[19:34:40] -!- ofara_ has joined #archlinux32
[19:36:16] -!- chub has joined #archlinux32
[19:36:56] <chub> ah yes it is running!
[19:37:01] <abaumann> cool :-)
[19:37:08] <chub> abaumann, thank you for teaching me systemd
[19:37:14] <abaumann> np
[19:37:20] <abaumann> still learning it myself :-)
[19:38:45] <chub> maybe it went broken because of all my power failures?
[19:39:16] <comrumino> Do you all plan on keeping py2 support?
[19:39:47] <abaumann> mmh. systemd writes a symlink of sorts when enabling a service. the fileystem journal should replay it. so, I think it's quite hard to loose it that way.
[19:40:05] <abaumann> comrumino: yeah we might have to.
[19:40:24] <abaumann> but otoh python2 is currently falling apart: less and less tests still work on 32-bit
[19:40:42] <abaumann> as long a upstream (64-bit Archlinux) is not dropping it, we are neither.
[19:41:19] <comrumino> fair enough
[19:41:21] <comrumino> thx
[19:41:27] <abaumann> policies. :-)
[19:41:27] <abaumann> np
[19:45:51] <elibrokeit> And x86_64 is not dropping it either, at least not before the PSF drops it
[19:46:35] <elibrokeit> Possibly not then either, because I for one would keep maintaining it if I needed to for userspace applications.
[19:47:49] <abaumann> https://pythonclock.org
[19:47:51] <abaumann> really..
[19:47:51] <phrik> Title: Python 2.7 Countdown (at pythonclock.org)
[19:48:21] <elibrokeit> I'm aware :/
[19:48:36] <abaumann> That's success, if you have to try so hard to get rid of it. :-)
[19:48:56] <elibrokeit> Ignoring for a moment that PyPy is still fully supported despite targeting the py2 language specification...
[19:49:43] <abaumann> I still use the osc-tools from SuSE, they are Python2, but might now slowly migrate to Python3
[19:50:07] <elibrokeit> And then there is jyrhon and ironpython
[19:50:31] <abaumann> true
[19:50:52] <elibrokeit> It's nice that people want to drop 2.x support in libs, but it's also completely unrealistic :p
[19:50:54] <abaumann> iron(y)python
[19:51:31] <elibrokeit> Then we get to the meat and potatoes of the matter, which is cpython itself
[19:52:05] <elibrokeit> The PSF can drop support all they want, but the stable releases of Red Hat, Debian and Ubuntu all ship python2
[19:52:27] <elibrokeit> So there are some lovely LTS cycles to keep it alive for years :)
[19:52:42] <elibrokeit> I'm sure there will be security fixes...
[19:53:20] <elibrokeit> And working code doesn't stop working just because the authors stop recommending it
[19:54:01] <abaumann> yeah. just digging though some code written in Modula-3.. :-)
[19:54:14] -!- chub has quit [Quit: Leaving]
[19:54:37] <abaumann> I have a cool link concerning RISC-V and bootstrapping: http://selfie.cs.uni-salzburg.at
[19:54:38] <phrik> Title: selfie | An educational software system of a tiny self-compiling C compiler, a tiny self-executing RISC-V emulator, and a tiny self-hosting RISC-V hypervisor. (at selfie.cs.uni-salzburg.at)
[19:54:59] <elibrokeit> Of course it may stop working for other reasons, like being written in qt4 :p
[19:55:27] <abaumann> .. maybe Tk fails too.. :-)
[19:57:21] <elibrokeit> I keep telling myself I need to teach myself C :(
[19:57:46] <abaumann> It's C*, so just a tiny subset of C (just while, if, functions, integers and pointers)
[19:57:47] -!- chub has joined #archlinux32
[19:57:54] <abaumann> no arrays, no structs, ...
[19:58:10] <chub> I think the reason why it didn't work is because I might never have enabled tinc.service to begin with
[19:58:35] <abaumann> chub: good explanation
[20:00:29] <chub> however, according to https://wiki.archlinux.org everything is fine. And I'm not finding anything else. but my service is starting, the nic is up, but the up script didn't run that sets the network configuration. I wonder if I should move that over to /etc/systemd/network
[20:00:30] <phrik> Title: Tinc - ArchWiki (at wiki.archlinux.org)
[20:02:04] <abaumann> no experience here to combine tinc and systemd-network..
[20:10:48] <chub> so .netdev is to create the tun device and .network is to configure it
[20:11:07] <chub> well I guess another reboot, or a million
[20:11:11] <chub> :)
[20:11:14] -!- chub has quit [Quit: Leaving]
[20:23:25] -!- chub has joined #archlinux32
[20:23:40] <chub> well, it turns out, only .network was necessary
[20:24:10] <chub> .netdev broke my bridge for some reason, talk about unplugging keyboards and running around haha
[20:24:11] <chub> oh well
[20:43:24] -!- abaumann has quit [Quit: leaving]
[21:19:07] -!- chub has quit [Quit: Leaving]
[22:21:31] <girls> yay, we have internet again at home!
[22:22:15] <girls> though I need to marry my router with the new cable modem and it looks, like we don't have ipv6 and are sharing port 22, 80 and 443 with other users O.o