El Thursday 19 June 2008 15:51:55 Daniel Burrows escribió:
> On Thu, Jun 19, 2008 at 06:12:36AM +0200, Noel David Torres Taño
<[EMAIL PROTECTED]> was heard to say:
> > El Thursday 19 June 2008 04:38:25 Daniel Burrows escribió:
> > > I need the *specific* package that should be triggering the fam
> > > installation (again assuming you mean fam). i.e., which package did
> > > you upgrade that didn't recommend fam in the past and now does, and
> > > what are its versions? (or what new package was installed that
> > > requires fam -- but I assumed that debian-reference-en didn't recommend
> > > fam, and it looks like I was right) Yes, I *could* trawl the
> > > repository and
> > > snapshots.debian.org for the 43 packages you list above and see which
> > > one got a new dependency on fam recently, but I thought that since you
> > > reported the bug it would be more efficient to ask you. :-)
> > >
> > > It might also be helpful if I could have access to the output of
> > > aptitude-create-state-bundle for debugging purposes.
> > >
> > > Thanks,
> > > Daniel
> >
> > Obviously the pakage that triggers the nonfulfilled recommendation is
> > libfam0, which was upgraded from 2.7.0-13.2 to 2.7.0-13.3
>
> Yeah, a simple search for packages recommending fam would have gotten
> me that. Sorry, I should have done that instead of writing the email
> above. My mistake.
No, it isn't. Do not worry about that.
>
> > P.S. What did you say about "didn't recommend fam in the past and now
> > does"?
>
> When you're upgrading packages, only *new* recommendations should be
> installed. So I was looking for a package where version N did not
> recommend fam, version M recommended fam, and you had upgraded from
> version N to version M. But in fact, I have an old .deb for libfam0
> lying around, and both versions of it recommend fam. So I don't think
> that fam *should* be installed in this situation.
>
> Daniel
Well, maybe the bug is in the documentation, instead. It reads
-r, --with-recommends
Treat recommendations as dependencies when installing new packages
(this overrides settings in /etc/apt/apt.conf and ~/.aptitude/config).
Maybe it is not clear enough that the option applies to new packages being
installed, instead of applying to the moment in which aptitude creates the
list of packages to install. That was what I thought.
My suggestion:
-r, --with-recommends
Treat recommendations as dependencies. This will work only for
installing new packages (this overrides settings in /etc/apt/apt.conf and
~/.aptitude/config), and does not work for packages being upgraded.
Thanks for everything
Noel
er Envite
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
