| 1 |
On Thu, Jul 24 2014, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Wed, 23 Jul 2014 09:24:44 -0400, gottlieb@×××.edu wrote: |
| 4 |
> |
| 5 |
>> I had mistakenly thought this would update all packages not at the |
| 6 |
>> latest version (subject to package.accept_keywords, package.mask, ...). |
| 7 |
> |
| 8 |
> It only updates runtime dependencies, you need --with-bdeps=y to update |
| 9 |
> all dependencies. |
| 10 |
|
| 11 |
Thank you and michael for this point. |
| 12 |
|
| 13 |
> However, the default is no for a good reason, there's no need to |
| 14 |
> update build time deps once the package is installed. |
| 15 |
|
| 16 |
I see. |
| 17 |
|
| 18 |
>> I now realize that it only does this for the packages in world and then |
| 19 |
>> follows the dependency tree. So if package A in world is up to date, A |
| 20 |
>> depends of B, and a new version of B appears, B will not be updated. |
| 21 |
>> |
| 22 |
>> As a result eix-test-obsolete finds that I have packages installed that |
| 23 |
>> are no longer in the database. |
| 24 |
> |
| 25 |
> That shouldn't happen. If an installed package is removed for the tree, |
| 26 |
> portage should either install the highest version that matches your |
| 27 |
> settings or print a warning. |
| 28 |
|
| 29 |
I am not sure if you consider the message from eix-test-obsolete |
| 30 |
as the message from portage. |
| 31 |
|
| 32 |
eix-test-obsolete prints (among other things) |
| 33 |
|
| 34 |
Installed packages with a version not in the database (or masked): |
| 35 |
[lines omitted] |
| 36 |
[U] virtual/perl-CPAN-Meta-Requirements (2.125.0@10/29/2013 -> (~)2.125.0-r1): Virtual for CPAN-Meta-Requirements |
| 37 |
|
| 38 |
eix virtual/perl-CPAN-Meta-Requirements prints |
| 39 |
|
| 40 |
[U] virtual/perl-CPAN-Meta-Requirements |
| 41 |
Available versions: 2.122.0-r2 (~)2.125.0-r1 |
| 42 |
Installed versions: 2.125.0(09:25:35 PM 10/29/2013) |
| 43 |
|
| 44 |
/etc/portage/package.accept_keywords/goingstable contains |
| 45 |
~virtual/perl-CPAN-Meta-Requirements-2.125.0 |
| 46 |
|
| 47 |
I thought this would be updated to 2.125.0-r1 but |
| 48 |
my update world (withOUT bdeps=y) says nothing to merge |
| 49 |
and prints no error or warning |
| 50 |
|
| 51 |
>> I could do |
| 52 |
>> |
| 53 |
>> emerge --update the-2-dozen-such-packages |
| 54 |
>> |
| 55 |
>> Is that wise? |
| 56 |
> |
| 57 |
> No, as it will add them to world (this behaviour of -u appears to vary |
| 58 |
> depending on portage version, wind direction and sunspot activity). Use |
| 59 |
> --oneshot. |
| 60 |
|
| 61 |
Understood. And I remember the discussion on the list about the meaning |
| 62 |
of -u. |
| 63 |
|
| 64 |
emerge -u -1 virtual/perl-CPAN-Meta-Requirements |
| 65 |
reveals what is probably my real problem |
| 66 |
|
| 67 |
[ebuild U ~] virtual/perl-CPAN-Meta-Requirements-2.125.0-r1 [2.125.0] 0 kB |
| 68 |
[nomerge ] perl-core/CPAN-Meta-Requirements-2.125.0 |
| 69 |
[ebuild UD ] virtual/perl-version-0.990.100 [0.990.400] 0 kB |
| 70 |
[ebuild UD ] perl-core/version-0.990.100 [0.990.400] 105 kB |
| 71 |
|
| 72 |
upgrading virtual/perl-CPAN-Meta-Requirements entails downgrading two |
| 73 |
other perl packages (or bumping their version in goingstable, which I |
| 74 |
remember you suggest). |
| 75 |
|
| 76 |
I am going away for 2 weeks, but when I return I will look carefully at |
| 77 |
the (mostly perl) files that eix-test-obsolete complains about. I am |
| 78 |
hopeful that armed with emerge -u -1 and/or --with-bdeps=y I can remove |
| 79 |
the warnings from eix-test-obsolete. |
| 80 |
|
| 81 |
Once again, thank you both, |
| 82 |
allan |
Archives