Symlinking of libraries in general?

Hello,
this is not based on an acutal problem, I seek guidance on that topic in general.
Let's assume program foo is built against library libbar-x.y. You upgrade (for whatever reason) library libbar-x.y to library libbar-x.z. Now the "dependency" is broken hence program foo is unable to run, until it is upgraded to a version built against library libbar-x.z.
Many people link the libraries (ln -s libbar-x.z libbar-x.y) to "hotfix" the problem (until the new version of foo is available).
I know, that there is no guarantor that this will work as it depends highly on the changes made to the library. However sometimes it "just works".
Actually I've done this myself a few times and afterwards deleted the symlink.
But...
Given that the library has influence on the acutal result of a program, it comes to my mind that there might be a chance that something goes terribly wrong while running this program.
In most of this cases, the program would just crash and that's it.
But let's assume, the program runs superficially as intendend and does not produce errors like hell, the result of the programm (a file, datastream or whatever) is some kind of corrupted.
So,,,,the corrupted data could cause serious damage to the entire system (especially if those data are used from other programs... some kind of error propagation).
Therefore my question:
What libs should never ever be symlinked (in that way)?
Do have essential parts of the system (glibc, kernel, filesystem related stuff and so on) some kind of protection against this potential cause of failure? (If this is possible at all)
Is jaunty symlinking really like playing with fire or am I just too worried?
Hope someone has wise words on that
Best regards
Last edited by pheon (2008-08-19 18:24:42)

oliwer wrote:That kind of problem often happens with proprietary apps that you can't recompile. So symlinking (or even funnier: renaming) is the only way.
It is not the only way...  build the library version you need and install it along side the current version in the Arch repos.  You will need to removing lots of conflicting files but it can be done fairly easily in most cases.

Similar Messages

  • How to symlink vendor libraries in DW? It doesn't consider that a library is in the local site folde

    Here's my question on Stackoverflow.
    http://stackoverflow.com/questions/13223428/how-to-symlink-vendor-libraries-in-dw-it-doesn t-consider-that-a-library-is-in
    And here I duplicate it. Please see on Stackoverflow because I'm afraid I'll not be able to format my question here right way using these forum tools.
    I use Win XP and Dreamweaver. I have ZF2 project. Here its "site root directory", using DW words:
    application_root/
        config/
            application.config.php
            autoload/
                global.php
                local.php
                // etc.
        data/
        module/
        vendor/
        public/
            .htaccess
            index.php
        init_autoloader.php
    I have it here C:\xampp\htdocs\mySite
    In /vendor directory there must be ZF2 library. But I have it in other directory'C:\xampp\htdocs\ZF2' and just want to put symlink to it in my /vendor directory.
    But if do so DW considers that ZF2 library is outside of my project directory. For example I want to require a class:
    require_once('\Zend\Mvc\Application.php');
    But DW says:
    This file is outside of the root folder of site "mySite", and may not be accessible when you publish the site... Would you like to copy the file there now?
    No, I don't want to copy. I don't want to make a score of the same library in every directory of my projects. But DW seems doesnt allow to do it. It makes me to copy only.
    So my question is. Is it possible to set DW that it allows to use symlinks to include libraries which are not in the "site root directory"? How to do it?
    I've read this http://www.adobe.com/devnet/dreamweaver/articles/setup_php.html , but it doesn't help. It has one sentence about the problem and that's all it has. It absolutely doesn't give the answer how to solve it.
    However, this results in two identical copies of every file. Instead it's common practice to store project files in a folder inside the document root of the testing server, which is what you'll do in this tutorial.
    And there is nothing in the tutorial about the problem.

    Non-Windows browsers do not have a concept of a "trusted" site. In Windows, IE and Chrome do not repeatedly prompt for credentials because they use the user's login credentials on the desktop. Other devices do not have this capability. Instead,
    you need to use something like ADFS to authenticate users.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • My wife and i both have an itunes library installed on to our separate pc's, we are now de-commissioning the pc's and are moving over to a single mac mini, can we install both libraries on to the mac mini and run them as separate libraries?

    my wife and i both have an itunes library installed on to our separate pc's, we are now de-commissioning the pc's and are moving over to a single mac mini, can we install both libraries on to the mac mini and run them as separate libraries?

    graham218 wrote:
    are moving over to a single mac mini, can we install both libraries on to the mac mini and run them as separate libraries?
    Generally YES.
    It's possible to hold separate iTunes library's on a single machine.
    Generate two new folders inside the Music folder of the Mini and name them differently; e.g. man and woman.
    Copy your whole library into "man" and your wifes into "woman"
    Go to sharing in the system settings of the Mini and share the Music folder in your network.
    After copying the whole library's to the Mini you may point iTunes to the new location at startup by holding the option key (alt) at the keyboard.
    iTunes will then ask you where the library is located.
    Point it to the matching library on the Mini.
    That's all.
    Lupunus
    PS ... If you both use only the Mini you have to setup a user account for each and just copy the whole library to the Music folder in particular.
    Message was edited by: lupunus

  • Merging iPhoto Libraries from two Macs

    Does anyone have a way of physically combining (not just sharing) iPhoto libraries from two macs? I'm hoping there's an easier, smarter way of doing it than just exporting all of the photos from one and importing them into the other and then just doing the reverse. Is there software that does this smarter? Can get rid of duplicates, etc.?

    Merge?
    Do you mean 'sync' libraries
    The general term means when two Libraries (A and B) are compared and files in Library A are copied to Library B, while files in Library B are also copied to Library A so that both Libraries are identical.
    This is bi-directional copying and you cannot do this with automatically with iPhoto. No Syncing software is capable of parsing the iPhoto Library in this manner. One or both of your Libraries will be damaged if you try this.
    The nearest you can get to syncing is to use iPhoto Library Manager to move files/Albums/Events plus assoicated metadata between Libraries. This process cannot be automated.
    The Export/Import route will not get your versions.
    Regards
    TD

  • Script to download source packages

    Hi there,
    I've made a Bash script "getsrc.sh" which download easily and quickly source packages from AUR or ABS (dependencies : yaourt and makepkg). The idea is just to do in one command, something we usually do in several commands (I use yaourt -G, then makepkg -o). Example :
    /home/ehmicky $ getsrc gnome-terminal
    /tmp/gnome-terminal/src/gnome-terminal-3.2.1 $ ls
    aclocal.m4 AUTHORS ChangeLog ChangeLog.pre-2-23 ChangeLog.README config.guess
    config.h.in config.sub configure configure.ac COPYING depcomp
    gnome-doc-utils.make gnome-terminal.desktop.in.in HACKING help install-sh ltmain.sh
    Makefile.am Makefile.in missing mkinstalldirs NEWS omf.make
    po README src xmldocs.make
    It's just a Bash script you need to source in your ~/.bashrc if you want to use :
    source /path/to/getsrc.sh
    I didn't package it cause I'm new to Archlinux and still uncomfortable with the packaging procedure right now.
    I'm really not sure this might be useful for anyone (it might probably be useless indeed). I guess there are already alternatives doing just the same thign, but since while googling for it, I didn't bump into them, I thought I could post this script just in case.
    Do getsrc -h for usage.
    Here is the script file :
    #!/bin/bash
    #============================================================================
    # NAME : getsrc
    # DESCRIPTION : Download source packages from ABS or AUR.
    # AUTHOR AND COPYRIGHT : ehmicky <ehmickyy at hotmail dot fr>
    # LICENSE : GPL3, see end of file
    # DEPENDENCIES : yaourt makepkg
    # USAGE : getsrc PACKAGE_NAME...
    # INSTALLATION : this file needs to be sourced (e.g. "source
    # getsrc.sh") in your ~/.bashrc
    # VARIABLES :
    # SourceDir : directory where to download the source package (default :
    # current directory)
    # VERSION : 1.1 (13/03/2012)
    # CHANGELOG : 1.1
    # * Supressed output
    # * Fix getopts bug
    # 1.0
    # * First release
    #============================================================================
    #Must define a function so it doesn't spawn a new subshell, and so we can
    #change the current directory of the caller
    getsrc()
    #Define this variable to change the download directory for source packages
    #(default is the current directory)
    local SourceDir="/tmp/MyTemp"
    #Verify dependencies
    test_command()
    while (( $# ))
    do
    if ! type "$1" &> /dev/null
    then
    echo "Error: $1 is not installed." >&2
    return 1
    fi
    shift
    done
    test_command yaourt makepkg
    #Script options : see help message for more info
    local makepkg_options="#"
    OPTIND=1
    while getopts ":hr" Opt
    do
    case "$Opt" in
    h)
    echo "getsrc: Download source packages from ABS or AUR
    Usage: $0 [OPTION]... PACKAGE_NAME...
    -r Use this option if you're root.
    -h Prints this help message.
    E-mail bug reports to: <ehmickyy at hotmail dot fr>"
    return ;;
    r)
    local makepkg_options="--asroot" ;;
    echo "Error: -$OPTARG is not a valid option." >&2
    return 1 ;;
    esac
    done
    shift $(( OPTIND - 1 ))
    local _SourceDir="${SourceDir:-.}"
    if [[ $UID -eq 0 && "$makepkg_options" != *"--asroot"* ]]
    then
    echo "Error: when root, please use the -r flag." >&2
    return 1
    fi
    #Process every argument from command line
    while (( $# ))
    do
    local PreviousDir="$PWD"
    #Go in the source package download directory
    [[ -d "$_SourceDir" ]]\
    || mkdir -p "$_SourceDir"
    if [[ ! -d "$_SourceDir" ]]
    then
    echo "Error: cannot create directory $_SourceDir" >&2
    cd "$PreviousDir"
    return 1
    fi
    cd "$_SourceDir"
    #Download the ABS of the package
    yaourt -G "$1" > /dev/null 2>&1
    #Check is the ABS has been downloaded
    if [[ ! -d "$1" ]]
    then
    echo "Error: $1 is not a valid package name" >&2
    local RelatedPackages="$( yaourt --color -Ss "$1"\
    | sed -n 'h;n;p;g;p'\
    | tac) "
    [[ "$RelatedPackages" =~ ^\ *$ ]]\
    || echo -e "Maybe you meant:\n$RelatedPackages" >&2
    cd "$PreviousDir"
    return 1
    fi
    #Download the source package from the ABS
    cd "$1"
    if ! makepkg -o "$makepkg_options" > /dev/null 2>&1
    then
    echo "Error: could not download source package" >&2
    rm -r "$_SourceDir/$1"
    cd "$PreviousDir"
    return 1
    fi
    #Goes to the root of the source package
    [[ -d "src/" ]]\
    || return
    cd "src/"
    local FinalSourceDir="$( find -mindepth 1 -maxdepth 1 -type d )"
    [[ -d "$FinalSourceDir" ]]\
    && cd "$FinalSourceDir"
    #Process next argument
    shift
    done
    # GNU GENERAL PUBLIC LICENSE
    # Version 3, 29 June 2007
    # Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
    # Everyone is permitted to copy and distribute verbatim copies
    # of this license document, but changing it is not allowed.
    # Preamble
    # The GNU General Public License is a free, copyleft license for
    # software and other kinds of works.
    # The licenses for most software and other practical works are designed
    # to take away your freedom to share and change the works. By contrast,
    # the GNU General Public License is intended to guarantee your freedom to
    # share and change all versions of a program--to make sure it remains free
    # software for all its users. We, the Free Software Foundation, use the
    # GNU General Public License for most of our software; it applies also to
    # any other work released this way by its authors. You can apply it to
    # your programs, too.
    # When we speak of free software, we are referring to freedom, not
    # price. Our General Public Licenses are designed to make sure that you
    # have the freedom to distribute copies of free software (and charge for
    # them if you wish), that you receive source code or can get it if you
    # want it, that you can change the software or use pieces of it in new
    # free programs, and that you know you can do these things.
    # To protect your rights, we need to prevent others from denying you
    # these rights or asking you to surrender the rights. Therefore, you have
    # certain responsibilities if you distribute copies of the software, or if
    # you modify it: responsibilities to respect the freedom of others.
    # For example, if you distribute copies of such a program, whether
    # gratis or for a fee, you must pass on to the recipients the same
    # freedoms that you received. You must make sure that they, too, receive
    # or can get the source code. And you must show them these terms so they
    # know their rights.
    # Developers that use the GNU GPL protect your rights with two steps:
    # (1) assert copyright on the software, and (2) offer you this License
    # giving you legal permission to copy, distribute and/or modify it.
    # For the developers' and authors' protection, the GPL clearly explains
    # that there is no warranty for this free software. For both users' and
    # authors' sake, the GPL requires that modified versions be marked as
    # changed, so that their problems will not be attributed erroneously to
    # authors of previous versions.
    # Some devices are designed to deny users access to install or run
    # modified versions of the software inside them, although the manufacturer
    # can do so. This is fundamentally incompatible with the aim of
    # protecting users' freedom to change the software. The systematic
    # pattern of such abuse occurs in the area of products for individuals to
    # use, which is precisely where it is most unacceptable. Therefore, we
    # have designed this version of the GPL to prohibit the practice for those
    # products. If such problems arise substantially in other domains, we
    # stand ready to extend this provision to those domains in future versions
    # of the GPL, as needed to protect the freedom of users.
    # Finally, every program is threatened constantly by software patents.
    # States should not allow patents to restrict development and use of
    # software on general-purpose computers, but in those that do, we wish to
    # avoid the special danger that patents applied to a free program could
    # make it effectively proprietary. To prevent this, the GPL assures that
    # patents cannot be used to render the program non-free.
    # The precise terms and conditions for copying, distribution and
    # modification follow.
    # TERMS AND CONDITIONS
    # 0. Definitions.
    # "This License" refers to version 3 of the GNU General Public License.
    # "Copyright" also means copyright-like laws that apply to other kinds of
    # works, such as semiconductor masks.
    # "The Program" refers to any copyrightable work licensed under this
    # License. Each licensee is addressed as "you". "Licensees" and
    # "recipients" may be individuals or organizations.
    # To "modify" a work means to copy from or adapt all or part of the work
    # in a fashion requiring copyright permission, other than the making of an
    # exact copy. The resulting work is called a "modified version" of the
    # earlier work or a work "based on" the earlier work.
    # A "covered work" means either the unmodified Program or a work based
    # on the Program.
    # To "propagate" a work means to do anything with it that, without
    # permission, would make you directly or secondarily liable for
    # infringement under applicable copyright law, except executing it on a
    # computer or modifying a private copy. Propagation includes copying,
    # distribution (with or without modification), making available to the
    # public, and in some countries other activities as well.
    # To "convey" a work means any kind of propagation that enables other
    # parties to make or receive copies. Mere interaction with a user through
    # a computer network, with no transfer of a copy, is not conveying.
    # An interactive user interface displays "Appropriate Legal Notices"
    # to the extent that it includes a convenient and prominently visible
    # feature that (1) displays an appropriate copyright notice, and (2)
    # tells the user that there is no warranty for the work (except to the
    # extent that warranties are provided), that licensees may convey the
    # work under this License, and how to view a copy of this License. If
    # the interface presents a list of user commands or options, such as a
    # menu, a prominent item in the list meets this criterion.
    # 1. Source Code.
    # The "source code" for a work means the preferred form of the work
    # for making modifications to it. "Object code" means any non-source
    # form of a work.
    # A "Standard Interface" means an interface that either is an official
    # standard defined by a recognized standards body, or, in the case of
    # interfaces specified for a particular programming language, one that
    # is widely used among developers working in that language.
    # The "System Libraries" of an executable work include anything, other
    # than the work as a whole, that (a) is included in the normal form of
    # packaging a Major Component, but which is not part of that Major
    # Component, and (b) serves only to enable use of the work with that
    # Major Component, or to implement a Standard Interface for which an
    # implementation is available to the public in source code form. A
    # "Major Component", in this context, means a major essential component
    # (kernel, window system, and so on) of the specific operating system
    # (if any) on which the executable work runs, or a compiler used to
    # produce the work, or an object code interpreter used to run it.
    # The "Corresponding Source" for a work in object code form means all
    # the source code needed to generate, install, and (for an executable
    # work) run the object code and to modify the work, including scripts to
    # control those activities. However, it does not include the work's
    # System Libraries, or general-purpose tools or generally available free
    # programs which are used unmodified in performing those activities but
    # which are not part of the work. For example, Corresponding Source
    # includes interface definition files associated with source files for
    # the work, and the source code for shared libraries and dynamically
    # linked subprograms that the work is specifically designed to require,
    # such as by intimate data communication or control flow between those
    # subprograms and other parts of the work.
    # The Corresponding Source need not include anything that users
    # can regenerate automatically from other parts of the Corresponding
    # Source.
    # The Corresponding Source for a work in source code form is that
    # same work.
    # 2. Basic Permissions.
    # All rights granted under this License are granted for the term of
    # copyright on the Program, and are irrevocable provided the stated
    # conditions are met. This License explicitly affirms your unlimited
    # permission to run the unmodified Program. The output from running a
    # covered work is covered by this License only if the output, given its
    # content, constitutes a covered work. This License acknowledges your
    # rights of fair use or other equivalent, as provided by copyright law.
    # You may make, run and propagate covered works that you do not
    # convey, without conditions so long as your license otherwise remains
    # in force. You may convey covered works to others for the sole purpose
    # of having them make modifications exclusively for you, or provide you
    # with facilities for running those works, provided that you comply with
    # the terms of this License in conveying all material for which you do
    # not control copyright. Those thus making or running the covered works
    # for you must do so exclusively on your behalf, under your direction
    # and control, on terms that prohibit them from making any copies of
    # your copyrighted material outside their relationship with you.
    # Conveying under any other circumstances is permitted solely under
    # the conditions stated below. Sublicensing is not allowed; section 10
    # makes it unnecessary.
    # 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
    # No covered work shall be deemed part of an effective technological
    # measure under any applicable law fulfilling obligations under article
    # 11 of the WIPO copyright treaty adopted on 20 December 1996, or
    # similar laws prohibiting or restricting circumvention of such
    # measures.
    # When you convey a covered work, you waive any legal power to forbid
    # circumvention of technological measures to the extent such circumvention
    # is effected by exercising rights under this License with respect to
    # the covered work, and you disclaim any intention to limit operation or
    # modification of the work as a means of enforcing, against the work's
    # users, your or third parties' legal rights to forbid circumvention of
    # technological measures.
    # 4. Conveying Verbatim Copies.
    # You may convey verbatim copies of the Program's source code as you
    # receive it, in any medium, provided that you conspicuously and
    # appropriately publish on each copy an appropriate copyright notice;
    # keep intact all notices stating that this License and any
    # non-permissive terms added in accord with section 7 apply to the code;
    # keep intact all notices of the absence of any warranty; and give all
    # recipients a copy of this License along with the Program.
    # You may charge any price or no price for each copy that you convey,
    # and you may offer support or warranty protection for a fee.
    # 5. Conveying Modified Source Versions.
    # You may convey a work based on the Program, or the modifications to
    # produce it from the Program, in the form of source code under the
    # terms of section 4, provided that you also meet all of these conditions:
    # a) The work must carry prominent notices stating that you modified
    # it, and giving a relevant date.
    # b) The work must carry prominent notices stating that it is
    # released under this License and any conditions added under section
    # 7. This requirement modifies the requirement in section 4 to
    # "keep intact all notices".
    # c) You must license the entire work, as a whole, under this
    # License to anyone who comes into possession of a copy. This
    # License will therefore apply, along with any applicable section 7
    # additional terms, to the whole of the work, and all its parts,
    # regardless of how they are packaged. This License gives no
    # permission to license the work in any other way, but it does not
    # invalidate such permission if you have separately received it.
    # d) If the work has interactive user interfaces, each must display
    # Appropriate Legal Notices; however, if the Program has interactive
    # interfaces that do not display Appropriate Legal Notices, your
    # work need not make them do so.
    # A compilation of a covered work with other separate and independent
    # works, which are not by their nature extensions of the covered work,
    # and which are not combined with it such as to form a larger program,
    # in or on a volume of a storage or distribution medium, is called an
    # "aggregate" if the compilation and its resulting copyright are not
    # used to limit the access or legal rights of the compilation's users
    # beyond what the individual works permit. Inclusion of a covered work
    # in an aggregate does not cause this License to apply to the other
    # parts of the aggregate.
    # 6. Conveying Non-Source Forms.
    # You may convey a covered work in object code form under the terms
    # of sections 4 and 5, provided that you also convey the
    # machine-readable Corresponding Source under the terms of this License,
    # in one of these ways:
    # a) Convey the object code in, or embodied in, a physical product
    # (including a physical distribution medium), accompanied by the
    # Corresponding Source fixed on a durable physical medium
    # customarily used for software interchange.
    # b) Convey the object code in, or embodied in, a physical product
    # (including a physical distribution medium), accompanied by a
    # written offer, valid for at least three years and valid for as
    # long as you offer spare parts or customer support for that product
    # model, to give anyone who possesses the object code either (1) a
    # copy of the Corresponding Source for all the software in the
    # product that is covered by this License, on a durable physical
    # medium customarily used for software interchange, for a price no
    # more than your reasonable cost of physically performing this
    # conveying of source, or (2) access to copy the
    # Corresponding Source from a network server at no charge.
    # c) Convey individual copies of the object code with a copy of the
    # written offer to provide the Corresponding Source. This
    # alternative is allowed only occasionally and noncommercially, and
    # only if you received the object code with such an offer, in accord
    # with subsection 6b.
    # d) Convey the object code by offering access from a designated
    # place (gratis or for a charge), and offer equivalent access to the
    # Corresponding Source in the same way through the same place at no
    # further charge. You need not require recipients to copy the
    # Corresponding Source along with the object code. If the place to
    # copy the object code is a network server, the Corresponding Source
    # may be on a different server (operated by you or a third party)
    # that supports equivalent copying facilities, provided you maintain
    # clear directions next to the object code saying where to find the
    # Corresponding Source. Regardless of what server hosts the
    # Corresponding Source, you remain obligated to ensure that it is
    # available for as long as needed to satisfy these requirements.
    # e) Convey the object code using peer-to-peer transmission, provided
    # you inform other peers where the object code and Corresponding
    # Source of the work are being offered to the general public at no
    # charge under subsection 6d.
    # A separable portion of the object code, whose source code is excluded
    # from the Corresponding Source as a System Library, need not be
    # included in conveying the object code work.
    # A "User Product" is either (1) a "consumer product", which means any
    # tangible personal property which is normally used for personal, family,
    # or household purposes, or (2) anything designed or sold for incorporation
    # into a dwelling. In determining whether a product is a consumer product,
    # doubtful cases shall be resolved in favor of coverage. For a particular
    # product received by a particular user, "normally used" refers to a
    # typical or common use of that class of product, regardless of the status
    # of the particular user or of the way in which the particular user
    # actually uses, or expects or is expected to use, the product. A product
    # is a consumer product regardless of whether the product has substantial
    # commercial, industrial or non-consumer uses, unless such uses represent
    # the only significant mode of use of the product.
    # "Installation Information" for a User Product means any methods,
    # procedures, authorization keys, or other information required to install
    # and execute modified versions of a covered work in that User Product from
    # a modified version of its Corresponding Source. The information must
    # suffice to ensure that the continued functioning of the modified object
    # code is in no case prevented or interfered with solely because
    # modification has been made.
    # If you convey an object code work under this section in, or with, or
    # specifically for use in, a User Product, and the conveying occurs as
    # part of a transaction in which the right of possession and use of the
    # User Product is transferred to the recipient in perpetuity or for a
    # fixed term (regardless of how the transaction is characterized), the
    # Corresponding Source conveyed under this section must be accompanied
    # by the Installation Information. But this requirement does not apply
    # if neither you nor any third party retains the ability to install
    # modified object code on the User Product (for example, the work has
    # been installed in ROM).
    # The requirement to provide Installation Information does not include a
    # requirement to continue to provide support service, warranty, or updates
    # for a work that has been modified or installed by the recipient, or for
    # the User Product in which it has been modified or installed. Access to a
    # network may be denied when the modification itself materially and
    # adversely affects the operation of the network or violates the rules and
    # protocols for communication across the network.
    # Corresponding Source conveyed, and Installation Information provided,
    # in accord with this section must be in a format that is publicly
    # documented (and with an implementation available to the public in
    # source code form), and must require no special password or key for
    # unpacking, reading or copying.
    # 7. Additional Terms.
    # "Additional permissions" are terms that supplement the terms of this
    # License by making exceptions from one or more of its conditions.
    # Additional permissions that are applicable to the entire Program shall
    # be treated as though they were included in this License, to the extent
    # that they are valid under applicable law. If additional permissions
    # apply only to part of the Program, that part may be used separately
    # under those permissions, but the entire Program remains governed by
    # this License without regard to the additional permissions.
    # When you convey a copy of a covered work, you may at your option
    # remove any additional permissions from that copy, or from any part of
    # it. (Additional permissions may be written to require their own
    # removal in certain cases when you modify the work.) You may place
    # additional permissions on material, added by you to a covered work,
    # for which you have or can give appropriate copyright permission.
    # Notwithstanding any other provision of this License, for material you
    # add to a covered work, you may (if authorized by the copyright holders of
    # that material) supplement the terms of this License with terms:
    # a) Disclaiming warranty or limiting liability differently from the
    # terms of sections 15 and 16 of this License; or
    # b) Requiring preservation of specified reasonable legal notices or
    # author attributions in that material or in the Appropriate Legal
    # Notices displayed by works containing it; or
    # c) Prohibiting misrepresentation of the origin of that material, or
    # requiring that modified versions of such material be marked in
    # reasonable ways as different from the original version; or
    # d) Limiting the use for publicity purposes of names of licensors or
    # authors of the material; or
    # e) Declining to grant rights under trademark law for use of some
    # trade names, trademarks, or service marks; or
    # f) Requiring indemnification of licensors and authors of that
    # material by anyone who conveys the material (or modified versions of
    # it) with contractual assumptions of liability to the recipient, for
    # any liability that these contractual assumptions directly impose on
    # those licensors and authors.
    # All other non-permissive additional terms are considered "further
    # restrictions" within the meaning of section 10. If the Program as you
    # received it, or any part of it, contains a notice stating that it is
    # governed by this License along with a term that is a further
    # restriction, you may remove that term. If a license document contains
    # a further restriction but permits relicensing or conveying under this
    # License, you may add to a covered work material governed by the terms
    # of that license document, provided that the further restriction does
    # not survive such relicensing or conveying.
    # If you add terms to a covered work in accord with this section, you
    # must place, in the relevant source files, a statement of the
    # additional terms that apply to those files, or a notice indicating
    # where to find the applicable terms.
    # Additional terms, permissive or non-permissive, may be stated in the
    # form of a separately written license, or stated as exceptions;
    # the above requirements apply either way.
    # 8. Termination.
    # You may not propagate or modify a covered work except as expressly
    # provided under this License. Any attempt otherwise to propagate or
    # modify it is void, and will automatically terminate your rights under
    # this License (including any patent licenses granted under the third
    # paragraph of section 11).
    # However, if you cease all violation of this License, then your
    # license from a particular copyright holder is reinstated (a)
    # provisionally, unless and until the copyright holder explicitly and
    # finally terminates your license, and (b) permanently, if the copyright
    # holder fails to notify you of the violation by some reasonable means
    # prior to 60 days after the cessation.
    # Moreover, your license from a particular copyright holder is
    # reinstated permanently if the copyright holder notifies you of the
    # violation by some reasonable means, this is the first time you have
    # received notice of violation of this License (for any work) from that
    # copyright holder, and you cure the violation prior to 30 days after
    # your receipt of the notice.
    # Termination of your rights under this section does not terminate the
    # licenses of parties who have received copies or rights from you under
    # this License. If your rights have been terminated and not permanently
    # reinstated, you do not qualify to receive new licenses for the same
    # material under section 10.
    # 9. Acceptance Not Required for Having Copies.
    # You are not required to accept this License in order to receive or
    # run a copy of the Program. Ancillary propagation of a covered work
    # occurring solely as a consequence of using peer-to-peer transmission
    # to receive a copy likewise does not require acceptance. However,
    # nothing other than this License grants you permission to propagate or
    # modify any covered work. These actions infringe copyright if you do
    # not accept this License. Therefore, by modifying or propagating a
    # covered work, you indicate your acceptance of this License to do so.
    # 10. Automatic Licensing of Downstream Recipients.
    # Each time you convey a covered work, the recipient automatically
    # receives a license from the original licensors, to run, modify and
    # propagate that work, subject to this License. You are not responsible
    # for enforcing compliance by third parties with this License.
    # An "entity transaction" is a transaction transferring control of an
    # organization, or substantially all assets of one, or subdividing an
    # organization, or merging organizations. If propagation of a covered
    # work results from an entity transaction, each party to that
    # transaction who receives a copy of the work also receives whatever
    # licenses to the work the party's predecessor in interest had or could
    # give under the previous paragraph, plus a right to possession of the
    # Corresponding Source of the work from the predecessor in interest, if
    # the predecessor has it or can get it with reasonable efforts.
    # You may not impose any further restrictions on the exercise of the
    # rights granted or affirmed under this License. For example, you may
    # not impose a license fee, royalty, or other charge for exercise of
    # rights granted under this License, and you may not initiate litigation
    # (including a cross-claim or counterclaim in a lawsuit) alleging that
    # any patent claim is infringed by making, using, selling, offering for
    # sale, or importing the Program or any portion of it.
    # 11. Patents.
    # A "contributor" is a copyright holder who authorizes use under this
    # License of the Program or a work on which the Program is based. The
    # work thus licensed is called the contributor's "contributor version".
    # A contributor's "essential patent claims" are all patent claims
    # owned or controlled by the contributor, whether already acquired or
    # hereafter acquired, that would be infringed by some manner, permitted
    # by this License, of making, using, or selling its contributor version,
    # but do not include claims that would be infringed only as a
    # consequence of further modification of the contributor version. For
    # purposes of this definition, "control" includes the right to grant
    # patent sublicenses in a manner consistent with the requirements of
    # this License.
    # Each contributor grants you a non-exclusive, worldwide, royalty-free
    # patent license under the contributor's essential patent claims, to
    # make, use, sell, offer for sale, import and otherwise run, modify and
    # propagate the contents of its contributor version.
    # In the following three paragraphs, a "patent license" is any express
    # agreement or commitment, however denominated, not to enforce a patent
    # (such as an express permission to practice a patent or covenant not to
    # sue for patent infringement). To "grant" such a patent license to a
    # party means to make such an agreement or commitment not to enforce a
    # patent against the party.
    # If you convey a covered work, knowingly relying on a patent license,
    # and the Corresponding Source of the work is not available for anyone
    # to copy, free of charge and under the terms of this License, through a
    # publicly available network server or other readily accessible means,
    # then you must either (1) cause the Corresponding Source to be so
    # available, or (2) arrange to deprive yourself of the benefit of the
    # patent license for this particular work, or (3) arrange, in a manner
    # consistent with the requirements of this License, to extend the patent
    # license to downstream recipients. "Knowingly relying" means you have
    # actual knowledge that, but for the patent license, your conveying the
    # covered work in a country, or your recipient's use of the covered work
    # in a country, would infringe one or more identifiable patents in that
    # country that you have reason to believe are valid.
    # If, pursuant to or in connection with a single transaction or
    # arrangement, you convey, or propagate by procuring conveyance of, a
    # covered work, and grant a patent license to some of the parties
    # receiving the covered work authorizing them to use, propagate, modify
    # or convey a specific copy of the covered work, then the patent license
    # you grant is automatically extended to all recipients of the covered
    # work and works based on it.
    # A patent license is "discriminatory" if it does not include within
    # the scope of its coverage, prohibits the exercise of, or is
    # conditioned on the non-exercise of one or more of the rights that are
    # specifically granted under this License. You may not convey a covered
    # work if you are a party to an arrangement with a third party that is
    # in the business of distributing software, under which you make payment
    # to the third party based on the extent of your activity of conveying
    # the work, and under which the third party grants, to any of the
    # parties who would receive the covered work from you, a discriminatory
    # patent license (a) in connection with copies of the covered work
    # conveyed by you (or copies made from those copies), or (b) primarily
    # for and in connection with specific products or compilations that
    # contain the covered work, unless you entered into that arrangement,
    # or that patent license was granted, prior to 28 March 2007.
    # Nothing in this License shall be construed as excluding or limiting
    # any implied license or other defenses to infringement that may
    # otherwise be available to you under applicable patent law.
    # 12. No Surrender of Others' Freedom.
    # If conditions are imposed on you (whether by court order, agreement or
    # otherwise) that contradict the conditions of this License, they do not
    # excuse you from the conditions of this License. If you cannot convey a
    # covered work so as to satisfy simultaneously your obligations under this
    # License and any other pertinent obligations, then as a consequence you may
    # not convey it at all. For example, if you agree to terms that obligate you
    # to collect a royalty for further conveying from those to whom you convey
    # the Program, the only way you could satisfy both those terms and this
    # License would be to refrain entirely from conveying the Program.
    # 13. Use with the GNU Affero General Public License.
    # Notwithstanding any other provision of this License, you have
    # permission to link or combine any covered work with a work licensed
    # under version 3 of the GNU Affero General Public License into a single
    # combined work, and to convey the resulting work. The terms of this
    # License will continue to apply to the part which is the covered work,
    # but the special requirements of the GNU Affero General Public License,
    # section 13, concerning interaction through a network will apply to the
    # combination as such.
    # 14. Revised Versions of this License.
    # The Free Software Foundation may publish revised and/or new versions of
    # the GNU General Public License from time to time. Such new versions will
    # be similar in spirit to the present version, but may differ in detail to
    # address new problems or concerns.
    # Each version is given a distinguishing version number. If the
    # Program specifies that a certain numbered version of the GNU General
    # Public License "or any later version" applies to it, you have the
    # option of following the terms and conditions either of that numbered
    # version or of any later version published by the Free Software
    # Foundation. If the Program does not specify a version number of the
    # GNU General Public License, you may choose any version ever published
    # by the Free Software Foundation.
    # If the Program specifies that a proxy can decide which future
    # versions of the GNU General Public License can be used, that proxy's
    # public statement of acceptance of a version permanently authorizes you
    # to choose that version for the Program.
    # Later license versions may give you additional or different
    # permissions. However, no additional obligations are imposed on any
    # author or copyright holder as a result of your choosing to follow a
    # later version.
    # 15. Disclaimer of Warranty.
    # THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
    # APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
    # HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
    # OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
    # THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    # PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
    # IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
    # ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
    # 16. Limitation of Liability.
    # IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
    # WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
    # THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
    # GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
    # USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
    # DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
    # PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
    # EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
    # SUCH DAMAGES.
    # 17. Interpretation of Sections 15 and 16.
    # If the disclaimer of warranty and limitation of liability provided
    # above cannot be given local legal effect according to their terms,
    # reviewing courts shall apply local law that most closely approximates
    # an absolute waiver of all civil liability in connection with the
    # Program, unless a warranty or assumption of liability accompanies a
    # copy of the Program in return for a fee.
    # END OF TERMS AND CONDITIONS
    # How to Apply These Terms to Your New Programs
    # If you develop a new program, and you want it to be of the greatest
    # possible use to the public, the best way to achieve this is to make it
    # free software which everyone can redistribute and change under these terms.
    # To do so, attach the following notices to the program. It is safest
    # to attach them to the start of each source file to most effectively
    # state the exclusion of warranty; and each file should have at least
    # the "copyright" line and a pointer to where the full notice is found.
    # <one line to give the program's name and a brief idea of what it does.>
    # Copyright (C) <year> <name of author>
    # This program is free software: you can redistribute it and/or modify
    # it under the terms of the GNU General Public License as published by
    # the Free Software Foundation, either version 3 of the License, or
    # (at your option) any later version.
    # This program is distributed in the hope that it will be useful,
    # but WITHOUT ANY WARRANTY; without even the implied warranty of
    # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    # GNU General Public License for more details.
    # You should have received a copy of the GNU General Public License
    # along with this program. If not, see <http://www.gnu.org/licenses/>.
    # Also add information on how to contact you by electronic and paper mail.
    # If the program does terminal interaction, make it output a short
    # notice like this when it starts in an interactive mode:
    # <program> Copyright (C) <year> <name of author>
    # This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    # This is free software, and you are welcome to redistribute it
    # under certain conditions; type `show c' for details.
    # The hypothetical commands `show w' and `show c' should show the appropriate
    # parts of the General Public License. Of course, your program's commands
    # might be different; for a GUI interface, you would use an "about box".
    # You should also get your employer (if you work as a programmer) or school,
    # if any, to sign a "copyright disclaimer" for the program, if necessary.
    # For more information on this, and how to apply and follow the GNU GPL, see
    # <http://www.gnu.org/licenses/>.
    # The GNU General Public License does not permit incorporating your program
    # into proprietary programs. If your program is a subroutine library, you
    # may consider it more useful to permit linking proprietary applications with
    # the library. If this is what you want to do, use the GNU Lesser General
    # Public License instead of this License. But first, please read
    # <http://www.gnu.org/philosophy/why-not-lgpl.html>.
    Last edited by ehmicky (2012-03-13 20:46:18)

    Here is the output of makepkg -s when I try to install packer:
    [tilley@take-kun packer]$ makepkg -s
    ==> Determining latest git revision...
      -> Version found: 20120509
    ==> Making package: packer 20120509-1 (Wed May  9 17:27:52 CDT 2012)
    ==> Checking runtime dependencies...
    ==> Installing missing dependencies...
    resolving dependencies...
    looking for inter-conflicts...
    Targets (2): jansson-2.3-1  jshon-20111222-1
    Total Download Size:    0.04 MiB
    Total Installed Size:   0.17 MiB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from community...
    jansson-2.3-1-x86_64      30.5 KiB   150K/s 00:00 [######################] 100%
    jshon-20111222-1-x86_64    9.8 KiB   806K/s 00:00 [######################] 100%
    (2/2) checking package integrity                   [######################] 100%
    (2/2) loading package files                        [######################] 100%
    (2/2) checking for file conflicts                  [######################] 100%
    (2/2) checking available disk space                [######################] 100%
    (1/2) installing jansson                           [######################] 100%
    (2/2) installing jshon                             [######################] 100%
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
    ==> Extracting Sources...
    ==> Entering fakeroot environment...
    ==> Starting build()...
    ==> Connecting to github GIT server....
    Cloning into 'packer'...
    error: Could not resolve host: (nil); No address associated with hostname while accessing https://github.com/bruenig/packer.git/info/refs
    fatal: HTTP request failed
    ==> ERROR: A failure occurred in build().
        Aborting...

  • Synchronization issues on OneDrive for Business

    Hi,
    Our OneDrive for Business experience is very confusing here. We are in the middle of a few synchronization problems that our users don't understand.
    Could not insert my screenshots, so please pardon me if the description is not clear. Full topic with screenshots can be found here: http://community.office365.com/en-us/f/172/p/273549/836906.aspx
    Description of the problem
    We have a lot of users using OneDrive for Business to synchronize three shared libraries stored on a on-premise installation of SharePoint 2013. The first setup has run (almost) smoothly, and all my users had a synchronized version of the files on the server
    (around 2GB of data). We are in the beginning of our deployment, so the users have not used it very intensively yet, and probably this is why problems start appearing.
    On computer 1, a file/folder reorganization has been realized within one folder (folder "TRAININGS") of one the libraries: creating new folders, moving files from one folder to another, renaming other folders and deleting old folders. Changes have
    been processed, and Computer 1 is now in sync with server: they now share the same file/folder organization under the "TRAININGS" folder. Also, on Computer 1, all folders and files show the "green tick" on their icon, showing that sync
    is completed.
    On computer 1, the OneDrive icon in the Windows task bar shows the synchronization is complete and does not show any sync issues.
    On computer 2, the folder "TRAINING" is a mess. The folder "TRAINING"'s icon has been the "blue arrows" for a while. Inside, I have a mix of "green tick", "blue arrows" and no icon status.
    Every now and then, the folder CATEGORIES turns to "green tick", then goes back to "blue arrows".
    If we drill down inside the sub-folders, I have the same bahaviour, some folders have "green tick", some other "blue arrows" and some other no icon status. I do not understand the logic.
    On Computer 2, no files or folders inside "TRAININGS" folder have never been opened by user "Fra".
    However, on SharePoint, I see that some files in the tree of the "TRAININGS" folder that have "last modified by" with name of the user in Computer 2, even though this user "Fra" never modified that precise file. Only user "Cla"
    did some modifications on the files and folders.
    For example, we are missing folder "TRAININGS\CATEGORIES\CATALOG STRUCTURE" on Computer 2.
    I do not understand what is going wrong there...
    Questions already answered:
    To save time for diagnosis:
    1. Does the issue only happen on the Computer 2? Please choose a PC and login with a problematic which have different issue to see what will happen.
    No, it happens also on a different PC, but with different status for each file.
    2. Have the files they upload met the restrictions of syncing SharePoint libraries? 
    No they have not:
    No special character in File Name
    524 files and 257 folders in the library
    Max length of full folder and file name is 157 characters.
    No invalid file types
    I have no idea if any file is open on any computer, and have no way of knowing it, with users all over the world.
    3. Have you tried to repair OneDrive for Business via right-clicking the OneDrive for Business icon then clicking repair? If not, please give it a shot and provide us with the result.
    Repair has been tested and does not help.
    4. Could you please clean the cache of OneDrive for Business to see if the issue persists?
    I have already tried deleting the Office Offline Cache on a similar problem one week ago. It is a pain in the neck since I have to do it on all my users who have problem (starts to be a lot), it involves re-downloading the whole contents of the libraries
    (2GB) and it does NOT solve the problem since it reappears one week later on a different set of files.
    Full delete of Office Offline Files temporarily solves the incident until the problem occurs again later. So doesn't help either.
    Please keep in mind I have over 30 other computers that have these libraries synced in 4 different countries, and I do not know whether they are properly synced or not. Repairing or resetting on the client computers is not an option if I am not sure I have
    completely solved the problem and I know for sure it will not happen again.
    5. How many files in these shared libraries? Generally, when suing OneDrive for Business, we don't recommend uploading/syncing a lot of files at a time.
    The folder "TRAININGS" where all changes have been made contains only 64 files and 42 folders.
    The library which contains the "TRAININGS" folder contains 524 files and 257 folders. But these files and folders have not been touched, except for the "TRAININGS" folder.
    I believe I am way under the 100 files that have moved at the same time.
    6. How long has the problem been waiting for? Have you tried letting it solve by itself?.
    Today, after 12 hours, Computer 2, 3 and 4 are still in the same state, synchronization is stuck.
    Can you please help me diagnose the issue and make sure it does not happen again?
    Thanks a lot.

    New update that might help.
    I have noticed on Computer 2 an anormal growth of the "%USERPROFILE%\AppData\Local\Microsoft\Office\15.0\OfficeFileCache" folder.
    The total synced libraries (both  with Office365 and with on-premise SharePoint) have a size of 5.5 GB.
    The OfficeFileCache folder has a size of 21.6GB and is growing by the minute.
    If I pause the sync, the folder stops growing. If I resume the sync, the folder grows.
    The changes are the following:
    File CentralTable21873.accdb has different date modified, but size remains the same.
    Files FSD-{id}.FSD (131,072 bytes) and  FSF-{id}.FSF  (114 bytes) are created. These files are created by pair, almost every second.
    Please find below extract of the contents of the OfficeFileCache on Computer 2. I stopped the sync at 12:07.
    2014-10-29 14:13:25.137808900 +0700 CentralTable21873.accdb
    2014-10-29 14:06:39.464552500 +0700 CentralTable21873.laccdb
    2014-10-29 13:49:47.221305400 +0700 FSD-{61B6B74C-BA6C-46A1-9CA0-F1031E1D4477}.FSD
    2014-10-29 13:49:43.225225000 +0700 FSD-{FF593C23-B2F6-4857-9B5D-3C278C2DF524}.FSD
    2014-10-29 13:49:43.225225000 +0700 FSF-{19C2F7EF-66A1-47D2-90C6-21104002B292}.FSF
    2014-10-29 13:46:23.720925000 +0700 FSD-{FF57C26D-73A3-41A9-B7A1-09BE0E94487F}.FSD
    2014-10-29 13:46:23.720925000 +0700 FSF-{FC35858F-8532-4D17-A94B-BC7A003D7750}.FSF
    2014-10-29 13:46:23.000910600 +0700 FSD-{B6715853-B58A-4538-9D40-C285355AA959}.FSD
    2014-10-29 13:46:23.000910600 +0700 FSF-{C367A019-6343-4998-BBDB-EEFBEFC48A53}.FSF
    2014-10-29 13:46:15.510760800 +0700 FSD-{2A81B7AF-6835-416C-9D39-759C69BCC6F9}.FSD
    2014-10-29 13:46:15.510760800 +0700 FSF-{D5DD04B0-3C47-4CB2-920A-1E61DC1C5987}.FSF
    2014-10-29 13:46:14.700744600 +0700 FSD-{B1588DF5-6985-4C3E-87C1-23259AFF8B3D}.FSD
    2014-10-29 13:36:29.610487100 +0700 FSD-{BA96AD01-7552-4893-840D-2FD804956CCC}.FSD
    2014-10-29 13:36:29.500484900 +0700 FSF-{41A2C30E-D125-471F-8885-2F50843B8218}.FSF
    2014-10-29 13:36:29.490484700 +0700 FSD-{B74D8923-28BD-4B5A-ACA2-CCD7D3A7ABA5}.FSD
    2014-10-29 12:07:28.600679500 +0700 FSD-{9FBD798B-E954-4D31-B5B8-25C1C9B9EA11}.FSD
    2014-10-29 12:07:28.600679500 +0700 FSF-{6657D798-2B7E-46C1-AA1F-F88E5C2AE906}.FSF
    2014-10-29 12:07:28.370674900 +0700 FSD-{C7F4EB47-C23F-4D35-98BD-2AE73C6F3612}.FSD
    2014-10-29 12:07:28.370674900 +0700 FSF-{0F334A91-F4B5-424B-B79B-0EA03BC46859}.FSF
    2014-10-29 12:07:28.140670300 +0700 FSD-{15A8F28E-502C-414C-B38C-1E3A9975468E}.FSD
    2014-10-29 12:07:28.140670300 +0700 FSF-{1C0AF415-373F-4C01-8C23-62E942E56E7E}.FSF
    2014-10-29 12:07:27.920665900 +0700 FSD-{58828162-A8D6-403F-AD42-889FA5F8D193}.FSD
    2014-10-29 12:07:27.920665900 +0700 FSF-{11C27630-BBD0-4797-94F0-81332B1BE598}.FSF
    2014-10-29 12:07:27.730662100 +0700 FSD-{879D25AE-37F5-47FD-9CF3-8DFBCF6C9A91}.FSD
    2014-10-29 12:07:27.730662100 +0700 FSF-{ACE9056D-ECE1-45FF-8569-437A8386001D}.FSF
    2014-10-29 12:07:27.176650700 +0700 FSD-{2E4495AE-5C09-4201-9E83-A6BDC83968EE}.FSD
    2014-10-29 12:07:27.176650700 +0700 FSF-{55EA3316-D2BE-4041-9599-E7030D5166D6}.FSF
    2014-10-29 12:07:26.986646900 +0700 FSD-{81883BA5-0FC1-4A01-91C4-B1B27930A20E}.FSD
    2014-10-29 12:07:26.986646900 +0700 FSF-{EFA9EF58-0DC0-44B1-A520-379ADAC135E5}.FSF
    2014-10-29 12:07:26.796643100 +0700 FSD-{765935BA-542C-4970-9EE3-5A6098E60D62}.FSD
    If I delete those files, and restart OneDrive, they just keep being recreated.

  • Restore iPhotoLibrary specifically from EXTERNAL Hard drive  Time Machine back up?

    My laptop Photo Library is corrupted somehow. I tried to restore from a prior in Time Machine on laptop and made the mistake of not saying to keep BOTH copies,  but after trying for 3 hours of telling me it was doing it through various windows, a little one popped open saying something about permissions and it opened an old iPhotoLibrary  from 2 years ago! ... I do have that one now and am copying it off my laptop as fast as I can to FLICKR
    cuz APPLE has become a PHOTO sinkhole... (We are talking 20,000 pics folks with scanned in family pics from 100 yrs ago!)
    I think I have a good copy on my External Hard Drive Time Machine back up from about 3 weeks ago. How do I use that to Restore from
    or should I just wait for this PHOTOS thing to come out?
    NEXT Question is there a convenient way to split it into MULTIPLE ones..eg KEEP old stable photos in one or more.
    and use another for all the new ones not editted or sorted yet? I do see there is a new Option under iPHOTO/File menu to just switch
    libraries but, of course, you cant even see that if your Library wont open!

    For TM help post in the forum for your OS - and see https://www.apple.com/support/timemachine/ and http://pondini.org/TM/FAQ.html and http://pondini.org/TM/Troubleshooting.html
    Depends on undisclosed information
    With the current OS and iPhoto you switch library using the switch library command - with any version you can switch libraries by holding the option key down while you launch iPhoto which brings up the select library window
    And generally it is not a smart idea to have multiple iPhoto libraries - it generally has no advantages and makes things much more difficult and complicated and often leads to user errors that cause major problems
    If you want to anyway the most convent way to split libraries is to use the paid version of iPhoto Library Manager - http://www.fatcatsoftware.com/iplm/ - 
    LN

  • Creation of MT940 file

    Hi,
    I am testing EBS and the user has given me a file which is in text format. But for EBS I need a file in MT940 or BAI format. SO I would to either convert the txt file to MT940, or create a new MT940 file. But I do not know how to do either of these. Can someone help me how can I do any of these things please?
    Thanks and Regards,
    Sameer Joshi

    Hi Sameer,
    The best way for creating the  file is to find an existing file in the same format and manually modifying the same to suit to our testing scenario. The file given by the user can be in BAI or MT940 format. There is no restriction as to the file being a text file. The contents in the file decides whether the file has been written in a BAI or MT940 code. The same needs to be specified by you in Tcode FF_5 while uploading the same inSAP.
    In this case, ask the user what is the format of the file, modify the same file to suit your testing scenario and use it.
    You can go through the below link as to what are the contents of a BAI file and what it stands for.
    http://www.bai.org/Libraries/Site-General-Downloads/Cash_Management_2005.sflb.ashx
    Also the below post on SCN may help you.
    http://scn.sap.com/thread/1985948
    Regards
    Vivek

  • My network drives crashed and I was able to restore one with the exact same name and login.  The second one I also created using the same name and login but it does not find the files when I click.

    I get Connection failed when I click on the photo in IPhoto. This window keeps popping up and I have to force quit IPhoto.

    iPhoto tracks referenced files using Aliases and this works just fine when the Library and the photos are on the same volume. However, Aliases won't survive being moved from one volume to another. This is why experienced users on here recommend against using Referenced Libraries in general, and in particular when the library and files are on different volumes.
    Try repair the aliases with an app like FileBuddy If that fails then I'm afraid you'll  need to do it manually for every photo in the Library, unfortunately.
    Regards
    TD

  • Ask another question about JIN and C/C++

    Using JNI on Solaris, is there any differences to build a shared library compiled from C code or C++ code?

    Huh?
    If you create a C/C++ file and use jni.h and use the method signatures from javah then either file will work. Depending on various factors, like the file extension, then you might have to specify different command line options to get the file to build.
    A C++ file could have templates would add additional problematic concerns.
    If you are talking about a C/C++ object files/shared libraries in general then there are conceptual differences (like mangled names) but no actual differences (mangled name is a legitimate C ident.)

  • Mac newcomer basic question

    As the subject says, I'm a newcomer to Mac, and a long-time hostage of Microsoft. I can't get used to working with "libraries of pictures". When I import to these libraries, what happens to the original pictures? If I edit the pictures in the library and later want to upload or email a picture, are the changes reflected in the original pictures? That is the behavior I would prefer rather than have duplicates of everything, if that is in fact what happens.
    An explanation of the purpose of libraries in general (pictures and libraries) would be really appreciated!
    Thanks.
    Nora

    Noramar:
    Welcome to the Apple Discussions. iPhoto 7 does have some very good editing tools. If you do need more sophisticated editing Photoshop Elements for Mac is, IMO, one of the best you can use. It has about 80% of the full Photoshop's capabilities as about 1/7 the cost. Another good shareware editor is Pixelmator which also users layers. These application can perform advanced editing like this.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • IPhoto Albums not seen in iTunes after iOS 6 update

    I upgraded a 3rd gen iPad and an iPhone 4 to iOS 6, then updated my Macbook Pro (2.4 ghz quad core i7, 8GB RAM) to 10.8.2 with the requisite iPhoto update.  Now, iTunes will not show my iPad even though wireless sync is enabled, unless the iPad is connected to the laptop via the docking cable.  Both iPhone and iPad error out on synch with an error 1140 if synching photos is enabled.  Under the photo tab, the button to have "selected albums, events and faces" is grayed out.  So I can only select to sync ALL photos or none.  I believe the error 1140 is stemming from my library being too large to sync to the i-device.  In any case, I can no longer choose certain albums that were enabled under iOS 5.  The area below these options in the Photos tab in iTunes also does not show any albums, where it used to do so in a grayed out fashion even if that option was not selected.  Major issue here.  Have tried all the rebuild and repair of iPhoto library.  The kicker is that both the devices I upgraded have the exact same issue, so I'm thinking this is an update/Apple problem, not an issue with my devices or config.

    Ok, all.  I think I found the problem.  In searching for reports of this issue and solutions I found someone that mentioned they had fixed a similar issue with a "free" program called "iPhoto Library Manager."  The app apparently lets you split a library into multiple smaller ones or combine multiple libraries.  Generally it just "manages" your libraries.  I figured I had nothing to lose so I checked it out.  Turns out it costs $19.99 but they do have a free demo. 
    I launched it and it immediately told me that it couldn't display my library and albums due to an issue with the AlbumData.xml file on line 22155.  I read in the documentation of the app under it's "Help" menu that likely causes were a keyword with a "null" character at the end, or a file path being referenced inside the library that had an ampersand or backslash in it.  The person on the board I'd found had had a keyword issue.
    Anyway, I opened the iPhoto library by showing package contents (right click the file to choose this) and loaded up the AlbumData.xml file in TextWrangler, since that displays line numbers.  I found that line 22155 indeed referenced an mp3 in my iTunes library that had an ampersand in it.  Deleted that line.  Then it said line 22156 had an issue so I deleted that, at which point iPhoto Library Manager instantly displayed all my albums.  I checked iTunes and it too now showed my albums and the option to sync only selected albums was no longer grayed out!
    Per the Library Manager's instructions, I saved the AlbumData.xml file I'd modified.  The app said the iPhoto only writes this file out, it doesn't read it.  However, other apps read it to get your album info, hence the issue.  So I had to go into iPhoto and fix the problem, else the next time I exited the app, it would write the file back out improperly.  I noticed in the xml file that where the song was listed it was also referencing one of my albums.  So when I launched iPhoto, I went to that album and checked the slide show settings.  Sure enough, I had set a custom playlist for that album and listed the song I had seen on line 22155 in the AlbumData.xml file.  I removed that song from the settings, and exited iPhoto.  No more issues!  I appear to be all set!
    Now, I'm not clear if I NEEDED to edit the AlbumData.xml file.  Just looking at it showed the error and then I had to fix it in iPhoto.  So you can probably do that.  However, the iPhoto Library Manager software is the only thing I know of that could show WHERE the error was.  Since the free demo works for this purpose, I'd suggest giving it a shot.  This issue is obviously caused by our individual libraries and is not an Apple issue.  Now, the album that had the problem has existed for almost 3 years and I've never had an issue like this arise before so it's anyone's guess as to why it became a problem now.  Fortunately, it's all in the past for me now, though!
    Hope this helps someone.  Good luck!

  • Oracle Linux Distribution on OSX

    The new release of Yellow Dog Linux for Apple platform is very promising... The question is: Is there any way that oracle's Linux distibution can be installed on that linux relase, so that it would be possible to run Oracle database on Mac?

    you need to install 64bit libraries, in general when you install yellow dog etc it's 32bit only, they have some prerelease stuff, as does gentooppc64 that has 64bit userland. if you install 64bit userland it works just fine.
    [oracle@spirit bin]$ file oracle
    oracle: ELF 64-bit MSB executable, PowerPC or cisco 7500, version 1 (SYSV), for
    GNU/Linux 2.4.13, dynamically linked (uses shared libs), not stripped
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Developer's Release
    With the Partitioning and Oracle Data Mining options
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Developer's Release
    With the Partitioning and Oracle Data Mining options
    woirks like a charm.
    again, find 64bit userspace. it takes some time to set it up but it works fine.

  • Post xml document

    pretty new to java. How can I post an XML document to the server? I want to do some sort of HTTP Request from a managed bean. Can't find anything on this. Isn't there some sort of HTTP Request in the base Java libraries?
    General flow of what I'm attempting:
    JSP entry of data
    managed bean controller gets data entered into entity class
    XMLencoder used to create string of xml representing entity data.
    need to send that XML to an .ASP page (yes, .ASP page because need to call pre existing com component).
    would rather not send this as a string, but rather as an XML in the body of the request. Not sure if any opf this makes sense, but trolling through the endless returns of a google search has me wasting away my last 2 days of work. Thanks for any info provided.

    Not sure if I understood you question right!! Are you trying to upload an XML document to the server? Or are you looking for AJAX to deal with XMLHttpRequest and XMLHttpResponse?

  • LabVIEW 2015 - Fast File Format and PlugIn Architecture

    In LabVIEW 2015 the new "fast file format" was introduced:
    "Improving Load Time for LabVIEW-Built Applications and Shared Libraries.
    You can build stand-alone applications (EXE) and DLLs that load faster by using the fast file format in LabVIEW. <...> When you enable the fast file format, LabVIEW does not use the Application Builder object cache"
    The question about PlugIn architecture, when lot of SubVIs called dynamically (for example, from external LLBs) from relative small core application. What I observed is - the size of the executable with this option was significantly reduced (roughly twice) and the core application itself starts faster, but PlugIns load time is the same regardless from this option (I understand why - when application fully loaded then Dynamic calls just "normal" LabVIEW code and therefore this option takes no effect). Unfortunately in code distribution build spec (as well as in packed libraries) this option is not available.
    Is it possible to get "fast" application also for PlugIn-based architecture and get LLBs or packed libraries in "fast file format"? Can someone explain, what means "LabVIEW does not use the Application Builder object cache" and how this "fast load" mechanism technically working?
    Thank you in advance,
    Andrey.

    Andrey_Dmitriev wrote:
    In LabVIEW 2015 the new "fast file format" was introduced:
    Is it possible to get "fast" application also for PlugIn-based architecture and get LLBs or packed libraries in "fast file format"? Can someone explain, what means "LabVIEW does not use the Application Builder object cache" and how this "fast load" mechanism technically working?
    Thank you in advance,
    Andrey.
    Hey Andrey!  It's good to see that you guys have been getting some good mileage out of this project.  I'll go through your questions in order ...
    1) These optimization are actually always enabled by default for packed project libraries. In fact, the load time benefits for packed libraries should generally be better than what you observe for .EXEs and .DLLs!
    2) The app builder cache is something that is enabled for EXEs and DLLs that works to cache the results of previous compiles when the source has not been updated.  It is somewhat analogous to the .obj object files generated by a C++ compiler.
    3) I won't get into too many nitty gritty details but the gist of it is... LabVIEWs various non optimized file formats are treated somewhat similarly to the way that we treat 'loose' VIs. In a DLL/EXE/LVLibp we know at build time what the contents and dependencies of a given built binary are going to be.  With this knowledge we can go ahead and construct something that is more similar to a statically linked PE or ELF file (clearly we're not using either of those) while the analogy is not 100% perfect it's the best I can do without going into a couple pages worth of description   In addition to these basic file format changes we did a large amount of work on implementing a new loader which is able to take advantage of the large amounts of precomputed file data that is now included in the format which enabled us to cut a lot of corners that were there previously.

Maybe you are looking for