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
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
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
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,
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
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-
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
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'
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
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
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
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
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
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
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
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
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
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
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
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
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'
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
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
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
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
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
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
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
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
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
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
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
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.
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
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.
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
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
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
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
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
'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
-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
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
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
t) in there sadly does not
work.
Not sure, maybe there is a better way. If there is, I hope someone will tell me
(us).
In the mean time, I hope this helps to some degree.
Have a nice day,
Tomas Volf
PS: My understanding it that #:modules is equivalent to (use-modules), that is
why I used
?
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
On 2024-01-11 13:41:39 +0100, Ludovic Courtès wrote:
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > Otherwise the shepherd would be stuck on shutdown waiting for process named
> >
> > [mt76-tx phy0]
> >
> > to terminate with messages along the line
On 2024-01-10 00:33:11 +0100, Ludovic Courtès wrote:
> Hi again Tomas,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > What I tried so far:
> >
> > 1) Asking on the IRC (2x). Once I even got a review, but from a
> > non-committer.
> > 2) Sending
PS:
On 2024-01-10 17:38:17 +0100, Tomas Volf wrote:
> scheme@(guile-user)> ((@@ (shepherd service) pseudo-process?) 688)
The pid is different than above, because this was after a reboot.
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things a
On 2024-01-10 11:23:22 +0100, Ludovic Courtès wrote:
> Hi!
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > However even in that light, I still consider the 3 and 4 to be worth
> > considering. Aaand even without 3, at least doing 4 in some shape or form
> &g
On 2024-01-10 00:34:48 +0100, Ludovic Courtès wrote:
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > On 2024-01-07 15:08:59 +0100, Ludovic Courtès wrote:
>
> [...]
>
> >> ** Do not accidentally wait for Linux kernel thread completion
> >> (<ht
On 2024-01-09 23:49:33 +0100, Ludovic Courtès wrote:
> Hello!
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > As seen in the example above, currently there is a need to manually
> > merge the list of additional modules with the original one. Failing
> >
such as PID 2 (“kthreadd”). This
> situation is now recognized and avoided.
This is great, I will not have to remember to run `modprobe -r mt7921e' before
each shutdown anymore. I hope. Looking forward to getting it in the Guix :)
Have a nice 2024,
Tomas Volf
--
There are only two hard thing
there is a mistake in the patch (code is fine, commit message is
off), and before I spent more time on it, I would like to know if it even makes
sense to send v2. I assume it will just sit in the same void, therefore this
inquiry.
Thank you and have a nice 2024,
Tomas Volf
PS: This patch being
probably
should be something like this (untested):
(or #$home (passwd:dir (getpw (if (and #$home-service? (not #$user))
(getuid) #$user
For your immediate problem, explicitly setting the (home) field in the
syncthing-configuration should help. I think.
Have a nice day,
Tomas Volf
--
There
On 2024-01-04 14:22:48 -0500, Thompson, David wrote:
> On Thu, Jan 4, 2024 at 5:34 AM Tomas Volf <~@wolfsden.cz> wrote:
> >
> > Greetings,
> >
> > I would like to inquire regarding digital-ocean-configuration type used for
> > provisioning DigitalOcean D
t would create Re: ..., properly putting it
into the (already existing) thread.
There might however be a different custom over here, so I am looking forward to
what other people have to say about this.
>
> I use Emacs Rmail if anyone uses the same tool as well.
>
> [0] https://lists.gnu.o
to me?
Thank you and have a nice day,
Tomas Volf
0: https://www.gnu.org/distros/free-distros.html
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
u for considering this proposal, and thank you in advance for
any helpful insight you are willing to provide.
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
On 2023-12-11 20:35:27 -0800, Felix Lechner via Development of GNU Guix and the
GNU System distribution. wrote:
> Hi,
>
> I have my own copy of Guix in order to hack on features. I 'pull' with
> the option '--allow-downgrades'.
>
> After that, 'deploy' does not require it again, but 'home reconfig
On 2023-12-08 10:42:07 +0200, Saku Laesvuori wrote:
> Hi,
>
> I'm planning on refreshing Guix's haskell packages as my fix for
> https://issues.guix.gnu.org/66347 requires rebuilding all of them
> anyway. Should I try to keep commits small with only one update per
> commit (which is more work but m
On 2023-11-28 14:48:05 +0100, Simon Tournier wrote:
> Hi Ludo,
>
> On Thu, 16 Nov 2023 at 15:40, Ludovic Courtès wrote:
>
> > That said, if you become aware of actual breakage, we can revisit this!
>
> The actual breakage is my own interaction with this file. :-)
>
> Again, it happened to me y
On 2023-11-28 14:37:55 +0100, Simon Tournier wrote:
> Hi,
>
> On Mon, 20 Nov 2023 at 14:03, Attila Lendvai wrote:
>
> > TL;DR the filename shouldn't contain the .gz extension, and the HTTP
> > standard is crap ("If no Accept-Encoding field is present in a
> > request, the server MAY assume that
On 2023-11-16 16:23:00 +0100, Ludovic Courtès wrote:
> Hi,
>
> Maxim Cournoyer skribis:
>
> > Felix Lechner writes:
>
> [...]
>
> >> How about a 'remote-user-profile'?
> >
> > 'guix package' is already the command we use to create profiles; maybe
> > it could accept a '--remote' argument to o
On 2023-11-08 15:44:46 -0800, Felix Lechner via Development of GNU Guix and the
GNU System distribution. wrote:
> Hi Felipe,
>
> On Wed, Nov 08 2023, Luis Felipe wrote:
>
> > I'm looking into packaging the current Guix's website theme
> > [...] I think it would be easier for other
> > Guix web
On 2023-11-02 16:38:29 +, Suhail wrote:
> [..]
> --
> Suhail
>
> This email is not an offer capable of acceptance, does not evidence an
> intention to enter into an agreement, has no operative effect until a
> definitive agreement is signed in writing by both parties, and that no
> party shou
On 2023-10-21 17:32:13 +0200, Ricardo Wurmus wrote:
>
> Maxim Cournoyer writes:
>
> > All in all, I guess my position is unchanged: despite the potential for
> > surprises, automating and enforcing these configs provide benefits that
> > outweigh the cons, in my experience/opinion.
>
> I concur
ectory, and now I have the include there (5 times).
I think turning it into a manual step, with the granularity proposed above, is a
good and welcomed solution. At least in my opinion.
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
68 matches
Mail list logo
