aurman: aurman fails to run on Raspberry Pi 2

Description

I wanted to update my Archlinux on my Raspberry Pi 2 like I used to do every one or two weeks. After the latest update using aurman (in which aurman itself was updated also from 2.14 to 2.16) I ran into this issue. Apparently this issue only appears on my Raspberry Pi 2 armv7h platform. On x86_64 the error did not appear.

Expected Behavior

aurman --version should return 2.16-1 or anything similar

Current Behavior

This is what I got:

2018-07-04 23:10:34,521 - wrappers - expac - ERROR - expac query -Q %v - for targets ['aurman-git', 'aurman'] failed
2018-07-04 23:10:34,523 - main - main - ERROR - 
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/aurman/main.py", line 835, in main
    process(argv[1:])
  File "/usr/lib/python3.6/site-packages/aurman/main.py", line 345, in process
    show_version()
  File "/usr/lib/python3.6/site-packages/aurman/main.py", line 85, in show_version
    aurman_note(expac("-Q", ["v"], ["aurman-git", "aurman"])[0])
  File "/usr/lib/python3.6/site-packages/aurman/wrappers.py", line 69, in expac
    raise InvalidInput("expac query {} for targets {} failed".format(query_stringified, targets))
aurman.own_exceptions.InvalidInput: expac query -Q %v - for targets ['aurman-git', 'aurman'] failed

Possible Solution

Sorry, I wouldn’t know, seems related to platform.

Version of aurman you are using

Latest package on AUR (2.16-1)

Steps to Reproduce

  1. aurman --version or -V
  2. Also tried aurman -Syu with similar result:
2018-07-04 23:20:40,564 - wrappers - expac - ERROR - expac query -Q '%n?!%v?!%D?!%H?!%o?!%P?!%T?!%e?!%G?!%w' - for targets ['faad2', 'bash', ...........] failed
  1. Tried updating expac-git manually from AUR --> no change in behaviour
  2. Tried replacing expac-git by expac from stable --> no change in behaviour

Read the README

Yes, I did!

Running linux distribution

Linux RPIarch 4.14.52-1-ARCH #1 SMP Thu Jun 28 00:45:47 UTC 2018 armv7l GNU/Linux

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 16 (12 by maintainers)

Most upvoted comments

Nevermind: I know what the problem is, char is unsigned on ARM, the return value of fgetc is going to be casted to something besides EOF all the time, because it is being saved in a char[], thus never as -1, thus line[i] == EOF is never true and thus the overflow. Going to prepare a proper patch and open a PR in the expac repo.