Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

Maxime Devos writes: > Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]: >> Which brings up another thing I've been considering working on thats >> been discussed in the Guix community: the need for click-to-edit >> wiki, written in Guile. [...] > > I don't think ‘written in Guile’ has been

Re: Dealing with upstream issues

Hi zimoun, et al, On +2022-06-28 18:25:05 +0200, zimoun wrote: > Hi, > > On Tue, 28 Jun 2022 at 14:31, Maxime Devos wrote: > > > You often close bugs with as rationale: ‘no response since X months, > > hence closing’, so it seems to me that you would simply close bug > > reports if the bug repo

Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

On +2022-06-28 22:13:58 +0200, Maxime Devos wrote: > Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]: > > Which brings up another thing I've been considering working on thats > > been discussed in the Guix community: the need for click-to-edit > > wiki, written in Guile. [...] > > I don't thi

Re: Non-free data in Poppler test suite

Marius Bakke schreef op di 28-06-2022 om 23:19 [+0200]: > I discovered a potential freedom issue with the Poppler test suite. > Specifically it includes a file with the CC BY-NC-ND (non-commercial) > license: Given that it what (some tests) are based on, this might count as functional data and hen

Non-free data in Poppler test suite

Hello Guix, I discovered a potential freedom issue with the Poppler test suite. Specifically it includes a file with the CC BY-NC-ND (non-commercial) license: https://gitlab.freedesktop.org/poppler/test/-/commit/920c89f8f43bdfe8966c8e397e7f67f5302e9435 It turns out the repository is filled wi

Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

Maxime Devos schreef op di 28-06-2022 om 22:13 [+0200]: > Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]: > > Which brings up another thing I've been considering working on > thats > > been discussed in the Guix community: the need for click-to-edit > > wiki, written in Guile. [...] > > I do

RE: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

> From: "Blake Shaw" > Subject: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile? > > Since getting feedback on my presentation for Guix Days, where I think a > lot of good criticism was raised, I've been thinking about ways to organize > contributions to the docs. An

Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]: > Which brings up another thing I've been considering working on thats > been discussed in the Guix community: the need for click-to-edit > wiki, written in Guile. [...] I don't think ‘written in Guile’ has been discussed? Also, I don't see th

Re: Dealing with upstream issues

zimoun schreef op di 28-06-2022 om 19:36 [+0200]: > Hi, > > On Tue, 28 Jun 2022 at 18:47, Maxime Devos wrote: > > > It is -- where's the bug report upstream or a fix? > > Upstream [1] does not have a bug tracker, or I am missing it.  See > bug#56285 for tracking the issue in Guix. > > O righ

Re: maradns reproducibility fixes and the merits of picking a random number

...I mean: as long as there's this second, run-time random term added to it as upstream says there is. I didn't audit the code to verify that. Kind regards, T G-R Sent on the go. Excuse or enjoy my brevity.

Re: maradns reproducibility fixes and the merits of picking a random number

>I am at a loss as to what to do then ... nothing and just have it be >unreproducible? embed a specific random number? come up with better >upstreamable patches? From upstream's response and my own biases and my reading of the room here, I'd say #2. Kind regards, T G-R Sent on the go. Excuse

Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?

Hi Luis, (copying in Guix as I digress into the subject of a Wiki for Guix & Guile communities) Thanks for this! It's cool and I would not have found it without your help. Which brings up another thing I've been considering working on thats been discussed in the Guix community: the need for clic

Re: First guix pull is too costly

zimoun writes: > Hi, > > On Tue, 28 Jun 2022 at 18:49, Akib Azmain Turja wrote: > >> Just out of curiosity, why the hash is >> pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq? Is this the hash >> of the channel declaration/definition/whatsoever? > > --8<---cut here-

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 18:47, Maxime Devos wrote: > It is -- where's the bug report upstream or a fix? Upstream [1] does not have a bug tracker, or I am missing it. See bug#56285 for tracking the issue in Guix. 1: 2:

Re: First guix pull is too costly

Hi, On Tue, 28 Jun 2022 at 18:49, Akib Azmain Turja wrote: > Just out of curiosity, why the hash is > pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq? Is this the hash > of the channel declaration/definition/whatsoever? --8<---cut here---start->8--- $ g

Re: First guix pull is too costly

Hi Efraim, On Tue, 28 Jun 2022 at 15:28, Efraim Flashner wrote: > There's already a copy of the guix source code at > /run/current-system/profile/share/guile/site/3.0/guix, what if we "just" > switched the new-user/new-cache experience to: This is only for Guix System and not on foreign distro,

Re: Dealing with upstream issues

zimoun schreef op di 28-06-2022 om 18:25 [+0200]: > My workflow dealing with old bugs is: pick one and read the report (and > the complete thread, if any), then, > >  1. the report provides enough information for reproducing; I try to >     reproduce myself and report more info, and then I try to

Re: Dealing with upstream issues

zimoun schreef op di 28-06-2022 om 18:21 [+0200]: > And… as I wrote [1]: > >     I agree; we cannot fix the world. ;-) In the case of patch#55541, the >     issues of cross-compilation can be reported directly to upstream and >     another Debbugs number could be open. > > 1:

Re: maradns reproducibility fixes and the merits of picking a random number

On 2022-06-28, Gábor Boskovits wrote: > Tobias Geerinckx-Rice ezt írta (időpont: 2022. jún. 28., K > 18:07): >> Vagrant said: >> > It is expensive to generate the random prime on some hardware, so doing >> > so at runtime might not be feasible in some cases... >> >> But in the same reply you're pa

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 14:31, Maxime Devos wrote: > You often close bugs with as rationale: ‘no response since X months, > hence closing’, so it seems to me that you would simply close bug > reports if the bug reporter is gone. [...] > That's the issue I wanted to highlight -- issues are c

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 14:21, Maxime Devos wrote: > zimoun schreef op di 28-06-2022 om 13:01 [+0200]: >> Well, from my understanding, the question is: should a perfectly working >> and fine submission be delayed because unrelated-to-Guix issues are in >> upstream code? > > This is not the que

Re: maradns reproducibility fixes and the merits of picking a random number

Hi, Tobias Geerinckx-Rice ezt írta (időpont: 2022. jún. 28., K 18:07): > Hi, > > Vagrant said: > > It is expensive to generate the random prime on some hardware, so doing > > so at runtime might not be feasible in some cases... > > But in the same reply you're paraphrasing, upstream also says: >

Re: maradns reproducibility fixes and the merits of picking a random number

Hi, Vagrant said: > It is expensive to generate the random prime on some hardware, so doing > so at runtime might not be feasible in some cases... But in the same reply you're paraphrasing, upstream also says: > In 2010, I updated that homegrown hash compression > algorithm to also add a random

Re: maradns reproducibility fixes and the merits of picking a random number

On Tue, 28 Jun 2022, Efraim Flashner wrote: On Mon, Jun 27, 2022 at 06:31:41PM -0700, Vagrant Cascadian wrote: https://github.com/samboy/MaraDNS/discussions/101#discussioncomment-3006487 Upstream appears to think it is mostly ok to actually embed a specific random prime... and not have it b

Re: First guix pull is too costly

zimoun writes: > Hi, > > On Tue, 28 Jun 2022 at 14:04, Akib Azmain Turja wrote: > >> Is possible to reuse the guix channel from any other user to do the >> first guix pull? Or maybe a shallow clone? > > Assuming alice is user already existing on the machine and bob is the > new user. Something

Re: Dealing with upstream issues

zimount: > Last, I miss these comments about old bugs and what you are implicitly > suggesting with them. Are you suggesting that old unsolved bugs are > closed without valid motivation? You often close bugs with as rationale: ‘no response since X months, hence closing’, so it seems to me that yo

Re: First guix pull is too costly

On Tue, Jun 28, 2022 at 01:23:00PM +0200, zimoun wrote: > Hi, > > On Tue, 28 Jun 2022 at 14:04, Akib Azmain Turja wrote: > > > Is possible to reuse the guix channel from any other user to do the > > first guix pull? Or maybe a shallow clone? > > Assuming alice is user already existing on the m

Re: Dealing with upstream issues

zimoun schreef op di 28-06-2022 om 13:01 [+0200]: >  Do you think that patch#55541 should be > delayed while submitter has not open an upstream issue? Yes, as mentioned in . Greetings, Maxime. signature.asc Description: This is a digitally signed message par

Re: Dealing with upstream issues

zimoun schreef op di 28-06-2022 om 13:01 [+0200]: > Well, from my understanding, the question is: should a perfectly working > and fine submission be delayed because unrelated-to-Guix issues are in > upstream code? This is not the question. The dispute is about: Maxime Devos: https://issues.guix

Re: First guix pull is too costly

Hi, On Tue, 28 Jun 2022 at 14:04, Akib Azmain Turja wrote: > Is possible to reuse the guix channel from any other user to do the > first guix pull? Or maybe a shallow clone? Assuming alice is user already existing on the machine and bob is the new user. Something like should do the job, --8<

Re: Dealing with upstream issues

Hi Maxime, I am confused by your replies in the thread. Maybe, I miss the topic of the comment by Ludo. Well, from my understanding, the question is: should a perfectly working and fine submission be delayed because unrelated-to-Guix issues are in upstream code? Ludo said these unrelated-to-Gui

Re: guix refresh to a specific version?

Hartmut Goebel schreef op wo 15-06-2022 om 13:34 [+0200]: > Hi, > > I wonder whether this is a way to refresh to a specific version, like > one can import a specific version: > > works: > > guix import pypi trytond@6.2.0 FWIW, this works for the 'crate' importer. Greetings, Maxime. sig

Re: First guix pull is too costly

On +2022-06-28 14:04:52 +0600, Akib Azmain Turja wrote: > > Hello, > > Yesterday, I created a new user in my system. Then I tried to install a > package, but found that it's not the latest, although I did sudo guix > pull before sudo guix system reconfigure. So I tried to do guix pull, > but it

Re: maradns reproducibility fixes and the merits of picking a random number

On Mon, Jun 27, 2022 at 06:31:41PM -0700, Vagrant Cascadian wrote: > On 2022-06-22, Vagrant Cascadian wrote: > > On 2022-06-08, Vagrant Cascadian wrote: > >> On 2022-06-08, Efraim Flashner wrote: > >>> On Tue, Jun 07, 2022 at 07:20:25AM +0200, Julien Lepiller wrote: > On June 7, 2022 5:24:22 A

First guix pull is too costly

Hello, Yesterday, I created a new user in my system. Then I tried to install a package, but found that it's not the latest, although I did sudo guix pull before sudo guix system reconfigure. So I tried to do guix pull, but it seems to clone the whole repository from scratch. But, unfortunately

Re: Release v1.4?

On Wed, Jun 22, 2022 at 03:31:34PM +0200, Ludovic Courtès wrote: > Hi, > > Brian Cully skribis: > > > Ludovic Courtès writes: > > > >> So plain ‘emacs’ package doesn’t work on Wayland? That sounds like > >> a > >> recipe for a poor user experience, no? > > > > The mainline Emacs is not Wayland

Re: RISCV porting effort

On Wed, Jun 22, 2022 at 03:19:43PM +, Ekaitz Zarraga wrote: > Also, hi! > > We kinda have a working bootstrappable GCC. > > If you want to know more you can read here: > > https://ekaitz.elenq.tech/bootstrapGcc4.html > > :) > I haven't been keeping much of a log of where I'm at, but here'

Re: guix refresh to a specific version?

FYI: I'm working on this. Given the number of importers and updaters is just takes some time. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |