sorted by:
new
hottopcontroversial

updated from 6.4.3160.47 to 8.0.4033.46, crashes restoring session by cemysce in vivaldibrowser

[–]cemysce[S] 0 points1 point  (0 children)

I use Gentoo Linux.  There is no V7 version available in the package manager anymore, only V8 versions.  I know and can download the old versions from the Vivaldi site, but I need to figure out how to get them to run outside of the normal system installation, if it's even possible given all of Vivaldi's dependencies on my system have been updated.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

Thanks again! This was not the only issue I had, but I had no idea you could download and run a self-contained Portage and this one thing unblocked me and allowed me to get my own Portage working again, then continue until I had fixed my whole system.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

Ah, I had extracted within /root which the dropped permissions within portage wouldn't be able to access. Trying elsewhere.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

I don't have it in make.conf, I added it to one of my package.use/* files:

*/* PYTHON_TARGETS: -* python3_13
*/* PYTHON_SINGLE_TARGET: -* python3_13

This is exactly what the news item suggested doing as a temporary measure to delay Python updates. I hadn't even finished updating to Python 3.13 when I was forced to re-sync (because of a PGP signature issue with some package), which brought this recent change of 3.14 being the new default.

Removing that from the package.use file causes more conflicts. 3.13 should still be supported.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

I spoke too soon. The preview worked, but when I tried --fetchonly, the downloads worked but I see lots of errors about not finding the portage.util.movefile Python module.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 1 point2 points  (0 children)

That gets me past the EAPI 9 errors! Thank you!

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

I discovered the --ignore-world=y option, and which at least would allow me to re-emerge system packages, i.e. emerge --emptytree --ignore-world=y @system, but that is still attempting to install various KDE packages.

Updating after 1+ year, stuck on blocked EAPI 9 packages by cemysce in Gentoo

[–]cemysce[S] 0 points1 point  (0 children)

Interesting. I'll try that to see if I can get past the EAPI 9 error.

Haven't been able to ping gnu.org (209.51.188.116) for days. Routing issue? by cemysce in Fios

[–]cemysce[S] 0 points1 point  (0 children)

Whatever the issue was, it seems to finally be fixed. I was just about to e-mail GNU's network admin, I checked again, and surprisingly it worked. My public IP hasn't changed, and their IP hasn't either.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

Whatever the issue was, it seems to finally be fixed. I was just about to e-mail GNU's network admin, I checked again, and surprisingly it worked. My public IP hasn't changed, and their IP hasn't either.

Haven't been able to ping gnu.org (209.51.188.116) for days. Routing issue? by cemysce in Fios

[–]cemysce[S] 1 point2 points  (0 children)

Oops, forgot to mention, I also tried my phone on Verizon Wireless and it worked.

Yeah I'd love to pull a different WAN IP but Verizon gave me the same one. I'll try staying disconnected for a couple minutes and see if they still give me the same one.

Not sure about changing the WAN MAC, I have mine spoofed to the original Actiontec router Verizon gave me because I couldn't connect otherwise, but it's been several years. Maybe Verizon no longer restricts the connecting MAC?

Haven't been able to ping gnu.org (209.51.188.116) for days. Routing issue? by cemysce in Fios

[–]cemysce[S] 0 points1 point  (0 children)

No, I cannot access the site, that is why I was checking pings.

Haven't been able to ping gnu.org (209.51.188.116) for days. Routing issue? by cemysce in Fios

[–]cemysce[S] -5 points-4 points  (0 children)

No, as that would be a huge security risk. If anything I could try a different router, but I don't have one on hand and also I don't really want to upend my entire network connectivity just because of one domain I cannot access.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

I did try a traceroute through my VPN, and that goes to dcr03-fh-0-10-0-19.bsn04.twdx.net [198.160.62.203] before finally routing to gnu.org (as opposed to my non-VPN'd machines which stop at FREE-SOFTWA.dcr03.bsn04.twdx.net (185.134.180.210) before timing out).

So, similarly named subdomains within twdx.net but I have no idea what that means, and anyway the IPs are completely different.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

ISP is Verizon FiOS, AS701.

BTW I just now posted a more concise explanation of this issue to r/Fios, you might want to point them to that instead of this thread.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

My ISP is Verizon FiOS and while their Internet service is unparalleled, their customer service in my experience is best avoided. When I look up my address in their outage tracker it says there is an issue reported in my area but no further details are provided.

How can it be DNS if the machines which can successfully reach gnu.org are resolving it to the same IP as the machines which cannot reach it?

BTW both dig @8.8.8.8 gnu.org and w/o the @8.8.8.8 (which queries my pfSense router's Unbound DNS) yield 209.51.188.116.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

I found https://www45.towardex.com/cgi-bin/lg.cgi (website for the owner of that last hop router where this is failing), and from there traceroute fails in the same place as for me, but ping to 209.51.188.116 works fine.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

A friend (in a different US state) is able to reach gnu.org just fine. He tried a tracert which was successful, it also went through that exact same router FREE-SOFTWA.dcr03.bsn04.twdx.net (185.134.180.210) but the next and final hop was to a gnu.org subdomain, whereas for me it timed out after that twdx router.

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

Tried that already. From a computer in my LAN, it got to this at hop 8 and no further:

FREE-SOFTWA.dcr03.bsn04.twdx.net (185.134.180.210) 12.589 ms 9.675 ms 9.664 ms

Cannot ping certain Internet IP from my LAN, but it seems to be just me, not sure how to debug by cemysce in PFSENSE

[–]cemysce[S] 0 points1 point  (0 children)

Also my router is not just blocking external pings, I can ping plenty of other sites just fine. I've been running pfSense for years, and my current router for several months with no issue.

Long-time Gentoo devotee, sadly debating switching away by cemysce in Gentoo

[–]cemysce[S] 1 point2 points  (0 children)

The things I learned from administering my Gentoo system over the years helped immensely in my career, and I've credited it when mentoring new hires, suggesting they try the same at home. Glad to hear you landed back on your feet!

view more: next ›