unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andy Tai <atai@atai.org>
To: help-guix@gnu.org
Subject: build broken packages handling
Date: Mon, 29 Mar 2021 13:02:37 -0700	[thread overview]
Message-ID: <CAJsg1E_jFL74hUoyMwJfjYv=5qv==jVwijmOpp2d0D=8PVTapA@mail.gmail.com> (raw)

Two questions:

1.  When submitting an updated package definition, is there an easy
way to check if other packages may be broken by this update?   Right
now it is easy to check if a package builds with updated package
definition; but it is not easy to see if committing it will break
others.

2. If a package is not building in guix, should a bug be filed against
it?  Ot there is a way, a CI web interface or something that shows all
existing packages whose builds are broken?

Thanks

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


             reply	other threads:[~2021-03-29 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 20:02 Andy Tai [this message]
2021-03-30  2:45 ` build broken packages handling Julien Lepiller

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='CAJsg1E_jFL74hUoyMwJfjYv=5qv==jVwijmOpp2d0D=8PVTapA@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=help-guix@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.
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).