On 06-04-18 08:11, Albert Graef via aur-general wrote:

The llvm35 package recently got kicked from extra, but I need it for my Pure package (https://aur.archlinux.org/packages/pure/) which in turn is needed for a bunch of other packages I maintain in the AUR.

So I resurrected llvm35 from extra, brushed it up a little so that it compiles again (also bumped the package revision), and tried to upload it to the AUR under the previous package name llvm35. All I get is:

Writing objects: 100% (8/8), 4.76 KiB | 2.38 MiB/s, done. Total 8 (delta 1), reused 0 (delta 0) remote: error: package already provided by []: llvm35 remote: error: hook declined to update refs/heads/master To ssh://aur.archlinux.org/llvm35.git ! [remote rejected] master -> master (hook declined) error: failed to push some refs to 'ssh://aur@aur.archlinux.org/llvm35.git'

My version of the PKGBUILD is available here: https://bitbucket.org/agraef/llvm35-pkgbuild

It's a split package, but isn't that supposed to be supported by the AUR? Anything else wrong with it?

Any help appreciated, many thanks in advance. Albert

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. I think AUR uses a blacklist to prevent duplicates with offical repos, maybe that blacklist needs updating ? AUR has llvm33 , llvm38, llvm39, llvm4 and llvm 5 . Maybe your packages can use one of those ? lW

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? Thanks Albert -- Dr. Albert Gr"af Computer Music Research Group, JGU Mainz, Germany Email: aggraef@gmail.com WWW: https://plus.google.com/+AlbertGraef

LoneVVolf wrote:

AUR has llvm33 , llvm38, llvm39, llvm4 and llvm 5 . Maybe your packages can use one of those ?

LLVM 3.5 is the last version which still has the old JIT backend, which is what Pure still needs right now. LLVM 3.4 would work just as well, but that's not available in the AUR, and LLVM 3.3 is 2 years older than 3.5, so I'd rather not use it if I can avoid it. You might ask why I've not updated Pure to the new JIT yet. In fact, that has been on my TODO list for a long time, but I've been busy with other projects, and it's not straightforward because Pure needs the ability to recompile a function on the spot, which the new MCJIT doesn't offer any more, so I'll have to rewrite Pure's entire code generator for the MCJIT. Albert -- Dr. Albert Gr"af Computer Music Research Group, JGU Mainz, Germany Email: aggraef@gmail.com WWW: https://plus.google.com/+AlbertGraef

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