24 сент. 2014 г., в 12:04, Magnus Therning <[email protected]> написал(а):

> On Tue, Sep 23, 2014 at 4:38 PM, Alexey Pavlov <[email protected]> 
> wrote:
>> 
>> 23 сент. 2014 г., в 18:21, Matthieu Vachon <[email protected]> 
>> написал(а):
>> 
>>> I can confirm this issue. I did not investigate further however. In my
>>> case, followed exact update information for updating "core" packages.
>>> Upon restart, impossible to call `pacman` from command line anymore.
>>> Same error message.
>> 
>> Try in bash:
>> cp /usr/bin/msys-nettle{5,4}.dll
>> pacman -S libarchive libnettle
>> rm -f /usr/bin/msys-nettle-4.dll
> 
> The `cp` call should of course be
> 
>    cp /usr/bin/msys-nettle{4,5}.dll
> 
> since I have `msys-nettle4.dll`, but not `msys-nettle5.dll`.
> 
> I can report that with that change `pacman` runs again.  In order to
> get all to work I had to force the install of `libnettle` to return to
> a properly working system though.
> 
> Does this mean that `libnettle` should be included in that list of
> "basic packages" that always should be updated first, i.e. together
> with filesystem msys2-runtime bash libreadline libiconv libarchive
> libgpgme libcurl pacman ncurses libintl?
> 
> Maybe all of `pacman`'s dependencies should be?

libnettle is dependency of libarchive and not pacman directly, first.
Second, this issue with dll’s  name  can’t be resolved by update priority.
After upgrading nettle we get DLL with different name (5 when old is 4). When 
you update it you don’t have anymore old DLL and lib archive can’t work.
If we first update libarchive then new libarchive  want libnettle-5 while in 
system present only libnettle-4 and libarchive not work again.

Regards,
Alexey.

> 
> /M
> 
> -- 
> Magnus Therning                      OpenPGP: 0xAB4DFBA4
> email: [email protected]   jabber: [email protected]
> twitter: magthe               http://therning.org/magnus
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Msys2-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/msys2-users


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users

Reply via email to