Re: bug#68453: closed (Re: bug#68453: [PATCH] doc: Improve VNC Services section.)

Hello Maxim, Thank you for reopening the issue. > > I meant that at one place we have (display-number 10), and then about > > 15 lines below, we have (display-number 5). That’s inconsistent! > > The same applies to the port numbers: 5910 vs. 5905. > > Is it a problem to show the use of different

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Ludo’, I support this overall direction. Implementation details may require additional concensus, though I’m not sure if they’ll rise to the level of a GCD, but would like to see some discussion of problems as they crop up. Forgejo is purpose-built for developing software; email is not.

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi, Suhail Singh skribis: > Ludovic Courtès writes: > >> even though I’m currently mixing ‘fj.el’ and the dreaded web >> interface. > > Out of curiosity, could you please briefly mention what you're using > each for as of now? With the understanding that it's not meant as a > recommendation, b

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi, Simon Tournier skribis: > Sorry if my understanding is incorrect, but if we do not increase the > number of people with specific/dedicated/controlled write access, the > move to Codeberg is useless. Provocative on purpose. ;-) As I mentioned in the GCD under “Workflow”, at the Guix Days, a

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hey Efraim, Efraim Flashner skribis: > I've never really had to use a webui (or Rich HTML Experience™) for > shared development previously, so the change is (don't say scary!) not > one that I'm looking forward to excitedly. That resonates with me: I’m excited about the prospects from a social

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Ekaitz Zarraga skribis: > On 2025-02-07 23:14, Hartmut Goebel wrote: [...] >> Codeberg.org is driven by Codeberg e.V. which is a registered >> non-profit association (German: Verein) according to German Law. You >> can become a member and get voting rights. Read more about it at >>

Re: Shoutout to the organizers!

Pjotr Prins skribis: > On Mon, Feb 03, 2025 at 11:26:01PM +0100, Ludovic Courtès wrote: >> Hello Guix, >> >> Huge thanks to the organizers of the Guix Days and the declarative & >> minimalistic computing track at FOSDEM, in particular Pjotr as the >> overseer máximo (I think I heard him say he’s

Re: renaming of fpga.scm module

Hi Cayetano, If you think renaming the module is justified, feel free to submit a patch addressing your concern, along with a rationale like the one in your email. Someone with commit access may or may not accept it eventually. (FYI I don't have a commit access.) Cheers, Bost Le sam. 8 févr. 202

Re: 01/02: gnu: Add dlib.

Hey Danny, dan...@friendly-machines.com skribis: > I've merged them now and checked the only 3 dependents, starting with > python-openturns and the rest being in guix-hpc: they still do the > same not-that-great stuff that they did before (since the python > bindings are not enabled in dlib and w

HTTP redirect for the Git repository

Hi, Tobias Geerinckx-Rice skribis: > but has the subject of a ‘git.guix.gnu.org’ delegation come up (which would > require some coöperation from the host for HTTPS)? I'm in favour of this Big > Migration but it would be nice to anticipate the next one. This (adding a DNS entry and HTTP redir

Shepherd and minimalism in pid 1

Hello, Ludo's FOSDEM talk inspired me to share some thoughts that I encountered during my time at my previous position where we designed an init system. This might be better targeted specifically for shepherd, in this case please redirect and let me know. The fist things are the specialities of

renaming of fpga.scm module

Hi Guix, I need to point out a (not that relevant after all) issue which bothers me a bit, regarding the gnu/package/fpga.scm module. Simply put, it doesn’t necessarily concern fpga related software, and so its name may be misleading. Electronics would be a much better choice: I ignore

Re: Shepherd and minimalism in pid 1

Likewise for me. My plans for the next weeks are to experiment with the Shepherd on Android, mixing in magiskinit as the first init program. I got guix running on Android, the next step will be also shepherd. I'll also watch the recording again, and some of the others from the same devroom, as I mi

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi all, Vagrant Cascadian writes: When working with salsa.debian.org (a gitlab instance) there is a way to fetch all the merge requests for a given git repository, so it just becomes part of my normal workflow and to some extent works offline. If codeberg had a similar feature, that would b

Re: renaming of fpga.scm module

Hi, I *think* a renaming patch would just show up as a massive diff that will conflict with other minor changes. In that case it's better to keep the discussion ‘conceptual’ until the very end. However, confused: we already have (gnu packages electronics). Why not simply move any misclassifi

Re: Contributing to translation

Hi Alexis, Taking the second link, I could find a sentence that is not translated: "there may be inconsistencies in the work tree from previous builds". Going to weblate, I select the guix project, documentation-manual, French, then I can search (it's a link near the top of the screen, in green

Re: 01/02: gnu: Add dlib.

Hi Ludo, Could you please either revert this commit or merge the two 'dlib' definitions, assuming the upgrade does not break any dependent? (You can use 'guix build -P1 dlib' for example to check that.) I've merged them now and checked the only 3 dependents, starting with python-openturns and

Contributing to translation

Hi, Looking at the French version of the manual for packaging, I was quite surprised to see several paragraphs still in English [1]. As I wanted to fix some of them, I found the guide for translation redirecting to Weblate. After creating an account, I could not find easily the corresponding

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

On 2025-02-08 11:44, Cayetano Santos wrote: ven. 07 févr. 2025 at 23:55, Ekaitz Zarraga wrote: I do not have that option on GitHub, Hetzner, or, for that matter, Codeberg. Codeberg.org is driven by Codeberg e.V. which is a registered non-profit association (German: Verein) according to Ge

Re: (i18n) msgid feedback for shepherd-1.0.1rc1

Hi Andrej, > Hi, I am working on a translation for shepherd-1.0.1rc1, and I thought I'd > give some msgid feedback on a few small issues that I noticed. Here goes: This is very valuable feedback. > There are several msgids with strings indented with two spaces at the > beginning. Could these t

Re: Contributing to translation

There's no review process really, but the files are updated manually. The translation can sometimes break guix, so we update it manually to ensure it builds, but there's no review of the content. Le 9 février 2025 01:01:31 GMT+01:00, ale...@praga.dev a écrit : >Hi Julien, > >Thanks for the point

Re: (i18n) msgid feedback for shepherd-1.0.1rc1

Hi. Andrej’s feedback is good; thank you both. However: Ludovic Courtès writes: >> There are several msgids which need to take advantage of the multiple plural >> support of gettext: >> - "service names: ~a; heap: ~,2f MiB; file descriptors: ~a" >> - "Monitoring logging period changed to ~

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Liliana, Liliana Marie Prikler writes: Hi Guix, That way, pushes to `master` will be limited to changes that have already been validated and built. Perhaps we should rename 'master' to something else too. Food for thought for a future GCD :) I support this, and think it’s worth incl

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Liliana, Liliana Marie Prikler writes: Hi Guix, That way, pushes to `master` will be limited to changes that have already been validated and built. Perhaps we should rename 'master' to something else too. Food for thought for a future GCD :) I support this, and think it’s worth incl

Re: Discussion with Codeberg volunteers

Hi Felix! Felix Lechner writes: >> similar in scope or design to my current implementation? > > Dunno. I didn't understand the discussion. > > I plan to merge the keyrings of all channels before checking new > commits. My own channel will provide the key I need. Um, OK. I think there may be s

Re: Discussion with Codeberg volunteers

Hi 45mg, On Sun, Feb 09 2025, 45mg wrote: > to authenticate a commit, a key needs to be in the > .guix_authorizations file of all of its parent commits. Okay, thanks! In that case, I will get my fingerprint, upon failure, from the .guix_authorizations files in all other channels---specifically

Re: bug#68453: closed (Re: bug#68453: [PATCH] doc: Improve VNC Services section.)

reopen 68453 quit +CC guix-devel to sollicit more input Hi, Rostislav Svoboda writes: > Hello Maxim, > >> > * doc/guix.texi (VNC Services): Don't change the value of >> > `display-number`. >> >> Do you mean 5905 is supposed to be the default value? It's not (the >> default display number is 0

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

>ven. 07 févr. 2025 at 23:55, Ekaitz Zarraga wrote: >>> I do not have that option on GitHub, Hetzner, or, for that matter, >>> Codeberg. >> Codeberg.org is driven by Codeberg e.V. which is a registered non-profit >> association >> (German: Verein) according to German Law. You can become a membe

Re: Discussion with Codeberg volunteers

Hi Ludo’, Ludovic Courtès writes: Hello Guix, • Availability: From what they told us, they didn’t experience any serious downtime over the last year or so. (I did see someone online suggest otherwise so if you have experience, please share. FWIW, over 3+ months o

Re: Discussion with Codeberg volunteers

Hi 45mg, On Sat, Feb 08 2025, 45mg wrote: > similar in scope or design to my current implementation? Dunno. I didn't understand the discussion. I plan to merge the keyrings of all channels before checking new commits. My own channel will provide the key I need. Kind regards Felix P.S. Sorry

Re: Contributing to translation

Hi Julien, Thanks for the pointer, I did not think the search bar allowed for content search... One last question : when will the changes be available on the website ? I'm not sure if there is a review there or if it's just udpated every few hours. Best, Alexis On 2025-02-08T22:17:59.000+01:00,

Re: Questions on updating `aerc` and its Go dependency

On Thu, Feb 06, 2025 at 09:35:49AM +0100, tan...@bioneland.org wrote: > > Yes it has V2 in import path > > https://git.sr.ht/~rjarry/go-opt/tree/main/item/go.mod#L1 > > > > So the common logic is to inherit and create new package variant. > > gnu packages golang-* contains a lot of examples of that

Re: Understanding #:substitutable? and #55231

Hi Morgan, Morgan Arnold via "Development of GNU Guix and the GNU System distribution." writes: Hello, If the issue is simply that the patch has not been rebased against a new enough version of Guix to be merged, I am happy to do that rebasing. Additionally, please correct me if I have ma

Re: [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Ludo', On Sat, Feb 08 2025, Ludovic Courtès wrote: > Doing line-by-line code review, where you add a comment about specific > lines of a patch (like we do by mail) is not possible with ‘fj.el’. So > for non-trivial patches, I would go the web interface to do that. That feature is the forge's