Bug 85887

Do you have the test files around?

Are you using a non utf8 file system or something similar?

Created attachment 109056 [details]
all log

Locales is fr_FR.UTF-8 and my keyboard layout is fr-latin9.
I retried the compilation to give you more log. You can see the log above in attachment.

Do not hesitate asking for more information. Regards

Please answer the question i already made, do you have the test files around?

<do you have the test files around?>
I don't understand, what the files you mean? what the extension?

there are many files starting with test

ls test*
test-password-qt4      test-poppler-qt4.o
test-password-qt4.cpp  test-render-to-file
test-password-qt4.o    test-render-to-file.cpp
test-poppler-qt4       test-render-to-file.o
test-poppler-qt4.cpp   test-suite.log

Well, i mean the file that is giving you the error as could not open in the log, obviously.

Ok I see.
"Error: Couldn't open file '/tmp/yaourt-tmp-paul/aur-poppler-qt5-git/src/poppler/./../test/unittestcases/Gday garon - open.pdf': No such file or directory."

This relative path supposed to look in the following folder is it correct?

/tmp/yaourt-tmp-paul/aur-poppler-qt5-git/src/test/unittestcases/

But this file "Gday garon - open.pdf" has not been found because the name is miscoded

$ cd /tmp/yaourt-tmp-paul/aur-poppler-qt5-git/src/test/unittestcases/
$ ls Gd*
Gday garçon - open.pdf  Gday garçon - owner.pdf

The name is not miscoded, the code is pretty clear and says

QString::fromUtf8(TESTDATADIR "/unittestcases/Gday garçon - open.pdf")

And obviously works for me. That is why i am asking if you have anything wrong in your system, because it sounds like it to me.

I do not know how to be helpful to solve this bug.
Here's what I found as a command that can perhaps help them understand the problem.

$ localectl status
   System Locale: LANG=fr_FR.UTF-8
                  LC_COLLATE=C
       VC Keymap: fr-latin9
      X11 Layout: fr
       X11 Model: pc105
     X11 Variant: latin9_nodeadkeys
     X11 Options: grp:shifts_toggle

$ pacman -Q | grep 'poppler\|qt'
poppler 0.26.5-1
poppler-data 0.4.7-1
poppler-glib 0.26.5-1
pyqt4-common 4.11.2-1
python-pyqt4 4.11.2-1
qt4 4.8.6-3
qt5-base 5.3.2-2
qt5-declarative 5.3.2-2
qt5-location 5.3.2-2
qt5-sensors 5.3.2-2
qt5-svg 5.3.2-2
qt5-tools 5.3.2-2
qt5-translations 5.3.2-2
qt5-webkit 5.3.2-2
qt5-xmlpatterns 5.3.2-2
qtchooser 41-1
qtdownloadmanager-svn 14-1
qtwebkit 2.3.4-1

But there is something wrong with relative path (/./../):
'/tmp/yaourt-tmp-paul/aur-poppler-qt5-git/src/poppler/./../test/unittestcases/Gday garon - open.pdf'

Perhaps the problem came from the PKGBUILD of AUR.

What's wrong with /./../ ?

I stongly suggest you speak with the AUR guys

<< What's wrong with /./../ ? >>

Simply, if you type in console : $ cd /A/path/./../somewhere
you will receive an error saying the path does not exist.


<< I stongly suggest you speak with the AUR guys >>

I stongly give up.

(In reply to Mr Bump from comment #13)
> << What's wrong with /./../ ? >>
> 
> Simply, if you type in console : $ cd /A/path/./../somewhere
> you will receive an error saying the path does not exist.

You're joking right?

tsdgeos@xps:~/borrame$ cd ./../borrame
tsdgeos@xps:~/borrame$ pwd
/home/tsdgeos/borrame
tsdgeos@xps:~/borrame$ cd /home/tsdgeos/./../tsdgeos/borrame
tsdgeos@xps:~/borrame$ pwd
/home/tsdgeos/borrame


> 
> 
> << I stongly suggest you speak with the AUR guys >>
> 
> I stongly give up.

Enjoy your weakness of mind.

"Error: Couldn't open file '/tmp/yaourt-tmp-paul/aur-poppler-qt5-git/src/poppler/./../test/unittestcases/Gday garon - open.pdf': No such file or directory."

Okay, I'm probably wrong. But your condescending attitude will not make me change my mind. In my case, the topic is closed.