<r0ni>
yall going with yarl 1.20.1 too huh, it's tagged 1.21.1 yet the files are 1.20.1... dont pull down using a $version in a pkgfile likely unless they fixed it by now
<r0ni>
unless one dont pull from github maybe, prob fine on pypi or whatnot
lavaball has quit [Remote host closed the connection]
serpente has joined #crux
lavaball has joined #crux
<frinnst>
are there no attempts at notification emails when an update breaks abi these days? or am I looking in the wrong place?
<cruxbot>
[contrib/3.8]: firefox: updated to version 139.0.4
<farkuhar>
frinnst: Which update are you referring to? I was surprised that the latest xkeyboard-config update did not come with a [notify] commit message, informing us that pkgadd would need to be invoked with the -f flag (due to pkgadd's broken symlink handling, causing false-positive reports of conflicting files).
<farkuhar>
ukky gave us this patch to fix how pkgadd handles ports that rearrange their footprint, with symlinks replacing the old directories. https://0x0.st/8bDs.patch But the original pkgadd will refuse to perform the update under such circumstances, when called without -f.
<cruxbridge>
<jloc0> qt6-5compat has the same fail locally as xkeyboarda-config did
lavaball has quit [Remote host closed the connection]
braewoods has quit [Remote host closed the connection]
braewoods has joined #crux
<jaeger>
If the maintainer forgets to add the notify tag :(