Github messages for voidlinux
 help / color / mirror / Atom feed
From: dmarto <dmarto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some 32bit packages don't have the deps correctly rewritten to -32bit packages
Date: Thu, 30 Sep 2021 06:24:03 +0200	[thread overview]
Message-ID: <20210930042403.0UhrUhx1Z05l12PTwLeXnP-WfQ_c6E6_b_zfOBxQG6c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23368@inbox.vuxu.org>

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

New comment by dmarto on void-packages repository

https://github.com/void-linux/void-packages/issues/23368#issuecomment-930767836

Comment:
I don't know the status of the issue (as it is a bit old), I am just passing to report 2 such packages
 #### `pango-devel-32bit`
```
makedepends="fribidi-devel harfbuzz-devel libXft-devel libthai-devel"
depends="${makedepends} pango-xft>=${version}_${revision} pango>=${version}_${revision}"
```
All, but `pango` it self, are not rewritten to the 32bit versions.

#### `eudev-libudev-devel-32bit`
`eudev-libudev-devel-32bit` is depending on `eudev-libudev`  and `eudev-libudev-devel`

I find the latter dependency extra strange, and that threw me in a circle that led to the edits of my comment. 

--

As usual, I am happy to help in any way, if I get a pointer or two (pun slightly intended) I am willing to go dig inside xbps to try and fix that.  

  parent reply	other threads:[~2021-09-30  4:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23368@inbox.vuxu.org>
2020-09-29 22:26 ` ericonr
2021-09-30  4:16 ` dmarto
2021-09-30  4:17 ` dmarto
2021-09-30  4:19 ` dmarto
2021-09-30  4:24 ` dmarto [this message]
2021-10-07  8:02 ` dmarto
2021-10-13  5:27 ` ericonr
2021-10-13  5:28 ` ericonr
2021-10-13 19:43 ` Chocimier
2022-04-17  2:06 ` github-actions
2022-07-19  2:14 ` github-actions

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=20210930042403.0UhrUhx1Z05l12PTwLeXnP-WfQ_c6E6_b_zfOBxQG6c@z \
    --to=dmarto@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).