KIM_JONG_JUICEBOX

joined 1 year ago
[–] KIM_JONG_JUICEBOX@lemmy.ml 11 points 1 year ago (1 children)
[–] KIM_JONG_JUICEBOX@lemmy.ml 4 points 1 year ago

I must taste this white blood wine.

[–] KIM_JONG_JUICEBOX@lemmy.ml 3 points 1 year ago (1 children)

I graduated in 1998 and it’s in my vermicelli.

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago

This guy maybe onions.

[–] KIM_JONG_JUICEBOX@lemmy.ml 9 points 1 year ago

The mole people had a funeral for him?

[–] KIM_JONG_JUICEBOX@lemmy.ml 23 points 1 year ago

It’s like it’s not enough that you deal with all the technical shit, updating to new versions, checking shit out from GitHub, running builds, paying for the goddamn thing, then you are also responsible for babysitting content? Fuck that. Unless you have a good group of mods/admins it is really difficult to do.

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago (1 children)

I was gonna abuse my children because I abuse my pets.

You’re saying I should go the other way?

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago (3 children)

Does this mean I can’t abuse them?

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

That is one derpy cat.

[–] KIM_JONG_JUICEBOX@lemmy.ml 3 points 1 year ago

Didn’t Lenovo like 15 years ago make a line of desktops that shipped with some redhat derivative installed? Or am I thinking of something else?

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

I thought Russia said they would not share any of the science.

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago

Yeah boofing is real. I don’t know about the tampon part though.

 

I'm trying this on Ubuntu 22.04 Rust's cargo install seems to keep creating permission problems between what I have to install, compile and what gets published in the cargo "registry", which causes issues at runtime when I run as lemmy:lemmy through systemctl.

If I run: cargo install lemmy_server --target-dir /usr/bin/ --locked --features embed-pictrs as a non-root user, I get permission denied issues with /usr/bin/.future-incompat-report.json and /usr/bin/release

If I run the build as a root user, and then manually copy the binaries to /usr/bin and chmod them to lemmy:lemmy, then try to run as lemmy:lemmy, it appears the binary is trying to access some "registry" files in /root/.cargo/registry (for which of course it does not have permissions.)

How do I fix this?

view more: next ›