Running "rm /usr/share/man/man3/*.3ssl.gz" enabled me to get past the "exists in filesystem" problem but there were still some errors and libgcc_s_dw2-1.dll was not updated. I think I've gone about updating Gtk2 and Gtk3 the wrong way and have badly broken msys in the process.
It's time I stopped messing around and simply did a fresh install. Cheers, Rob On Sun, Jun 2, 2019 at 11:51 AM Óscar Fuentes <o...@wanadoo.es> wrote: > sisyphus <sisyphus...@gmail.com> writes: > > > I removed the offending files, but the error still persists. (See > attached > > msys2_upgrade.txt) > > I made sure that I opened a new shell following the removal of the files, > > but it seems there's some cached information that these files are still > > present. > > How can pacman complain about the existence of deleted files? Are you > sure that you deleted them? > > Just in case, check that there are no zombie pacman processes. Open the > task manager, look for instances of pacman.exe and kill them. I don't > think that those are causing your problems, though. > > > What's the best way around that snag ? > > Just do > > $ rm /usr/share/man/man3/*.3ssl.gz > > After that, if pacman keeps complaining about those files, then we have > a deeper problem. > > > Following advice at > > > https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error > > , > > I did check that the 3 files were not owned by another package: > > > > sisyphus@Owner-PC311012 MSYS ~ > > $ pacman -Qo /usr/share/man/man3/BN_print.3ssl.gz > > error: No package owns /usr/share/man/man3/BN_print.3ssl.gz > > > > sisyphus@Owner-PC311012 MSYS ~ > > $ pacman -Qo /usr/share/man/man3/LHASH.3ssl.gz > > error: No package owns /usr/share/man/man3/LHASH.3ssl.gz > > > > sisyphus@Owner-PC311012 MSYS ~ > > $ pacman -Qo /usr/share/man/man3/UI.3ssl.gz > > error: No package owns /usr/share/man/man3/UI.3ssl.gz > > That's expected. IIUC pacman fails because a package pretends to install > files that already exist on the filesystem and are not owned by that > package (or any package at all, as in your case). Deleting those files > should fix the problem. > > > Oddly, although each of those three filenames begin with upper case > > letters, Windows has them as lower case. > > Can that be complicating things ? > > That's interesting. Maybe pacman is using some simplistic, case > insensitive function such as strcmp for comparing file names. > > > > _______________________________________________ > Msys2-users mailing list > Msys2-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/msys2-users >
_______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
