You are not logged in.
Heya..
I download muffin-git from aur, and then edit the recipe to contain , replaces, provides and conflicts=("${_pkgname}") which is muffin.
Even so, when doing makepkg -si, say, pacman doesn't resolve correctly, and exits with files already exists. If I remove muffin, it works obviously.
It's a bit odd, but I don't know if my system is for some reason borked in the db, or if someone can replicate (this particular package).
I cannot replicate the issue with other packages, only this one.
EDIT: and before the foaming mouth appear.. yes I am perfectly sure it is just me not understanding the resolving tree path here.. but just want someone with a helpful feedback on it. ,x
Last edited by solar (2014-01-15 05:23:15)
I am hilariously insane. yup. you won't notice though.. I promise...I think.
Offline
Did you read the pacman manual ?
ewaller$@$odin ~ 1007 %man pacman | tail -30 | head -4
BUGS
Bugs? You must be kidding, there are no bugs in this software. But if we happen to be wrong,
send us an email with as much detail as possible to pacman-dev@archlinux.org.ewaller$@$odin ~ 1008 %
![]()
Perhaps if you were to share your PKGBUILD...
Edit: Moving to AUR issues, Discussion and PKGBUILD requests
Last edited by ewaller (2014-01-15 05:39:21)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
What if you actually put conflicts=('muffin')? Does it still do it then?
Offline
I think he used the one from the AUR. I did get the errors too.
I'll try with 'muffin' instead of '${_pkgname}'
Edit: It worked.
Last edited by karol (2014-01-15 05:55:46)
Offline
Can someone provide the PKGBUILD that is "broken" so I take take a look at it. bonus points for extracting the .PKGINFO from the built package and posting it too!
Offline
https://aur.archlinux.org/packages/mu/m … t/PKGBUILD doesn't work.
Offline
Not a pacman bug, but a bad PKGBUILD. Single quotes don't allow the variables to expand, they should be double quotes.
Last edited by Scimmia (2014-01-15 07:28:00)
Offline
@ Scimmia, but the OP does use double quotes. Or maybe he used double quotes only for the post...
Last edited by x33a (2014-01-15 08:46:36)
Offline
Double quotes work.
Offline
Indeed, there are single quotes around the variable in the package.
@solar, look up the difference between single an double quotes in bash. Then you'll see why this was borked and why your original post caused confusion.
Offline
"Trust no one", as the Eskimos say ;-)
Offline
But what if I don't trust Eskimos?
</off topic>
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline