Re: google chrome browser being kept back on squeeze?

http://www.debian.org/releases/wheezy/kfreebsd-i386/release-notes/ch-upgrading.en.html

specifically, section 4.3, Preparing sources for APT, basically explains how the upgrade is going to work, and what to do with the external repository source lines.

Sorry for the noise.

On Mon, Jun 24, 2013 at 6:32 AM, Joel Rees <joel.rees@gmail.com> wrote:

Okay,

On Mon, Jun 24, 2013 at 12:29 AM, Curt <curty@free.fr> wrote:

On 2013-06-23, Joel Rees <joel.rees@gmail.com> wrote:
>
> Since sometime last week, apt-get upgrade and dist-upgrade both report that
> google-chrome-stable has been kept back.
>
> Anyone else seeing this? Anyone know why?
>

I'm seeing it. Wheezy (cough) is now stable is the why.

The following packages have unmet dependencies:
google-chrome-stable : Depends: gconf-service but it is not installable
Depends: libgconf-2-4 (>= 2.31.1) but it is not installable
Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) but it is not installable
Depends: libgtk2.0-0 (>= 2.24.0) but 2.20.1-2 is to be installed
Depends: libnspr4 (>= 1.8.0.10) but it is not going to be installed
Depends: libnss3 (>= 3.12.6) but it is not going to be installed
Depends: libstdc++6 (>= 4.6) but 4.4.5-8 is to be installed
Depends: libx11-6 (>= 2:1.4.99.1) but 2:1.3.3-4+squeeze1 is to be installed

So, the docs on upgrading to wheezy indicates that holds should be removed, but this hold can't be removed before upgrading to wheezy. So the package should be removed before installing wheezy? And pulled back in after the install?

--
Joel Rees

--
--
Joel Rees