Package Details: photoflow 0.2.8.r2.gdf03f253-1

Git Clone URL: https://aur.archlinux.org/photoflow.git (read-only)
Package Base: photoflow
Description: Non-destructive, layer-based photo retouching including RAW image development
Upstream URL: http://aferrero2707.github.io/PhotoFlow
Licenses: GPL3
Conflicts: photoflow
Provides: photoflow
Submitter: Joermungand
Maintainer: Joermungand
Last Packager: Joermungand
Votes: 7
Popularity: 0.000148
First Submitted: 2015-10-30 22:20
Last Updated: 2017-09-05 15:03

Pinned Comments

Joermungand commented on 2018-05-10 15:37

The issue is caused by the upgrade of gcc to 8.1 a couple of days ago. I have not managed to sort it out satisfactorily, yet, so please use photoflow-git instead (for which I’ve found a workaround), until things get back to normal. As a matter of fact, the developer himself suggests users should choose the git version, as it dramatically improves on the stable version. The updated PKGBUILD for that one also fixes the other issues you’ve raised.

Latest Comments

Joermungand commented on 2019-02-24 18:48

@alex-y:

cc1plus : tous les avertissements sont traités comme des erreurs

Please see pinned post.

alex-y commented on 2019-02-24 18:05

[ 7%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/RawImage.cpp.o /var/tmp/pamac-build-ego/photoflow/src/photoflow/src/external/rawspeed/src/librawspeed/common/RawImage.cpp:135:57: error: attribut « const » sur une fonction retournant « void » [-Werror=attributes] void attribute((const)) RawImageData::poisonPadding() { ^ /var/tmp/pamac-build-ego/photoflow/src/photoflow/src/external/rawspeed/src/librawspeed/common/RawImage.cpp:156:59: error: attribut « const » sur une fonction retournant « void » [-Werror=attributes] void attribute((const)) RawImageData::unpoisonPadding() { ^ cc1plus : tous les avertissements sont traités comme des erreurs make[2]: [src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/build.make:128: src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/RawImage.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:626: src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/all] Error 2 make: *** [Makefile:152: all] Error 2 ==> ERREUR : Une erreur s’est produite dans build(). Abandon…

Joermungand commented on 2018-05-10 15:37

The issue is caused by the upgrade of gcc to 8.1 a couple of days ago. I have not managed to sort it out satisfactorily, yet, so please use photoflow-git instead (for which I’ve found a workaround), until things get back to normal. As a matter of fact, the developer himself suggests users should choose the git version, as it dramatically improves on the stable version. The updated PKGBUILD for that one also fixes the other issues you’ve raised.

dreieck commented on 2018-05-09 13:55

Build fails for me when working on rawspeed:

Scanning dependencies of target rawspeed
[  5%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/Common.cpp.o
[  5%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/Cpuid.cpp.o
[  6%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/DngOpcodes.cpp.o
[  6%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/ErrorLog.cpp.o
[  6%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/Memory.cpp.o
[  7%] Building CXX object src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/RawImage.cpp.o
/var/tmp/yaourt-tmp-felics/aur-photoflow/src/photoflow/src/external/rawspeed/src/librawspeed/common/RawImage.cpp:135:57: error: ‘const’ attribute on function returning ‘void’ [-Werror=attributes]
 void __attribute__((const)) RawImageData::poisonPadding() {
                                                         ^
/var/tmp/yaourt-tmp-felics/aur-photoflow/src/photoflow/src/external/rawspeed/src/librawspeed/common/RawImage.cpp:156:59: error: ‘const’ attribute on function returning ‘void’ [-Werror=attributes]
 void __attribute__((const)) RawImageData::unpoisonPadding() {
                                                           ^
cc1plus: all warnings being treated as errors
make[2]: *** [src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/build.make:128: src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/common/RawImage.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:621: src/external/rawspeed/src/librawspeed/CMakeFiles/rawspeed.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

dreieck commented on 2018-05-09 13:54

The file PKGBUILD has the executable bit set .. this should not be .. can you remove the executable permission from the PKGBUILD?

dreieck commented on 2018-05-09 12:14

Maybe you add a required version to the vips-dependency? (An entry of vips>=8.5.1 in the depends-array in the PKGBUILD would do the trick.)

When running ./configure, I get:

[...]
-- Checking for module 'vips>=8.5.1'
--   Requested 'vips >= 8.5.1' but version of vips is 7.36.5
CMake Error at /usr/share/cmake-3.11/Modules/FindPkgConfig.cmake:419 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.11/Modules/FindPkgConfig.cmake:586 (_pkg_check_modules_internal)
  CMakeLists.txt:115 (pkg_check_modules)


-- Configuring incomplete, errors occurred!
See also "/var/tmp/yaourt-tmp-felics/aur-photoflow/src/photoflow/build/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Makepkg was unable to build photoflow.

Updating vips and ./configure runs fine.

Joermungand commented on 2016-04-16 10:11

Right. Updated. Thanks!

ciappi commented on 2016-04-16 09:22

Joermungand, thanks for the clarification.
Btw, I think you need to add pugixml in the dependency list.
Thanks, ciappi

Joermungand commented on 2016-03-27 20:19

Package is NOT, I repeat, NOT out of date. It was built just after the LATEST commit in the master branch. The tag was defined AFTER the latest commit, which the current PKGBUILD reflects. You can always compare commit tags. I’ll update the PKGBUILD shortly, but it will only make you build the very same version again. Thanks, ciappi.