Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: exiv2: update to 0.28.0.
Date: Fri, 03 Nov 2023 21:18:12 +0100	[thread overview]
Message-ID: <20231103201812._SvH7PXavjE7MeggOLUiU0slixolRJQRi7JO3eQA-Gc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46838@inbox.vuxu.org>

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

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/pull/46838#issuecomment-1793043864

Comment:
This should be ready; the only problem is this:

```
=> nufraw-0.43.3_1: installing host dependencies: pkg-config-0.29.2_3 automake-1.16.5_1 libtool-2.4.7_4 ...
=> nufraw-0.43.3_1: installing target dependencies: gimp-devel-2.10.34_2 glib-devel-2.78.0_3 gtkimageview-devel-1.6.4_3 lcms2-devel-2.15_1 lensfun-devel-0.3.3_3 jasper-devel-2.0.25_1 exiv2-devel-0.28.0_1 ...
=> nufraw-0.43.3_1: removing autodeps, please wait...
=> ERROR: nufraw-0.43.3_1: failed to install target dependencies! (error 8)
libgexiv2-0.14.0_3: broken, unresolvable shlib `libexiv2.so.27'
Transaction aborted due to unresolved shlibs.
=> ERROR: Please see above for the real error, exiting...
```

For some reason xbps-src isn't automatically building the bumped libgexif2, I'm not sure how to fix it...

  parent reply	other threads:[~2023-11-03 20:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  0:10 [PR PATCH] " mhmdanas
2023-10-23  0:20 ` [PR PATCH] [Updated] " mhmdanas
2023-11-01 17:23 ` mhmdanas
2023-11-01 17:26 ` mhmdanas
2023-11-01 18:11 ` mhmdanas
2023-11-02 19:42 ` biopsin
2023-11-03 20:00 ` [PR PATCH] [Updated] " mhmdanas
2023-11-03 20:18 ` mhmdanas [this message]
2023-11-04 21:57 ` mhmdanas
2023-11-06 20:17 ` mhmdanas
2023-11-06 20:18 ` mhmdanas
2023-11-06 20:19 ` mhmdanas
2023-11-06 20:20 ` mhmdanas
2023-11-12 13:04 ` biopsin
2023-11-12 15:01 ` mhmdanas
2023-11-12 22:54 ` [PR PATCH] [Updated] " mhmdanas
2023-11-12 22:55 ` exiv2: update to 0.28.1 mhmdanas
2023-11-13  0:00 ` [PR PATCH] [Updated] " mhmdanas
2023-11-15 17:40 ` mhmdanas
2023-11-15 17:57 ` mhmdanas
2023-11-16 15:12 ` [PR REVIEW] " sh1r4s3
2023-11-16 15:56 ` mhmdanas
2023-11-16 16:43 ` sh1r4s3
2023-11-16 21:50 ` [PR PATCH] [Updated] " mhmdanas
2023-11-16 21:51 ` [PR REVIEW] " mhmdanas
2023-11-18 15:57 ` [PR PATCH] [Updated] " mhmdanas
2023-11-18 21:41 ` [PR PATCH] [Merged]: " classabbyamp

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=20231103201812._SvH7PXavjE7MeggOLUiU0slixolRJQRi7JO3eQA-Gc@z \
    --to=mhmdanas@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).