Your message dated Tue, 11 Feb 2020 12:52:53 +0000
with message-id <e1j1v25-0005st...@fasolo.debian.org>
and subject line Bug#950798: Removed package(s) from unstable
has caused the Debian Bug report #851024,
regarding leap-cli: FTBFS: ERROR: Test "ruby2.3" failed.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leap-cli
Version: 1.9-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Checking Rubygems dependency resolution on ruby2.3                          
>  │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> GEM_PATH=debian/leap-cli/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"leap_cli\"
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
> 'faraday' (>= 0.9.1, ~> 0.9) among 22 total gem(s) (Gem::LoadError)
> Checked in 
> 'GEM_PATH=debian/leap-cli/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
>  execute `gem env` for more information
>       from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1439:in `block in 
> activate_dependencies'
>       from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>       from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>       from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>       from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>       from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>       from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>       from -e:1:in `<main>'
> base32 (0.3.2)
> bigdecimal (1.2.8)
> capistrano (3.4.0)
> colorize (0.8.1)
> did_you_mean (1.0.0)
> gli (2.14.0)
> i18n (0.7.0)
> io-console (0.4.5)
> json (2.0.1, 1.8.3)
> minitest (5.9.0)
> net-scp (1.2.1)
> net-ssh (3.2.0)
> net-telnet (0.1.1)
> power_assert (0.2.7)
> psych (2.1.0)
> rake (10.5.0)
> rdoc (4.2.1)
> sshkit (1.9.0)
> test-unit (3.1.7)
> ya2yaml (0.31)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/leap-cli_1.9-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Version: 1:1.9-3+rm

Dear submitter,

as the package leap-cli has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/950798

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note 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.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to