[solved] virtualbox-ose-additions-modules and pacman -Syu

I get the following error from my VM (Oracle VM VirtualBox) under Windows when doing a pacman -Syu:
:: Starting full system upgrade...
:: Replace kernel26-firmware with core/linux-firmware? [Y/n]
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-ose-additions-modules: requires kernel26<2.6.34
pacman -Qs kernel26 =
local/kernel26 2.6.33.4-1 (base)
The Linux Kernel and modules
local/kernel26-firmware 2.6.33.4-1 (base)
The included firmware files of the Linux Kernel
local/kernel26-headers 2.6.33.4-1
Header files and scripts for building modules for kernel26
Please help.d
Last edited by tpfkanep (2010-06-22 09:00:51)

find a more up to date mirror. virtualbox-ose-additions-modules 3.2.4-3 has the proper dependencies

Similar Messages

  • [Solved]virtualbox-ose-additions needs virtualbox-ose-additions

    Hello everybody. I noticed that mayor updates were released some time ago but I couldn't update because of my exams. Anyway, now I'm trying to update (pacman -Syu) and I recieve the following error:
    :: virtualbox-ose-additions-modules: needs kernel26<2.6.28
    So, that package is out of date, I don't mind if I have to remove it and install virtualbox after updating again, so I tried to remove it and what I get is this;
    :: virtualbox-ose-additions: needs virtualbox-ose-additions-modules
    Even if I do a ~$ pacman -R -f virtualbox-ose-additions-modules get the same error.
    How can I remove it and update?
    Thanks
    Last edited by endless_dark (2009-02-16 21:02:41)

    pointone wrote:
    Remove virtualbox-ose-additions first?
    Or...
    pacman -Syu --ignore virtualbox-ose-additions*
    Omg it was as easy as that. -1 for me
    Thank you very much!

  • I can't load VirtualBox OSE additions modules

    Hi to everyone:
    I have VirtualBox (OSE) installed on my system:
    [glsadmin@researchlinux ~]$ pacman -Qs virtualbox
    local/virtualbox-modules 3.0.12-1
    Kernel modules for VirtualBox
    local/virtualbox-ose 3.0.12-1
    Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
    local/virtualbox-ose-additions 3.0.12-1
    Guest Additions for VirtualBox (Open Source Edition)
    local/virtualbox-ose-additions-modules 3.0.12-1
    Kernel modules for VirtualBox Guest Additions
    I can't load the modules of OSE additions:
    [root@researchlinux ~]# modprobe vboxadd
    FATAL: Error inserting vboxadd (/lib/modules/2.6.31-ARCH/misc/vboxadd.ko): No such device
    [root@researchlinux ~]# modprobe vboxvfs
    FATAL: Error inserting vboxvfs (/lib/modules/2.6.31-ARCH/misc/vboxvfs.ko): No such device
    [root@researchlinux ~]#
    But they're on the system:
    [root@researchlinux ~]# pacman -Ql virtualbox-ose-additions-modules
    virtualbox-ose-additions-modules /lib/
    virtualbox-ose-additions-modules /lib/modules/
    virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/
    virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/
    virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/vboxadd.ko
    virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/vboxvfs.ko
    [root@researchlinux ~]#
    Someone else with the same problem ... anyone knows how to fix it?

    wonder wrote:
    do you have virtualbox-additions installed?
    pacman -Qs virtualbox
    No, I don't.
    [glsadmin@researchlinux ~]$ pacman -Qs virtualbox
    local/virtualbox-modules 3.1.0-1
    Kernel modules for VirtualBox
    local/virtualbox-ose 3.1.0-1
    Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
    local/virtualbox-ose-additions 3.1.0-1
    Guest Additions for VirtualBox (Open Source Edition)
    local/virtualbox-ose-additions-modules 3.1.0-1
    Kernel modules for VirtualBox Guest Additions
    I remember that program's package (virtualbox-additions) is under PUEL license, but I can't use the package in one enterprise environment; by that reason I thought that the virtualbox-ose-additions package could be useful for my main target: change between the guest system and the host system without to use the CTRL key for to release the mouse pointer.

  • Cant Find to install VirtualBox-Ose-Additions

    Hi All
    I have installed virtualbox-ose and virtualbox-ose-additions from packages and configured virtualbox etc ... and it runs just fine.  But when i go to configure guest additions, i cant find where its been installed ...
    I thought it was supposed to be here /usr/share/virtualbox/additions/VBoxGuestAdditions.iso  But its not ...
    Any suggestions please ?
    Many Thanks

    whitetimer wrote:Done that but the iso is still not in /usr/share/virtualbox .......
    it doesn't need to be there. just try to load the iso from vbox and you'll see that is working
    pacman -Ql virtualbox-additions
    Last edited by wonder (2010-12-03 22:43:34)

  • [Solved] Localtime is messed up, and pacman doesn't work anymore

    Hi everyone,
    I'm quite new to Arch Linux but I've succeded so far in installing the base system, setting up my wifi card (wasn't easy) and installing xfce4. When I first installed everything seemed to work fine (wifi, dropbox, pacman, etc.) but I noticed that my time doesn't reflect the current local time. I've selected America/Montreal in rc.conf and through "Orage Globaltime" in xfce4 but both return the UTC instead of the localtime. Also, when I try to get the UTC from Orage, it returns my localtime instead (Montreal)...
    So there's definitely something wrong there. I've then had a look at the forums/wiki and found that a network synchronisation should be used to correct the issue (such as ntp) but now pacman can't connect to anything. It returns something like this when I try to install/update/search:
    $ sudo pacman -Syu
    Password:
    :: Synchronizing package databases...
    error: failed retrieving file 'core.db' from mirror.us.leaseweb.net : Connection time-out
    ^C (keeps on getting time-outs if I don't interrupt)
    Some info on my system:
    General info: as stated above, internet over wifi (wlan0) works, pacman times-out and the local time is off.
    $ uname -a
    Linux giga-arch 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 i686 GNU/Linux ---(today's Sept 3, ~10:35am)---
    $ cat rc.conf
    DAEMONS=(syslog-ng network crond)
    TIMEZONE="America/Montreal"
    $ ip addr
    3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 84:c9:b2:00:41:e3 brd ff:ff:ff:ff:ff:ff
        inet 192.168.0.179/24 brd 192.168.0.255 scope global wlan0
        inet6 fe80::86c9:b2ff:fe00:41e3/64 scope link
            valid_lft forever preferred_lft forever
    $ cat /var/log/pacman.log
    [2012-09-02 16:31] starting full system upgrade
    [2012-09-02 18:16] Running 'pacman -S ntop'
    [2012-09-02 18:17] installed rrdtool (1.4.7-2)
    [2012-09-02 18:17] installed geoip-database (20120808-1)
    [2012-09-02 18:17] installed geoip (1.4.8-2)
    [2012-09-02 18:17] ==> Before running the daemon script for the first time, you need to run
    [2012-09-02 18:17]     ntop as the root user to set an administrator password.
    [2012-09-02 18:17] ==> If you attempt to run ntop as a daemon without setting a password, a
    [2012-09-02 18:17]     FATAL ERROR message is generated and ntop stops.
    [2012-09-02 18:17] installed ntop (5.0-2)               <------------ At this point pacman worked, but the time wasn't right (it was ~22:17)
    [2012-09-03 04:43] Running 'pacman -Syu ntp'      <------------ From this point on pacman would time-out continually
    [2012-09-03 04:43] synchronizing package lists
    [2012-09-03 04:45] Running 'pacman -S ntp'
    [2012-09-03 04:51] Running 'pacman -Syu'
    [2012-09-03 04:51] synchronizing package lists
    [2012-09-03 04:51] Running 'pacman -Syu'
    [2012-09-03 04:51] synchronizing package lists
    [2012-09-03 06:00] Running 'pacman -Syu'
    [2012-09-03 06:00] synchronizing package lists
    [2012-09-03 06:30] Running 'pacman -Syu'
    [2012-09-03 06:30] synchronizing package lists
    $ ls -lhA /etc | grep localtime
    lrwxrwxrwx 1 root root   36 Sep  3 04:34 localtime -> /usr/share/zoneinfo/America/Montreal
    My first guess was that the localtime offset was preventing me from accessing pacman's repositories, but since it worked yesterday (when the time was already corrupt) it seems otherwize. Now I'm quite lost, especially since no one seems to report every pacman repository being down... could anyone please help me solve this problem?
    Thanks!
    Last edited by miek (2012-09-03 20:28:44)

    WonderWoofy wrote:I think you may find relevant information here.  I ahve seem many of these threads in the forums lately.  Are you dual booting w/ another operating system... in particular, one that uses localtime for the hardware clock (and there is only one that does this).
    Thanks I'll look at that entry. Still I'd like to point out that this page clearly says that the timezone is to be set in rc.conf, which is a bit confusing. I must've followed this guide to get to my current configuration. I am dual booting with multiple other systems (xubuntu, win7, puppy, crunchbang) so from what I've read win7 might be the problem, but I haven't started it since i installed arch and my time has been off from the start.
    Should I simply use NTP now that pacman is working again?
    Thanks
    Last edited by miek (2012-09-03 17:41:56)

  • [solved] Virtualbox guest additions stopped working

    Hi,
    I got some trouble after an upgrade of kernel yesterday. Virtualbox guest additions doesn't work any longer, and I have tried both downgrading virtualbox-guest-additions and the new linux that got pushed yesterday, but it's still not working.
    Is there some know issue related to this?
    Do anyone have information on how to trace errors with Virtualbox, or any guide on how to fix this.
    I have also tried a reinstall of the modules without success.
    Thanks.
    Last edited by grrrm (2014-10-08 15:45:45)

    Suddenly it worked

  • [SOLVED] gnome-settings-daemon problem after pacman -Syu

    Today after updating my hp laptop with pacman -Syu, I noticed that I lost a few of my multimedia key shortcuts. When I tried to fix this with System->Preferences->Keyboard Shortcuts, I get this error:
    Unable to start the settings manager 'gnome-settings-daemon'.
    Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
    The keyboard shortcut menu comes up as normal, and seems to work like it should for everything but the multimedia keys. I get the same error when clicking on the Appearance & Keyboard menus.
    I remember pacman asking me if I wanted to replace gail with gtk2. Could that have anything to do with it?
    Any ideas?
    Thanks!!!!
    Last edited by bebeababa (2008-10-23 17:08:13)

    JGC wrote:Log out from gnome and login again, this should fix your issues.
    Tried it, no change.
    I forgot to mention that running "gnome-settings-daemon" in a termal produces:
    ** ERROR **: You can only run one xsettings manager at a time; exiting
    aborting...
    Aborted
    ... and that the pstree shows a "gnome-settings-" entry.
    Any other ideas?

  • [SOLVED] cannot find root device after pacman -Syu

    Today I had a problem after pacman -Syu. Of course, my problem stemmed from not paying attention to the following (from https://bbs.archlinux.org/viewtopic.php?id=57205):
    <b>Read pacman's output while upgrading.</b>
    I could no longer boot. I received a message "cannot find root device" or something similar indicating a device with the appropriate UUID had not been found and I was being dropped into a recovery shell, then, when I typed exit, an emergency shell, followed shortly by a freeze.
    After some investigation it appeared my initramfs was broken/non-existent/something after the install. I booted into a live CD and found that updating pacman again, and mkinitcpio -p linux both displayed the following error: "Failed to create temporary working directory in /tmp". Long story short: mktemp was segfaulting. This should be extremely easy to check if you're having a similar problem. I replaced it with the version on the live CD and ran the pacman update again. Success. If you do this, you may need to make sure your live cd architecture and installed kernel architecture are the same.
    I'm not sure of the etiquette here, so I'm posting this in case someone else has the same problem I did; and benefits from a similar solution. I have checked the etiquette post and I don't think it's clear whether it's kosher to post things that don't actually require a solution. However, if I have misinterpreted the rules/etiquette and/or this type of post is considered extraneous please remove it.

    You have to use lvm first.  As all those vg*, lv*, and pv* commands are actually links to the lvm command, you should have to do something like "lvm vgscan" instead of just "vgscan".
    Edit: oh and at that point in the boot process, you are actually in the initramfs still (ash to be specific).
    Edit2: I was having issues with a USB keyboard and a new machine (actually just a new bios), and found out that because of windows 8's requriement for a fast POST, the default is to turn off the scanning for usb devices.  Though this was for UEFI, and I am not sure if the same would apply for a bios booting machine...
    Last edited by WonderWoofy (2013-03-26 23:10:40)

  • [Solved] VirtualBox-ose no run GUI

    I has installed VirtualBox, but don't work. In bash appears this:
    VirtualBox: Error -10 in SUPR3HardenedMain!
    VirtualBox: Effective UID is not root (euid=1000 egid=1000 uid=1000 gid=1000)
    VirtualBox: Tip! It may help to reinstall VirtualBox.
    With qt yes work, but with sdl says that I executed with root!! ¿Is normal?
    Nom            : virtualbox-ose
    Versió         : 3.2.8-2
    URL            : http://virtualbox.org
    Llicències     : GPL  custom
    Grups          : Cap
    Proporciona    : virtualbox=3.2.8
    Depen de       : libxml2  libxcursor  libidl2  libxinerama  sdl  libxmu  curl
                     kernel26-headers  gcc  make
    Dep opcionals  : libxt: for shared clipboard
                     libvncserver: for VNC support in VBoxHeadless
                     pulseaudio: for pulseAudio support
                     python: for python support
                     qt: for VirtualBox GUI
    Requerit per   : Cap
    Conflictes amb : virtualbox-modules<=3.1.6-2
    Substitueix    : virtualbox-modules
    Mida instal.   : 39548,00 K
    Empaquetador   : Ionut Biru <[email protected]>
    Arquitectura   : x86_64
    Data de constr.: dl 23 ago 2010 13:43:39 CEST
    Data instal.   : dv 27 ago 2010 16:53:41 CEST
    Raó instal.    : Instal·lat explícitament
    Script instal. : Sí
    Descripció     : Powerful x86 virtualization for enterprise as well as home use
                     (Open Source Edition)
    Last edited by igallart (2010-08-27 15:03:13)

    I think that is necesary qt to GUI. Before working with sdl, with the version of AUR, but now it seems that no. Thanks

  • Pacman and pacman -Syu

    I was 100% sure I already posted this message but it is not here, I think I have done something terribly wrong with the submit button.  :oops:
    As everybody (should) know in case you do a pacman -Syu and a newer version of pacman is out, you should stop it, then upgrade only pacman and after do again pacman -Syu.
    Could it be possible to have pacman that checks  if there is a newer version available and in that case do only pacman upgrade?
    This should save (especially newcomers) many problem.
    I know that newcomers start to take advantage from a such feature only from 0.6 but somewere we have to start.
    I think pacman is this case can have two operating mode:
    1) pacman -Syu
    2) pacman see a newer pacman version
    3) pacman warn the user  to do a pacman -S pacman  before the pacman -Syu and stop. Eventually with the option to force the -Syu anyway. If somebody wants to mess up his/her system they should be free to do it 
    Another way can be
    1) pacman -Syu
    2) pacman see a newer pacman version
    3) pacman automatically update itself and after stop  warning the user that pacman has been update and now he/she need to start pacman -Syu again

    I think this is a good idea. You should submit a feature request to the bugtracker.
    Bobonov wrote:
    I think pacman is this case can have two operating mode:
    1) pacman -Syu
    2) pacman see a newer pacman version
    3) pacman warn the user  to do a pacman -S pacman  before the pacman -Syu and stop. Eventually with the option to force the -Syu anyway. If somebody wants to mess up his/her system they should be free to do it 
    Another way can be
    1) pacman -Syu
    2) pacman see a newer pacman version
    3) pacman automatically update itself and after stop  warning the user that pacman has been update and now he/she need to start pacman -Syu again
    A third way would be:
    1) pacman -Syu
    2) See never pacman version
    3) "Do you want to update pacman y/n"
    4) If yes upgrade pacman
    5) Continue with normal update.

  • [SOLVED] Cannot startup properly after recent pacman -Syu

    I'm having a bit of trouble starting up my system after a recent upgrade (6-6-13).  I ran into some issues beforehand with the error
    filesystem: /bin exists in filesystem
    filesystem: /sbin exists in filesystem
    but resolved that by following the steps highlighted on the recent news section on the home page.  I use rEFInd and I get the normal boot menu and everything seems normal, but I get this message when loading up the OS
    [FAILED] Failed to mount /boot.
    See 'systemctl status boot.mount' for details.
    [DEPEND] Dependency failed for Local File Systems.
    So I run the command mentioned above and get this
    boot.mount - /boot
    Loaded: loaded (/etc/fstab)
    Active: failed (Result: exit-code) since Fri 2013-06-07 19:30:39 CDT; 2 min 0s ago
    Where: /boot
    What: /dev/disk/by-uuid/F1E8-4195
    Process: 168 ExecMount=/bin/mount /dev/disk/by-uuid/F1E8-4195 /boot -t vfat -o rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro (code=exited, status=32)
    Jun 07 19:30:39 ux31a systemd[1]: boot.mount mount process exited, code=exited status=32
    Jun 07 19:30:39 ux31a systemd[1]: Failed to mount /boot
    Jun 07 19:30:39 ux31a systemd[1]: Unit boot.mount entered failed state.
    I'm still new and getting used to this but it looks like my filesystem is not loading properly (obviously) and I do not know how to resolve my issue.  Any help?  You guys were great helping with my install issues.
    Last edited by somedood (2013-06-09 13:17:38)

    I'm happy to say that I was able to successfully boot thanks to some research into the Arch boot sequence and adding MODULES="vfat" to my /etc/mkinitcpio.conf!  I ran
    mkinitcpio -p linux
    to create the initramfs-linux.img and initramfs-linux-fallback.img in my /boot directory.  I tried to reboot, however it did not work because I did not have what rEFInd needed to boot successfully.  I then ran
    cp /boot/vmlinuz-linux /boot/EFI/arch/vmlinuz-arch.efi
    cp /boot/initramfs-linux.img /boot/EFI/arch/initramfs-arch.img
    cp /boot/initramfs-linux-fallback.img /boot/EFI/arch/initramfs-arch-fallback.img
    to place the images and the kernel in my rEFInd directory so that rEFInd could find those things in order to boot successfully.  So basically I had the right files in the wrong place!
    Anyways, thanks for all the help everyone!  The Arch community is great when noobs like me get stuck! 
    One more small question from me... I'm supposed to mark the topic as SOLVED when it is in fact solved.  How do I change the title of this topic?  Thanks

  • [SOLVED] Virtualbox-host-dkms module not compatible with Linux 3.17rc

    Using the linux-mainline package from aur, was unable to get dkms to compile the vboxdrv module. Mainline is currently at around 3.17rc3, didn't work at rc1 either.
    Apparently a patch has already been made, it is available at:
    https://forums.virtualbox.org/viewtopic … 50#p296650
    Loaded the abs system and applied the patch from the forum:
    https://forums.virtualbox.org/download/ … p?id=13399
    Patch works like a charm. I have compiled the package, if anyone else would like to save some cpu cycles and time, I wouldn't mind uploading it if there is somewhere it can be posted.

    Ideka wrote:I suspect this may be a regression but I couldn't find any information or reports of other people having the same problem anywhere.
    You must not have searched very long then, because you've missed not one, but two threads:
    https://bbs.archlinux.org/viewtopic.php?id=134374
    https://bbs.archlinux.org/viewtopic.php?id=134580

  • [SOLVED]Problems when installing - DHCP and Pacman

    Hello Arch Linux Forums,
    I'm kind of new here and I'm switching from Debian, so excuse me if this question is noobish.
    I've been trying to install Arch Linux for three days now, and the installation always screws up at either Select Source, Select Packages or Install Packages. It changes every time I try.
    On Select Source - Failed to run dhcpcd. Check /dev/tty7 for errors.
    On Select Packages - Pacman preparation failed! Check /dev/tty7 for errors.
    On Install Packages - Installs a few packages, and then after a few packages download I get "No address record" on everything else.
    Can someone point me in the right direction on what to do?
    Thanks in advance.
    EDIT: I tried to install today, worked fine. Did nothing different. Thanks anyway guys!
    Last edited by SeekAndDestroy (2012-05-09 16:27:30)

    Mr.Elendig wrote:Check /dev/tty7 for errors and post them here in code tags.
    I tried the installation again and it failed at install packages. Here's the only line in /dev/tty7 that I think is related to it.
    [DEBUG_UI] Package installation failed, check below for errors
    I don't have it on right now, but it said something to that effect. It says that on the installer as well, although the only other thing it gives is the No address record error mentioned in the OP.

  • VirtualBox OSE (missing vboxwebsrv)

    Dunno if its a bug or i'm looking in the wrong package, but, im trying to install phpVirtualBox (http://code.google.com/p/phpvirtualbox/) but the needed binary 'vboxwebsrv' isn't installed on my system.
    These are the VirtualBox related packages that i have installed:
    virtualbox-additions-3.2.8-1/
    virtualbox-ose-3.2.8-3/
    virtualbox-ose-additions-3.2.8-3/
    virtualbox-ose-additions-modules-3.2.8-3/
    TIA.
    spkz
    Last edited by spunkiie (2010-09-29 17:54:49)

    Is it included with OSE? I know there are some features missing in that version. I've got it, but I run PUEL.
    Last edited by urist (2010-09-29 18:14:41)

  • [SOLVED] Perl updated to 5.20: Should I pacman -Syu?

    Hi all,
    In the arch home page one reads:
    Perl updated to 5.20
    2014-06-04
    Perl 5.20, as any other new perl version, requires all modules that are not purely perl code to be rebuilt. We did that for all packages in our repos.
    The last couple major updates printed an error message when trying to load modules built against the wrong version, 5.20 seems to cause segfaults. Please make sure to rebuild all custom installed CPAN modules and binaries that link to libperl.so.
    Refer to my post on arch-dev-public for a script that helps to find those packages.
    I executed the script and I got this:
    $cd /tmp/find-broken-perl-package.22jFUOeh
    $ls *
    pacman.txt perl-dists.txt perl-modules.txt raw.txt
    $cat *
    libproxy
    Net::Libproxy
    /usr/lib/perl5/vendor_perl/auto/Net/Libproxy/Libproxy.so
    I read the announcement, but I'm not sure what to do next.. What should I rebuild and how?
    Or am I good to just go on and pacman -Syu? I'm a bit extra cautious as I had problems in
    the past when I wasn't.
    Thanks in advance
    EDIT: perl-dists.txt was empty, so the output of cat * is for pacman.txt, perl-modules.txt, and raw.txt, respectively.
    Last edited by geo909 (2014-06-17 01:43:51)

    tomk wrote:I guess it might be helpful to add that in the news item, the word "custom" essentially means "installed from source(s) other than the official Arch repos", since the devs have taken care of any official packages. So you just need to determine the source of that libproxy package, and then rebuild or not as required.
    Thanks.. I think I'll be safe to upgrade. Just one more question: while trying to figure out who is using the libproxy package
    I did the following:
    jorge@flamingo:~$ sudo pacman -Qo /usr/lib/perl5/vendor_perl/auto/Net/Libproxy/Libproxy.so
    /usr/lib/perl5/vendor_perl/auto/Net/Libproxy/Libproxy.so is owned by libproxy 0.4.11-2
    Ok, so sure enough Libproxy.so is used by libproxy. Then I'm not sure how to find out
    who is using libproxy as a dependency. I did
    pacman -Si libproxy
    but that didn't give any information about that. So I had to pretend that I'm
    uninstalling things to get to what is using libproxy:
    jorge@flamingo:~$ sudo pacman -R libproxy
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: glib-networking: requires libproxy
    jorge@flamingo:~$ sudo pacman -R glib-networking
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: libsoup: requires glib-networking
    jorge@flamingo:~$ sudo pacman -R libsoup
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: abiword-plugins: requires libsoup
    :: darktable: requires libsoup
    :: gst-plugins-good: requires libsoup
    :: gstreamer0.10-good-plugins: requires libsoup-gnome
    :: gvfs: requires libsoup
    :: webkitgtk2: requires libsoup
    Is there a more proper way of obtaining those packages?

Maybe you are looking for