[Edgy] Broken packages while trying to install libgtk2.0-dev

Thanks for your bug. Could you run those commands and copy that to a comment?
- apt-cache policy
- apt-cache policy libgtk2.0-dev
- apt-cache policy libglib2.0-dev
- apt-cache policy libglib2.0-0

apt-cache policy:
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://wine.budgetdedicated.com dapper/main Packages
     release o=winehq,a=dapper,l=winehq,c=main
     origin wine.budgetdedicated.com
 500 http://kubuntu.org dapper/main Packages
     release v=6.06,o=Ubuntu,a=dapper,l=Ubuntu,c=main
     origin kubuntu.org
 500 http://packages.freecontrib.org dapper/non-free Packages
     origin packages.freecontrib.org
 500 http://packages.freecontrib.org dapper/free Packages
     origin packages.freecontrib.org
 500 http://theli.free.fr ./ Packages
     origin theli.free.fr
 500 http://security.ubuntu.com edgy-security/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=multiverse
     origin security.ubuntu.com
 500 http://security.ubuntu.com edgy-security/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=universe
     origin security.ubuntu.com
 500 http://security.ubuntu.com edgy-security/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=restricted
     origin security.ubuntu.com
 500 http://security.ubuntu.com edgy-security/main Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=main
     origin security.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-backports/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=multiverse
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-backports/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=universe
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-backports/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=restricted
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-backports/main Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
 500 http://archive.ubuntu.com edgy/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=multiverse
     origin archive.ubuntu.com
 500 http://archive.ubuntu.com edgy/universe Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=universe
     origin archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-updates/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=multiverse
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-updates/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=universe
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-updates/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=restricted
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy-updates/main Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=restricted
     origin gb.archive.ubuntu.com
 500 http://gb.archive.ubuntu.com edgy/main Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=main
     origin gb.archive.ubuntu.com
Pinned packages:

apt-cache policy libgtk2.0-dev:
libgtk2.0...

libglib2.0-dev candidate is 2.10.2-1ubuntu3 where libglib2.0-0 candidate is 2.10.3-0ubuntu1, that doesn't make really sense. What architecture do you use? Does it happen with a different mirror than the gb one?

On Fri, 2006-06-16 at 08:09 +0000, Sebastien Bacher wrote:
> libglib2.0-dev candidate is 2.10.2-1ubuntu3 where libglib2.0-0 candidate
> is 2.10.3-0ubuntu1, that doesn't make really sense. What architecture do
> you use? Does it happen with a different mirror than the gb one?
>

I'm running on i386 (i686 kernel for my Pentium M 725 - Dell Inspiron
6000), and it makes no difference which mirror I use.

To overcome this, I just used aptitude to install a version that worked - I'm sorry, I can't tell you what version that was.

i have a strong feeling its from the non-official repos you added im able to grab the package just fine with apt-get (i only have official repos here is the command and output:

sorry hit the butto by mistake heres the output of it :
gnomefreak@EdgyEft:~$ sudo apt-get install libgtk2.0-dev
Password:
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  libatk1.0-dev libcairo2-dev libpango1.0-dev
Suggested packages:
  libcairo2-doc libgtk2.0-doc libpango1.0-doc
The following NEW packages will be installed:
  libatk1.0-dev libcairo2-dev libgtk2.0-dev libpango1.0-dev
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 2971kB of archives.
After unpacking 10.6MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com edgy/main libatk1.0-dev 1.11.4-0ubuntu1 [103kB]
Get:2 http://archive.ubuntu.com edgy/main libcairo2-dev 1.0.4-0ubuntu1 [349kB]
Get:3 http://archive.ubuntu.com edgy/main libpango1.0-dev 1.12.2-0ubuntu3 [300kB]
Get:4 http://archive.ubuntu.com edgy/main libgtk2.0-dev 2.8.17-1ubuntu5 [2220kB]Fetched 2971kB in 1m51s (26.7kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_US:en_GB:en",
        LC_ALL = (unset),
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Selecting previously deselected package libatk1.0-dev.
(Reading database ... 179724 files and directories currently installed.)
Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.11.4-0ubuntu1_i386.deb) ...
Selecting previously deselected package libcairo2-dev.
Unpacking libcairo2-dev (from .../libcairo2-dev_1.0.4-0ubuntu1_i386.deb) ...
Selecting previously deselected package libpango1.0-dev.
Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.12.2-0ubuntu3_i386.deb) ...
Selecting previously deselected package libgtk2.0-dev.
Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.8.17-1ubuntu5_i386.deb) ...
Setting up libatk1.0-dev (1.11.4-0ubuntu1) ...
Setting up libcairo2-dev (1.0.4-0ubuntu1) ...
Setting up libpango1.0-dev (1.12.2-0ubuntu3) ...
Setting up libgtk2.0-dev (2.8.17-1ubuntu5) ...
gnomefreak@EdgyEft:~$

ignore the locales error thats thanks to libc6 ;)

could you try to install libglib2.0-0?

On Fri, 2006-06-23 at 09:10 +0000, Sebastien Bacher wrote:
> could you try to install libglib2.0-0?
>
It is installed; as I said, by rolling back to what appeared to be an
earlier version using one of aptitude's suggested solutions, I managed
to install libgtk2.0-dev. However, this now seems to be the latest
version, as aptitude install libgtk2.0-dev showed no updates to the
package. The version is (of libgtk2.0-dev) 2.8.17-1ubuntu5, and (of
libglib2.0-0) 2.10.2-1ubuntu3. Shouldn't they be the same - either
2.8.17 or 2.10.2?

Iam gonna mark this as fixed due to the problem being no longer producable. If this is still an issue for someone please feel free to reopen it thank you.
ps. Toby not libgtk and libglib are not the same file.

On Wed, 2006-07-19 at 18:07 +0000, John Vivirito wrote:
> ps. Toby not libgtk and libglib are not the same file.

Thanks: sorry; I wasn't sure!

I'm having the same problem.
There is definately something wrong with the files on one of the repositories.

libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.10.6-0ubuntu3) but 2.10.6-0ubuntu3.1 is to be installed

This is right. I see that libgtk2.0 with the 3.1 sub-version is in fact installed, and the libgtk2.0-dev package does require the 3.0 version.

$ apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://security.ubuntu.com edgy-security/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=universe
     origin security.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=multiverse
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=universe
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/main Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=main
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-updates/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-updates/main Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=main
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/universe Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=universe
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/main Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=main
     origin de.archive.ubuntu.com

and:

$ policy libgtk2.0-dev
libgtk2.0-dev:
  Installed: (none)
  Candidate: 2.10.6-0ubuntu3
  Version table:
     2.10.6-0ubuntu3 0
        500 http://de.archive.ubuntu.com edgy-updates/main Packages
     2.10.6-0ubuntu1 0
        500 http://de.archive.ubuntu.com edgy/main Packages
[

Steve, you don't have configured edgy-updates/universe, that's not an Ubuntu bug no

Hi, Sebastian,

This appears not to be a problem with that particular package,
but here I'm looking at my Adept Manager under Manage Repositories, and I don't see anything about edgy-updates/universe.

Could you tell me how to do that?

Since I have only modified the repositories using Adept Manager, I am thinking this is a problem with that program.

Sebastian:

I figured out how to add a repository in Adept.

I clicked on
debian-updates main restricted
then clicked "Clone"
which made a copy of that repository
then I double clicked the copy's line, which allowed me to edit the fields. I changed "main restricted" to "universe", then clicked "Apply".

But sadly, it doesn't fix the problem. Now I have

$apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://security.ubuntu.com edgy-security/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-security,l=Ubuntu,c=universe
     origin security.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/multiverse Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=multiverse
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=universe
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-backports/main Packages
     release v=6.10,o=Ubuntu,a=edgy-backports,l=Ubuntu,c=main
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-updates/universe Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=universe
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-updates/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy-updates/main Packages
     release v=6.10,o=Ubuntu,a=edgy-updates,l=Ubuntu,c=main
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/universe Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=universe
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/restricted Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=restricted
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com edgy/main Packages
     release v=6.10,o=Ubuntu,a=edgy,l=Ubuntu,c=main
     origin de.archive.ubuntu.com
Pinned packages:

you might want to use an user forum for that, I don't use kubuntu nor adept for my part and the bug tracker is not really the right place to ask about how to use that software

Sebastian,

The problem plainly has nothing to do with Adept or Kubuntu, per se.
It is a package problem.

It might be that I have mis-configured my repositories somehow, but besides enabling the repositories that were provided by my distro, the only repository I have enabled was the one you suggested.

The bug persists, and we don't know what its root is.

You seem to know something about repositories...can you look again at the ones I have enabled, and see if something is amiss?

you probably need edgy-security/main, you configured it for universe only

Thanks Sebastian,

I don't understand the relationship between the output of apt-cache policy and the repository settings.

But I was configured to use
    edgy-security/main.

I figured out what was missing: you had previously recommended
     edgy-updates/universe
which I did, but for type 'deb' only. This made this entry unsymmetrical with the other repository entries, which had both 'deb' and 'deb-src'. When I enabled the 'deb-src' entry, I got the corrrect libgtk versions.

This does then appear not to be a but with the library packages in question here, so I'll drop it. However, it appears to be a problem that a lot of people have. In my case, I have only altered the repositories carefully, and only when it was recommended that I do so. Yet it gets tangled up.

But I don't know where to report this. I'll continue to think about it.

apt-cache policy list the sources configured. When a package has binaries to main and universe (and they need to be in sync) you need to have the same sources configure for them. The deb-src sources are used when you "apt-get source" something, not for package installation. Anyway package management tools should be smarter about that, feel free to open a bug about that on the tool you are using if there is not already one