all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, 64001@debbugs.gnu.org
Subject: Re: pending mate upgrade patches to 1.26
Date: Mon, 24 Jul 2023 09:28:38 -0700	[thread overview]
Message-ID: <CAJsg1E8VjPWpcmeXKs8mSOvL5Cs=BpfgD+XtS0pkW8YtEQ=Apw@mail.gmail.com> (raw)
In-Reply-To: <ZL4uNd3PZWoSgppI@jurong>

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

Hi, these patches have been merged by Mr. Song (iyzsong@envs.net) . He
worked to get these built without the two extra patches. Thanks

On Mon, Jul 24, 2023 at 12:54 AM Andreas Enge <andreas@enge.fr> wrote:

> Hello Andy,
>
> Am Mon, Jun 26, 2023 at 12:09:41PM -0700 schrieb Andy Tai:
> > The state of them is that there are two prerequisites that have passed
> > Guix QA check:
> > https://issues.guix.gnu.org/64001
>
> I had a quick look at this patch, but am a bit confused. If I read it
> correctly, it updates tzdata (which causes a lot of rebuilds, and without
> updating python-pytz as stipulated by a comment in the code of tzdata),
> and then it creates a new variable tzdata-next which looks to be the same.
>
> Would the good approach not be to update tzdata and python-pytz, and to
> copy the old version into tzdata-for-tests?
>
> It is quite possible I am misunderstanding something, and in any case I
> would like to defer to someone more knowledgeable about the core packages.
>
> Andreas
>
>

-- 
Andy Tai, atai@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat:
andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能

[-- Attachment #2: Type: text/html, Size: 2128 bytes --]

  reply	other threads:[~2023-07-24 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 19:09 pending mate upgrade patches to 1.26 Andy Tai
2023-07-24  7:54 ` [bug#64001] " Andreas Enge
2023-07-24 16:28   ` Andy Tai [this message]
2023-07-24 16:36     ` Andreas Enge

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='CAJsg1E8VjPWpcmeXKs8mSOvL5Cs=BpfgD+XtS0pkW8YtEQ=Apw@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=64001@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /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.