| 1 |
Ok. All devs, please use 2.0.51. PLEASE provide bugs with |
| 2 |
any and all issues or needs reguarding portage and repoman. |
| 3 |
We can't fix it if we don't know it's broken. |
| 4 |
|
| 5 |
2.0.51_pre13 has completed two unaided/uninterupted |
| 6 |
rounds of catalyst stage building (meaning 8 stages) |
| 7 |
normally signalling readiness for ~arch. There are a |
| 8 |
couple of features still to be added, which will be |
| 9 |
in and ~arch in the near future. |
| 10 |
|
| 11 |
Easy way to be using the developer portages: |
| 12 |
echo "sys-apps/portage" >> /etc/portage/package.mask |
| 13 |
echo "sys-apps/portage" >> /etc/portage/package.keywords |
| 14 |
|
| 15 |
Key points that need to be clear to everyone: |
| 16 |
|
| 17 |
Portage is very loud during rsync updates right now as the |
| 18 |
cache has changed for 2.0.51 and will change again some time |
| 19 |
after 2.0.51 has become stable. The corruption messages are |
| 20 |
normal for the time being, but I will get the cache updated |
| 21 |
and the messages will go away within a week or two. AFTER |
| 22 |
that week or two, all portages prior to 2.0.50-r7 will start |
| 23 |
to complain as they aren't capable of handling the new cache. |
| 24 |
I expect many users to post bugs or concerns about that due |
| 25 |
to the fact that many people ignore the messages portage |
| 26 |
prints out about updating portage (which should be done as |
| 27 |
often as necessary to never see that message). |
| 28 |
|
| 29 |
/var/cache/edb/virtuals is going away. It's obsoleted. Portage |
| 30 |
now calculates the virtuals based on packages installed in the |
| 31 |
database. Do not do anything with the old file. Delete it, but |
| 32 |
do not copy it or suggest anyone copy it. It is obsoleted. It |
| 33 |
is obsoleted. /etc/portage/virtuals can be used to add user |
| 34 |
modifications but ONLY user modifications. The full file is |
| 35 |
obsoleted. People have already done what I'm saying not to, |
| 36 |
so make sure everyone knows it's obsoleted. |
| 37 |
|
| 38 |
/var/cache/edb/world has moved. It's located in portage's new |
| 39 |
FHS compliant state directory. /var/lib/portage. There may or |
| 40 |
may not be a symlink from /etc/portage/sets/world to that file |
| 41 |
as it seems to confuse people, and getting the symlink to stick |
| 42 |
around is challenging for some reason. The directory is created |
| 43 |
and scanned for bad files which are then deleted. Nothing is |
| 44 |
allowed to be in that directory other than portage:portage |
| 45 |
owned and o-rwx files. Everything else should be deleted when |
| 46 |
portage runs as root. /usr/lib/portage/bin/regenworld can fix |
| 47 |
most any worldfile deletion. You can use 'emerge depclean -p' |
| 48 |
and 'emerge -uD world -p' to work on the missing parts and |
| 49 |
the cruft. |
| 50 |
|
| 51 |
--NJ |
Archives