=== pieq_ is now known as pieq === xevious_ is now known as xevious === pieq_ is now known as pieq [08:05] tjaalton, hello, do we have any reason for ocl-icd being at a really old version? [10:30] * LocutusOfBorg does sync it [10:34] bad rafaeldtinoco not forwarding kronosnet patches to Debian... [10:34] * LocutusOfBorg does it [10:34] oh somebody tried to do a merge request [10:47] didnt I ? [10:47] now I got push rights to debian-ha #) [10:50] oh, bryce's i386 ones.. I see now [10:50] wasn't sure I should fwd it back then, as we were doing all the i386 moves in focal, thx for fwding [11:26] rafaeldtinoco, so if you want to merge, there is my pr now open [11:27] https://salsa.debian.org/ha-team/kronosnet/-/merge_requests/2 [11:27] I would also close the other one [11:36] LocutusOfBorg: will do [11:38] ta! [13:02] rafaeldtinoco, don't forget to close the other pull request please :D [13:20] I did altogether [13:34] thanks! [14:32] GunnarHj: hey! Would you be fine for me to release all the updated focal base langpack packages to -updates? [14:33] s/for me to release/with me releasing/ [14:35] sil2100: Yes, I see no reason why you wouldn't. Haven't seen any regression myself, and have not seen any reports which would indicate a problem. [14:54] GunnarHj: thanks! === AdmWiggin is now known as tianon [16:27] Hello! I've registered the issue https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257 and found a solution. Since it's the first time I try to apply a fix in an Ubuntu bug report, can some dev tell me if its in a correct form or if something else is needed? [16:27] Launchpad bug 1887257 in grub2 (Ubuntu) "update-grub does not create any entry on grub.cfg for ZFS on root" [Undecided,New] === ijohnson is now known as ijohnson|lunch === ijohnson|lunch is now known as ijohnson [18:26] pqatsi: maybe attach also the set -x output after your change, so the diff between them can be compared? [21:04] sarnold: I can make it too, but the bug got awnsered and I need to check that condition [21:30] pqatsi: aha I see juliank had my similar concerns but came to a better conclusion :D [23:25] sarnold: Indded juliank is right, but I did not made any manual change here, so I'm trying (Without sucess) to find out who is the package that changed the default sh link. [23:25] I remember a old discussion about the dash issue (And why bash is not used) and all the effects on system. I'm also checking scripts at /var/lib/dpkg/info but no much sucess here :( [23:34] sarnold: Only thing I found here is bash.postinst that sets a link to sh if no other link is found. Dash also does have a function like this, but with more strict checks [23:35] For some reason may be bash being configured before dash anyways or after some update? [23:36] pqatsi: mm, maybe if one or the other were stuck in half-configured state, then the other one were run, maybe? [23:37] sarnold: Dunno. I know some ubuntu internals and etc, but in this computer I use it as i'm a dumb, restricting me to use zfs (For testing and docker) and some apt install commands. This is why I cant understand what happened here. [23:38] wow you weren't kidding about the dash postinst, that's involved.. [23:38] sarnold: no no, im reading the files to find what can be changed the link. I never touched on dpkg-reconfigure as example [23:38] (Ah, sorry, I understood wrong what you said) [23:39] dash.postinst and bash.postint handles the symlink [23:39] I'm considering remove the link and try dpkg-reconfigure dash [23:40] This issue with grub happened after some big update here and I guess it was before 5.4.0-32 kernel version was launched, since my updates stucked at this kernel