From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Sage Weil <sage@inktank.com>
Cc: Xiaopong Tran <xiaopong.tran@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: Strange behavior after upgrading to 0.48
Date: Fri, 06 Jul 2012 16:52:26 +1200 [thread overview]
Message-ID: <4FF66F0A.7000804@catalyst.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.64.1207052117080.565@cobra.newdream.net>
On 06/07/12 16:17, Sage Weil wrote:
> On Fri, 6 Jul 2012, Mark Kirkwood wrote:
>>
>> FYI: I ran into this too - you need to do:
>>
>> apt-get dist-upgrade
>>
>> for the 0.47-2 packages to be replaced by 0.48 (of course purging 'em and
>> reinstalling works too...just a bit more drastic)!
> That's strange... anyone know why?
>
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
From the apt-get manual:
upgrade
upgrade is used to install the newest versions of all packages
currently installed on the system from the sources enumerated in
/etc/apt/sources.list. Packages currently installed with new
versions available are retrieved and upgraded; under no
circumstances are currently installed packages removed, or
packages
not already installed retrieved and installed. New versions of
currently installed packages that cannot be upgraded without
changing the install status of another package will be left at
their current version. An update must be performed first so that
apt-get knows that new versions of packages are available.
dist-upgrade
dist-upgrade in addition to performing the function of upgrade,
also intelligently handles changing dependencies with new
versions
of packages; apt-get has a "smart" conflict resolution
system, and
it will attempt to upgrade the most important packages at the
expense of less important ones if necessary. So, dist-upgrade
command may remove some packages. The /etc/apt/sources.list file
contains a list of locations from which to retrieve desired
package
files. See also apt_preferences(5) for a mechanism for
overriding
the general settings for individual packages.
Does 0.48 have new dependancies perhaps?
next prev parent reply other threads:[~2012-07-06 4:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 6:41 Strange behavior after upgrading to 0.48 Xiaopong Tran
2012-07-05 6:47 ` Xiaopong Tran
2012-07-05 14:26 ` Sage Weil
2012-07-05 14:35 ` Xiaopong Tran
2012-07-05 14:38 ` Sage Weil
2012-07-06 2:38 ` Xiaopong Tran
2012-07-06 4:14 ` Mark Kirkwood
2012-07-06 4:17 ` Sage Weil
2012-07-06 4:52 ` Mark Kirkwood [this message]
2012-07-06 5:07 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF66F0A.7000804@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=xiaopong.tran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.