unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Helmut Grohne <helmut@subdivi.de>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 54276@debbugs.gnu.org, 990250-done@bugs.debian.org
Subject: bug#54276: Bug#990250: guile-2.2 FTBFS on musl: dh_missing complains about charset.alias
Date: Sun, 6 Mar 2022 19:11:54 +0100	[thread overview]
Message-ID: <YiT5avHJwuLee8co@alf.mars> (raw)
In-Reply-To: <87k0d7hs9n.fsf@trouble.defaultvalue.org>

Hi Rob,

On Sun, Mar 06, 2022 at 12:04:20PM -0600, Rob Browning wrote:
> Hmm, it looks like this may have changed in more recent 3.0 releases
> (i.e. need_charset_alias is no longer mentioned anywhere in the tree).
> I wonder if that means we need a different patch, or perhaps the problem
> has been resolved.

Thank you for looking into this. I'm unsure at this point and we cannot
really tell as jenkins has no signal in the noise of temporary failing
builds since a while. Thus closing. If it happens to still be an issue,
I'll file a new bug with a new patch.

Just next time, please be a little quicker, ok? ;)

Helmut






      parent reply	other threads:[~2022-03-06 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YNOmbrzdJLuIvyEG@alf.mars>
2022-03-06 17:56 ` bug#54276: Bug#990250: guile-2.2 FTBFS on musl: dh_missing complains about charset.alias Rob Browning
2022-03-06 18:04   ` Rob Browning
     [not found]   ` <87k0d7hs9n.fsf@trouble.defaultvalue.org>
2022-03-06 18:11     ` Helmut Grohne [this message]

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YiT5avHJwuLee8co@alf.mars \
    --to=helmut@subdivi.de \
    --cc=54276@debbugs.gnu.org \
    --cc=990250-done@bugs.debian.org \
    --cc=rlb@defaultvalue.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 read-only IMAP folder(s) and NNTP newsgroup(s).