Your message dated Tue, 27 Jan 2026 12:36:49 +0000
with message-id <[email protected]>
and subject line Bug#1125316: fixed in open-coarrays 2.10.3-3
has caused the Debian Bug report #1125316,
regarding libcoarrays-openmpi-dev: postinst for amd64 fails because it refers 
to aarch64-linux-gnu
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.)


-- 
1125316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125316
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libcoarrays-openmpi-dev
Version: 2.10.3-2+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected], [email protected]
User: [email protected]
Usertags: amd64

Hello,
I've encountered an issue while upgrading libcoarrays-openmpi-dev:

    [UPGRADE] libcoarrays-openmpi-dev:amd64 2.10.2+ds-4 -> 2.10.3-2+b1

The error is:

    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Setting up libcoarrays-openmpi-dev:amd64 (2.10.3-2+b1)…
    update-alternatives: error: alternative path 
/usr/lib/aarch64-linux-gnu/open-coarrays/openmpi/bin/caf does not exist
    dpkg: error processing package libcoarrays-openmpi-dev:amd64 (--configure):
     old libcoarrays-openmpi-dev:amd64 package postinst maintainer script 
subprocess failed with exit status 2
    Errors were encountered while processing:
     libcoarrays-openmpi-dev:amd64


Probably because of a recent [commit], the postinst script for amd64
tries to update alternatives referring to aarch64-linux-gnu.

[commit]: 
<https://salsa.debian.org/science-team/open-coarrays/-/commit/1567d62eb3f14ebbac5c21bc8c6759fe6040db3d>

I see:

    $ cat /var/lib/dpkg/info/libcoarrays-openmpi-dev\:amd64.postinst 
    #!/bin/sh
    
    set -e
    
    # Note  two-level system
    
    if [ "$1" = "configure" ]; then
    
    update-alternatives \
        --install /usr/bin/caf.openmpi    caf-openmpi    
/usr/lib/aarch64-linux-gnu/open-coarrays/openmpi/bin/caf 50 \
        --slave   /usr/bin/cafrun.openmpi cafrun-openmpi 
/usr/lib/aarch64-linux-gnu/open-coarrays/openmpi/bin/cafrun 
    
    update-alternatives \
        --install /usr/bin/caf    caf    /usr/bin/caf.openmpi   50 \
        --slave   /usr/bin/cafrun cafrun /usr/bin/cafrun.openmpi
    
    fi


Manually modifying ( s/aarch64/x86_64/ ) the script in 
'/var/lib/dpkg/info/libcoarrays-openmpi-dev:amd64.postinst'
fixes the issue.

Please investigate what went wrong with the pre-computed DEB_HOST_MULTIARCH
and fix the bug in the Debian package.

Thanks for your time and dedication!



-- System Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.17.13+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_DIE, TAINT_FIRMWARE_WORKAROUND
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 libcoarrays-openmpi-dev depends on:
ii  gfortran [fortran-compiler]  4:15.2.0-4
ii  libc6                        2.42-7
ii  libcaf-openmpi-3t64          2.10.3-2+b1
ii  libcoarrays-dev              2.10.3-2+b1
ii  libgcc-s1                    15.2.0-12
ii  libgfortran5                 15.2.0-12
ii  libopenmpi40                 5.0.9-1
ii  openmpi-bin                  5.0.9-1

libcoarrays-openmpi-dev recommends no packages.

libcoarrays-openmpi-dev suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: open-coarrays
Source-Version: 2.10.3-3
Done: Alastair McKinstry <[email protected]>

We believe that the bug you reported is fixed in the latest version of
open-coarrays, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry <[email protected]> (supplier of updated open-coarrays 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 27 Jan 2026 11:45:57 +0000
Source: open-coarrays
Architecture: source
Version: 2.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 1125316 1125345
Changes:
 open-coarrays (2.10.3-3) unstable; urgency=medium
 .
   * Fix autogenerated files cleanup that was breaking pre/postinst
     generation. Closes: #1125345, #1125316
Checksums-Sha1:
 13faff3710399f48437441b8d79052f24db41b22 2986 open-coarrays_2.10.3-3.dsc
 c3a7efc0b64b13eed19edfa657c85e16bfb357c5 18364 
open-coarrays_2.10.3-3.debian.tar.xz
Checksums-Sha256:
 d40ca3f97c1c2c1810359973c3ff55d159a49733e62197cb760a8fc8a2cf0182 2986 
open-coarrays_2.10.3-3.dsc
 a9658cb3ae60ff362a362fdaeaaf5ec6bfe95625e3ab12901c536b838bcf1a63 18364 
open-coarrays_2.10.3-3.debian.tar.xz
Files:
 a33fe5a8cb70d2bbc8c7583a3ffc96e6 2986 utils optional open-coarrays_2.10.3-3.dsc
 608ad65eda9eac1d93a77c89fbaa8377 18364 utils optional 
open-coarrays_2.10.3-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIyBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAml4qMsACgkQy+a7Tl2a
06W80Q/3d2QLpU/zq/T8YiBj0iXJNOOpMhWms8jRYOoJtLGvQWl8KBeim3jdr1pr
o4LhB6ugJo6EJFVxrSFBs2+O3sHkEmF1maDbX6ZDsEnBd+cqEEkU+GzH5FV0cVkP
kaplcbxrj+N4nm8cTzgG1Ns0Rcmvx3P/qEdPBLlM/hyQVPFmhTep+2vT5xNQrZaP
O8Do1PDBAttEw4rkbLsKlnSxZg3imWHGApl3RZjbHzjZ/oPZgDTXrmWD0TvL4CF/
9t5xffJQ3jUYwDFkKzo7K3+1aVOS8oC2vgiuV7r6qhIBeoCnlpu1d+4lOZgxHsui
88YFnepl005qQJ/U0qX2hW+Sjoey5eUjzj6NkTzdWt1x7ed1D9KOvLjUu04GYASJ
AnC84UACqRkLbgwwGzfkdO4WkIxyhxGkcWmtvvpXLLhhtLfpRuzuwU2ZkXUuXCB4
Z3IsELYwS0xEO0ohbPyyeug19+rsgQceykSfcIVzMgukaHqZGyawiQQX/jAyIYkY
xUqbH9fymcArhG5vlN0m1Xa3e9Ujjj0llqT+s9HQxYNCWnoTp2ZgDh3HSo8uQ0gw
lwY/euFUNTw8wWYUgoy1j6lTqlSEO7W/XIj1uQf8Ap91cKaeZZQPaBc0zngC8zrH
yB1WbXfdmoxAYdJldfJjvKjbEN5bLd7D3rm8dPcMMCo4WV8d5A==
=+gCi
-----END PGP SIGNATURE-----

Attachment: pgpTlM0fjs_OR.pgp
Description: PGP signature


--- End Message ---

Reply via email to