On 24. 4. 2015 11:34, Rainer Schuetz wrote: > Dear all, > > I just updated the msys core using: > > pacman -Sy;pacman --needed -S bash pacman pacmanmirrors msys2-runtime > > > I wasn’t paying attention closely, unfortunately, but I think two components > got updated: pacman and msys2-runtime (my last update can’t have been older > than 2 days or so). > Since then I cannot start my shells anymore, I just get a one liner stating: > > Failed to fork child process: No such file or directory. > > Could somebody tell me what to do?
Hi. I'm only guessing that the update process deleted some files and failed to replace them with new versions. Some information about that could be hidden in /var/log/pacman.log. Are you able to run bash or pacman from cmd? You can look into your /var/cache/pacman/pkg and extract latest bash and msys2-runtime packages manually. Hopefully some of this helps. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
