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 Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
Opened by Andrew Nitschke (anitschk) - Thursday, 28 April 2022, 01:03 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
|
Details
Description:
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 ( https://bugs.launchpad.net/enblend/+bug/1970518 ) 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 ( https://aur.archlinux.org/packages/enblend-hg ) 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: ** https://bugs.launchpad.net/enblend/+bug/1970518 Steps to reproduce: See reproduciton steps in upstream bug report: https://bugs.launchpad.net/enblend/+bug/1970518 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:03 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/enblend-enfuse/issues/ 1
Saturday, 25 November 2023, 20:03 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/enblend-enfuse/issues/ 1
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.
{
"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
}