Your message dated Sun, 16 Feb 2020 00:22:05 +0000
with message-id <e1j37hf-0005wp...@fasolo.debian.org>
and subject line Bug#951133: Removed package(s) from unstable
has caused the Debian Bug report #867650,
regarding berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean?
Berkshelf::NullFormatter (NameError)
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.)
--
867650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: berkshelf
Version: 4.3.5-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 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):
> Did you mean? Berkshelf::NullFormatter (NameError)
> ./lib/berkshelf.rb:164:in `const_get'
> ./lib/berkshelf.rb:164:in `set_format'
> ./lib/berkshelf/cli.rb:78:in `initialize'
> ./lib/berkshelf/cli.rb:49:in `dispatch'
> ./lib/berkshelf/cli.rb:27:in `execute!'
> ./features/step_definitions/utility_steps.rb:6:in `/the output from
> ./features/step_definitions/utility_steps.rb:6:in
> (.+)./features/step_definitions/utility_steps.rb:6:in should be the same as
> ./features/step_definitions/utility_steps.rb:6:in
> (.+)./features/step_definitions/utility_steps.rb:6:in /'
> features/help.feature:9:in `Then the output from `berks cookbook -h` should
> be the same as `berks help cookbook`'
> features/help.feature:3:in `Then the output from `<actual>` should be the
> same as `<expected>`'
>
> Failing Scenarios:
> cucumber features/help.feature:6 # Scenario Outline: Using various help
> switches, Examples (#1)
> cucumber features/help.feature:7 # Scenario Outline: Using various help
> switches, Examples (#2)
> cucumber features/help.feature:8 # Scenario Outline: Using various help
> switches, Examples (#3)
> cucumber features/help.feature:9 # Scenario Outline: Using various help
> switches, Examples (#4)
>
> 146 scenarios (4 failed, 142 passed)
> 823 steps (4 failed, 819 passed)
> 0m9.671s
> ERROR: Test "ruby2.3" failed:
The full build log is available from:
http://aws-logs.debian.net/2017/07/07/berkshelf_4.3.5-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: 4.3.5-2+rm
Dear submitter,
as the package berkshelf 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/951133
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 ---
