On Thu, Jul 24 2014, Neil Bothwick wrote:
> On Wed, 23 Jul 2014 09:24:44 -0400, gottl...@nyu.edu wrote:
>
>> I had mistakenly thought this would update all packages not at the
>> latest version (subject to package.accept_keywords, package.mask, ...).
>
> It only updates runtime dependencies, you need --with-bdeps=y to update
> all dependencies.
Thank you and michael for this point.
> However, the default is no for a good reason, there's no need to
> update build time deps once the package is installed.
I see.
>> I now realize that it only does this for the packages in world and then
>> follows the dependency tree. So if package A in world is up to date, A
>> depends of B, and a new version of B appears, B will not be updated.
>>
>> As a result eix-test-obsolete finds that I have packages installed that
>> are no longer in the database.
>
> That shouldn't happen. If an installed package is removed for the tree,
> portage should either install the highest version that matches your
> settings or print a warning.
I am not sure if you consider the message from eix-test-obsolete
as the message from portage.
eix-test-obsolete prints (among other things)
Installed packages with a version not in the database (or masked):
[lines omitted]
[U] virtual/perl-CPAN-Meta-Requirements (2.125.0@10/29/2013 -> (~)2.125.0-r1):
Virtual for CPAN-Meta-Requirements
eix virtual/perl-CPAN-Meta-Requirements prints
[U] virtual/perl-CPAN-Meta-Requirements
Available versions: 2.122.0-r2 (~)2.125.0-r1
Installed versions: 2.125.0(09:25:35 PM 10/29/2013)
/etc/portage/package.accept_keywords/goingstable contains
~virtual/perl-CPAN-Meta-Requirements-2.125.0
I thought this would be updated to 2.125.0-r1 but
my update world (withOUT bdeps=y) says nothing to merge
and prints no error or warning
>> I could do
>>
>> emerge --update the-2-dozen-such-packages
>>
>> Is that wise?
>
> No, as it will add them to world (this behaviour of -u appears to vary
> depending on portage version, wind direction and sunspot activity). Use
> --oneshot.
Understood. And I remember the discussion on the list about the meaning
of -u.
emerge -u -1 virtual/perl-CPAN-Meta-Requirements
reveals what is probably my real problem
[ebuild U ~] virtual/perl-CPAN-Meta-Requirements-2.125.0-r1 [2.125.0] 0 kB
[nomerge ] perl-core/CPAN-Meta-Requirements-2.125.0
[ebuild UD ] virtual/perl-version-0.990.100 [0.990.400] 0 kB
[ebuild UD ] perl-core/version-0.990.100 [0.990.400] 105 kB
upgrading virtual/perl-CPAN-Meta-Requirements entails downgrading two
other perl packages (or bumping their version in goingstable, which I
remember you suggest).
I am going away for 2 weeks, but when I return I will look carefully at
the (mostly perl) files that eix-test-obsolete complains about. I am
hopeful that armed with emerge -u -1 and/or --with-bdeps=y I can remove
the warnings from eix-test-obsolete.
Once again, thank you both,
allan
