Luj

Yes I can confirm that those two properties are indeed not present with `org-ql`.

> This might be an issue though: > > https://github.com/nikstur/userborn/blob/main/rust%2Fuserborn%2Fsrc%2Fmain.rs#L129-146 I agree. I am not sure I 100% understand how userborn handles "impure" users/groups, I am trying to get a...

Interesting, I wonder where this thing is set in the module system. I wouldn't expect this to be hardcoded neither in userborn or in the users module, will check.

> This might be an issue though: > > https://github.com/nikstur/userborn/blob/main/rust%2Fuserborn%2Fsrc%2Fmain.rs#L129-146 To this point, this is correct. I just pushed a commit with a failing test case that covers this issue....

> I have just realized that we end with a broken /etc/passwd (as we don't have /run/current-system [yet?]): > > ``` > root:x:0:0:System administrator:/root:/run/current-system/sw/bin/bash > nobody:x:65534:65534:Unprivileged account (don't use!):/var/empty:/run/current-system/sw/bin/nologin >...

Userborn change that introduces stateful users is submitted upstream: https://github.com/nikstur/userborn/pull/36

This method (of creating a registry) mostly works, but it's very hard finding a combination of repository commits that allows us to build everything. My impression at this point is...

The new strategy I'm betting on now is to build a specific registry per package, with as much automation as possible.

The remaining piece of this puzzle is to correctly wire the registry generating script with the update script, but I'll leave this for later.

I'll reopen this to track the issue. This is not high priority but still relevant.