=== popey_ is now known as popey [09:57] ricotz, mamarley: I downloaded the tarballs for 390.59, but I get a warning when extracting, and the amd64 installer is extracted in the main directory, not in "amd64" https://paste.ubuntu.com/p/39q9DBytcH/ [09:58] I'm going to create a new tarball [09:59] Note: you can download and create the tarballs with "debian/rules get-orig-source" [10:03] tseliot: Cool, where does that get the .run files for the tarball? [10:04] mamarley: yep, it downloads the installers, creates the directories and the tarballs. You only have to move the tarballs out of the main directory, when you're done. [10:05] tseliot: Is there any way to do that for drivers not downloaded from the main download site, such as Vulkan development drivers or drivers extracted from the CUDA installer? [10:06] mamarley: if you change the urls and the names in debian/rules.defs, I think things will work [10:07] OK, thanks! That is definitely easier than manually creating the tarballs, which is what I had been doing. [10:07] :) [10:08] And less error-prone too, because I somehow screwed up the 390.59 one apparently. I'm still not sure how it could build if it was extracted to the wrong directory though. [10:10] tseliot, sorry for missing that, but the tarball is not wrong, having a subfolder in them is what is confusing since they are dropped on extracting by dpkg [10:11] the suffix e.g. -amd64 defines the resulting destination directory inside the source-folder [10:12] ... if there is only one file in the archive [11:07] ricotz: I know it's kind of confusing [11:09] tseliot, better don't "prepend" the subfolder while creating the tarball [11:10] those warnings has nothing to do with it, I assume the archives are generated by e.g. file-roller and not plain tar [12:56] ricotz: I think I took the get-orig-source functions from Debian, and I tweaked them a bit