** Description changed:

+ Removal request
+ ---------------
+ 
+ Please remove the binaries built from src:badger for all 32bit
+ architectures from groovy-release.
+ 
+ The binary package names are:
+ badger
+ golang-github-dgraph-io-badger-dev
+ 
+ 
+ The (release) archs that should get targeted for removal are:
+ armhf
+ 
+ 
+ It was removed from Debian as well:
+ 
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953370
+ 
+ 
+ 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://github.com/dgraph-
+ io/badger/issues/1384 even though we provided them with a 32bit CI test
+ integration.
+ 
+ 
+ 
+ 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://launchpad.net/~slyon/+archive/ubuntu/testing/+packages

** Changed in: badger (Ubuntu)
       Status: Incomplete => New

** Description changed:

  Removal request
  ---------------
  
  Please remove the binaries built from src:badger for all 32bit
- architectures from groovy-release.
+ architectures from Groovy.
  
  The binary package names are:
  badger
  golang-github-dgraph-io-badger-dev
  
- 
  The (release) archs that should get targeted for removal are:
  armhf
- 
  
  It was removed from Debian as well:
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953370
- 
  
  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://github.com/dgraph-
  io/badger/issues/1384 even though we provided them with a 32bit CI test
  integration.
  
- 
- 
  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://launchpad.net/~slyon/+archive/ubuntu/testing/+packages

** Description changed:

  Removal request
  ---------------
  
  Please remove the binaries built from src:badger for all 32bit
  architectures from Groovy.
  
  The binary package names are:
  badger
  golang-github-dgraph-io-badger-dev
  
- The (release) archs that should get targeted for removal are:
+ The (release) arch that should get targeted for removal is:
  armhf
  
  It was removed from Debian as well:
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953370
  
  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://github.com/dgraph-
  io/badger/issues/1384 even though we provided them with a 32bit CI test
  integration.
  
  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://launchpad.net/~slyon/+archive/ubuntu/testing/+packages

** Description changed:

  Removal request
  ---------------
  
  Please remove the binaries built from src:badger for all 32bit
  architectures from Groovy.
  
  The binary package names are:
  badger
  golang-github-dgraph-io-badger-dev
  
  The (release) arch that should get targeted for removal is:
  armhf
  
  It was removed from Debian as well:
- 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953370
  
  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://github.com/dgraph-
  io/badger/issues/1384 even though we provided them with a 32bit CI test
  integration.
  
  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://launchpad.net/~slyon/+archive/ubuntu/testing/+packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884753

Title:
  Please remove badger/armhf binaries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/badger/+bug/1884753/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to