From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 34044@debbugs.gnu.org
Subject: [bug#34044] Packaging Jami (ex GNU Ring)
Date: Wed, 13 Mar 2019 19:51:42 +0100 [thread overview]
Message-ID: <87sgvq4ngh.fsf@elephly.net> (raw)
In-Reply-To: <87a7hyty0x.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Looking more closely, the closure of qtbase contains both sqlite packages has
> well.
> I suspect a bug in the qtbase package.
That might be because dependencies of qtbase don’t use that same sqlite
variant. Generally, we should make sure that we don’t have different
library variants in the closure.
What pulls in the vanilla sqlite package? Can we use input rewriting to
ensure that all references to sqlite are replaced with
sqlite-with-column-metadata? (This would require building package
variants.)
--
Ricardo
next prev parent reply other threads:[~2019-03-13 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 18:58 bug#34044: Packaging Jami (ex GNU Ring) Pierre Neidhardt
2019-01-11 21:37 ` Marius Bakke
2019-01-12 9:15 ` Pierre Neidhardt
2019-01-12 10:12 ` Gábor Boskovits
2019-03-13 15:00 ` [bug#34044] " Ricardo Wurmus
2019-03-13 18:44 ` Pierre Neidhardt
2019-03-13 18:51 ` Ricardo Wurmus [this message]
2019-03-14 8:29 ` Pierre Neidhardt
2019-03-14 14:45 ` Pierre Neidhardt
2019-03-14 14:49 ` Pierre Neidhardt
2019-03-14 17:26 ` Ricardo Wurmus
2019-03-14 17:38 ` Pierre Neidhardt
2019-03-14 17:40 ` Pierre Neidhardt
2019-03-14 18:00 ` Ricardo Wurmus
2019-03-14 18:01 ` Ricardo Wurmus
2019-03-14 18:15 ` Pierre Neidhardt
2019-03-14 18:34 ` Pierre Neidhardt
2019-03-17 21:50 ` Christopher Lemmer Webber
2019-03-18 7:41 ` Pierre Neidhardt
2019-03-25 8:32 ` Pierre Neidhardt
2019-03-25 15:19 ` Christopher Lemmer Webber
2019-03-26 18:26 ` Pierre Neidhardt
2019-03-26 18:41 ` Ricardo Wurmus
2019-03-27 1:52 ` Brett Gilio
2019-03-27 7:45 ` Pierre Neidhardt
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=87sgvq4ngh.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34044@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.