[arch-general] OpenRA / Mono exceptions

2018-03-02 Thread Alajos Odoyle
Hi all, When trying to run OpenRA from the community repository or when building the package myself (using the community PKGBUILD) I get Mono exceptions like the one below [1]. At first I thought it could be an upstream issue but sure enough it builds just fine when using a clean chroot. As I

Re: [arch-general] OpenRA / Mono exceptions

2018-03-02 Thread Dan Haworth
On 02/03/18 10:34, Alajos Odoyle wrote: Hi all, When trying to run OpenRA from the community repository or when building the package myself (using the community PKGBUILD) I get Mono exceptions like the one below [1]. At first I thought it could be an upstream issue but sure enough it builds

Re: [arch-general] OpenRA / Mono exceptions

2018-03-02 Thread Alajos Odoyle
On 2018-03-02 11:38, Dan Haworth wrote: I had the same issue, seems to be related to the following bug https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0 to get things going again. --dan Thanks, that was quick! I also had to install libtinfo5 (AUR) and symlink /usr/lib/

Re: [arch-general] OpenRA / Mono exceptions

2018-03-02 Thread Dan Haworth
On 02/03/18 11:17, Alajos Odoyle wrote: On 2018-03-02 11:38, Dan Haworth wrote: I had the same issue, seems to be related to the following bug https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0 to get things going again. --dan Thanks, that was quick! I also had to insta

Re: [arch-general] OpenRA / Mono exceptions

2018-03-02 Thread Levente Polyak via arch-general
On March 2, 2018 12:38:33 PM GMT+01:00, Dan Haworth wrote: >On 02/03/18 11:17, Alajos Odoyle wrote: >> On 2018-03-02 11:38, Dan Haworth wrote: >>> >>> I had the same issue, seems to be related to the following bug >>> https://github.com/mono/mono/issues/6752. I downgraded ncurses to >6.0 >>> to

Re: [arch-general] Intel microcode - latest version not loading

2018-03-02 Thread Mike Cloaked via arch-general
There is a newer version of that file dated February 26th but I can't remember where I downloaded it from. On Thu, Mar 1, 2018 at 7:59 PM, Dutch Ingraham wrote: > On Thu, Mar 01, 2018 at 08:13:08PM +0100, ProgAndy wrote: > > Am 01.03.2018 um 00:41 schrieb Dutch Ingraham: > > > On Wed, Feb 28, 20

Re: [arch-general] Intel microcode - latest version not loading

2018-03-02 Thread Mike Cloaked via arch-general
> > >> That's excellent information. Apparently, my 8 year old Core2 may soon be >> getting its first MCU! >> > > > My apologies for top posting - it was accidental. There is a newer version of that file dated February 26th but I can't remember where I downloaded it from. I've put it at https://

Re: [arch-general] Intel microcode - latest version not loading

2018-03-02 Thread Dutch Ingraham
On Fri, Mar 02, 2018 at 08:10:45PM +, Mike Cloaked via arch-general wrote: > There is a newer version of that file dated February 26th but I can't > remember where I downloaded it from. > > I've put it at > https://filebin.net/q3s5in117kp7mkut/microcode-update-guidance.pdf if you > want to see

[arch-general] Reliability test for hard drives and SSD

2018-03-02 Thread Andrey Ponomarenko via arch-general
Hi there! Good news for all interested in hardware compatibility and reliability. I've started a new project to estimate reliability of hard drives and SSD in real-life conditions based on the SMART data reports collected by Linux users in the Linux-Hardware.org database since 2014. The initial

[arch-general] Why no git --depth=1 option for makepkg?

2018-03-02 Thread Adam Levy via arch-general
Hi I recently came across this closed feature request for a way to perform a shallow clone with makepkg. https://bugs.archlinux.org/task/52957 The closing comment was: Closed by Andrew Gregory (andrewgregory) Monday, 13 February 2017, 17:29 GMT-9 Reason for closing: Won't implement Additional

Re: [arch-general] Reliability test for hard drives and SSD

2018-03-02 Thread Ralf Mardorf
On Sat, 03 Mar 2018 10:20:51 +0300, Andrey Ponomarenko wrote: >The primary aim of the project is to find drives with longest "power >on hours" and minimal number of errors. Pardon, but this is idiotic, since the HDDs and SSDs with the longest power on hours and minimal number of errors are already