[solved] sync fails: rsync delete_file permission denied

Message

avx · Post by **avx** » Tue Jan 13, 2009 3:30 pm

While running

emerge --sync

the process fails, cause rsync produces a lot of line like the following

Code: Select all

rsync: delete_file: unlink(net-libs/icee/files/icee-1.3.0-maverick-fix.patch) failed: Permission denied (13)

portage-2.2_rc21

Resyncing doesn't solve it, yet. Someone with the same problem?

Kosmas · Post by **Kosmas** » Tue Jan 13, 2009 6:11 pm

Same here...

Must be some kind of problem with the permissions of the files of the mirror.

Hope someone sees it and resolves it.

Mirror guys are you listening??? knock knock...

gcasillo · Post by **gcasillo** » Tue Jan 13, 2009 7:42 pm

Same problem here.

smlgbl · Post by **smlgbl** » Tue Jan 13, 2009 9:58 pm

You can still sync...
If you do an update to portage afterwards, it will be downgraded. So probably a portage error.

shrimp123 · Post by **shrimp123** » Wed Jan 14, 2009 12:52 am

mask the latest portage u have
downgrade to the previous version

i did the above and all is fine.

Grahammm · Post by **Grahammm** » Wed Jan 14, 2009 5:00 am

I noticed that some files/directories in /usr/portage were owned by 'portage portage' and others by 'root root'. Running `chown -R portage.portage /usr/portage` fixed the problem for me and then I was able to sync.

pappy_mcfae · Post by **pappy_mcfae** » Wed Jan 14, 2009 5:54 am

Big bug in portage there. Downgrading portage to 2.2_rc20 did the trick for me...but now portage wants to upgrade itself back to 2.2_rc21. What a drag.

EDIT: The above method also works, and no need to mess with portage. /EDIT

Blessed be!
Pappy

PurpleSkunk · Post by **PurpleSkunk** » Wed Jan 14, 2009 7:13 am

Grahammm wrote:I noticed that some files/directories in /usr/portage were owned by 'portage portage' and others by 'root root'. Running `chown -R portage.portage /usr/portage` fixed the problem for me and then I was able to sync.

Thanks, it did the trick very well.

Elbar Thera · Post by **Elbar Thera** » Wed Jan 14, 2009 8:06 am

pappy_mcfae wrote:...but now portage wants to upgrade itself back to 2.2_rc21. What a drag.

had the same problem...the thing is you have probably (at least i had) something like sys-apps/portage in your unmask file.
replace that with <sys-apps/portage-2.2_rc21

Live long and prosper,
Elbar

pappy_mcfae · Post by **pappy_mcfae** » Wed Jan 14, 2009 8:58 am

Good point. Since the chown command seemed to take care of it, it's pretty anticlimactic at this point. However, I remember having to unmask portage-2.2 it so I didn't get portage-2.16, or something like that. Makes sense now.

Blessed be!
Pappy

Nijinski · Post by **Nijinski** » Wed Jan 14, 2009 12:27 pm

This is showing up on my machine as well, wonder if there was any testing done on this version of portage ?

Timbers2k · Post by **Timbers2k** » Wed Jan 14, 2009 2:29 pm

Wow! This paniced me. I just changed my root partition to ext4. When I tried to sync and saw this I thought the file system was hosed! Thanks for the easy fix.

Nephilim666 · Post by **Nephilim666** » Wed Jan 14, 2009 3:24 pm

They oviously released

Code: Select all

sys-apps/portage-2.2_rc22

which fixes the bug.

Silentsand74 · Post by **Silentsand74** » Wed Jan 14, 2009 3:47 pm

Nephilim666 wrote:They oviously released
Code: Select all
sys-apps/portage-2.2_rc22
which fixes the bug.

-

Because mentioned package isn't listed on gentoo-portage.com.

Fixed the link, BBCode is not quite clever enough to figure out implicit protocols. -- desultory

Nephilim666 · Post by **Nephilim666** » Wed Jan 14, 2009 5:28 pm

gentoo-portage.com is not an official page. On Gentoo Packages things are up-to-date.

andorreJr · Post by **andorreJr** » Wed Jan 14, 2009 5:58 pm

Same problem here with portage-2.1.6.5
Upgrade to portage-2.1.6.6 fix this.

avx · Post by **avx** » Wed Jan 14, 2009 8:54 pm

Marking this [solved], since fixes are available and seem to work.