leptonica 1.83.1 installation failed

  • Done
  • quality assurance status badge
Details
3 participants
  • francismb
  • Herman Rimm
  • Maxim Cournoyer
Owner
unassigned
Submitted by
francismb
Severity
normal
Merged with
F
F
francismb wrote on 19 Aug 2023 12:10
(address . bug-guix@gnu.org)
d729dec9-7177-96cc-a0d6-a56e241cf5a8@email.de
Dear Maintainers,
while trying to install package the installation fails:



guix package -i leptonica
The following package will be installed:
leptonica 1.83.1

The following derivation will be built:
/gnu/store/p3rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv

building /gnu/store/p3rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv...
\ 'check' phasebuilder for
`/gnu/store/p3rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv'
failed with exit code 1
build of
/gnu/store/p3rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv failed
View build log at
'/var/log/guix/drvs/p3/rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv.bz2'.
guix package: error: build of
`/gnu/store/p3rxqvszpwfgjf9v9hfh06v6a8p1gsf6-leptonica-1.83.1.drv' failed



Attached the build log,

I hope it helps, thanks in advance!
francisMB
M
M
Maxim Cournoyer wrote on 2 Sep 2023 04:12
control message for bug #65381
(address . control@debbugs.gnu.org)
877cp91fxp.fsf@gmail.com
merge 65381 65441
quit
H
H
Herman Rimm wrote on 18 Jan 13:57 +0100
leptonica 1.83.1 installation failed
(address . 65381@debbugs.gnu.org)(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
tmaj2po4izpgx5qz6jtnyw4rtbahivd5du5mklullo5k46rkw3@gpjbb7h4rll4
Hello,

#68560 disables this failing test. You can apply that patch series or
just add this build-phase to the leptonica package definition:

(add-after 'unpack 'disable-failing-tests
(lambda _
(substitute* "prog/Makefile.am"
(("ioformats_reg") ""); Fails for unclear reason.
(("pngio_reg") "")))) ; Fails non-deterministically.

Cheers,
Herman Rimm
?
Your comment

This issue is archived.

To comment on this conversation send an email to 65381@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 65381
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch