Your message dated Sat, 28 Dec 2024 13:21:12 -0500
with message-id 
<cad+gyvyddu29s4grvr4gyw_2igguwgxz+vf7jepkcdxnwbu...@mail.gmail.com>
and subject line close bug for packages intentionally not build on 32-bit and 
already removed
has caused the Debian Bug report #1091262,
regarding rust-vm-memory: FTBFS on armhf: build-dependency not installable: 
architecture-is-64-bit
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 ow...@bugs.debian.org
immediately.)


-- 
1091262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-vm-memory
Version: 0.16.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20241223 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, this package failed to build
on armhf.

This package currently has binary packages on armhf, so this is a regression.

Maybe you need to request removal of binaries on armhf?

Also, there are no known issues on amd64 or arm64 according to recent (a couple
days ago) rebuilds.

The rebuild was done using an armhf chroot on an AWS "m6g" instance (Graviton2
CPU).

Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                          
>  |
> +------------------------------------------------------------------------------+
> 
> 
> Setup apt archive
> -----------------
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-libc-0.2+default-dev (>= 0.2.39-~~), 
> librust-thiserror-1+default-dev (>= 1.0.40-~~), 
> librust-winapi-0.3+default-dev, librust-winapi-0.3+errhandlingapi-dev, 
> librust-winapi-0.3+sysinfoapi-dev, architecture-is-64-bit, build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-libc-0.2+default-dev (>= 0.2.39-~~), 
> librust-thiserror-1+default-dev (>= 1.0.40-~~), 
> librust-winapi-0.3+default-dev, librust-winapi-0.3+errhandlingapi-dev, 
> librust-winapi-0.3+sysinfoapi-dev, architecture-is-64-bit, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease
> Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
> Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [985 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [915 B]
> Fetched 2509 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> ----------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/12/23/rust-vm-memory_0.16.1-4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241223;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241223&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
These were removed on 32-bit architectures today and this is
intentional. Therefore I am closing the bugs.

https://bugs.debian.org/1090075

Thank you,
Jeremy BĂ­cha

--- End Message ---

Reply via email to