IRC channel logs

2024-11-07.log

back to list of logs

<ZhaoM>I'm installing the Hurd on my T60
<sneek>ZhaoM, you have 1 message!
<sneek>ZhaoM, gnucode says: I would recommend this as a good guide for setting up a mail server. It's kind of tricky. https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/
<ZhaoM>I have wrote this image to a CD: https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20230608/debian-sid-hurd-i386-NETINST-1.iso
<ZhaoM>what's the meaning of 'sid'?
<ZhaoM>sneek later tell gnucode thank you for the guide I will read it
<sneek>Will do.
<anatoly>ZhaoM: debian sid is debian unstable, see https://wiki.debian.org/DebianUnstable
<ZhaoM>anatoly: thanks this is what I'm looking for
<ZhaoM>I just wrote my CD(CD-R) with the sid version (https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20230608/debian-sid-hurd-i386-NETINST-1.iso)
<ZhaoM>and I haven't got another empty CD
<ZhaoM>is it fine to install the sid version?
<ZhaoM>it seems getting a new empty CD and installing the stable version is safer, I should do it :)
<anatoly>ZhaoM not sure it will be true for hurd, a "stable" release of hurd could be released long time ago and containing older hurd/mach/etc versions which could be more problematic than something fresher in the end.
<anatoly>I would say the main concern (in the sense of stability) is hurd itself and less the software from debian unstable
<ZhaoM>anatoly: sorry for the misuse of "stable", the stable version I referred to is the image in this link: https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20230608/iso-cd/
<ZhaoM>this image does not have 'sid' keyword
<janneke>in pciutils and libpci i'm getting errors like:
<janneke>error: passing argument 3 of ‘dir_readdir’ from incompatible pointer type
<janneke>size_t instead of mach_msg_type_number_t
<janneke>is my gnumach too new, or too old, or should i just patch this?
<janneke>ACTION didn't find any debian patches for this?
<youpi>it'd rather be mig, which is "too new"
<youpi>I haven't recompiled libpciaccess / pciutils for a while, so we probably just haven't met the issue yet
<janneke>youpi: ok, thanks
<janneke>interesting how it builds unpatched on 32bit
<janneke>(guix mig is at 1.8+git20230520)
<solid_black>janneke, youpi: mig is fine, but {libpciaccess,pciutils} should be updated to use mach_msg_type_number_t
<solid_black>it builds on 32-bit because both types are 32-bit there
<solid_black>isn't this the fix? https://gitlab.freedesktop.org/xorg/lib/libpciaccess/-/commit/6cd5a4afbb70868c7746de8d50dea59e02e9acf2
<janneke>sneek: later tell solid_black: yes, that's the fix; thanks. good to know it's upstreamed and better to take it from there.
<sneek>Okay.
<janneke>sneek: botsnack
<sneek>:)
<gnucode>QNX may be free for non-commercial for a while.
<sneek>gnucode, you have 1 message!
<sneek>gnucode, ZhaoM says: thank you for the guide I will read it
<gnucode> https://news.ycombinator.com/item?id=42079460
<azert>damo22: are you around?