Github messages for voidlinux
 help / color / mirror / Atom feed
From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openldap: update to 2.6.4
Date: Wed, 03 May 2023 18:08:30 +0200	[thread overview]
Message-ID: <20230503160830.tCNMfK3iB4Go8_hF0e2zellk4EtaaoB7SFO2wRMLlZk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41948@inbox.vuxu.org>

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

New comment by klarasm on void-packages repository

https://github.com/void-linux/void-packages/pull/41948#issuecomment-1533318144

Comment:
The biggest holdup now is apr-util, a change in the libtool package broke cross-compilation for it and that was not fixed initially. As this PR revbumps apr-util cross-compilation of it would fail without the update (quite a few packages also depend on it).
The virtuoso update is not as critical (the test suite was already failing before).

Otherwise more testing would probably help. I'll rebase this again and rerun tests when I have time.

  parent reply	other threads:[~2023-05-03 16:08 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 23:49 [PR PATCH] openldap: update to 2.6.3 klarasm
2023-01-31 23:28 ` [PR PATCH] [Updated] " klarasm
2023-01-31 23:31 ` klarasm
2023-01-31 23:55 ` [PR PATCH] [Updated] " klarasm
2023-02-01  0:32 ` klarasm
2023-02-01  0:47 ` [PR PATCH] [Updated] " klarasm
2023-02-01  1:22 ` klarasm
2023-02-01  2:11 ` klarasm
2023-02-01 14:20 ` [PR PATCH] [Updated] " klarasm
2023-02-01 14:29 ` klarasm
2023-02-01 14:37 ` klarasm
2023-02-01 14:57 ` klarasm
2023-02-01 15:24 ` klarasm
2023-02-01 15:44 ` klarasm
2023-02-01 15:53 ` klarasm
2023-02-01 16:01 ` klarasm
2023-02-01 16:04 ` klarasm
2023-02-01 19:47 ` [PR PATCH] [Updated] " klarasm
2023-02-01 19:50 ` klarasm
2023-02-01 20:49 ` [PR PATCH] [Updated] " klarasm
2023-02-01 20:50 ` klarasm
2023-02-01 21:49 ` [PR PATCH] [Updated] " klarasm
2023-02-01 21:50 ` klarasm
2023-02-01 22:59 ` [PR PATCH] [Updated] " klarasm
2023-02-01 23:01 ` klarasm
2023-02-01 23:33 ` [PR PATCH] [Updated] " klarasm
2023-02-01 23:35 ` klarasm
2023-02-02 11:50 ` klarasm
2023-02-02 13:38 ` klarasm
2023-02-02 20:20 ` klarasm
2023-02-03 15:41 ` dkwo
2023-02-03 15:50 ` dkwo
2023-02-03 16:01 ` klarasm
2023-02-03 16:21 ` kruceter
2023-02-03 16:26 ` klarasm
2023-02-03 16:29 ` kruceter
2023-02-03 16:34 ` klarasm
2023-02-03 16:45 ` [PR REVIEW] " paper42
2023-02-03 16:45 ` paper42
2023-02-03 16:45 ` paper42
2023-02-03 16:45 ` paper42
2023-02-03 16:45 ` paper42
2023-02-03 16:46 ` paper42
2023-02-03 16:46 ` klarasm
2023-02-03 16:49 ` klarasm
2023-02-03 17:05 ` paper42
2023-02-03 17:16 ` klarasm
2023-02-03 17:20 ` klarasm
2023-02-03 17:30 ` klarasm
2023-02-03 17:41 ` [PR REVIEW] " klarasm
2023-02-03 18:14 ` [PR PATCH] [Updated] " klarasm
2023-02-03 18:34 ` dkwo
2023-02-04  0:25 ` [PR PATCH] [Updated] " klarasm
2023-02-06 17:32 ` klarasm
2023-02-14 20:51 ` klarasm
2023-02-15  0:34 ` [PR PATCH] [Updated] " klarasm
2023-02-15 16:22 ` [PR PATCH] [Updated] openldap: update to 2.6.4 klarasm
2023-02-15 16:23 ` klarasm
2023-02-16 11:59 ` klarasm
2023-02-23 19:50 ` paper42
2023-02-23 21:05 ` [PR PATCH] [Updated] " klarasm
2023-03-02 14:53 ` klarasm
2023-03-05 21:05 ` klarasm
2023-03-06 19:40 ` [PR REVIEW] " paper42
2023-03-06 21:54 ` klarasm
2023-03-08 18:49 ` [PR PATCH] [Updated] " klarasm
2023-03-08 19:29 ` klarasm
2023-04-01 11:28 ` klarasm
2023-04-06 21:19 ` klarasm
2023-04-15 18:01 ` klarasm
2023-04-25  7:05 ` klarasm
2023-05-03 15:05 ` Emru1
2023-05-03 16:08 ` klarasm [this message]
2023-05-03 19:23 ` [PR PATCH] [Updated] " klarasm
2023-05-03 19:28 ` klarasm
2023-05-05 17:19 ` klarasm
2023-05-05 17:37 ` klarasm
2023-05-05 17:39 ` klarasm
2023-05-09  8:20 ` klarasm
2023-05-09  8:44 ` klarasm
2023-05-09 12:59 ` [PR PATCH] [Updated] " klarasm
2023-05-09 13:31 ` klarasm
2023-05-09 13:32 ` klarasm
2023-05-12 18:49 ` [PR PATCH] [Updated] " klarasm
2023-05-14 10:16 ` klarasm
2023-05-17 16:01 ` klarasm
2023-05-30 14:04 ` klarasm
2023-05-30 14:33 ` klarasm
2023-06-11 17:02 ` klarasm
2023-06-19 20:22 ` klarasm
2023-06-25 21:05 ` klarasm
2023-07-12 15:58 ` klarasm
2023-07-12 16:54 ` [PR PATCH] [Updated] " klarasm
2023-07-21 16:55 ` [PR PATCH] [Updated] openldap: update to 2.6.5 klarasm
2023-07-29 22:58 ` klarasm
2023-08-04 16:24 ` klarasm
2023-08-08 22:59 ` [PR PATCH] [Updated] openldap: update to 2.6.6 klarasm
2023-08-22 21:20 ` klarasm
2023-08-22 21:26 ` klarasm
2023-08-28 12:26 ` [PR PATCH] [Updated] " klarasm
2023-08-30 17:15 ` klarasm
2023-09-09 12:14 ` klarasm
2023-09-14 12:24 ` klarasm
2023-09-17 18:44 ` klarasm
2023-09-17 18:57 ` [PR PATCH] [Merged]: " the-maldridge
2023-09-17 19:57 ` klarasm

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=20230503160830.tCNMfK3iB4Go8_hF0e2zellk4EtaaoB7SFO2wRMLlZk@z \
    --to=klarasm@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).