[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1088282: marked as done (RM: criu [armhf] -- RoM; fails to build on arm64 host)

Your message dated Sat, 11 Jan 2025 09:30:25 +0000
with message-id <E1tWXp3-003Hio-SX@fasolo.debian.org>
and subject line Bug#1088282: Removed package(s) from stable
has caused the Debian Bug report #1088282,
regarding RM: criu [armhf] -- RoM; fails to build on arm64 host
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 owner@bugs.debian.org
immediately.)


-- 
1088282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088282
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: criu@packages.debian.org, carnil@debian.org
Control: affects -1 + src:criu
User: release.debian.org@packages.debian.org
Usertags: rm

Hi stable release managers,

criu were affected by #918229 in stable, which we did now hit as all
the buildds are arm64. Packages got build now again in stable for the
first time due to #1087931.

I propose to simply get criu removed on armhf (the current unfixed
package would not be usable without fix from #1087931, but neither it
can be built again in stable).

In trixie/unstable criu does not get anymore build for armhf.

Regards,
Salvatore

--- End Message ---
--- Begin Message --- 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from stable:

      criu |   3.17.1-2 | armhf

------------------- Reason -------------------
RoM; fails to build on arm64 host
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1088282@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1088282

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)

Attachment: pgpua7x9CaGrC.pgp
Description: PGP signature


--- End Message ---
Reply to: