From: rubin55 <rubin55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Various 32bit packages with broken dependencies
Date: Thu, 03 Mar 2022 18:01:18 +0100 [thread overview]
Message-ID: <20220303170118.8g4gzBCBFgYd6JN_XQ4NHBSTEDAJmNxbnlYwlvu-8rA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35948@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
New comment by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/35948#issuecomment-1058264059
Comment:
@ZyxerZyxani I'm not so sure, I think `openjpeg2-32bit` and `file-32bit` are old leftovers themselves and simply have those old dependencies because they are still in the repository, pointing to its dependencies at the time, even though the srcpkg is updated which doesn't create these anymore. Not 100% sure about that though.
next prev parent reply other threads:[~2022-03-03 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:41 [ISSUE] " rubin55
2022-03-03 16:58 ` ZyxerZyxani
2022-03-03 17:01 ` rubin55 [this message]
2022-03-03 17:02 ` rubin55
2022-06-27 2:16 ` github-actions
2022-06-27 12:54 ` rubin55
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=20220303170118.8g4gzBCBFgYd6JN_XQ4NHBSTEDAJmNxbnlYwlvu-8rA@z \
--to=rubin55@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).