On 4. 4. 2016 2:19, Eric Hiller wrote: > Hi guys -- Ran the update - was confused at first about the lack of > `update-core` but figured it out after seeing git. Now I am confused about > the pacman version After running: > > pacman -Sy --noconfirm pacman > :: Synchronizing package databases... > mingw32 is up to date > mingw64 is up to date > msys is up to date > warning: pacman-5.0.1.6403.520736d-1 is up to date -- reinstalling > resolving dependencies... > looking for conflicting packages... > > Packages (1) pacman-5.0.1.6403.520736d-1 > > ::: I still see :::: > > > pacman.exe --version > > .--. Pacman v4.2.1-516-g52073-dirty - libalpm v10.0.1
Yeah, I see it as well. It's a byproduct of git merges in our pacman repository. The actual code is really based on upstream 5.0.1. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
