15
submitted 1 year ago by Illecors@lemmy.cafe to c/gentoo@lemmy.cafe

I've got a physical bit of tin that I'm playing around with. It has a livecd booted. I ssh into it, enter chroot, happy days.

I've been trying to install tmux, but libevent just wouldn't finish configuring. I had forgetten about it and left over the weeked. Found it still running (probably in loops) this morning. Quick websearch did not yield anything obvious, thought I'd sync the repo in hopes it was an ebuild issue. That threw up on me with SSL errors, complaining the certs are not valid, yet. This was the hint I needed. After setting the correct time the build went through in seconds.

I don't understand why it got in the way in the first place, but I guess it's not something people would run into all that often. Something to keep in mind, though!

top 5 comments
sorted by: hot top controversial new old
[-] Illecors@lemmy.cafe 2 points 1 year ago

For clarity's sake the date was off by almost 5 years, nothing to scoff at.

[-] DeviatedForm@lemmy.cafe 1 points 1 year ago

Easy solution; just wait for 5 years

[-] Illecors@lemmy.cafe 2 points 1 year ago* (last edited 1 year ago)

Simples! Time progression should be terminated and running at the same time!

We may have broken physics ๐Ÿ˜

[-] nyan@lemmy.cafe 2 points 11 months ago

For even more amusement, try correcting the system clock after fetching the source but before compiling certain packages, and watch ninja flail around because it can't deal with source from the future, until it finishes its thousand default iterations and causes portage to error out. (My system is only about twelve hours in the future on startup, fortunately, so it's self-correcting if you wait overnight. It took me a while to figure out what the actual problem was.)

[-] Illecors@lemmy.cafe 1 points 11 months ago

Timestamp of the source actually makes sense! Thanks for that! :D

this post was submitted on 30 Oct 2023
15 points (94.1% liked)

Gentoo

152 readers
2 users here now

founded 1 year ago
MODERATORS