• Bug#1100307: ruby-gelf: FTBFS:

    From Santiago Vila@21:1/5 to All on Wed Mar 12 17:40:08 2025
    Package: src:ruby-gelf
    Version: 3.1.0-2
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

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

    --------------------------------------------------------------------------------
    [...]
    debian/rules clean
    dh clean --buildsystem=ruby --with ruby
    dh_auto_clean -O--buildsystem=ruby
    dh_ruby --clean
    W: XS-Ruby-Versions is deprecated, and will be ignored
    dh_autoreconf_clean -O--buildsystem=ruby
    dh_clean -O--buildsystem=ruby
    debian/rules binary
    dh binary --buildsystem=ruby --with ruby
    dh_update_autotools_config -O--buildsystem=ruby
    dh_autoreconf -O--buildsystem=ruby
    dh_auto_configure -O--buildsystem=ruby
    dh_ruby --configure
    dh_auto_build -O--buildsystem=ruby
    dh_ruby --build
    dh_auto_test -O--buildsystem=ruby
    dh_ruby --test
    create-stamp debian/debhelper-build-stamp
    dh_testroot -O--buildsystem=ruby
    dh_prep -O--buildsystem=ruby
    dh_auto_install --destdir=debian/ruby-gelf/ -O--buildsystem=ruby
    dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-gelf

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ ruby-gelf: Install files │
    └──────────────────────────────────────────────────────────────────────────────┘

    install -d /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/logger.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/logger.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/notifier.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/notifier.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/severity.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/severity.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/transport/tcp.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/transport/tcp.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/transport/tcp_tls.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/transport/tcp_tls.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf/transport/udp.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf/transport/udp.rb
    install -D -m644 /<<PKGBUILDDIR>>/lib/gelf.rb /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby/gelf.rb

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ ruby-gelf: Install Rubygems integration metadata │
    └──────────────────────────────────────────────────────────────────────────────┘

    generating gemspec at /<<PKGBUILDDIR>>/debian/ruby-gelf/usr/share/rubygems-integration/all/specifications/gelf-3.1.0.gemspec
    dh_installchangelogs -pruby-gelf /<<PKGBUILDDIR>>/CHANGELOG upstream /usr/bin/ruby3.3 /usr/bin/gem2deb-test-runner

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ Run tests for ruby3.3 from debian/ruby-tests.rb │
    └──────────────────────────────────────────────────────────────────────────────┘

    RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-gelf/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-gelf/usr/share/rubygems-integration/all:/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.3.0:/var/lib/gems/3.3.0:/
    usr/local/lib/ruby/gems/3.3.0:/usr/lib/ruby/gems/3.3.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.3.0:/usr/share/rubygems-integration/3.3.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.3.0 ruby3.3 debian/ruby-tests.rb
    mv Gemfile.lock ./.gem2deb.Gemfile.lock <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- mocha/setup (LoadError)
    from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:136:in `require'
    from /<<PKGBUILDDIR>>/test/helper.rb:4:in `<top (required)>'
    from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:136:in `require'
    from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:136:in `require'
    from debian/ruby-tests.rb:2:in `<main>'
    mv ./.gem2deb.Gemfile.lock Gemfile.lock
    ERROR: Test "ruby3.3" failed. Exiting.
    dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-gelf returned exit code 1
    make: *** [debian/rules:15: 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.

    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.

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

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Fri Apr 25 11:00:02 2025
    This is a multi-part message in MIME format...

    Your message dated Fri, 25 Apr 2025 08:55:46 +0000
    with message-id <E1u8EqY-004Ffz-79@fasolo.debian.org>
    and subject line Bug#1090866: fixed in ruby-gelf 3.1.0-3.1
    has caused the Debian Bug report #1090866,
    regarding ruby-gelf: FTBFS: <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:136:in `require': cannot load such file -- mocha/setup
    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@bugs.debian.org
    immediately.)


    --
    1090866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090866
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 12 Mar 2025 16:34:05 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-119.9 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,
    PP_MIME_FAKE_ASCII_TEXT,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_NONE,
    USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 31; hammy, 150; neutral, 163; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--sk:dh_auto, 0.000-+--H*F:U*sanvila Return-path: <sanvila@debian.org>
    Received: from mitropoulos.debian.org