[arch-general] [makepkg] Permission denied on pkg/ directory
I’ve been porting my old PKGBUILDs to the 4.1 format for VCS packages, and for some reason I keep getting errors building the package, with the pkg/ directory being created with 000 (d---------) permissions. My umask isn’t malformed as I can create directories and files just fine, and if I chmod the directory and re-run makepkg, it seems to lock the directory. Is this a bug, or a new feature of 4.1? Or have I misconfigured something somewhere? I did a diff of the configuration files when 4.1 was released so they should be up-to-date.
On Wed, Apr 10, 2013 at 04:38:42PM +1000, Robbie Smith wrote:
I’ve been porting my old PKGBUILDs to the 4.1 format for VCS packages, and for some reason I keep getting errors building the package, with the pkg/ directory being created with 000 (d---------) permissions. My umask isn’t malformed as I can create directories and files just fine, and if I chmod the directory and re-run makepkg, it seems to lock the directory.
Is this a bug, or a new feature of 4.1? Or have I misconfigured something somewhere? I did a diff of the configuration files when 4.1 was released so they should be up-to-date.
Stuff in the build() function should not be touching the $pkgdir, that should all happen in the package() function. This is to somewhat force people to use package functions and not put everything in the build function. Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
On 10/04/13 16:46, William Giokas wrote:
On Wed, Apr 10, 2013 at 04:38:42PM +1000, Robbie Smith wrote:
I’ve been porting my old PKGBUILDs to the 4.1 format for VCS packages, and for some reason I keep getting errors building the package, with the pkg/ directory being created with 000 (d---------) permissions. My umask isn’t malformed as I can create directories and files just fine, and if I chmod the directory and re-run makepkg, it seems to lock the directory.
Is this a bug, or a new feature of 4.1? Or have I misconfigured something somewhere? I did a diff of the configuration files when 4.1 was released so they should be up-to-date.
Stuff in the build() function should not be touching the $pkgdir, that should all happen in the package() function. This is to somewhat force people to use package functions and not put everything in the build function.
Thanks,
Ah I see what I was doing wrong. build() had a `make install` invocation. Cheers.
participants (2)
-
Robbie Smith
-
William Giokas