all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 74291-done@debbugs.gnu.org, Steve George <steve@futurile.net>
Subject: bug#74291: [Website patch] Announcing the Guix user survey - blog post
Date: Mon, 11 Nov 2024 09:14:36 +0000	[thread overview]
Message-ID: <87ed3irv2b.fsf@cbaines.net> (raw)
In-Reply-To: <87zfm7mblb.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Sun, 10 Nov 2024 15:01:52 +0100")

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:

> Steve George <steve@futurile.net> writes:
>> Attached is a blog post for the Guix blog. Can someone add it for me please?
>
> If someone adds this:
>
> Could the person adding the blog post also do a pull+reconfigure?
>
> Presumably the website updates are still blocked until the website
> server (is that bayfront?) gets reconfigured, because Guix commit
> e99f7b8abcfab260fafcb353cbd6904c0e3aafb7 made an incompatible change
> that broke the website, therefore I pushed to guix-artwork a fix
> ce25c1ad7c0db77c729b1821b295c5aea021a959, but my fix breaks when the
> server does not yet have
> e99f7b8abcfab260fafcb353cbd6904c0e3aafb7.

I've pushed the blog post to guix-artwork now. I also reconfigured
bayfront yesterday with commit aa2ccd6350caa094519c41f547f1d0fa68ab29ac.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

      reply	other threads:[~2024-11-11  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 12:00 [bug#74291] [Website patch] Announcing the Guix user survey - blog post Steve George
2024-11-10 14:01 ` pelzflorian (Florian Pelz)
2024-11-11  9:14   ` Christopher Baines [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed3irv2b.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=74291-done@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    --cc=steve@futurile.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.