Your message dated Mon, 29 May 2023 09:22:03 +0300
with message-id <[email protected]>
and subject line Re: Bug#1036023: same problem on armhf
has caused the Debian Bug report #1036023,
regarding cabal-install: cabal install fails on i686: fdTryLock: invalid
argument (Invalid argument)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1036023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036023
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cabal-install
Version: 3.4.1.0-3
Severity: important
X-Debbugs-Cc: [email protected]
Hi,
I'm experiencing a persistent issue with the 'cabal install' on an i686.
Regardless of the package I attempt to install, the command consistently fails
with the error: fdTryLock: invalid argument (Invalid argument).
Here is a typical example of the error occurring when trying to install the
'hello' package:
$ cabal install hello
Resolving dependencies...
Build profile: -w ghc-9.0.2 -O1
In order, the following will be built (use -v for more details):
- hello-1.0.0.2 (exe:hello) (requires download & build)
Downloading hello-1.0.0.2
Downloaded hello-1.0.0.2
Starting hello-1.0.0.2 (all, legacy fallback)
Building hello-1.0.0.2 (all, legacy fallback)
Installing hello-1.0.0.2 (all, legacy fallback)
cabal: Failed to build hello-1.0.0.2. The failure occurred during the final
install step. The exception was:
fdTryLock: invalid argument (Invalid argument)
For the moment, I am able to work around the issue by using the upstream build,
which does not seem to produce this error.
However, I would prefer to use the Debian packaged version.
Greetings,
Uros
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 6.1.0-7-686-pae (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cabal-install depends on:
ii ghc 9.0.2-4
ii libc6 2.36-9
ii libffi8 3.4.4-1
ii libgmp10 2:6.2.1+dfsg1-1.1
ii sgml-base 1.31
ii zlib1g 1:1.2.13.dfsg-1
Versions of packages cabal-install recommends:
ii curl 7.88.1-9
ii wget 1.21.3-1+b1
cabal-install suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.4.1.0-3
Hi Uros, Joey,
Thanks for reporting this. I believe this should be fixed now
in version 3.4.1.0-3+b1, available both in unstable and testing.
On Sun, May 28, 2023 at 11:53PM, Joey Hess wrote:
> I rebuilt cabal-install from source, turning off the lukko build
> flag, and confirmed that fixed this problem.
>
> My recommendation would be to just do that for now, until lukko gets
> fixed.
Fortunately, we have already fixed lukko in Debian, so we only needed to
rebuild cabal-install. See also https://bugs.debian.org/1036833 for more
information.
Best,
--
Ilias
--- End Message ---
