Your message dated Thu, 15 Oct 2015 16:47:23 +0100
with message-id <[email protected]>
and subject line Re: Resolving broken dependencies is not fully working
has caused the Debian Bug report #338386,
regarding Resolving broken dependencies is not fully working
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 [email protected]
immediately.)
--
338386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338386
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.0-3
Severity: normal
Hello,
I had installed a polygen (1.0.6-9) package which depends on
ocaml-base-nox-3.08.3 (provided by ocaml-base-nox 3.08.3-8). The 2nd one
has been installed too and it has been marked as automagically installed.
Recently new ocaml-base-nox (3.09.0-1) has been uploaded into archive.
It provides name ocaml-base-nox-3.09.0 instead of ocaml-base-nox-3.08.3
and polygen has a broken dependency.
aptitude has marked ocaml-base-nox 3.09.0-1 to remove saying:
[quote]
ocaml-base-nox was installed automatically; it is being removed because
all of the packages which depend upon it are being removed:
The following packages depend on ocaml-base-nox and will be broken by its
removal:
* polygen depends on ocaml-base-nox-3.08.3 (provided by ocaml-base-nox
3.08.3-8)
[/quote]
and finally aptitude suggests only one solution: remove albo polygen
packages.
If I remove an auto mark from ocaml-base-nox another solution appears:
keep ocaml-base-nox at current version.
The question is: it is possible to have in this case two solutions
even if ocaml-base-nox is marked as an auto?
Regards
Artur
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-arc4bl
Locale: LANG=C, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.3-6-3.1 0.6.42.2 Advanced front-end for dpkg
ii libc6 2.3.5-7 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-3 GCC support library
ii libncursesw5 5.5-1 Shared libraries for terminal hand
ii libsigc++-2.0-0c2 2.0.16-1 type-safe Signal Framework for C++
ii libstdc++6 4.0.2-3 The GNU Standard C++ Library v3
Versions of packages aptitude recommends:
ii aptitude-doc-en [aptitude-doc 0.4.0-3 English manual for aptitude, a ter
-- no debconf information
--- End Message ---
--- Begin Message ---
2009-12-12 12:28 Artur R. Czechowski:
# After browsing through all bugreports submitted by me I found the
# following ones or as fixed (at least I cannot reproduce the bug
# anymore), or I am just simple not interested in fixing them due
# to some other reasons. As a maintainer you can simply close them,
# I don't mind.
[...]
# 338386 - works for me now
submitter 338386 !
Closing then. The resolver changed a lot during the years after this
bug was submitted, so it was probably fixed in the changes that Burrows
mentions or as a side effect of other changes.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
