Hi Andreas,
On mar., 14 mars 2023 at 21:43, Andreas Enge wrote:
>> 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™...
The set of Someone is restricted since it requir
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: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,
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
Hi Felix and Andreas,
--- Original Message ---
On Friday, March 17th, 2023 at 8:27 PM, Felix Lechner
wrote:
>
>
> Hi Andreas and Kaelyn,
>
> On Fri, Mar 17, 2023 at 1:18 PM Kaelyn kaelyn.al...@protonmail.com wrote:
>
> > sorry about "git am" not working
>
>
> I hesitate to get in
Hi Andreas and Kaelyn,
On Fri, Mar 17, 2023 at 1:18 PM Kaelyn wrote:
>
> sorry about "git am" not working
I hesitate to get in the middle, but it may be appropriate for
attribution reasons to revert commit cc56be2f and then re-commit with
the '--author' option, unless rebasing and breaking histo
--- Original Message ---
On Friday, March 17th, 2023 at 8:01 PM, Andreas Enge wrote:
>
> 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 new
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
> pack
Hi Felix,
Felix Lechner writes:
> Hi Andreas,
>
> On Wed, Mar 15, 2023 at 7:57 AM Andreas Enge wrote:
>>
>> Somehow the sending of store items when offloading poses problems
>
> Somehow I think I see a similar problem with 'guix deploy,' which I
> have to restart manually several times in order
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.
Thanks! Actually the
On Wed, 15 Mar 2023 14:33:36 +0100
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.
Björn
pgpqnmLKJ8OMX.pgp
Description: OpenPGP digita
Hi Andreas,
On Wed, Mar 15, 2023 at 7:57 AM Andreas Enge wrote:
>
> Somehow the sending of store items when offloading poses problems
Somehow I think I see a similar problem with 'guix deploy,' which I
have to restart manually several times in order to complete the store
transfer. In my case, th
Hi,
On the topic of the state of core-updates, I wanted to mention two things
affecting i686-linux builds (and by extension some x86_64 packages like wine64):
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
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
> silence. All of
Hi Efraim,
Efraim Flashner writes:
> On Wed, Mar 15, 2023 at 08:54:55AM +0100, Andreas Enge wrote:
>> 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 trie
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
rus
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 complaini
Hi Andreas,
Andreas Enge writes:
> 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 stagi
On Wed, Mar 15, 2023 at 08:54:55AM +0100, Andreas Enge wrote:
> 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
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 with
Hi Andreas,
Andreas Enge writes:
> 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 branche
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
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
Hi Andreas,
Andreas Enge writes:
> 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 fo
Ok, cool. Looking forward to it.
Josselin Poiret writes:
> [[PGP Signed Part:Undecided]]
> Hi Andreas,
>
> Roman Scherer writes:
>
>> Hi Andreas,
>>
>> could we please add the jemalloc package that supports transparent huge
>> page sizes on aarch64 (which is currently waiting in core-updates)
Hi Andreas,
Roman Scherer writes:
> Hi Andreas,
>
> could we please add the jemalloc package that supports transparent huge
> page sizes on aarch64 (which is currently waiting in core-updates) to
> this list? At the moment any substitute which involves jemalloc isn't
> useable on Linux kernels w
Hi Andreas,
could we please add the jemalloc package that supports transparent huge
page sizes on aarch64 (which is currently waiting in core-updates) to
this list? At the moment any substitute which involves jemalloc isn't
useable on Linux kernels with a page size > 4K and requires building the
Hi,
On ven., 10 mars 2023 at 15:58, Andreas Enge wrote:
> 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
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:
> https://git.cbaines.net/guix/qa-frontpage/commit/?id=39e9ec627faca95a7b43ff91e195ca9ab9846bf
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
Andreas Enge writes:
> So it would be nice if someone could set up a more complete job for
> core-updates on cuirass or QA, and maybe write up a how-to to see which
> packages work and which ones need more love, preferably by architecture.
> (Without offense, I honestly do not see what
>http
Hi Andreas,
Andreas Enge writes:
> 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 fo
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, wit
34 matches
Mail list logo