mauricev

My Mac hosting virtualbox crashing during an ego sync. Now I get error: object file .git/objects/db/bf91bacaf480aae4d2899cfb10c15b4706d3f5 is empty fatal: loose object dbbf91bacaf480aae4d2899cfb10c15b4706d3f5 (stored in .git/objects/db/bf91bacaf480aae4d2899cfb10c15b4706d3f5) is corrupt ERROR: There was an error syncing meta-repo. How can I fix this?

For some reason, genkernel did have cryptsetup set on. I turned it off and now emerge is working. Thanks.

emerge: there are no ebuilds built with USE flags to satisfy "dev-libs/json-c:=[static-libs(+)]". !!! One of the following packages is required to complete your request: - dev-libs/json-c-0.12::core-kit (Change USE: +static-libs) (dependency required by "sys-fs/cryptsetup-2.1.0::core-kit[static,-static-libs]" [ebuild]) (dependency required by "sys-kernel/genkernel-3.4.40.23-r2::core-kit[cryptsetup]" [installed]) (dependency required by "sys-kernel/debian-sources-lts-4.19.67_p2-r1::core-kit[binary]" [ebuild]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument])

This is not the case. My emerge output is https://pastebin.com/Pb8PTyWY

Just ran ego sync and emerge is complaining !!! One of the following packages is required to complete your request: - dev-libs/json-c-0.12::core-kit (Change USE: +static-libs)

I actually have one overlay working and one not. /opt/my-overlay/net-fs/s3ql is recognized and let's me emerge net-fs/s3ql-3.3::my-overlay /opt/my-overlay/dev-fs/s3fs isn't recognized: net-fs/s3fs-1.83::net-kit

I just tried this with s3fs and it built the manifest without complaining as it was doing earlier, but portage doesn't see the overlay at all.

This may be of help, https://forum.level1techs.com/t/corsair-h100i-linux-howto/75829/15

What I am noticing is that on the machines with ipv6, the nf_conntrack modules are loaded.

Can confirm that the kernel has IPv6. The bug is elsewhere.

https://bugs.funtoo.org/browse/FL-6605

I figured it out. One is a slightly older build than the other. The debian-kernal lts had to have been compiled against different configs. The one with ipv6 is running 4.9.168_p1 and the one without 4.19.37_p6. I guess this is a bug. ipv6 was left out of the newer kernel.

How can a machine be missing ipv6? Also, they're identical.

Two machines identically configured. On one, netstat returns tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN tcp 0 0 45.76.6.231:497 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:497 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp6 0 0 :::33060 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN On the other, tcp 0 0 localhost:mysql 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp 0 0 localhost:9000 0.0.0.0:* LISTEN Why is Apache showing up in one and not the other? More generally, why does one list IPv6 connectivity and the other not?

Ah, thanks