Here I go replying to myself again. I noticed just now that the same sort of problem happens if your sources.list contains kde.tdyc.com stuff. That is, we get kde2 package combinations that don't work. I'm beginning to think there is a serious fundamental problem with apt...
The one useful suggestion I got was to download packages first, examine them, and then decide whether or not to install them. Very messy and time-consuming. For the moment, I'm thinking I will just keep commenting out various parts of my sources.list. If Gnome needs upgrading, then us.debian.org must be deleted (commented out). If kde2 needs upgrading, I think I might stick with debian and comment out tdyc, but maybe vice versa???? On Mon, Oct 16, 2000 at 11:24:46AM -0700, Michael Epting wrote: > apt-get upgrade broke my Gnome this weekend. Looking in my apt/archives, I > see that I have a gnome-bin (and maybe some other Gnome-related packages) > that is not from Helix and I suspect that is the source of my problem. So, > does anybody know a way to steer apt preferentially. That is, how can I > ensure that .debs from debian/woody/main don't replace the ones from Helix > that are presumably "integrated" to work together? > > I suspect there is no easy way to accomplish this, short of individually > putting packages on hold and commenting out lines in sources.list, but I > hope I'm wrong. > > Is there even a way to see where potential upgrades, will come from? I > normally apt-get -s upgrade to see what is going to happen before I > upgrade, but this doesn't even show the new package version numbers, much > less where they are coming from.
