On Tue, May 22, 2012 at 4:54 PM, Jonathan Nieder <[email protected]> wrote: > ... > > It is normal for some packages to have unmet dependencies in unstable. > A good way to cope is to use normal "apt-get upgrade" (not > dist-upgrade) and let the packages have some time to sync up. >
No. Things did not resolve with "apt-get upgrade. > ... > > But I don't think that is what is happening above. I think what > happened is that you installed zlib 1:1.2.7.dfsg-7 from > incoming.debian.org "by hand" using "dpkg --install" packages from > incoming.debian.org and then tried to use apt-get to upgrade other > packages and encountered the above trouble. > > Am I guessing correctly? If so, I want to say "don't do that, then". > No I did not install zlib 1:1.2.7.dfsg-7 "by hand". > > But I don't have any leg to stand on, since we don't provide some > other obvious command which would do the right thing, namely to > install the package specified on the command line while ensuring > that dependencies of other packages remain satisfied. > Perhaps someone could shed some light as to how one could install zlib1g (= 1:1.2.7.dfsg-4). All I can get on this is it's the news announcing that particular version has been accepted [1]. But I can only think of obscure ways of reaching that version. A .deb and/or how to make it would be fine. > > If I have guessed correctly, the underlying bug would be a wishlist > bug against apt: please provide a simple way to install a single .deb > package from incoming.debian.org. > > Did I guess right? > That's not a question for me, I guess - is it? Sophoklis [1] http://packages.qa.debian.org/z/zlib/news/20120520T160616Z.html -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
