Package: nginx
Version: 1.20.2-2
Severity: serious
X-Debbugs-CC: 1004511@bugs.debian.org, lumin@debian.org
Control: reopen 1004511
Control: block 1004511 by -1
Control: block 1012362 by 1004511
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:aegisub 3.2.2+dfsg-6
Control: reassign -3 src:ettercap 1:0.8.3.1-9
Control: reassign -4 src:knot-resolver 5.5.1-1
Control: reassign -5 src:snort 2.9.15.1-6
Control: reassign -6 src:trafficserver 	9.1.2+ds-10
Control: reassign -7 src:uwsgi-plugin-luajit 0.0.7
Control: reassign -8 src:luakit 1:2.3-1

Dear maintainers,

We have been working for a while to get a working libluajit on ppc64el
(for reference, see history in bug #1012362). In the end we concluded
that it's not going to work as commitment upstream is lacking to support
ppc64el.

Your source package build depends on libluajit-5.1-dev when building on
ppc64el and at least one of its binaries depends on libluajit-5.1-2 on
that architecture. Please use liblua on ppc64el if that works for your
package, otherwise please request removal of the binaries on ppc64el
(e.g. by reassigning the bug to ftp.debian.org, lowering severity and
re-titling appropriately).

Sorry we couldn't solve the problem in a better way.

Paul

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   aegisub | 3.2.2+dfsg-6+b1 | ppc64el

------------------- Reason -------------------
RoQA; luajit2 segfaults
----------------------------------------------

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 http://snapshot.debian.org/.

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

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

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.
Thorsten Alteholz (the ftpmaster behind the curtain)