Re: mumi am --skip, --continue ?

Hi Danny, > mumi/client.scm:280:12: In procedure call-with-output-pipe*: > Command invocation failed ("git" "am") > $ mumi am --skip This needs to be `mumi am -- --skip'. All `git am' arguments come after the `--'. The segfault was from the argument parser. `mumi am' is a wrapper around `git a

Re: Preparing for Git repository migration

Hi Ludo, > I’m also happy to add your account to the “owners” team; let me know > when you have one. I already have an account. Here it is: https://codeberg.org/arunisaac Thanks, Arun

Re: Preparing for Git repository migration

Hi Ludo, > Looking at , there’s one > repository I forgot to mention (shame on me): mumi. > > Arun, should I let you migrate it? Let me know what you prefer. Since you're already familiar with the process, it might be easier for you to migrate the mumi

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

I accept.

Re: branch master updated: gnu: dico: Update to 2.12.

Hi Ludo, > (Arun: surprisingly, is 404. Any > idea what’s up?) Unfortunately, recently, mumi seems to be missing some issues when indexing. I believe this is related to the recent optimizations I put in to speed up indexing. I am hoping the upcoming change t

Re: Search alerts and Watch issue on mumi

Hi Gabriel, Thank you for your quick response! > mumi.css 1970:2 >> line-height: var(--line-height); > > Brought "Projects" to the same height as "Search Alert". I tried this, and it brings the "Projects" link higher up, but leaves the little dropdown arrow where it is. I'll probably go with L

Re: Search alerts and Watch issue on mumi

> Love it. Really. Thanks a lot for all those improvements to mumi, which > is getting more and more useful with time. Thank you very much for the encouragement. :-) I hope I can continue to hack on mumi for a while. >> Search alerts and issue watching are all powered by Atom feeds under the >>

Search alerts and Watch issue on mumi

full firehose. Maybe you want to only subscribe to the Emacs team—find the search alert feed for "tag:team-emacs". Or, subscribe to all issues in which you participated in—submitter:"Arun Isaac" (replace my name with yours, of course)—and never worry about people not Ccing you corr

Re: Search alerts and Watch issue on mumi

> Or, subscribe to all issues in which you participated > in—submitter:"Arun Isaac" (replace my name with yours, of course)—and > never worry about people not Ccing you correctly. Small correction. This query should be author:"Arun Isaac". submitter:"Arun Isaa

Re: Automatic tagging of unanswered issues in mumi

> one last question: AND operator is implicit (by default) ? Any other > accepted ? Boolean search prefixes (the tag:, severity:, is: prefixes, etc.) work with an implicit AND. Free text search terms work with an implicit OR. Also, when the same boolean prefix occurs twice (for example, tag: in

Re: Automatic tagging of unanswered issues in mumi

> I had in mind both, "tag:unanswered" and "tag:team-whatever", which > don’t appear in the help page. Thanks, I have added these as examples in https://issues.guix.gnu.org/help#search > (I understand here that not any tag is accepted by mumi). Tags, as understood by mumi, are arbitrary string

Re: mumi CLI now supports tagging

Hi Ricardo, > We can record the original numeric time stamp in a "data-" attribute > and use JavaScript to sort by that data attribute on the client. (In > the past I've used listjs[1] for this, which is likely overkill here.) > > [1]: https://github.com/javve/list.js Good find, and a good sugg

Re: Automatic tagging of unanswered issues in mumi

Hi Cayetano, > I’m just wondering if the help page up to date with most recent hints. > > https://issues.guix.gnu.org/help The help page is technically up-to-date since I haven't changed that interface. However, the help page could be improved significantly by adding examples of real-world

Automatic tagging of unanswered issues in mumi

Hi, mumi now automatically tags unanswered issues. Unanswered issues are those in which no one has responded to the original submitter. You can search for these using queries like "tag:unanswered", "tag:unanswered AND tag:team-python". https://issues.guix.gnu.org/search?query=tag%3Aunanswered h

Re: Automatic tagging by team on mumi

> (It is with a happy befuddlement that I observe apparently increased > interest in mumi since the GCD proposing abandoning it. A welcome side > effect.) Nothing like a good "now or never"! ;-)

Re: Bug triage

> So I cloned the mumi repo and ran it - and I found > https://issues.guix.gnu.org/76919. I have pushed that patch now. Thanks!

Automatic tagging by team on mumi

Hi all, mumi now automatically tags issues by team. You can try queries like "tag:team-games", "tag:team-python date:1m..", etc. And, you can freely combine these with any other keywords or queries---for example, "tag:team-games strategy". As usual, these queries work both in the web and CLI int

Re: mumi CLI now supports tagging

Hi Noé, The new open/closed indicator badges and separation of open/closed issues is now online. I'm happy to hear your feedback and tweak it a bit. >> Also, implementing sorting on the list is difficult to do, especially >> with the new relative dates that we have. And, I don't have much time

Re: Bug triage

Hi Nicolas and Bost, Sorry for the extremely late reply. >>> I've tried to do some bug/patch triage yesterday and marked a bunch of >>> patches as "easy" >> >> How well does mumi, the issue tracker, support predicates? >> >> This does not work: 'tag:easy AND (NOT (is:closed OR is:done))' >> htt

Re: Mumi list interface [Was: mumi CLI now supports tagging]

Hi Samuel, > One thing to add: before, it was intuitive to sort issues by date > and status (done/open). Is this still possible? I could not tell. Sorting is not possible at the moment. But, you can filter for open/closed issues by adding "is:open" or "is:closed" to your search query. See this

Re: mumi CLI now supports tagging

Hi Noé, > Seeing closed issues is very important depending on what I’m looking > for. How about having a colored « open » indicator next to the tags (or > as a tag)? Yes, we could have an "open/closed" indicator badge similar to the tag badges. I'll implement that. I also think we should make

Re: Mumi list interface [Was: mumi CLI now supports tagging]

Hi Felix, > I find that the list interface [1] made the website [2] less helpful, Could you please elaborate? Maybe we can work out the shortcomings of the new interface. Regards, Arun

Re: mumi CLI now supports tagging

Hi Cayetano, > Now, the "reviewed-looks-good" tag may be set (without sending any > email) using (right ?) > > mumi -t +reviewed-looks-good There are two orthogonal issues here: 1. `mumi command' merely composes the email for you and fires up your email client. You still need to "click Sen

Re: mumi CLI now supports tagging

Hi Cayetano, >> For example, to tag the current issue with the confirmed and easy tags: >> mumi command -t +confirmed -t +easy >> >> To remove the moreinfo tag and add the help tag: >> mumi command -t -moreinfo -t +help > > Those tags are equivalent to the ones we set by sending emails to > cont

Re: mumi CLI now supports tagging

Hi Noé, Thank you for your feedback! > It seems the new design has removed the ability to sort by date in > searches, which is a very important feature for me. We could bring back the sorting. But first, could you help me understand what you use the sorting for? Would maybe, narrowing down you

mumi CLI now supports tagging

Hi, With the latest mumi 0.5.0, the mumi CLI now supports tagging and easy composition[1] of command emails to the debbugs control server. For example, to tag the current issue with the confirmed and easy tags: mumi command -t +confirmed -t +easy To remove the moreinfo tag and add the help tag

Re: Libravatar avatars on mumi

> Sorry, we had some issues (probably kernel related) when reconfiguring > berlin and had to roll back. The latest version of mumi with Libravatar > avatars will be back after we have resolved these issues. The latest version of mumi is now on berlin. And, we now have Libravatar avatars!

Re: Libravatar avatars on mumi

Sorry, we had some issues (probably kernel related) when reconfiguring berlin and had to roll back. The latest version of mumi with Libravatar avatars will be back after we have resolved these issues.

Libravatar avatars on mumi

Hi, We now have Libravatar[1] avatars on mumi thanks to Felix Lechner and Noé Lopez! For those who don't have Libravatar avatars, we fall back to identicons[2]. Libravatar federation is not implemented yet in guile-avatar and may be a good project for someone to hack on. See the NEWS file[3] in

Re: Guix Common Document process (v7) (was: Request-For-Comment, RFC)

>> On the matter of communication channels for the RFC process, can we have >> a separate mailing list for RFC announcements? > > An announce to info-g...@gnu.org, does it appear to you enough? > > Well, the RFC will be low traffic, I guess. And info-guix seems a good > start. I am ok with info

Re: Guix Common Document process (v7) (was: Request-For-Comment, RFC)

Hi Simon, Thanks for pushing the RFC process forward. > https://www.seedsforchange.org.uk/consensus I highly appreciate that you linked to this. It helps for us to be on the same page on this complex matter. Too often, democracy is misunderstood as being only about the majoritarian voting syst

Re: New mumi am subcommand

> I guess a next step, in case you (and others!) are looking for one, > would be to allow users to run through a review check list from the > command line, and to add a ‘reviewed-looks-good’ tag. Great idea! I have opened an issue https://issues.guix.gnu.org/71622 to brainstorm and to invite con

New mumi am subcommand

Hi, The latest mumi CLI (version 0.3.0) comes with a new `mumi am' subcommand. With this, you can automagically apply the latest patchset in an issue. First, set the current issue (say 61036). $ mumi current 61036 Then, apply the latest patchset using $ mumi am You may also apply a patchset

Re: New mumi www and mumi compose subcommands

Hi Ludo, >> The www and compose subcommands rely on xdg-open to open your browser >> and mail client correctly. > > Won’t work with Gnus, but nice still. ;-) If it's a matter of getting our .desktop files working correctly for different email clients, we should do so. It would be good to have

New mumi www and mumi compose subcommands

Hi all, The latest mumi CLI (version 0.1.0) comes with two new subcommands—www and compose. Now, when an issue is current, you can open that issue in your web browser using the www subcommand; and, you can compose a mail to that issue using the compose subcommand. For example, $ mumi current

Re: February hybrid Guix London meetup

ou familiarise with the document and that you > share its principles before attending our events. > > Should you at any time before, during, or after one of our events want > to raise an issue or discuss any CoC-related topic, please do not > hesitate to reach out to the organisers

February hybrid Guix London meetup

Should you at any time before, during, or after one of our events want to raise an issue or discuss any CoC-related topic, please do not hesitate to reach out to the organisers at the contacts below. - Arun Isaac, arunis...@systemreboot.net - Fabio Natali, m...@fabionatali.com # Get involved S

Re: January hybrid Guix London meetup

end, Guix London adheres to the Guix project's official Code of > Conduct, as published at this link. Please make sure you familiarise > with the document and that you share its principles, before attending > our events. > > Should you—at any time before, during, or after one of o

January hybrid Guix London meetup

ach out to the organisers at the contacts below. - Arun Isaac, arunis...@systemreboot.net - Fabio Natali, m...@fabionatali.com # Get involved Should you be interested in becoming a Guix London organiser, please let us know. It'd be great to have you onboard. No previous Guix knowledge is required.

Re: December London Guix meetup

make sure you familiarise > with the document and that you share its principles, before attending > our events. > > Should you—at any time before, during, or after one of our events—want > to raise an issue or discuss any CoC-related topic, please do not > hesitate to reach out to th

December London Guix meetup

attending our events. Should you—at any time before, during, or after one of our events—want to raise an issue or discuss any CoC-related topic, please do not hesitate to reach out to the organisers at the contacts below. - Arun Isaac, arunis...@systemreboot.net - Fabio Natali, m...@fabionatali.com

November online London Guix/Guile meetup

Hi All, The next London Guix meetup is scheduled for Monday 20th November, 6 pm London time (i.e. UTC) onward. 😃🤖🌈💻 This time the meetup will be fully online, at the link below. https://meet.jit.si/london-guix-meetup This is a great opportunity for people anywhere in the world to jump in! As

Re: October hybrid London Guix/Guile meetup

Hi all, Just a reminder for the London Guix/Guile meetup tomorrow! Don't forget that this is a hybrid meetup and you can join even if you are not in London. Online location: https://meet.jit.si/london-guix-meetup Face-to-face location: c/o HubHub 20 Farringdon Street, EC4A 4AB, London Date/T

October hybrid London Guix/Guile meetup

Hi all, The next London Guix meetup is scheduled for Monday 23rd October, 6 pm London time (i.e. UTC+0100) onward. 😃🤖🌈💻 Join us in person at 20 Farringdon Street, EC4A 4AB. BIG NEWS 😃: If you like, you can join us remotely from anywhere on the planet too, using the following link: https://meet

Re: [PATCH] web: Include merged_with in graphql .

> Sorry, I missed this patch. I will apply it tonight. Done! https://git.savannah.gnu.org/cgit/guix/mumi.git/commit/?id=a89c5109963de0b5fd1f500ed2e2ede47728fdb4 https://git.savannah.gnu.org/cgit/guix/mumi.git/commit/?id=025fc600f1cb4c73042bf920aee3e07d5fb9c53a I have also reconfigured berlin w

Re: [PATCH] web: Include merged_with in graphql .

Hi, Sorry, I missed this patch. I will apply it tonight. I am not usually subscribed to guix-devel. In the future, please Cc me on patches related to mumi. Thanks! Arun

Re: September London Guix/Guile meetup

Reminder for today's London Guix/Guile meetup! > Guixers of the world (or more simply, from the London area) unite! > 😃🤖🌈💻 > > Unbelievable, we've reached our fourth event already, which will be held > at the very heart of the City of London. Join us to talk about Guix, > Guile, Scheme & Lisp, a

September London Guix/Guile meetup

Hi all, Guixers of the world (or more simply, from the London area) unite! 😃🤖🌈💻 Unbelievable, we've reached our fourth event already, which will be held at the very heart of the City of London. Join us to talk about Guix, Guile, Scheme & Lisp, and all things Free Software. Bring your laptop for

Mumi CLI client (was: How can we decrease the cognitive overhead for contributors?)

Hi all, I'm glad we're having this difficult but necessary conversation. I have been following the conversation with much interest. There seems to be a developing consensus that we should switch to sourcehut. I am all in favour of any decision the community comes to on this. But, meanwhile, I

August Guix/Guile London meetup reminder

Hi all, A quick reminder for the August edition of the Guix London meetup. As usual, it'll be a chance to talk about Guix, our favourite package manager and the Guile programming language. Date/Time: Thursday 24th August, 6 pm onwards Location: Riverside Terrace Cafe at the Southbank Centre Mob

Re: July Guix London meetup

Hi all, > Join us on Mon 24th July, 6 pm – 8.30 pm, at the Lakeside Terrace of > the Barbican Centre, Silk Street, EC2Y 8DS, London. You'll find us at > a table near the water fountains. We'll have a couple of small Guix > posters to indicate it's us. Quick reminder for the Guix London meetup t

Re: Development repositories as Guix channels

> Another person reported that missing bit to me and I’ve now fixed the > blog post. Apologies for the waste of time! No worries! It's been a very enlightening blog post. Thanks for writing it!

Re: Development repositories as Guix channels

Hi Daniel, > You have to replace the relative path in the local-file form with > "../.." as that gives you the root of your source tree relative to the > new location of the Scheme file. Then everything works nicely. Thank you! That's all I was missing. Now everything works perfectly! > Bonus:

Development repositories as Guix channels

Hi, This is with reference to the "Level 2: The repository as a channel" section in the Guix blog post "From development environments to continuous integration—the ultimate guide to software development with Guix"[1]. This section describes how to convert a project repository into a Guix channel

Re: London Guix meetup

Hi Etienne, > Oops. I missed that! Is this a regular thing? > Is there a UK community of sort, e.g. online platform, mailing list and so > forth? Nope, this was just the first meetup. There may be another meetup in a month or so. We don't have any separate online presence yet. Regards, Arun

Re: London Guix meetup

Hi all, We had a good turnout with 8 attendees. Thank you all for coming! We may have another meetup in a month or so. Looking forward to seeing you all again and hope to see new faces too! Regards, Arun

Re: London Guix meetup

Hi all, Just a quick reminder for tomorrow's Guix meetup at the Barbican. Looking forward to seeing many of you! :-) Date: Tuesday, June 27 6–9 pm BST Location: Barbican Centre, Silk Street, EC2Y 8DS, London Mobilizon page: https://mobilizon.fr/events/f18da336-07f5-489f-ae7c-394458668cea How t

London Guix meetup

Hi all, We are organizing a casual Guix meetup in London. There is no specific agenda. The intention is for Guix users and would-be Guix users in London to get to know each other, and to put faces to names. No prior experience with Guix (or Guile) is necessary. Newcomers are very welcome! Date:

Re: [PATCH] web: Include blocked-by in graphql .

Hi Chris, Thanks for the patch! I have pushed it after renaming blocked-by to blocked_by. Underscores are a bit cringey, but unfortunately GraphQL doesn't like hyphens. To see the effects of this change, we need to reconfigure berlin to run the latest mumi. I will figure that out and do it soon

Re: `mumi send-email' means no more debbugs dance to send multiple patches

Hi Josselin, > Thanks for looking into it. I have tried twice now, with the same issue > both times, with [1] and [2]. > > [1] mid:cover.1682364024.git@jpoiret.xyz > https://yhetil.org/guix/cover.1682364024.git@jpoiret.xyz/ > > [2] mid:cover.1682452738.git@jpoiret.xyz > http

Re: `mumi send-email' means no more debbugs dance to send multiple patches

> All the above could be handled at the level of git directly with the > changes suggested in #58813, so I'd suggest we do this, which benefits > everyone/everything relying on it. Ah, I was not aware of #58813 and that this could be done at the level of git. Good point! And, thanks for your wor

Re: mumi web server bugs [was "`mumi send-email' means no more debbugs dance to send multiple patches"]

Hi Andreas, > When I start it, it runs on 0.0.0.0, port 1.2.3.4; should it not choose > a sensible default, such as localhost and 8080? I agree. A patch setting the defaults to localhost and 8080 is welcome. Would you like to give it a shot? If not, could you register these in our bug tracker s

Re: `mumi send-email' means no more debbugs dance to send multiple patches

Hi John, > I just tried it out and it worked smoothly for sending 2 patches to an > existing bug. However, it was sent only directly to the bug address, > not being aware I guess of anyone that had submitted or since been > CC'ed to the thread. > > Is there anything we can do here? I learned abo

Re: `mumi send-email' means no more debbugs dance to send multiple patches

Hi Josselin, > My mails usually take less that 30 seconds to get a reply from debbugs. > I don't remember how long it took yesterday for the issue to appear on > mumi though, but more than the 15 retries of mumi send-email (I manually > checked). Could you link to the specific email message tha

Re: `mumi send-email' means no more debbugs dance to send multiple patches

> This could be changed. We don’t need to wait for the email to arrive on > the mumi server; could we ask debbugs directly for the email? (If we > can’t ask for the mail we could ask for newest bugs and check if that > contains the email.) `mumi send-email' polls mumi's /msg-id endpoint to fin

Re: `mumi send-email' means no more debbugs dance to send multiple patches

Hi Josselin, > I've just tried it out, but unfortunately mumi didn't receive the mail > in time and it just timed out sending the replies :( is there anything > that could be done on that front? Does mumi use IMAP IDLE? Ouch! Unfortunately, timeouts can happen. I was just hoping it would be un

`mumi send-email' means no more debbugs dance to send multiple patches

Hi all, mumi, the software powering our debbugs frontend at https://issues.guix.gnu.org/, now also comes with a command-line interface. At the moment, the new command-line interface allows searching for issues, and sending patches. Most notably, it frees us from the debbugs dance required for se

Licence of the Guix blog posts

Yes, I agree for my contribution to the blog posts to be published under the licenses CC-BY-SA 4.0 and GFDL version 1.3 or later (with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts).

Re: Mumi Feature Request: Easier way to apply patches from web interface

> Maybe add a guix command for issues/patches? > > guix issues new > guix issues open nnn > guix issues reply nnn > guix issues apply nnn > guix issues close nnn Indeed, we should have something like this. But, probably better to put it in mumi so that other projects that use debbugs (I have sk

Re: issue tracking in git

Hi zimoun, >> We also have ci and cd based on our own system containers in Guix. >> >> => https://ci.genenetwork.org/ > > This is based on which CI code? Your own or do you use an existing CI > framework/tools? This CI is built using guix-forge documented at https://guix-forge.systemreboot.net

Re: issue tracking in git

Hi Giovanni, > Please Arun is there a devel mailing list dedicated to tissue so we can > discuss details of the project? There isn't one yet, but I will set up a public inbox soon. > I'm not a Guile developer but I would like to help with testing and (the > lack of) documentation, if I can. Y

Re: Get all closed tickets with kolam

title open date ;; Find the title and submitter of issue 34948. (define %graphql-document '(document (query (#(issue #:number 34948) title (submitter name address) ;; Find issues Arun Isaac participated in, the title

Re: “Building a Secure Software Supply Chain with GNU Guix”

> I don’t plan personally to make it a separately-maintained tool, but it > could be interesting. More generally, getting in touch with the Git > developers and also with other projects with similar concerns would be > great. That's good to know, thanks! Yup, git integration would be great. Mea

Re: “Building a Secure Software Supply Chain with GNU Guix”

Hi Ludo, > https://doi.org/10.22152/programming-journal.org/2023/7/1 This is an excellent read! Are there plans to release this git authentication system as a separate tool so that other non-Guix projects may use it easily? Thanks, Arun

Re: On commit access, patch review, and remaining healthy

>> Also, should we remove old/broken/unused/rarely-used packages from Guix? >> In the past, I have packaged and contributed very niche packages which >> probably no one else uses, and sometimes even I don't use anymore. But, >> these packages continue to stay in Guix and add to the maintenance >>

Re: On commit access, patch review, and remaining healthy

Hi, > That’s why, I think the project should: > > 1. change the default branch of “git push” vs the default branch of > “guix pull”. > > 2. add a bit more of checkers on patch submission easing patch > review. I like and support both these ideas. Maybe, they are even long overdue! ;-) I w

Re: On commit access, patch review, and remaining healthy

>>> Personally, I think nowadays this purpose is better fulfilled by >>> good commit messages and git blame. Especially with an editor that makes >>> it easy to use them to navigate through history (such as Emacs, but >>> certainly others as well). >> >> Because these standards, it is easy to nav

Re: On commit access, patch review, and remaining healthy

Hi Giovanni, Rather than any specific criticism of our workflow, my point was that there are many little things to keep in mind when reviewing patches, and this makes it demanding. I am pretty happy with Guix's rigorous coding standards, and am not suggesting we abandon them. Cheers! :-) Arun

Re: Teams

Hi Guix, I like the idea of teams. And, it's nice to see so many volunteers raise their hands! > * Rust team > Efraim Flashner > Aleksandr Vityazev > Arun Isaac > John Soo > Maxim Cournoyer > Nicolas Goaziou > Tobias Geerinckx-Rice However, I know very little a

Re: On commit access, patch review, and remaining healthy

Hi Ludo, > I can think of two ways to reassure committers: > > 1. By having clear reviewer check lists (you’d do that if you tick all > the boxes, you’re fine); > > 2. By improving automation—nothing new here: if there was a tick that > says “applies without merge conflicts” and an

Re: On commit access, patch review, and remaining healthy

Hi Giovanni, >> Guix has very high coding standards > > Do you think other software distribution do have less high coding > standards? I meant that Guix has very high coding/packaging standards in the following senses: - We prefer to not bundle dependencies. Tracking out bundled dependencies

Re: Mummi wishlist: API using Message-ID

> As long as the script shows it's trying and explains why it takes > time, it should be fine. It could offer a --continue option too :) Yeah, my thoughts exactly. Definitely beats the two-step manual process that we have to endure now.

Re: Move switch-symlinks to (guix build utils)

Hi Maxime, Thanks for the explanation! I am working on a patch. I'll send something soon. Regards, Arun

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

Hi Vagrant, > But there's one nervous-making issue this revealed; maradns embeds a > random number at build time ... allegedly for systems that don't have > /dev/urandom... see > maradns-3.5.0020/deadwood-3.5.0020/src/Makefile.ubuntu2004: > > # Since some systems may not have /dev/urandom (Win

Re: Mummi wishlist: API using Message-ID

> This sounds like it could take quite some time, and the work it performs > is not transactional, so an impatient person cancelling it before > completion could end up with a bunch of “initial” emails without ever > sending the rest of the patches. True. > I think that maybe we should wean mum

Re: On commit access, patch review, and remaining healthy

Hi all, Tooling aside, at least for me, I think there is an important emotional and psychological aspect to patch review. Maybe others share it too. So, I'll speak up. Sometimes, I don't review and commit patches because I feel like I am not qualified to review them, and am afraid of pushing a

Re: Mummi wishlist: API using Message-ID

> Once delpoyed to issues.guix.gnu.org you can visit > > https://issues.guix.gnu.org/msgid/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link This is great news! Using this, we should be able to implement a `mumi send-email' c

Re: Move switch-symlinks to (guix build utils)

> Maybe replace > >(symlink target pivot) > > by (symlink/remove-old target pivot) > > where > > (define (symlink/remove-old target link) > "Make a symbolic link named LINK pointing to TARGET. > If LINK already exists, it will be removed first. > This is not an atomic operation." > (catch

Re: proposal: guix-ment...@gnu.org list/alias

Hi Ricardo, Perhaps I missed something in your email, but I have a question. Is this new guix-mentors mailing list open to all contributions or only to first-time contributions? If there are too many contributions sent to guix-mentors, how do we manage the workload? Regards, Arun

Re: Move switch-symlinks to (guix build utils)

Hi Maxime, > To avoid a world-rebuild, you could for now make a module (guix build > symlinks) or such? An alternative is (gnu build activation), but then > some (guix ...) modules would depend on (gnu ...). I don't really mind waiting for the next core-updates cycle. This problem has been aro

Move switch-symlinks to (guix build utils)

Hi Guix, The switch-symlinks function from (guix utils) is often required in activation-service G-expressions. But, only (guix build utils) and not (guix utils) is available to such G-expressions. See, for example, the pcscd-activation G-expression in (gnu services security-token) where switch-s

Re: Cuirass and SQL

Hi Ludo, > Years before, Hydra (https://nixos.org/hydra) also dropped its SQLite > backend in favor of PostgreSQL only. > > Like you, not being a database person, I liked that SQLite was easy to > deploy and had a clear model: it just touches this one file and that’s > it. Exactly! :-) If we u

Re: Arun Isaac Presentation on guix-forge this Saturday

Hi Ludo, > This is really nice. I like the idea of having easy deployment through > a Guix service, and of composing existing tools. (It’d even be worth a > blog post, hint hint ;-)) He he, I'm getting the hint! ;-) Maybe, I'll write a blog post when guix-forge is a little bit more featureful

Re: Cuirass and SQL

> For simplicity in a single-system deployment I recommend running > postgres in "trust" mode and listen on a local unix socket rather than > exposing it to the network. This allows you to use the same access > control for Postgres that you'd use for an sqlite3 db file: file > permissions. This

Re: Cuirass and SQL

Hi zimoun, > Initially, Cuirass was using SQLite but then switched [1] to > PostgreSQL. The main reason is scalability. Ah, I see. I didn't know that. > I do not know if it is a technically doable to have two SQL backends and > let the user pick the one they prefer. For sure, it is not doabl

Re: Arun Isaac Presentation on guix-forge this Saturday

Hi Olivier, > Right. Postgresql makes sens for huge CI like ci.guix.gnu.org I guess. > However it would indeed be nice to have the option to select sqlite as > the DBMS. Exactly! > Maybe the solution would be to use a object-relational mapper and > generate the schemas on the fly depending on

Re: Arun Isaac Presentation on guix-forge this Saturday

Hi Olivier, > Tell me, does Laminar check for channels update like cuirass? The main > feature I like about cuirass is that if any dependencies of a package is > updated, it will rebuild my package. If it does support that, I will > seriously consider switching to guix-forge for my project. S

Re: Arun Isaac Presentation on guix-forge this Saturday

Hi all, Thanks for giving me this opportunity to present guix-forge. In particular, I wish to thank both jgart and Pjotr. guix-forge owes its existence to their encouragement. guix-forge is a Guix service that, ambitiously, tries to reproduce a sourcehut, GitHub or GitLab like code forge, but u

Re: Arun Isaac Presentation on guix-forge this Saturday

Hi Olivier, > Quick question about guix-forge. Why laminar instead of cuirass as > the CI? Two reasons: - Cuirass requires a PostgreSQL database, but I wanted guix-forge to be as stateless as possible and definitely not require a complex database server like PostgreSQL. Laminar just uses

Re: Mumi, public-inbox and tools

Hi Ludo, > The attached super-early-draft ‘guix review’ script fetches mboxes from > mumi—that part is OK. I like the idea! But, could we put this in mumi instead of guix? That way, other packages that use debbugs/mumi (skribilo comes to mind), can benefit from it as well. Something like $ gui

  1   2   3   4   >