August 2013 - Arch-general - lists.archlinux.org

[arch-general] OpenNTPd not correcting time on boot
by Joe Eaves 08 Aug '13

08 Aug '13

Hi, First time posting so forgive me if I get it wrong. (This is already a resend because I used the wrong email previously!) I'm using OpenNTPd as a time server for my local network, but I have a slight issue. I run it on my Raspberry Pi which lacks a hardware clock, so every time I boot it, it thinks the time is 1970. In the systemd init file, openntpd.service, it runs the ntpd daemon with the '-s' option, which tell it that if the time is really far out of sync, just update it straight to the time that the server has. The problem is, this doesn't happen after boot. If I manually set the time with 'date -s @0000000000' and then restart the openntpd service it will work, but not automatically after boot up. I suspect it might be that it's not able to talk to a server because it's starting the service before the network is ready or something, but I'm using a static IP and have told openntpd.service that "wants" and "after" both == network.target. Any ideas? Joe -- *:wq!*

5 7

[arch-general] remote poweroff with systemd
by Fons Adriaensen 07 Aug '13

07 Aug '13

Hello all, In one installation I manage I have a script that (among other actions) remotely shuts down a number of headless machines. Until recently these machines used the traditional init scripts, and the commands in the script were ssh -t remote1 "sudo /sbin/init 0" ssh -t remote2 "sudo /sbin/init 0" etc. This has worked well for years. Recently the machines were upgraded and mow use systemd. I replaced the original commands by ssh -t remote1 "sudo telinit 0" etc. This shuts down the first one OK, but then the script hangs. Apparently the ssh connection isn't closed cleanly. I didn't yet try 'systemctl poweroff', but according the man page, 'telinit 0' is equivalent to it. Another one I didn't yet try (just discovered it in the man pages but I don't have access to the installation ATM) is systemctl's --host option, in other words, let systemctl do the ssh. Can this be expected to work ? If not, any other ideas ? TIA for any help or hints. -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)

10 18

[arch-general] ndiswrapper patch for linux-3.10
by Christian Weber 06 Aug '13

06 Aug '13

Hello, I wrote a patch for ndiswrapper to compile on 3.10 kernels. I also put together a PKGBUILD and made it available in the AUR. The patch: https://raw.github.com/TheWebster/Packaging/master/ARCH/ndiswrapper/kernel-… AUR: https://aur.archlinux.org/packages/ndiswrapper/ Maybe the old maintainer wants to resume maintainership or someone else wants to take it. I will happily maintain it in the AUR but if there are plans to take it back into official repos i'll have to pass for now. Regards Christian Weber

2 1

[arch-general] QEMU: mouse not working in arch guest
by phanisvara 06 Aug '13

06 Aug '13

i've switched from virtualbox to QEMU recently and am quite happy with it -- except that i can't get any mouse working properly in arch guests. others distro i've installed as guests (fedora 19, debian wheezy, even ubuntu) don't have that problem, for some reason only arch does. (i've got xf86-input-vmmouse installed on the guest.) i've exported "SDL_VIDEO_X11_DGAMOUSE=0" before starting qemu, and this seems to lessen the erratical jumping around of the mouse, but it's still unusable. i've also tried to specify "-usbdevice mouse," "-usbdevice tablet," and passing the USB device via vendor- and product ID, to no avail. have been searching quite a bit, but didn't find anything relevant. i'm using quemu-git from AUR now, and while the mouse doesn't jump around erratically, neither the left button nor it's position are being registered, while right button click is (always at the screen's center position, irrespective of mouse movement). would be grateful for any hints re. this. -- phani.

2 3

[arch-general] efivars kernel module not loaded automatically in 3.10 kernel
by Sebastiaan Lokhorst 04 Aug '13

04 Aug '13

Hello fellow Archers, I've noticed that the efivars kernel module is no longer loaded automatically. Previously (I believe also in 3.9), it was loaded by default and commands like gummiboot and efibootmgr would work without any manual loading. The wiki[1] also explains that it should be enabled in the stock Arch kernel. I am not sure if this is intended, but if it is, all UEFI bootloader instructions should be updated because none of them work without efivars. Thanks! Sebastiaan [1] https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#…

1 0

[arch-general] pyalpm 0.6.2
by Rémy Oudompheng 04 Aug '13

04 Aug '13

Hello, pyalpm 0.6.2 has been released to [extra]. The following fixes are included: * pycman: recognize RemoteFileSigLevel and UseDelta=x options (FS#34791) * init_with_config now handles IgnorePkg and similar options (FS#29688) Regards, Rémy.

1 0

[arch-general] Texlive 2013 packages released in [extra]
by Rémy Oudompheng 03 Aug '13

03 Aug '13

On 2013/7/3 Rémy Oudompheng <remyoudompheng(a)gmail.com> wrote: > Hello, > > I have pushed TeXLive 2013 packages to [testing]. > The packages are now available in [extra]. Please read the news announcement for any issues after the upgrade: https://www.archlinux.org/news/texlive-2013-update-may-require-user-interve… Rémy.

1 0

[arch-general] Disabled asm in x264 on i686
by Jens Arm 02 Aug '13

02 Aug '13

Hi ArchLinux-Team Why are asm optimizations disabled in x264 on i686? In the PKGBUILD is written: [[ "$CARCH" == "i686" ]] && _asm='--disable-asm' Are there any bugs when asm is enabled? Regards Jens

3 2

[arch-general] Upstream urls and package descriptions
by Karol Blazewicz 02 Aug '13

02 Aug '13

Intro: Below are some questions / ideas I came up with. I simply don't know if anyone cares about these issues, whether there are rules or at least suggestions how to best deal with them or is it up to the maintainer. I've heard there were some plans wrt a build server that would periodically check if packages still build. Any news? If there indeed are issues that need fixing, should I file the low-priority bugs now? Summer vacation may not be the best time for Arch-related work so maybe I should wait until September so that people are back from holidays? Upstream urls: I found that dozens of packages in the repos have an upstream url that prints 'Page Not Found' in one way or another. Should I open bug reports for these packages or does nobody care about it? I could also check if the source is still available. If opening bug reports is OK, should I limit creating the reports to e.g. 10 a day? If I find a url that works, I will include it as a suggestion for the maintainer. For example for https://www.archlinux.org/packages/community/i686/autocutsel/ neither the url nor the source is available, but I found what seems like a perfectly good autocutsel website: http://www.nongnu.org/autocutsel/ with a link to the source. Some projects seem to be gone for good e.g. https://www.archlinux.org/packages/extra/i686/apricots/ even grabs the sources from ftp.archlinux.org https://projects.archlinux.org/svntogit/packages.git/plain/trunk/PKGBUILD?h… Would http://freecode.com/projects/apricots be a better website? It has some info e.g. that last development is from a decade ago, a screenshot, a longer description ... What about urls that point to a redirect? Is it OK only if the redirect is automatic and otherwise upstream urls should be updated if they moved e.g. from SourceForge to GoogleCode? An example: https://www.archlinux.org/packages/extra/any/junit/ has http://junit.sourceforge.net/ as the upstream url, but when you go there, it says 'Please see our main site at junit.org'. Is there a rule that 'www' should be omitted or that it should be included? https://www.archlinux.org/packages/extra/i686/alsa-lib/ : http://www.alsa-project.org https://www.archlinux.org/packages/extra/any/alsa-firmware/ : http://alsa-project.org/ What about the slash at the end of the url? Sometimes the slash makes a difference: https://www.archlinux.org/packages/community/i686/pidgin-toobars/ uses http://vayurik.ru/wordpress/en/toobars/ and shows (via a redirect) the Russian version http://vayurik.ru/wordpress/toobars while the English version demands no slash at the end of the url: http://vayurik.ru/wordpress/en/toobars The same upstream url can be used by many packages and standardizing would make it a bit easier to find which packages need to have the upstream url updated. Are upstream urls mandatory? https://www.archlinux.org/packages/extra/any/hwdetect/ does not have one. Package descriptions: There was an attempt at improving the descriptions last year, but it didn't go so well https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packag… I don't know if maintainers should write package descriptions or should they just take them from upstream, but IMHO e.g. https://www.archlinux.org/packages/extra/i686/kdeplasma-addons-wallpapers-v… : 'Description: Virus' has to go. Even https://www.archlinux.org/packages/extra/i686/kdeplasma-addons-wallpapers-w… - Weather or https://www.archlinux.org/packages/extra/i686/kdetoys-ktux/ - KTux are pretty bad descriptions. Quite a few descriptions could be more informative, but I don't know if anyone cares about it e.g. description for https://www.archlinux.org/packages/extra/i686/kdeutils-ktimer/ says 'Countdown Launcher' and is IMHO too terse. Should I suggest changing it upstream, will the maintainer change it to a more descriptive one or is it considered just pointless churn? Similarly, https://www.archlinux.org/packages/extra/i686/kdeplasma-addons-applets-calc… could be described as e.g. 'A simple calculator' instead of the current 'Calculate simple sums'. Is adding 'data files' phrase to descriptions of packages that provide architecture-independent data recommended? I've noticed many packages share the same description, usually because it's a generic one: monica - A monitor calibration tool kdegraphics-kgamma - A monitor calibration tool or because the packages represent different version of e.g. the same toolkit: qt3 - A cross-platform application and UI framework qt4 - A cross-platform application and UI framework Sometimes the descriptions explicitly says it's a python2 thing: python2-atspi - Python 2 bindings for at-spi python2-dbus - Python 2.7 bindings for DBUS Some language-related packages use the same description for all of them e.g. xpdf-korean - Encoding information to use specific character sets in Xpdf; does not include fonts vim-spell-af - Language files for Vim spell checking Other packages, like firefox-i18n-* or libreoffice-* adjusted the description for each package: firefox-i18n-af - Afrikaans language pack for Firefox libreoffice-af - Afrikaans language pack for LibreOffice Is one way preferred over the other or is it up to the maintainer? Should language files always have a description that says which language do they represent or are package names enough? I also found https://www.archlinux.org/packages/extra/any/libreoffice-sid/ - ??? language pack for LibreOffice https://www.archlinux.org/packages/extra/any/libreoffice-tt/ - TT ? language pack for LibreOffice What's this?

7 10