FS#45410 - [AUR4] TUs can't submit blacklisted packages

Attached to Project: AUR web interface
Opened by Kyle Keen (keenerd) - Monday, 22 June 2015, 06:32 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 25 June 2015, 07:33 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.0-rc3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Attempting to move a package from the repos to the AUR fails due to blacklisting. Sample error:

[master (root-commit) 4f4da71] Initial import
3 files changed, 104 insertions(+)
create mode 100644 .SRCINFO
create mode 100644 PKGBUILD
create mode 100644 friend-function.patch
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.85 KiB | 0 bytes/s, done.
Total 5 (delta 0), reused 0 (delta 0)
remote: error: package is blacklisted: yap
remote: error: hook declined to update refs/heads/master
Toaur@aur4.archlinux.org/yap.git"> ssh://aur@aur4.archlinux.org/yap.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'ssh://aur@aur4.archlinux.org/yap.git'
Import finished
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Thursday, 25 June 2015, 07:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 4.0.0-rc6.
Comment by Johannes Löthberg (demize) - Monday, 22 June 2015, 07:08 GMT
Hmm, I'm not sure if there's any way to find out which key was used to auth with SSH inside the hook unless OpenSSH merges one of the patches to add an env variable for it.
Comment by Johannes Löthberg (demize) - Monday, 22 June 2015, 07:15 GMT
Actually, checking git-serve.py it seems we set AUR_USER already, so scratch that.
Comment by Pablo Lezaeta (Jristz) - Wednesday, 24 June 2015, 19:10 GMT
Or why not have a master list and make only accesible to TU and Dev, a tu could simply ctl+f package and then remove it from the list.

Another option could have a list available coping from community database and if a package is removed from community then is removed automaticaly from the blacklist too.
Comment by Kyle Keen (keenerd) - Wednesday, 24 June 2015, 19:18 GMT
This was fixed on the 23rd.

Loading...