09:34 <SiFuh> zorz: You are here

10:52 <ppetrov^> SiFuh, zorz is still here

10:53 <SiFuh> Interesting.

10:53 <ppetrov^> zorz, SiFuh finds your presence here interesting

10:54 <SiFuh> Totemo kyomi no aru

11:14 <SiFuh> ppetrov^: farkuhar hasn't been here for two days

11:19 <SiFuh> ppetrov^: You have left.

14:34 <SiFuh_> https://sputnikglobe.com/20250327/signal-deep-states-cia-tool-to-frame-team-trump-1121698488.html

15:39 <SiFuh> ukky: Still functions like the normal handle except it doesn't return into the flattened state automatically like the original rubber handle would do. So you need to manually slide it into a flattened state.

17:51 <zorz> yes interesting

17:53 <SiFuh> zorz: Yeah but you are not interesting :-P

17:57 <zorz> Yeahhhhhhh

20:46 <SiFuh> remiliascarlet: https://www.infowars.com/posts/watch-renowned-doctor-drops-vaccine-bombshells-on-rogan-exposes-polio-eradication-myths/ This alone proves AlienBob a fucking idiot in slackware and I knew about this in the 90's but he defends it by blocking me

20:47 <SiFuh> remiliascarlet: The mor I learn about how right I was the more I discover how much of a fucking child he is.

21:15 <farkuhar> bsdtar(1) promises that "The complete list of modules and keys ... for extract and list modes [can be found] in archive_read_set_options(3)", but the latter man-page is not nearly so extensive as the examples section in bsdtar(1). Nevertheless, there doesn't seem to be a way to leverage TAR_READER_OPTIONS to accomplish the --no-xattrs flag that frinnst needed for the sshfs tarball.

21:23 <farkuhar> Interestingly, --no-xattrs is claimed to be the default behaviour when bsdtar is run as a non-root user. If we had endowed pkgmk with the ability to escalate privileges only as needed, rather than for every step from downloading to unpacking and building, then frinnst would have an even simpler way to avoid the bsdtar error.

21:26 <farkuhar> For generating the correct footprint of a built package, we could have just invoked bsdtar on the contents of $PKG with flags "--uid 0 --gid 0" whenever pkgmk detects that it is being run as a non-root user. The resulting footprint will usually be correct, except for daemon ports where the owner and group are not root:root; those ports really do need fakeroot.

23:56 <farkuhar> darfo's ability to hold two seemingly contradictory positions (April 2024: linux-pam in core is fine; February 2025: "I *really* don't like libbsd in a Linux system. It belongs in a BSD system.") makes it easy to accuse him of reading too much into the name of the port. If linux-pam had been named plan9-pam instead, would he have been so willing to defend its inclusion in core?