| 1 |
On Monday 09 Sep 2013 09:44:01 Tanstaafl wrote: |
| 2 |
> Wow... just noticed an update is available which, for me, means it has |
| 3 |
> been stabilized (at least on amd64)... |
| 4 |
|
| 5 |
--->8 |
| 6 |
|
| 7 |
> Now to wait a few days to see if there is any breakage to report (not |
| 8 |
> worried about it really, though, since it has actually gotten a ton of |
| 9 |
> testing over the last year or two)... |
| 10 |
|
| 11 |
...and the first time I use it it falls over! Portage was the only thing |
| 12 |
updated yesterday, so nothing else changed at the same time. |
| 13 |
|
| 14 |
# emerge --sync |
| 15 |
>>> Synchronization of repository 'gentoo' located in '/usr/portage'... |
| 16 |
>>> Starting rsync with rsync://192.168.2.2/gentoo-portage... |
| 17 |
>>> Checking server timestamp ... |
| 18 |
receiving incremental file list |
| 19 |
rsync: mkstemp "/var/tmp/.tmp8KJSYc.AHSsPH" failed: Permission denied (13) |
| 20 |
|
| 21 |
I checked it wasn't anything I'd set in make.conf by stripping out everything |
| 22 |
but the original few lines from system installation, so I'm sure I hadn't set |
| 23 |
any odd paths. |
| 24 |
|
| 25 |
So for the moment I've masked out =sys-apps/portage-2.2.1 and reverted to |
| 26 |
2.1.12.2. Now I'm getting some odd USE flag conflicts, which I suppose won't be |
| 27 |
related; I'll work on sorting that out. |
| 28 |
|
| 29 |
I also tried syncing a 32-bit chroot Gentoo system and that worked fine. That |
| 30 |
system has always had: |
| 31 |
|
| 32 |
# grep portage /etc/portage/package.keywords |
| 33 |
<sys-apps/portage-9999 ** |
| 34 |
|
| 35 |
Trust someone to find a problem! :-( |
| 36 |
|
| 37 |
Is it working for you, Dale? :-) |
| 38 |
|
| 39 |
-- |
| 40 |
Regards, |
| 41 |
Peter |
Archives