From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 29106@debbugs.gnu.org
Subject: bug#29106: Build loop after changing pulseaudio and emacs-ido-completing-read+
Date: Wed, 29 Nov 2017 17:43:57 +0100 [thread overview]
Message-ID: <87shcxqble.fsf@gnu.org> (raw)
In-Reply-To: <87lgip3d6i.fsf@gmail.com> (Oleg Pykhalov's message of "Wed, 29 Nov 2017 07:45:57 +0300")
Hi Oleg,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Ping!
>>> Also, is the “build loop” you mentioned fixed with this patch?
>
> Sorry, I don't see any patches attached.
See <https://bugs.gnu.org/29106> (the issue we’re talking about.) There
you submitted an emacs-ido-completing-read+ patch¹, and it isn’t clear
to me how it relates to the initial problem you reported.
¹ https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29106#8
> I still have never ending pulseaudio derivation build if I add
> ("python-pyqt" ,python-pyqt) to the inputs field.
OK, I suppose that’s because python-pyqt indirectly depends on
pulseaudio (currently Guix doesn’t try to detect cycles around
derivations, which is why you get this “never-ending” behavior.)
The usual approach to break such cycles is by having a “-minimal”
variant of one of the packages in the loop.
Would it work for you?
Thanks,
Ludo’.
prev parent reply other threads:[~2017-11-29 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 14:40 bug#29106: Build loop after changing pulseaudio and emacs-ido-completing-read+ Oleg Pykhalov
2017-11-01 14:47 ` Oleg Pykhalov
2017-11-05 16:07 ` Ludovic Courtès
2017-11-24 17:26 ` Ludovic Courtès
2017-11-29 4:45 ` Oleg Pykhalov
2017-11-29 16:43 ` Ludovic Courtès [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
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=87shcxqble.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29106@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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).