Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #175901 > unrolled thread

Package upgrades why and how to avoid?

Back to article view | Back to linux.debian.user

Contents

  Package upgrades why and how to avoid? Man_Without_Clue <love.chaser@gmail.com> - 2016-12-24 03:50 +0100
    Re: Package upgrades why and how to avoid? Joe <joe@jretrading.com> - 2016-12-24 10:40 +0100
    Re: Package upgrades why and how to avoid? Michael Lange <klappnase@freenet.de> - 2016-12-24 13:20 +0100
      Re: Package upgrades why and how to avoid? A_Man_Without_Clue <love.chaser@gmail.com> - 2016-12-24 14:30 +0100

#175901 — Package upgrades why and how to avoid?

Hi all,

Couple days ago I was trying to general package update by simply "Mark
All Upgrades" and "Apply" from the Synaptic package manager as I usually do.

I noticed the audacious was up-gradable so I simply marked all upgrades
and tried to install. However I also noticed by doing this it will
remove other packages such as Skype, and others.

Why this happens and how to avoid this?


I guess just simply choosing upgrading all packages is not good idea.

Thanks

[toc] | [next] | [standalone]

#175904

On Sat, 24 Dec 2016 11:47:21 +0900
Man_Without_Clue <love.chaser@gmail.com> wrote:

> Hi all,
> 
> Couple days ago I was trying to general package update by simply "Mark
> All Upgrades" and "Apply" from the Synaptic package manager as I
> usually do.
> 
> I noticed the audacious was up-gradable so I simply marked all
> upgrades and tried to install. However I also noticed by doing this
> it will remove other packages such as Skype, and others.
> 
> Why this happens and how to avoid this?
> 
> 
> I guess just simply choosing upgrading all packages is not good idea.
> 

The short answer is 'Yes'.

The longer answer is 'Look at the proposed removals. Now go through the
Synaptic Installed (upgradable) list and select some packages, right
click and click 'Mark for Upgrade', and when you have a few selected,
click 'Apply'. If you are warned of removes, clear some marked packages
and try again. You will probably be able to upgrade most packages in a
few cycles of this, but may have to leave a few. After a while, you
will get something of a feel for which packages are responsible for the
proposed removals'

You are using either the unstable or testing distribution, and
sometimes not all packages that form a consistent set are ready for
upgrade at the same time. In that case, you wait a few days until the
upgrade works without removals.

Sometimes, new packages with different names replace old ones, and the
old ones are removed permanently. This is a condition which will not
change after a few days, and again after a while you will learn to
recognise it. Synaptic is not much help here, either the aptitude or
apt-get command line suites will give you much more information about
what is going on.

In short, running either testing or unstable distributions is not a
'fit and forget' operation, they do require a little hand-holding. They
are both continuously upgradeable operating systems, as opposed to
'upgrade to a complete shiny new version with a different number' kinds,
as the stable distribution is. They therefore do require a little care
to keep them in a more-or-less fully operational state at all times.

For future reference, the apt-get and aptitude text commands have
options for permitting removals or not. 'aptitude update', followed by
'aptitude safe-upgrade' will never remove a package (other than the
older versions being upgraded) and 'apt-get update' followed by
'apt-get upgrade' will do much the same. 'aptitude full-upgrade' is the
command to do everything. but it will still warn of removals before
going ahead, and 'apt-get dist-upgrade' again will do much the same.
Synaptic is the GUI front-end to apt-get, and will by default want to
do a 'dist-upgrade'.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#175908

On Sat, 24 Dec 2016 11:47:21 +0900
Man_Without_Clue <love.chaser@gmail.com> wrote:

> Why this happens and how to avoid this?

As an appendix to Joe's extensive reply:

Once you found the package(s) that would cause e.g. Skype to be removed,
you can put these packages on "hold" (or "lock" in synaptic) so these
packages won't be upgraded on future system upgrades until the hold is
removed, allowing you to do full-/dist-upgrades without removing other
packages that you want to keep.
Unfortunately however, each one of synaptic, apt-get and aptitude have
their own "hold" system, which won't be respected by the other programs,
so to be on the safe side you might have to "hold" a package more than
just once.

To put a package on "hold" for apt-get, just do  (as root):
	apt-mark hold <packagename>
The aptitude command is similar:
	aptitude hold <packagename>
In synaptic, select the package and pick from the menu
	Package -> Lock Version

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

No one may kill a man.  Not for any purpose.  It cannot be condoned.
		-- Kirk, "Spock's Brain", stardate 5431.6

[toc] | [prev] | [next] | [standalone]

#175910

Joe, Michael,

Thank you guys, good explanation and tutorial.

I didn't know about "holding" feature so I will definitely implement that.
That was good help, thank you again.

Man without clue



On 12/24/2016 09:06 PM, Michael Lange wrote:
> On Sat, 24 Dec 2016 11:47:21 +0900
> Man_Without_Clue <love.chaser@gmail.com> wrote:
> 
>> Why this happens and how to avoid this?
> 
> As an appendix to Joe's extensive reply:
> 
> Once you found the package(s) that would cause e.g. Skype to be removed,
> you can put these packages on "hold" (or "lock" in synaptic) so these
> packages won't be upgraded on future system upgrades until the hold is
> removed, allowing you to do full-/dist-upgrades without removing other
> packages that you want to keep.
> Unfortunately however, each one of synaptic, apt-get and aptitude have
> their own "hold" system, which won't be respected by the other programs,
> so to be on the safe side you might have to "hold" a package more than
> just once.
> 
> To put a package on "hold" for apt-get, just do  (as root):
> 	apt-mark hold <packagename>
> The aptitude command is similar:
> 	aptitude hold <packagename>
> In synaptic, select the package and pick from the menu
> 	Package -> Lock Version
> 
> Regards
> 
> Michael
> 
> 
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
> 
> No one may kill a man.  Not for any purpose.  It cannot be condoned.
> 		-- Kirk, "Spock's Brain", stardate 5431.6
> 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web