Re: Farewell to the Change-Id: trailer

Cayetano Santos writes: >>> What is the standard procedure in codeberg land to travel from a commit >>> to its corresponding pr ? Same for the other way round. >> >> I do not believe there is a way to do that in our model when the changes >> are merged manually due to GPG signing. >> >> At least

Re: Farewell to the Change-Id: trailer

Cayetano Santos writes: >>ven. 01 août 2025 at 15:02, Maxim Cournoyer wrote: > >> Hello, >> >> I'm proposing to remove the automatically added Change-Id git trailers >> to our commit messages, for reasons explained in the commit message of >> the commit at

Re: Merge conflict in etc/git/gitconfig leads to unusable git commands

Hello Maxim, Maxim Cournoyer writes: >> so, in guix repository we include ../etc/git/gitconfig in the >> .git/config. I get the motivation for that, but I wanted to raise a >> down side that I encountered today. I have fetched the upstream Guix >> and went on to merge the updates, but got a me

Merge conflict in etc/git/gitconfig leads to unusable git commands

Hi, so, in guix repository we include ../etc/git/gitconfig in the .git/config. I get the motivation for that, but I wanted to raise a down side that I encountered today. I have fetched the upstream Guix and went on to merge the updates, but got a merge conflict, in the etc/git/gitconfig file. T

Re: GitHub hash mismatch?

Noé Lopez writes: > [..] > > So… I have no idea what happened. I would check SoftwareHeritage to see > if they have evidence of a version from that time but it does not load > today. Git tags are not immutable. So the most likely explanation is that the upstream made a git tag for 1.2.0, later

Re: Thoughts on setting a minimum requirement for committing changes, and the contribution model in general.

Andreas Enge writes: > Am Sun, Jul 13, 2025 at 10:14:16PM + schrieb Attila Lendvai: >> this is somewhat tangential, but guix is the first project in my entire >> programmer career where it's not only allowed to commit changes that will >> break >> things, but it's straight out demanded (the

Re: Branches and other updates

Hi Andreas, Andreas Enge writes: > [..] > > This should not be confounded with a merge train. If I understand it > correctly, a merge train of n commits consists in letting the ci system > run in parallel all 2^n-1 combinations of including a commit or not; > then out of the succeeding runs, it

Re: Revisiting the "ChangeLog" style.

Hi, the commit style did grow on me over the time, but I do not have particularly strong opinion either way. Just wanted to react to few things. Liam Hupfer writes: > [..] > > The commit message’s purpose isn’t to enable people to avoid reading the > diff; that’s an impossible goal. It’s to co

Re: Sunsetting of guix-commits mailing list?

Maxim Cournoyer writes: > Mark H Weaver writes: [..] >> >> I looked at your earlier reply to Tomas, and the gitea pull request that >> you linked to. I didn't see any comments there addressing the potential >> issue that Tomas raised. Apologies if I missed it. >> >> To clarify, the issue is

Re: Sunsetting of guix-commits mailing list?

Hi, Maxim Cournoyer writes: > Hi, > > Attila Lendvai writes: > >>> I personally find the mailing list useful for getting quick overview of >>> what is happening and whether there is something interesting I should >>> pull. >> >> >> i think RSS readers serve that usecase better. codeberg see

Re: Sunsetting of guix-commits mailing list?

Hi Maxim, Maxim Cournoyer writes: > After cleaning my mailbox recently, I've noticed that guix-commits was > very heavy on disk usage, with translation commits weighing upward of 10 > MiB often, and with large topic branch rebases being notified as well, > for the complete series of rebased comm

Re: System without GDM [was: GNOME 49’s dependencies on systemd]

Hi, Andreas Enge writes: > a somewhat tangential question, since in any case Gnome is an important > part of our system: Can we make it easier for a user to get rid of > everything Gnome? > > Personally I chose the XFCE desktop (but might also be happy with > others, such as KDE or LXQT), but I

Re: Extra commits pushed on Savannah

Noé Lopez via "Development of GNU Guix and the GNU System distribution." writes: > Hi everyone, > > There are four extra commits that were pushed on Savannah and not > Codeberg: > > ad8cb7af8f * savannah/master gnu: openscad: Update to 2025.06.01. This one does not build (at least per IRC and th

Re: Alternative way to manage configurations

Maxim Cournoyer writes: > Sergey Trofimov writes: > >> Hi Guix, >> >> I'd like to raise concerns about Guix's current approach to software >> configuration management. Configuration schemas are inherently public >> interfaces >> of software, valid only for specific package versions. Currently,

Re: Codeberg migration check list

Overall sounds good, one suggestion though. Ludovic Courtès writes: > - [ ] Git repository imported *Sunday* I think before the import, you should remove write permissions from everyone (except you), to make sure people do not push to savannah by mistake. Sorry if that was already planned

Re: Preparing for Git repository migration

Ludovic Courtès writes: > Hello, > > Efraim Flashner writes: > >> Can we also ask the Savannah admins to change the cgit clone URIs for >> the repos that have been moved over? > > Is it feasible? I would think that Cgit has those hardcoded, no? Looking at cgitrc(5), I think it should be possib

Re: github updater doesn't behave well when "releases" have been abandonned

Efraim Flashner writes: > I suppose if a project had releases but didn't tag the releases in the > git repo then the github updater would be preferable, but that's the > only example I can think of where we'd necessarily need the github > updater. Is that scenario even possible? Looking at the

Re: Regarding removal of the rottlog-service-type

Ludovic Courtès writes: > [..] > > Expiry is expressed as a duration. I’m skeptical about expressing it as > a number of files. > > One thing we could do is make #:expiry a procedure taking a file name > and returning its expiry. I have to admit I just do not fully get the thought process behin

Re: Regarding removal of the rottlog-service-type

Ludovic Courtès writes: > Hi Tomas, > > Tomas Volf <~@wolfsden.cz> writes: > >> --8<---cut here---start->8--- >> Warning: The Rottlog service presented here is deprecated in favor >> of ‘log-rotation-servic

Re: guix shell --container from Shepherd to run a service

Hello Attila, Attila Lendvai writes: > dear Guix, > > my ultimate goal is to run Home Assistant (a python based service) from > Shepherd. > > packaging it seems to be too much effort, so i looked into running it in a > `guix shell --container`. it works fine when done from the terminal: > > $

Re: Please don't leave GNU

Hi, responding to just few points. "pelzflorian (Florian Pelz)" writes: >> Guix has several drawbacks that, while trivial, make it worse than >> Fedora Silverblue: >> >> * Guix asks for my LUKS password twice > > Not sure of the current situation, but this was because GNU GRUB lacked > support

Regarding removal of the rottlog-service-type

Hi, I am currently trying to configure my home server and I have finally got to the log management part. I will probably end up having to use the rottlog-service-type instead of the log-rotation-service-type (due to limitations of the latter), however in documentation I see the following: --8<--

Re: Some thoughts about the documentation

"Thomas Ieong" writes: > [..] > > can /boot be stored unencrypted? I am pretty sure that is possible. > Why do we need to type our password 2-3 times to unlock our computer? We do not need to do that. For over a year. Tomas -- There are only two hard things in Computer Science: cache inval

Re: Reliable way to get directory of current guile script

Hi, first let me have a meta comment. Your client seems to embed \r characters (0x0D, CR) into your emails. Not sure if that is intentional. reza writes: > Hi Guix > > I have problems of finding a reliable way to access the current > directory from a guile script. > > My setup is the foll

Re: [GCD] Rename “main” branch

Vivien Kraus writes: > Hello! > > Le samedi 15 février 2025 à 09:42 +0100, Liliana Marie Prikler a > écrit : >> Recent versions of Git support arbitrary initial branches and the >> default >> branch name is subject to change upstream, at least in part because >> the >> current default — “master”

Re: [GCD] Rename “main” branch

On February 15, 2025 10:26:53 AM GMT+01:00, Simon Tournier wrote: >Hi Liliana, all, > >On Sat, 15 Feb 2025 at 09:42, Liliana Marie Prikler > wrote: > >> sponsors: > >Please note that this thread is not for discussing the proposal but for >looking for Sponsor. :-) So, ugh, people started to disc

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

Tomas Volf <~@wolfsden.cz> writes: > Liliana Marie Prikler writes: > >> Note that these steps are really not that different from moving Guix to >> Codeberg (you have to update %default-channel-url). Since users have >> to update either way, it's better to

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

Liliana Marie Prikler writes: > Note that these steps are really not that different from moving Guix to > Codeberg (you have to update %default-channel-url). Since users have > to update either way, it's better to do both at once than just one at a > time. For users running from a git checkout

Re: Discussion with Codeberg volunteers

Simon Tournier writes: > Especially when it becomes so “easy” (familiar) to click on a button for > forking. Without counting on the “wish-to” effect: I would like to > contribute and even if I will never do it, I start to fork in case. While on GitHub and GitLab forks can effectively live fore

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

Simon Tournier writes: > Hi, > > On Sun, 09 Feb 2025 at 12:43, Tomas Volf <~@wolfsden.cz> wrote: > >>> Maybe this is semantic nitpicking, but people who are able to merge are >>> effectively committers, if only potentially limited to some parts of &g

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

Ludovic Courtès writes: > The Savannah `guix.git` repository would become a mirror of the one at > Codeberg, with a script periodically updating it, as a way to ease > migration to the new repository for users. Will the mirroring ensure that the guix-commits mailing list still works? I find it

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

Hartmut Goebel writes: > Am 10.02.25 um 21:38 schrieb Ludovic Courtès: >> I support it as well¹ but I think we’d rather address it separately. > > I'm in favor of changing the name of the main branch in one go when switching > to > Codeberg. > > Rational: People need to touch their setup anyway

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

Ian Eure writes: > Hi 45mg, > > 45mg <45mg.wri...@gmail.com> writes: > There are many possible consequences of this. One is that GCDs like this one would be seen by fewer people, so there would be less useful discussion and feedback. And in general, people outside of a small c

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

Andreas Enge writes: > Am Sat, Feb 08, 2025 at 05:43:20PM +0100 schrieb Ludovic Courtès: >> I gave the example of Nixpkgs, where package maintainers, who are not >> necessarily committers, can trigger merges for some changes that touch >> their packages and that pass a number of tests. > > Maybe

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

I mostly agree with your wider points, however couple of nitpicks below. 45mg <45mg.wri...@gmail.com> writes: > [..] > > For those of us without the werewithal to self-host our email on our own > hardware (which includes me, and I would assume the majority of us, > despite the overall power-user

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

reza writes: > To access the email lists on savannah you%d > provide an email address and a password, to create an account on%d > codeberg you provide exactly the same information. For participating in the email lists (both bug reports and patch submissions), you only need to send an email. You

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

Sorry for second email, few more comments and questions. Ludovic Courtès writes: > ## Choice of a Forge > > The software behind the forge has to be free software that is > *plausibly* self-hosted on Guix System—this probably rules out GitLab > Community Edition I am curious about this. GitLab

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

Ludovic Courtès writes: > [..] > > Anyway, the proposal is about migrating repositories, issues, and > patches to Codeberg. You’ll find the rationale, plan, and open issues > in the attached draft. I already found two “sponsors” for the proposal > (meaning they agree with the general direction

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

Leo Famulari writes: > On Tue, Jan 28, 2025 at 03:33:26PM +0100, Ludovic Courtès wrote: >> title: Migrating repositories, issues, and patches to Codeberg >> id: 002 >> status: draft > > I support this proposal, in general, in its draft state. > > I'm very interested to hear about any discussions

Re: Non-committers can't keep authenticated forks updated

Liliana Marie Prikler writes: >> All of these things discussed in this thread are technically >> possible. But I think that we all agree that the friction involved, >> compared to just using my own fork with the patch applied, is much >> larger, at least in my opinion. > Yes, we can agree that t

Re: Non-committers can't keep authenticated forks updated

Saturanya Rahjane de Lasca writes: >> Again, not disputing that things work fine for people with commit >> access. Perhaps that is part of why this issue hasn't been addressed >> before :P > You may call us privileged – and yes, we are – but that doesn't change > the fact that weakening security

Re: Non-committers can't keep authenticated forks updated

Liliana Marie Prikler writes: > [..] > >> Then there is anything modifying any of the guix commands.  #74832 is >> over month old, and as far as I know, I am not able to fix guix-copy >> from a channel.  #72928 took over a month to merge, and again, not >> sure how to patch guix-describe from a c

Re: Non-committers can't keep authenticated forks updated

Ricardo Wurmus writes: > Liliana Marie Prikler writes: > >>> This has the slight issue that I can no longer easily answer a >>> question "is this commit in my fork", since I cannot search by the >>> commit hash. I admit it is not a question I need to answer often >>> (last time was on 21st of Oc

Re: Non-committers can't keep authenticated forks updated

Liliana Marie Prikler writes: > I think you're making this more complicated than it needs to be. > checkout, authenticate, rebase*, merge* ought to have you covered. > > * you can authenticate after these if you're paranoid > >> We could create a script to do all the steps for us, but if and wh

Re: 03/11: reconfigure: Support loading the system for kexec reboot.

Ludovic Courtès writes: Hello :) > Hi, > > Tomas Volf <~@wolfsden.cz> skribis: > >> thank you for this series, it looks quite useful, however couple of >> questions about this commit are below. :) > > For me privately? If not, feel free to share m

Re: handling package tests requiring root?

45mg <45mg.wri...@gmail.com> writes: > The only approach I'm aware of is to just ignore such tests. Examples of > this I've seen: > > mdadm: > https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/linux.scm#n5943 > borg: > https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/backup.

Re: Docs: Clarify use-cases of `guix-for-channels`?

Hi, 45mg <45mg.wri...@gmail.com> writes: > Hi Tomas, > > I finally understand that it's my use of `guix-for-channels` that's > making it pull when I reconfigure. So, my issue is solved by removing > the `(guix)` field from the `(guix-configuration)` form in the > configuration I posted. > > All I

Re: Why does `system reconfigure` need to `pull`?

Hello, 45mg <45mg.wri...@gmail.com> writes: > [..] > > As I suspected, the issue does not show up until you add additional > channels in your configuration file - in the case of the configuration > below, that means adding the `my-channels` definition and the > `modify-services` form. When you r

Re: mirrors of main guix repository at savannah

Felix Lechner via "Development of GNU Guix and the GNU System distribution." writes: > Hi Cayetano, > > On Wed, Dec 18 2024, Cayetano Santos wrote: > >> (more or less) official mirrors for main guix repo at savannah ? > > I maintain a lazy mirror on Codeberg. [1] The effort is manual because > Co

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Well, since the thread was revived anyway... Ludovic Courtès writes: > Hi again! > > Over the years, consensus emerged that ‘core-updates’, as a branch where > we lump together all sorts of rebuild-the-world changes, is no longer > sustainable. So, uh, how should I sent patches for that? Befo

Re: On the quest for a new release model

Suhail Singh writes: > Tomas Volf <~@wolfsden.cz> writes: > >> I would like to point out that there is more work involved than just >> splitting it into separate channels and adding those into >> %default-channels. > > Could you please elaborate? Or were th

Re: No ibus modules for GTK4 with Sway

Hi Ricardo, Ricardo Wurmus writes: > Hi Guix, > > I've reconfigured my system with Sway and I noticed that GTK4 > applications now ignore my input method. GTK3 applications and Emacs > still work fine. > > GTK4 applications used to work with IBus under Gnome, so I'm guessing > that some more c

Re: On the quest for a new release model

Suhail Singh writes: > Simon Josefsson via "Development of GNU Guix and the GNU System > distribution." writes: > >> can we strip away almost all of the packages and still have a minimal >> bootable system? If we minimize that set of really-core packages, >> maybe there can be one team that wor

Regarding the vertical alignment in the record definitions

Hello Guix, I would like to bring up for debate the convention the project has of vertically aligning the record definitions. While I agree it lead to visually pleasing code, I also leads to significantly bloated diffs. While some amount of noise in diffs is expected in any lisp language (the t

Re: TTY auto-login broken

Hi, Christian Miller writes: > Hello, > > this is how I configured my system: > > (modify-services %desktop-services > (delete gdm-service-type) > (mingetty-service-type config => > (mingetty-configuration > (inherit config) > (auto-login "cm") > ;; TODO: Work around to

Re: Guix (and Guile's) promise, and how to (hopefully) get there

Since we are putting personal anecdotes onto the pile... spacecadet writes: >> The main turn-off people cite to me is our association with GNU. As a >> particularly poignant case study, in conversations with someone who >> has contributed significantly to Guix on my recommendation and did >> not

Are there any polices on author field of the commit?

Hello Guix, when looking into the git log of Guix, in particular author field of many commits, I noticed that some commits have an author in the form of: --8<---cut here---start->8--- Igor Goryachev via Guix-patches via --8<---cut here

Re: 01/04: gnu: libtorrent-rasterbar: Update to 2.0.10.

Hello John, John Kehayias writes: > Dear Tomas (and CC'ing the debbugs number, co-author, and committer Z572), > > On Sun, Oct 06, 2024 at 07:52 PM, Tomas Volf wrote: > >> guix-comm...@gnu.org writes: >> >>> z572 pushed a commit to branch master

Re: 01/04: gnu: libtorrent-rasterbar: Update to 2.0.10.

guix-comm...@gnu.org writes: > z572 pushed a commit to branch master > in repository guix. > > commit 37dede4c4d8c25a786f2a2e2a17ba54b4ba6283f > Author: Adam Faiz via Guix-patches via > AuthorDate: Tue Aug 6 21:07:40 2024 +0800 I have to admit I am not very happy regarding the change in the comm

Re: bug#72686: Impossible to remove all offload machines

Hello, Ian Eure writes: > Disregard this, I continued thinking after sending the email (as one does) and > realized that any managed file will be a link into the store -- so if the > system > is reconfigured with no build-machines or channels *and* the corresponding > file > is a store link,

Re: ‘core-updates’ merged! 🎉

Ludovic Courtès writes: Hi! > Hello Guix! > > I rebased and applied ‘core-updates’ on top of ‘master’ minutes ago with > commit b8327cb31199fb9f4ebed6c53a59601d41def5a1! 🎉 > > Consider contributing translations of the news entry added in that > commit. > > Let’s congratulate everyone involved in

How to cache the result of guix-for-channels?

Hi all, I am finally trying to incorporate `guix-for-channels' into my system configuration and cannot figure out how to make it cache the resulting package. Following snippet illustrates the problem: --8<---cut here---start->8--- /tmp/repro $ cat x.scm (use-

Re: Request for assistance maintaining LibreWolf

Ian Eure writes: >> >> I believe the usual way of doing something like this is via teams (see >> ./etc/teams.scm ). >> > > I’m not sure whether/how well this mechanism works for non-committers. I believe it should. AFAIK pretty much all it does is to automatically add the team members onto CC l

Re: Install the configuring 'guix' into system/root profile

Hi, On 2024-08-14 07:32:34 -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote: > Hi, > > A few months ago, someone (maybe Ludovic) posted here or on Mastodon > about how to install the 'guix' executable that was used to reconfigure > a system into that system'

Re: Need help about guix home "home-run-on-first-login-service-type"

r for `/gnu/store/3szcc1q867q7hrqigsns4xf8bvrc2l5h-home.drv' failed > with exit code 1 > build of /gnu/store/3szcc1q867q7hrqigsns4xf8bvrc2l5h-home.drv failed > View build log at > '/var/log/guix/drvs/3s/zcc1q867q7hrqigsns4xf8bvrc2l5h-home.drv.gz'. > guix home: error: build of > `/gnu/store/3szcc1q867q7hrqigsns4xf8bvrc2l5h-home.drv' failed > > --- end > --- > > > I`m a novice of guix, any big guys can help me? > > > Thank you! Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: Should we document how to detect if build machines are reachable before trying to offload?

On 2024-07-21 16:26:41 +, Vincent Legoll wrote: > Hello, > > On Sun, Jul 21, 2024 at 12:57 PM Ludovic Courtès wrote: > > > I guess this is probably what we should permit: building locally when we > > cannot offload. > > > > Does that make sense? > > > > What about making "build locally" not a

Re: Sustainable funding and maintenance for our infrastructure

On 2024-07-08 18:28:23 +, Vincent Legoll wrote: > Hello, > > On Mon, Jul 8, 2024 at 3:47 PM Vagrant Cascadian wrote: > > > This may be a little wild, but what are the downsides to doing some > > combination of all of the above? > > > > A mixed strategy could reduce ... the upfront cost of buyi

How to invoke shepherd action from shepherd action?

This does work, but the round-trip via separate binary (and the way to figure it out) is hardly elegant. Could someone advice me on how the typical pattern for this should look? Preferably while staying inside Guile (so no invoke). Thanks and have a nice day, Tomas Volf -- There are only two hard thing

Re: Rust-team branch status?

Hello, On 2024-06-27 05:50:02 -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote: > Hi Efraim, > > On Wed, Jun 26 2024, Efraim Flashner wrote: > > > The packages are public but hidden > > Interesting! How does that work, please? I looked at the package > def

Re: Breath, let take a short break :-)

oC violation. The "piling on" part can just be viewed as expression of the fact that many people disagree with you, not a harassment. If you believe any particular message violated CoC, you should report it according to the CoC. That will move it outside of "in *your* opinion it wa

Proposal for removing some serialization limitations of define-configuration

x27; while serializing the `key-file' field via the (new) `record' argument. And it is fully backwards compatible. What do you think? Would these extensions make sense? Thanks for reading and commenting and have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: Did something with format-patch or send-email break?

CC-ing Ludovic as author of the recent guix git authenticate changes. On 2024-06-09 12:19:21 +0200, Tomas Volf wrote: > So, can you please try the usual `./bootstrap && ./configure && make' and > report > back whether it helped? Ha, but there indeed is a bug pr

Re: Did something with format-patch or send-email break?

Hi, On 2024-06-08 17:22:30 -0700, Ian Eure wrote: > I’m not sure of the precise mechanism employed, but I believe that that in the > past, if I ran `git format-patch' and `git send-email', it would send an email > to the right place. There is etc/git/gitconfig in the repository that sets the nece

Re: Autodafe is "production" ready

o help you with your goal? > We do love our guile, so we will probably encourage you > to use some scheme code.  :) > > Richard do you have any advice for Eric in how to "fix or > replace" autotools? > > Ludo, does guix need to do anything to get ready for some > soft

Re: How to write a compute-file producing utf8 output?

On 2024-06-01 15:39:56 +0200, Ludovic Courtès wrote: > Tomas Volf <~@wolfsden.cz> skribis: > > > I am currently struggling when trying to create a computed-file producing > > internationalized content. Simple reproducer is: > > I think you found out in the meanti

How to write a compute-file producing utf8 output?

Hello Guix, I am currently struggling when trying to create a computed-file producing internationalized content. Simple reproducer is: (use-modules (gnu packages base) (guix gexp)) (computed-file "utf8-display" #~(with-output-to-file #$output

Re: branch master updated (2bea3f2562 -> 6745d692d4)

On 2024-05-10 11:28:48 -0400, kiasoc5 wrote: > > Yeah, it's very annoying that I missed these two FIXUP commits :-/ > > > > Seeing that these are the only 2 FIXUP commits on the master branch history > so far, would it make sense to force push and edit the history? Yes, it > would mess up everyone'

Re: The `channels' field of `operating-system' record

On 2024-04-10 17:17:27 +0200, Ludovic Courtès wrote: > Yes, we could change the default to #f: it’s equivalent to > ‘%default-channels’ but wouldn’t cause the undesirable side effect you > experienced. > > Do you want to prepare a patch (or two)? :-) Well it took me approximately forever to get to

Re: Concerns/questions around Software Heritage Archive

r free license (requirement for inclusion into Guix), I am unsure based on what would the removal be demanded. Do you have some specific approach in mind? Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one

Re: The `channels' field of `operating-system' record

On 2024-04-10 17:17:27 +0200, Ludovic Courtès wrote: > Hello, > > Tomas Volf <~@wolfsden.cz> skribis: > > > After ~2 hours of digging I realized this is caused by the changes in > > 883e69cdfd226c8f40b6e3b76ce0740b59857de6. > > > > I see couple of issu

Re: The `channels' field of `operating-system' record

On 2024-04-08 23:06:00 -0500, Nathan Dehnel wrote: > I don't think you're supposed to edit /etc/guix/channels.scm directly, Is this documented anywhere? I used the code for over a year and it worked just fine. I cannot find any instruction to not touch it anywhere in the info manual. > I think

Re: The `channels' field of `operating-system' record

h one could also use the -C flag to > a channels.scm file including the list of channels. The /etc/... one has advantage of applying to all users. Which is nice. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

The `channels' field of `operating-system' record

gic. Would it not be better to default to #f, so that it would do nothing magical out of the box and would be backwards compatible? You could still turn it on by (Somehow? See above.) providing desired value. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science

Re: Backdoor in upstream xz-utils

Hello, On 2024-03-29 13:39:59 -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote: > > Is there a way we can blacklist known bad versions? > > Having said all that, I am not sure Guix is affected. > > On my systems, the 'detect.sh' script shows no referece to l

Re: rewriting history; Was: Concerns/questions around Software Heritage Archive

ou there is a little value in the act of Guix preserving wrong metadata by itself, any history-modifying operation would have quiet large impact on the ecosystem, so that needs to be taken into account as well. And it that light I would say yes, preserving wrong metadata (when viewed from this angl

Re: Guix role in a free society

hout some empirical study is not great, since it is, as you said yourself, just your claim not supported by anything (as far as I can tell). Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: Concerns/questions around Software Heritage Archive

On 2024-03-17 12:53:54 +0100, paul wrote: > only a 35 yrs old white cis boy Could you stop labeling people like this? It makes me feel uncomfortable and not welcomed... T. -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature

Re: Concerns/questions around Software Heritage Archive

On 2024-03-17 00:16:26 +0100, Vivien Kraus wrote: > Hello! > > Le samedi 16 mars 2024 à 17:50 +, Christopher Baines a écrit : > > This is probably worth thinking about as Guix is in a similar > > situation > > regarding publishing source code, and people potentially wanting to > > change histor

Re: Concerns/questions around Software Heritage Archive

On 2024-03-16 12:06:27 -0700, Ian Eure wrote: > > Christopher Baines writes: > > > [[PGP Signed Part:Undecided]] > > > > Ian Eure writes: > > > > > Hi Guixy people, > > > > > > I’d never heard of SWH before I started hacking on Guix last fall, > > > and > > > it struck me as rather a good idea.

Re: Concerns/questions around Software Heritage Archive

s fetching them by commit hash. At least as far as I know. Since that commit hash does contain the author field, what is the proposed solution here to change the author name without changing the commit hash? While I am not a huge fan of the ability to map the "fake" author name over th

Re: You're invited to the first patch review session!

On 2024-03-06 11:36:29 +, Etienne B. Roesch wrote: > That's the link I have https://meet.jit.si/london-guix-meetup Great, thank you very much, looking forward to tomorrow. :) Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

Re: You're invited to the first patch review session!

efore the link would be shared somewhere, so please take this as a reminder (since it is tomorrow already). Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: You're invited to the first patch review session!

ince meetup.com is a commercial, third-party service, I assume there is not anything you can do about that, so I am curious if there are any alternatives how to get into the review session. Thank you and have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: On the road to the next release: testing the installer

key slot, to make the unlocking faster. Or, just use the key file unlock and enter password just once (albeit it would be the qwerty one). Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: Guix Days: Patch flow discussion

ed to 2. and it worked well, so I prefer that approach now. I agree there is no issue for new packages nor new services, I should have clarified that in my original message. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and of

Re: Guix Days: Patch flow discussion

t workflow model can forks use (e.g. merge not being possible if the fork should be authenticated), maintaining non-package modifications for longer periods of time can be a hassle. So it could be beneficial to put some though into that as well. Tomas Volf -- There are only two hard thi

Re: Guix Days: Patch flow discussion

't work effectively..." case). Or, to put it in a different way: The problem is not that too few patches get merged. The problem is that too few patches get reviewed. Have a nice day, Tomas Volf -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. signature.asc Description: PGP signature

Re: Symlinks in "guix pack" and "guix shell"

-rw-r--r-- 1 wolf users 32 Jan 29 11:14 group -rw--- 1 wolf users 20 Jan 29 11:14 hosts -rw-r--r-- 1 wolf users 92 Jan 29 11:14 passwd lrwxrwxrwx 1 wolf users 59 Jan 29 11:14 ssl -> /gnu/store/s0mdc10pkb9kcmnzjfywax1d42rm4car-profile/etc/ssl Could you please share some

Re: How to always keep build tree when run guix build.

On 2024-01-17 16:21:05 +0800, Adam Faiz wrote: > Hello, > > > Hello: > > > > How to always keep build tree when run guix build, at the moment, I > > use --keep-failed, but it will remove build tree when build success, the > > problem is that build success alway not right build success :-), I n

Re: Golang check phase skipping some tests?

t isn't, because it looks like we > are skipping a lot of tests during the check phase. However, I might > also simply be overlooking something here as I am new to packaging > Golang with Guix. I tend to agree (on both accounts). I am not aware of anything Guix specific here that wo

  1   2   >