Re: Building more of ‘core-updates’ on ci.guix

Am Wed, Mar 22, 2023 at 03:32:07PM +0100 schrieb Ludovic Courtès: > Yes, it looks like we can safely uncomment icecat in ‘%system-packages’. Done! > Now, maybe we’ve reached the point where we can get ci.guix to build all > of ‘core-updates’? With staging built and the build farm being quite

Re: Gnome dans core-updates

Hello Josselin, Am Mon, Mar 20, 2023 at 08:18:41PM +0100 schrieb Josselin Poiret: > I ended up > fixing a couple of things locally for qemu-minimal to build (since I was > working on the Hurd and disk images). I also fixed u-boot-tools not > building on Python 3.10 (even though it's a swig bug

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

472b61f4 Mon Sep 17 00:00:00 2001 Message-Id: From: Andreas Enge Date: Wed, 29 Mar 2023 14:50:49 +0200 Subject: [PATCH] gnu: kcodecs: Disable obsolete test. * gnu/packages/patches/kcodecs-5.98-drop-test.patch: New file. * gnu/packages/kde-frameworks.scm (kcodecs): Add patch. * gnu/local.mk (dis

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

Am Wed, Mar 29, 2023 at 11:53:22AM +0200 schrieb Andreas Enge: > The file was removed in commit > commit 2e7dc813c2b4672f34d135755e928c52c15a1c3a > Author: Volker Krause > Date: Sun Feb 19 20:15:29 2023 +0100 > Remove QTextCodec leftovers > This is all unuse

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

Am Wed, Mar 29, 2023 at 11:35:24AM +0200 schrieb Andreas Enge: > FAIL! : KUsAsciiTextCodecTest::testBrokenBuiltinEncoding() Compared values > are not the same >Actual (failConverterState.invalidChars): 1 >Expected (0) : 0 >Loc: >

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

Am Wed, Mar 29, 2023 at 11:35:24AM +0200 schrieb Andreas Enge: > FAIL! : KUsAsciiTextCodecTest::testBrokenBuiltinEncoding() Compared values > are not the same We are not the only ones: https://bugs.gentoo.org/885615 for version 5.99, but there is no patch. Andreas

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

Am Tue, Mar 28, 2023 at 11:10:01PM -0400 schrieb Maxim Cournoyer: > It'd be useful if people tested it by reconfiguring their systems with > it or updating their profiles, and report any issues Supposedly the Qt update breaks kcodecs, which in turn breaks most of KDE. This issue is also present

Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging

Hello, Am Tue, Mar 28, 2023 at 11:10:01PM -0400 schrieb Maxim Cournoyer: > I've updated the following dependencies in a group (to try to make > things a bit more efficient) on the staging branch; the motivation > originally stemmed from the latest Jami now requiring FFmpeg 6. that sounds good if

Re: [GSoC 23] distributed substitutes, cost of storage

Hello, Am Wed, Mar 29, 2023 at 01:49:23AM +0530 schrieb Vijaya Anand: > In the case of accessing Guix substitutes from p2p > network, we ensure authorization by Guix team by making sure the urn of the > substitute is the urn mentioned in the narinfo no, currently substitutes are authenticated by

Re: Procps in core-updates

Am Mon, Mar 20, 2023 at 09:02:01PM +0100 schrieb Michael Schierl: > Seems that you accidentally attached the object file (binary) instead of > the assembly output. :-) Hm, I had accidentally written the assembly output to a .o file, and then apparently accidentally overwritten the file before

Re: Gnome dans core-updates

Am Mon, Mar 20, 2023 at 07:17:41PM +0200 schrieb Efraim Flashner: > > Time to merge master into core-updates, I would say. > Often a good idea :) Ah, it makes me super nervous. I now did for the first time ever... There were a few problems with openjdk, where the automatic merge took the wrong

Re: Gnome dans core-updates

Am Mon, Mar 20, 2023 at 06:00:37PM +0100 schrieb Andreas Enge: > If it is indeed a solution... Here is how far I got, patch attached. Actually it was updated by Efraim in master on March 9. Time to merge master into core-updates, I would say. Andreas

Re: Gnome dans core-updates

See also here: https://github.com/ipxe/ipxe/issues/775 isolinux.bin is supposed to be installed by syslinux, but it is not. If you could have a more informed look, that would be great. Andreas >From 6b4ed4a924994ee5ea12a38d91288238e34e33a2 Mon Sep 17 00:00:00 2001 From: Andreas Enge Date:

Re: Gnome dans core-updates

Am Sun, Mar 19, 2023 at 10:20:27AM +0100 schrieb Josselin Poiret: > The project does seem functional, they just seem to not care about > making new releases, since they direct users to official builds of HEAD > [1]. Maybe we could just point there as well? > [1]

Re: Python

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

Re: Gnome dans core-updates

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

Re: Procps in core-updates

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

Re: State of core-updates

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.

Re: Building more of ‘core-updates’ on ci.guix

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.

PyQt in core-updates

of knowledge about sip. Andreas >From 82cb67b324e9ef63bb105caae5b778467aedf894 Mon Sep 17 00:00:00 2001 From: Andreas Enge Date: Sat, 18 Mar 2023 15:48:48 +0100 Subject: [PATCH] gnu: python-pyqt: Set variable in configure script. * gnu/packages/patches/pyqt-minimum-sip-version.patch: New file. * gnu/packages/qt.s

Procps in core-updates

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"

Re: Gnome dans core-updates

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

Re: Gnome dans core-updates

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 ->

Re: Python

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

Re: Gnome dans core-updates

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

Re: Gnome dans core-updates

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?

Re: State of core-updates

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

Re: Python

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

Re: State of core-updates

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

Re: State of core-updates

Am Wed, Mar 15, 2023 at 05:59:12PM + schrieb Kaelyn: > 1) glib-networking has a 32-bit-only patch left over from the upgrade from > 2.70.0 to 2.72.2, which does not apply against the newer version, and which > seems unneeded. I just sent in https://issues.guix.gnu.org/62209 to fix the >

Re: Gnome dans core-updates

Am Fri, Mar 17, 2023 at 08:40:00PM +0100 schrieb Andreas Enge: > libcacard fails validate-runpath: > It looks like we need some of nss (the "normal" output, not "bin") as a This did not help, nss appears in no runpath; this is what is printed: starting phase `

Gnome dans core-updates

Hello, today I have compiled a maximum of inputs for gnome on berlin. Here is what is missing: The following derivations would be built: /gnu/store/1f71al4jx8pn7qnpp94642pvf6m4la5m-gnome-42.4.drv /gnu/store/4yvabkw23pwmxcanvl1qn8ch9jak7py4-packagekit-1.2.5.drv

Re: Offloading problems on berlin

Hello Kaelyn, Am Thu, Mar 16, 2023 at 09:25:27PM + schrieb Kaelyn: > You may be able to use jnettop to see the network streams (it does need > superuser privileges to run). Not sure how readable/useful it might be if > berlin has a lot of active connections, though. This is a huge help,

Re: Offloading problems on berlin

Am Thu, Mar 16, 2023 at 09:40:37PM +0100 schrieb Andreas Enge: > Thanks for pointing out that it is a known issue! And it happens quite systematically with large packages sent as inputs. When trying to build openjdk, I get without pause output like this: building /gnu/st

Re: Offloading problems on berlin

Am Thu, Mar 16, 2023 at 02:50:53PM +0100 schrieb Ludovic Courtès: > There’s a problem with offloading on berlin: > https://issues.guix.gnu.org/61839 > I occasionally offload from my laptop to machines at work but didn’t hit > this bug, so we’ll have to see if it’s specific to berlin or not.

Re: State of core-updates

Am Thu, Mar 16, 2023 at 10:33:08AM +0100 schrieb Björn Höfling: > Andreas Enge wrote: > > I more or less tried this by building things on berlin; however, big > > packages (?, precisely: openjdk checkout (not even building!) > OpenJDK@9 and @10 builds are fixed now on master.

Re: State of core-updates

Am Wed, Mar 15, 2023 at 02:33:36PM +0100 schrieb Andreas Enge: > I more or less tried this by building things on berlin; however, big > packages (?, precisely: openjdk checkout (not even building!), ghc@9.2.5 > and llvm-for-mesa) failed complaining about a 3600s timeout because of >

Re: KDE in core-updates

A quick update on KDE in core-updates: kcodecs also fails I tried to update extra-cmake-files and kwayland to the next version 5.99, which also forced me to update plasma-wayland-protocols to 1.9.0. But then kwayland shows three test failures instead of one... The latest KDE version is 5.104,

Re: Python

Hello, Am Sat, Feb 25, 2023 at 05:56:59PM +0100 schrieb Lars-Dominik Braun: > > 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):

Zig on core-updates

Just a one-package-failure-report: zig fails on core-updates, and I do not see why from the error message. If someone who knows the package could have a look, that would be great. Andreas

Re: Branch and release process

Am Wed, Mar 15, 2023 at 09:32:44AM -0400 schrieb Maxim Cournoyer: > I see; so it'd be useful for the integration of package changes > impacting multiple others; some kind of staging or core-updates > topic-focused branches. Simple leaf package updates could still be > merged directly to master

Re: State of core-updates

Am Wed, Mar 15, 2023 at 01:33:52PM +0200 schrieb Efraim Flashner: > This and other bugs are fixed on the rust-team branch. Once I figure out > how to compare it against master and force rust to build for aarch64 > we'll be nearly there. That sounds great! Then the order of merging might end up

Re: State of core-updates

Am Tue, Mar 14, 2023 at 11:50:12AM -0400 schrieb Maxim Cournoyer: > Some things that may help that I use: > - Offloading I more or less tried this by building things on berlin; however, big packages (?, precisely: openjdk checkout (not even building!), ghc@9.2.5 and llvm-for-mesa) failed

Re: State of core-updates

Am Tue, Mar 14, 2023 at 08:56:38PM -0400 schrieb Maxim Cournoyer: > OK! We could probably merge staging into master and be done already. We should build it first. The last time I tried, there was a showstopper bug. Here it is: I tried to build staging for my profile on x86_64, but it failed

Re: gnu: inetutils: Update to 2.4.

Am Tue, Mar 14, 2023 at 09:10:33PM -0400 schrieb Maxim Cournoyer: > Could you share the reference of that? I'm not against it, but our > currently documented process still mention the good old staging and > core-updates branches. It has not been documented yet, we should do it. Here is the

Re: State of core-updates

Am Mon, Mar 13, 2023 at 03:14:09PM +0100 schrieb Simon Tournier: > Well, maybe it could be helpful if now Berlin or Bordeaux starts to > build etc/release-manifest.scm. WDYT? That sounds like a great next step. Someone just has to do it™... Andreas

Re: Core-updates and cross-compilation

Hello Josselin, Am Tue, Mar 14, 2023 at 06:48:16PM +0100 schrieb Josselin Poiret: > I'm working on building Hurd atm, and it's been taking longer than I > would've liked. We needed an update to mig, which cascaded into updates > to gnumach and hurd, but they also shouldn't be too recent as we'd

Re: gnu: inetutils: Update to 2.4.

Hello Felix, Am Tue, Mar 14, 2023 at 09:37:23AM -0700 schrieb Felix Lechner via Development of GNU Guix and the GNU System distribution.: > With the core-updates process now abandoned, I retitled the issue to > "[PATCH wip-inetutils 0/4] gnu: inetutils: Update to 2.4". apologies for not

Re: State of core-updates

Hello Maxim, Am Tue, Mar 14, 2023 at 11:50:12AM -0400 schrieb Maxim Cournoyer: > That looks promising. Should we spun a differently named branch to > avoid people sending core-updates change? This was discussed in the > past and agreed to (main branches do not *freeze* themselves), instead > we

Re: GHC in core-updates

Am Sun, Mar 12, 2023 at 05:26:51PM +0100 schrieb Lars-Dominik Braun: > > But I confirm that ghc@9.2.5 now fails its tests > fixed by commit ec79901a33b6463ad77dcaf4c37e538645b4d7b5 on > core-updates. I also verified pandoc builds. Wow, fantastic, thanks a lot! Andreas

Re: bug#61894: [PATCH RFC] Team approval for patches

Hello, Am Sat, Mar 11, 2023 at 10:26:18PM -0500 schrieb Maxim Cournoyer: > Ludovic Courtès writes: > > I hope the maintainer team can help make teams “more functional”, > > whatever that teams. It’s really what maintainership is about in Guix; > > it’s not about writing code. > I'm happy to

Re: Core-updates and cross-compilation

Hello, Am Sat, Mar 11, 2023 at 01:56:27PM +0100 schrieb Josselin Poiret: > I've been looking at the state of most failures for the CI jobset for > core-updates, and we have a couple of problems: > - gcc < 9 and gcc == 12 never cross-compile. > - we can't build the cross toolchain for the hurd,

Re: State of core-updates

Hello Chris, Am Fri, Mar 10, 2023 at 06:24:38PM + schrieb Christopher Baines: > I configured QA to submit builds for core-updates a little while back, > currently it requires a code change [1]. > 1: >

Re: State of core-updates

Am Fri, Mar 10, 2023 at 07:55:00PM +0100 schrieb Josselin Poiret: > I would add gdm, xfce, gnome as those are part of most people's default > configuration. sway is probably another good candidate. Good points! I just tried "sway", and it compiles! (It depends on relatively few packages compared

Re: Python

Am Sat, Mar 11, 2023 at 12:20:25PM +0100 schrieb Andreas Enge: > There is a bug report for feedparser: >https://github.com/kurtmckee/feedparser/issues/328 > Unfortunately it was immediately closed with a link to an alternative > project by the feedparser author, but which has see

Re: Python

Am Sat, Feb 25, 2023 at 07:00:30PM +0100 schrieb Andreas Enge: > > sgmllib3k looks pretty dead upstream. Perhaps it’s > > not even needed any more? Updates to Python packages (via `guix refresh`) > > do not update dependencies and thus the list of inputs/native-inputs > >

Re: bug#61894: [PATCH RFC] Team approval for patches

Am Fri, Mar 10, 2023 at 06:33:58PM +0100 schrieb Simon Tournier: > However, for some packages or changes, the impact is far from being > trivial. I have in mind many changes that happen aside gnu/packages and > also some core packages (Guile, etc.). > For these kind of changes, it does not appear

State of core-updates

Hello all, let me start with a call for help! I realise that it takes me about one week and something close to 100GB on my poor 2-core laptop to rebuild the bulk of core-updates up to the packages in my profile, and that is not sustainable. It also forces me to do a "guix gc" between two runs,

Re: bug#61894: [PATCH RFC] Team approval for patches

Hello Simon, Am Thu, Mar 09, 2023 at 10:46:08AM +0100 schrieb Simon Tournier: > Hierarchy already exists, as in any social group, as in any group of > people collaborating. The hierarchy is currently informal. while I am sensitive to your argument about privileges, I am afraid that the

Re: GHC in core-updates

But I confirm that ghc@9.2.5 now fails its tests, it has happened a second time for me. Nothing in the recent commits to core-updates since I tried the last time springs to mind as obviously having a connection to these failures. Andreas

Re: GHC in core-updates

Hello Lars, Am Thu, Mar 09, 2023 at 01:45:54PM +0100 schrieb Lars-Dominik Braun: > I tried to compile GHC on core-updates recently, but didn’t even get > to GHC 9.2.5, because python2 failed to build (test test_asyncore failed, > without any further information). Do you have any extra patches

GHC in core-updates

Hello, the latest trial to compile ghc@9.2.5 resulted in many test errors, see below. Andreas SUMMARY for test run started at Thu Mar 9 06:51:34 2023 2:19:05.987429 spent to go through 8323 total tests, which gave rise to 41557 test cases, of which 29559 were skipped 44 had

Re: Merging branch wip-haskell

Am Wed, Feb 22, 2023 at 12:54:03PM +0200 schrieb Efraim Flashner: > > By the way, when building pandoc for my core-updates profile, I noticed > > that ghc bootstrapping takes a terribly long time. Might there be a fleeting > > chance to jump over some older releases? > I believe in core-updates

Re: Ungoogled-chromium in core-updates

Am Sat, Feb 25, 2023 at 03:41:58PM +0100 schrieb Andreas Enge: > Ungoogled-chromium compiles on core-updates! I now even tried it out > and it shows a website :) Ah, this is a crazy program - C++! It just failed after 17h of compilation in the very last step: [52515/52515] LINK ./chrome

Re: bug#61894: [PATCH RFC] Team approval for patches

Hello, Am Tue, Mar 07, 2023 at 09:53:29AM +0800 schrieb 宋文武: > I usually push patches for others who don't have commit access, while > most packages don't have a team at all, and some with me as the only > team member. > Should I wait for another commiter's approvol under this new policy or > can

Re: bug#61894: [PATCH RFC] Team approval for patches

Hello, in the current situation I think the suggestion is putting the horse before the cart. In a first step before adding policy, we should make the teams functional. While working on core-updates, I have been realising we are already spread too thin: Some important languages have teams with one

Re: Qt in core-updates

Am Wed, Mar 01, 2023 at 12:54:04AM +0100 schrieb Andreas Enge: > Well, I gave it a try, and it seems to be okay. I spake too fast. Somehow I took samba/fixed from core-updates instead of samba/pinned from master, and since I do not quite follow which is what, I will give up and let someone e

Re: Qt in core-updates

Am Tue, Feb 28, 2023 at 09:55:28PM +0100 schrieb Andreas Enge: > Am Tue, Feb 28, 2023 at 09:51:49PM +0100 schrieb Andreas Enge: > > Maybe it is time to merge master back into core-updates? > Where the vague "it is time to" could be read as "could you please?". >

Re: Qt in core-updates

Am Tue, Feb 28, 2023 at 09:51:49PM +0100 schrieb Andreas Enge: > Maybe it is time to merge master back into core-updates? Where the vague "it is time to" could be read as "could you please?". It is something I have never done, so it makes me nervous. Well, I suppose I c

Re: Qt in core-updates

Am Tue, Feb 28, 2023 at 01:20:08PM -0500 schrieb Leo Famulari: > Qtwebkit has been removed from the master branch. Oh right, I even remember now that you sent messages about it. Maybe it is time to merge master back into core-updates? (Although the problem here seems to be unrelated to webkit,

Re: Qt in core-updates

Am Tue, Feb 28, 2023 at 04:13:52PM +0100 schrieb Andreas Enge: > Now I am trying to build all > the Qt packages before applying the patch to core-updates; it looks good > so far. It went well with all the qt* packages. Then python-pyqt-without-qtwebkit fails already in its config

Re: Qt in core-updates

In the context of security problems and package removal, I just noticed (by "./pre-inst-env guix package -A ^qt") that we still have a qtwebkit package. The latest release dates from 2020, and this also the last release, if I understand correctly that the project has been abandoned. However:

Re: Qt in core-updates (was: KDE in core-updates)

Hello Philip, Kiasoc5, Efraim, thanks a lot for your input! Indeed I got my information that Qt 5 was phased out from Wikipedia, which mentioned May 2021 as the end of support. I did not expect there to be more versions! But then discovered the 5.15.8 version, probably related to the commercial

Re: Python

Am Mon, Feb 27, 2023 at 08:14:54PM +0100 schrieb Lars-Dominik Braun: > I don’t think we should follow PyPi’s names strictly. python-cheetah3 > makes much more sense than python-ct3. That’s what upstream-name is for. Okay, I am fine with doing nothing :) Andreas

Re: Question on the process of packge withdrawal

Hello, Am Sun, Feb 26, 2023 at 08:11:52PM + schrieb Sharlatan Hellseher: > If we check > > > commit removing jrnl variable which has it's source pointing to >

Re: Qt in core-updates (was: KDE in core-updates)

Am Sat, Feb 25, 2023 at 07:19:15PM +0100 schrieb Ludovic Courtès: > Given the test name, one would hope that it’s the usual time bomb of an > expired X.509 certificate. Apparently not, just some strange handling of openssl@3; if I understand correctly, these tests are expected to fail and should

Re: Python

Am Sat, Feb 25, 2023 at 07:15:24PM +0100 schrieb Andreas Enge: > Actually, upstream has changed its pypi name! >https://pypi.org/project/CT3/ I updated it to its latest version under its current name python-cheetah, but would suggest to rename it to python-ct3. What do you think? Andreas

Re: Python

Am Sat, Feb 25, 2023 at 07:00:30PM +0100 schrieb Andreas Enge: > It is also a propagated input of python-feedparser And this fails its tests after disabling the tests of python-sgmllib3k, even after updating to its latest version 6.0.10, like below. Then why I was at it, I also disab

Re: Python

Am Sat, Feb 25, 2023 at 07:06:31PM +0100 schrieb Andreas Enge: > Python-cheetah is misnamed, it should be called python-cheetah3; the first > one is the python@2 version, both exist on pypi. Is it okay to rename it? > It looks like moderate work: > > $ guix refresh -l pytho

Re: Python

Python-cheetah is misnamed, it should be called python-cheetah3; the first one is the python@2 version, both exist on pypi. Is it okay to rename it? It looks like moderate work: $ guix refresh -l python-cheetah Die folgenden 6 Pakete zu erstellen, würde zur Folge haben, dass 9 abhängige Pakete

Re: Python

Am Sat, Feb 25, 2023 at 05:56:59PM +0100 schrieb Lars-Dominik Braun: > Well, there are reasons no-one is updating the Python ecosystem > regularly… ;-) > I don’t know for sure why any of these packages’ tests fail. typeguard > looks like it expects specific strings from Python or one of its

Re: Python

Am Sun, Feb 19, 2023 at 09:27:23PM +0100 schrieb Andreas Enge: > Am Sun, Feb 19, 2023 at 04:50:37PM +0100 schrieb Lars-Dominik Braun: > > eolie upstream looks dead, same with jrnl. Removed. > I found python-miio, which depends on python-android-backup, which depends > on

Re: Python

Am Sat, Feb 25, 2023 at 04:45:39PM +0100 schrieb Lars-Dominik Braun: > note that importlib-metadata is – again – part of the standard > library, as the table on [1] points out. So if we would ship Python 3.12, > we would not need it. Bumping it to version 5.2 seems like the correct > approach

Re: Python

Hello Lars, Am Fri, Feb 24, 2023 at 07:08:44PM +0100 schrieb Lars-Dominik Braun: > sorry, I can’t quite keep up with the Python issues on core-updates > right now :( thanks for your reply, this is very helpful, as I am more than insecure when it comes to python packaging! > > Yet another python

Re: Ungoogled-chromium in core-updates

Ungoogled-chromium compiles on core-updates! I now even tried it out and it shows a website :) One problem less. Andreas

Re: Python

Am Fri, Feb 24, 2023 at 05:47:33PM +0100 schrieb Andreas Enge: > Yet another python failure: python-pathlib Maybe this is our fault; Debian has a pathlib2 package. Us too. So we should try to see whether we can replace the dependency python-pathlib by python-pathlib2. Work for another

Re: Python

Yet another python failure: python-pathlib import pathlib File "/tmp/guix-build-python-pathlib-1.0.1.drv-0/pathlib-1.0.1/pathlib.py", line 10, in from collections import Sequence ImportError: cannot import name 'Sequence' from 'collections'

Re: KDE in core-updates

And another undebuggable (?) failure, this time for qtbase: Total Test time (real) = 544.95 sec The following tests FAILED: 354 - tst_qsslkey (Failed) Errors while running CTest error: in phase 'check': uncaught exception: %exception #< program: "xvfb-run" arguments: ("ctest"

Re: Python

Another very problematic python package: python-sgmllib3k It fails its tests in core-updates. Unmaintained since 2010, the author states that they do not wish to maintain it. Some dependencies: Building the following 6 packages would ensure 8 dependent packages are rebuilt:

Re: Python

In my goal of building calibre on core-updates, I encounter many build failures. The Python package graph seems to be extremely entangled, with dependencies on specific input package and even Python versions. The only approach I could imagine is updating to newer versions, and this solved some of

Re: Icecat (was: Python)

Am Tue, Feb 21, 2023 at 05:58:26PM +0100 schrieb Andreas Enge: > I opted for this fix and could compile python-graphviz; this enables me to > test the build of icecat now. Good news for once: I could build icecat from core-updates on x86_64! Andreas

Re: Merging branch wip-haskell

Hello Lars, Am Wed, Feb 15, 2023 at 11:38:23AM +0100 schrieb zimoun: > Feel free to merge. :-) +1, please go ahead! By the way, when building pandoc for my core-updates profile, I noticed that ghc bootstrapping takes a terribly long time. Might there be a fleeting chance to jump over some older

Re: Thoughts on committers pushing simple changes from other committers?

Am Tue, Feb 21, 2023 at 01:00:07PM -0500 schrieb Leo Famulari: > Commit access is controlled via membership of the Savannah project: > https://savannah.gnu.org/project/memberlist.php?group=guix > Thus, that is the list. Thanks, very helpful! Andreas

Re: Python (was: Merging core-updates?)

Hello, Am Sun, Feb 19, 2023 at 11:24:44PM +0100 schrieb Andreas Enge: > python-graphviz does not pass its tests any more in core-updates, and > I can trace it back to your commit 3d388fe3d0475f2e991ae061cc1364529a97af42. > Adding python-mock back to native-inputs fixes it. I opted for

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:30:42PM +0100 schrieb Andreas Enge: > And another one: python-ecdsa This just built. Strange, but I will not complain! Andreas

Re: Python

Am Sun, Feb 19, 2023 at 09:31:44PM +0100 schrieb Andreas Enge: > And yet another one: python-testtool > FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error > FAIL: > testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error This

Re: Python

Am Sun, Feb 19, 2023 at 03:10:03PM + schrieb Attila Lendvai: > weirdly enough, upstream uses one git repo for multiple projects, and uses > prefixed tag names for them. > FYI, there's this long-pending patchset to update the trezor-agent (something > i can test myself): >

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 10:59:35PM + schrieb Kaelyn: > It was mentioned recently that python-pycryptodome is / should be a drop-in > replacement for python-pycrypto (it is also says that in the package > description); Apparently it is not, as Lars wrote. And in any case, it does require

Re: Ungoogled-chromium in core-updates

Am Mon, Feb 20, 2023 at 09:41:23PM +0100 schrieb Andreas Enge: > It is also in the Debian patches as fixes/clang-and-gcc11.patch. It helps to go further, new patch attached. Now I get until the message below. [45812/52515] CXX obj/third_party/blink/renderer/core/core/attribution_src_loade

Re: Thoughts on committers pushing simple changes from other committers?

Am Tue, Feb 21, 2023 at 12:54:32PM + schrieb Christopher Baines: > Generally, I don't push changes for other committers, but I wonder if > that would be helpful now. Personally I prefer to push my own changes. And let other people push theirs if they can. Actually I think we are responsible

<    1   2   3   4   5   6   7   8   9   10   >