On 10/30/2011 06:23 PM, Marc J. Driftmeyer wrote:
Of course it has to do with
libgnome-desktop-3.0

Not to mention libgail and glibmm. Your Debian GNOME 3.2 list is false.

http://www.0d.be/debian/debian-gnome-3.2-status.html

You cannot upgrade to libgnome-desktop-3.2 without breaking gnome-shell, evolution and several other packages.

A simple sudo apt-get upgrade after you install gnome-shell 3.2.1 by hand reveals all the packages that will be dumped when trying to upgrade including gnome-shell 3.2.1.

Regarding the Status of glibmm:

It claims all architectures are ready when they aren't even close.

http://packages.debian.org/search?keywords=libglibmm-2.4-1c2a


experimental <http://packages.debian.org/experimental/libglibmm-2.4-1c2a>(libs): C++ wrapper for the GLib toolkit (shared libraries)
2.30.0-1: armel hurd-i386 i386 powerpc s390

Sorry, but how is it that armel, powerpc and s390 have built packages before the most common architecture, amd64?

I won't even comment on hurd. Any time I see a hurd package before the rest of the options I have to shake my head. The priority seems to imply availability of hardware first and serving the most commonly used architecture first.

first => last

- Marc

- Marc

On 10/30/2011 06:03 AM, Gergely Nagy wrote:
Michael Biebl<[email protected]>  writes:

The dependency against libgnome-desktop-3-0 instead of libgnome-desktop-3-2 
breaking upgrade path from 3.0.x to 3.2.1 in Experimental.

What upgrade path is broken? TBH I'm not really sure what you are
complaining about. Please be more verbose what your problem is.
I think the problem is with libgail. When doing an aptitude install
gnome-shell/experimental, it can't find a solution where major parts of
gnome wouldn't be removed.

The best it could do, without keeping gnome-shell at 3.0 is:

The following actions will resolve these dependencies:

       Remove the following packages:
1)      gnome
2)      gnome-core
3)      gnome-desktop-environment
4)      libgail-3-common

       Install the following packages:
5)      gir1.2-accountsservice-1.0 [0.6.15-1 (unstable)]

       Upgrade the following packages:
6)      gir1.2-gtk-3.0 [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
7)      gjs [1.29.0-2+b1 (now, unstable) ->  1.30.0-1 (experimental)]
8)      libgail-3-0 [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
9)      libgjs0b [1.29.0-2+b1 (now, unstable) ->  1.30.0-1 (experimental)]
10)     libglib2.0-0 [2.28.8-1 (now, unstable) ->  2.30.1-2 (experimental)]
11)     libglib2.0-0-dbg [2.28.8-1 (now, unstable) ->  2.30.1-2 (experimental)]
12)     libglib2.0-bin [2.28.8-1 (now, unstable) ->  2.30.1-2 (experimental)]
13)     libglib2.0-dev [2.28.8-1 (now, unstable) ->  2.30.1-2 (experimental)]
14)     libgtk-3-0 [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
15)     libgtk-3-bin [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
16)     libgtk-3-common [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
17)     libgtk-3-dev [3.0.12-2 (now, unstable) ->  3.2.1-1 (experimental)]
18)     libmutter0 [3.0.2.1-4 (now, unstable) ->  3.2.1-1 (experimental)]
19)     mutter-common [3.0.2.1-4 (now, unstable) ->  3.2.1-1 (experimental)]

This seems to happen because libgail-3-common has a dependency on
libgail-3-0 (= 3.0.12-2), and libgail-3.0 would be upgraded to 3.2.1-1,
breaking libgail-3-common. And gnome-core depends on libgail-3-common,
and that's where all hell breaks loose.

(an updated libgail-3-common does not seem to be available in
experimental).

I'm not entirely sure this is related to the original report, as it has
nothing to do with libgnome-desktop-3.0 as far as I see, but it sure
prevents one from installing gnome-shell from experimental. At least, if
one does not wish to remove a few handy meta packages.


--
Marc J. Driftmeyer
Email :: [email protected] <mailto:[email protected]>
Web :: http://www.reanimality.com
Cell :: (509) 435-5212

--
Marc J. Driftmeyer
Email :: [email protected] <mailto:[email protected]>
Web :: http://www.reanimality.com
Cell :: (509) 435-5212

<<attachment: mjd.vcf>>

Reply via email to