Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44196 - makepkg --source creates .SRC file with permissions of 777 instead of required 755

Attached to Project: Arch Linux
Opened by Ivan P (Soukyuu) - Sunday, 15 March 2015, 16:54 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 15 March 2015, 17:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
adopted my first AUR package today, so maybe this is supposed to be like this and I am missing a step...
If no .SRC file was generated, one is generated by makepkg --source

The resulted .tar.gz can not be uploaded to AUR because of:
"Error - all files must have permissions of 644 or 755"

Upon inspection, the .SRC file has permissions set to 777 instead of 755

Steps to reproduce:
1. run makepkg --source on a package without an existing .SRC
2. attempt to upload to AUR
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 15 March 2015, 17:39 GMT
Reason for closing:  Not a bug
Additional comments about closing:  User error.
Comment by Dave Reisner (falconindy) - Sunday, 15 March 2015, 17:03 GMT
What is .SRC ? Do you mean .SRCINFO? If that's the case, your instructions are insufficient to reproduce the bug you're reporting.

$ ABSROOT=. abs core/systemd
[...]
$ cd core/systemd
$ makepkg --source
$ cat .SRCINFO
cat: .SRCINFO: No such file or directory
$ makepkg --source
[...]
$ bsdtar tvf systemd-218-2.src.tar.gz systemd/.SRCINFO
-rw-r--r-- 0 root root 5369 Mar 15 13:05 systemd/.SRCINFO
Comment by Ivan P (Soukyuu) - Sunday, 15 March 2015, 17:04 GMT
Yes, sorry, I meant .SRCINFO
Comment by Dave Reisner (falconindy) - Sunday, 15 March 2015, 17:07 GMT
See earlier comment (I've edited it). There were bugs in makepkg 4.2.0 which did this wrongly in the case of non-standard umask, but you haven't mentioned any versions here or much else about your environment...
Comment by Ivan P (Soukyuu) - Sunday, 15 March 2015, 17:20 GMT
makepkg (pacman) is 4.2.1

I'm doing this in my ~/aur/package/ subdirectory, filesystem is ext4

$ tar xvf deadbeef-git.tar.gz
$ ls -la
total 20
drwxr-xr-x 2 azure azure 4096 Mar 15 18:12 .
drwxr-xr-x 3 azure azure 4096 Mar 15 18:14 ..
-rwxr-xr-x 1 azure azure 192 Oct 22 2010 deadbeef.install
-rwxr-xr-x 1 azure azure 2313 Mar 15 17:34 PKGBUILD
-rw-r--r-- 1 azure azure 2175 Mar 15 18:12 .SRCINFO

This doesn't get accepted by the AUR website, but after doing

$ chmod 755 .SRCINFO
$ ls -la
total 20
drwxr-xr-x 2 azure azure 4096 Mar 15 18:12 .
drwxr-xr-x 3 azure azure 4096 Mar 15 18:14 ..
-rwxr-xr-x 1 azure azure 192 Oct 22 2010 deadbeef.install
-rwxr-xr-x 1 azure azure 2313 Mar 15 17:34 PKGBUILD
-rwxr-xr-x 1 azure azure 2175 Mar 15 18:12 .SRCINFO
$ makepkg --source

it does get accepted by the AUR website uploader.

edit: which is weird I guess, since -rw-r--r-- should be valid (644)?
Comment by Dave Reisner (falconindy) - Sunday, 15 March 2015, 17:25 GMT
Your initial report says that .SRCINFO is created with 777 perms, but now you're saying that a .SRCINFO with mode 644 isn't accepted by the AUR. If that's really the case, then it's a bug in the AUR (but I think there's a simpler explanation).
Comment by Ivan P (Soukyuu) - Sunday, 15 March 2015, 17:36 GMT
Well, this is embarassing. It seems that somehow the permission of the PKGBUILD file got changed when I edited it, not the .SRCINFO.
And I just assumed I had to change all of them to 755, when it should have been 644 for all of them .

Everything works as expected, sorry for wasting your time.

Loading...