For what's its worth: After a system update a few weeks ago I encountered a similar problem when running Warcraft III in Wine with my old Nvidia GeForce GTX 260 (GT200), where it was running unaccelelerated with llvmpipe instead of Nouveau drivers. Nvidia drivers stopped supporting this card several ...

This is currently happening for any program run in an xterm that uses the tty in its basic "cooked" mode (subject to stty settings). The simplest such program is "cat".

It also happens with programs that might interactively ask for confirmation, such as "emerge -a", "cp -i", etc. You occasionally ...

I see the same thing, but only sometimes. Probably based on which DNS response (mirror) it happens to try first, each time.

I suspect it would be safe to follow a procedure:
Control-C cancel the sync if you see that error.
Re-start the sync
When/if a sync doesn't give that message, let it finish ...

For the wine/game problem I went ahead and bisected and further analyzed the underlying problem and some possible solutions, which I've written up in an upstream bug report: https://bugs.winehq.org/show_bug.cgi?id=54243 .

For debugging wine in gentoo specifically, in case anyone else wants to ...

I just tried wine-vanilla-7.22 and wine-proton-7.0.5, but they still cause Warcraft 2 to fail the CD check. I had previously tried vanilla 7.0, 7.0.1, 7.9, and 7.13 without success. My old install of wine-vanilla-6.0.2 from the overlay still works for now, but who knows for how long, especially ...

I use the wine overlay to install an older slotted version of wine, since 7.x causes CD check failures in an older game I like to play (Warcraft 2 BNE).

Today I did a full update (both main and wine overlay), and started getting a ton of major error messages about EAPI=6 no longer supported ...

I don't know if this should be considered a problem worth changing anything for or not, but:

If I download the original SRC_URI indicated in the dev-python/charset-normalizer-2.1.1 ebuild ( https://github.com/Ousret/charset_normalizer/archive/2.1.1.tar.gz ), it is currently a 86023 byte file. If ...

Fixed the check to only fire when distcc is enabled (thanks for the report!)
If your system is working fine, you shouldn't need to bother with any rebuilding of things. If you don't use distcc, forget about all this.
We only stabilise GCC versions when the vast majority of packages are ready. I ...

So now I'm confused by the new gcc>10 pkg_pretend() check.

I updated libxcrypt a few weeks ago (when it became stable) without any sign of these gcc version problems. Most or all of the machines I upgraded are using gcc 9.3 or 9.4, or possibly older, but I don't use distcc at all. I don't think any ...

I also got a file collision and needed to do the equivalent of
FEATURES='-protect-owned' emerge --oneshot libxcrypt
on the first machine I updated, but 5 or 6 other machines worked fine without it. The suggested FEATURES="-collision-protect unmerge-orphans" from the news item did not work; those ...

I have not defined any proxy, but i get a somewhat different error message when doing emerge --sync :
File "/usr/lib/python3.7/site-packages/portage/sync/modules/rsync/rsync.py", line 136, in update
openpgp_env = self._get_openpgp_env(self.repo.sync_openpgp_key_path)
File "/usr/lib/python3.7 ...

Another workaround is to temporarily set http_proxy to an empty string (as opposed to unset) in the environment when invoking "emerge --sync", as in something like "(export http_proxy="" ; emerge --sync)" or "(http_proxy="" emerge --sync)". This currently seems to work regardless of what kind of ...

You might be able to hack something in /etc/gai.conf (man gai.conf), although I'm not sure I would recommend modifying the defaults. Or maybe simpler to just override DNS and force an IPv4 address with /etc/hosts or something.

However, what kind of network setup would have IPv6 only broken for a ...

Is it in a public overlay somewhere? Does anyone have an ebuild in a local overlay and be willing to pastebin it?
I've attached a preliminary ebuild to the same [bug]705606[/bug], along with associated files/*. My comments in the bug outline a variety of limitations and concerns with it.

Any ...

xedakini has done a lot of work on http-replicator; maybe it could be re-added to portage, although that would probably require an official maintainer (or at least proxy maintainer). More information from https://forums.gentoo.org/viewtopic-t-1097768-postdays-0-postorder-asc-highlight-httpreplicator ...

Status: I haven't had time to try it myself, but xedakini has apparently done a lot of upstream maintenance of version 4, and "sort of" became the upstream maintainer ( https://github.com/xedakini/replicator/pull/5 ). A quick glance suggests it already has most desired updates, including: python3 ...

Overview

With app-editors/vim-8.2.0360 running in ":set compatible" mode and running in an xterm window, if I try to use the "r" command to replace the character under the cursor with any capital letter, it misinterprets the command in a strange way.

Can anyone else repeat see this and/or have ...

Status: As I suspected would happen, repcacheman is broken now that portage has dropped the ability to run under python2 (after the end of http-replicator's last rites), but http-replicator itself (v3) is still working (for now).

I wonder if xedakini is still working on it?

Summary:

If you recently noticed the new version of ninja (1.9.0) as invoked from GNU make suddenly taking a lot longer to build things in your environment, then the basic cause is a lack of a '+' symbol prefix in the makefile when invoking ninja.

-----

Details:

It took a bit of research to ...

In bug 705606 comment 6, xedakini is starting work on porting http-replicator to python 3. Anyone willing to help might want to coordinate with that effort.

I intend to keep running a local copy of the http-replicator 3 ebuild I saved off my personal overlay until it actually breaks more than I can live with. After that, if a better alternative doesn't pop up, I'll probably just stop trying to use any proxy server at all, even though I don't really want ...

I recently updated a post I wrote several months ago describing several aspects of the current status of http-replicator in a fair amount of detail. See https://forums.gentoo.org/viewtopic-t-1101822-highlight-httpreplicator.html

New changes: I suspect that repcacheman will probably stop working ...

@Thistled: some thoughts below. The third bullet below may be the most useful for you, but the others help provide context.

1. Despite your edits about version 3, that log snippet looks like it is more likely to have come from version 4. Version 3 was removed from portage several months ago ...

I intermittently see similar key verification problems on my
machine. Most recently gpg has reported "Server indicated a failure"
rather than "No keyserver available", in otherwise-similar output.

WORKAROUND: I've found the best (most likely to eventually work)
general workaround to key sync ...

Overview :

http-replicator's primary purpose is to locally cache and distribute source packages for portage within a LAN environment. This can be useful if you have limited external internet bandwidth from inside that LAN, but:

IMHO, it also just seems like good manners to minimize the load you ...