Please remove badger/armhf binaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
badger (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Removal request
---------------
Please remove the binaries built from src:badger for all 32bit architectures from Groovy.
The binary package names are:
badger
golang-
The (release) arch that should get targeted for removal is:
armhf
It was removed from Debian as well:
https:/
Extended removal reason:
2.0.1-4 included a bunch of patches that made badger not only build
but also pass its own testsuite on 32bit architectures. This was a
mistake, because it was later realized that the trivial patches
created didn't actually make badger practically usable on 32bit
archs - as badger is usually built into another application and if that
application does any memory allocations then badger will not work.
A non-trivial amount of work is needed to fix badger on 32bit architectures and it seems upstream doesn't have interest in this at the moment. There has been no progress on https:/
Original bug report
-------------------
badger 2.0.3-1 fails to build on armhf, due to running out of memory while executing its test suite inside the armhf build VM, during dh_auto_test stage.
This patch disables running the test suite during the build on armhf. The test suite will still be run via autopkgtest.
With this patch it built successfully in a PPA: https:/
description: | updated |
tags: | added: id-5eeb8f9af79fbd71a17226db |
description: | updated |
description: | updated |
Changed in badger (Ubuntu): | |
status: | Incomplete → New |
description: | updated |
description: | updated |
description: | updated |
Actually, there seems to be a bigger, 32bit related issue: /buildd. debian. org/status/ package. php?p=badger& suite=sid
https:/
Let me check that in detail...