RM due to diaspora-installer installation fails

[Eric Desrochers]

Please remove disapora-installer, as it fails installation and thus its autopkgtest. It was removed from artful, yet somehow it has migrated in bionic now.

Maybe tests need to be reset to never passed, as it was removed and reintroduced now? Do we reset ADT results on pkg removal?

Regards,

Dimitri.

--

diasporama-installer cannot be installed successfully on Zesty.

While working on the percona SRU (LP: #1657256), we have noticed a few diaspora-installer autopkgtest failure which after more tests force us to conclude the installation of diasporama-installer is broken.

#Reproducer (outside autopkgtest context)

 # Install Zesty
 # apt-get update
 # apt-get install diaspora-installer -y

#Autopkg link
http://autopkgtest.ubuntu.com/packages/diaspora-installer/zesty/amd64
http://autopkgtest.ubuntu.com/packages/diaspora-installer/zesty/s390x

#Buildlog example
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/s390x/d/diaspora-installer/20171114_155330_1c389@/log.gz

#Error:
[32mBundle complete! 137 Gemfile dependencies, 263 gems now installed.[0m
[32mGems in the groups development and test were not installed.[0m
[32mBundled gems are installed into `./vendor/bundle`[0m
rake aborted!
NoMethodError: undefined method `with' for #<Bundler::Settings:0x00561a1b3f63b8>
/usr/share/diaspora/config/application.rb:4:in `<top (required)>'
/usr/share/diaspora/Rakefile:8:in `require'
/usr/share/diaspora/Rakefile:8:in `<top (required)>'
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
Checking if the database is empty...
Initializing database...
rake aborted!
NoMethodError: undefined method `with' for #<Bundler::Settings:0x00560c0bd5a558>
/usr/share/diaspora/config/application.rb:4:in `<top (required)>'
/usr/share/diaspora/Rakefile:8:in `require'
/usr/share/diaspora/Rakefile:8:in `<top (required)>'
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
dpkg: error processing package diaspora-installer (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 autopkgtest-satdep depends on diaspora-installer; however:
  Package diaspora-installer is not configured yet.

dpkg: error processing package autopkgtest-satdep (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
 diaspora-installer
 autopkgtest-satdep
E: Sub-process /usr/bin/dpkg returned an error code (1)
blame: diaspora-installer
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
autopkgtest [16:11:50]: ERROR: erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

[Eric Desrochers (slashd)]

I haven't test so far if other releases are affected outside Zesty.

[Eric Desrochers (slashd)]

$ rake gemspec --trace
rake aborted!
NoMethodError: undefined method `with' for #<Bundler::Settings:0x0055cb1e5c98a8>
/usr/share/diaspora/config/application.rb:4:in `<top (required)>'
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/diaspora/Rakefile:8:in `<top (required)>'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:689:in `raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:94:in `block in load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:176:in `standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:93:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:77:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:176:in `standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:75:in `run'
/usr/bin/rake:27:in `<main>'

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Eric Desrochers (slashd)]

At first glance, it really seems like diaspora-installer is affected by the following bug :

https://github.com/diaspora/diaspora/issues/7653

First introduced in bundler v1.16.0 by :
https://github.com/bundler/bundler/commit/8ccf49c3b4a086f1e0cad2130dc30c04304175b7

I confirmed both Zesty system and autopkgtest uses bundler 1.16.0 :

* Zesty affected system :
# gem list | grep -i bundler
bundler (1.16.0)

* Zesty Autopkgtest (mentioned above):
Using bundler 1.16.0

Seems like this has been addressed upstream with commit (first introduced upstream in v0.7.1.1) :

commit 63fcc9c1bcfe5a5033344358fff13ab803f724a7
Author: Benjamin Neff <email address hidden>
Date: Sat Oct 28 19:14:35 2017 +0200

    Fix compatibility with Bundler 1.6

    Stop using `Bundler.settings.with`, because it will be removed from
    Bundler 1.6.

    Also, as described in #7653, we could use `Bundler.settings[:with]`, but
    that would be internal API again, so it probably breaks again in the
    future. That's why I added a `BundlerHelper` module to parse the
    required optional group from our config files, without the use of any
    internal Bundler API.

    Fixes #7653

- Eric

[Matthias Klose (doko)]

I'm removing the package from bionic again (wasn't part of artful). Never shipped in Debian either (#866862). Maybe we should black-list it.

[Steve Langasek (vorlon)]

The current version of this package does not fail its autopkgtests. There should be no reason to use block-proposed bugs for packages which fail their autopkgtests anyway, failing autopkgtests are already enforced in proposed-migration.

[Dimitri John Ledkov (xnox)]

Well, the package now fails with ruby2.5 as default, which was the intention for bionic.

I'm trying to upgrade the package to use "next-minor" branch, but i'm not sure if I will be able to do that.

If it continues to fail, I guess I will raise the issue upstream.

[Steve Langasek (vorlon)]

Same story with diaspora: the autopkgtests are their own blocker, blocking bugs should not be used.