Your message dated Tue, 15 Apr 2025 17:44:39 +0000
with message-id <e1u4kkt-009hpv...@fasolo.debian.org>
and subject line Bug#1102689: Removed package(s) from unstable
has caused the Debian Bug report #1101712,
regarding ruby-mail-room: FTBFS: Failure/Error: @server.start
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.)


-- 
1101712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-mail-room
Version: 0.10.0+really0.0.24-2
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
Failures:

  1) MailRoom::HealthCheck#run sets running to true
     Failure/Error: @server.start

     Mocha::StubbingError:
       #<Mock:0x32c8> was instantiated in one test but it is receiving 
invocations within another test. This can lead to unintended interactions 
between tests and hence unexpected test failures. Ensure that every test 
correctly cleans up any state that it introduces.
     # /<<PKGBUILDDIR>>/lib/mail_room/health_check.rb:18:in `block in run'

Finished in 2.21 seconds (files took 0.4228 seconds to load)
118 examples, 1 failure, 4 pending

Failed examples:

rspec /<<PKGBUILDDIR>>/spec/lib/health_check_spec.rb:36 # 
MailRoom::HealthCheck#run sets running to true

Randomized with seed 58521

Coverage report generated for RSpec to /<<PKGBUILDDIR>>/coverage. 1475 / 1541 
LOC (95.72%) covered.
Stopped processing SimpleCov as a previous error not related to SimpleCov has 
been detected
/usr/bin/ruby3.3 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
pkill redis-server || true
ERROR: Test "ruby3.3" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<<BUILDDIR>>/ruby-mail-room-0.10.0\+really0.0.24/debian/ruby-mail-room 
returned exit code 1
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202503/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

Note: The failure happens randomly, but more than 50% of the time here,
which I consider unsuitable for release.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible (within its randomness).

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:ruby-mail-room, so that this is still
visible in the BTS web page for this package.

Thanks.

--- End Message ---
--- Begin Message ---
Version: 0.10.0+really0.0.24-2+rm

Dear submitter,

as the package ruby-mail-room 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/1102689

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to