From: "Gábor Boskovits" <boskovits@gmail.com>
To: 31719@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>
Subject: bug#31719: icedtea-3 binaries contain references to icedtea-2
Date: Tue, 5 Jun 2018 13:49:12 +0200 [thread overview]
Message-ID: <CAE4v=pgmd_B9UBEVT+DQ7Ypd7ZdeLcT7zZQJh-C1VuDc5cCBLg@mail.gmail.com> (raw)
In-Reply-To: <877end1pda.fsf@mdc-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Do you think we can do something like rebuild icedtea3 with icedtea3, and
then rewrite the references? I guess this way the dependency loop could be
broken, as we could detach the last icedtea3 build from the packages used
for bootstrapping.
We could even make on more rebuilding, if necessary. WDYT?
[-- Attachment #2: Type: text/html, Size: 348 bytes --]
next prev parent reply other threads:[~2018-06-05 11:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 10:47 bug#31719: icedtea-3 binaries contain references to icedtea-2 Ricardo Wurmus
2018-06-05 11:49 ` Gábor Boskovits [this message]
2018-06-05 12:36 ` Ricardo Wurmus
2018-06-05 12:45 ` Leo Famulari
2018-06-05 14:45 ` Gábor Boskovits
2018-09-10 21:00 ` Gábor Boskovits
2020-05-14 18:02 ` Ricardo Wurmus
2021-02-27 11:17 ` bug#31719: Chains of dependencies getting longer Andreas Enge
2021-03-01 10:04 ` Ludovic Courtès
2021-03-01 12:00 ` Andreas Enge
2021-03-01 21:33 ` Ludovic Courtès
2021-03-01 22:15 ` Björn Höfling
2021-04-14 7:36 ` Ricardo Wurmus
2021-04-16 19:22 ` Björn Höfling
2021-04-16 22:26 ` Carlo Zancanaro
2021-04-17 7:11 ` Carlo Zancanaro
2021-04-17 9:38 ` Carlo Zancanaro
2021-04-19 16:22 ` Andreas Enge
2021-04-19 18:18 ` Ricardo Wurmus
2021-04-20 8:34 ` Andreas Enge
2021-04-20 9:24 ` bug#31719: icedtea-3 binaries contain references to icedtea-2 Ludovic Courtès
2021-04-20 9:36 ` Andreas Enge
2021-04-20 11:32 ` Carlo Zancanaro
2021-04-20 16:38 ` Ludovic Courtès
2021-04-20 21:00 ` Carlo Zancanaro
2021-04-21 12:40 ` Ludovic Courtès
2021-04-20 9:01 ` bug#31719: Chains of dependencies getting longer Carlo Zancanaro
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pgmd_B9UBEVT+DQ7Ypd7ZdeLcT7zZQJh-C1VuDc5cCBLg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=31719@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.