| 00:07.11 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 00:20.07 | *** join/#devuan targz (~Thunderbi@unaffiliated/targz) |
| 00:22.35 | Xenguy | Does anyone recall offhand what package needs to be reconfigured to display larger text on the console? |
| 00:22.55 | plub | no |
| 00:23.03 | plub | i'd like multi-console though |
| 00:23.07 | plub | someone should write that for me |
| 00:23.21 | plub | 2 or 3 or 4 virtual framebuffers |
| 00:23.33 | Xenguy | I remember in the old days the default font was a nice large size, whereas nowadays some genius has decided to make the default console font a perfect size for 'young eyes' |
| 00:23.41 | Xenguy | plub: Don't hijack the question |
| 00:23.49 | plub | sorry i'll try to find an answer |
| 00:23.56 | Xenguy | I don't need to hear if you don't know the answer |
| 00:24.13 | fsmithred | Xenguy, dpkg-reconfigure console-setup |
| 00:24.19 | Xenguy | Thank you |
| 00:24.55 | plub | /etc/default/console-setup |
| 00:26.14 | systemdlete | yesterday's upgrade resulted in the creation of 2 new unix groups, render and kvm. afaik, I don't have virtualization installed other than vbox client software. Vbox has been working here for ages, so this is a bit odd. |
| 00:27.17 | systemdlete | render, I understand, is related to graphics, so it seems some features supporting X or other graphics tools now require this "render" ownership. |
| 00:28.49 | systemdlete | It is the "kvm" group that has me a bit worried. Why would that group suddenly be required when (a) I don't use kvm for virtualization (except for vbox which has been here for ages), and (b) |
| 00:29.09 | systemdlete | I did not install any new software that I can think of. |
| 00:30.35 | fsmithred | systemdlete, eudev created it. Did you get an error message, or you just saw that it got created? |
| 00:30.47 | systemdlete | the apt history.log file only shows one entry yesterday (the previous update was on 2/6/2021) so the addition of kvm group must have been created by one of the package updates yesterday. |
| 00:31.00 | fsmithred | yeah, eudev |
| 00:31.02 | systemdlete | fsmithred: my nightly logwatch report. |
| 00:31.18 | fsmithred | came from beowulf-proposed-updates along with a few other things |
| 00:31.36 | systemdlete | Any idea why? |
| 00:31.39 | fsmithred | see bug#548 for more info |
| 00:31.42 | systemdlete | I find it strange. |
| 00:31.43 | systemdlete | ok |
| 00:31.50 | systemdlete | devuan bug 548? |
| 00:31.53 | fsmithred | which has not yet been answered by the dev |
| 00:31.55 | fsmithred | yeah |
| 00:31.59 | systemdlete | hmmm. |
| 00:32.19 | systemdlete | I take it this would originate "upstream"? |
| 00:32.22 | systemdlete | (debian) |
| 00:32.24 | fsmithred | no |
| 00:32.32 | fsmithred | well, I don't know |
| 00:32.40 | systemdlete | ok... thanks for this info. |
| 00:32.51 | systemdlete | is grateful for logwatch... |
| 00:33.15 | fsmithred | it's not related to any changes in eudev that I'm aware of, and I was involved in reporting the problem and testing the fix. |
| 00:33.26 | fsmithred | but there were probably some other changes, too |
| 00:33.49 | fsmithred | "the problem" is completely different from what we're talking about now |
| 00:34.03 | numzob | odd, in another distro i only eeded to add a kvm group when installing qemu |
| 00:34.06 | systemdlete | of course it is ;) |
| 00:34.09 | numzob | needed* |
| 00:34.18 | systemdlete | yes, exactly. |
| 00:34.59 | systemdlete | vbox USES kvm for guests that are configured to do so, but it is not needed by the guest itself. |
| 00:35.11 | systemdlete | vbox offers kvm and other virt methods |
| 00:35.35 | systemdlete | if it were needed by the guest, it would have been configured for kvm long ago |
| 00:38.32 | systemdlete | fsmithred: I have not attempted to reboot since the update yesterday... from the sounds of the report, I wonder if my system is still bootable? |
| 00:38.47 | systemdlete | I'm guessing it is, since my update did not fail. |
| 00:38.47 | fsmithred | what??? |
| 00:38.54 | fsmithred | why would it not be bootable? |
| 00:39.24 | systemdlete | I guess I'd only need to worry if the update had failed as per the report (548) |
| 00:39.39 | systemdlete | and even then, that might not be an issue, idk. |
| 00:39.41 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 00:40.54 | systemdlete | Messing around with / modifying such basic and essential parts of the system is generally a bad idea. GNU/Linux has been around for over 25 years now, so my feeling is that this portion of the system should be very stable by now. Updates/changes/fixes rare. |
| 00:41.10 | systemdlete | (Oh, yes. I know why it isn't... ) |
| 00:42.29 | systemdlete | I guess some people think that the software base of GNU/Linux is some sort of self-amusement park, and don't realize that there might be actual serious applications in use. |
| 00:42.37 | systemdlete | but alas... |
| 00:45.34 | systemdlete | https://linux.slashdot.org/story/21/02/13/0115253/did-linux-kill-commercial-unix |
| 00:46.19 | systemdlete | just by coincidence, this is a slashdot story that broke recently. "If something's genuinely mission-critical and it's working, you leave it working." I agree. |
| 00:46.43 | systemdlete | If you want to play, there's a sandbox for that somewhere... |
| 00:58.55 | *** join/#devuan Acacia (~Acacia@unaffiliated/acacia) |
| 01:09.48 | *** join/#devuan ar3itrary (~hacker@2a03:4000:6:8177:2::1) |
| 01:18.13 | *** join/#devuan tuxd3v_ (~tuxd3v@94.133.162.237) |
| 01:47.39 | *** join/#devuan arnoldoree (~arnoldore@113.210.59.196) |
| 02:44.07 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 02:55.55 | *** join/#devuan morla1011193 (~morla1011@mail.cracksucht.de) |
| 02:57.17 | *** join/#devuan hook54321_ (sid149355@gateway/web/irccloud.com/x-yzakhxhyvycajkdh) |
| 02:58.27 | *** join/#devuan bleb_ (~cm@unaffiliated/bleb) |
| 03:00.13 | *** join/#devuan byzandula (~byzandula@beerbq.net) |
| 03:00.36 | *** join/#devuan jelly-home (jelly@pdpc/supporter/active/jelly) |
| 03:01.02 | *** join/#devuan hplar (~ralph@147.87.5.199) |
| 03:01.30 | *** join/#devuan arnoldoree (~arnoldore@113.210.59.196) |
| 03:02.21 | *** join/#devuan dagelf (~quassel@dsl-197-245-38-51.voxdsl.co.za) |
| 03:03.24 | *** join/#devuan jelly-home (jelly@pdpc/supporter/active/jelly) |
| 03:17.27 | *** join/#devuan yanmaani (~yanmaani@gateway/tor-sasl/yanmaani) |
| 03:24.48 | *** join/#devuan D-HUND (~debdog@2a00:79c0:638:900:7a24:afff:fe8a:d04d) |
| 03:25.35 | *** join/#devuan clemens3 (~clemens@225.40.150.83.ftth.as8758.net) |
| 03:58.27 | *** join/#devuan sunshavi (~user@190.42.230.123) |
| 04:36.01 | *** mode/#devuan [+o mason] by ChanServ |
| 04:36.13 | *** mode/#devuan [+b *!clr0t@gateway/shell/ircnow/*] by mason |
| 04:36.17 | *** kick/#devuan [plub!~mason@redhat/mason] by mason (plub) |
| 04:37.23 | *** mode/#devuan [-o mason] by ChanServ |
| 04:37.52 | *** join/#devuan fling (~fling@fsf/member/fling) |
| 04:58.57 | *** join/#devuan Kimmo_ (sprite@silokki.org) |
| 05:12.19 | *** join/#devuan targz (~Thunderbi@unaffiliated/targz) |
| 05:15.48 | *** join/#devuan FlibberTGibbet (~david@unaffiliated/flibbertgibbet) |
| 05:23.24 | *** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:25.53 | *** join/#devuan Menelkir (~terramex@unaffiliated/menelkir) |
| 05:34.23 | *** join/#devuan ar3itrary (~hacker@2a03:4000:6:8177:2::1) |
| 05:51.36 | *** join/#devuan o01eg (~o01eg@2a02:2698:82a:bb0:5a1e:eb56:b74a:64e1) |
| 06:05.27 | *** join/#devuan zxq9 (~zxq9@FL1-119-244-160-91.okn.mesh.ad.jp) |
| 06:27.46 | *** join/#devuan kiwi9 (~john@2001:8003:6da8:c01:2d8:61ff:fe7b:961b) |
| 06:29.15 | *** join/#devuan kiwi9 (~john@2001:8003:6da8:c01:2d8:61ff:fe7b:961b) |
| 07:11.58 | lts | Just noticed some 404s in apt upgrade. How common is it that several mirrors fail sync? The one I use is on the list https://pkgmaster.devuan.org/mirror_status.html |
| 07:25.30 | *** join/#devuan arnoldoree (~arnoldore@113.211.188.151) |
| 07:30.08 | *** join/#devuan Joril (~joril@217.194.188.145) |
| 07:49.01 | *** join/#devuan luser978 (~resuuser@188.25.231.227) |
| 07:52.23 | *** join/#devuan xinomilo (~xinomilo@gateway/tor-sasl/xinomilo) |
| 08:33.19 | *** join/#devuan krzych (krzych@nroot.pl) |
| 08:36.10 | *** join/#devuan tuxd3v (~tuxd3v@a94-133-162-237.cpe.netcabo.pt) |
| 08:44.35 | *** join/#devuan onefang (~dvs1@devuan/developer/onefang) |
| 08:51.08 | *** join/#devuan furrymcgee (~debian@31.179.186.66) |
| 09:08.44 | *** join/#devuan luna_is_here (~quassel@ip-95-223-58-221.hsi16.unitymediagroup.de) |
| 09:15.20 | *** join/#devuan Pali (~pali@Maemo/community/contributor/Pali) |
| 09:43.11 | *** join/#devuan rsx (~rsx@ppp-188-174-135-195.dynamic.mnet-online.de) |
| 10:03.12 | djph | lts: if your timing is good, it's fairly common |
| 10:03.26 | djph | ("good" as in "you hit them mid-update") |
| 10:16.22 | *** join/#devuan dice (~puppy@n49-187-117-34.rdl3.qld.optusnet.com.au) |
| 10:17.35 | *** part/#devuan dice (~puppy@n49-187-117-34.rdl3.qld.optusnet.com.au) |
| 10:28.53 | lts | Right, thanks for confirming |
| 10:29.22 | onefang | My network has been down most of the day, I wonder what you are talking about? Sounds a bit package mirror related to me. |
| 10:31.16 | *** join/#devuan gnu_srs (~srs@devuan/developer/srs) |
| 10:32.18 | lts | I was just wondering how normal this is https://pkgmaster.devuan.org/mirror_status.html |
| 10:32.18 | onefang | djph , lts ^^^ |
| 10:34.36 | onefang | https://sledjhamr.org/apt-panopticon/results/Report-web.html shows more info. And some of the errors in the Updated column are coz I haven't updated how often some of the mirrors update. |
| 10:35.27 | onefang | I need to crack the whip and get some mirrors to fix a few things as well. lol |
| 10:37.40 | onefang | Soooo, for the Updated column, a warning means "the upstream master pkgmaster has been updated, this mirror hasn't caught up yet, but is still within its update time". A mirror not being fully up to date 10 minutes after pkgmaster updates, but it still has a 20 minute window to get updated. Error means it's now outside of it's update window and still not updated. |
| 10:39.01 | lts | Thanks. Looks quite minor. The mirror I use still shows there as FAILED but now has started to work (in the last 30 minutes I think) |
| 10:39.16 | lts | To work = now has the newest updates |
| 10:39.57 | enyc | meows |
| 10:42.04 | *** join/#devuan psarria (~psarria@91.194.63.144) |
| 11:20.44 | *** join/#devuan Soo_Slow (Soo_Slow@gateway/vpn/privateinternetaccess/sooslow/x-31376162) |
| 11:31.26 | *** join/#devuan romo (~romo@unaffiliated/romo) |
| 12:02.50 | *** join/#devuan arnoldoree (~arnoldore@113.210.54.52) |
| 12:09.25 | *** join/#devuan jotaxpe (jotaxpe@gateway/vpn/protonvpn/jotaxpe) |
| 12:32.10 | *** join/#devuan l41f3n (~l41f3n@mail.laifen.org) |
| 12:33.02 | l41f3n | Hello, I can see embedded section for ascii devuan but not for beowulf. Is it normal ? |
| 12:33.24 | l41f3n | I would like install beowulf on my rapi3 :) |
| 12:40.59 | *** join/#devuan AZG256 (~user@78-56-98-5.static.zebra.lt) |
| 13:14.17 | fsmithred | l41f3n, there are community-produced images for beowulf here - https://arm-files.devuan.org/ |
| 13:15.05 | fsmithred | and a forum section for arm discussion: https://dev1galaxy.org/viewforum.php?id=24 |
| 13:18.27 | l41f3n | thank you fsmithred :) |
| 13:18.55 | fsmithred | also #devuan-arm irc |
| 13:22.12 | *** join/#devuan sunshavi (~user@190.42.230.123) |
| 13:48.55 | *** join/#devuan guest29348769876 (~rsx@ppp-188-174-155-159.dynamic.mnet-online.de) |
| 13:55.20 | *** join/#devuan blizzow (~blizzow@71-218-115-215.hlrn.qwest.net) |
| 13:56.54 | *** join/#devuan targz (~Thunderbi@unaffiliated/targz) |
| 14:13.36 | *** join/#devuan luser977 (~resuuser@188.25.231.227) |
| 14:54.00 | *** join/#devuan rsx (~rsx@ppp-188-174-156-12.dynamic.mnet-online.de) |
| 15:08.30 | *** join/#devuan furrymcgee (~debian@31.179.186.66) |
| 15:23.06 | *** join/#devuan xrogaan (~xrogaan@unaffiliated/xrogaan) |
| 15:30.20 | *** join/#devuan xes_ (~xes@unaffiliated/xes) |
| 15:32.25 | *** join/#devuan lkjasdf (~u0_a63@c-69-243-91-117.hsd1.md.comcast.net) |
| 16:04.18 | *** join/#devuan aldebaran (~aldebaran@net-93-151-173-245.cust.dsl.teletu.it) |
| 16:04.28 | *** join/#devuan cd (~cd@unaffiliated/cd) |
| 16:09.41 | *** join/#devuan IoFran (~Thunderbi@189.237.85.240) |
| 16:14.22 | *** join/#devuan lkjasdf (~u0_a63@c-69-243-91-117.hsd1.md.comcast.net) |
| 16:17.48 | *** join/#devuan fling (~fling@fsf/member/fling) |
| 17:06.56 | rwp | fsmithred, TIL: Devuan BTS does not support severity important! "severity 548 important; Severity level `important' is not known. Recognized are: critical, grave, normal, minor, wishlist." |
| 17:07.28 | rwp | Seems odd they did not like that level and did not implement it in the BTS. |
| 17:07.50 | fsmithred | I'll mention it at our meeting today |
| 17:08.27 | fsmithred | thanks. I never noticed that because I never bother with severity. I think mine are all normal. |
| 17:08.41 | rwp | I also don't see "serious |
| 17:08.50 | rwp | I also don't see "serious" in the list either. So that one was dropped too. |
| 17:08.59 | fsmithred | debian has all those? |
| 17:09.01 | rwp | So now I must decide, is it grave? |
| 17:09.02 | *** join/#devuan st3ma (~st3ma@88.133.163.96) |
| 17:09.09 | rwp | Yes. See this list: https://www.debian.org/Bugs/Developer#severities |
| 17:09.30 | fsmithred | doesn't really matter. The maintainer is aware of it and it will be taken care of. |
| 17:10.11 | rwp | Yes. But for us out in the field using the system we must maintain a list in our head of how everything is slightly different here versus there. |
| 17:10.27 | fsmithred | the dev who got the bts up and running was the one who gave the talk on minimalism at the conference |
| 17:10.41 | rwp | Hahaha! |
| 17:11.32 | *** join/#devuan n4dir (~n4dir@i577BC919.versanet.de) |
| 17:12.59 | rwp | I have often used "important" when I thought something was significant to raise up out of the see of sometimes thousands of "normal" bugs. |
| 17:13.04 | rwp | Oh well. Anyway... Just thought I would pass that tidbit along. |
| 17:14.06 | fsmithred | thanks |
| 17:15.27 | *** join/#devuan Akuli (~akuli@87-94-110-91.bb.dnainternet.fi) |
| 17:23.16 | luser977 | be sure to ask for severity levels "systemd_tainted" and "ridiculous". if the 1st is not accepted then the 2nd could be used instead. |
| 17:23.25 | luser977 | <jk> |
| 17:25.27 | fsmithred | systemd_tainted might actually be a useful tag |
| 17:25.42 | mason | fsmithred: Less typing: unclean |
| 17:25.46 | fsmithred | as they fuck up more packages causing bugs |
| 17:26.02 | fsmithred | ok, that works |
| 17:30.20 | tuxd3v | is observing gladly the systemd_tainted tag :) |
| 17:45.29 | *** part/#devuan n4dir (~n4dir@i577BC919.versanet.de) |
| 17:47.44 | *** join/#devuan sunshavi (~user@190.42.230.123) |
| 17:56.01 | *** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 18:00.28 | *** join/#devuan alexandros_tab_ (~quassel@unaffiliated/alexandros-c/x-1684531) |
| 18:00.33 | *** join/#devuan alexandros_c__ (~quassel@unaffiliated/alexandros-c/x-1684531) |
| 18:03.33 | *** join/#devuan user__ (~user@188.25.231.227) |
| 18:05.25 | user__ | Updates on bluez-tools and bluetooth @beowulf: the bluez-tools are a huge huge set of C sources which mostly manipulate strings related to dbus. Iow, a Perl, bash (!), tcl, etc approach might have done the job as needed (in the right programmer's hand), using nothing (much) more than dbus-monitor and dbus-send, 2 cli tools supplied with dbus. |
| 18:06.03 | *** join/#devuan enyc (~enyc@muddle.enyc.org.uk) |
| 18:06.54 | user__ | Just as a simple example, bt-agent source in bluez-tools has a ~80loc C function to read and hash (!) the known devices pin file which may have 10 entries or so on a busy machine, and that hash table is used in a 300 loc C function to authenticate (bluetooth pairing) a new device. Would I rewrite this? No. |
| 18:07.09 | user__ | Is anyone aware of a project accessing dbus from scripts only? |
| 18:11.48 | fsmithred | I used to have a script for shutdown/reboot that used dbus commands |
| 18:20.11 | *** join/#devuan Kitty (freemadi@mail.quixotic.eu) |
| 18:20.32 | Kitty | hi, who would I need to talk to about a package being added to backports? |
| 18:21.04 | fsmithred | what do you want to backport? |
| 18:21.10 | Kitty | dropbear |
| 18:22.29 | gnarface | it is present in ceres |
| 18:22.50 | Kitty | I'm currently using beowulf-backports |
| 18:23.14 | fsmithred | all of it? |
| 18:23.39 | Kitty | well I stuck it in apt config, and did a dist-upgrade |
| 18:23.46 | Kitty | where doeas ceres fit ? |
| 18:23.49 | fsmithred | wow |
| 18:23.51 | fsmithred | ceres=sid |
| 18:23.58 | fsmithred | chimaera=bullseye |
| 18:24.01 | Kitty | sid == testing? |
| 18:24.09 | fsmithred | sid=unstable |
| 18:24.19 | fsmithred | chimaera is testing |
| 18:24.20 | Kitty | I can never track the names, so always just think of stable, unstable, testing |
| 18:24.27 | fsmithred | same version of dropbear in both |
| 18:24.34 | Kitty | and backports... which IIRC is stable+some stuff from testing |
| 18:24.41 | fsmithred | yeah |
| 18:24.43 | gnarface | hmm |
| 18:24.54 | gnarface | it is also in beowulf already... why do you need the backports one now? |
| 18:25.06 | fsmithred | ...that has not *all* been tested together |
| 18:25.09 | *** join/#devuan plasma41 (~plasma41@72.34.178.45) |
| 18:25.27 | Kitty | because version 2018.76 doesn't support ED25519 keys, |
| 18:25.46 | Kitty | but version 2020.79 or later does |
| 18:26.18 | fsmithred | have you backported it yourself yet? |
| 18:26.51 | Kitty | how would I do that? |
| 18:27.01 | gnarface | Kitty: a lot of times debian backports patches for important stuff, but does not backport the version number. has it been verified that the build in beowulf doesn't support ED25519 keys whatever they are, or is this assumption being made based on the version number alone, compared to that version number in other unrelated distros? |
| 18:28.03 | gnarface | Kitty: i'm just mentioning it because it is common for people to go chasing their tail for no reason over such issues |
| 18:28.17 | Kitty | I installed the dropbear that is in beowulf, and it doesn't support ed25519 keys. |
| 18:28.24 | gnarface | ok |
| 18:28.31 | gnarface | the backport process might be simple |
| 18:28.35 | plasma41 | Just got Internet connectivity back. What software are we talking about? |
| 18:28.43 | Kitty | the upstream project only added it as a feature in version 2020.79 in jun 2020 |
| 18:28.51 | Kitty | https://matt.ucc.asn.au/dropbear/CHANGES |
| 18:30.00 | gnarface | Kitty: 1) you just check out the build deps for the beowulf version with "apt-get build-dep dropbear" then you get the source package from ceres with "apt-get -t ceres source dropbear" and then you build it with ... i think something like: cd ./dropbear[tab] && dpkg-buildpkg -us -uc |
| 18:30.38 | gnarface | Kitty: the process is well documented at debian but they bury it in chapter 6 of the new maintainer's guide. someone has a condensed summary of the process around here somewhere but i don't have the link |
| 18:30.59 | Kitty | eek, that looks complicated |
| 18:31.35 | gnarface | it is the best option all things considered |
| 18:32.21 | Kitty | what is the name for the equivilant of testing? |
| 18:32.25 | gnarface | nothing is really stopping you from just upgrading to ceres instead, other than the significantly higher cost in luck |
| 18:32.32 | gnarface | chimera is testing |
| 18:32.34 | plasma41 | Kit |
| 18:32.53 | plasma41 | Kitty: testing is chimaera |
| 18:33.16 | fsmithred | oldie but goodie: http://forums.debian.net/viewtopic.php?f=16&t=38976 |
| 18:33.29 | gnarface | in theory the backport process from ceres->beowulf should work just as well for chimera->beowulf |
| 18:33.59 | fsmithred | ceres and chimaera are mostly the same now, since sid is in early freeze |
| 18:34.42 | Kitty | E: The repository 'http://deb.devuan.org/merged chimera Release' does not have a Release file. |
| 18:34.51 | fsmithred | try again in a little while |
| 18:34.58 | Kitty | looks like it's not a simple case of swapping beowulf for chimera in the sources file |
| 18:34.58 | fsmithred | few minutes maybe |
| 18:35.07 | fsmithred | almost simple |
| 18:35.13 | plasma41 | Kitty: Looks like the testing version of dropbear requires the testing release of libtommath-dev to compile. All other build dependencies are available in stable or stable-backports. |
| 18:35.15 | *** join/#devuan orcus-de (~orcus_@213.170.218.225) |
| 18:35.27 | fsmithred | you don't need -updates or -security for chimaera or ceres |
| 18:35.43 | gnarface | Kitty: nothing will stop you from just installing the ceres or chimera version directly into beowulf either, but that's not advised because the library version mismatches might cause instability |
| 18:35.50 | plasma41 | afk |
| 18:35.59 | Kitty | I tried that, but it went into dependency hell |
| 18:36.34 | gnarface | ah. well, backporting is the way you get around that |
| 18:36.41 | gnarface | in theory, anyway |
| 18:36.50 | *** join/#devuan lkjasdf (~u0_a63@c-69-243-91-117.hsd1.md.comcast.net) |
| 18:36.50 | gnarface | sometimes you have to backport some dependencies too |
| 18:37.15 | *** join/#devuan lkjasdf (~u0_a63@c-69-243-91-117.hsd1.md.comcast.net) |
| 18:37.18 | gnarface | and it is possible to run into a situation where you end up recursively backporting basically the entire next release |
| 18:37.38 | gnarface | (in which case you might as well have just gone ahead and upgraded to it) |
| 18:38.09 | Kitty | what am I doing wrong with my sources.list file... deb http://deb.devuan.org/merged chimera main |
| 18:38.26 | gnarface | that's the binary line |
| 18:38.45 | gnarface | duplicate it with "deb-src" at the beginning instead of just "deb" for source packages |
| 18:39.09 | gnarface | source packages and binary packages are on different source lines |
| 18:39.10 | Kitty | except when I do apt-get update |
| 18:39.12 | Kitty | I get E: The repository 'http://deb.devuan.org/merged chimera Release' does not have a Release file. |
| 18:39.28 | gnarface | like fsmithred just said. wait a few minutes, it is updating |
| 18:39.41 | Kitty | oh right, I hadn't understood that |
| 18:39.56 | gnarface | debian has over 150 mirrors... we have like 12 or 13 |
| 18:41.39 | Kitty | http://deb.devuan.org/merged/dists/chimaera/Release - the file exists... |
| 18:42.19 | gnarface | deb.devuan.org is a dns round-robin |
| 18:42.27 | gnarface | you don't necessarily see the same server every time |
| 18:42.30 | Kitty | oh |
| 18:43.10 | gnarface | "nslookup deb.devuan.org" will show you the whole list |
| 18:43.26 | Kitty | bash: nslookup: command not found |
| 18:43.29 | Kitty | or maybe not |
| 18:43.36 | gnarface | heh, if furnished |
| 18:43.51 | Kitty | 131.188.12.211 - it's doing this site |
| 18:44.08 | Kitty | ah well, patience |
| 18:44.56 | fsmithred | it's up again |
| 18:45.19 | Kitty | still complaining :( |
| 18:45.38 | fsmithred | oh, sorry |
| 18:46.13 | Kitty | <PROTECTED> |
| 18:46.17 | Kitty | E: The repository 'http://deb.devuan.org/merged chimera Release' does not have a Release file. |
| 18:46.52 | gnarface | seems to be working here |
| 18:47.10 | Kitty | PEBKAC |
| 18:47.15 | Kitty | chimera != chimaera |
| 18:47.39 | gnarface | ah |
| 18:50.08 | plasma41 | Kitty: I was just about to point that out, but you realized it before I could type it out. Feel free to personally blame me for choosing a weirdly spelled codename. |
| 18:50.27 | Kitty | I have dyslexia... |
| 18:50.45 | fsmithred | wow, I just tried installing the 2020 version in beowulf live iso, and it would be a mess. (remove a bunch and upgrade libc6 among others) |
| 18:51.25 | fsmithred | backport or upgrade would be much better |
| 18:53.32 | mason | Or a chroot, if there end up being extensive build deps that are problematic. |
| 18:55.02 | plasma41 | Kitty: I also proposed the codename for the release after chimaera: daedalus. Apologies for all the weird vowels. |
| 18:56.25 | gnarface | great, google accepts both spellings |
| 18:56.42 | gnarface | no way to tell which is more proper due to sponsored links as responses |
| 18:56.45 | gnarface | facepalms |
| 18:57.35 | plasma41 | fsmithred: Now you've got me curious. I'm going to try doing a local backport to see how hard it is. |
| 19:02.00 | *** part/#devuan orcus-de (~orcus_@213.170.218.225) |
| 19:09.21 | plasma41 | Well so far I can say that the build dependencies themselves don't spring any recursive dependency traps. |
| 19:12.40 | Kitty | thank you all for your help |
| 19:13.00 | Kitty | I'm logging off for the night. Thanks! am looking forward to using devuan some more |
| 19:13.32 | plasma41 | Kitty: Thanks for stopping by! |
| 19:14.22 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
| 19:16.46 | *** join/#devuan freemangordon (~ivo@46.249.74.23) |
| 19:20.28 | *** join/#devuan orcus-de (~orcus_@213.170.218.225) |
| 19:30.39 | user__ | I think this debian / devuan code name game should be taken to the next level, like those iq logic tests, where the green house is left of the one that has no dogs and not the last one in the row? One could win prizes for guessing the right code names in a short amount of time. |
| 19:31.11 | fsmithred | ours are going in alphabetical order |
| 19:31.24 | user__ | It is almost there, just needs some inpartial arbiter in the form of an irc trivia bot. |
| 19:33.05 | user__ | Also, iirc, on devuan.org, there used to be a table with code names in devuan, an debian, testing whatever, and numbers. Which are yet another facet. Is it still there? |
| 19:33.40 | user__ | I don't see it |
| 19:34.05 | user__ | https://www.devuan.org/os/releases AHHH |
| 19:34.38 | user__ | Kitty should see this. Left? |
| 19:34.52 | user__ | Kitty: ^ tab completion let me down, sorry |
| 19:35.35 | *** join/#devuan lkjasdf (~u0_a63@c-69-243-91-117.hsd1.md.comcast.net) |
| 19:35.50 | *** join/#devuan AnimaInvicta (~AnimaInvi@ber27-1-78-230-215-86.fbx.proxad.net) |
| 19:36.18 | user__ | So, alphabetic: J A B C C ... well Debian also does it. J S B B S |
| 19:36.26 | user__ | (this is so terrible) |
| 19:36.49 | fsmithred | jessie=jessie |
| 19:36.53 | gnarface | it makes more sense if you know more about how debian actually does it |
| 19:37.12 | user__ | openwrt got a clue for the release names from somewhere and double the letter. Attack Attitude, Barrier Breaker etc |
| 19:37.19 | fsmithred | ceres=sid and never changes, is not part of the alphabetical order |
| 19:38.03 | fsmithred | they can wrap around to Attack Barrier? |
| 19:38.15 | user__ | hm? |
| 19:38.21 | user__ | AA BB CC ... |
| 19:38.33 | fsmithred | that's good for 26 versions in english |
| 19:38.41 | fsmithred | after that... |
| 19:38.47 | fsmithred | AB AC AD |
| 19:38.53 | user__ | Yes. By version 13 it will become sentient and rename itself I guess. |
| 19:39.09 | fsmithred | shit, I forgot about skynet |
| 19:39.20 | fsmithred | and we are way OT now |
| 19:39.23 | user__ | Also version HH is close now. I wonder if they'll skip it. |
| 19:39.33 | user__ | yes, let's stop this |
| 19:39.35 | plasma41 | Kitty: AFAICT, if you download the dropbear source from testing as well as the libtommath binary packages from testing and the dephelper binary package from stable-backports, you should be able to compile dropbear on stable and install the resulting binary without triggering any recursive dependency traps. |
| 19:40.11 | user__ | One question: why does Kitty need dropbear instead of sshd? Small device with no room for full sshd? |
| 19:40.13 | gnarface | i remember when they came up with the naming convention for debian, the idea of running out of toy story characters before the distro collapsed in upon itself due to human arrogance was laughable. but here we are... |
| 19:40.41 | Kitty | user__: dropbear can be installed in the initramfs, |
| 19:40.52 | Kitty | which means that you can use it on boot to unlock a LUKS petition |
| 19:41.08 | fsmithred | OH! |
| 19:41.25 | gnarface | god i hope you've tied the decryption keys to a server you physically own |
| 19:41.33 | Kitty | https://www.cyberciti.biz/security/how-to-unlock-luks-using-dropbear-ssh-keys-remotely-in-linux/ |
| 19:41.36 | gnarface | if that's some aws instance you're just asking for trouble |
| 19:41.47 | user__ | Kitty: nice idea |
| 19:41.59 | Kitty | I don't do cloud |
| 19:42.38 | gnarface | well, i wouldn't do this at all, and i would advise anyone not to, but it's a clever idea if you care more about the ability to lock people out on purpose than whether you lock them out on accident |
| 19:42.38 | user__ | Well, technically, initramfs is a small device. Sort of. |
| 19:43.07 | Kitty | gnarface: ? |
| 19:43.21 | user__ | Kitty: have you considered importing the static dropbear usually compiled for use with busybox? |
| 19:43.23 | gnarface | Kitty: lemme put it this way. you'd better have unencrypted backups somewhere |
| 19:43.55 | Kitty | backups are encrypted as well. but we have multiple users with keys to decrypt |
| 19:44.20 | user__ | I see packages for dropbear in beowulf including dropbear-initramfs |
| 19:44.34 | Kitty | yes, but they are not recent enough to support ED25519 keys |
| 19:44.51 | user__ | I am not familiar with those |
| 19:45.16 | Kitty | ecdsa and ed25519 keys are eliptic curve encryption keys |
| 19:45.22 | user__ | ah ok |
| 19:45.28 | Kitty | I wish it also supported ed25519-sk keys |
| 19:46.08 | user__ | Ok, djb is behind this, then it has to be good :) |
| 19:46.15 | plasma41 | Kitty: If you need any help with the above provided recipe, just let me know. I'd be happy to help. |
| 19:47.18 | user__ | Kitty: you can always compile dropbear from scratch. Someone already have you the "debian way". |
| 19:47.22 | user__ | Above. |
| 19:47.38 | Kitty | yeah, I was trying to avoid having to go the from scratch route... |
| 19:48.05 | user__ | Well, debian and bleeding edge packages -- does that even fit in one line of text? |
| 19:48.43 | user__ | 2018.76 to 2020.81 is "just" 5 versions behind. |
| 19:49.37 | Kitty | ed25519 was added in June last year |
| 19:49.44 | user__ | Interesting he had .deb packages up till 2004. On the dropbear site. |
| 19:50.02 | plasma41 | Kitty: It only took me about fifteen minutes to do. Granted, I frequently do quick 'n dirty backports for my own personally use. |
| 19:50.08 | user__ | Sorry, till 2009 |
| 19:50.12 | *** join/#devuan IoFran (~Thunderbi@189.237.140.105) |
| 19:51.24 | user__ | So .80 would work? |
| 19:51.38 | Kitty | I solved it by dist-upgrading to chimaera |
| 19:51.48 | user__ | Is there an automated way to debianize an arch package or such? Almost sure they'd be on the latest. |
| 19:51.54 | user__ | Oh ok. |
| 19:51.58 | plasma41 | Kitty: That's one way to do it |
| 19:52.34 | user__ | What happens if one simply takes the .deb from the version one needs and dpkg installs it? Assuming no big changes? |
| 19:52.46 | user__ | did this in the past quite a few times. |
| 19:53.13 | Kitty | right, at this point, I'm going to stop playing with my laptop, and go watch NASA lower a rocket pupping semi autonomous nuclear powered robot, onto mars from a rocket powered sky crane |
| 19:53.32 | Kitty | s/pupping/pooping/ |
| 19:53.37 | user__ | :) |
| 19:53.49 | plasma41 | user__: The close thing I can think of would be Bedrock Linux <https://bedrocklinux.org/>, but that's a whole other can of worms. |
| 19:53.56 | lkjasdf | you switch to Klingon |
| 19:54.35 | user__ | plasma41: nice link, thanks. |
| 19:56.43 | *** join/#devuan Akuli_ (~akuli@87-94-110-91.bb.dnainternet.fi) |
| 19:56.51 | *** join/#devuan terabit (sid146285@gateway/web/irccloud.com/x-yxujqpjppulrclnx) |
| 19:58.30 | *** join/#devuan scoofy_ (~scoofy@catv-89-135-21-225.catv.broadband.hu) |
| 19:58.32 | *** part/#devuan scoofy (~scoofy@catv-89-135-21-225.catv.broadband.hu) |
| 20:03.25 | *** join/#devuan orcus-de (~orcus_@213.170.218.225) |
| 20:24.50 | *** join/#devuan Guest0 (442a443f@gateway/web/cgi-irc/kiwiirc.com/ip.68.42.68.63) |
| 20:25.24 | Guest0 | does devuan provide screensavers or do they come with xfce? |
| 20:25.49 | Guest0 | i remember using debian stable and not having any screensavers with xfce |
| 20:29.04 | plasma41 | Guest0: Try the xscreensavers packages |
| 20:29.10 | gnarface | Guest0: devuan and debian aren't different in this regard. the screensavers are in the "xscreensaver*" packages |
| 20:29.28 | Guest0 | ah ok so i guess my install must have come with the xscreensaver package |
| 20:29.49 | lts | xfce4-goodies maybe too? |
| 20:30.22 | gnarface | there are some non-stock optional ones that usually aren't included because of video driver stability issues; "apt-cache search ^xscreensaver" |
| 20:30.39 | Guest0 | alr |
| 20:31.19 | gnarface | xlockmore still exists somewhere i think, but it was pulled from debian several releases ago, and it has all the same screensavers as xscreensaver anyway |
| 20:31.46 | lts | Nope, debian/devuan doesn't seem to have xfce4-screensaver in xfce4-goodies. Arch does, I remember using that. Sorry for misinformation |
| 20:31.55 | gnarface | a couple window managers have static lockscreens of their own built-in, superseding the xscreensaver functionality as far as their developers are concerned |
| 20:32.42 | gnarface | (personally i disagree but you're talking about people who get free monitors from their jobs and have never had to make one last more than 2 years) |
| 20:33.55 | lkjasdf | https://www.jwz.org/blog/2021/01/i-told-you-so-2021-edition/ |
| 20:33.57 | gnarface | if you're using nvidia drivers i strongly recommend to avoid the xscreensaver-gl and xscreensaver-gl-extra packages |
| 20:34.14 | gnarface | (hard i/o locks, going back decades.... ) |
| 20:34.37 | Guest0 | hahaha yeah |
| 20:35.41 | lkjasdf | "If you are not running XScreenSaver on Linux, then it is safe to assume that your screen does not lock." --- the Xscreensaver author, highly biased, but with legitimate reasons and evidence |
| 20:36.13 | rrq | xautolock -time 5 -detectsleep -locker /usr/bin/xtrlock -b -corners 00-+ -cornerdelay 10 -notify 10 -notifier /usr/bin/play -v 0.1 /home/ralph/Sounds/860_1245242569.mp3 |
| 20:36.16 | lts | "physlock -l && <any fancy screensaver you want> && physlock -L" is nice. Failure of screensaver will still lock you to a dedicated empty TTY. |
| 20:36.57 | gnarface | oh yea, to be clear, xscreensaver is not actual security software. everyone should know that already. |
| 20:37.20 | gnarface | i merely advocate it for display wear-leveling |
| 20:38.34 | gnarface | the problem with any screensaver software is if you kill it somehow, you've unlocked the screen then |
| 20:42.51 | *** join/#devuan AnimaInvicta (~AnimaInvi@ber27-1-78-230-215-86.fbx.proxad.net) |
| 20:44.22 | user__ | First time I read about physlock |
| 20:45.51 | user__ | lts: does physlock package install an /etc/init.d/ script? |
| 20:46.07 | user__ | no |
| 20:46.21 | lts | ..and I remembered wrong. That command string was for removing ability to change tty during screensaver. What I meant was "<your fancy screensaver command> || physlock" |
| 20:46.37 | lts | You don't run it from a service though |
| 20:46.42 | *** join/#devuan _william_ (~william@lfbn-cle-1-138-151.w2-3.abo.wanadoo.fr) |
| 20:46.46 | user__ | what's the command again for cli auto timeout / logout ? |
| 20:46.57 | user__ | lts: it has a -d option |
| 20:47.06 | lts | Hmm, never used that |
| 20:47.25 | mason | gnarface: xscreensaver breaks on my workstation lately |
| 20:47.43 | gnarface | mason: i assume it's just certain screensavers |
| 20:48.33 | gnarface | mason: try stuff like space and rain |
| 20:49.08 | gnarface | the old pixel-based ones are the ones that suffer from the least video driver compatibility issues |
| 20:49.19 | mason | gnarface: boxfit in this case - might be some interaction with nVidia, since there isn't a similar flakiness on my laptop, which has Intel graphics. |
| 20:49.58 | mason | gnarface: I'll try something different. I've not been able to isolate a trigger, but the process just goes away. |
| 21:03.25 | user__ | <ot> is that Mars landing on some live yt channel? |
| 21:03.55 | user__ | yes, found |
| 21:04.31 | mason | user__: NASA TV anyway, possibly YouTube as well - https://www.nasa.gov/multimedia/nasatv/#public |
| 21:04.54 | mason | user__: Note that #devuan-offtopic exists. |
| 21:07.31 | *** join/#devuan kiwi9 (~john@2001:8003:6da8:c01:2d8:61ff:fe7b:961b) |
| 21:11.06 | *** join/#devuan AndyGB (79b0175b3b@cappuccino.street.me.uk) |
| 21:15.32 | *** join/#devuan ephemer0l_ (~ephemer0l@pentoo/user/ephemer0l) |
| 21:25.38 | *** join/#devuan terabit (sid146285@gateway/web/irccloud.com/x-tikxqbfsdcwvwxiq) |
| 21:34.15 | *** join/#devuan ac_laptop (~ac_laptop@186.2.247.129) |
| 21:44.08 | *** join/#devuan bru (~bru@181.31.19.187) |
| 22:11.39 | *** join/#devuan lagfra (~fra@host-79-41-72-188.retail.telecomitalia.it) |
| 22:23.12 | *** join/#devuan _william_ (~william@lfbn-cle-1-318-193.w90-52.abo.wanadoo.fr) |
| 23:47.33 | *** join/#devuan markizano (markizano@2600:3c00::f03c:92ff:fe86:b66e) |
| 23:55.59 | *** join/#devuan Xenguy (~Xenguy@devuan/community/Xenguy) |