[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#762567: marked as done (apt-get wants to remove stellarium)

Your message dated Fri, 14 Aug 2015 14:38:48 +0200
with message-id <20150814123848.GA15182@crossbow>
and subject line Re: apt-get wants to remove stellarium
has caused the Debian Bug report #762567,
regarding apt-get wants to remove stellarium
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
762567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762567
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.0.9.1

I installed jessie and a bunch of packages, then upgraded to sid.
Now "apt-get dist-upgrade" wants to remove stellarium:

# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
  libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5declarative5 libqt5gui5 libqt5network5 libqt5opengl5
  libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5script5 libqt5sql5 libqt5webkit5 libqt5widgets5
  libxcb-render-util0 libxcb-sync1 libxcb-xkb1 libxkbcommon-x11-0 qtquick1-qml-plugins stellarium-data
Use 'apt-get autoremove' to remove them.
Done
The following packages will be REMOVED:
  stellarium
The following packages will be upgraded:
  libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5declarative5 libqt5gui5 libqt5network5 libqt5opengl5
  libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5script5 libqt5sql5 libqt5webkit5 libqt5widgets5
  qtquick1-qml-plugins
15 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 20.8 MB of archives.
After this operation, 9317 kB disk space will be freed.
Do you want to continue? [Y/n] 


This makes no sense at all. apt-get *knows* that I wanted to install
stellarium by itself, and apt-get *knows* that I didn't explicitly asked
for all those libraries to be installed alone. This knowledge is in fact
the base for the autoremove feature.

But apparently apt-get does not use all the information it has in this case.

Whenever possible, packages that I asked to install should have
absolute priority (i.e. should be kept installed) over packages
that I didn't explicitly asked to be installed.


Way to reproduce: Install jessie, install stellarium, then upgrade to sid.


Thanks.

--- End Message ---
--- Begin Message --- 
On Tue, Sep 23, 2014 at 10:54:49AM +0200, Santiago Vila wrote:
> This makes no sense at all. apt-get *knows* that I wanted to install
> stellarium by itself, and apt-get *knows* that I didn't explicitly asked
> for all those libraries to be installed alone. This knowledge is in fact
> the base for the autoremove feature.
> 
> But apparently apt-get does not use all the information it has in this case.
> 
> Whenever possible, packages that I asked to install should have
> absolute priority (i.e. should be kept installed) over packages
> that I didn't explicitly asked to be installed.

This means that an old package you once installed but is now no longer
updated/included in the Debian Release will prevent you from ever
updating…

dist-upgrade is called that way because it upgrades between distribution
releases – so what happens here is that apt things stellarium is no
longer updated and hence has to go away to not prevent the upgrade of
other packages. Okay, the other packages are dependencies of stellarium,
but that is how unstable works. A few days later at most stellarium was
rebuild and the upgrade was working properly.

The "problem" you discribe never happens in stable or testing, those
users would just be effected by the negative effects of fixing this
"problem". As unstable users are expected to be experienced enough to
deal with such temprorary breakage, this is an acceptable tradeoff and
hence it works as designed and isn't a bug. Therefore closing.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: