Re: How to determine why a package is "held back"?
okay, i just zapped most of this thread yesterday, and now i go back to look for it and it's not yet on geocrawler, and it's not yet on lists.debian.org either... what's the sequence for establishing WHY apt is holding packages back from being upgraded, again? :) thanks! -- I use Debian/GNU Linux version 3.0; Linux server 2.4.20-k6 #1 Mon Jan 13 23:49:14 EST 2003 i586 unknown DEBIAN NEWBIE TIP #60 from Vineet Kumar <[EMAIL PROTECTED]> : Been hoping to find A FEATURE-PACKED MUTT CONFIG FILE? Check out the ones at Sven Guckes' site: http://www.fefe.de/muttfaq/muttrc There's also some great vimrc ideas there, too. Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to determine why a package is "held back"?
Le lun 27/01/2003 à 10:58, Ron Johnson a écrit : > On Mon, 2003-01-27 at 03:07, Xavier Bestel wrote: > > > You should do this: > > > # apt-gte update && apt-get dist-upgrade > > > > I prefer this: > > > > # apt-get update && apt-get dist-upgrade --no-remove > > > > > > That way if there's a package with broken dependencies, I can see it > > before it removes half my desktop. > > Sounds like you put that in a cron script, and I don't like that > idea. However, this is recommended method, I believe: > In the cron script: > # apt-get update && apt-get -d -u dist-upgrade > Next morning, from a terminal window: > # apt-get -u dist-upgrade No, I didn't put some auto-upgrade thing in a cron script. However I'll look at what your commands do, that seems interesting. Xav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to determine why a package is "held back"?
On Mon, 2003-01-27 at 03:07, Xavier Bestel wrote: > > You should do this: > > # apt-gte update && apt-get dist-upgrade > > I prefer this: > > # apt-get update && apt-get dist-upgrade --no-remove > > > That way if there's a package with broken dependencies, I can see it > before it removes half my desktop. Sounds like you put that in a cron script, and I don't like that idea. However, this is recommended method, I believe: In the cron script: # apt-get update && apt-get -d -u dist-upgrade Next morning, from a terminal window: # apt-get -u dist-upgrade That'll allow you to decide what you *really* want to do, especially regarding config files. -- +---+ | Ron Johnson, Jr.mailto:[EMAIL PROTECTED] | | Jefferson, LA USA http://members.cox.net/ron.l.johnson | | | | "Fear the Penguin!!" | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to determine why a package is "held back"?
> You should do this: > # apt-gte update && apt-get dist-upgrade I prefer this: # apt-get update && apt-get dist-upgrade --no-remove That way if there's a package with broken dependencies, I can see it before it removes half my desktop. Xav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to determine why a package is "held back"?
On Sun, 2003-01-26 at 09:35, stan wrote: > I've got 2 differnt "testing' machines that should be set up in a very > similar fashion (mine which I tend to test things on first, and my wife's, > which I ry to keep _very_ stable). > > Latley when I do apt-gte update ; apt-get dist-upgrade, her machine has > been "holding back" gnome-common. > > How can I determine why this is os, and correct it? # apt-get -s -u install gnome-common Oh, and NEVER do "apt-gte update ; apt-get dist-upgrade". If the "apt-get upgrade" fails, the dist-upgrade will proceed anyway. You should do this: # apt-gte update && apt-get dist-upgrade -- +---+ | Ron Johnson, Jr.mailto:[EMAIL PROTECTED] | | Jefferson, LA USA http://members.cox.net/ron.l.johnson | | | | "Fear the Penguin!!" | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to determine why a package is "held back"?
On Sun, Jan 26, 2003 at 10:35:00AM -0500, stan wrote: > I've got 2 differnt "testing' machines that should be set up in a very > similar fashion (mine which I tend to test things on first, and my wife's, > which I ry to keep _very_ stable). > > Latley when I do apt-gte update ; apt-get dist-upgrade, her machine has > been "holding back" gnome-common. > > How can I determine why this is os, and correct it? This may tell you why it is held back: Start aptitude. Search for gnome-common. Press enter to display package description and dependencies. Scroll to bottom to view available versions. Highlight held-back version and press enter and scroll through list to find dependencies that are not being met. Repeatedly press "q" to close displayed information and exit aptitude. -- Jerome msg26461/pgp0.pgp Description: PGP signature
How to determine why a package is "held back"?
I've got 2 differnt "testing' machines that should be set up in a very similar fashion (mine which I tend to test things on first, and my wife's, which I ry to keep _very_ stable). Latley when I do apt-gte update ; apt-get dist-upgrade, her machine has been "holding back" gnome-common. How can I determine why this is os, and correct it? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
