[02:59] <arraybolt3> Liver_K: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408
[03:00] -ubottu:#ubuntu-server- Launchpad bug 2006408 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-uvm module does not exist, making CUDA unusable with the 390 driver" [Undecided, New]
[03:00] <Liver_K> Thanks again arraybolt3 
[03:00] <arraybolt3> Never heard back from Oblomov, so I tried to describe the problem and put that in the report. If I misunderstood something, lemme know so I can edit it.
[03:01] <Liver_K> Yeah #opencl is a very very low traffic channel
[03:02] <Liver_K> Ooo arraybolt3 you should include ocl along with CUDA
[03:02] <Liver_K> They both require it
[03:02] <Liver_K> In fact ocl was my intended use case XD
[03:22] <arraybolt3> Liver_K: Done.
[03:24] <Liver_K> Also, what is this "source package" thing it shares with the desktop driver?
[03:25] <Liver_K> arraybolt3: nvidia-graphics-drivers-390
[03:26] <arraybolt3> There's two kinds of packages in Ubuntu - binary and source packages. Binary packages are the things you install, source packages are the source code (or source files) that the binaries are built from.
[03:26] <arraybolt3> Oftentimes multiple binary packages are produced by building a single source package.
[03:26] <Liver_K> Ah I saw "package" and thought immediately of the binary
[03:45] <Liver_K> arraybolt3: Do you think this bug will actually get fixed?
[03:45] <Liver_K> Like in the foreseeable future?
[03:46] <sarnold> ± apt-file search nvidia-uvm.ko | wc -l
[03:46] <sarnold> 5343
[03:46] <sarnold> omg
[03:48] <sarnold> oh hrm those are all .sig files.
[03:53] <Liver_K> I mean the sources are there at /usr/src/nvidia-390.157/nvidia-uvm/
[03:53] <Liver_K> Dunno what I can do with those if anything
[12:43] <ahasenack> sdeziel: hi, would you like to give my rsyslog packages with apparmor a try?
[12:43] <ahasenack> they won't change existing enforcement mode, but the apparmor profile has "news" (documented in d/NEWS and d/README.apparmor)
[12:44] <ahasenack> on fresh installs, however, it will put the profile in enforce mode
[12:44] <ahasenack> just won't touch the confimenent mode on upgrades
[12:46] <ahasenack> it's in https://launchpad.net/~ahasenack/+archive/ubuntu/rsyslog-apparmor-dep8-take4. The build with the mentioned docs is currently still happening
[12:46] <ahasenack> I'm dynamically handling mysql, postgresql, gnutls and openssl
[12:47] <ahasenack> omprog is one I doubt I can handle for now, I would need to be able to properly parse the rsyslog conf to catch that. The conf can be in 3 formats! (very old, old, and rainer script)
[13:54] <patdk-lap> I'm suprised it's only 3 formats, it feels like every major version is a new config format
[14:11] <sdeziel> ahasenack: of course, will do!
[14:11] <ahasenack> patdk-lap: well, it can be 3 formats at the same time, in the same config :)
[14:23] <patdk-lap> I know, I keep having to change config formats to work around bugs, it's annoying
[17:23] <inscw00table> I've seen a couple times during an autoinstall from ubuntu-22.04.1-live-server-amd64.iso it fails apt-get install on the first entry in my 'packages' clause, claiming the package is not found.  Anyone happen to know how subiquity configures/uses the mirrors setup in the 'apt' section?  I find no reference to them in etc/apt on the target install fs as I would have expected.
[21:28] <effendy[m]> inscw00table: is the package not part of the main ubuntu repository?
[21:28] <effendy[m]> I'm guessing you're ruling out any syntax problem, like wrongly specifying the version and that?