IRC channel logs

<damo22>azeem: it syncs the tree every so often and runs a build against master after it is committed

<damo22>only if there are new commits

<damo22>we got our first error reports

<damo22>interesting, ERROR tests/test-gsync (exit status: 99) on i386

<damo22>ive not seen i386 fail for a long time

<damo22>maybe it timed out?

<damo22> https://lists.gnu.org/archive/html/commit-hurd/2026-08/threads.html

<damo22>i think it timed out and the other test that was non-user32 failed because of some new logging for FS/GS interfering with the end marker?

<damo22>so two of those fails are spurious, 6 are real

<sam_>I was about to reply to the -Werror thread but youpi said everything I was going to :)

<sam_>we can add some --enable-werror/--disable-werror to configure if people want that and have the default value depend on if we're building a release or not, I guess, but personally I'd rather not bother

<yang3>Could someone help me solve these signature verification errors? http://pastie.org/p/05cDGkD9HWkqJpCejJf6oZ/raw

<yang3>i tried importing gpg keys manually, but it didn't have much effect

<youpi>yang3: did you put trusted=yes as documented ?

<yang3>These are the sources http://pastie.org/p/5D84QamhJL6cXvEr6n4uvi/raw

<youpi>have you tried sticking with the .bak version ?

<youpi>I don't know if the modernized version has all the behavior that we need

<yang3>ok

<yang3>I'll remove the i moved /etc/apt/sources.list.d/* to some other directory (backup) and now it seems to work

<yang3>I moved /etc/apt/sources.list.d/* to some other directory (backup) and now it seems to work

<yang3>still getting a PGP signature verification problem http://pastie.org/p/0Qf0EERU7q70G4qm0vE9H8/raw

<youpi>that is just a warning

<yang3>can I get rid of that?

<youpi>by adding the proper key, I haven't investigated how

<yang3>gpg --keyserver keyserver.ubuntu.com --recv-keys 3AF65F93D6FBC5B9

<yang3>gpg: keyserver receive failed: Translator died

<yang3>checking on another machine, it's an expired key

<yang3>pub rsa4096 2024-01-05 [SC] [expired: 2026-02-01]

<yang3> 519759FBC670BFA6C87E42413AF65F93D6FBC5B9

<yang3>uid [ expired] Debian Ports Archive Automatic Signing Key (2025) <ftpmaster@ports-master.debian.org>

<youpi>yes, that's the problem with snapshot.debian.org, that's essentially unsolvable

<youpi>thus why putting trusted=yes

<youpi>and check-valid-until

<yang3>yes, probably relates to the 2025 snapshot archive, and it's not actual any longer?

<youpi>what do you mean by "actual" ?

<youpi>we are not in 2025 any more, yes

<youpi>if you want to access the 2025 snapshot, when then yes you want to ignore that the certificate has expired

<yang3>I mean it dates before the key expired, so its not actual for that key

<yang3>right

<yang3>check-valid-until=yes ?

<yang3>OI have 2no"

<yang3>i have "check-valid-until=no"

<youpi>sorry, set to =no indeed

<yang3>ok

<yang3>does smartctl works in Hurd ? to check the HDD status?

<youpi>no

<youpi>probably you can add signed-by=/usr/share/keyrings/debian-ports-archive-keyring-removed.gpg to give it the old key

<yang3>youpi like this? http://pastie.org/p/3cNCyuhFpJkPTR0T2iScbf/raw

<youpi>yes

<youpi>though for debian it would be the debian keyring removed file

<youpi>debian-archive-removed-keys.pgp

<yang3>yes, I noticed tzhe symlink

<youpi>(as opposed to debian-ports)

<etno>Every time I see apt cert issues, I always think : "is the machine wall clock correct" (I was biten so hard by this :D )

<jab>hello friends!

IRC channel logs

2026-08-04.log