On 04/06/2018 07:12 AM, LoneVVolf wrote:

Although SRCINFO does have pkgbase=llvm35 in it, that's not in the PKGBUILD. I doubt that's the cause of the issue, but try adding pkgbase explicitly to PKGBUILD.

Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg sets it from the first element of pkgname, and this is why the .SRCINFO still shows it.

I think AUR uses a blacklist to prevent duplicates with offical repos, maybe that blacklist needs updating ?

The blacklist currently contains llvm35, which I think is because it is erroring when running updates. ``` [eschwartz@luna ~]$ ./aurblup.py inserting update for libreoffice-still-pa-in (provides: libreoffice-pa-IN) Traceback (most recent call last): File "./aurblup.py", line 55, in <module> main() File "./aurblup.py", line 44, in main "VALUES (?, ?, ?)", [pkg, repo, provides]) File "/usr/lib/python3.6/site-packages/aurweb-4.6.0-py3.6.egg/aurweb/db.py", line 43, in execute File "/usr/lib/python3.6/site-packages/mysql/connector/cursor.py", line 561, in execute self._handle_result(self._connection.cmd_query(stmt)) File "/usr/lib/python3.6/site-packages/mysql/connector/connection.py", line 514, in cmd_query result = self._handle_result(self._send_cmd(ServerCmd.QUERY, query)) File "/usr/lib/python3.6/site-packages/mysql/connector/connection.py", line 416, in _handle_result raise errors.get_exception(packet) mysql.connector.errors.IntegrityError: 1062 (23000): Duplicate entry 'libreoffice-still-pa-in-libreoffice-pa-IN' for key 'ProviderNameProvides' ``` -- Eli Schwartz Bug Wrangler and Trusted User

On 04/08/2018 03:29 AM, Albert Graef via aur-general wrote:

On Sun, Apr 8, 2018 at 5:56 AM, Eli Schwartz via aur-general wrote:

...

Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg sets it from the first element of pkgname, and this is why the .SRCINFO still shows it.

I can add an explicit pkgbase=llvm35 again. (I already tried that before and it didn't fix the upload problem, so I removed it again, because that's the way it was in the original PKGBUILD from extra.)

...

The blacklist currently contains llvm35, which I think is because it is erroring when running updates.

It sure is. Can anyone of the admins remove it, please?

I've removed it manually, we're looking at a more permanent solution. -- Eli Schwartz Bug Wrangler and Trusted User

On Sun, Apr 8, 2018 at 9:51 AM, Albert Graef wrote:

Thanks, Eli! I'll give it another go immediately.

Worked, thanks again! -- Dr. Albert Gr"af Computer Music Research Group, JGU Mainz, Germany Email: aggraef@gmail.com WWW: https://plus.google.com/+AlbertGraef