all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gabriel Wicki <gabriel@erlikon.ch>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: 67273@debbugs.gnu.org
Subject: [bug#67273] [PATCH gnome-team 3/5] gnu: sratom: Update to 0.6.16.
Date: Wed, 29 Nov 2023 14:19:21 +0100	[thread overview]
Message-ID: <vf2xiohj4dadvb2oexkxswc73fma222bnc25yepeez2kc4wjpf@de2cd6waonj5> (raw)
In-Reply-To: <87h6l4q1fp.fsf@iscas.ac.cn>

Hi!

Thanks for the explanation!

So the patch set should be changed in order - i can confirm that all
packages now build just fine!

They generally look good to me, except for one question:  is it
impossible to patch the sources so we wouldn't need to propagate more
inputs?  Otherwise all seems fine.


So, if you could re-send your patchset with
 - the correct order,
 - $(guix style) ran on all the packages,
 - and maybe less input propagation (if possible)

that'd be great!

Thanks for your time and effort!





  parent reply	other threads:[~2023-11-29 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19 10:03 [bug#67273] [PATCH gnome-team 0/5] update lilv and its dependency Zheng Junjie
2023-11-19 10:07 ` [bug#67273] [PATCH gnome-team 1/5] gnu: zix: Update to 0.4.2 Zheng Junjie
2023-11-19 10:07 ` [bug#67273] [PATCH gnome-team 2/5] gnu: sord: Update to 0.16.16 Zheng Junjie
2023-11-19 10:07 ` [bug#67273] [PATCH gnome-team 3/5] gnu: sratom: Update to 0.6.16 Zheng Junjie
     [not found]   ` <uoxjxcye2wagwty7ly7wkh4kkq53dmbrv56ed54a53e7lnzldu@bq4wbvnsfqfo>
     [not found]     ` <87h6l4q1fp.fsf@iscas.ac.cn>
2023-11-29 13:19       ` Gabriel Wicki [this message]
2023-11-19 10:07 ` [bug#67273] [PATCH gnome-team 4/5] gnu: lv2: Update to 1.18.10 Zheng Junjie
2023-11-19 10:07 ` [bug#67273] [PATCH gnome-team 5/5] gnu: lilv: Update to 0.24.22 Zheng Junjie
2024-03-30 14:27 ` bug#67273: close Zheng Junjie

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=vf2xiohj4dadvb2oexkxswc73fma222bnc25yepeez2kc4wjpf@de2cd6waonj5 \
    --to=gabriel@erlikon.ch \
    --cc=67273@debbugs.gnu.org \
    --cc=zhengjunjie@iscas.ac.cn \
    /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.