00:03 <cruxbot> [contrib/3.7]: docker-compose: updated to version 2.26.1

00:03 <cruxbot> [contrib/3.7]: docker-buildx: updated to version 0.13.1

00:03 <cruxbot> [contrib/3.7]: docker: updated to version 26.0.0

00:03 <cruxbot> [contrib/3.7]: containerd: updated to version 1.7.15

05:10 <cruxbot> [contrib/3.7]: assimp: 5.3.1 -> 5.4.0

05:10 <cruxbot> [contrib/3.7]: python3-flask: 3.0.2 -> 3.0.3

05:10 <cruxbot> [contrib/3.7]: python3-rapidfuzz: 3.8.0 -> 3.8.1

05:18 <cruxbot> [compat-32/3.7]: gnutls-32: 3.8.4 -> 3.8.5

05:18 <cruxbot> [compat-32/3.7]: mpg123-32: 1.32.5 -> 1.32.6

05:18 <cruxbot> [compat-32/3.7]: mtdev-32: 1.1.6 -> 1.1.7

05:18 <cruxbot> [compat-32/3.7]: xorg-libx11-32: 1.8.8 -> 1.8.9

05:22 <cruxbot> [compat-32/3.7]: libtiff-32: 4.6.0 -> 4.6.0t

05:22 <cruxbot> [opt/3.7]: libtiff: 4.6.0 -> 4.6.0t

12:22 <ukky> Note to myself: We need a way to protect files when install location changes. Currently, pkgadd removes user-modified-and-protected file, for example /usr/lib/iproute2/rt_tables, when its location changes to /usr/share/iproute2/rt_tables.

13:16 <cruxbot> [core/3.7]: libarchive: updated to version 3.7.3

15:38 <farkuhar> ukky: FS#1074 offered a few patches, most recently http://sprunge.us/gKluVV which works with pkgadd.conf to prevent deleting user-modified and protected files (usually under /etc but could also be in /usr/lib if you write such UPGRADE NO directives).

16:10 <ukky> farkuhar: thanks. I guess the patch was not approved/adopted/accepted/considered. 'jmq' repo does not have pkgutils fork. Do you maintain local repo with your changes? I will switch to your version.

16:16 <farkuhar> ukky: I did install a local fork of pkgutils with that patch applied, but I didn't set up a public repo with those changes. Flyspray tasks weren't getting much consideration in the months before switching to Gitea, anyway. We have a new bugtracker in place, so I might open a pull request to restart the discussion.

16:20 <farkuhar> it's already one of the bullet points under Pkgutils in https://crux.nu/Wiki/TODO37-1 but in the absence of any firm plans for the next CRUX release, a separate Gitea issue might be warranted.

16:23 <ukky> farkuhar: Can you share a diff file with all your private patches for pkgutils?

16:44 <farkuhar> ukky: I think FS#1074 is the only bug I bothered to patch locally. Other features are just "nice-to-have", not worth deviating too much from the official pkgutils.

16:51 <farkuhar> FS#15 (symlink handling) is a recurring annoyance, but the track record of proposed fixes seems to discourage new attempts, or at least to temper the enthusiasm of anyone who thinks they've figured out how to solve it. https://lists.crux.nu/hyperkitty/list/crux-devel@lists.crux.nu/thread/X3QDPEJNUMFGPB62BYOS6IPEYLIA5GXV/

17:08 <ukky> WRT FS#15, if it would be me, I would add special symbol to every symlink (@) in /var/lib/pkg/db to avoid dereferencing each path on a real filesystem, similar to the output of 'ls -1 --file-type <path>', and then dereference path if symlink is part of the full file name. This should speed up DB processing when there are 100,000 files in the footprint.

17:27 <SiFuh> jaeger: You should have a partial eclipse today where you are

18:17 <jaeger> yes

18:29 <SiFuh> We had one a couple of years ago here. I didn't bother to go outside. But I did see everything go from bright to brown.

18:55 <jaeger> I'm not in the path of totality here so it's a little less impressive than it could be. With that said, I traveled for the one in 2017 to be in the path of totality and it was very cool to see everything go dark at lunch time.

18:58 <SiFuh> jaeger: Nice

19:04 <dlcusa> I decided the forecasts did not justify the expedition when guessing how much congestion would obtain. Indiana overperformed, but c'est la vie.

19:05 <SiFuh> C'est la vie

19:43 <cruxbridge> <jloc0> It’s got dusk-like dark here, but the ominous church bells made it extra creepy. Kept waiting for rapture, but it’s never my lucky day :(