Re: Strange dependencies with apt-get/dselect
Jorge Santos <firstname.lastname@example.org> writes:
> When I tried to upgrade with dselect it would try to uninstall
> j2sdk1.3 and other packages even when there was no mention of them in
> the dependencies problems screen. Then I tried to run apt-get upgrade
> and see what happened:
> root@dep3$ apt-get upgrade ~
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages have been kept back
> eterm xspecs
> 79 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> Sorry, but the following packages have unmet dependencies:
> eterm: Depends: libc6 (>= 2.1.97) but 2.2.4-1 is to be installed
> j2sdk1.3: Depends: java-common but 0.7 is to be installed
> libgnome-pilot0: Depends: libglib1.2 (>= 1.2.0) but 1.2.10-1.2 is to be installed
> Depends: libgnome32 (>= 1.2.0) but 1.2.13-9 is to be installed
> Depends: libz1
> python-graphics: Depends: python-base (>= 1.5) but 1.5.2-16 is to be installed
> task-debian-devel: Depends: maint-guide but 1.0.2 is to be installed
> task-newbie-help: Depends: mc but 4.5.54-1.1 is to be installed
> Depends: lynx
> task-tex: Depends: src2tex but 2.12h-5 is to be installed
> Depends: dviutils but 2.19-8 is to be installed
> E: Internal Error, InstallPackages was called with broken packages!
> Aren't this dependencies issues strange? j2sdk1.3 depends on
> java-common, with no specific version mentioned, and java-common is
> installed and at its newest version, and what about the dependencies
> to newer packages not met?
> Any ideas? What's going on?
> jorge santos
Oh, and this just happened when I just switched from the main Debian
mirror to another does this has anything to do with it?
Also, I get sources from a different place than binaries, is this a
good idea? I can't imagine that being a problem (aside from the
sources being a little out of sync with the binaries which I don't
care that much about).