SaveSyu - a pacman wrapper to savely upgrade your system

This wrapper will evaluate the "upgrade level" of every packages that could be upgraded.
The "upgrade level" is defined as follows:
Assuming version number looks like x.y.z-p. And we consider that:
x is a major version number, y is a normal version number, and z is a minor version number, and p is a packaging version number.
If a version number looks like 1-2, we consider 1 is the major.
And if it looks like 1.2-3, we consider 1 is the major, and 2 is the normal.
And if it looks like 1.2.3.4-5, we consider 1 is the major, 2.3 is the normal, and 4 is the minor.
And,
level 19: packaging change
             x1=x2 y1=y2 z1=z2, only p1 != p2
level 25: minor upgrade
             x1=x2 y1=y2, z1 != z2, but 1 week old
level 29: minor upgrade
             x1=x2 y1=y2, z1 != z2
level 35: normal upgrade
             x1=x2, y1!=y2, but 2 weeks old
level 39: normal upgrade
             x1=x2, y1!=y2
level 45: major upgrade
             x1!=x2, but 4 weeks old
level 49: major upgrade, x1!=x2
While invoking, you should specify a threshold that you think is save to upgrade, and the wrapper - saveSyu, will invoke pacman to upgrade only those packages under the threshold.
Here comes...
#!/bin/bash
# save upgrade
# we can create some upgrade policy, for example:
# the package is one month old, or
# the package is a "packaging upgrade" (which means "the same
# software version", different "packaging version"), or
# the package is a "minor upgrade", x.y.z -> x.y.?
# the package is not in core (nor extra)
# function(s)
# assume version number looks like x.y.z-p
# others include:
# x.y.y.z-p
# x.y-p
# y-p
# level 19: packaging change, x1=x2 y1=y2 z1=z2, only p1 != p2
# level 25: minor upgrade, x1=x2 y1=y2, z1 != z2, but 1 week old
# level 29: minor upgrade, x1=x2 y1=y2, z1 != z2
# level 35: normal upgrade, x1=x2, y1!=y2, but 2 weeks old
# level 39: normal upgrade, x1=x2, y1!=y2
# level 45: major upgrade, x1!=x2, but 4 weeks old
# level 49: major upgrade, x1!=x2
# other criteria including:
# which repository (not in core, in community, etc.)
# minor upgrade, but packaging number is not 1 (which means it has been (bug) fixed)
evaluate_upgrade_level() {
# init
ONE_WEEK=$((1 * 7 * 24 * 60 * 60))
TWO_WEEKS=$((2 * $ONE_WEEK))
FOUR_WEEKS=$((4 * $ONE_WEEK))
old_ver=$1
new_ver=$2
repo=$3
date=$(date -d "$4" +%s)
now=$(date +%s)
# parse
old_tmp=${old_ver%-*}
old_pkg=${old_ver#$old_tmp-}
old_major=${old_tmp%%.*}
old_minor=${old_tmp##*.}
old_normal=${old_tmp#$old_major.}
old_normal=${old_normal%.$old_minor}
echo old_ver=$old_ver major=$old_major normal=$old_normal minor=$old_minor pkg=$old_pkg
new_tmp=${new_ver%-*}
new_pkg=${new_ver#$new_tmp-}
new_major=${new_tmp%%.*}
new_minor=${new_tmp##*.}
new_normal=${new_tmp#$new_major.}
new_normal=${new_normal%.$new_minor}
echo new_ver=$new_ver major=$new_major normal=$new_normal minor=$new_minor pkg=$new_pkg
age=$(($now - $date))
echo date=$date now=$now age=$age
if [ "$old_major" = "$new_major" -a "$old_normal" = "$new_normal" -a "$old_minor" = "$new_minor" ] ; then
level=19
elif [ "$old_major" = "$new_major" -a "$old_normal" = "$new_normal" ] ; then
if [ $age -gt $ONE_WEEK ] ; then
level=25
else
level=29
fi
elif [ "$old_major" = "$new_major" ] ; then
if [ $age -gt $TWO_WEEKS ] ; then
level=35
else
level=39
fi
else
if [ $age -gt $FOUR_WEEKS ] ; then
level=45
else
level=49
fi
fi
echo level=$level
return $level
# init
SUDO=sudo
PACMAN=pacman
ARCH=i686
TMP_FILE=/tmp/$(basename $0).tmp
if [ 0 -eq $# ] ; then
echo usage: $0 threshold
exit 4
fi
threshold=$1
# get upgrade list
"$SUDO" "$PACMAN" -Syu --print-uris | grep ".pkg.tar.gz$" >"$TMP_FILE"
targets=""
# analyse "upgrade level"
while read uri ; do
pkg=$(basename "$uri")
pkg=${pkg%-$ARCH.pkg.tar.gz}
pkg=${pkg%.pkg.tar.gz}
name=${pkg%-*-*}
new_ver=${pkg#$name-}
old_ver=$("$PACMAN" -Qi "$name" | grep "^Version")
old_ver=$(echo $old_ver)
old_ver=${old_ver#Version : }
repo=$(basename $(dirname $(dirname $(dirname "$uri"))))
date=$("$PACMAN" -Si "$name" | grep "^Build Date")
date=$(echo $date)
date=${date#Build Date : }
echo name=$name repo=$repo old_ver=$old_ver new_ver=$new_ver date=$date
evaluate_upgrade_level "$old_ver" "$new_ver" "$repo" "$date"
level=$?
if [ $level -lt $threshold ] ; then
echo save
targets="$targets $name"
fi
echo
done <"$TMP_FILE"
# do it!
echo $targets
"$SUDO" "$PACMAN" -S $targets
Last edited by bsdson.tw (2008-11-07 10:14:36)

nice idea! but i like to live life on the edge
will be useful for server stuff. will give it a spin when i set up my server with arch

Similar Messages

  • How do I get my purchased apps/ringtones/songs after you upgraded your system?

    I upgraded the system on my phone from the 4 to the 4S on iTunes and I have lost all my purchased songs/apps/ringtones. How do I recover these? There is nothing on my iTunes that has backed up my info. Also I went to see if I could get them by redownloading them but I had to pay for them so I didn't do that because I don't want to have to pay twice.

    uiux wrote:
    I can't seem to find any of the apps that I downloaded + purchased before updating my Apple ID & payment method.
    Does this mean you Created a NEW Apple ID..?
    It should be Noted that anything Downloaded with a Particular Apple ID is tied to that Apple ID and Cannot be Merged or Transferred to a Different Apple ID
    Apple ID FAQs  >  http://support.apple.com/kb/HT5622

  • [SOLVED] Pacman broken by partial upgrade. How to fix and update?

    Pacman partially upgraded a system during pacman -Syu and, as a result, pacman itself is broken.
    So I'm facing two issues, the one which caused the upgrade to fail and the fact that pacman no longer works.
    I answered yes to all of the below:
    :: Starting full system upgrade...
    :: Replace kactivities with extra/kactivities4? [Y/n] y
    :: Replace lzo2 with core/lzo? [Y/n] y
    :: Replace phonon-gstreamer with extra/phonon-qt4-gstreamer? [Y/n] y
    :: Replace phonon-gstreamer with extra/phonon-qt5-gstreamer? [Y/n] y
    :: Replace polkit-qt with extra/polkit-qt4? [Y/n] y
    :: Replace shared-color-profiles with extra/colord? [Y/n] y
    :: Replace twisted with extra/python2-twisted? [Y/n] y
    All seemed well until all the downloads and verifications were finished.
    (646/646) checking for file conflicts [######################] 100%
    (1/6) removing lzo2 [######################] 100%
    (2/6) removing shared-color-profiles [######################] 100%
    (3/6) removing polkit-qt [######################] 100%
    (4/6) removing phonon-gstreamer [######################] 100%
    (5/6) removing kactivities [######################] 100%
    (6/6) removing twisted [######################] 100%
    ( 1/646) upgrading linux-api-headers [######################] 100%
    ( 2/646) upgrading tzdata [######################] 100%
    ( 3/646) upgrading filesystem [######################] 100%
    warning: /etc/group installed as /etc/group.pacnew
    warning: /etc/passwd installed as /etc/passwd.pacnew
    warning: /etc/gshadow installed as /etc/gshadow.pacnew
    warning: /etc/shadow installed as /etc/shadow.pacnew
    error: extract: not overwriting dir with file /var/run
    error: problem occurred while upgrading filesystem
    error: could not commit transaction
    error: failed to commit transaction (transaction aborted)
    Errors occurred, no packages were upgraded.
    The upgrade failed because of "extract: not overwriting dir with file /var/run".
    The last line is not entirely true because I don't think the removals were rolled back.
    Since pacman depends on lzo2 I now get the error below whenever I try to launch it.
    pacman: error while loading shared libraries: liblzo2.so.2: cannot open shared object file: No such file or directory
    So I need to figure out a way to fix pacman and correct the issue that is causing the update to fail without causing even bigger problems.
    I'd appreciate any suggestions!
    Thanks.
    Last edited by authentec (2014-08-26 07:02:00)

    headkase wrote:
    Your filesystem package was upgraded, you had 646 packages to upgrade.  You haven't run "pacman -Syu" in years.  Your system will be near impossible to upgrade.  Reinstall, and update regularly.
    Am I wrong?
    According to pacman.log my last successful upgrade was in April May 2014 (hardly anything upgraded so I missed it in the logs at first).
    Strangely enough, pacman -Qe reports the same filesystem version (filesystem 2014.07-1) both before and after the upgrade today.
    Unless I'm mistaken that would mean it wasn't upgraded (or it was upgraded and not rolled back when the transaction failed which wouldn't be my first guess).
    So it would appear you are wrong on both counts, headkase.
    After I forced installation of the replacement lzo the upgrade went ahead without a hitch.
    So no, the system wasn't impossible to upgrade either. Wrong there too.
    I'm not sure exactly what went wrong though. It might have all been due to lzo2 not being automatically replaced successfully. Yet I'm not sure why it would have attempted to upgrade filesystem when it failed then report the same version after the full system upgrade completed successfully.
    Last edited by authentec (2014-08-26 16:16:46)

  • Cannot upgrade the system due to dependency cycle

    Hi there,
    I am trying to upgrade the system with
    pacman -Syu
    Here is what I get:
    warning: dependency cycle detected:
    warning: xorg-server will be installed before its nvidia-utils dependency
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: ipw3945: requires kernel26<2.6.27
    Please help.

    there is no cycle.
    ipw3945 is deprecated. http://www.archlinux.org/news/414/
    remove it and then try to upgrade your system.

  • Please add your experience to this thread: LR V1 vs LR V2- on YOUR system

    Just out of curiosity sake...would people mind putting a few thoughts here as to their upgrade experience. PLEASE NO posts about speed issues, or arguing over system specs etc etc...there are already plenty of those threads here.
    Instead what I am asking is for people to simply answer the following questions, no more no less. So if you like to participate please keep the posts simple. I am hoping this will provide some idea to those of us who have yet to upgrade as to what we can expect. Thanks for helping..
    1) What OS, ie Windows or Mac (XP or Vista, What Mac OS version)
    2) Processor type (cores and speed)
    3) Ram (amount and speed if you know it)
    4) Main working Hard drive (internal, external-& connection here- And speed ie 7200, 10,000, striped raid...etc)
    5) Average # of images in library
    6) In you subjective opinion would you say that LR V1.x ran:
    a) Adequate
    b) Good
    c) Screaming fast
    d) Slooow
    7) Since upgrading to V2 on your CURRENT system how would you rate LR V2 vs your experience in V1? Please use the above a-d answers
    8 ) After your experience with question #7, did you upgrade your system? If so what did you do and how did it affect your perception of speed in LR V2? Again using the above a-d answers
    Thanks again. I know this is not scientific, nor does it address all the possible variables. But it will give us an idea as to how LR V2 MAY run on our systems when compared to V1

    1.Xp-sp3
    2. 2G Amd Athlon 64
    3. 2456 Mb memory
    4. Internal 7200
    5. images +- 1700mb (new cataloque for Aug.)
    6. V1.4 -good, but would lock up on export once a week
    7.a)initially good -first two days after install
    b)uninstalled v1.4 and v2 went from sloooow to very bad.
    c.Today Aug-Registry clear out of anything 'Lightroom',Moved any folder connected to Lightroom off the hard drive except current cataloque, UNINSTALLED V2. shut down computer-rebooted.
    d. Reinstalled V2, redid preferences, opened current cataloque, redid a develop preset EVERYTHING is working WELL! Local adjustments now usable.
    8.No changes to computer. Should have cleared out old Lightroom stuff before installing V2

  • Pacman wrapper to allow source builds (srcpac)

    This is mostly just something that I did because I had never written a wrapper for pacman before and wanted to see if it worked with the current pacman feature set.
    It's 1:30ish in the morning, so my eyes are a little blurry.
    The wrapper is called srcpac.  It's version 0.1 at this point
    The code is quite ugly because I threw it together in the past 3 hours, but my inital tests have been successes.
    Now, for the pitch.  Imagine if you could use pacman to install binary packages as well as build those same packages from source (with your own optimizations).  Not only that, but upgrades remembered which packages were precompiled and which were compiled on the spot.
    Now, imagine that pacman didn't actually handle that, because the hard-core KISS people would complain too much and you wouldn't be able to think while you watch gcc output flash by.  Imagine instead a wrapper around pacman that handled it for you.
    Enter srcpac.  Lights brighten, music comes to a peak, close up!
    srcpac acts exactly the same as pacman (well, it should anyway), except you get this little extra flag -b (or --build) tacked on to -S (--sync) to build from source instead of install from a binary package.
    Let's see an example:
    srcpac -Sb w3m
    will compile w3m, install it, and remember that it was compiled
    srcpac -Sybu
    will upgrade all the packages that need upgrading by building them and remember that they were compiled (be careful with this one, it will include packages that weren't previously compiled).
    srcpac -Syu
    will upgrade all binary packages by installing binaries and upgrade all source packages by compiling from source.
    srcpac -Qi w3m adds an extra line too, "Source", with a simple yes or no.
    Which packages are source and which aren't are stored in /var/lib/srcpac just as files.  If the file exists, then the package was a source package (so it's easy to fix it if srcpac gets confused, also it doesn't touch anything pacman uses).
    While I can guarantee that this wrapper won't break your packages (because it uses pacman and makepkg to do all of it's package related stuff), I can't guarantee it'll work 100% correctly (it's 1:45 now!).
    If anyone is interested, the script is available here: http://xentac.net/svn/arch-tools/srcpac/tags/0.1/srcpac
    Yes, it's in bash.
    Feel free to tell me problems you run into using this tool.  Remember, if you use pacman instead of using srcpac, then all the packages will continue installing as binary packages.
    BEWARE: the -r option isn't fully implemented and may install to / in some cases, I'm pretty sure I don't ever write to / when -r is specified, but I can't be sure.
    .:edit - changed title to show srcpac name - dibble:.

    rls wrote:ABS is fine, but unless I am mistaken, it does nothing to ensure the configure and make stages go smoothly. It is a good way to integrate "home-rolled" packages into the Arch system.
    hmmmm... I could be wrong because I've never used Gentoo, but if you make a package that doesn't already exist for Gentoo, does it do anything to make sure the compilation goes smoothly?  If the package exists, then there is a way to build the package that has been tested by somebody else. This is how ABS works too; if a PKGBUILD exists, you can be reasonably sure it will work.
    I can't imagine a program that can automatically fix or recover from compiler or Makefile errors. If it does, then... wow.
    I assume that Gentoo has a larger package base than Arch, but let's not get into that discussiong again!
    Xentacs script is basically designed to allow you to choose whether you are going to install from source or binary. Assuming the PKGBUILDS are in order (which for arch repository programs they are, because the binaries were built from them!), this should work as flawlessly as installing from binaries.
    Dusty

  • [GIVEAWAY] pacman-wrapper shell functions

    Hi all,
    under http://pastebin.com/vikWUQiK you can find a set of pacman command wrappers that I have found out to be usefull to me.
    I want to share and give other users the opportunity to benefit from it aswell as receiving some critics, ideas, comments and suggestions for improvement.
    Brief description:
    - upgrade only packages wanted by YOU with pacman-upgrade-explicit, else pacman-upgrade-all for system-wide upgrade (deps aswell)
    - all atomic actions log the installed packages, before and after the action (good for debugging, sometimes pkg-names change, etc.)
    - support for multithreaded and concurrent distfiles retrieval (requires aria2c to be installed, else wget is used by default)
    These are things that I (almost always) want to do when using pacman and upgrading packages, so I decided to work with these wrapper functions whenever applicable instead with the (real/backend) pacman.
    This is pretty much it for the beginning.
    Enjoy & Bye,
    Archytect.
    UPDATE 1:
        date: Wed, Oct 12, 2011 11:42:33 AM CEST
        url: http://pastebin.com/A2tQaJgF
        changes/notes:
    added *-preview functions for installs and upgrades
    fixed pacman-fetch not being executed in xargs, because it is a function
    Last edited by Archytect (2011-10-12 09:45:15)

    keenerd wrote:This is fast. And fails even faster if you don't have sudo set up.  The one nice thing about yaourt is that if will check if you can sudo pacman, otherwise it asks for your root password.  I like this behavior.
    I don't understand what you mean. I can run packer as non-root, and when it needs root access it asks me for my password. As far as I can tell, this is the same thing that yaourt does. Are you expecting it to do something else?
    Mikko777 wrote:
    1: yaourt -Syu --aur --devel --noconfirm    (--devel is nice)
    2: on first install edit/ show pkgbuild
    3: yaourt -C  <-- list and edit .pacnew files
    4: vote for packages
    Those are all great ideas. I will add my opinion as another packer user.
    1. I've never used the "--devel" option. Does that mean, it will look for AUR packages that you installed that got the files out of a CVS repository, and download and install the super duper just-updated-at-two-in-the-morning version of it? If that's what it does, then I can imagine that being a nice feature, but it can also be done by doing "packer -S", right? As for "--noconfirm", packer seems pretty unobtrusive to me right now, so I don't really miss that option.
    2. I'm confused. Packer asks me if I want to see the PKGBUILD when I install a package from the AUR. You mean, show the PKGBUILD instead of asking? Or, only show PKGBUILD on the first install?
    3. I personally prefer to do "sudo updatedb && locate pacnew".
    4. I never liked the "vote" feature on yaourt. I think it's confusing. If I just finished installing a package from the AUR, how do I know if I want to vote for it if I haven't used it yet? I prefer to use the program for a while, then use "aurvote".

  • Cannot open indd file in CS5.5? "Please upgrade your plugins to the latest version or upgrade..."

    I refer to a similar forum post here - http://forums.adobe.com/message/4081971 - which outlines a similar problem with opening a file.
    The difference is the file I can no longer open was created using Adobe indd CS5.5 and I am opening it with Adobe indd CS5.5. I have never had this issue previously. The only change is to a new OS on Mac - Version 10.8.2. Error message says "Cannot open "File name" please upgrade your plugins to the latest version or update to the latest version of Adobe" - I know there is CS6 but why should I now need to upgrade suddenly?
    Can anyone help here? I can forward a link to the file in question if needs be.
    Cheers,
    Catie

    @Catie – did you verify, if your InDesign file is saved in version CS5.5?
    You could do so by using a ExtendScript (Adobe's version of JavaScript) written by Jongware.
    Here is the full story of "IDentify.jsx":[Ann] Identify Your InDesign File
    http://forums.adobe.com/message/4071273#4071273
    If the problem is due to a corruption of plug-in version information, I fear you have no chance other than:
    1. Update CS5.5 to the latest bug-fix version => 7.5.3
    2. Download a trial version of InDesign CS6, open and export the file to IDML and re-open it in InDesign CS5.5 (though this might not work for a corrupted file)
    3. Try to open the file on a different machine
    Are there 3rd party plug-ins involved? If so contact their makers…
    Uwe

  • Packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

    There are some people who wish to keep aur and pacman separate. For those people there is aurget and slurpy.
    There are others who wish to integrate them  for certain tasks like myself. For those people there really is only yaourt which is excruciatingly slow and in many ways bloated. For instance, why would you need to use yaourt -R package ever? All that happens when you do that is it calls pacman. What a joke.
    I contend that an aur+pacman wrapper only need to perform 4 major functions.
    1) Search pacman and aur at the same time with one query (-Ss)
    2) Get info from packages in the repository (-Si)
    3) Install packages from either (especially be able to handle the dependencies of aur packages which can sometimes have other dependencies on aur which themselves might have dependencies on aur, etc.) (-S)
    4) Update packages at the same time (again with an interest of handling aur packages which might have new dependencies in newer versions and such) (-Su)
    If you agree with this or just are curious and want to test my program, please download the script from my github and leave feedback. This is a pretty early release (just began working on it 3 days ago), but all four of those functionalities are implemented. There will be cosmetic changes for sure to come and please comment on what you think those should be or any other bugs or problems you might have had.
    github link
    aur link
    packer wiki
    EDIT:
    I have forked pacdiffviewer from yaourt and modified it to work as a stand alone program due to many people saying they coud not switch from yaourt because it has pacdiffviewer. To avoid path conflicts, I have named it pacdiff.
    github link
    aur link
    forum post about pacdiff
    EDIT: Title edited due to gratuitous number of complaints.
    Last edited by bruenig (2010-04-22 02:04:13)

    keenerd wrote:This is fast. And fails even faster if you don't have sudo set up.  The one nice thing about yaourt is that if will check if you can sudo pacman, otherwise it asks for your root password.  I like this behavior.
    I don't understand what you mean. I can run packer as non-root, and when it needs root access it asks me for my password. As far as I can tell, this is the same thing that yaourt does. Are you expecting it to do something else?
    Mikko777 wrote:
    1: yaourt -Syu --aur --devel --noconfirm    (--devel is nice)
    2: on first install edit/ show pkgbuild
    3: yaourt -C  <-- list and edit .pacnew files
    4: vote for packages
    Those are all great ideas. I will add my opinion as another packer user.
    1. I've never used the "--devel" option. Does that mean, it will look for AUR packages that you installed that got the files out of a CVS repository, and download and install the super duper just-updated-at-two-in-the-morning version of it? If that's what it does, then I can imagine that being a nice feature, but it can also be done by doing "packer -S", right? As for "--noconfirm", packer seems pretty unobtrusive to me right now, so I don't really miss that option.
    2. I'm confused. Packer asks me if I want to see the PKGBUILD when I install a package from the AUR. You mean, show the PKGBUILD instead of asking? Or, only show PKGBUILD on the first install?
    3. I personally prefer to do "sudo updatedb && locate pacnew".
    4. I never liked the "vote" feature on yaourt. I think it's confusing. If I just finished installing a package from the AUR, how do I know if I want to vote for it if I haven't used it yet? I prefer to use the program for a while, then use "aurvote".

  • Getting error while opening a saved for later notification: The selected action is not available. The cause may be related to security. Contact your system administrator to verify your permission level for this action.

    Hi All,
    While opening a saved for later notification, we are getting "The selected action is not available. The cause may be related to security. Contact your system administrator to verify your permission level for this action". error.
    This is a custom notification.
    Please help.
    Thanks
    Raghava

    HI All,
    Please help on this issue.
    Thanks
    Raghava

  • I am using a mac mini 2011 an 3gs i phone 2010 macbook white 2008 and a new 2013 apple tv box. When i check info on the cloud I get 'upgrade your operating system to the latest. My question is is it possible to use the icloud system without an upgrade

    I am using a mac mini 2011 an 3gs i phone 2010 macbook white 2008 and a new 2013 apple tv box. When i check info on the cloud I get 'upgrade your operating system to the latest. My question is is it possible to use the icloud system without an upgrade

    iCloud requires OS X 10.7.2.

  • I have a G5 mac using ver 10.4.11 and a newer mac using ver 10.8.4 these are networked. using the new mac i looked up my my photo on the old mac. It then said you need to upgrade your library which it did. Now the old mac can not open the photos

    I have a G5 mac using ver 10.4.11 and a newer mac using ver 10.8.4 these are networked. using the new mac i looked up my my photo on the old mac. It then said you need to upgrade your library which it did. Now the old mac can not open the photos and say that I need to upgrade my I photo to a newer version. The old mac has no more support from apple in software update so I am not sure where I should go from here. can I use new soft ware with the old mac

    The other part of the upgrade message was a warning that once you upgraded you would no longer be able to open the library with the old version which is exaclty what you did and what happened when you choose to continue
    The iphoto library needs to be upgraded to work with this version of iPhoto. Your photo library will not be readable by previous versions of iphoto after the upgrade. The upgrade process may take several minutes depending on the number of photos in the library. Cancel or upgrade.
    So now your choices are to not use iPhoto with the previous version using it onky with the newer version, restore your backup from before you did this upgrade or purchase iPhoto Library Manager and use it to rebuild the library using the older version of iPhoto (instructions are on their web site) thereby downgrading it (without projects)
    LN

  • Is there an easy way to upgrade your OS from 10.5.8 to 10.6

    is there an easy way to upgrade your OS from 10.5.8 to 10.6?
    Thanks for your help
    desmoutis

    Welcome to Apple Support Communities
    To upgrade, first buy Snow Leopard > http://store.apple.com/us/product/MC573/mac-os-x-106-snow-leopard
    It's recommended to make a backup of your files. If the upgrade fails, you will lose data. After making the backup, insert the DVD and follow on-screen steps to upgrade.
    That disc will install 10.6.3, so open  > Software Update, and install OS X 10.6.8

  • In CS4, "Cannot open file" "Please upgrade your plug-ins..."

    Greetings,
    I am using InDesign CS4 on a PC. I am trying to open an .indd file created by our marketing department. I don't know what version of InDesign they use nor whether they work on Macs or PCs.
    When I double-click to open the file, I get a "Cannot Open File" popup box. The box reads "Cannot open docname.indd. Please upgrade your plug-ins to their latest versions, or upgrade to the latest version of Adobe InDesign." It then lists 18 different plugins:
    ASSIGNMENTS.RPLN
    TEXT.RPLN
    SPREAD.RPLN
    MASTER PAGE.RPLN
    TEXT ATTRIBUTES.RPLN
    .... and 13 more.
    When I go to Help > Configure Plug-Ins, I can see that I do have all of these plug-ins. But apparently they are not the latest versions.
    Anyone know how I can update these plugins? I have searched for them on the Adobe website, but no joy.
    Thanks in advance.
    Jen

    It's a safe bet that they are working in CS5. The only way to get those plugins is to install CS5 on your machine.
    You could ask your marketing department to export an IDML file from CS5, which you can open up in CS4, but it might fail horribly (and it's guaranteed to lay out incorrectly if they've used any tools in CS5 that aren't in CS4). If you rely on this workflow, by regularly using a document going back and forth between CS5 and CS4, chances are very, very good that it will fail at a critical moment. The only really safe thing to do here is to get everyone using the same version of InDesign.

  • Error "Could not open [filename]...Please upgrade your plug-ins

    A collegue send us an CS4 InDesign file and when I opened, it says this:
    Error "Could not open [filename]. Please upgrade your plug-ins to their latest versions or upgrade to the latest of Adobe InDesign."
    Any suggestion? I also have CS4 installed.

    I see. Thanks for the help. I just confirmed with the sender of this file and it seems that she has CS5 installed. So, I can that you're right that it's a CS5 file.
    Thanks, again.

Maybe you are looking for