Hi Ludo,
Ludovic Courtès writes:
> Do you think this could be turned into a Guix System service, with an
> eye towards making it run on project infrastructure?
I need to revisit what you did with Disarchive and Cuirass. The process
for the PoG report is very similar. I can’t jump into it righ
Hey,
Simon Tournier writes:
> Well, I do not remember if you consider also the ’origin’
> (fixed-outputs) as ’inputs’ or ’patches’. Do you?
I’m quite confident I’m getting everything. I’ll describe my approach,
because I’m happy with it. :)
The Guix package graph exists twice, essentially.
Hey Ludo,
Ludovic Courtès writes:
> I copied over the 12K entries that were missing from
> disarchive.guix.gnu.org. (Note that there are currently only two copies
> of the database: one at/in [bB]erlin, and one at/in [Bb]ordeaux.)
> disarchive.guix.gnu.org now weighs in at 1.8 GiB for 31,839 en
Am Sat, Mar 18, 2023 at 10:43:17AM +0100 schrieb Lars-Dominik Braun:
> Anything else that needs work?
Well, there is pyqt as written elsewhere, but this is not only python.
I just updated python-ipython to the first version that passes all tests
without any change, in the hope that this would hav
Am Sat, Mar 18, 2023 at 12:15:34PM +0100 schrieb Liliana Marie Prikler:
> Feel free to promote it into a snippet. I didn't, because it only
> affects the build files rather than the package being built.
Okay, I did and pushed, many thanks again!
Andreas
Am Sat, Mar 18, 2023 at 01:38:48PM -0400 schrieb Leo Famulari:
> I recommend trying the latest upstream version, 4.0.3. The Sourceforge
> download page points to the new canonical location:
I already tried, it does not change anything. If I mess with the package,
I would in any case update the ver
On Fri, Mar 17, 2023 at 08:24:44AM -0700, Felix Lechner via Development of GNU
Guix and the GNU System distribution. wrote:
> Instead of dividing similar tasks among many people with different
> priorities, I would appoint a "feature branch manager" (or perhaps,
> chief pruner).
>
> That person's
I recommend trying the latest upstream version, 4.0.3. The Sourceforge
download page points to the new canonical location:
https://gitlab.com/procps-ng/procps
If that doesn't work, I would just disable the test, unless there is
some authoritative upstream opinion about which patch to apply.
Am Sat, Mar 18, 2023 at 04:36:26PM + schrieb Kaelyn:
> I'm at a complete loss as to why the patch won't apply properly.
Ah, the joys of email formatting maybe.
> I've attached the original patch as generated by "git format-patch
Thanks, I applied and pushed it and am closing the bug.
Andrea
--- Original Message ---
On Saturday, March 18th, 2023 at 8:56 AM, Andreas Enge wrote:
>
>
> Hello,
>
> Am Fri, Mar 17, 2023 at 08:43:13PM + schrieb Kaelyn:
>
> > I'm at least a little in favor of that, as the commit message for
> > cc56be2f3858487cf1d8acfb345942f0784221ee is mi
Hello!
Am Wed, Mar 15, 2023 at 05:47:08PM +0100 schrieb Ludovic Courtès:
> I’ve just changed it the ‘core-updates’ job to build
> ‘etc/release-manifests.scm’ (you can check what’s in there). So
> everything goes well (a big “if” :-)), we’ll soon have substitutes for
> Emacs, GTK, and whatnot.
th
Hello,
the attached patch seems to be necessary to start configuring python-pyqt
in core-updates.
But then the configure step still fails. The error message of "guix build"
is not helpful, but running the configure step in the result of "guix build -K"
shows the following:
...
The interpreter use
Hello,
procps fails its tests on core-updates when built with --system=i686-linux
(it succeeds on x86_64).
The error is completely not understandable (and Debian has disabled the test).
I modified the test file as attached; my changes are to compute the value val
separately before the "if" (inter
Just a quick reminder ;)
The patch series is 62202.
I can squash the commits if this is too precise, you can tell me ;)
Have a great week-end.
On 2023-03-15 13:43, Nicolas Graves wrote:
> Hi all!
>
> Took me quite more time than I would've liked, but I have a usable
> juliahub scheme impo
Am Samstag, dem 18.03.2023 um 11:36 +0100 schrieb Andreas Enge:
> Am Sat, Mar 18, 2023 at 12:00:49AM +0100 schrieb Liliana Marie
> Prikler:
> > This error is caused by trying to install
> > '/gnu/store/mxp199mvjb6dhyyg0pi4hn6c7m0xibvp-bash-completion-
> > 2.11/share/bash-completion/completions/pkco
Am Sat, Mar 18, 2023 at 12:00:49AM +0100 schrieb Liliana Marie Prikler:
> This error is caused by trying to install
> '/gnu/store/mxp199mvjb6dhyyg0pi4hn6c7m0xibvp-bash-completion-
> 2.11/share/bash-completion/completions/pkcon'. Meson appears to have a
> feature where it tries to use pkexec to gai
Am Sat, Mar 18, 2023 at 11:07:08AM +0100 schrieb Andreas Enge:
> And a help-guix question: How do I retrace the part of the dependency
> graph that links ipxe-qemu to gnome?
I am still interested in the answer to this question, but here the line
is short:
ipxe-qemu -> qemu-minimal -> gnome-boxes -
Am Sat, Mar 18, 2023 at 11:02:57AM +0100 schrieb Lars-Dominik Braun:
> I just saw it was fixed on the develop branch already, but there’s no
> new release:
> https://github.com/kurtmckee/feedparser/commit/c55bd8ad37db89bd219783bc514d600c9523ed38
This dates from 2021, but strangely is not part of a
Am Fri, Mar 17, 2023 at 08:40:00PM +0100 schrieb Andreas Enge:
> ipxe-qemu also fails its build phase:
> In file included from tests/bigint_test.c:38:
> tests/bigint_test.c: In function ‘bigint_test_exec’:
> tests/bigint_test.c:232:14: error: ‘result_raw’ may be used uninitialized
> [-Werror=maybe
Hello Andreas,
> excellent! It contradicts the feedparser author's statement that everything
> works well, so if you have the courage, maybe you could report the issue
> upstream.
I just saw it was fixed on the develop branch already, but there’s no
new release:
https://github.com/kurtmckee/feedp
Am Fri, Mar 17, 2023 at 09:46:27PM +0100 schrieb Liliana Marie Prikler:
> On a rather unrelated note, the uri
> https://gitlab.freedesktop.org/spice/libcacard/uploads/13b249e695a0d9aa7cb501b1a85ebab1/libcacard-2.8.1.tar.xz
> looks rather sus. Should we perhaps replace that with a git-reference?
T
Hi again,
> > > Right now I am left with a number of test failures that look real and
> > > cannot
> > > easily be solved by an upgrade (either because we are already on the
> > > latest
> > > version or because the tests still fail): python-sgmllib3k,
> > > python-typeguard
> > > and python-co
Hello,
Am Wed, Mar 15, 2023 at 05:59:12PM + schrieb Kaelyn:
> 2) libaio 0.3.113 does not build on core-updates, though the previous version
> 0.3.112 does. I'm not sure how to handle this one, as the failure is a
> compile error from one of the test cases:
it compiles for me on x86_64, but
Hello Lars,
Am Sat, Mar 18, 2023 at 09:59:37AM +0100 schrieb Lars-Dominik Braun:
> I fixed both python-sgmllib3k and python-feedparser. Disabling tests
> would not do much in this case, since the packages really *were* broken
> by a Python upstream change.
excellent! It contradicts the feedparser
Hello Andreas,
> This one is used for python-feedparser, used for calibre and quodlibet.
> The feedparser author is not enclined to work on it:
>https://github.com/kurtmckee/feedparser/issues/328
> I would suggest to try compiling python-sgmllib3k (and potentially
> python-feedparser) without
Hello,
Am Fri, Mar 17, 2023 at 08:43:13PM + schrieb Kaelyn:
> I'm at least a little in favor of that, as the commit message for
> cc56be2f3858487cf1d8acfb345942f0784221ee is mis-formatted (it doesn't have
> the first 'gnu: ' prefixed summary line, and so git log --oneline doesn't
> format i
26 matches
Mail list logo
