Bug#976477: marked as done (jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2022 18:55:16 -0500
with message-id <08d81437-5814-e2b4-ea9f-59627b396314 at riseup.net>
and subject line Re: jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
has caused the Debian Bug report #976477,
regarding jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
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 owner at bugs.debian.org
immediately.)


-- 
976477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976477
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Lucas Nussbaum <lucas at debian.org>
Subject: jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
Date: Sat, 5 Dec 2020 14:03:13 +0100
Size: 405541
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20221203/4aff6deb/attachment-0002.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: =?UTF-8?B?SsOpcsO0bWUgQ2hhcmFvdWk=?= <jerome at riseup.net>
Subject: Re: jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
Date: Sat, 3 Dec 2022 18:55:16 -0500
Size: 2647
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20221203/4aff6deb/attachment-0003.eml>