Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#74575 - [enblend-enfuse] enfuse creates too large of image with black border on right and bottom

Attached to Project: Community Packages
Opened by Andrew Nitschke (anitschk) - Thursday, 28 April 2022, 01:03 GMT
Last edited by David Thurstenson (thurstylark) - Thursday, 28 April 2022, 01:38 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Bruno Pagani (ArchangeGabriel)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



There is a bug with the version of enfuse arch packages where it creates too large of an image with a black border on the right and bottom of the image.

I have reported this issue to the enfuse developers ( ) and after some investigation we found that Arch is packaging a ~3 year old version from the development branch.

If I build enblend/enfuse from source using ( ) then this seems to fix the bug.

I am creating this as a bug rather then a "flag out of date" because I can see the following comment in the PKGBUILD for enblend-enfuse that seems to suggest enblend needs a more up to date version of exiv2 then what Arch currently supports so I am not sure it will be possible to just upgrade to the latest version of what is off the head?

"# The latest revision moves to C++17 instead of boost but requires exiv2 2.28 which is currently unreleased"

I am also creating this in addition to the report I made to the enblend team because it sounds like Arch may be using a non-stable version off the development branch so I am not sure if there is any expectation that the enblend team will patch this issue for us?

Additional info:
* package version(s)
** pacman -Qi enblend-enfuse
Name : enblend-enfuse
Version : 4.2.r1524+h4c30a326b3f4-2
* config and/or log files etc.:
** See upstream report
* link to upstream bug report, if any:

Steps to reproduce:
See reproduciton steps in upstream bug report:
This task depends upon

Comment by Bruno Pagani (ArchangeGabriel) - Thursday, 28 April 2022, 10:35 GMT
I don’t remember how it went exactly, but IIRC a newer build with exiv2 was required, but current master indeed requires an unreleased version of exiv2. I guess that if you try to build -hg with exiv2 from repos it does not work. We will need to wait for at least exiv2 to release, and ideally enblend-enfuse too though we should just be able to find a proper point of current master for that.
Comment by Andrew Nitschke (anitschk) - Thursday, 28 April 2022, 11:50 GMT
I was curious how it is that I was able to build the enblend-hg AUR package ( without the new version of exiv2. Looks like that is building enblend without the "--with-exiv2" flag.

As the enblend documentaiton states:

** --with-exiv2=CHECK/yes/no

Use Exiv2 library for meta-data transfer of the input images to the
result. Without this library Enblend or Enfuse will not copy any EXIF
meta data.

Would building enblend-enfuse without this flag be a workable option? I suspect that many/most people using enblend/enfuse are using it via the hugin package which already uses exiftool to copy exif data to the final stitched image.

Comment by Bruno Pagani (ArchangeGabriel) - Thursday, 28 April 2022, 11:58 GMT
I need to find out why I added exiv2. If I did so, there must have been some reason normally… But if can’t find it, we can try, and affected people might then complain.
Comment by Andrew Nitschke (anitschk) - Thursday, 28 April 2022, 13:39 GMT
I took a look at for both enblend-enfuse and hugin. Looks like there are a few people (~4%) that have installed enblend-enfuse without hugin but it is pretty rare:

"name": "enblend-enfuse",
"samples": 235502,
"count": 12381,
"popularity": 5.26,
"startMonth": 202103,
"endMonth": 202203

"name": "hugin",
"samples": 235502,
"count": 11884,
"popularity": 5.05,
"startMonth": 202103,
"endMonth": 202203