![]() Gpg: requesting key 4CA56930 from hkp server Gpg: requesting key 2C51581E from hkp server Gpg: requesting key A47D45A1 from hkp server Gpg: requesting key 3E652008 from hkp server Gpg: requesting key 3E0D0813 from hkp server Gpg: requesting key AEEA755C from hkp server Gpg: requesting key CA25678A from hkp server Gpg: requesting key 3E058AFD from hkp server ![]() ![]() the first two steps appeared to go OK, but he last step produced and ERROR, as per: Try removing /etc/pacman.d/gnupg, then pacman-key -init, pacman-key -populate msys2, pacman-key -refresh-keys. Try re-installing gpgme libgpgme, gnupg and pacman packages (you can temporarily disable signature checking in /etc/nf) Gpgme errors all over the place, so, (David's suggested link) from BLODA, I have no software installed that is on their "conflict" listĬlean install MSys2, following the EXACT instructions from ( ) Had cygwin/cygwin terminal installed, so just in case, uninstalled that (not a simple process) Perhaps Ray Donnelly or somebody might be asked to respond.īased on DavidEGrayson's suggestion, I performed all that I could from that link, with the errors as described below: At the very least, you might provide information on how one would even approach a "solution" to the stated errors. I should say that also, while it may not be intended, your responses seem to come across a bit confrontational and unhelpful. The problems with MSys2 seem to "deep in its bowels", and we have no access to, control over, or knowledge of why it throws GPGME errors, and why it insists on corrupting its own databases, which are managed with proprietary and inaccessible machinery in MSys2. We have spent many man hours trying to get it to work, so far all that time is a waste. and it may help if all the staff at MSys2 "has the same story", rather than the conflicting story unfolding here.Īs WinXP is an important platform, we definitely would wish for it to be supported.Īs for us to the "dig into problems and provide solution for it". In the alternative, make it clear on your dload/install pages that your product does not work with WinXP so people don't waste their time with. I have no idea what "turbans" are in this context.Īs the developers state that WinXP is "targeted", it should be supported. I am not sure if it's some "language thing", but I don't understand some of the words you are using. Have tried several times to attach a jpg of a screen print example of the GPGME etc errors, but the blog keeps responding with "Something went really wrong, and we can't process that file". No idea how to proceed, but would desperately wish to have a working WinXP64 install. couldn't find an WinXP64 specific solutions on the MSys forum Have tried various other "fixes" seen on the web (autorebase) etc., no joy. On some occasions, not idea why, it completely "looses bash", and will not accept any bash commands at all (e.g. There is no possibility of downloading anything even with Sync deleted, since it must first create Sync for the download, and immediately creates corrupt db's, preventing any further communication with the server. This allows a pacman Su etc to work once in the sense that it recreates the Sync dir, but again with "corrupt" db's. One attempt at a solution is to delete the Sync Dir. Apparently MSys2's databases become "corrupt" and after that it will not work. on the rare occasions that it has, any variation of pacman -Su, Syuu etc fails with "GPGME error" "invalid crypto" etc.It almost never even gets to the first step of update-core due to "GPGME" etc errors. Have tried many times with many permutations to install Msys2 on WinXP64 (all SP's) using msys2-x86_64-20160205.exe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |