From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: bootstrap fails for missing debuginfod
Date: Wed, 16 Dec 2020 01:53:40 +0100 [thread overview]
Message-ID: <20201216005340.-XqlGJrwozIVc1P4mxd8eJ7-SO3895DbfMJ0SUbkdQQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27190@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745692444
Comment:
Peeking at the stage0 `x86_64-repodata` I see it is the `binutils` referring to `debuginfod`:
```xml
<key>binutils</key>
<dict>
<key>architecture</key>
<string>x86_64</string>
<key>filename-sha256</key>
<string>3618d892f6c72dbfd156649d2777f617e727bd7bd3ca6a89e65c889bd01483d1</string>
<key>filename-size</key>
<integer>5650737</integer>
<key>homepage</key>
<string>http://www.gnu.org/software/binutils/</string>
<key>installed_size</key>
<integer>27194915</integer>
<key>license</key>
<string>GPL-3.0-or-later</string>
<key>maintainer</key>
<string>Enno Boland <gottox@voidlinux.org></string>
<key>pkgver</key>
<string>binutils-2.34_1</string>
<key>run_depends</key>
<array>
<string>zlib>=1.2.3_1</string>
<string>glibc>=2.29_1</string>
<string>libdebuginfod>=0.182_1</string>
<string>libstdc++>=4.4.0_1</string>
<string>libgcc>=4.4.0_1</string>
</array>
<key>shlib-requires</key>
<array>
<string>libz.so.1</string>
<string>libdl.so.2</string>
<string>libc.so.6</string>
<string>libdebuginfod.so.1</string>
<string>libstdc++.so.6</string>
<string>libgcc_s.so.1</string>
<string>libpthread.so.0</string>
</array>
<key>short_desc</key>
<string>GNU binary utilities</string>
</dict>
```
next prev parent reply other threads:[~2020-12-16 0:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 23:54 [ISSUE] " pullmoll
2020-12-16 0:05 ` q66
2020-12-16 0:10 ` pullmoll
2020-12-16 0:12 ` q66
2020-12-16 0:13 ` pullmoll
2020-12-16 0:14 ` q66
2020-12-16 0:17 ` pullmoll
2020-12-16 0:20 ` pullmoll
2020-12-16 0:21 ` q66
2020-12-16 0:22 ` pullmoll
2020-12-16 0:26 ` pullmoll
2020-12-16 0:53 ` pullmoll [this message]
2020-12-16 0:56 ` ericonr
2020-12-16 0:58 ` pullmoll
2020-12-16 1:00 ` pullmoll
2020-12-16 1:03 ` pullmoll
2020-12-16 1:05 ` q66
2020-12-16 1:08 ` pullmoll
2020-12-16 1:10 ` pullmoll
2020-12-16 1:49 ` pullmoll
2020-12-26 2:44 ` [ISSUE] [CLOSED] " q66
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=20201216005340.-XqlGJrwozIVc1P4mxd8eJ7-SO3895DbfMJ0SUbkdQQ@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).