Jeremy Nicoll <jn.ml.sfrg...@letterboxes.org> writes: > On Wed, 25 Oct 2017, at 23:45, David Grayson wrote: >> A conflict is an unusual event that is different from a routine >> upgrade to a new version of a package. > > OK (and thank-you for replying)... > >> It looks like you deleted the most important parts of the pacman >> output and just paraphrased it instead. You should post the full >> pacman output so we can understand exactly which packages were >> conflicting and what pacman was asking you. > > I really don't think I deleted anything significant. Here is all of > it: > > DayToDay01@SAMSUNG-NP350 MSYS ~ > $ pacman -Syuu > :: Synchronising package databases... > mingw32 361.4 KiB 774K/s 00:00 [###] 100% > mingw32.sig 96.0 B 93.8K/s 00:00 [###] 100% > mingw64 361.2 KiB 2.37M/s 00:00 [###] 100% > mingw64.sig 96.0 B 0.00B/s 00:00 [###] 100% > msys is up to date > :: Starting core system upgrade... > there is nothing to do > :: Starting full system upgrade... > resolving dependencies... > looking for conflicting packages... > > Packages (2) mingw-w64-i686-p11-kit-0.23.9-1 > mingw-w64-x86_64-p11-kit-0.23.9-1
Those are not conflicting packages. They are the packages with newer versions available. The looking for conflicting packages... text just before the list of packages is a bit misleading. If some conflict is found, pacman will tell you explicitly with a message like: "package foo conflicts with package bar". ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
