Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Aura error '': wrong or NULL argument passed #109

Closed
c00w opened this Issue Jun 4, 2013 · 17 comments

Comments

Projects
None yet
6 participants

c00w commented Jun 4, 2013

% sudo aura -Ayu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
aura >>= Fetching package information...
aura >>= Aura update available. Update it first? [Y/n] n
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
aura : 1.2.0.1-2 => 1.2.0.1-3
tp_smapi-dkms : 0.6.4-2 => 0.41-7

aura >>= Determining dependencies... 
aura >>= AUR Packages:
aura
tp_smapi-dkms

aura >>= Continue? [Y/n] 
aura >>= Building `aura`...
loading packages...
error: '': wrong or NULL argument passed
Raw shell command call failed.
Contributor

tlunter commented Jun 4, 2013

This seems to be happenng post makepkg.

Same deal here. I was on aura-bin 1.2.0.1-2. I installed manually and it worked, so it's not a package issue, but an aura one.

Owner

fosskers commented Jun 4, 2013

What the heck is this error? I can't reproduce it.

Owner

fosskers commented Jun 4, 2013

I have a theory. What shell and terminal are you gentlemen using?

justinkb commented Jun 4, 2013

could it have to do with the recent /bin -> /usr/bin move?

I can reproduce this problem with zsh, sh, bash from within gnome-terminal, xterm, actual 'console' terminal so it's unrelated to any of that

it happens on every AUR package, it seems

Owner

fosskers commented Jun 4, 2013

I figured it out.
You can reproduce by opening up ghci and:

Prelude> :m + System.Process
Prelude> rawSystem "pacman" ["-Qi","","curl"]

justinkb commented Jun 4, 2013

git bisect between 12.0.0 and 12.0.1 could help nail down if it was caused by changes in aura, or unrelated to it

edit: so it's a "whitespace" problem? caused by some wrongly placed quote characters somewhere? causing misinterpretation of certain input? odd

@fosskers fosskers closed this in 7d1d79e Jun 4, 2013

justinkb commented Jun 4, 2013

yeah, I was just about to point out that "" should probably have been the Haskell null type, whatever that is ;-)

everyone that has the 'faulty' aura version installed will have to upgrade manually, correct?

Owner

fosskers commented Jun 4, 2013

This was caused by changes I made to adapt to the new graph-based dependency checking. It had to do with marking packages with the "--asdeps" flag if they were depedencies, or nothing if they were one of the original packages asked for. For those, I was tagging them with "" which was making things explode. It's abstracted out now with Haskell's Maybe type.

Owner

fosskers commented Jun 4, 2013

Can someone tell me if this worked?

Contributor

tlunter commented Jun 4, 2013

I have success here.

Owner

fosskers commented Jun 4, 2013

Excellent, thank you Todd.

rmarquis commented Jun 4, 2013

On a sidenote: Seems you forgot to update the md5sum of the aura-bin PKGBUILD. Can't install without passing makepkg's --skipinteg option :)

Owner

fosskers commented Jun 4, 2013

Really? I thought I did. Thanks.

I'm still getting this with aura-bin (1.2.0.1-4), but aura seems to work fine.

Owner

fosskers commented Jun 5, 2013

Just threw up 1.2.0.1-5 for aura-bin.

That seems to have fixed it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment