Your message dated Wed, 25 Jan 2023 21:27:32 +0100
with message-id <c73e1ee704d2f3a1bfeb35818f9088a69d75a122.ca...@gmx.net>
and subject line Unreproducible
has caused the Debian Bug report #1026607,
regarding ruby-jekyll-paginate-v2: FTBFS: ERROR: Test "ruby3.1" failed:
<internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
`require': cannot load such file -- jekyll-paginate-v2/version (LoadError)
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.)
--
1026607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jekyll-paginate-v2
Version: 3.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require': cannot load such file -- jekyll-paginate-v2/version (LoadError)
> Did you mean? jekyll-watch/version
> from
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require'
> from /<<PKGBUILDDIR>>/spec/spec_helper.rb:5:in `<top (required)>'
> from /<<PKGBUILDDIR>>/spec/generator/defaults_spec.rb:1:in
> `require_relative'
> from /<<PKGBUILDDIR>>/spec/generator/defaults_spec.rb:1:in `<top
> (required)>'
> from
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require'
> from
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
> `block in <main>'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
> `select'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
> `<main>'
> rake aborted!
> Command failed with status (1): [ruby -w -I"specs"
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
> "spec/generator/defaults_spec.rb" "spec/generator/paginationPage_spec.rb"
> "spec/generator/paginator_spec.rb" "spec/generator/utils_spec.rb" -v]
>
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/12/20/ruby-jekyll-paginate-v2_3.0.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Hi,
I cannot reproduce the bug. The package builds fine. It might have been
affected by the broken jekyll package, which has already been fixed. We will do
several rebuilds during the ruby3.1 transition anyways. If this issue pops up
again, we'll deal with it.
Regards, Daniel
--- End Message ---
