| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Graham Murray wrote: |
| 5 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
| 6 |
> |
| 7 |
>> unmerge the blocking packages, coldplug, pam-login and ant-tasks. This |
| 8 |
>> usually happens because the functionality the package provides is now |
| 9 |
>> handled by something else that emerge world needs to bring it. This is |
| 10 |
>> certainly the case with udev now handling coldplug's job. |
| 11 |
> |
| 12 |
> Which begs the question that if attempting to rebuild all the packages |
| 13 |
> in a working system indicates blockers, how did the system get in that |
| 14 |
> state and why did portage not indicate a blockage when the incompatible |
| 15 |
> packages were installed or upgraded? |
| 16 |
|
| 17 |
Just because they are conflicting now doesn't mean that there was |
| 18 |
conflicting packages before. Upgrades do happen, and things do change ;) |
| 19 |
Every time you sync and get a new ebuild, you are generally getting a |
| 20 |
new version of the package (assuming there is a new version available). |
| 21 |
|
| 22 |
- -- |
| 23 |
Jeremy Olexa |
| 24 |
(olexa@××××××.edu) |
| 25 |
Office: EE/CS 1-201 |
| 26 |
CS/IT Systems Staff |
| 27 |
University of Minnesota |
| 28 |
|
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.4.3 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iD8DBQFEZIqmFN7pD9kMi/URAkfTAJ4vYtxZTPGTYufzQyWJaog5dk+zBwCfVtPQ |
| 34 |
WitkwasBfNu1qMKQTpTsXQc= |
| 35 |
=UqNp |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-user@g.o mailing list |
Archives