0 Followers
0 Following
3 Posts

Status: Closed

That means it wasn’t accepted, see also the last comment before closing:

It’s an optional field in the userdb JSON object. It’s not a policy engine, not an API for apps. We just define the field, so that it’s standardized iff people want to store the date there, but it’s entirely optional.

Hence, please move your discussion elsewhere, you are misunderstanding what systemd does here. It enforces zero policy, it leaves that up for other parts of the system.

And sorry, I am really not interested in these discussions here. it’s not the right place for this, and please don’t bring it here. Thank you.

Not true, looking at systemd main branch shows the field still exists. Here’s the state as of posting this comment:

github.com/systemd/systemd/blob/…/homectl.xml#L37…

Also ping @[email protected] fyi

systemd/man/homectl.xml at 494c65236b19e160ade48315edfa0f089f3d4154 · systemd/systemd

The systemd System and Service Manager . Contribute to systemd/systemd development by creating an account on GitHub.

GitHub
Weren’t they though? Like they were absolutely horrible but last I remember most everything else in WH was also somehow worse than them so they are the “good”-er guys.
Pretty sure they renamed it to Copilot

github.com/openwrt/openwrt/issues/22412

I think the only thing holding it up is the package rebuild action.

Pro tip: If you’re using openwrt or other managed network components don’t forget to automatically back those up too. I almost had to reset my openwrt router and having to reconfigure that from scratch sucks.
We’re going to teeach them our eco friendly ways, by force
Here, watch as I did and hear the horror: youtu.be/IiyKh1d_U7o
SpongeBob's "Squeaky Boots" 🔊 | SpongeBob

YouTube
If logging is down and there’s no one around to log it, is it really down?