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

Bug#167398: marked as done (Provide a way to satisfy dependencies using a minimum of non-default versions)

Your message dated Fri, 14 Aug 2015 22:20:41 +0200
with message-id <20150814202041.GA24448@crossbow>
and subject line Re: Bug#167398: selecting packages via depends relations, esp. with versioned deps
has caused the Debian Bug report #167398,
regarding Provide a way to satisfy dependencies using a minimum of non-default versions
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.)


-- 
167398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167398
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: aptitude
Version: 0.2.11.1-3
Severity: normal

 I have stable and unstable repositories in my sources.list, and
APT::Default-Release "stable"; in my apt.conf.  Tubesock is a
package that's only in unstable, and has versioned dependencies that require
the unstable versions of libatk1.0-0, libgli2.0-0, libgtk2.0-0, and
libpango1.0-0.  (expanding the depends tree as much as possible, there is
only one version listed for each dep, since the stable versions don't
satisfy the versioned dependencies.)

 On tubesock's its package screen, pressing '+' on the "--\ Depends" line
should select the required version of all the packages listed, but it
doesn't.  It selects the unstable version of libatk1.0-0, but the stable
version of the other three.  That's right, aptitude selects glib 2.0.1-2,
which does not help at all in satisfying tubesock's dependencies!  I have no
idea why libatk's unstable version gets selected.

 Again on tubesock's pkg screen, with the selection line on the libglib2.0-0
line, pressing '+' still selects the stable version.  Moving down to the
actual 2.0.6-1 line, pressing plus will select version 2.0.6-1 (finally!).
However, pressing '_' doesn't do anything on that line.  You have to press
return on that line to go to the package page and press '_' there to
deselect it.

 All of this is part of a larger problem:  Aptitude is cumbersome to use
when a package that isn't from the default release.  When I use aptitude to
install the unstable version of a package, I end up having to manually
select the dependencies of the unstable version.  If you fix the problems I
described using tubesock as an example without addressing the larger problem
of selecting a package from unstable on a machine with Default-release
"stable", then please downgrade this bug to wishlist, or something.

 When a package with dependencies that require other packages from unstable
to be installed, aptitude should be willing to satisfy those dependencies,
instead of forcing the unstable packages to be manually selected.  The
distinction between manually selected and automatically selected packages is
important, and would be even more important if debfoster was better
integrated with anything else :)

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux llama.nslug.ns.ca 2.4.19preempt-gcc32 #6 Wed Sep 25 05:30:53 ADT 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.2- 0.5.4           Advanced front-end for dpkg
ii  libc6                    2.3.1-3         GNU C Library: Shared libraries an
ii  libncurses5              5.2.20020112a-7 Shared libraries for terminal hand
ii  libsigc++0               1.0.4-3         Type-safe Signal Framework for C++
ii  libstdc++2.10-glibc2.2   1:2.95.4-7      The GNU stdc++ library

--- End Message ---
--- Begin Message --- 
Version: 0.8.11

On Fri, Nov 01, 2002 at 10:02:28PM -0700, Jason Gunthorpe wrote:
> >  It's a general problem, not at all specific to tubesock.  It happens any
> > time I'm installing a package that has dependencies that can't be satisfied
> > from stable.  I've already got tubesock/unstable installed, so I need to
> > find another package who's unstable version has unsatisfied deps from
> > unstable...
> 
> It isn't actually a problem. It is doing exactly what you asked:
> 
> apt-get -t stable install nessus/unstable
> ...
>    nessus: Depends: libnessus1 (>= 1.2.5) but 1.0.10-2 is to be installed
> 
> Which translates exactly into: 'use the stable version of all packages,
> except nessus'. So there is no bug here..
> 
> What you want is some new feature that tries to find a set of required
> packages such that the minimum number of other packages are moved to
> non-default verisons. That's actually quite algorithmically challenging :|

This is indeed challenging, but for a while we at least try a little harder for
requests like the one above or more specific like:
apt-get install nessus/unstable

This will set nessus to unstable and also all versioned dependencies it has
which are not statisfied in the default release, but are in unstable, so the
feature requested here is implemented, hence closing as done.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: