Github messages for voidlinux
 help / color / mirror / Atom feed
From: rubin55 <rubin55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Various 32bit packages with broken dependencies
Date: Thu, 03 Mar 2022 17:41:02 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35948@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

New issue by rubin55 on void-packages repository

https://github.com/void-linux/void-packages/issues/35948

Description:
Various 32bit packages in multilib have broken dependencies. This might be because they are old (i.e., newer versions of the package don't create the -32bit variant package anymore but the old one sticks around) and should be removed from multilib:

I initially created dedicated issues for these, but as requested by @abenson and @Chocimier I've brought them together in one issue.

* udisks2-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5 (was #35773) 
* openjpeg2-32bit: MISSING: libopenjpeg2-32bit-2.3.0_1 (was #35772) 
* libreoffice-[common, gnome, writer]-32bit: MISSING: openldap-32bit>=0 (was #35770)
* libblockdev-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5 (was #35769)
* gvfs-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5 (was #35766)
* gnome-settings-daemon-32-bit: MISSING: geoclue2-32bit>=2.4.4_1 (was #35765)
* gnome-bluetooth-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5 (was #35764)
* fwupd-32bit: MISSING: dmraid-32bit>=1.0.0.rc16.3_5 (was #35763)
* file-32bit: MISSING: libmagic-32bit-5.40_1 (was #35762) 

             reply	other threads:[~2022-03-03 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 16:41 rubin55 [this message]
2022-03-03 16:58 ` ZyxerZyxani
2022-03-03 17:01 ` rubin55
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35948@inbox.vuxu.org \
    --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).