FS#43381 - [AUR 4.0.0] remote: error: package is blacklisted:

Attached to Project: AUR web interface
Opened by UnicornDarkness (Xorg) - Thursday, 08 January 2015, 21:15 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 09 January 2015, 08:53 GMT
Task Type Bug Report
Category PKGBUILD Parser
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.5.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I don't understand, I can't push.

Package python2-mmkeys is not in officials repo, so why blacklisted ?
You can find PKGBUILD on AUR v3 (https://aur.archlinux.org/packages/py/python2-mmkeys/PKGBUILD).
Renaming variable _pkgbase in another don't solve this problem.
   aur-4.0.0-blacklist.txt (0.6 KiB)
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 09 January 2015, 08:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 5816cc7 (aurblup: Do not blacklist provides, 2015-01-09).
Comment by Lukas Fleischer (lfleischer) - Thursday, 08 January 2015, 21:26 GMT
sonata in [extra] already provides python2-mmkeys which is why it is on the package blacklist.
Comment by UnicornDarkness (Xorg) - Thursday, 08 January 2015, 21:36 GMT
Yes, sonata provides python2-mmkeys, but doesn't replace.
python2-mmkeys contains only one library, sonata is more powerfull.
python2-mmkeys can be a part of sonata, but it is not. For instance, I need library mmskeys.so which is provided both sonata and python2-mmkeys, but I prefer use python2-mmkeys because I don't use sonata.

I understand, but the same package works on AUR v3. I think it will work on AUR v4 too, I don't attempt to replace an official package.
Comment by Lukas Fleischer (lfleischer) - Thursday, 08 January 2015, 21:49 GMT
So you are packaging python2-mmkeys only because you want to save some disk space? I am on the fence on whether we should loosen the blacklist and drop provides. That said, provides have been added to the blacklist for a long time, since commit ddc5435 (Add packages' provides and replaces to the blacklist in aurblup., 2011-02-08). However, the blacklist is only queried when you submit a *new* package -- see 2e1ce86 (Reject blacklisted packages on initial submission only., 2011-02-25) -- which is why you don't see the error message when using AUR 3.0.0. It is not a regression in 4.0.0.
Comment by UnicornDarkness (Xorg) - Thursday, 08 January 2015, 22:10 GMT
Oh yes, the origin of this story is long.

I've installed Exaile (from AUR), a music player. To use my media keys (on keyboard), I need to enable plugin XKeys, which depends on library mmkeys.so.
On AUR, I have found a package called python2-mmkeys (which provides only mmkeys.so), but it was orphain, so that is why I've adopted it.
Directly install sonata has no sense for me.

I understand what you say. I thought it was a regression, so if it is not, I will not upload python2-mmkeys on AUR v4.

I'm sorry for this false bug report.
Comment by UnicornDarkness (Xorg) - Friday, 09 January 2015, 06:39 GMT
Ok, I think it will be great, when a package is blacklisted, than we can't do a 'setup-repo' and a 'git clone'.
Comment by Lukas Fleischer (lfleischer) - Friday, 09 January 2015, 08:33 GMT
No need to be sorry. It is not a regression but after discussion with some other TUs and devs, we came to the conclusion that provides should not be blacklisted, so your bug report is valid :) I am going to prepare a patch soon that will allow you to upload python2-mmkeys to the AUR.

Checking the blacklist on `setup-repo` or `git clone`, however, does not work, since we do not know the package names at that point in time (package names and package base may differ).
Comment by UnicornDarkness (Xorg) - Friday, 09 January 2015, 14:16 GMT
Your patch works fine.

I understand better mechanism of blacklist. You really do good job. ;)

Loading...