KIM_JONG_JUICEBOX

joined 1 year ago
[–] [email protected] 4 points 5 months ago

Is it happening??

[–] [email protected] 11 points 5 months ago

“It’s a tv show about these people who make a podcast.”

[–] [email protected] 1 points 5 months ago (3 children)

Did he go MAGA too?

I heard Gallagher went MAGA, but he’s been balding since the 70s.

[–] [email protected] 12 points 5 months ago (2 children)

He was kind of funny on the show News Radio before even that. That was a good show with a lot of good actors but seems like a lot of people never heard of it.

[–] [email protected] 1 points 5 months ago

I feel like if they were butcher, they would only work with fish.

[–] [email protected] 3 points 5 months ago

They will be flying and self driving by the year 2000.

[–] [email protected] 10 points 5 months ago
[–] [email protected] 1 points 1 year ago (1 children)

I’m confused. Is it 650 rounds per minute or 100 rounds per minute?

[–] [email protected] 2 points 1 year ago

It’s like a roast. His friends give him sick burns all evening one night a year.

[–] [email protected] 5 points 1 year ago (2 children)

What is the Fword or the Kword?

[–] [email protected] 10 points 1 year ago (2 children)
[–] [email protected] 13 points 1 year ago (1 children)
 

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 ›