• Bug#1064554: jruby fails to build from source in unstable

    From Vladimir Petko@21:1/5 to All on Sat Feb 24 09:00:02 2024
    Source: jruby
    Version: 9.4.5.0+ds-1
    Severity: serious

    Dear Maintainer,

    When building jruby in unstable, the following error occurs:

    [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install- plugin:3.1.1:install (default-install) on project jruby-parent: Failed to install artifact org.jruby:jruby-parent:pom:9.4.5.0: /<<PKGBUILDDIR>>/debian/maven-repo/org/jruby/jruby-parent/9.4.5.0/jruby- parent-9.4.5.0.pom (Permission denied) -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<<BUILDDIR>>/jruby-9.4.5.0\+ds -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<<BUILDDIR>>/jruby-9.4.5.0\+ds/debian/maven.properties
    org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings- debian.xml -Ddebian.dir=/<<BUILDDIR>>/jruby-9.4.5.0\+ds/debian -Dmaven.repo.local=/<<BUILDDIR>>/jruby-9.4.5.0\+ds/debian/maven-repo --batch- mode -Djruby.revision=9.4.5.0\+ds-1build1\~ppa2 -Pmain,complete,dist -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
    make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:9: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------
    Build finished at 2024-02-24T07:14:56Z

    This is due to maven-repo-helper copying symlinks to jruby poms rather than poms themselves.

    One possible solution is to copy jruby poms manually in execute_after_dh_auto_configure:
    # copy jruby poms rather than links, because the build will try to patch them
    for p in jruby jruby-parent jruby-base jruby-core jruby-artifacts ; do \
    rm debian/maven-repo/org/jruby/$$p/* ;\
    mkdir debian/maven-repo/org/jruby/$$p/debian ; \
    cp /usr/share/maven-repo/org/jruby/$$p/debian/* debian/maven- repo/org/jruby/$$p/debian/ ;\
    done




    -- System Information:
    Debian Release: trixie/sid
    APT prefers mantic-updates
    APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports')
    Architecture: amd64 (x86_64)
    Foreign Architectures: i386

    Kernel: Linux 6.5.0-17-generic (SMP w/32 CPU threads; PREEMPT)
    Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Feb 29 07:20:02 2024
    This is a multi-part message in MIME format...

    Your message dated Thu, 29 Feb 2024 06:10:06 +0000
    with message-id <E1rfZcM-009pLm-MA@fasolo.debian.org>
    and subject line Bug#1064554: fixed in jruby 9.4.6.0+ds-1
    has caused the Debian Bug report #1064554,
    regarding jruby fails to build from source in unstable
    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.)


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

    Received: (at submit) by bugs.debian.org; 24 Feb 2024 07:53:53 +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=-2.0 required=4.0 tests=BAYES_00,FOURLA,HELO_LH_HOME,
    RCVD_IN_PBL,RDNS_NONE,SPF_FAIL,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE,
    XMAILER_REPORTBUG autolearn=no autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 51; hammy, 150; neutral, 214; spammy,
    0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O,
    0.000-+--trixie
    Return-path: <vladimir.petko@canonical.com>
    Received: from [203.211.106.87] (port=31731 helo=vladimirp.Home)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
    (Exim 4.94.