AUR web interface

Tasklist

FS#2555 - Adding package fails (untarred files need permissions standardization)

Attached to Project: AUR web interface
Opened by Tarik Koujou (tARIX) - Tuesday, 12 April 2005, 19:26 GMT
Last edited by Paul Mattal (paul) - Saturday, 11 June 2005, 04:22 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version 1.2
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The web interface drops me these lines when I try to add a package. What's wrong?

Warning: rmdir(/home/aur/unsupported/csound/csound-4.23f12gbs.11-1) [function.rmdir]: Directory not empty in /home/aur/aur/web/lib/aur.inc on line 524

Warning: rmdir(/home/aur/unsupported/csound) [function.rmdir]: Directory not empty in /home/aur/aur/web/lib/aur.inc on line 524
Could not create incoming directory: /home/aur/unsupported/csound.
(application/x-gzip)    csound.tar.gz (0.5 KiB)
(application/x-gzip)    csound.tar.gz (0.5 KiB)
This task depends upon

Closed by  Paul Mattal (paul)
Thursday, 31 August 2006, 01:42 GMT
Reason for closing:  Works for me
Additional comments about closing:  This one wasn't reproducible. We'll handle it when/if it comes up again.
Comment by Paul Mattal (paul) - Tuesday, 12 April 2005, 21:55 GMT
It appears that what's going on here is that somehow the indicated directory got created without the execute bit set for the user. I'm not sure how or why, but I'll look into this.
Comment by Paul Mattal (paul) - Thursday, 14 April 2005, 03:40 GMT
Can you attach the tar.gz for csound that you uploaded to this bug (using the Attachments tab)?

I'm speculating it's some property of that tar, but I want to see what it looks like to decide how best to handle it.

Then again, I could be wrong. But at least then I'll find that out, too.
Comment by Tarik Koujou (tARIX) - Thursday, 14 April 2005, 08:42 GMT
Hi Paul,

I uploaded two package files. they differ in the name of the included folder. Both failed. Let me know what you found out.

-tARIX
Comment by Paul Mattal (paul) - Thursday, 14 April 2005, 14:47 GMT
I see what has happened. The second package would have worked, except that the first one was uploaded first. The first package didn't have the execute bit set for the directory, so it couldn't be traversed or deleted.

So the upload of the new csound package couldn't occur properly.

There will need to be some significant new code written to avoid this kinda of bad situation in the future. I will work on that for release v1.1. In the meanwhile, due to weird permissions problems, it's not easy for me to even remove this old package directory immediately! I'll get on a solution for that ASAP.

Thanks for finding this bug! Sorry for the trouble it has caused.
Comment by Tarik Koujou (tARIX) - Thursday, 14 April 2005, 15:28 GMT
No problem at all. Thank you very much for examining what was causing the trouble.
Comment by Paul Mattal (paul) - Wednesday, 04 May 2005, 17:16 GMT
Okay, while this bug hasn't yet been fixed, I have finally removed the csound files! So you should be able to upload a new version.
Comment by Douglas Soares de Andrade (dsa) - Thursday, 10 August 2006, 12:50 GMT
Hello Paul,

Can we close this one ? I could not reproduce it here.

Loading...