sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
crabbedhaloablut has joined #dri-devel
i509vcb has quit [Quit: Connection closed for inactivity]
Haaninjo has joined #dri-devel
macslayer has quit [Remote host closed the connection]
AnuthaDev has joined #dri-devel
fab has joined #dri-devel
junaid has quit [Remote host closed the connection]
AnuthaDev has quit []
glennk has joined #dri-devel
AnuthaDev has joined #dri-devel
fab has quit [Ping timeout: 480 seconds]
sima has joined #dri-devel
nirmoy has quit []
gouchi has joined #dri-devel
gouchi has quit []
heat has joined #dri-devel
pcercuei has joined #dri-devel
pH5 has joined #dri-devel
Leopold_ has quit [Remote host closed the connection]
mclasen has joined #dri-devel
Company has joined #dri-devel
bazsi has joined #dri-devel
AnuthaDev has quit []
kts has joined #dri-devel
bazsi has quit []
kts has quit [Quit: Leaving]
mclasen has quit []
mclasen has joined #dri-devel
AnuthaDev has joined #dri-devel
mclasen has quit [Ping timeout: 480 seconds]
bazsi has joined #dri-devel
bazsi has quit []
<mareko>
DavidHeidelberg: that would never happen, Mesa is tightly dependent on libdrm, they both advance in lockstep, when the libdrm version is bumped, 99% of the time we need to bump the Mesa->libdrm requirement the same day
ap51 has joined #dri-devel
<mareko>
DavidHeidelberg: it's never a good idea to use libdrm from the distro with mesa/main
<mareko>
DavidHeidelberg: libdrm changes are mostly made when Mesa needs them, and when Mesa needs them, it needs them immediately
<mareko>
DavidHeidelberg: the gitlab-ci change doesn't work for all jobs, and I'm out of ideas
heat has quit [Remote host closed the connection]
<mareko>
DavidHeidelberg: the other project that is problematic to use from the distro is llvm
<mareko>
debian having too old LLVM has been a problem in the past to the point that we considered removing the jobs from the CI because it was too much pain in the ass
heat has joined #dri-devel
Leopold has joined #dri-devel
AnuthaDev has quit []
<mareko>
llvm could be installed from the llvm.org apt source
Leopold has quit [Remote host closed the connection]
Leopold__ has joined #dri-devel
<mareko>
DavidHeidelberg: sorry if some of my comments were harsh
glennk has joined #dri-devel
<eric_engestrom>
FWIW, at the time I said that it was a mistake to remove the "build libdrm locally" code in favour of installing from debian repos just because debian had just updated its libdrm; I said that we were going to have to revert all that code sooner or later... looks like we have reached that point 🤷
<karolherbst>
mareko: looks like virglrender needs libdrm, and if you force remove it, it can't find it anymore
<karolherbst>
or if you don't install it
<karolherbst>
but it's kinda weird, because I don't see it being removed in that `debian/x86_64_test-base` job
<karolherbst>
mareko: +1 to using llvms deb repos
<karolherbst>
and we should just use those going forward
Leopold__ has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
<DavidHeidelberg>
eric_engestrom: or we could just install recent libdrm package..
<DavidHeidelberg>
mareko: can I propose just doing "wget $pkg && dpkg -i $pkg && rm $pkg" please?
<DavidHeidelberg>
I can give you the commit / sent the MR
rasterman has joined #dri-devel
<eric_engestrom>
DavidHeidelberg: sure, but even if we maintain our own packages, this is still quite the burden for driver devs, and really pointless for something tiny like libdrm
<eric_engestrom>
for deqp it's a good idea, but not for libdrm
<DavidHeidelberg>
hmm, I see it's not bumped yet and I don't have deb-ci-repo ready yet; for the ugly stuff, I would just override the libdrm and kept the package installed
kts has joined #dri-devel
junaid has joined #dri-devel
Leopold_ has joined #dri-devel
kts has quit [Quit: Leaving]
junaid has quit [Remote host closed the connection]
iive has joined #dri-devel
camus has quit []
mclasen has joined #dri-devel
fab has joined #dri-devel
fab is now known as Guest11698
mclasen has quit [Ping timeout: 480 seconds]
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #dri-devel
ap51 has joined #dri-devel
<karolherbst>
or we just built it and install it system wide. Do we have any dependencies installed actually needing libdrm?
<karolherbst>
there is no point using packages if it's just annoying us
Leopold_ has quit [Remote host closed the connection]
<karolherbst>
which with libdrm is the case, so we should just build it ourselves _forever_
<karolherbst>
and using debian's package was a mistake imho
<karolherbst>
which we shouldn't repeat
<karolherbst>
and if debian makes this a pain for us, maybe using debian was a mistake...
<karolherbst>
and I think pinning the libdrm version in CI also gives us the advantage, that libdrm bumps are actually done correctly (in some sense). There is this "depending on the config we use a certain version" but at least disitributions go with the highest one there anyway
<karolherbst>
and then _if_ we wnated to replicate that via a deb rep, we'd have to keep all versions we care about (from all stable branches) and CI needs to install the specific version we need. Building libdrm inside CI kinda sounds like the easier and better solution here...
<karolherbst>
also.. other package managers have the option to mark a package as installed even though it isn't. Couldn't find if apt supports, some others do.
<karolherbst>
(the idea here is, that you compile and install system wide, and then tell the package manager it's already taken care of and it can just assume it's there)
Duke`` has joined #dri-devel
Coelacanthus[m] has quit []
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
cgsif^ has quit [Ping timeout: 480 seconds]
i509vcb has joined #dri-devel
cphealy has joined #dri-devel
<robclark>
DavidHeidelberg: it is useful to be able to build libdrm from a libdrm MR sometimes.. not for marge pipeline necessarily, but in other cases