From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Updating java-commons-io?
Date: Sun, 22 Dec 2024 20:05:02 +0100 [thread overview]
Message-ID: <8734ifedy9.fsf@elephly.net> (raw)
In-Reply-To: <3f67fb9a-01fa-4482-a64d-13aaeb92cc72@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 22 Dec 2024 18:00:35 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> how to update java-commons-io?
Consider *adding* a more recent version instead of replacing it.
There's a chance we need the older version for the early Java dependency
graph. Upgrading packages close to the root is pretty messy.
--
Ricardo
next prev parent reply other threads:[~2024-12-22 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 17:00 Updating java-commons-io? Hartmut Goebel
2024-12-22 19:05 ` Ricardo Wurmus [this message]
2024-12-22 22:55 ` Hartmut Goebel
2024-12-22 20:02 ` Julien Lepiller
2024-12-22 22:56 ` Hartmut Goebel
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=8734ifedy9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).