From: rubin55 <rubin55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openjpeg2-32bit: MISSING: libopenjpeg2-32bit-2.3.0_1
Date: Thu, 03 Mar 2022 14:41:41 +0100 [thread overview]
Message-ID: <20220303134141.IdNZ29cKe3fDND_Zqvx8V8owVrNzShGtcEolE1Fxf7E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35772@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
New comment by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/35772#issuecomment-1058049561
Comment:
It does not work (I have multilib enabled of course):
```
$ sudo xbps-query -l | grep void-repo-multilib
ii void-repo-multilib-6_3 Void Linux drop-in file for the multilib repository
$ sudo xbps-install -Suv
sudo xbps-install openjpeg2-32bit
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/x86_64-repodata' ...
MISSING: libopenjpeg2-32bit-2.3.0_1
Transaction aborted due to unresolved dependencies.
```
I see a version difference: `openjpeg2-32bit` depends on `libopenjpeg2-32bit-2.3.0_1`, but I have `libopenjpeg2-32bit-2.4.0_2`
It seems to me that either `openjpeg2-32bit` should not exist in the repo (I.e., it was removed in the later 2.4.0_2` build, but the package was never removed from the repository) or `openjpeg2-32bit` *should* exist, but its dependencies are wrong.
next prev parent reply other threads:[~2022-03-03 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:41 [ISSUE] " rubin55
2022-02-24 21:55 ` abenson
2022-02-25 10:30 ` rubin55
2022-03-03 13:35 ` ZyxerZyxani
2022-03-03 13:37 ` rubin55
2022-03-03 13:39 ` rubin55
2022-03-03 13:41 ` rubin55 [this message]
2022-03-03 13:42 ` rubin55
2022-03-03 16:43 ` rubin55
2022-03-03 18:59 ` [ISSUE] [CLOSED] " paper42
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=20220303134141.IdNZ29cKe3fDND_Zqvx8V8owVrNzShGtcEolE1Fxf7E@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).