- Arch-general - lists.archlinux.org

Re: [arch-general] Espeak in official repositories needs an overhaul
by Daniel M. Capella 09 Mar '18

09 Mar '18

https://aur.archlinux.org/packages/espeak-ng PS: Resending to (hopefully) fix the thread and avoid confusion. My apologies for being terrible at mailing lists. PPS: Just in case this doesn't work: https://lists.archlinux.org/ pipermail/arch-general/2017-December/044513.html

1 0

Re: [arch-general] [arch-dev-public] LLVM 6 and splitting up {clang, lld, lldb, compiler-rt} into separate PKGBUILDs
by Jordan Glover 09 Mar '18

09 Mar '18

On March 9, 2018 1:26 PM, Evangelos Foutras via arch-dev-public <arch-dev-public(a)archlinux.org> wrote: > I pushed llvm 6.0.0-1 to \[staging\] without the rest of the packages > > mentioned in the subject. I am planning to add them back as individual > > packages in the following days. > > This separation will bring faster builds when one of these components needs > > patching. It also allows building clang with shared libraries and merging > > the extra-tools package into it (thus fixing https://bugs.archlinux.org/tas > > k/50865). > > Once everything is in \[staging\], I'll create a TODO list for rebuilds as > > usual. Just in case if you don't already know this: -fno-plt is available in clang 6[1]. You can drop the no-op patch. [1] https://reviews.llvm.org/rL317605 Jordan

1 0

[arch-general] Espeak in official repositories needs an overhaul
by Daniel Capella 08 Mar '18

08 Mar '18

https://aur.archlinux.org/packages/espeak-ng -- Best, polyzen

1 0

[arch-general] OpenRA / Mono exceptions
by Alajos Odoyle 05 Mar '18

05 Mar '18

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 did not customize the mono package and cannot think of anything else causing this (configuration?), i hope someone here might have some ideas. NB, I never used Mono before - it was auto-installed as a dependency of OpenRA. Thanks, Alajos [1]: Unhandled Exception: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.ConsoleDriver..cctor () [0x0004d] in <a84b655e5e6a49ee96b338ec792f5580>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.Console..cctor () [0x0008e] in <a84b655e5e6a49ee96b338ec792f5580>:0 --- End of inner exception stack trace --- at Mono.CSharp.Driver.Main (System.String[] args) [0x00019] in <2b1e99ce45b54209bdcdab138d9758ae>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.ConsoleDriver..cctor () [0x0004d] in <a84b655e5e6a49ee96b338ec792f5580>:0 --- End of inner exception stack trace --- at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a84b655e5e6a49ee96b338ec792f5580>:0 at System.Console..cctor () [0x0008e] in <a84b655e5e6a49ee96b338ec792f5580>:0 --- End of inner exception stack trace --- at Mono.CSharp.Driver.Main (System.String[] args) [0x00019] in <2b1e99ce45b54209bdcdab138d9758ae>:0 make: *** [Makefile:278: OpenRA.Game.exe] Error 1

6 11

[arch-general] Why no git --depth=1 option for makepkg?
by Adam Levy 05 Mar '18

05 Mar '18

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 comments about closing: This has been rejected numerous times: https://wiki.archlinux.org/index.php/Use r:Apg#makepkg:_shallow_git_clones Which provides a now dead link. Would anyone in the know be willing to explain why this feature is considered outside the scope of makepkg? Clearly if the developers aren't interested in the feature, well then they just won't want to support it. But if there is some rationale behind this I am curious about it. On one hand this is pure curiosity, but on the other hand, I use makepkg and the Arch packaging system multiple times per week so I like to understand the design and the intent. Thank you! Adam Levy (alaskanarcher)

9 15

[arch-general] Intel microcode - latest version not loading
by Dutch Ingraham 03 Mar '18

03 Mar '18

Hi all: I'm having an issue with Intel microcode loading. Specifically, the microcode does not appear to be loading the latest version: ~ $ dmesg | grep microcode [ 0.000000] microcode: microcode updated early to revision 0x19, date = 2013-06-21 [ 0.931272] microcode: sig=0x106a5, pf=0x2, revision=0x19 [ 0.931319] microcode: Microcode Update Driver: v2.2. My processor is: ~ $ grep -E 'family|model|stepping' -m 4 /proc/cpuinfo cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3503 @ 2.40GHz stepping : 5 The Intel website indicates the latest version of microcode for this processor is version 20171117 [1]. However, as indicated above, the version loaded at boot is dated 2013-06-21. I have the latest stable version of intel-ucode installed: ~ $ pacman -Q intel-ucode intel-ucode 20180108-1 I have updated GRUB with <grub-mkconfig -o /boot/grub/grub.cfg>, and rebooted. The grub.cfg file shows, as the last line in the menuentry: 'initrd /boot/intel-ucode.img /boot/initramfs-linux.img' I am using a stock kernel: ~ $ uname -a Linux arch2 4.15.5-1-ARCH #1 SMP PREEMPT Thu Feb 22 22:15:20 UTC 2018 x86_64 GNU/Linux Can someone help me determine what is going on here? [1] https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-D…

5 10

[arch-general] Arch Linux on MacBookPro13,3
by Jeremy Brown 02 Mar '18

02 Mar '18

Hey Arch folks, I have a work-provided laptop which is a MacBookPro13,3; in other words a fairly recent MacBook Pro (one of the touch bar ones). I've shrunk the root partition on it and would like to install Arch on a second partition and use that as my primary OS. I've been able to do this with previous versions of MacBook Pros no problem. However, doing some research it appears as though installing Linux on this hardware is difficult and many of the components either require extensive customization (e.g. building your own drivers) or don't work at all: https://github.com/Dunedan/mbp-2016-linux https://gist.github.com/roadrunner2/1289542a748d9a104e7baec6a92f9cd7 Assuming that page is correct audio, wifi, and suspend not working (or barely working) are going to be dealbreakers for me, I think. I'm going to take a crack at it in the next few days but wondered if anyone in arch-general had any success with similar hardware. Is it livable, or is the driver support and such just not there yet? Cheers, Jeremy

2 1

[arch-general] emby-server package outdated
by Patrick Dijkgraaf 28 Feb '18

28 Feb '18

Hi all, I hope this is the right place to ask, the bugtracker says to use "the Mailing List", but not which Mailing List, for reporting outdated packages... If this is the wrong place, please point me to the right one! Here's the info: * Package name: emby-server * Current version in the Arch repo: 3.2.60.0-1 * Last updated: 2017-12-23 14:43 UTC * Flagged out-of date: 2018-01-18 (shortly after version 3.2.70.0 was released) We are now more than a month later, and another new version has been released, namely 3.3.0.0. What would be the way to go to get this package updated? -- Cheers, Patrick Dijkgraaf

1 0

[arch-general] dhcpcd-7.0.1-1 seems to break SLAAC
by Jukka Salmi 26 Feb '18

26 Feb '18

Hello Since upgrading dhcpcd from 6.11.5-1 to 7.0.1-1 my (VLAN) interface doesn't get an IPv6 address (via SLAAC) anymore. The netctl profile in question: Interface=enp0s25.100 Connection=vlan BindsToInterfaces=enp0s25 VLANID=100 IP=dhcp IP6=stateless With dhcpcd-6.11.5-1 starting this netctl profile results in an IPv4 address being configured via DHCP and an IPv6 address being configured via SLAAC as expected. With dhcpcd-7.0.1-1 starting this netctl profile results in an IPv4 address being configured via DHCP, but no IPv6 address is configured. In both cases, netctl passes dhcpcd the same arguments: dhcpcd -4 -q -t 30 -L enp0s25.100 so that's probably not the source of the problem. If I disable IPv4 DHCP (by setting `IP=no' in the above netctl profile), SLAAC works fine again (but of course then I don't get an IPv4 address via DHCP anymore...). Is anybody seeing the same issue? Is really dhcpcd to blame? TIA & cheers, Jukka -- This email fills a much-needed gap in the archives.

2 2

[arch-general] linux kernel 4.15.4-1 un-bootable
by David Rosenstrauch 24 Feb '18

24 Feb '18

Ran into a weird issue today. I upgraded a bunch of packages, including the kernel to v4.15.4-1 (from 4.15.3-1). But for some reason the system was un-bootable. The boot process would get part-way through, then the booting screen would suddenly start showing its text on a green background (rather than black) and it would freeze. It took some jumping through hoops, but I was eventually able to boot to a chroot environment, upgrade to a newer kernel (v4.15.5-1) and suddenly the problem magically went away and my machine boots fine. Anyone have any idea what might have happened here? I'm assuming it was a bad kernel build, but I'd like to know for sure. I didn't see any recent bugs under the "linux" kernel package that matched what I was seeing. Thanks, DR

3 3