Arch Linux User Repository

@Hexdump Unfortunately, this is beyond my controls as I believe the issue is that the version of ruby-maxitest in the official repositories is incompatible with the version of ruby-minitest.

Hi, I had to manually run 'gem install maxitest' for the installation to complete. More precisely, ruby-css_parser was doing an error. It may be a forgotten compilation dependency.

/usr/bin/ruby -w -I"lib" /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/rule_set/declarations/test_value.rb" "test/rule_set/test_declarations.rb" "test/test_css_parser_basic.rb" "test/test_css_parser_loading.rb" "test/est_css_parser_media_types.rb" "test/test_css_parser_misc.rb" "test/test_css_parser_offset_capture.rb" "test/test_css_parser_regexps.rb" "test/test_helper.rb" "test/test_merging.rb" "test/test_rule_set.rb" "test/test_rule_set_creating_shorthand.rb" "test/test_rule_set_expanding_shorthand.rb"
Could not find compatible versions

Because every version of maxitest depends on minitest >= 5.0.0, < 5.19.0 and minitest >= 5.0.0, < 5.19.0 could not be found in locally installed gems, maxitest cannot be used. So, because Gemfile depends on maxitest >= 0, version solving has failed.                                                                                                                    
rake aborted!
Command failed with status (6): [ruby -w -I"lib" /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/rule_set/declarations/test_value.rb" "test/rule_set/test_declarations.rb" "test/test_css_parser_basic.rb" "test/est_css_parser_loading.rb" "test/test_css_parser_media_types.rb" "test/test_css_parser_misc.rb" "test/test_css_parser_offset_capture.rb" "test/test_css_parser_regexps.rb" "test/test_helper.rb" "test/test_merging.rb" "test/test_rule_set.rb" "test/est_rule_set_creating_shorthand.rb" "test/test_rule_set_expanding_shorthand.rb" ]

@j-h, could reproduce this issue - the test fails for me now as well. I've pushed a new pkgver with it removed. Thanks for reporting!

Hi,

I'm getting the test failure shown below when trying to install ascii-doctor-pdf 2.3.10:

Failures:

  1) Asciidoctor::PDF::Converter - Image Inline should not mangle character spacing in line if inline image wraps
     Failure/Error: (expect to_file).to visually_match 'image-wrap-inline.pdf'
       expected /home/jos/.cache/yay/asciidoctor-pdf/src/asciidoctor-pdf-2.3.10/spec/output/image-wrap-inline.pdf to be visually identical to /home/jos/.cache/yay/asciidoctor-pdf/src/asciidoctor-pdf-2.3.10/spec/reference/image-wrap-inline.pdf
     # ./spec/image_spec.rb:2127:in `block (3 levels) in <top (required)>'

Finished in 3 minutes 18.7 seconds (files took 0.42013 seconds to load)
2144 examples, 1 failure

Failed examples:

rspec ./spec/image_spec.rb:2111 # Asciidoctor::PDF::Converter - Image Inline should not mangle character spacing in line if inline image wraps

==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: asciidoctor-pdf-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
asciidoctor-pdf - exit status 4

I'm getting this even after a complete system update, so I don't think it's anything wrong with my setup.

@zkrx Thanks for reporting. Fixed.

Looks like you are missing a few dependencies: -ruby-matrix (AUR) -ruby-concurrent

[user Vulkan-Docs-1.3.272]$ asciidoctor-pdf --version
/usr/lib/ruby/3.0.0/rubygems/specification.rb:1453:in `rescue in block in activate_dependencies': Could not find 'matrix' (>= 0.4) among 120 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/user/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' at: /usr/lib/ruby/gems/3.0.0/specifications/asciidoctor-pdf-2.3.9.gemspec, execute `gem env` for more information
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1450:in `block in activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `each'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1421:in `activate'
        from /usr/lib/ruby/3.0.0/rubygems.rb:286:in `block in activate_bin_path'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `synchronize'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/bin/asciidoctor-pdf:25:in `<main>'
/usr/lib/ruby/3.0.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'matrix' (>= 0.4) - did find: [matrix-0.3.1] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/home/user/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' , execute `gem env` for more information
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1451:in `block in activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `each'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1421:in `activate'
        from /usr/lib/ruby/3.0.0/rubygems.rb:286:in `block in activate_bin_path'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `synchronize'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/bin/asciidoctor-pdf:25:in `<main>'

[user Vulkan-Docs-1.3.272]$ asciidoctor-pdf --version
/usr/lib/ruby/3.0.0/rubygems/specification.rb:1453:in `rescue in block in activate_dependencies': Could not find 'concurrent-ruby' (>= 1.1) among 121 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/user/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' at: /usr/lib/ruby/gems/3.0.0/specifications/asciidoctor-pdf-2.3.9.gemspec, execute `gem env` for more information
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1450:in `block in activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `each'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1421:in `activate'
        from /usr/lib/ruby/3.0.0/rubygems.rb:286:in `block in activate_bin_path'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `synchronize'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/bin/asciidoctor-pdf:25:in `<main>'
/usr/lib/ruby/3.0.0/rubygems/dependency.rb:311:in `to_specs': Could not find 'concurrent-ruby' (>= 1.1) among 121 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/user/.local/share/gem/ruby/3.0.0:/usr/lib/ruby/gems/3.0.0' , execute `gem env` for more information
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1451:in `block in activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `each'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1439:in `activate_dependencies'
        from /usr/lib/ruby/3.0.0/rubygems/specification.rb:1421:in `activate'
        from /usr/lib/ruby/3.0.0/rubygems.rb:286:in `block in activate_bin_path'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `synchronize'
        from /usr/lib/ruby/3.0.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/bin/asciidoctor-pdf:25:in `<main>'

Cheers

@culyun: Also the makepkg --nocheck option exists.

@culyun Having tests in the package is best practices and ensures the software is functional on Arch Linux. This provides a great value and comfort to packagers. The test failure for some users in this comment section is exactly why tests should be run. This time it was a problem with the test suite, but it could just as well have been a problem with the software that upstream failed to capture.

Long compilation and/or testing times is a consequence of AUR packages being built from source when you install them.

The end goal, for me, would be for this package to end up in [extra] and be distributed pre-built. This would eliminate the requirement for users to build it themselves. The more votes and users of this package (and others), the more likely that is to happen :)

2.3.9.3 resolves the test failures reported in 2.9.9.2. Thanks :-)

The tests take a long time to run on older hardware. Are they necessary as part of the PKGBUILD? Surely upstream runs regression tests against releases.

I've released a new pkgver with the failing tests removed and reported the issue upstream: https://github.com/asciidoctor/asciidoctor-pdf/issues/2444.