unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Tanguy LE CARROUR <tanguy@bioneland.org>,
	Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Notes from discussion on Quality Assurance from the 10 Years of Guix event
Date: Wed, 19 Oct 2022 11:57:15 +0200	[thread overview]
Message-ID: <86edv4p24k.fsf@gmail.com> (raw)
In-Reply-To: <166610995881.29629.5985110023514931507@localhost>

Hi Tanguy,

On Tue, 18 Oct 2022 at 18:19, Tanguy LE CARROUR <tanguy@bioneland.org> wrote:

> ```console
> $ guix package -I | awk '{print $1}' | tr '\n' ' ' | xargs guix refresh 2>&1 | ag -v "already" | ag -v "failed" | ag -v "no updater" | ag -v "warning"
> ```
>
> Yeah, I know… ugly! But, it does (part of) the job! 😎

Well, if you are using a manifest file, you can directly pass it to
’guix refresh‘.  Otherwise,

    guix package --export-manifest > /tmp/my-pkgs.scm
    guix refresh -m /tmp/my-pkgs.scm 2>&1 | ...

And even, being in a checkout of Guix,

    guix refresh -m /tmp/my-pkgs.scm --update

and then give a look at the script etc/committer.scm.


Cheers,
simon




  reply	other threads:[~2022-10-19 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 15:55 Notes from discussion on Quality Assurance from the 10 Years of Guix event Christopher Baines
2022-10-05 14:01 ` Tanguy LE CARROUR
2022-10-05 16:51   ` Christopher Baines
2022-10-09 15:58     ` Tanguy LE CARROUR
2022-10-18 16:19   ` Tanguy LE CARROUR
2022-10-19  9:57     ` zimoun [this message]
2022-10-23 15:40       ` Tanguy LE CARROUR
2022-10-24  7:34         ` zimoun
2022-10-24 11:43           ` Tanguy LE CARROUR
2022-10-23 21:33       ` kiasoc5
2022-10-19 19:31     ` Efraim Flashner
2022-10-23 15:48       ` Tanguy LE CARROUR
2022-10-24  7:44         ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=86edv4p24k.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    --cc=tanguy@bioneland.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).