IRC channel logs

<damo22>youpi: is there still a problem with dak for hurd port? i recall you mentioned some thing could be improved there so hurd port would be less to maintain?

<jab>"with dak for hurd port?" What is dak ?

<damo22>its a set of scripts to manage the debian archive

<damo22>i submitted a merge request to dak to fix a few lint errors to see if they would accept patches, it went stale and it was closed

<damo22>(00:25:02) gnu_srs: I know about that, but anyway. BTW: How can the problem of *-common packages being upgraded when the source package FTBFS be solved?

<damo22>(00:28:14) youpi: with the mini-dak software currently running on debian-ports, it cannot

<damo22>(00:28:26) youpi: it'd need either improving mini-dak, or installing the full dak

<damo22>sounds like there is a mini version of dak managing the debian-ports archive

<AlmuHS>i'm using deepseek to generate a PostgreSQL-CRUD translators. After a couple of week, the model learned about how to create translators, and resumed the information in this guide

<AlmuHS> https://gitlab.com/AlmuHS/hurd-translator-in-rust/-/blob/main/docs/translator-guide.en.md

<AlmuHS>could you check if the information is precise?

<AlmuHS>**accurate, not precise

<damo22>well, if you are using LLM to write your code, it is up to you to verify it

<damo22>personally i avoid LLMs

<AlmuHS>i use it in a limited mode: I direct the model step by step. I never wrote any translator, the docs about it are rare, so i needed a bit of helpful. But I am watching in each step

<AlmuHS>i'm guiding about implementation

<AlmuHS>i only want to check if the info which we join about translators, trivfs functions, etc, is correct

<damo22>i dont know

<damo22>assume it is wrong and then check every step?

<AlmuHS>ok

<damo22>youpi: is binary-all imported from main debian?

<damo22>i dont see it here https://deb.debian.org/debian-ports/dists/unreleased/main/

<youpi>damo22: in unreleased each arch has its own archive, its now sources, its own arch:all packages. See the Packages.gz file, it has the Architecture: all entries

<jab>youpi: how would you feel about turning the the qoth into a "this month in the Hurd?" hurd.gnu.org would have a blog update once a month...

<youpi>the only question is feeding it :)

<jab>I'm happy to write it. We might end up having some months that are very sparse, but I feel that more blog posts might attract more contributors.

<azeem>did QotH get much longer in recent quarters?

<jab>azeem: it somewhat depends on how much work gets done. I will say that in recent qoth's I am making it a bit longer by adding in lots of direct quotes.

<azeem>my gut feeling is that quarterly is still the right cadence for now unless development picks up considerably, but that is of course just my outside opinion

<jab>well, how about this...I'll write up a "july update" news article, and I'll send it to bug-hurd. We'll see what people think. If it is too short, then I can just save it and write a q3 in a few months.

<Alicia>or keep calling it qoth but post more often anyway if there are many updates? :)

<jab>qoth stands for quarterly update...

<jab>so having more than 4 updates per year seems like we shouldn't use the name qoth. My personal opinion.

<jab>Alicia did you end up committing your here's download and install a hurd vm script to source somewhere ?

<Alicia>no

<jab>I very much so encourage you to do so. I don't want to lose it. :)

<Alicia>but where?

<jab>do you have a git account somewhere ? gitlab, sourcehut, etc.

<jab>just somewhere.

<Alicia>I selfhost my git repositories, but making a repository for just one script seems a little pointless

<jab>your choice.

IRC channel logs

2026-07-26.log