Bug#795260: marked as done (Please consider downgrading when calling apt-get -f install)
Your message dated Wed, 12 Aug 2015 14:06:19 +0200
with message-id <20150812140339.GA25789@debian.org>
and subject line Re: Bug#795260: Please consider downgrading when calling apt-get -f install
has caused the Debian Bug report #795260,
regarding Please consider downgrading when calling apt-get -f install
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.)
--
795260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795260
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.0.9.1
Severity: normal
Lets say the following packages are installed:
Package: foo
Version: 1.0
Depend: bar | baz
Package: bar
Version: 1.0+broken
Depends: broken
and the default repository has the following packages:
Package: foo
Version: 1.0
Depend: bar | baz
Package: bar
Version: 1.0
Package: baz
Version: 1.0
Trying to install anything with apt tells you to try "apt-get -f
install" to fix the broken dependency. But "apt-get -f install" will
then suggest removing bar and installing baz.
Instead I think the less intrusive fix would be to suggest
downgrading bar but apt-get does not seem to consider that at all.
MfG
Goswin
-- Package-specific info:
-- (/etc/apt/preferences present, but not submitted) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages apt depends on:
ii debian-archive-keyring 2012.4
ii gnupg 1.4.16-1.1
ii libapt-pkg4.12 1.0.9.1
ii libc6 2.19-17
ii libgcc1 1:4.9.2-10
ii libstdc++6 4.9.2-10
apt recommends no packages.
Versions of packages apt suggests:
ii apt-doc 1.0.2
ii aptitude 0.6.10-1
ii dpkg-dev 1.17.18
pn python-apt <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Aug 12, 2015 at 01:23:16PM +0200, Goswin von Brederlow wrote:
> Package: apt
> Version: 1.0.9.1
> Severity: normal
>
> Lets say the following packages are installed:
>
> Package: foo
> Version: 1.0
> Depend: bar | baz
>
> Package: bar
> Version: 1.0+broken
> Depends: broken
>
> and the default repository has the following packages:
>
> Package: foo
> Version: 1.0
> Depend: bar | baz
>
> Package: bar
> Version: 1.0
>
> Package: baz
> Version: 1.0
>
> Trying to install anything with apt tells you to try "apt-get -f
> install" to fix the broken dependency. But "apt-get -f install" will
> then suggest removing bar and installing baz.
>
> Instead I think the less intrusive fix would be to suggest
> downgrading bar but apt-get does not seem to consider that at all.
I'm sorry, but removals are safe, downgrades are not.
While they work in most cases, they are completely unsupported, so it's
nothing we should suggest.
So we are not going to add that, and I'm closing this bug. Sorry
about that.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
Reply to: