From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 61616-done@debbugs.gnu.org
Subject: bug#61616: [PATCH] gnu: komikku: Update to 1.12.0.
Date: Sun, 05 Mar 2023 09:48:06 +0100 [thread overview]
Message-ID: <2415d80e01afd0290ccd51ed362fccbb5d0ccd08.camel@gmail.com> (raw)
In-Reply-To: <ab7ddd1aefc3f3be6473af87e7b9abb9f48c0225.camel@gmail.com>
Am Samstag, dem 04.03.2023 um 19:28 +0100 schrieb Liliana Marie
Prikler:
> Am Samstag, dem 04.03.2023 um 18:50 +0100 schrieb Liliana Marie
> Prikler:
> > Am Samstag, dem 04.03.2023 um 18:40 +0100 schrieb Ludovic Courtès:
> > > Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> > >
> > > > * gnu/packages/gnome.scm (komikku): Update to 1.12.1.
> > >
> > > This seems to break a few packages:
> > >
> > > https://qa.guix.gnu.org/issue/61616
> > >
> > > Could you take a look?
> > Komikku is a leaf package, it shouldn't affect openmpi at all.
> > Perhaps that's a flaky package?
> Following up on this:
> > ice-9/read.scm:126:4: In procedure read-expr*:
> > /gnu/store/snf3n2cv3676c4l0axc5r6p5pd7rjklq-openmpi-thread-
> > multiple-
> > 4.1.4-builder:1:4765: Unknown # object: "#<"
> This appears to indicate a broken (possibly corrupted?) input file.
> WDYT?
At least one of the packages still builds locally, so I pushed the
change now. Let's watch what CI does.
Cheers
next prev parent reply other threads:[~2023-03-05 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 8:19 [bug#61616] [PATCH] gnu: komikku: Update to 1.12.0 Liliana Marie Prikler
2023-02-26 8:42 ` [bug#61616] [PATCH v2] gnu: komikku: Update to 1.12.1 Liliana Marie Prikler
2023-03-04 17:40 ` [bug#61616] [PATCH] gnu: komikku: Update to 1.12.0 Ludovic Courtès
2023-03-04 17:50 ` Liliana Marie Prikler
2023-03-04 18:28 ` Liliana Marie Prikler
2023-03-05 8:48 ` Liliana Marie Prikler [this message]
2023-03-06 15:54 ` Ludovic Courtès
2023-03-06 17:54 ` Liliana Marie Prikler
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=2415d80e01afd0290ccd51ed362fccbb5d0ccd08.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=61616-done@debbugs.gnu.org \
--cc=ludo@gnu.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.
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.