Pacman Upgrade Failed: Libtool-Multilib Dependency

This morning I attempted to upgrade my Pacman repository and do a system upgrade and got:
carlos ~ $ sudo pacman -Syyu
[sudo] password for carlos:
:: Synchronizing package databases...
ec2 129.9 KiB 127M/s 00:00 [###############################################################] 100%
core 117.8 KiB 5.75M/s 00:00 [###############################################################] 100%
extra 1716.7 KiB 25.8M/s 00:00 [###############################################################] 100%
community 2.3 MiB 34.5M/s 00:00 [###############################################################] 100%
multilib 120.1 KiB 19.5M/s 00:00 [###############################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: libtool-multilib: requires libltdl=2.4.2
:: libtool-multilib: requires gcc-multilib=4.9.1
:: libtool-multilib: requires lib32-libltdl=2.4.2
Last edited by Carlwill (2014-11-03 16:05:32)

This is an Arch Linux AMI which is maintained by ?
Looks like this is something specific w/ how this runs in Amazon EC2 cloud:
carlos ~ $ sudo pacman -Ss libltdl
[sudo] password for carlos:
ec2/lib32-libltdl 2.4.3-1 [installed: 2.4.2-16]
A system independent dlopen wrapper for GNU libtool (32-bit)
ec2/libltdl 2.4.3-1 [installed: 2.4.2-14]
A system independent dlopen wrapper for GNU libtool
ec2/libx32-libltdl 2.4.3-1
A system independent dlopen wrapper for GNU libtool (64-bit, x32 ABI)
core/libltdl 2.4.2-14 [installed]
A system independent dlopen wrapper for GNU libtool
multilib/lib32-libltdl 2.4.2-14 [installed: 2.4.2-16]
A system independent dlopen wrapper for GNU libtool (32-bit)
Last edited by Carlwill (2014-11-03 16:07:23)

Similar Messages

  • Pacman upgrade fails because of unsatisfied pacman-color dependency *

    Hello, my most recent attempt to run pacman -Suy results in pacman trying to update itslef and failing:
    :: Synchronizing package databases...
    core 35.4K 500.1K/s 00:00:00
    [#####################] 100%
    extra 453.0K 2.2M/s 00:00:00
    [#####################] 100%
    community 377.2K 2.2M/s 00:00:00
    [#####################] 100%
    :: The following packages should be upgraded first :
    pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n] Y
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: pacman-color: requires pacman=3.3.3
    Any idea how to fix this?
    Last edited by .:B:. (2010-06-28 20:26:09)

    There are a couple of threads about this.
    1.Uninstall pacman-color
    2. pacman -Syu
    3. Reinstall pacman-color
    4. Put the kettle on...
    #edit too much detail...
    Last edited by jasonwryan (2010-06-28 19:48:50)

  • [SOLVED] Pacman upgrade failed because of gcc-libs

    I have the multilib version of gcc installed in my 64 bit system. Ten minutes ago I tried to upgrade with pacman -Syu and I got:
    :: I seguenti pacchetti dovrebbero essere aggiornati prima :
    pacman
    :: Vuoi annullare l'operazione corrente
    :: e aggiornare adesso questi pacchetti? [S/n]
    risoluzione delle dipendenze in corso...
    ricerca dei conflitti in corso...
    :: gcc-libs e gcc-libs-multilib vanno in conflitto. Vuoi rimuovere gcc-libs-multilib? [s/N] n
    errore: sono stati rilevati dei conflitti irrisolvibili
    errore: impossibile eseguire l'operazione richiesta (dipendenze in conflitto)
    :: gcc-libs e gcc-libs-multilib vanno in conflitto
    It is in italian, but basically it complains about a conflict between the installed gcc-libs-multilib and the needed gcc-libs. gcc-libs-multilib provides gcc-libs, so why this kind of error? I thought my mirror could be out of sync but I get the same error also using mirrors.kernel.org.
    Am I doing something wrong?
    Last edited by snack (2012-02-18 17:30:59)

    I did mean 'search the forums':
    * https://bbs.archlinux.org/viewtopic.php?pid=1045658
    * https://bbs.archlinux.org/viewtopic.php?pid=1049681
    * https://bbs.archlinux.org/viewtopic.php?pid=1057624
    * https://bbs.archlinux.org/viewtopic.php?pid=1054861
    * https://bbs.archlinux.org/viewtopic.php?pid=1057459
    * https://bbs.archlinux.org/viewtopic.php?id=134397

  • [Solved] pacman upgrade fail

    When I try to upgrade pacman I get the following:
    gordiegii@Ion-Arch ~]$ sudo pacman -S pacman
    Password:
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): pacman-4.0.3-1
    Total Installed Size: 3.54 MiB
    Proceed with installation? [Y/n]
    (1/1) checking package integrity [###################################################] 100%
    (1/1) loading package files [###################################################] 100%
    (1/1) checking for file conflicts [###################################################] 100%
    error: failed to commit transaction (conflicting files)
    pacman: /usr/bin/cleanupdelta exists in filesystem
    pacman: /usr/bin/makepkg exists in filesystem
    pacman: /usr/bin/pacman exists in filesystem
    pacman: /usr/bin/pacman-db-upgrade exists in filesystem
    pacman: /usr/bin/pacman-key exists in filesystem
    pacman: /usr/bin/pacman-optimize exists in filesystem
    pacman: /usr/bin/pacsort exists in filesystem
    pacman: /usr/bin/pactree exists in filesystem
    pacman: /usr/bin/pkgdelta exists in filesystem
    pacman: /usr/bin/rankmirrors exists in filesystem
    pacman: /usr/bin/repo-add exists in filesystem
    pacman: /usr/bin/repo-elephant exists in filesystem
    pacman: /usr/bin/repo-remove exists in filesystem
    pacman: /usr/bin/testdb exists in filesystem
    pacman: /usr/bin/testpkg exists in filesystem
    pacman: /usr/bin/vercmp exists in filesystem
    pacman: /usr/include/alpm.h exists in filesystem
    pacman: /usr/include/alpm_list.h exists in filesystem
    pacman: /usr/lib/libalpm.a exists in filesystem
    pacman: /usr/lib/libalpm.so exists in filesystem
    pacman: /usr/lib/libalpm.so.7 exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/man/man3/libalpm.3.gz exists in filesystem
    pacman: /usr/share/man/man5/PKGBUILD.5.gz exists in filesystem
    pacman: /usr/share/man/man5/makepkg.conf.5.gz exists in filesystem
    pacman: /usr/share/man/man5/pacman.conf.5.gz exists in filesystem
    pacman: /usr/share/man/man8/makepkg.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pacman-key.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pacman.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pkgdelta.8.gz exists in filesystem
    pacman: /usr/share/man/man8/repo-add.8.gz exists in filesystem
    pacman: /usr/share/man/man8/repo-remove.8.gz exists in filesystem
    pacman: /usr/share/man/man8/vercmp.8.gz exists in filesystem
    pacman: /usr/share/pacman/ChangeLog.proto exists in filesystem
    pacman: /usr/share/pacman/PKGBUILD-split.proto exists in filesystem
    pacman: /usr/share/pacman/PKGBUILD.proto exists in filesystem
    pacman: /usr/share/pacman/proto.install exists in filesystem
    pacman: /usr/share/zsh/site-functions/_pacman exists in filesystem
    Errors occurred, no packages were upgraded.
    [gordiegii@Ion-Arch ~]$
    Has anybody seen this or have any idea how to fix it?
    Should I just delete all these files?
    I was getting a gcc / gcc-libs error before but reinstalling gcc as per other forum help fixed that.
    Last edited by GordieGii (2012-04-29 15:29:26)

    @Gcool: I did a quick search and could not find anything that matched my symptoms. The only things I found that seemed to apply were the gcc / gcc-libs issue which I resolved and merging my pacman.conf.pacnew file into pacman.conf file (only two non-comments were new and they didn't seem related).
    Perhaps I can't assess the applicability of a post to my symptoms.
    @karol: I did -Syu, as I always do, but this time I got this:
    :: The following packages should be upgraded first :
    pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n]
    I tried both 'Yes' and 'no' and both failed. 'No' took much longer because it had to download a couple hundred packages (I have been trying to resolve this myself for over a week and the list keeps getting longer) before failing so I switched to just pacman.
    Pacman was in the list of packages and I couldn't figure out how to exclude it to see if the others would update. Reinstalling gcc worked.
    [gordiegii@Ion-Arch man]$ stat -c %s $(find /var/lib/pacman/local -name "pacman-4*")/files
    0
    [gordiegii@Ion-Arch man]$
    Please pardon my newbieness, I came from Ubuntu when GnomeBloat became too much for my Intel ATOM and am still learning the Arch way.

  • [SOLVED]Full upgrade fails after new install

    Hello,
    Please note before reading that I know about the recent changes with the /lib symlink to /usr/lib and the filesystem (I read the home page).
    After a fresh install, I try to upgrade the system :
    pacman -Syy && pacman -Syu : it asks for pacman update, I say yes.
    pacman -S pacman : fails because of glibc
    pacman -S pacman --ignore glibc : fails, won't upgrade because glibc it's a dependency of pacman
    pacman -Syu : say no to pacman upgrade, fails because of glibc and filesystem
    pacman -Syu --ignore glibc --ignore fliesystem : upgrade almost nothing because most of the packages (~400M) need glibc
    I can't upgrade anything at the end...
    Thanks for any help
    Last edited by John0000 (2012-07-19 14:52:17)

    If either of this steps does not work (e.g. due to dependency version issues, file conflicts in /lib), refer to this G U I D E for more detailed instructions on performing this upgrade.
    Did you read this guide?
    There is thread about it also: https://bbs.archlinux.org/viewtopic.php?id=144620
    And Allan wrote a blog entry about upgrading from core installation: http://allanmcrae.com/2012/07/updating- … e-install/
    BTW as Pres suggested go with the net-install, core installation was always kind of a fallback for me and I had to do this just once because of network troubles. It just doesn't make much sense to do core installation if there is no holdback because with first pacman -Syu you'll end up downloading the same amount of data as if you would do a clean net-install, and it's faster and you probably won't get conflicts accumulated from year or so.
    Last edited by masteryod (2012-07-19 14:38:38)

  • Upgrade fails because of gcc-gcj

    Full system upgrade fails because the following dependency cannot be satisfied.
    :: gcc-gcj: requires gcc=4.6.1
    Any solution?
    ty

    (sigh)
    I am still stuck;
    if I try to update (via pacman) either libtool/gcc-fortran I get that they cannot be updated because gcc-fortran/libtool and gcc-gcj need gcc 4.6.1
    if I try to update (via yaourt) gcc-gcj it says that libtool AND gcc-fortran require gcc 4.6.1 (even though gcc-gcj is up to date)
    My mirror says that gcc-fortran is at the version 4.6.2-1 and libtool at 2.4.2
    My mirror is up to date
    Basically I am stuck in a loop.
    A solution would be to uninstall gcc-gcj and reinstall it, but pdftk depends on it, and last time I installed it it took something like two hours to complete, I would like to avoid that
    Any suggestion?
    (edit: thanks for the help!)
    Last edited by miguelroboso (2011-11-01 20:56:51)

  • Automatic upgrade of AUR packages dependent on kernel version.

    I have an issue with upgrading AUR packages with pacaur. When I try to upgrade with one of the following commands:
    pacaur -u [package_name]
    pacaur -Su -a
    pacaur -Syu
    I keep getting the error 'no results found for dependencies)' 
    Here an example output:
    [ ~ ]$ pacaur -Syu
    :: Synchronizing package databases...
    core is up to date
    extra is up to date
    community is up to date
    :: Starting full system upgrade...
    resolving dependencies...
    looking for conflicting packages...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: spl-git: requires linux=3.17.6-1
    :: zfs-git: requires linux=3.17.6-1
    :: Starting AUR upgrade...
    :: resolving dependencies...
    :: no results found for dependencies)
    As seen in this example, the system upgrade is failed due to two kernel packages which require the previous kernel version.
    I wonder, does the AUR upgrade fails after the failed system upgrade because of new spl-git and zfs-git packages require the new kernel version? And the message ":: no results found for dependencies)" is caused by this?
    It seems there is a kind of a circular dependency in this case - kernel doesn't upgrade because of zfs requires the older kernel, and zfs doesn't upgrade because the new version of zfs requires the new kernel.
    Previously I upgraded AUR packages manually, by first removing them, then upgrading the kernel and after that installing new versions of packages.
    Is it possible to automatically upgrade kernel packages? If so can this be done with pacaur?
    Last edited by nbd (2015-01-19 23:39:49)

    Hi, so I'm not the only newbie doing such things.
    here:
    https://bbs.archlinux.org/viewtopic.php?id=181717
    ukhippo wrote:Afterwards I also suggest using “pacman -Syyu” to update (note the double “y”, this forces a refresh of all packages)
    meaning first add the repository and the key for demz-repo-core https://wiki.archlinux.org/index.php/Un … -repo-core.
    I did that today but the output was just:
    [root@machine1 ~]# pacman -Syyu
    :: Synchronizing package databases...
    core 121.6 KiB 599K/s 00:00 [########################################################] 100%
    extra 1806.6 KiB 671K/s 00:03 [########################################################] 100%
    community 2.5 MiB 672K/s 00:04 [########################################################] 100%
    multilib 121.2 KiB 932K/s 00:00 [########################################################] 100%
    demz-repo-archiso 5.5 KiB 37.9K/s 00:00 [########################################################] 100%
    demz-repo-archiso.sig 287.0 B 0.00B/s 00:00 [########################################################] 100%
    demz-repo-core 7.8 KiB 48.6K/s 00:00 [########################################################] 100%
    demz-repo-core.sig 287.0 B 0.00B/s 00:00 [########################################################] 100%
    :: Starting full system upgrade...
    resolving dependencies...
    looking for conflicting packages...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: spl-git: requires linux=3.17.6-1
    :: zfs-git: requires linux=3.17.6-1
    even though I read
    https://www.archlinux.org/packages/?sor … =&flagged=
    x86_64     Core     linux     3.18.2-2     The Linux kernel and modules     2015-01-15     2015-01-16
    and
    https://github.com/demizer/archzfs
        spl-git     Update git packages for kernel 3.18.2-2     4 days ago
        zfs-git     Update git packages for kernel 3.18.2-2     4 days ago
    I don't really know if I want to remove the package first, while running the machine from a zfs filesystem.
    If it runs automatically the chance of me making an error is a little smaller, don't really want to have a not bootable system.

  • [solved] Upgrade fails

    Commanding 'pacman -Syu' says the following packages will be upgraded,
    acpid-2.0.14-2  ati-dri-8.0.1-2  bash-4.2.024-1  blueman-1.23-3  bluez-4.99-1  boost-libs-1.49.0-1
                   dnsutils-9.9.0-1  e2fsprogs-1.42.1-1  ekiga-3.3.2-3  firefox-11.0-2  flashplugin-11.1.102.63-1
                   freetype2-2.4.9-1  gcc-4.6.3-1  gcc-libs-4.6.3-1  git-1.7.9.4-1  glproto-1.4.15-1  gmime-2.6.7-1
                   grep-2.11-2  gstreamer0.10-0.10.36-1  gstreamer0.10-bad-0.10.23-1
                   gstreamer0.10-bad-plugins-0.10.23-1  gstreamer0.10-base-0.10.36-1
                   gstreamer0.10-base-plugins-0.10.36-1  gstreamer0.10-good-0.10.31-1
                   gstreamer0.10-good-plugins-0.10.31-1  gstreamer0.10-ugly-0.10.19-1
                   gstreamer0.10-ugly-plugins-0.10.19-1  imagemagick-6.7.6.0-1  inputproto-2.2-1  intel-dri-8.0.1-2
                   kmod-6-1  krb5-1.10.1-1  lame-3.99.5-1  libcroco-0.6.4-1  libdmx-1.1.2-1  libedit-20120311_3.0-1
                   libgl-8.0.1-2  libglapi-8.0.1-2  libgphoto2-2.4.13-1  libltdl-2.4.2-4  libmpdclient-2.7-1
                   libmtp-1.1.2-1  libpciaccess-0.13-1  libpst-0.6.54-1  libsocialweb-0.25.20-0  libtiff-4.0.1-1
                   libtool-2.4.2-4  libwbclient-3.6.3-4  libx11-1.4.99.901-1  libxau-1.0.7-1  libxcb-1.8.1-1
                   libxcursor-1.1.13-1  libxdmcp-1.1.1-1  libxext-1.3.1-1  libxft-2.3.0-2  libxi-1.6.0-1
                   libxinerama-1.1.2-1  libxkbfile-1.0.8-1  libxmu-1.1.1-1  libxpm-3.5.10-1  libxrender-0.9.7-1
                   libxres-1.0.6-1  libxss-1.2.2-1  libxt-1.1.3-1  libxtst-1.2.1-1  libxv-1.0.7-1  libxvmc-1.0.7-1
                   libxxf86dga-1.1.3-1  libxxf86vm-1.1.2-1  linux-3.2.11-1  lirc-utils-1:0.9.0-12  lm_sensors-3.3.2-1
                   lua-5.1.5-1  man-pages-3.37-1  mesa-8.0.1-2  mkinitcpio-0.8.4-1  mkinitcpio-busybox-1.19.4-2
                   mpc-0.22-1  mpfr-3.1.0.p7-1  mtdev-1.1.2-1  mx-1.4.3-1  net-snmp-5.7.1-2  networkmanager-0.9.2.0-3
                   openssl-1.0.0.h-1  poppler-0.18.4-1  poppler-glib-0.18.4-1  powertop-1.13-3  ppl-0.12-1  qt-4.8.0-6
                   sane-1.0.22-7  smbclient-3.6.3-4  subversion-1.7.4-1  sudo-1.8.4.p4-1  svga-dri-8.0.1-2
                   tzdata-2012b-1  udev-181-4  usbutils-005-1  util-linux-2.21-5  xcb-proto-1.7-2
                   xf86-input-acecad-1.5.0-3  xf86-input-aiptek-1.4.1-3  xf86-input-evdev-2.7.0-1
                   xf86-input-joystick-1.6.1-1  xf86-input-keyboard-1.6.1-2  xf86-input-mouse-1.7.2-1
                   xf86-input-synaptics-1.5.99.901-2  xf86-input-vmmouse-12.8.0-1  xf86-input-void-1.4.0-3
                   xf86-video-apm-1.2.3-5  xf86-video-ark-0.7.4-1  xf86-video-ast-0.93.9-2  xf86-video-ati-6.14.3-2
                   xf86-video-chips-1.2.4-4  xf86-video-cirrus-1.3.2-8  xf86-video-dummy-0.3.5-1
                   xf86-video-fbdev-0.4.2-6  xf86-video-glint-1.2.7-1  xf86-video-i128-1.3.4-5
                   xf86-video-i740-1.3.2-8  xf86-video-intel-2.18.0-1  xf86-video-neomagic-1.2.5-6
                   xf86-video-nv-2.1.18-5  xf86-video-rendition-4.2.4-6  xf86-video-s3-0.6.3-7
                   xf86-video-s3virge-1.10.4-7  xf86-video-siliconmotion-1.7.5-4  xf86-video-sisusb-0.9.4-6
                   xf86-video-trident-1.3.4-6  xf86-video-tseng-1.2.4-6  xf86-video-v4l-0.2.0-10
                   xf86-video-vesa-2.3.0-8  xf86-video-vmware-12.0.1-1  xf86-video-voodoo-1.2.4-6
                   xf86-video-xgixp-1.8.0-5  xmms2-0.8DrO_o-5  xorg-fonts-encodings-1.0.4-3  xorg-server-1.12.0-1
                   xorg-server-common-1.12.0-1  xorg-xinput-1.5.99.1-1  xproto-7.0.23-1
    The upgrade fails, however, with an error 'damaged package' or something (I have it in finnish). The file '/var/log/pacman.log'
    does not give any info. I have no idea how to proceed.
    EDIT: Thanks guys. I did
    pacman -Sc
    which fixed the problem. I should've known that from the start, but then again this was the first time I've had problems with upgrades.
    Last edited by habbe (2012-03-17 10:44:03)

    Could you please run it as:
    LC_ALL=C pacman -Syu
    That will cause the message to be created in English.  Then, go ahead and post the full error message.  Thanks.

  • On Windows 7 PC, got the "upgrade iTunes" notice, said sure, but the upgrade failed, now I can't access iTunes "invalid permissions"

    On Windows 7 PC, got the "upgrade iTunes" notice this morning, said sure, but the upgrade failed, now I can't access iTunes "invalid permissions"
    I wasn't paying attention so I don't know the precise error I got on the upgrade failure.
    All other iTunes upgrades have been fine...no brainers.  Done several on this W7 PC.
    If I re-download and install a fresh iTunes I assume I will lose my library...true?  Can I find and save off my library so I don't have to "discover" all my music which is scattered all over the PC and a 1T attached USB drive.
    Or is there some way to get the iTunes upgrade to successfully restart and install correctly?
    Help!

    Hello there, Konami84.
    The following Knowledge Base article provides some recomendations for troubleshooting:
    iTunes 11.1.4 for Windows: Unable to install or open
    http://support.apple.com/kb/TS5376
    Check for .dll files
    Go to C:\Program Files (x86)\iTunes and C:\Program Files\iTunes and look for .dll files.
    If you find QTMovie.DLL, or any other .dll files, move them to the desktop.
    Reboot your computer.
    Note: Depending on your operating system, you may only have one of the listed paths.
    Uninstall and reinstall iTunes
    Uninstall iTunes and all of its related components.
    Reboot your computer. If you can't uninstall a piece of Apple software, try using the Microsoft Program Install and Uninstall Utility.
    Re-download and reinstall iTunes 11.1.4.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • Pacman -Syu fails on perl5

    This machine doesnt have much on it, but maybe I hosed when getting vmware installed.  My other machine has a very similar config, and is still working.  Anyway, both running xine and "pacman -Syu" fail, here is the ouput:
    login as: root
    Sent username "root"
    [email protected]'s password:
    Last login: Sun Mar 21 11:11:37 2004
    [root@cpq24 root]# xine
    xine: error while loading shared libraries: libssl.so.0.9.6: cannot open shared object file: No such file or directory
    [root@cpq24 root]# pacman -Syu
    :: Synchronizing package databases...
    current                  [################] 100%|     38K|   63.2K/s| 00:00:00
    extra                    [################] 100%|    127K|   40.1K/s| 00:00:03
    unstable                 [################] 100%|      1K|    5.4K/s| 00:00:00
    Targets: centericq-4.9.10-2 curl-7.11.0-2 gtk-perl-0.7009-4
             reiserfsprogs-3.6.14-1 wget-1.9.1-2 xchat-2.0.7-2 xine-lib-1rc3b-2
    Proceed with upgrade? [Y/n]
    checking package integrity... done.
    loading package data... done.
    checking for file conflicts...
    error: the following file conflicts were found:
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Atoms.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/CListModel.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/ColorSelectButton.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/ImlibImage.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/ImlibImage/Install/Files.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/ImlibImage/Install/GdkImlibTypes.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/ImlibImage/Install/pkg.typemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Install/Files.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Install/GdkPixbufDefs.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Install/GdkPixbufTypemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Install/PerlGdkPixbufInt.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Install/pkg.typemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Gdk/Pixbuf/Types.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/Files.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/GdkTypes.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/GtkDefs.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/GtkTypemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/GtkTypes.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/MiscTypes.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/PerlGtkExt.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/PerlGtkInt.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gendefs.pl: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gendoc.pl: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/genext.pl: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gpdoc2pod: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-0.99.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-0.99.typemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.0.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.1.1.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.1.3.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.1.4.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.1.6.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.1.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.2.defs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/gtk-1.2.typemap: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Install/ppport.h: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Keysyms.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/LWP.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/LWP/http.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/LogHandler.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/Types.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/TypesLazy.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/io.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/Gtk/lazy.pm: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/ImlibImage/.packlist: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/ImlibImage/ImlibImage.bs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/ImlibImage/ImlibImage.so: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/Pixbuf/.packlist: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/Pixbuf/Pixbuf.bs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/Pixbuf/Pixbuf.so: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gdk/autosplit.ix: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gtk.bs: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/Gtk.so: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/autosplit.ix: exists in filesystem
      /usr/lib/perl5/site_perl/current/i686-linux/auto/Gtk/base/.packlist: exists in filesystem
    [root@cpq24 root]#

      Sarah;
        Reviewing ...man pacman...I find not reference to ...-Suf... but i do find one reference to the term.... --f... which is one of the commands which is not recommended(not at all).
        The use of ...-Suf... combo is not listed.
        I have no idea how to interpret the use of pacman when such upgrade problems are encountered.  And I would not be able to apply the pacman system in any new problem I may encounter without examples that keep me out of more trouble should more " forcing functions" or other work arounds be necessary.
      I more than appreciate the post describing how to proceed when the upgrade reports that the file already exists because it provided a procedure which successfully corrected the difficulty and eliminated the "fear of failure" associated with the "force" command(not recommended at all).
      Please appreciate that I did read the man pacman many times but am not confident in using elements of that manual in "combination", especially when warned not to use "force".
        Please appreciate the fact that pacman is advertised as an asset for arch and, when not encountering the difficulty of this post, it does upgrade efficiently.
       I have re-installed arch about a dozen times due to my ignorance of pitfalls in the upgrade process some of which haven't shown themselves in the posts I have read.
       But the first ...-Syu...gave the result covered by this post{16 packages rejected).
       To one familiar with linux and arch, all things appear in the manual but not in a form recognized from the viewpoint of a newbie especially if interpretation is required.
       I am told to research the forums, which I did.  When I found a posted solution and thanked those involved, I am told that the solution is somewhere in the manual......
       One's point of view is paramount, expert or novice.....

  • Solaris 10 live upgrade failed

    I am trying to upgrade Solaris 10 U6 10/08 to U7 05/09 with live upgrade. But it failed with following errors:
    # luupgrade -u -n solaris_u7 -s /mnt/cdrom
    No entry for BE <solaris_u7> in GRUB menu
    Copying failsafe kernel from media.
    Uncompressing miniroot
    Creating miniroot device
    miniroot filesystem is <ufs>
    Mounting miniroot at </mnt/cdrom/Solaris_10/Tools/Boot>
    Validating the contents of the media </mnt/cdrom>.
    The media is a standard Solaris media.
    The media contains an operating system upgrade image.
    The media contains <Solaris> version <10>.
    Constructing upgrade profile to use.
    Locating the operating system upgrade program.
    Checking for existence of previously scheduled Live Upgrade requests.
    Creating upgrade profile for BE <solaris_u7>.
    Checking for GRUB menu on ABE <solaris_u7>.
    Saving GRUB menu on ABE <solaris_u7>.
    Checking for x86 boot partition on ABE.
    Determining packages to install or upgrade for BE <solaris_u7>.
    Performing the operating system upgrade of the BE <solaris_u7>.
    CAUTION: Interrupting this process may leave the boot environment unstable
    or unbootable.
    ERROR: Installation of the packages from this media of the media failed; pfinstall returned these diagnostics:
    Processing profile
    Loading local environment and services
    Generating upgrade actions
    WARNING: SUNWwgetu depends on SUNWgcmn, which is not selected
    WARNING: SUNWi15cs depends on SUNWi15rf, which is not selected
    WARNING: SUNWi1cs depends on SUNWxwplt, which is not selected
    WARNING: SUNWbind depends on SUNWbindr, which is not selected
    WARNING: SUNWale depends on SUNWxwrtl, which is not selected
    WARNING: SUNWale depends on SUNWxwplt, which is not selected
    ERROR: No upgradeable file systems found at specified mount point.
    Restoring GRUB menu on ABE <solaris_u7>.
    ABE boot partition backing deleted.
    PBE GRUB has no capability information.
    PBE GRUB has no versioning information.
    ABE GRUB is newer than PBE GRUB. Updating GRUB.
    GRUB update was successfull.
    Did it really fail due to file dependencies? Will it fix the problem by installing the missing packages on the running BE?

    You need to run this script from the CD or Install server: Solaris_10/Tools/Installers/liveupgrade20 when upgrading to 10 u7. I had run into this. Run the script and choose all the defaults. Liveupgrade will then not give the errors you have seen.
    Linuxbass :-)

  • Mail upgrade failed: osx lion

    I have a Macbook pro 17 intel dual core.
    I upgraded from Snow Leopard to Lion and I have encountered the following problem.
    Mail begins the importing of messages and once the import is complete it moves to the migrating data step
    "MAIL UPGRADE FAILED"
    An error occured during the upgrade. Click continue to launch the Mail Import Assistant, which will help you create a new library and import your existing messages"
    When I click "Continue", the following message appears
    Your Mail index has been damaged. To repair it, quit Mail.
    Mail will repair the index the next time you open Mail. Your mailboxes and messages will be preserved.
    But of course, Mail doesn't repair itself the next time it is opened....this just continues to happen.
    Any help? I have read threads that suggesting deleting Mail preferences can help. Interestingly, I can't find mail preferences in the library folder

    I fixed my issue, though it took hours of trial and error.
    First, check Console (Applications/Utilities/Console) and click on All Messages in the left sidebar.   I had a message about permission denied to copy a file during the upgrade.  I manually moved that file to the desktop.  After that the message migration finished, and Mail launched.  Hurray I thought!  But on reboot, Mail would not launch.  It just hung.  This time there weren't any helpful messages in Console to be found.
    I read over these threads for the tips:
    https://discussions.apple.com/thread/3189986?start=0&tstart=0
    https://discussions.apple.com/message/15666804#15666804
    As best I can remember (it's been a long night), this was my process:
    (Force) Quit Mail
    Navigate to userI/Library/Mail folder
    Move the entire Mail folder elsewhere, like your desktop
    Launch Mail.  At this point it should be be prompting you for info.
    If you don't have anything on your machine only, just put in your info and download everything from your server from scratch.  You're done!   If however you have my problem with 164,000 messages stored locally, read on…
    Quit Mail
    Back in user/Library there's a new Mail folder.
    One by one, move the items from the old Mail folder to the new one and launch Mail.  Make sure to move the user/library/mail/v2/maildata/accounts.plist first so it stops prompting you for account info.  Make sure to quit Mail between every file move.  If you don't see a v2 folder, or a v2-temp folder, it means the migration hasn't happened yet.  Just keep moving things over until it does, cause the migration changes the directory structure of the Mail folder.
    At the point you move your old archived messages over, the next Launch Apple will import and migrate all the messages.  This can take anywhere from 2 minutes to 45 depending on how many messages it needs to cull through.  
    I ended up moving everything but the RSS folder items back, and Mail is once again stable.
    At some point I also booted into Lion Recovery partition (hold Command + R at boot) and ran Disk Utility to repair permissions.  However I don't believe that actually helped.
    Good Luck!

  • [Solved] pacman-color failed to install missing dependencies

    Just upgraded my AUR packages and I get this error:
    :: Starting AUR upgrade...
    :: perl-class-load-xs 0.04-2 -> 0.06-1
    AUR Targets (1): perl-class-load-xs
    Proceed with installation? [Y/n] y
    :: Edit perl-class-load-xs PKGBUILD? [Y/n] n
    :: Building perl-class-load-xs package...
    ==> Making package: perl-class-load-xs 0.06-1 (Sat Nov 3 09:14:38 PDT 2012)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Installing missing dependencies...
    error: target not found: perl-test-without-module
    ==> ERROR: 'pacman-color' failed to install missing dependencies.
    :: perl-class-load-xs cleaned
    Any help appreciated.
    Last edited by lagagnon (2012-11-04 03:07:33)

    perl-test-without-module is in the AUR.
    edit: build the package yourself in makepkg or use an aur helper.
    Last edited by SS4 (2012-11-03 16:41:55)

  • [solved]pacman upgrade issue using axel

    i changed the default downloading tool to axel, but ervery time before i run pacman -Syu, i need to rm /var/lib/pacman/sync/*.db. If I don't do this, axel can't overwrite the database automatically, which can result in the fail of pacman upgrade.
    what should i do so needn't i rm the db files before upgrade.
    Last edited by zsrkmyn (2013-09-18 14:16:58)

    karol wrote:
    Post the XferCommand you're using. Is it https://wiki.archlinux.org/index.php/Im … plications
    XferCommand = /usr/bin/axel -n 2 -v -a -o %o %u
    Seems to work for me.
    oh, it works, thx a lot!
    but why i could't succeed when i using "XferCommand = /usr/bin/axel -n 2 -v -a -o `basename %u` %u" before?

  • Rsyslogd refuses to start after pacman upgrade

    Hello,
    After last pacman upgrade rsyslog refused to start.
    This also caused boot problems - systemd would go into infinite loop trying to start rsyslog and failing miserably.
    I've disabled rsyslog.service from chroot environment and booted from disk - it helped.
    I've also noticed that latest package version (  rsyslog-7.2.6-4-x86_64)  does not ship with /etc/rsyslog.conf, so
    upgrading to it removes this file which is why rsyslog refused to start
    Downgrading, copying file elsewhere and moving it back to /etc/rsyslog.conf is a simple workaround.
    Previous package versions had this file inside ( I checked rsyslog-7.2.4-1 and rsyslog-7.2.6.1, both for x64)
    Hope that helps someone.
    Should I perform anny additional steps to resolve this issue ( e.g open a bug ? )
    Thanks for any help!

    The package was changed with 7.2.6-4 to copy rsyslog-example.conf to /usr/share/doc/rsyslog/ rather than as configuration to /etc.
    Probably because the rsyslog devs apparently changed it in a way that causes the program to instantly go into an infinite loop.
    Since it won't start at all without /etc/rsyslog.conf present, I just copied the default Debian ships 7.2.6 with (available in here). Works properly so far.
    Last edited by misc (2013-03-14 23:16:19)

Maybe you are looking for

  • Is there any way to prevent non-root users from rebooting the system?

    This question seems to be addressed many times on the web, but the problem is that none of the wannabe-howtos work on my system. In particular, this doesn't work and this doesn't work either, because (1) I need to keep policykit installed for udisks

  • User exit after FI post

    Hi, I'm trying to link a user process to a FI document posting but I haven't found a user exit or badi to do it, I try to link it via a sustitution or validation but those are executed during the fi document process and the user process must be execu

  • InfoProviders versus Queries Data Source for BO SAP Integration

    Hi All, I would like to know if there is any discussion or suggestion on commonly used choice of data source for BO with SAP Integration. I do know there is a best practices suggestion from Ingo on Webi and the choice is to use queries so that we cou

  • Copying the VC templates for other Developers

    Everyone, We have configured a VC developer to access templates from a track and would like to make the templates available for other VC developers too. So, I would like to know what happens when we export the SC's from the templates, Is there any ot

  • I purchased Photoshop cs6 and lightroom for windows but now I have a Mac

    Does anyone have a 1 -800 number for Adobe? I purchased the teacher/student edition of Adobe photoshop cs6 extended and adobe Lightroom 4 but I didn't really even get to learn how to use them because my computer was old and crashed. Since then I purc