guru____________ | I just installed libsdl2-dev:i386 and I created chaos: https://pastebin.com/BePUw5NX | 05:30 |
---|---|---|
guru____________ | i'm multiarch | 05:31 |
guru____________ | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905624 | 05:36 |
guru____________ | oh crap | 05:36 |
guru____________ | The following partially installed packages will be configured: | 05:42 |
guru____________ | gir1.2-ibus-1.0 gir1.2-ibus-1.0:i386 libibus-1.0-dev:i386 libsdl2-dev:i386 | 05:42 |
terra | Hi, is there a gtk2 variant of lightdm-gtk-gteeter? Current one is gtk3 based and pushes lots of unnecessary dependencies. | 07:53 |
armin | wow, bash 5. it's a thing nao. https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00063.html | 08:53 |
errandir1 | kernel 5, bash 5. Is 2019 the "year of 5"? | 10:44 |
debdog | high five on that! | 10:46 |
g40 | Hi all. Using Devuan as the RFS on an Arm64 system. It seeds from `bootstrap-devuan-arm64-stage3.tgz`. Only problem is I cannot recall where I sourced this file. Ring any bells? | 10:49 |
KatolaZ | g40? | 10:52 |
KatolaZ | are you using arm-sdk? | 10:52 |
g40 | Hi KatolaZ, no. I could never get it to work properly with our slightly odd u-boot/kernel requirements. | 10:55 |
KatolaZ | g40: that file would probably come from files.devuan.org/devuan_ascii/embedded ? | 11:02 |
g40 | KatolaZ, thanks but I'd checked there. No obvious signs ... | 11:09 |
nyov | Is there something wrong with the package repo keyrings? I have installed the devuan-keyring package 2017.10.03 but I get key-errors with both deb.devuan.org and auto.mirror.devuan.org repos? | 15:20 |
nyov | W: GPG error: http://deb.devuan.org/merged ascii InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BB23C00C61FC752C | 15:20 |
nyov | W: GPG error: http://packages.roundr.devuan.org/merged jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB | 15:20 |
KatolaZ | nyov: this is really strange | 15:21 |
KatolaZ | nyov: can you see the keys in `apt-key list` ? | 15:21 |
nyov | apt-key list | grep devuan shows them | 15:22 |
nyov | /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.gpg, /etc/apt/trusted.gpg.d/devuan-keyring-2016-cdimage.gpg, /etc/apt/trusted.gpg.d/devuan-keyring-2017-archive.gpg | 15:22 |
KatolaZ | nyov: which signature is failing? | 15:22 |
nyov | well it says NO_PUBKEY BB23C00C61FC752C NO_PUBKEY 94532124541922FB | 15:23 |
KatolaZ | (well, the problem is probably not there, since it says "NO PUBKEY") | 15:24 |
KatolaZ | indeed | 15:24 |
KatolaZ | which command are you using? | 15:24 |
nyov | apt-get update :) | 15:25 |
nyov | oh wait | 15:25 |
KatolaZ | did you change the permissions on those key files, by any chance? | 15:25 |
KatolaZ | (it shouldn't matter anyway, since those are pubkeys...) | 15:25 |
nyov | wait a second. I did aptitude update, actually | 15:26 |
KatolaZ | still... | 15:26 |
nyov | apt-get update seems to work.... gpg failure? | 15:26 |
KatolaZ | could you please try apt-get update? | 15:26 |
KatolaZ | nope | 15:26 |
KatolaZ | if apt-get update works, then the keys are there | 15:26 |
KatolaZ | and are OK | 15:26 |
KatolaZ | are you on ascii? | 15:27 |
nyov | mostly. oh well, if it's an aptitude/gpg error, I have things covered | 15:27 |
nyov | thanks for the help | 15:28 |
KatolaZ | nyov: are you on ascii? | 15:28 |
nyov | mostly | 15:29 |
KatolaZ | o_O | 15:29 |
MinceR | >year of 5 | 15:37 |
MinceR | system 5? | 15:37 |
nyov | ah, to solve my apt mystery; it was a bad gpg file in /etc/apt/sources.list.d/. looks like that prevented apt from finding some but not all keys... | 15:48 |
g40 | anyone familiar with eudev? I'm seeing it apparently hang while the bootlog has 'synthesizing the initial hotplug events'. As this is test of a new board hotplug etc. not really required. Any thoughts on disabling and/or debugging? TIA | 16:27 |
gnarface | g40: i've never had that issue with it. have you tried isolating the hang to a specific device? | 17:09 |
g40 | @gnarface. Hi, thanks. No, I'm slowly working thru a list of blocks to disable in the device tree. No fun. | 17:46 |
* Digit wonders about installing trinity in devuan ceres, searches, finds https://wiki.trinitydesktop.org/Devuan_Trinity_Repository_Installation_Instructions and wonders if that's the optimal route to take | 17:46 | |
gnarface | g40: unless you have significantly strange hardware, hotplug is most likely exclusively dealing with USB devices | 17:47 |
gnarface | so that can probably shorten your troubleshooting process a lot by just unplugging them all then trying to boot with one at a time | 17:48 |
gnarface | presumably you can re-trigger hotplug after boot though too, which might be a faster procedure than rebooting | 17:48 |
gnarface | Digit: it's usually a mistake to mix distros | 17:51 |
gnarface | the damage may not always be immediate or obvious. it usually shows up by sabotaging a system upgrade, months or years later | 17:52 |
Digit | gnarface: unless bedrocklinux, right? hehe. but yeah, i was just wondering about how to install trinity in devuan. | 17:52 |
gnarface | Digit: distros like ubuntu that casually encouraging mixing 3rd party repos usually are not immune to the negative side-effects. rather they just promote a culture of ignoring the problem. | 17:53 |
gnarface | Digit: the officially recommended approach in cases like this (for Debian *or* Devuan) is to build a binary package from the source package yourself, taking care to fix any dependency tangles preemptively | 17:54 |
gnarface | that said, if the debian package doesn't depend on anything not in devuan (like systemd) then you probably will get away with it | 17:55 |
gnarface | just... be careful when you're actually installing it if you go that way. take a backup first if you can. and make sure to pay attention to any extra packages it wants to pull in (typically if there are any at all that is bad) | 17:57 |
gnarface | and know that this is the type of action that can make a mistake that can't be cleaned up | 17:57 |
gnarface | i can't speak authoritatively about the 3rd party packages from "Slávek Banko" they mention. they might be legit, they might not. i have no idea who that is. | 17:59 |
g40 | @gnarface. Indeed but it never makes it to a console. just hangs. how can I disable (e)udev? Is this a kernel thing? | 18:21 |
Digit | yeah, just looking what it would want to install, with the repo added to sources.list in a way it doesnt error, looks too much (even for a de). methinks i'll stick to my prior plan, just get trinity from slackel, in bedrock. that way my devuan can stay pristine. | 18:21 |
gnarface | g40: it's the thing that populates /dev. you kinda need it unless you're really good with mknod | 18:22 |
gnarface | there are alternatives but i don't know if any are in better shape than eudev | 18:23 |
gnarface | there was going to be a vdev ... dunno what the status of that is though now | 18:23 |
* Digit comments out the trinity repos, adds a comment reminder, and updates apt's available packages list again | 18:23 | |
Digit | s/slackel/q4os/ | 18:25 |
gnarface | g40: to be clear, i still think there's a good chance you're facing some sort of hardware failure. do you get the same freeze with udev as eudev? | 18:26 |
gnarface | g40: if so, that supports my concern about a hardware issue. if not, then you've found a bug in eudev and you should report it. | 18:26 |
gnarface | i don't think vdev is in the repos anywhere yet, but someone here might know where you can get a good devuan-safe build | 18:27 |
gnarface | Digit: yea, i'd try again after being fully updated, but if it still wants to drag in a pile of dependency packages from their repo instead of devuan's, then i'd definitely advise against doing that | 18:28 |
g40 | Problem is which bit of the hardware. It's a complex SoC (AllWinner H5 quad core). Image boots fine on reference system. At this point having hotplug capabilities is luxury. Just wanna see if we can get this sucker to a console prompt | 18:29 |
gnarface | g40: OH, ... ARM hardware. so in theory this could be a issue with your u-boot build too. that changes stuff. i can't really help you much more, but i can tell you that you should ask about this in #devuan-arm and maybe also #linux-sunxi | 18:30 |
gnarface | Digit: (the primary cause for rebuilding it yourself would be to correct the package dependencies so it only asks for stuff you can get from the devuan repos) | 18:31 |
g40 | @gnarface. Cool. I really appreciate the help. Thank you. | 18:31 |
gnarface | g40: no problem, good luck | 18:31 |
gnarface | g40: which allwinner H5 quad-core, out of curiosity? | 18:31 |
gnarface | the pine64 by any chance? | 18:31 |
gnarface | they also have their own IRC network and channel | 18:32 |
g40 | Final question. I asked this earlier but may have got lost in translation. I am building Devuan RFS from bootstrap-devuan-arm64-stage3.tgz. Does anyone recoginize where this file may be originated? Is it from the SDK builder or some download on Devuan? | 18:32 |
gnarface | but they have a lot of overlap with the more generic #linux-sunxi channel | 18:32 |
KatolaZ | g40: I asked you if you were using arm-sdk and you said you are not | 18:33 |
g40 | @gnarface - custom design. for our sins. | 18:33 |
gnarface | ah, gotcha | 18:33 |
KatolaZ | g40: that looks like the bootstrap file generated by arm-sdk after it has installed the base system | 18:33 |
KatolaZ | but if you are not using arm-sdk, I don't know where it comes from, TBH | 18:34 |
gnarface | g40: ^ this guy builds devuan arm images. he knows stuff. | 18:34 |
g40 | Hi @Katolaz. Indeed and that is the truth. But memory fails me. It is the one part of our RFS builder whose provenance eludes me. | 18:34 |
KatolaZ | g40: I don't know that "our RFS builder" is and what it does, so I can't answer that question :P | 18:36 |
gnarface | g40: if it came out of devuan it probably came from git.devuan.org somewhere | 18:37 |
g40 | @KatolaZ. Think you call it the arm-sdk. I've been all over git.devuan.org but find no clues. | 18:37 |
KatolaZ | g40: arm-sdk is a specific piece of software | 18:42 |
KatolaZ | https://git.devuan.org/sdk/arm-sdk <- g40 | 18:43 |
KatolaZ | just search for "arm-sdk", literally | 18:44 |
g40 | @KatolaZ I will have to reinstall that and build to see what it produces. Thanks. | 18:47 |
KatolaZ | g40: you can actually store a stage4 tarball as well, if you want | 19:08 |
KatolaZ | just set "TAR_STAGE4=true" in the config file | 19:08 |
g40 | @KatolaZ. I will dig in and let you know how far I get. Thanks again. | 19:14 |
KatolaZ | g40: np | 19:15 |
xkr47 | oh would I love to run Devuan on this one.. https://www.indiegogo.com/projects/cosmo-communicator#/ | 22:26 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!