Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update-core not working anymore #524

Closed
jpsdr opened this issue Mar 31, 2016 · 7 comments
Closed

update-core not working anymore #524

jpsdr opened this issue Mar 31, 2016 · 7 comments

Comments

@jpsdr
Copy link

jpsdr commented Mar 31, 2016

Hello.
Since the last core system update very recently, update-core command is not working anymore.

@elieux
Copy link
Member

elieux commented Mar 31, 2016

It was replaced by functionality in pacman. Our wiki was updated to reflect that. Just use pacman -Syuu. If core packages update, follow instructions and repeat.

@elieux elieux closed this as completed Mar 31, 2016
@sskras
Copy link

sskras commented Apr 2, 2016

@elieux, excuse my noobness but isn't the project going to merge -Suu option with -Su (as in original pacman) ? So as to keep differences between both implementations minimal.

@elieux
Copy link
Member

elieux commented Apr 4, 2016

What do you mean? The upstream pacman manual page also mentions differences between -Su and -Suu.

@White-Tiger
Copy link

White-Tiger commented Apr 19, 2016

the main page wasn't updated yet to reflect this change, however.. (the one most people will use/see)
https://msys2.github.io/

My usual problem with MSYS2 was, that after every update, "update-core" were missing and I had to run pacman -S bash pacman pacman-mirrors msys2-runtime to get it back.
Hope pacman got improved in this regard and it's more reliable from now on.

edit:
is it normal to have pacman -V say v4.2.1-516-g52073-dirty - libalpm v10.0.1
I also had to make a copy of pacman called pacman2 and run pacman2 -S pacman because it said Pacman v4.2.1-273-gfa50-dirty - libalpm v9.0.1 before... So I'm not sure if everything is correct now...
Though on forced install, it'll say warning: pacman-5.0.1.6403.520736d-1 is up to date -- reinstalling

@mati865
Copy link
Collaborator

mati865 commented Apr 19, 2016

@White-Tiger Pacman v4.2.1-516-g52073-dirty - libalpm v10.0.1 if most recent version of pacman. You had Pacman v4.2.1-273-gfa50-dirty - libalpm v9.0.1 because you were downgrading pacman to restore update-core which was deprecated. If you are unsure if everything is ok you can force downloading latest database and updating/downgrading packages with pacman -Syyuu.
If everything is fine you will see this output:

pacman -Syyuu
:: Synchronising package databases...
 mingw32                  272.1 KiB   538K/s 00:01 [#####################] 100%
 mingw32.sig               96.0   B  0.00B/s 00:00 [#####################] 100%
 mingw64                  271.7 KiB   774K/s 00:00 [#####################] 100%
 mingw64.sig               96.0   B  0.00B/s 00:00 [#####################] 100%
 msys                     133.3 KiB  1269K/s 00:00 [#####################] 100%
 msys.sig                  96.0   B  0.00B/s 00:00 [#####################] 100%
:: Starting core system upgrade...
 there is nothing to do
:: Starting full system upgrade...
 there is nothing to do

@White-Tiger
Copy link

White-Tiger commented Apr 20, 2016

I wasn't downgrading anything myself.. I've always been using update-core as "suggested" but it also deleted itself after every update... (before it got officially removed)
By running pacman -S bash pacman pacman-mirrors msys2-runtime I've simply forced a reinstall of all core components which was mostly needed to get update-core working again..

And yesterday, I've just run update-core and let it do its stuff, restarted MSYS2 (by clicking the close button) and then used pacman -Syuu which didn't touch any core files and only updated MinGW and other stuff.
After all that, I've been stuck at the old Pacman v4.2.1-273-gfa50-dirty - libalpm v9.0.1.
Running pacman -S bash pacman pacman-mirrors msys2-runtime just yields the usual errors

:: Processing package changes...
error: cannot remove /usr/bin/msys-2.0.dll (Permission denied)
(1/4) reinstalling msys2-runtime
warning: warning given when extracting /usr/bin/msys-2.0.dll (Could not unlink)
error: cannot remove /usr/bin/bash.exe (Permission denied)
(2/4) reinstalling bash
warning: warning given when extracting /usr/bin/bash.exe (Could not unlink)
(3/4) reinstalling pacman-mirrors
error: cannot remove /usr/bin/pacman.exe (Permission denied)
(4/4) reinstalling pacman
warning: warning given when extracting /usr/bin/pacman.exe (Could not unlink)

and to really update pacman, I had to run a copy of it, so it was able to replace the original

@elieux
Copy link
Member

elieux commented Apr 20, 2016

the main page wasn't updated yet to reflect this change, however.. (the one most people will use/see) https://msys2.github.io/

Yes, we're waiting with that change until we release new installers. With the current installers, you have to run update-core at least once.

is it normal to have pacman -V say [...]

It's a known issue. The internal version number doesn't correspond to the actual version.

error: cannot remove /usr/bin/msys-2.0.dll (Permission denied)

This is wrong. The runtime should be able to replace files even when they're in use. Is your MSYS2 installed on a FAT volume or on a volume with the Windows Recycle Bin disabled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants