unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 74206@debbugs.gnu.org
Subject: [bug#74206] [PATCH v2] gnu: Fix java-jaxen.
Date: Wed, 20 Nov 2024 00:52:49 +0100	[thread overview]
Message-ID: <84f47b7deabeb34f39d0e26b2cbeb7d79bc99092.1732060243.git.h.goebel@crazy-compilers.com> (raw)
In-Reply-To: <5715f36b461fb1bd61966a21f7b69fc6049955a2.1730755471.git.h.goebel@crazy-compilers.com>

java-jaxen was missing the dom4j and xom sub-packages. This was caused by
java-jaxen-bootstrap deleting the respective directories (which is okay) and
java-javen not removing the phase that does this.

Solve this by removing the #:phases argument for java-jaxen and thus make guix
use the default phases.

* gnu/packages/java-xml.scm (java-jaxen)[arguments]: Remove #:phases.
, making
---
 gnu/packages/java-xml.scm | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gnu/packages/java-xml.scm b/gnu/packages/java-xml.scm
index 9ec11fa83e..0153e26ef8 100644
--- a/gnu/packages/java-xml.scm
+++ b/gnu/packages/java-xml.scm
@@ -241,6 +241,10 @@ (define-public java-jaxen
   (package
     (inherit java-jaxen-bootstrap)
     (name "java-jaxen")
+    (arguments
+     (strip-keyword-arguments
+      '(#:phases)  ;; remove any phases added by java-jaxen-bootstrap
+      (package-arguments java-jaxen-bootstrap)))
     (inputs
      (list java-jdom java-xom java-dom4j))))
 

base-commit: 33665c52c4670bc3b4d337c89ac9cc6c4c69b26f
-- 
2.41.1





      parent reply	other threads:[~2024-11-19 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 21:26 [bug#74206] [PATCH] gnu: Fix java-jaxen Hartmut Goebel
2024-11-08 10:57 ` Liliana Marie Prikler
2024-11-08 14:47   ` Hartmut Goebel
2024-11-08 14:56     ` Liliana Marie Prikler
2024-11-19 23:52 ` Hartmut Goebel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84f47b7deabeb34f39d0e26b2cbeb7d79bc99092.1732060243.git.h.goebel@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=74206@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).