[SOLVED]Nomenclature in virtualbox packages

╔═[20:17]═[inxs @ wolfdale]
╚═══===═══[~]>> pacs virtualbox
community/libvirt 0.8.8-1
API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)
community/virtualbox 4.0.4-2
Powerful x86 virtualization for enterprise as well as home use
community/virtualbox-additions 4.0.4-1
CD image containing guest additions for VirtualBox
community/virtualbox-guest-additions 4.0.4-2
VirtualBox user-space tools for Linux guests
community/virtualbox-guest-modules 4.0.4-2
VirtualBox kernel modules for Linux guests
community/virtualbox-sdk 4.0.4-2
VirtualBox Software Developer Kit (SDK)
why is cd image containing guest additions for Virtualbox named as virtualbox-additions and user space tools for Linux guests named virtualbox-guest-additions. Shouldn't it be the other way round?

I recall Ionut (wonder, ioni etc.) once said (to me) that he will do the renaming as he updates the packages from time to time. He probably forgot or is shying away from the matter since it's (1) just renaming and therefore (2) too much of a hassle for the complicated packaging steps it requires.

Similar Messages

[SOLVED] Setting up virtualbox & wine and on x86_64

Hello again
Ok so this should be my last annoying noob post, I have 64-bit Arch setup correctly with gnome and everything. However, I still have a few questions starting with how do I install virtualbox & wine on x86_64? I tried to install virtualbox with pacman -S virtualbox_bin 3.1.2-1 and that didn't work and I haven't even made an attempt with wine yet. Can I safely install a bin32 version of wine? - The wiki didn't make that very clear.
Additionally, I have copied a lot of backup data to my home folder that belongs to the user 'root'. Is there a way that I can, via command line make everything in my home belong to my user?
Last edited by dcj123 (2009-12-29 02:40:31)

anonymous_user wrote:
Both programs can be found in the AUR:
http://aur.archlinux.org/packages.php?ID=9753
http://aur.archlinux.org/packages.php?ID=7915
You can install yaourt first and then use it to install other packages from AUR:
http://wiki.archlinux.org/index.php/Yaourt
ok thanks, I am just going to assume that its safe to install wine bin32. In the mean time, if I chown username my home folder will that change the ownership of every sub-directory/file?
Edit: Found it, thanks anonymous_user.
chown -hvR user /home/user
Solved
Last edited by dcj123 (2009-12-29 02:40:08)

[Solved] problem with virtualbox-iso-additions for virtualbox v. 4.2

VirtualBox 4.2 was released recently and one of the features mentioned is support for Mac OSX. However, having installed it (an Arch virtualbox 4.2 host, and an osx guest), I found that I couldn't install guest additions via the devices menu on my osx guest. Whereupon I examined the file corresponding to virtualbox-iso-additions (/usr/lib/virtualbox/additions/VBoxGuestAdditions.iso) and found that in fact there were no scripts or drivers for osx (darwin) like there are for windows and linux. Is it possible that the Arch release of this file has not been updated properly or am I missing anything else?
Update: I downloaded the current iso (VBoxGuestAdditions_4.2.0.iso) from http://download.virtualbox.org/virtualbox/4.2.0/ and found that that too has no files that appear linked to osx or darwin. That rules out an Arch packaging issue and I'll need to pursue things at virtualbox.org itself.
Last edited by kinleyd (2013-07-18 12:03:48)

I think I've figured it out, finally. It seems v. 4.2 introduces virtualbox on a mac osx host. osx guests are apparently not officially supported with guest additions. I had assumed that host support already existed, and that the new stuff in v. 4.2 was for guests.

How to solve problem with Installer Package for itunes

Hi! I'm attempting to upadte itunes so I can get the latest software for my iphone. It's a 3GS. Every time when ready to instal it says I have a problem with the installer package - something is missing. What can I do to solve this?

Repair your Apple software update.
Go to START/ALL PROGRAMS/Apple Software Update. If it offers you a newer version of Apple Software Update, do it but Deselect any other software offered at the same time. Once done, try another iTunes install
If you don't find ASU, go to Control Panel:
START > CONTROL PANEL >
Add n Remove Programs(XP)
Programs n Features(Win7/Vista)
highlight ASU and click CHANGE then REPAIR,

How to solve this error 'This package is using an app name that hasn't been reserved for this app: "Matest"

i already reserved app name as Ma_Test. But only one error showing "This package is using an app name that hasn't been reserved for this app: "Matest". how to solve?

Hello,
You need to make sure both names match exactly

[SOLVED] Make Pacman cache packages installed with -U

When installing a package with -U, pacman doesn't cache packages as it does when installing with -S. Is there a way to change this behavior?
I read somewhere that specifying the package's full path and prepending "file://", as in "pacman -U file://path/to/package.pkg.tar.xz", but this often complains of an "invalid or corrupted package (PGP signature)".
How can I make pacman always copy installed packages to the cache?
MOD EDIT: change 'closed' to 'solved' in title to avoid confusion
Last edited by fukawi2 (2013-07-06 13:09:21)

You can't. This has been discussed on the bugtracker several times.
https://bugs.archlinux.org/task/35699
https://bugs.archlinux.org/task/31243
https://bugs.archlinux.org/task/15143
https://bugs.archlinux.org/task/18012
If you're building the packages yourself with makepkg, you can set PKGDEST to your cache in makepkg.conf. Otherwise you could write a small pacman wrapper that copies the package after installing it.

[SOLVED]How to search package name only when using yaourt

I often install a AUR package by yaourt term, but it does not only search terms in package name but also package description, since there are so much packages in AUR, it produce many pages of items, and it can not support more to page one screenful at a time, It
become difficult to get the right choice,
Thank you in advance!
Last edited by netawater (2013-06-14 00:47:06)

Hey, that's one thing I actually know how to do with regexes! All package descriptions have some spaces at their beginning, the package names themselves have not, so you can just use inverted grepping like so:
$ pacman -Ss test | grep -v '^ '
core/perl 5.10.1-5 (base)
extra/fprint_demo 0.4-2 (fprint)
extra/ghc 6.12.1-2
extra/haskell-hunit 1.2.2.1-1
extra/haskell-quickcheck 2.1.0.3-1
extra/junit 4.7-1
extra/kdesdk-kpartloader 4.4.0-1 (kde kdesdk)
extra/libxtst 1.1.0-1
extra/memtest86+ 4.00-1
extra/mono-tools 2.6.1-1
extra/openoffice-base 3.2.0-1
extra/openoffice-base-beta 3.2.0_ooo320_m12-1
extra/perl-test-pod 1.41-1
extra/python-nose 0.11.1-1
extra/qemu-kvm 0.12.2-1
extra/testdisk 6.11.3-2
extra/unarj 2.63a-2
extra/xbill 2.1-6
xyne-any/reflector 5.0-2
community/buildbot 0.7.11p3-1
community/cppunit 1.12.1-1
community/cxxtest 3.10.1-3
community/dsniff 2.4b1-15
community/gtk-aurora-engine 1.5.1-1
community/gtkperf 0.40-3
community/java-jdom 1.1.1-1
community/lib32-libxtst 1.1.0-1 (lib32)
community/perl-test-base 0.59-1
community/perl-test-deep 0.106-1
community/perl-test-differences 0.500-1
community/perl-test-exception 0.29-1
community/perl-test-manifest 1.23-1
community/perl-test-mockobject 1.09-1
community/perl-test-nowarnings 1.01-1
community/perl-test-tester 0.107-1
community/perl-test-warn 0.21-2
community/phoronix-test-suite 2.4.0-1
community/pmtools 20100123-1
community/reflector 5.0-2
community/stress 1.0.0-2
community/typespeed 0.6.5-2
arch-games/mangler-snapshot 1.1.20100116-3
arch-games/ultimatestunts 0.7.5.1-1
This still shows the repos and the versions (nothing cut wouldn't be able to handle though). It works fine with pacman as you just saw, I can't guarantee for yaourt as I don't have it installed.
Edit: Hm… I just realized that this still displays the results where 'test' only occured in the package description. Give me some time to figure this out.
Edit 2: Another grep for 'test' would solve it:
$ pacman -Ss test | grep -v '^ ' | grep test
extra/memtest86+ 4.00-1
extra/perl-test-pod 1.41-1
extra/testdisk 6.11.3-2
community/cxxtest 3.10.1-3
community/perl-test-base 0.59-1
community/perl-test-deep 0.106-1
community/perl-test-differences 0.500-1
community/perl-test-exception 0.29-1
community/perl-test-manifest 1.23-1
community/perl-test-mockobject 1.09-1
community/perl-test-nowarnings 1.01-1
community/perl-test-tester 0.107-1
community/perl-test-warn 0.21-2
community/phoronix-test-suite 2.4.0-1
arch-games/ultimatestunts 0.7.5.1-1
Still, it's not that pretty to write the same thing twice. If you really want to do it like this, I suggest you make it a function in your ~/.${SHELL}rc.
Last edited by Runiq (2010-02-27 08:36:11)

[solved] Help troubleshoot Virtualbox hanging (possible btrfs related)

Sometime longer than a week ago I did not have this problem.
Yesterday I encountered it for the first time. Starting a windows 8 VM works all the way through the apps screen and then it just hangs. No way to quit virtualbox. Weirdly enough, Firefox is still working at this point but becomes unresponsive after a while as well. My WM (awesome) and terminals are unaffected, but kill/killall doesn't work.
On shutdown I see this error (first code box below). I have done btrfsck on all my partitions since then, still the same problem.
My pacman log for the past 10 days is in the second code box below. I have tried downgrading to linux-3.11.1-1 and 3.11-1 without success. 3.11-1 allows me to get past the apps screen, but once I open a document in the VM it becomes unresponsive again, so the bug is just being delayed.
This laptop is heavily used and no other unresponsivity was noted this past week prior to using VirtualBox.
Final point, I'm fully updated using [testing].
Any suggestions would be appreciated, I'm quite stumped at this point. Considering creating a new VM to test whether my image is faulty....
Sep 25 11:24:01 ngoonee-laptop kernel: ------------[ cut here ]------------
Sep 25 11:24:01 ngoonee-laptop kernel: kernel BUG at fs/btrfs/ctree.c:2964!
Sep 25 11:24:02 ngoonee-laptop kernel: invalid opcode: 0000 [#1] PREEMPT SMP
Sep 25 11:24:02 ngoonee-laptop kernel: Modules linked in: ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables pci_stub vboxpci(O) vboxnetflt(O) vboxneta
Sep 25 11:24:02 ngoonee-laptop kernel: i2c_core mei_me mei serio_raw battery evdev processor shpchp ac thermal button mxm_wmi vboxdrv(O) vhba(O) asus_nb_wmi asus_wmi sparse_keymap rfkill wmi video btrfs libcrc3
Sep 25 11:24:02 ngoonee-laptop kernel: CPU: 0 PID: 435 Comm: btrfs-endio-wri Tainted: G O 3.11.0-1-ARCH #1
Sep 25 11:24:02 ngoonee-laptop kernel: Hardware name: ASUSTeK COMPUTER INC. N56VJ/N56VJ, BIOS N56VJ.203 08/29/2012
Sep 25 11:24:02 ngoonee-laptop kernel: task: ffff88021e1721c0 ti: ffff880222da6000 task.ti: ffff880222da6000
Sep 25 11:24:02 ngoonee-laptop kernel: RIP: 0010:[<ffffffffa02a6d21>] [<ffffffffa02a6d21>] btrfs_set_item_key_safe+0x161/0x170 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: RSP: 0018:ffff880222da7b18 EFLAGS: 00010286
Sep 25 11:24:02 ngoonee-laptop kernel: RAX: 00000000ffffffff RBX: 0000000000000027 RCX: 000000002fa00000
Sep 25 11:24:02 ngoonee-laptop kernel: RDX: 00000000ffffffff RSI: ffff880222da7c1e RDI: ffff880222da7b37
Sep 25 11:24:02 ngoonee-laptop kernel: RBP: ffff880222da7b70 R08: 0000000000000001 R09: ffff880222da7b38
Sep 25 11:24:02 ngoonee-laptop kernel: R10: 000000002fa60000 R11: 000000002fa60000 R12: ffff880222da7b26
Sep 25 11:24:02 ngoonee-laptop kernel: R13: ffff8801cd7f23f0 R14: ffff880222da7c1e R15: ffff880217e95040
Sep 25 11:24:02 ngoonee-laptop kernel: FS: 0000000000000000(0000) GS:ffff88022ee00000(0000) knlGS:0000000000000000
Sep 25 11:24:02 ngoonee-laptop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 25 11:24:02 ngoonee-laptop kernel: CR2: 00000032768abac0 CR3: 000000000180d000 CR4: 00000000001427f0
Sep 25 11:24:02 ngoonee-laptop kernel: Stack:
Sep 25 11:24:02 ngoonee-laptop kernel: ffff8802218a7800 4511ffffa02e0c39 006c00000000000f 11000000002f9f80
Sep 25 11:24:02 ngoonee-laptop kernel: 6c00000000000f45 000000002f9f8000 ffff880217e95040 000000002fa00000
Sep 25 11:24:02 ngoonee-laptop kernel: 0000000000000000 ffff8801cd7f23f0 00000000000007b8 ffff880222da7c68
Sep 25 11:24:02 ngoonee-laptop kernel: Call Trace:
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02ddfa9>] __btrfs_drop_extents+0x559/0xac0 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02deff0>] btrfs_drop_extents+0x60/0x90 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02cf7ec>] insert_reserved_file_extent.constprop.58+0x6c/0x290 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02d6cae>] btrfs_finish_ordered_io+0x52e/0x9a0 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff8106ed62>] ? del_timer_sync+0x52/0x60
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff814dbc5c>] ? schedule_timeout+0x13c/0x290
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff8106e170>] ? detach_if_pending+0x120/0x120
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02d7305>] finish_ordered_fn+0x15/0x20 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02f737e>] worker_loop+0x14e/0x550 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff81093832>] ? default_wake_function+0x12/0x20
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffffa02f7230>] ? btrfs_queue_worker+0x330/0x330 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff810836a0>] kthread+0xc0/0xd0
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff810835e0>] ? kthread_create_on_node+0x120/0x120
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff814e892c>] ret_from_fork+0x7c/0xb0
Sep 25 11:24:02 ngoonee-laptop kernel: [<ffffffff810835e0>] ? kthread_create_on_node+0x120/0x120
Sep 25 11:24:02 ngoonee-laptop kernel: Code: 48 8b 45 bf 48 8d 7d c7 4c 89 f6 48 89 45 d0 0f b6 45 be 88 45 cf 48 8b 45 b6 48 89 45 c7 e8 a7 f2 ff ff 85 c0 0f 8f 48 ff ff ff <0f> 0b 0f 0b 66 66 2e 0f 1f 84 00 00
Sep 25 11:24:02 ngoonee-laptop kernel: RIP [<ffffffffa02a6d21>] btrfs_set_item_key_safe+0x161/0x170 [btrfs]
Sep 25 11:24:02 ngoonee-laptop kernel: RSP <ffff880222da7b18>
Sep 25 11:24:03 ngoonee-laptop kernel: ---[ end trace 80929b31898e484c ]---
[2013-09-16 12:01] [PACMAN] Running 'pacman -Syu'
[2013-09-16 12:01] [PACMAN] synchronizing package lists
[2013-09-16 12:02] [PACMAN] starting full system upgrade
[2013-09-16 12:06] [ALPM-SCRIPTLET] > Ardour now supports video timeline. To use this feature, please get
[2013-09-16 12:06] [ALPM-SCRIPTLET] > static builds of the required external runtime dependencies from:
[2013-09-16 12:06] [ALPM-SCRIPTLET]
[2013-09-16 12:06] [ALPM-SCRIPTLET] http://x42.github.io/harvid/
[2013-09-16 12:06] [ALPM-SCRIPTLET]
[2013-09-16 12:06] [ALPM-SCRIPTLET] > You may then install the binaries in /usr/local/bin and import a video
[2013-09-16 12:06] [ALPM-SCRIPTLET] > via Session > Open Video.
[2013-09-16 12:06] [ALPM-SCRIPTLET]
[2013-09-16 12:06] [ALPM-SCRIPTLET] > Due to uncertainties with regards to program stability, 'harvid' is
[2013-09-16 12:06] [ALPM-SCRIPTLET] > currently not packaged in our repositories.
[2013-09-16 12:06] [ALPM-SCRIPTLET]
[2013-09-16 12:06] [ALPM-SCRIPTLET] > In addition to the timeline, video can be monitored with xjadeo.
[2013-09-16 12:06] [PACMAN] upgraded ardour (3.3-1 -> 3.4-1)
[2013-09-16 12:07] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-09-16 12:07] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> ERROR: file not found: `fsck.btrfs'
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> WARNING: No fsck helpers found. fsck will not be run on boot.
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-16 12:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-09-16 12:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-16 12:07] [PACMAN] upgraded linux (3.11-1 -> 3.11.1-1)
[2013-09-16 12:07] [PACMAN] upgraded bbswitch (0.7-13 -> 0.7-14)
[2013-09-16 12:07] [ALPM-SCRIPTLET] Generating locales...
[2013-09-16 12:07] [ALPM-SCRIPTLET] en_GB.UTF-8... done
[2013-09-16 12:07] [ALPM-SCRIPTLET] en_GB.ISO-8859-1... done
[2013-09-16 12:07] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-09-16 12:07] [ALPM-SCRIPTLET] en_US.ISO-8859-1... done
[2013-09-16 12:07] [ALPM-SCRIPTLET] Generation complete.
[2013-09-16 12:07] [PACMAN] upgraded glibc (2.18-3 -> 2.18-4)
[2013-09-16 12:07] [PACMAN] upgraded bluez-libs (5.7-1 -> 5.8-1)
[2013-09-16 12:07] [PACMAN] upgraded bluez-utils (5.7-1 -> 5.8-1)
[2013-09-16 12:07] [PACMAN] upgraded cinelerra-cv (1:2.2-17 -> 1:2.2-18)
[2013-09-16 12:07] [PACMAN] upgraded hdf5 (1.8.10_patch1-1 -> 1.8.11-1)
[2013-09-16 12:07] [PACMAN] upgraded lib32-glibc (2.18-3 -> 2.18-4)
[2013-09-16 12:07] [PACMAN] upgraded linux-headers (3.11-1 -> 3.11.1-1)
[2013-09-16 12:07] [PACMAN] upgraded lirc-utils (1:0.9.0-59 -> 1:0.9.0-60)
[2013-09-16 12:07] [PACMAN] upgraded meld (1.7.5-1 -> 1.8.0-1)
[2013-09-16 12:07] [PACMAN] upgraded nvidia (325.15-6 -> 325.15-7)
[2013-09-16 12:07] [PACMAN] upgraded postgresql-libs (9.3.0-2 -> 9.3.0-3)
[2013-09-16 12:07] [PACMAN] upgraded sip (4.15.1.908d49322dcf-1 -> 4.15.2-1)
[2013-09-16 12:07] [PACMAN] upgraded python-sip (4.15.1.908d49322dcf-1 -> 4.15.2-1)
[2013-09-16 12:07] [PACMAN] upgraded python2-sip (4.15.1.908d49322dcf-1 -> 4.15.2-1)
[2013-09-16 12:07] [PACMAN] upgraded raptor (2.0.9-2 -> 2.0.10-2)
[2013-09-16 12:07] [PACMAN] upgraded valgrind (3.8.1-3 -> 3.8.1-4)
[2013-09-16 12:07] [ALPM-SCRIPTLET] > Updating module dependencies...
[2013-09-16 12:07] [PACMAN] upgraded vhba-module (20130607-13 -> 20130607-14)
[2013-09-16 12:07] [PACMAN] upgraded vigra (1.9.0-5 -> 1.9.0-6)
[2013-09-16 12:07] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-09-16 12:07] [PACMAN] upgraded virtualbox-host-modules (4.2.18-2 -> 4.2.18-3)
[2013-09-16 12:07] [PACMAN] upgraded xorg-luit (1.1.1-1 -> 1.1.1-2)
[2013-09-16 13:57] [PACMAN] Running '/usr/bin/pacman -S --asdeps lsb-release'
[2013-09-16 13:58] [PACMAN] installed lsb-release (1.4-13)
[2013-09-16 13:58] [PACMAN] Running '/usr/bin/pacman -U /home/ngoonee/cower/google-talkplugin/google-talkplugin-4.5.3.0-1-x86_64.pkg.tar.xz'
[2013-09-16 13:58] [PACMAN] installed google-talkplugin (4.5.3.0-1)
[2013-09-17 07:33] [PACMAN] Running 'pacman -Syu'
[2013-09-17 07:33] [PACMAN] synchronizing package lists
[2013-09-17 07:33] [PACMAN] starting full system upgrade
[2013-09-17 07:34] [PACMAN] upgraded btrfs-progs (0.20rc1.2-2 -> 0.20rc1.3-1)
[2013-09-17 07:34] [PACMAN] upgraded gnome-desktop (1:3.8.3-2 -> 1:3.8.4-1)
[2013-09-17 07:34] [PACMAN] upgraded gnome-settings-daemon (3.8.4-2 -> 3.8.5-1)
[2013-09-17 07:34] [PACMAN] upgraded gnome-themes-standard (3.8.3-1 -> 3.8.4-1)
[2013-09-17 07:34] [PACMAN] upgraded icedtea-web-java7 (1.4-2 -> 1.4.1-1)
[2013-09-17 07:34] [PACMAN] upgraded intel-tbb (4.1_20130613-1 -> 4.2_20130725-1)
[2013-09-17 07:34] [PACMAN] upgraded lib32-libsm (1.2.1-1 -> 1.2.2-1)
[2013-09-17 07:34] [PACMAN] upgraded lib32-libx11 (1.6.1-1 -> 1.6.2-1)
[2013-09-17 07:34] [PACMAN] upgraded lib32-libxrandr (1.4.1-1 -> 1.4.2-1)
[2013-09-17 07:34] [PACMAN] upgraded lib32-libxv (1.0.9-1 -> 1.0.10-1)
[2013-09-17 07:34] [PACMAN] upgraded libpng (1.6.3-1 -> 1.6.5-1)
[2013-09-17 07:34] [PACMAN] upgraded orc (0.4.17-1 -> 0.4.18-1)
[2013-09-17 07:34] [PACMAN] upgraded python-setuptools (1.0-1 -> 1.1.5-1)
[2013-09-17 07:34] [PACMAN] upgraded python2-setuptools (1.0-1 -> 1.1.5-1)
[2013-09-17 07:34] [PACMAN] upgraded serf (1.3.0-1 -> 1.3.1-1)
[2013-09-17 07:34] [PACMAN] upgraded subversion (1.8.1-2 -> 1.8.3-1)
[2013-09-17 07:34] [PACMAN] upgraded udisks2 (2.1.0-3 -> 2.1.1-1)
[2013-09-17 07:34] [PACMAN] upgraded xorg-xinput (1.6.0-1 -> 1.6.1-1)
[2013-09-18 07:11] [PACMAN] Running 'pacman -Syu'
[2013-09-18 07:11] [PACMAN] synchronizing package lists
[2013-09-18 07:12] [PACMAN] starting full system upgrade
[2013-09-18 07:13] [PACMAN] upgraded firefox (23.0.1-1 -> 24.0-1)
[2013-09-18 07:13] [PACMAN] upgraded lib32-libpng (1.6.3-1 -> 1.6.5-1)
[2013-09-18 07:13] [PACMAN] upgraded ruby (2.0.0_p247-1 -> 2.0.0_p247-3)
[2013-09-18 07:13] [PACMAN] upgraded systemd (207-1 -> 207-2)
[2013-09-18 07:13] [PACMAN] upgraded systemd-sysvcompat (207-1 -> 207-2)
[2013-09-18 08:50] [PACMAN] Running 'pacman -S gptfdisk'
[2013-09-18 08:50] [PACMAN] installed gptfdisk (0.8.7-1)
[2013-09-19 09:01] [PACMAN] Running 'pacman -Syu'
[2013-09-19 09:01] [PACMAN] synchronizing package lists
[2013-09-19 09:02] [PACMAN] starting full system upgrade
[2013-09-19 09:04] [PACMAN] upgraded bluez-libs (5.8-1 -> 5.9-1)
[2013-09-19 09:04] [PACMAN] upgraded systemd (207-2 -> 207-3)
[2013-09-19 09:04] [PACMAN] upgraded bluez-utils (5.8-1 -> 5.9-1)
[2013-09-19 09:04] [PACMAN] upgraded chromium (29.0.1547.65-1 -> 29.0.1547.76-1)
[2013-09-19 09:04] [PACMAN] upgraded polkit (0.111-1 -> 0.112-1)
[2013-09-19 09:04] [PACMAN] upgraded systemd-sysvcompat (207-2 -> 207-3)
[2013-09-19 09:04] [PACMAN] upgraded xvidcore (1.3.2-1 -> 1.3.2-2)
[2013-09-19 10:25] [PACMAN] Running 'pacman -S steam'
[2013-09-19 10:26] [ALPM-SCRIPTLET] if you are running x86_64, you need the lib32 opt depends for your driver
[2013-09-19 10:26] [ALPM-SCRIPTLET] if you are having problems with the steam license, remove .steam and .local/share/Steam
[2013-09-19 10:26] [PACMAN] installed steam (1.0.0.42-1)
[2013-09-19 14:24] [PACMAN] Running 'pacman -S lib32-primus'
[2013-09-19 14:24] [PACMAN] installed lib32-primus (20130815-1)
[2013-09-20 07:45] [PACMAN] Running 'pacman -Syu'
[2013-09-20 07:45] [PACMAN] synchronizing package lists
[2013-09-20 07:45] [PACMAN] starting full system upgrade
[2013-09-20 07:47] [PACMAN] upgraded gparted (0.16.1-5 -> 0.16.2-1)
[2013-09-20 07:47] [PACMAN] upgraded systemd (207-3 -> 207-5)
[2013-09-20 07:47] [PACMAN] upgraded systemd-sysvcompat (207-3 -> 207-5)
[2013-09-20 12:01] [PACMAN] Running 'pacman -Syu'
[2013-09-20 12:01] [PACMAN] synchronizing package lists
[2013-09-20 12:02] [PACMAN] starting full system upgrade
[2013-09-22 21:04] [PACMAN] Running 'pacman -Syu'
[2013-09-22 21:04] [PACMAN] synchronizing package lists
[2013-09-22 21:04] [PACMAN] starting full system upgrade
[2013-09-22 21:06] [PACMAN] upgraded elfutils (0.155-1 -> 0.156-1)
[2013-09-22 21:06] [PACMAN] upgraded fakeroot (1.19-1 -> 1.20-1)
[2013-09-22 21:06] [PACMAN] upgraded ibus (1.5.3-2 -> 1.5.4-1)
[2013-09-22 21:06] [PACMAN] upgraded imagemagick (6.8.6.9-1 -> 6.8.6.10-1)
[2013-09-22 21:07] [PACMAN] upgraded inkscape (0.48.4-10 -> 0.48.4-11)
[2013-09-22 21:07] [PACMAN] upgraded lib32-dbus (1.6.12-1 -> 1.6.14-1)
[2013-09-22 21:07] [PACMAN] upgraded lib32-elfutils (0.155-2 -> 0.156-1)
[2013-09-22 21:07] [PACMAN] upgraded lib32-sqlite (3.8.0.1-1 -> 3.8.0.2-1)
[2013-09-22 21:07] [PACMAN] upgraded libmariadbclient (5.5.32-2 -> 5.5.33-1)
[2013-09-22 21:07] [PACMAN] upgraded m4 (1.4.16-3 -> 1.4.17-1)
[2013-09-22 21:07] [PACMAN] upgraded man-pages (3.53-1 -> 3.54-1)
[2013-09-22 21:07] [PACMAN] upgraded meld (1.8.0-1 -> 1.8.1-1)
[2013-09-22 21:07] [PACMAN] upgraded mutagen (1.21-1 -> 1.22-1)
[2013-09-22 21:07] [PACMAN] upgraded python2-mako (0.8.1-2 -> 0.9.0-1)
[2013-09-22 21:07] [PACMAN] upgraded rtkit (0.11-2 -> 0.11-3)
[2013-09-22 21:07] [PACMAN] upgraded tcl (8.6.0-6 -> 8.6.1-1)
[2013-09-22 21:07] [PACMAN] upgraded tk (8.6.0-4 -> 8.6.1-1)
[2013-09-23 06:00] [PACMAN] Running 'pacman -Syu'
[2013-09-23 06:00] [PACMAN] synchronizing package lists
[2013-09-23 06:01] [PACMAN] starting full system upgrade
[2013-09-23 06:03] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-09-23 06:03] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-2-ARCH
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> ERROR: file not found: `fsck.btrfs'
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> WARNING: No fsck helpers found. fsck will not be run on boot.
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-2-ARCH
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-23 06:03] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-09-23 06:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-23 06:03] [PACMAN] upgraded linux (3.11.1-1 -> 3.11.1-2)
[2013-09-23 06:03] [PACMAN] upgraded linux-headers (3.11.1-1 -> 3.11.1-2)
[2013-09-24 07:06] [PACMAN] Running 'pacman -Syu'
[2013-09-24 07:06] [PACMAN] synchronizing package lists
[2013-09-24 07:07] [PACMAN] starting full system upgrade
[2013-09-24 07:08] [PACMAN] upgraded jre7-openjdk-headless (7.u40_2.4.1-3 -> 7.u40_2.4.2-1)
[2013-09-24 07:08] [PACMAN] upgraded jre7-openjdk (7.u40_2.4.1-3 -> 7.u40_2.4.2-1)
[2013-09-24 07:08] [PACMAN] upgraded jdk7-openjdk (7.u40_2.4.1-3 -> 7.u40_2.4.2-1)
[2013-09-24 07:08] [PACMAN] upgraded networkmanager (0.9.8.2-1 -> 0.9.8.4-1)
[2013-09-24 07:08] [PACMAN] upgraded network-manager-applet (0.9.8.2-1 -> 0.9.8.4-1)
[2013-09-24 07:08] [PACMAN] upgraded python-setuptools (1.1.5-1 -> 1.1.6-1)
[2013-09-24 07:08] [PACMAN] upgraded python2-setuptools (1.1.5-1 -> 1.1.6-1)
[2013-09-24 07:08] [PACMAN] upgraded serf (1.3.1-1 -> 1.3.1-2)
[2013-09-24 15:41] [PACMAN] Running 'pacman -Syu'
[2013-09-24 15:41] [PACMAN] synchronizing package lists
[2013-09-24 15:41] [PACMAN] starting full system upgrade
[2013-09-24 15:42] [ALPM-SCRIPTLET] Generating locales...
[2013-09-24 15:42] [ALPM-SCRIPTLET] en_GB.UTF-8... done
[2013-09-24 15:42] [ALPM-SCRIPTLET] en_GB.ISO-8859-1... done
[2013-09-24 15:42] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-09-24 15:42] [ALPM-SCRIPTLET] en_US.ISO-8859-1... done
[2013-09-24 15:42] [ALPM-SCRIPTLET] Generation complete.
[2013-09-24 15:42] [PACMAN] upgraded glibc (2.18-4 -> 2.18-5)
[2013-09-24 15:42] [PACMAN] upgraded lib32-glibc (2.18-4 -> 2.18-5)
[2013-09-24 22:13] [PACMAN] Running 'pacman -Syu'
[2013-09-24 22:13] [PACMAN] synchronizing package lists
[2013-09-24 22:14] [PACMAN] starting full system upgrade
[2013-09-24 22:20] [PACMAN] upgraded cantarell-fonts (0.0.14-1 -> 0.0.15-1)
[2013-09-24 22:20] [PACMAN] upgraded dialog (1.2_20130902-1 -> 1.2_20130923-1)
[2013-09-24 22:20] [PACMAN] upgraded libmariadbclient (5.5.33-1 -> 5.5.33.a-1)
[2013-09-24 22:21] [PACMAN] Running '/usr/bin/pacman -U /home/ngoonee/cower/google-talkplugin/google-talkplugin-4.6.3.0-1-x86_64.pkg.tar.xz'
[2013-09-24 22:21] [PACMAN] upgraded google-talkplugin (4.5.3.0-1 -> 4.6.3.0-1)
[2013-09-25 08:30] [PACMAN] Running 'pacman -Syu'
Last edited by ngoonee (2013-09-26 03:03:29)

And after scratching my head with different kernels and rebuilding vboxdrv, I dug up an old VDI for this virtual machine and hey presto, doesn't seem to hang. Seems the btrfs errors were the symptom rather than the cause.

[SOLVED] python2-parted (debian package)

Would really appreciate it if you could bring this to Arch. I've tried
deb2targz but got confused about the proper Arch directory structure. I
don't know enough about Python to do it justice.
Download: http://packages.ubuntu.com/quantal/python-parted
Wasted a day trying to line up the deps for Arch Linux ARM to virtualize,
these Debian packages are getting in the way, to put it mildly.
Last edited by atweiden (2013-03-27 20:17:21)

I did see pyparted, but after investigating python-parted
on packages.ubuntu.com, it appeared that python-parted depends upon
pyparted, which in Ubuntu land means who knows how or where or in
what weird ways Ubuntu expects python-parted to be there. In any case,
linaro-image-tools fails for a plethora of reasons and there's no way
I can ascertain whether pyparted made a difference.
Words of advice, If you're trying to follow the MDN guide to virtualize
ARM, you have to virtualize Ubuntu first.
I'm marking this thread solved: I bought a development board.

[SOLVED] First crack at packaging

After the first instance ever on Arch where a (admittedly very new) program has to be done by source, and not on the AUR. It got me wanting to know how to package things, although nothing so complex as the program I'm after yet, I want to crawl before walking.
I decided to have a crack at a smaller program - so chose a rouge like game I hadn't yet seen in the AUR - not that it matters even if it was.
I paste the PKGBUILD I made for it below - it's not finished, but the instructions to make and build the package are there:
I took a lot of "inspiration" from the ASCIIPortal PKGBUILD because, like this game "AQuestTooFar", in the source, there is no "make install" part of the process, only a "make" and then an executable is made that you run straight from wherever the source and everything was downloaded to. Theres also no Package() part. But it works and makes a package nonetheless. However after intallation with pacman, I get an error when I try and launch it from terminal, about not being able to load one of the files in the "Data" folder, which I've checked it included and is present in my package.
Hopefully some of you would be able to offer any feedback and advice, and any thoughts on this error. I'm a complete newb to doing things from source and then packaging them - Oh package managers, how you spoil us =].
Cheers,
Ben.
# Maintainer: Ben Ward <[email protected]>
pkgname=AQuestTooFar
pkgver=1.3
pkgrel=1
pkgdesc="A rouge-like dungeon crawling game, using text."
arch=(any)
url="http://www.randomstuff.org.uk/~geoffrey/roguelikes/aquesttoofar.html"
license=()
depends=()
makedepends=('')
optdepends=('')
source=(http://www.randomstuff.org.uk/~geoffrey/roguelikes/AQuestTooFar1.3-091010.zip)
md5sums=('68545729914de7c7549b8d5ece13f061') #generate with 'makepkg -g'
build() {
cd "${srcdir}/AQuestTooFar1.3-091010"
make
install -d $pkgdir/opt/AQuestTooFar
install -D AQuestTooFar $pkgdir/opt/AQuestTooFar/
install -D readme.txt $pkgdir/usr/share/doc/AQuestTooFar/README
cp -r Build Data $pkgdir/opt/AQuestTooFar
mkdir $pkgdir/usr/bin
ln -s $pkgdir/opt/AQuestTooFar/AQuestTooFar $pkgdir/usr/bin/AQuestTooFar
chmod -x $pkgdir/opt/AQuestTooFar/*/*
Last edited by Ben9250 (2011-03-06 15:09:44)

Ben9250 wrote:Is there a certain situation then when ('any') is ok to be used or should one always try to put either i686 or x86_64 or both?
Yes, for example if your build only contains python code, then it runs on every platform which python runs on. That's when you can put arch=(any) into the PKGBUILD, because it runs everywhere.
Ben9250 wrote:
"install -Dm755 ${_realname} $pkgdir/opt/${_realname}/${_realname}"
"install -Dm644 readme.txt ${pkgdir}/usr/share/doc/${_realname}/README"
With these such lines, the -Dm755 part for example, it looks to me as though this is setting permissions, rather in a chmod kindof manner?
It's always good to set the permissions directly. Only that way you can be sure that the permissions will be right.
Ben9250 wrote:
for i in Data/*;do install -Dm644 "$i" ${pkgdir}/opt/${_realname}/"$i";done
This line is a loop, which loops around for every file in the Data folder, and copies them to the opt directory, essentially getting rid of the cp line?
Unfortunately something like install -Dm644 Data/* ${pkgdir}/opt/${_realname}/ doesn't work, so I solved it with a loop. But this line is basically doing the same as
cp -r Data/* ${pkgdir}/opt/${_realname}/
chmod 644 ${pkgdir}/opt/${_realname}/Data/*
but as I wrote before, the PKGBUILD I posted is how I would do it and I don't like to use cp in a build function, it's a matter of personal taste I guess.
Ben9250 wrote:
echo "#!/bin/sh - forgive me but I don't know about this line, echo is something to do with printing things, and theres someting going on with a shebang and sh, so something to do with bash?
"cd /opt/${_realname}"
"./${_realname}" > ${pkgdir}/usr/bin/${_realname}"
"chmod +x ${pkgdir}/usr/bin/${_realname}"
This looks to me like the answer to the softlinking?
Yes. If you use a softlink in /usr/bin which directs to /opt/${_realname}, it's kind of like the binary file is in /usr/bin. The binary expects the data directory in the same directory, but it's in /opt/${_realname}. That's why the ln -s method doesn't work. The shell script however first does cd into /opt/${_realname} and then executes the binary. That way everything's fine, because the data directory is in the same directory.
Last edited by Army (2011-03-04 13:18:30)

[SOLVED] Cannot install any package thru pacman

I cannot install any package thru pacman
when i try to install the package with pacman -S,
I started getting error when my sytem crashed and i have to forcefully switch off my laptop through power button
after that when i install anything from pacman i got following error:
[tan@ARCH ~]$ sudo pacman -S shotwell
Password:
warning: shotwell-0.9.3-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (1): shotwell-0.9.3-1
Total Download Size: 0.00 MB
Total Installed Size: 9.12 MB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [##########] 100%
(1/1) checking for file conflicts [##########] 100%
(1/1) upgrading shotwell [##########] 100%
ldconfig: File /usr/lib/libgexiv2.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgexiv2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgexiv2.so is empty, not checked.
ldconfig: File /usr/lib/libraw.so is empty, not checked.
ldconfig: File /usr/lib/libraw.so.2 is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so.2 is empty, not checked.
ldconfig: File /usr/lib/libraw.so.2.0.1 is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so is empty, not checked.
ldconfig: File /usr/lib/libraw_r.so.2.0.1 is empty, not checked.
Thanks in advance
Last edited by tan (2011-05-29 05:45:28)

Thank God, everything is fixed now:
First, I deleted all these files, then i follows the following procedure
1. For libgexiv2 file i upgraded 'xorg-server, xorg-xinit, xorg-utils, xorg-server-utils' from pacman
# pacman -S xorg-server xorg-xinit xorg-utils xorg-server-utils
2. For libraw file i upgraded 'libraw' from pacman
# pacman -S libraw
There will be some conflicting files
After deleting some conflicting files it solves the problem and restore all the 'lib' file.

[SOLVED] Pacman not updating packages

When I try to upgrade using
pacman -Syu
I get this:
error: failed to commit transaction (conflicting files)
pam: /sbin/mkhomedir_helper exists in filesystem
pam: /sbin/pam_tally exists in filesystem
pam: /sbin/pam_tally2 exists in filesystem
pam: /sbin/pam_timestamp_check exists in filesystem
pam: /sbin/unix_chkpwd exists in filesystem
pam: /sbin/unix_update exists in filesystem
pam: /usr/include/security/_pam_compat.h exists in filesystem
pam: /usr/include/security/_pam_macros.h exists in filesystem
pam: /usr/include/security/_pam_types.h exists in filesystem
pam: /usr/include/security/pam_appl.h exists in filesystem
pam: /usr/include/security/pam_client.h exists in filesystem
pam: /usr/include/security/pam_ext.h exists in filesystem
pam: /usr/include/security/pam_filter.h exists in filesystem
pam: /usr/include/security/pam_misc.h exists in filesystem
pam: /usr/include/security/pam_modules.h exists in filesystem
pam: /usr/include/security/pam_modutil.h exists in filesystem
pam: /usr/lib/libpam.so exists in filesystem
pam: /usr/lib/libpam.so.0 exists in filesystem
pam: /usr/lib/libpam.so.0.83.1 exists in filesystem
pam: /usr/lib/libpam_misc.so exists in filesystem
pam: /usr/lib/libpam_misc.so.0 exists in filesystem
pam: /usr/lib/libpam_misc.so.0.82.0 exists in filesystem
pam: /usr/lib/libpamc.so exists in filesystem
pam: /usr/lib/libpamc.so.0 exists in filesystem
pam: /usr/lib/libpamc.so.0.82.1 exists in filesystem
pam: /usr/lib/security/pam_access.so exists in filesystem
pam: /usr/lib/security/pam_cracklib.so exists in filesystem
pam: /usr/lib/security/pam_debug.so exists in filesystem
pam: /usr/lib/security/pam_deny.so exists in filesystem
pam: /usr/lib/security/pam_echo.so exists in filesystem
pam: /usr/lib/security/pam_env.so exists in filesystem
pam: /usr/lib/security/pam_exec.so exists in filesystem
pam: /usr/lib/security/pam_faildelay.so exists in filesystem
pam: /usr/lib/security/pam_filter.so exists in filesystem
pam: /usr/lib/security/pam_filter/upperLOWER exists in filesystem
pam: /usr/lib/security/pam_ftp.so exists in filesystem
pam: /usr/lib/security/pam_group.so exists in filesystem
pam: /usr/lib/security/pam_issue.so exists in filesystem
pam: /usr/lib/security/pam_keyinit.so exists in filesystem
pam: /usr/lib/security/pam_lastlog.so exists in filesystem
pam: /usr/lib/security/pam_limits.so exists in filesystem
pam: /usr/lib/security/pam_listfile.so exists in filesystem
pam: /usr/lib/security/pam_localuser.so exists in filesystem
pam: /usr/lib/security/pam_loginuid.so exists in filesystem
pam: /usr/lib/security/pam_mail.so exists in filesystem
pam: /usr/lib/security/pam_mkhomedir.so exists in filesystem
pam: /usr/lib/security/pam_motd.so exists in filesystem
pam: /usr/lib/security/pam_namespace.so exists in filesystem
pam: /usr/lib/security/pam_nologin.so exists in filesystem
pam: /usr/lib/security/pam_permit.so exists in filesystem
pam: /usr/lib/security/pam_pwhistory.so exists in filesystem
pam: /usr/lib/security/pam_rhosts.so exists in filesystem
pam: /usr/lib/security/pam_rootok.so exists in filesystem
pam: /usr/lib/security/pam_securetty.so exists in filesystem
pam: /usr/lib/security/pam_shells.so exists in filesystem
pam: /usr/lib/security/pam_stress.so exists in filesystem
pam: /usr/lib/security/pam_succeed_if.so exists in filesystem
pam: /usr/lib/security/pam_tally.so exists in filesystem
pam: /usr/lib/security/pam_tally2.so exists in filesystem
pam: /usr/lib/security/pam_time.so exists in filesystem
pam: /usr/lib/security/pam_timestamp.so exists in filesystem
pam: /usr/lib/security/pam_umask.so exists in filesystem
pam: /usr/lib/security/pam_unix.so exists in filesystem
pam: /usr/lib/security/pam_userdb.so exists in filesystem
pam: /usr/lib/security/pam_warn.so exists in filesystem
pam: /usr/lib/security/pam_wheel.so exists in filesystem
pam: /usr/lib/security/pam_xauth.so exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_ADG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_ADG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_MWG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_MWG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_SAG.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/Linux-PAM_SAG.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-files.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-glossary.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-by-app-expected.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-of-app-expected.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface-programming-notes.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-interface.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction-description.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction-synopsis.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-libpam-functions.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-libpam_misc.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-porting.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-conv-function.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-library-calls.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-resources.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-service-name.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security-user-identity.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-security.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/adg-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/draft-morgan-pam-current.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/index.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module-item.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module-other.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-by-module.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-acct.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-auth.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-chauthtok.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module-session.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-expected-of-module.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction-description.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction-synopsis.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-options.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-libs.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-sec.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming-syslog.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/mwg-see-programming.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/rfc86.0.txt exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-author.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-directory.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-example.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration-file.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-configuration.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-copyright.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-introduction.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-module-reference.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-overview.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_access.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_cracklib.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_debug.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_deny.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_echo.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_env.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_exec.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_faildelay.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_filter.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_ftp.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_group.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_issue.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_keyinit.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_lastlog.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_limits.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_listfile.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_localuser.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_loginuid.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_mail.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_mkhomedir.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_motd.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_namespace.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_nologin.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_permit.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_pwhistory.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_rhosts.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_rootok.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_securetty.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_selinux.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_shells.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_succeed_if.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_tally.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_tally2.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_time.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_timestamp.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_umask.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_unix.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_userdb.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_warn.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_wheel.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-pam_xauth.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues-other.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues-wrong.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-security-issues.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-see-also.html exists in filesystem
pam: /usr/share/doc/Linux-PAM/sag-text-conventions.html exists in filesystem
pam: /usr/share/locale/ar/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/as/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/bn_IN/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ca/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/cs/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/da/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/de/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/es/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/fi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/fr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/gu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/he/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/hi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/hu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/it/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ja/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/kk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/km/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/kn/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ko/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ml/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/mr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ms/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/nb/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/nl/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/or/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pa/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pl/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pt/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/pt_BR/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ru/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/si/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sr@latin/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/sv/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/ta/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/te/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/tr/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/uk/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/vi/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zh_CN/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zh_TW/LC_MESSAGES/Linux-PAM.mo exists in filesystem
pam: /usr/share/locale/zu/LC_MESSAGES/Linux-PAM.mo exists in filesystem
Errors occurred, no packages were upgraded.
I tried googling up something but I can't find anything.
What should I do? Thanks
EDIT: Solved. Sorry for spamming the forum like this before trying with pacman man pages.
I just did
pacman -Syu -f
and it worked.
Last edited by TheGatorade (2013-02-07 14:42:17)

That might have solved that particular problem, but you may have more. Getting that amount of 'exists in filesystem' errors in one go suggests to me that your pacman database has been corrupted. Read this if you get more problems like this: https://wiki.archlinux.org/index.php/Ho … l_database
You should avoid using the -f flag, it could result in a broken system.

[SOLVED] Unable to install packages in lxc container

tl;dr: lxc-console should be used for logging in, not lxc-attach. Also, I had to do some additional work to get the tty to work in systemd, and I plan to update the wiki soon.
I created a container using the following command:
# lxc-create -n test -t archlinux
Once created and configured, I started the container daemonized, and attached:
# lxc-start -n test -d
# lxc-attach --clear-env -n test -- su - root
However, I am unable to install any software packages because GPG isn't working properly
[root@test ~]# pacman -Syu openssh
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Packages (3): ldns-1.6.17-1 libedit-20130601_3.1-1 openssh-6.5p1-2
Total Installed Size: 6.08 MiB
:: Proceed with installation? [Y/n]
(3/3) checking keys in keyring [###########################] 100%
(3/3) checking package integrity [###########################] 100%
error: GPGME error: Inappropriate ioctl for device
error: GPGME error: Inappropriate ioctl for device
error: GPGME error: Inappropriate ioctl for device
error: libedit: missing required signature
:: File /var/cache/pacman/pkg/libedit-20130601_3.1-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: ldns: missing required signature
:: File /var/cache/pacman/pkg/ldns-1.6.17-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: openssh: missing required signature
:: File /var/cache/pacman/pkg/openssh-6.5p1-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
error: segmentation fault
Please submit a full bug report with --debug if appropriate.
The container config is as follows:
lxc.utsname=test
lxc.autodev=1
lxc.tty=1
lxc.pts=1024
lxc.rootfs=/var/lib/lxc/test/rootfs
lxc.mount=/var/lib/lxc/test/fstab
lxc.cap.drop=mknod sys_module mac_admin mac_override
lxc.kmsg=0
lxc.stopsignal=SIGRTMIN+4
#networking
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.name=eth0
lxc.network.ipv4=10.10.209.2/24
lxc.network.ipv4.gateway=10.10.209.1
lxc.network.mtu=1500
#cgroups
lxc.cgroup.devices.deny = a
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
lxc.cgroup.devices.allow = c 1:7 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 4:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:2 rwm
lxc.cgroup.devices.allow = c 136:* rwm
Has anyone else experienced this? I've searched the web for solutions to the GPG error, and most of them relate to GPG not working in a chroot because the right things don't exist in /dev. However, I was under the impression that lxc.autodev=1 would take care of this, and indeed /dev/pts, etc. all exist in the container.
Last edited by archtaku (2014-02-07 23:19:12)

x33a wrote:
Try
# pacman-key --refresh-keys
from within the container. Though, I do notice a segmentation fault, so I am not sure if it'll work.
I just did this, and the command succeeded:
gpg: refreshing 75 keys from hkp://pool.sks-keyservers.net
gpg: requesting key 5263801D from hkp server pool.sks-keyservers.net
gpg: requesting key FFF979E7 from hkp server pool.sks-keyservers.net
gpg: requesting key CDFD6BB0 from hkp server pool.sks-keyservers.net
gpg: requesting key 4C7EA887 from hkp server pool.sks-keyservers.net
... snip ...
gpg: Total number processed: 74
gpg: unchanged: 74
However, the installation still failed.
I was able to get pacman to install openssh by turning off signature verification. I then ssh'ed into the container, turned signature verification back on, and was able to install other packages just fine.
So the issue seems to be with how lxc-attach connects to the container. A temporary solution would be:
Add openssh to the list of packages installed when running lxc-create.
# lxc-create -n test -t archlinux -- -P vim,openssh
Attach to the container and run systemctl enable sshd.service, and set a root password
Detach, then ssh into container and go about your business.
However, I'd rather have the option of not using sshd on the container, and still be able to install packages, so I don't necessarily consider this problem solved yet.
Can anyone shed some light on what I might be doing wrong when I attach to the container?
Last edited by archtaku (2014-02-07 16:46:52)

No More Virtualbox Package in archlinuxfr?

On my desktop I installed Virtualbox from a *.run file I downloaded from the Virtualbox web site. On my laptop I used archlinuxfr to install it. I decided to make both my laptop and desktop pull Virtualbox from archlinuxfr, so I removed Virtualbox from my desktop with the *.run "uninstall" option and tried to install it from archlinuxfr. It cannot find the package even though I followed the Virtualbox instructions on the Archwiki.
I browsed the following directory and I didn't see Virtualbox there either:
http://repo.archlinux.fr/x86_64/
Was it removed? I don't mind installing Virtualbox from .run files if I have to but I'd rather add it to my pacman.conf so it can grab the latest version whenever I sync the packages.
I've tried to do "pacman -Ss virtualbox" and it doesn't find it.
If anyone knows the status (or if I'm just doing something wrong) I'd appreciate it.

wonder wrote:
virtualbox-ose is available in community for i686. for x86_64 you have to use virtualbox_bin from aur or use my mirror in which is virtualbox-ose for x86_64.
[vbox]
#virtualbox-ose for x86_64
Server = http://archlinux.ro/~ioni/vbox
On my laptop, which is also 64-bit, I installed virtualbox_bin from archlinuxfr without issues. It even automatically upgraded to 3.1 as soon as I synced my packages after it was released. Today, virtualbox_bin is not there despite the Arch Wiki saying it should be, so that's why I was confused if it was taken away or something.

[solved] Compilation problems - virtualbox module with custom 2.6.37..

Hi all
I have some problems compiling the vbox drivers on my custom kernel26-n130 (http://aur.archlinux.org/packages.php?ID=32042). From /var/log/vbox-install.log:
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.5.2/include -I/usr/src/linux-2.6.37-N130/arch/x86/include -Iinclude
In file included from include/linux/io.h:22:0,
from include/linux/pci.h:54,
from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:99,
from /tmp/vbox.0/linux/SUPDrv-linux.c:32:
/usr/src/linux-2.6.37-N130/arch/x86/include/asm/io.h:45:21: fatal error: xen/xen.h: No such file or directory
compilation terminated.
I built the kernel without xen support. It's the same config I used with 2.6.36.2. I found a similar problem here: https://bbs.archlinux.org/viewtopic.php … 61#p871261 . I did the same as .:B:. did and commented out the "#include <xen/xen.h>" line in the file mentioned above. Compilation runs fine and virtualbox seems to run with the drivers compiled this way. Though I don't think this is a very elegant way.
Any other suggestions?
Vlad
PS: Sry for the noise!
Had to install the xen header file...
Last edited by DonVla (2011-01-08 16:26:36)

I found the solution on http://communities.vmware.com/thread/29 … 0&tstart=0
Linux x201 2.6.37-ARCH #1 SMP PREEMPT Fri Feb 18 16:58:42 UTC 2011 i686 Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz GenuineIntel GNU/Linux
VMware Workstation 7.1.3 build-324285

[SOLVED]Nomenclature in virtualbox packages

Similar Messages

Maybe you are looking for