| mason | plasma41: archive.org is a good source of that kind of thing. | 00:00 |
|---|---|---|
| plasma41 | mason: I don't disagree. The Internet Archive is *awesome*! | 00:01 |
| golinux | We can't have users installing the latest beowulf and NOT going to libera for help | 00:02 |
| mason | A move for the future might be linking to a resources page rather than putting stuff that depends on outside resources in the announcement. | 00:03 |
| golinux | Why make it harder for users to access info? I often won't click to get additional info. Maybe that's just me | 00:04 |
| golinux | The notes here http://files.devuan.org/devuan_beowulf/Release_notes.txt still point to leenode | 00:06 |
| golinux | That's almost more important to correct that the web announcement. | 00:06 |
| jushur | i think its better to refer to resource page by default, and only announce changes in release logs | 00:07 |
| plasma41 | In email I'm generally in favor of including information inline rather than including a link when doing so doesn't substantially increase the length of the message. | 00:07 |
| golinux | jushur: You are welcome to join the documentation project. :) | 00:08 |
| golinux | And how many angels can dance on the head of a pin. Currently anyone referencing our official documentation is being sent to leenode. | 00:09 |
| golinux | Ugh. | 00:10 |
| jushur | well this is me on a good day, stuff can get crazy on a bad one xD | 00:10 |
| golinux | Is anyone keeping track of what's going on over there? Are there shadow devuan channels functioning there? | 00:11 |
| golinux | joerg: ^^^ | 00:12 |
| joerg | hm? | 00:12 |
| plasma41 | golinux: I have nothing to gain from checking. | 00:12 |
| golinux | but devuan does | 00:13 |
| joerg | leenode? no idea | 00:13 |
| golinux | freenode | 00:13 |
| golinux | It just hurts to write the real name of the now impostor. | 00:14 |
| joerg | could somebody run a grep -ri "freenode" /documents/devuan maybe? | 00:15 |
| golinux | Those channels are listed in historical documents but sadly also in some current documentation. We have been discussing how to deal with it. So folks have possibly gone to freenode and in noman's land | 00:18 |
| joerg | I didn't touch peenode since... they nuked services | 00:18 |
| golinux | but have devuan channels been recreated there | 00:18 |
| golinux | ? | 00:18 |
| joerg | for sure | 00:18 |
| golinux | and no one is monitoring them? | 00:19 |
| joerg | anybody ignorantly doing a /join #devuan there will "create" the channel | 00:19 |
| joerg | I don't care if they have chanops, founders, a topic, users, whatever. leenode is a death zone for me, steer clear by all means | 00:20 |
| UsL | speaking of which: looks like they pulled the plug. But I guess it mus be some other issue: https://netsplit.de/networks/top10.php | 00:22 |
| joerg | netsplit is a trustworthy overview that might give some insight regarding channels ezc on leenode without touching it directly | 00:26 |
| joerg | https://netsplit.de/networks/statistics.php?net=freenode | 00:28 |
| joerg | >>From July 2021 no more connections to freenode could be established. The network was accordingly classified as historic.<< | 00:28 |
| UsL | the network is refusing connections then. Well, that is certainly the nail in the coffin. | 00:30 |
| mason | It could just be refusing unencrypted connections. | 00:30 |
| jushur | they activly ip banned a loot of "internet" its not down. | 00:30 |
| joerg | /msg alis list freenode | 00:32 |
| joerg | don't be fooled, those are LIBERA channels related to freenode | 00:34 |
| jushur | what matters is how we handle it now, ignore those servers. and we activly keep people on the proper path.. | 00:37 |
| joerg | sed -i 's/freenode/libera/g' devuan/docs/ | 00:40 |
| joerg | [1 Sep 2021 00:15:05] <joerg> could somebody run a grep -ri "freenode" /documents/devuan maybe? | 00:41 |
| joerg | maybe ask libera staff, they might be willing to help, contribute and mentor | 00:44 |
| Xenguy | joerg, I ran your query on the 'documentation' repo, and it comes up clean, hrm | 00:46 |
| joerg | and eventually I need to finally run sth similar to above mentioned sed job across the logbot filenames and scripts and config files | 00:46 |
| Xenguy | joerg, Yeah, a few people have mentioned that, would be great it there was a way to patch that path | 00:51 |
| Xenguy | golinux, Strange, even the Beowulf release notes are coming up clean here, i.e. don't mention 'freenode'. | 00:51 |
| Xenguy | Current working theory re: Release Notes: version 3.0 does reference 'freenode'; version 3.1 does not. | 00:59 |
| jushur | hmm geting some lag, guess someone didnt like me. | 01:02 |
| fsmithred | has anyone tried loggin into freenode devuan channels? | 01:16 |
| fsmithred | to see what's going on? | 01:17 |
| * fsmithred goes off to answer his own question | 01:17 | |
| fsmithred | I can't log in. | 01:22 |
| joerg | Xenguy: the chanlog URL/path? | 01:22 |
| mason | fsmithred: They require encrypted logins. | 01:23 |
| joerg | fsmithred: https://netsplit.de/networks/statistics.php?net=freenode >>From July 2021 no more connections to freenode could be established. The network was accordingly classified as historic.<< | 01:24 |
| fsmithred | I've got ssl and sasl enabled | 01:24 |
| fsmithred | oh! | 01:24 |
| fsmithred | it's just gone? | 01:24 |
| mason | jushur spoke to this earlier | 01:24 |
| mason | lots of blocking but still up | 01:25 |
| joerg | fore me it's long gone. The question is which relevance it has to devuan | 01:25 |
| golinux | Xenguy: http://files.devuan.org/devuan_beowulf/Release_notes.txt | 01:25 |
| joerg | nobody wants to login to leenode, the question is what's needed so nobody does accidentally | 01:26 |
| fsmithred | I just wanted to see if anyone was hanging out in devuan channels | 01:26 |
| mason | fsmithred: :*.joseon.kr NOTICE * :*** You must use TLS/SSL and authenticate via SASL to connect to freenode please visit https://irc.com/login/sso in order to create an account. SASL Configuration: https://freenode.net/kb/answer/sasl - Webchat: https://webchat.freenode.net/ | 01:27 |
| fsmithred | yeah, that's the message I keep getting. | 01:28 |
| fsmithred | SASL fails | 01:28 |
| fsmithred | I assume they deleted my account | 01:28 |
| mason | They deleted all accounts, yes. | 01:28 |
| golinux | fsmithred: Maybe you can correct it here? http://files.devuan.org/devuan_beowulf/Release_notes.txt | 01:29 |
| fsmithred | yeah, I can do that | 01:29 |
| fsmithred | what should I put? | 01:29 |
| fsmithred | just irc.libera.? | 01:29 |
| fsmithred | chat | 01:30 |
| golinux | I checked out freenode.net. Somehow that message doesn't compute to have a billionaire saying it | 01:30 |
| golinux | Ask Xenguy how he's doing it | 01:30 |
| joerg | gosh, could you please avoid mentioning detailed instructions how to join a deprecated rogue network in here? | 01:31 |
| golinux | Actually all addresses are here https://www.devuan.org/os/community | 01:31 |
| fsmithred | what am I changing on fdo? | 01:32 |
| fsmithred | found it | 01:32 |
| fsmithred | right. change nothing. it already says IRC channel: #devuan #devuan-dev on libera.chat | 01:34 |
| golinux | http://files.devuan.org/devuan_beowulf/Release_notes.txt | 01:34 |
| joerg | note that on peenode the above instructions for libera would not only earn you a ban, also your channel gets hijacked and you get removed from ACL | 01:34 |
| joerg | I really don't see why we need instructions here how to join peenode | 01:35 |
| fsmithred | ? | 01:35 |
| fsmithred | here because I asked. Not in any docs. | 01:36 |
| * golinux goes off to egg foo yung | 01:36 | |
| fsmithred | I can just replace freenode with irc.libera.chat? | 01:36 |
| fsmithred | in these two lines: | 01:36 |
| fsmithred | #devuan (freenode) - general discussion about Devuan | 01:36 |
| fsmithred | #devuan-arm (freenode) - specific support for ARM | 01:36 |
| joerg | fsmithred: sounds good | 01:37 |
| fsmithred | done | 01:37 |
| golinux | - shouting (but not too loudly) on one of the Devuan IRC channels: | 01:57 |
| golinux | #devuan (freenode) - general discussion about Devuan | 01:57 |
| golinux | #devuan-arm (freenode) - specific support for ARM | 01:57 |
| golinux | 3 lines | 01:58 |
| golinux | Sorry seeing double obviously | 01:58 |
| mason | Hrm, we'll want to fork podman for Chimaera. It defaults to systemd as a cgroup manager but will accept other stuff, but the baked-in default will need to change. Same with logging - defaults to journald but has a knob. | 01:58 |
| mason | I'm going to see if I can get a sane rebuild using cgroupfs and syslog. | 01:59 |
| mason | (podman is something I actively want for my own use) | 01:59 |
| golinux | That is something that has already been discussed iirc | 01:59 |
| mason | Oh, hrm. In meeting notes? | 02:00 |
| golinux | https://pad.dyne.org/code/#/2/code/edit/zrwXb4YnOlmO6fy2mPq4AsmR/ | 02:00 |
| mason | ty | 02:00 |
| mason | Oh, neat. Looks like it's already resolved?!? | 02:01 |
| golinux | Seems like there is a fix there | 02:01 |
| golinux | https://lists.dyne.org/lurker/search/20380101.000000.00000000@ml:devuan-dev,podman.en.html | 02:03 |
| golinux | Does anyone know why rrq has been absent from these channels? | 02:04 |
| mason | looking at logs, and will email him if there's nothing obvious | 02:05 |
| mason | Saw him a day ago, give it take. Will email. | 02:06 |
| fsmithred | wb | 02:33 |
| mason | rrq: o/ | 02:34 |
| rrq | I think znc got upset by some chat network service.. should be back now (for a while) | 02:35 |
| mason | Our fix for podman is beautifully minimal and elegant. It's just https://bpa.st/VKNQ | 02:39 |
| golinux | rrq: Missed you! | 03:03 |
| * rrq been too busy newlisp-ing to observe disconnect ;) | 03:08 | |
| mason | rrq: My nine year old want to learn programming, so she's working through Land of Lisp. | 03:09 |
| mason | We got a second copy so we could go through it together. | 03:09 |
| mason | Also, newLISP is unfortunately named given that it's thirty years old and things like Clojure are newer. Just saying. :P | 03:09 |
| rrq | yeah; "newlisp" is just a convenient scripting tool with lisp-like language | 03:10 |
| mason | Then again, I suppose people could poke fun at Common Lisp for including "Common" | 03:10 |
| mason | Hrm, newLISP looks like it has some of the same strengths as Chicken Scheme. | 03:12 |
| rrq | let's you do stuff you'd consider using bash for, but need a bit more of data manipulation ability | 03:12 |
| mason | nifty | 03:12 |
| rrq | like, if you want to find the outline boxes for characters in a bitmap.. | 03:13 |
| * mason struggles to parse that. | 03:14 | |
| mason | Like, looking at a bitmap and identifying boundaries for individual characters? | 03:14 |
| rrq | yes | 03:14 |
| * mason doesn't feel smart any more. | 03:14 | |
| * rrq exploring an OCR idea based on regression matching for character feature vectors, and I don't want to invest the time of a proper C coding frameowrk.. using newlisp for quick-and-dirty exploration | 03:17 | |
| rrq | using bash would be tricky wrt the data manipulation | 03:18 |
| bgstack15 | I would just go "apt search ocr" | 03:18 |
| bgstack15 | lol | 03:18 |
| rrq | been there, done that | 03:18 |
| mason | rrq: You're not trying to defeat captchas, are you? =narrows eye= | 03:25 |
| rrq | .. ah; reminds me that newlisp can be run in the browser .. hmm | 03:27 |
| onefang | Ah the irony, defeating captchas with a bot. | 03:32 |
| mason | heh | 03:34 |
| bgstack15 | Devuan meet tomorrow, 02 September, at 20:30 UTC. Pad is here: https://pad.dyne.org/code/#/2/code/edit/6ejjHrAKxKsNk28D4GoaGkqX/ | 16:47 |
| gnu_srs | Hi, a question about bug closing: Do I have to close both bug #xx and bugs #yy, #zz, etc merged with #xx explicitly? | 19:28 |
| LeePen | No, closing any one of the merged ones will close the rest. | 19:32 |
| gnu_srs | LeePen: I have now pushed eudev-3.2.9-10 to unstable. Can you take a look. And how can I issue a build (forgot how)? | 19:45 |
| gnu_srs | Found the link of Jenkins Autobuild Infrastructure at https://git.devuan.org/devuan/documentation/src/branch/master/maintainers | 19:58 |
| gnu_srs | Anyway, I'll wait for your (and others) comments. | 19:59 |
| LeePen | gnu_srs: Thanks. Generally looks fine to me. | 20:25 |
| LeePen | A couple of small points: why urgency high? | 20:26 |
| LeePen | The convention for d/changelog is to indent the line under the * bullet point. | 20:26 |
| LeePen | Since you are the de-facto maintainer, would you own the Maintainer field in d/control? | 20:27 |
| LeePen | In general, I would use separate commits for different issues rather than squashing them together. | 20:32 |
| LeePen | It makes review and reverts easier. | 20:33 |
| LeePen | But that is just me, others may well differ. | 20:33 |
| gnu_srs | LeePen: Urgency high due to that bug #598 has severity grave. | 20:55 |
| gnu_srs | Regarding indentation, I see that that went wrong. Should I change? | 20:56 |
| gnu_srs | Separate commits would be nicer I agree. I should have made the commits twice, but was lazy. | 20:58 |
| gnu_srs | Regarding the Maintainer: I'm reluctant to change that. Especially when upstream is soon gone... | 20:59 |
| gnu_srs | I see a small problem: Change and commit for bug #598, and then change and commit for bug #600. How to handle the changelog? Still using the same version 3.2.9-10?? | 21:07 |
| LeePen | gnu_srs: Yes, fix the indentation if you can be bothered. dpkg-parsechangelog doesn't seemt o mind, but it would make it more consistent. | 21:58 |
| LeePen | The way *I* work is to do single commits for particular issues and then update the changelog as a separate item. | 21:59 |
| LeePen | gbp-dch can help manage that. | 21:59 |
| LeePen | Alternatively, start the new changelog version with release=UNRELEASED and add a new * bullet point in the commit that addresses the issue. | 22:00 |
| LeePen | Then finalise the changelog by changing release to unstable and add your signature. | 22:01 |
| LeePen | I think it is a matter of taste which of those to prefer, but they keep commits clean and on topic. | 22:01 |
| LeePen | HTH | 22:01 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!