Please remove armhf binaries from plucky

Bug #2103963 reported by Simon Quigley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fastp (Ubuntu)
Fix Released
High
Unassigned
gfal2 (Ubuntu)
Invalid
High
Unassigned
gfal2-bindings (Ubuntu)
Invalid
High
Unassigned
liberasurecode (Ubuntu)
Invalid
High
Unassigned
libisal (Ubuntu)
Fix Released
High
Unassigned
nordugrid-arc (Ubuntu)
Invalid
High
Unassigned
python-isal (Ubuntu)
Fix Released
High
Unassigned
python-pyeclib (Ubuntu)
Invalid
High
Unassigned
xrootd (Ubuntu)
Invalid
High
Unassigned
xrootd-s3-http (Ubuntu)
Invalid
High
Unassigned

Bug Description

libisal and reverse dependencies need removal from the release pocket, only on armhf. The Debian maintainer has intentionally limited the architectures, armhf is no longer built as a result of that.

Here is a recursive reverse dependency map:
 - dpdk (false positive)
 - fastp - needed, rdeps:
   - debian-med - arch:all
   - pigx-rnaseq - arch:all
 - liberasurecode - needed
 - python-isal - needed, rdeps:
   - python-xopen - arch:all
 - python-pyeclib - needed, rdeps:
   - swift - arch:all
 - xrootd - needed, rdeps:
   - gfal2 - needed, rdeps:
     - gfal2-bindings, needed
     - gfal2-util - arch:all
   - nordugrid-arc - needed, rdeps:
     - nordugrid-arc-nagios-plugins - arch:all
     - debian-science - arch:all
   - xrootd-s3-http - needed

Thanks in advance.

Simon Quigley (tsimonq2)
Changed in fastp (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in gfal2 (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in gfal2-bindings (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in liberasurecode (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in nordugrid-arc (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in python-isal (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in python-pyeclib (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in xrootd (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in xrootd-s3-http (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Simon Chopin (schopin) wrote :

xrootd, liberasurecode and python-pyeclib are false-positive, the B-D are arch-specific.

This leaves us with the following binaries to remove:

libisal2 isal libisal-dev python3-isal fastp

❯ remove-package -m "libisa doesn't support 32-bit arches (LP: #2103963)" -A ubuntu -s questing -a armhf -b libisal2 isal libisal-dev python3-isal fastp
Removing packages from questing:
 libisal2 2.31.0-0.3 in questing armhf
 isal 2.31.0-0.3 in questing armhf
 libisal-dev 2.31.0-0.3 in questing armhf
 python3-isal 1.7.2-1 in questing armhf
 fastp 0.24.0+dfsg-1 in questing armhf
Comment: libisa doesn't support 32-bit arches (LP: #2103963)
Remove [y|N]? y
5 packages successfully removed.

Changed in fastp (Ubuntu):
status: Triaged → Fix Released
Changed in gfal2 (Ubuntu):
status: Triaged → Invalid
Changed in gfal2-bindings (Ubuntu):
status: Triaged → Invalid
Changed in liberasurecode (Ubuntu):
status: Triaged → Invalid
Changed in libisal (Ubuntu):
status: Triaged → Fix Released
Changed in nordugrid-arc (Ubuntu):
status: Triaged → Invalid
Changed in python-isal (Ubuntu):
status: Triaged → Fix Released
Changed in python-pyeclib (Ubuntu):
status: Triaged → Invalid
Changed in xrootd (Ubuntu):
status: Triaged → Invalid
Changed in xrootd-s3-http (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.