[SOLVED] pkgbuild and yaourt trouble

Typz · 2015-01-06 00:04:57

Hi,

I'm trying to re-install update yaourt and pkgbuild is giving me some issues:

[user@Test package-query]$ makepkg -cs
==> Making package: package-query 1.5-2 (Tue Jan  6 01:54:16 IST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found package-query-1.5.tar.gz
==> Validating source files with md5sums...
    package-query-1.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting package-query-1.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/home/user/downloads/package-query/PKGBUILD: line 15: ./configure: Permission denied
==> ERROR: A failure occurred in build().
    Aborting...

Any ideas?

Oh and just in case i don't have something special in the mount points:
├─/tmp tmpfs tmpfs rw
├─/home /dev/sda3 ext4 rw,noatime,discard,data=ordered

Last edited by Typz (2015-01-11 20:37:43)

Trilby · 2015-01-06 00:29:31

run `makepkg -o`, then post the output of the following:

ls -l src/package-query-1.5/configure

ewaller · 2015-01-06 03:40:32

Moving to AUR issues

Typz · 2015-01-06 08:27:48

Trilby wrote:

run `makepkg -o`, then post the output of the following:
ls -l src/package-query-1.5/configure

[user@Test package-query]$ makepkg -o
==> Making package: package-query 1.5-2 (Tue Jan  6 10:26:12 IST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found package-query-1.5.tar.gz
==> Validating source files with md5sums...
    package-query-1.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting package-query-1.5.tar.gz with bsdtar
==> Sources are ready.
[user@Test package-query]$ ls -l src/package-query-1.5/configure
-rw-r----- 1 js js 514014 Dec 23 13:20 src/package-query-1.5/configure

Trilby · 2015-01-06 12:55:25

That's odd. The configure script is not executable - but it is in the source I just grabbed with makepkg.

You could make it as executable yourself, then continue, but if it were me I'd want to figure out how that is happening.

To do the shortcut fix, you should be able to do the following:

makepkg -o # unless you just did
chmod 777 src/package-query-1.5/configure
makepkg -ef

To start to tract down the underlying issue I'd want to know more about the mount points. You posted some info above - what comand was that from? Can you post the output of `mount`?

EDIT: and what is your user name? Are you editting it out of your posts? In the first post, the path indicates that your user name is "user", but the ownership of the configure file is "js:js" who/what is js? Can you also post the output of `umask`?

Last edited by Trilby (2015-01-06 12:57:47)

Typz · 2015-01-09 17:16:51

Trilby wrote:

That's odd. The configure script is not executable - but it is in the source I just grabbed with makepkg.
You could make it as executable yourself, then continue, but if it were me I'd want to figure out how that is happening.
To do the shortcut fix, you should be able to do the following:
makepkg -o # unless you just did
chmod 777 src/package-query-1.5/configure
makepkg -ef
To start to tract down the underlying issue I'd want to know more about the mount points. You posted some info above - what comand was that from? Can you post the output of `mount`?
EDIT: and what is your user name? Are you editting it out of your posts? In the first post, the path indicates that your user name is "user", but the ownership of the configure file is "js:js" who/what is js? Can you also post the output of `umask`?

Sorry for no updating but i had little time, i really do want to know the cause and not just fix the issue...

but just for the record the quick fix didn't work:

[user@Test package-query]$ makepkg -o
==> Making package: package-query 1.5-2 (Fri Jan  9 19:08:31 IST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found package-query-1.5.tar.gz
==> Validating source files with md5sums...
    package-query-1.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting package-query-1.5.tar.gz with bsdtar
==> Sources are ready.
[user@test package-query]$ chmod 777 src/package-query-1.5/configure
[user@test package-query]$ makepkg -ef
==> Making package: package-query 1.5-2 (Fri Jan  9 19:08:42 IST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/home/user/downloads/package-query/PKGBUILD: line 15: ./configure: Permission denied
==> ERROR: A failure occurred in build().
    Aborting...

The output is from a mount command i found while googling the issue (can't remember the name sry).
here is the output of mount:

[user@test package-query]$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8193260k,nr_inodes=2048315,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda2 on / type ext4 (rw,noatime,discard,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/sda3 on /home type ext4 (rw,noatime,discard,data=ordered)
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sdb4 on /mnt/share type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdc2 on /mnt/backup type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1639204k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Regarding the user yes i have a user called 'js' but i also have a user called user for testing.

[user@Test package-query]$ umask
0022

Trilby · 2015-01-09 17:23:32

Typz wrote:

Regarding the user yes i have a user called 'js' but i also have a user called user for testing.

All the commands you've presented in this thread were run by 'user' under the home directory of 'user'. How are these files owned by js? That is the problem. User 'user' can't write into directories or files owned by js.

The only way I can think of for this to happen is if you created that directory structure as 'js' in under the home directory of 'js' then as root, moved or copied the directory to the user 'user'.

EDIT: no, scratch that - that might explain the ownership, but not permission differences.

As a very basic first step in narrowing this down, try the following:

cd /tmp
mkdir pq
cd pq
wget https://aur.archlinux.org/packages/pa/package-query/PKGBUILD
makepkg

Does this work? If it does, try the same but in a new directory in your user's home directory:

cd
mkdir pq
cd pq
wget ...

Last edited by Trilby (2015-01-09 17:31:23)

Typz · 2015-01-11 20:37:22

Trilby wrote:

Typz wrote:
Regarding the user yes i have a user called 'js' but i also have a user called user for testing.
All the commands you've presented in this thread were run by 'user' under the home directory of 'user'. How are these files owned by js? That is the problem. User 'user' can't write into directories or files owned by js.
The only way I can think of for this to happen is if you created that directory structure as 'js' in under the home directory of 'js' then as root, moved or copied the directory to the user 'user'.
EDIT: no, scratch that - that might explain the ownership, but not permission differences.
As a very basic first step in narrowing this down, try the following:
cd /tmp
mkdir pq
cd pq
wget https://aur.archlinux.org/packages/pa/package-query/PKGBUILD
makepkg
Does this work? If it does, try the same but in a new directory in your user's home directory:
cd
mkdir pq
cd pq
wget ...

That worked!(both) Thanks a lot

Arch Linux

#1 2015-01-06 00:04:57

[SOLVED] pkgbuild and yaourt trouble

#2 2015-01-06 00:29:31

Re: [SOLVED] pkgbuild and yaourt trouble

#3 2015-01-06 03:40:32

Re: [SOLVED] pkgbuild and yaourt trouble

#4 2015-01-06 08:27:48

Re: [SOLVED] pkgbuild and yaourt trouble

#5 2015-01-06 12:55:25

Re: [SOLVED] pkgbuild and yaourt trouble

#6 2015-01-09 17:16:51

Re: [SOLVED] pkgbuild and yaourt trouble

#7 2015-01-09 17:23:32

Re: [SOLVED] pkgbuild and yaourt trouble

#8 2015-01-11 20:37:22

Re: [SOLVED] pkgbuild and yaourt trouble

Board footer