unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 43501@debbugs.gnu.org
Subject: bug#43501: gst-plugins-bad cannot be built on linux-armhf
Date: Thu, 24 Sep 2020 00:41:33 -0400	[thread overview]
Message-ID: <87pn6bvlaa.fsf_-_@gmail.com> (raw)
In-Reply-To: <87k0wmy1v1.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 21 Sep 2020 22:36:02 -0400")

retitle 43501 new-title gst-plugins-bad fails to build on armhf-linux
quit

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello Mark!
>
> Mark H Weaver <mhw@netris.org> writes:
>
>> Earlier, I wrote:
>>> Ever since 'spice-gtk' was added, it has included *every* gstreamer
>>> plugin package in its 'propagated-inputs'.
>>
>> On my private branch, I removed 'gst-libav', 'gst-plugins-bad' and
>> 'gst-plugins-ugly' from the propagated-inputs of 'spice-gtk'.
>>
>> diff --git a/gnu/packages/spice.scm b/gnu/packages/spice.scm
>> index 4aff8dbf56..4b4c673a9d 100644
>> --- a/gnu/packages/spice.scm
>> +++ b/gnu/packages/spice.scm
>> @@ -144,11 +144,8 @@ which allows users to view a desktop computing environment.")
>>      (build-system gnu-build-system)
>>      (propagated-inputs
>>        `(("gstreamer" ,gstreamer)
>> -        ("gst-libav" ,gst-libav)
>
> I feel less strongly about this one, perhaps because its name doesn't
> contain "bad" or "ugly" ;-).  Why should we remove it?
>
>>          ("gst-plugins-base" ,gst-plugins-base)
>>          ("gst-plugins-good" ,gst-plugins-good)
>> -        ("gst-plugins-bad" ,gst-plugins-bad)
>> -        ("gst-plugins-ugly" ,gst-plugins-ugly)
>>          ("spice-protocol" ,spice-protocol)
>

> I agree philosophically, but I feel we need more testing of the spice
> part, to know what we're loosing, if we're loosing anything.  I'll try
> rebuilding qemu with this patch and test gnome-boxes, which must make
> use of spice-gtk.

I've now done so, and could run a foreign distribution that I had
already installed without any perceived difference.

I've pushed this as 035df987f1.  Editing the title to reflect the fact
that QEMU is no longer affected by this problem.

Thanks!

Maxim




  reply	other threads:[~2020-09-24  4:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  1:45 bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu Maxim Cournoyer
2020-09-19  3:40 ` Mark H Weaver
2020-09-19 14:24   ` bug#43501: Whitelisting/blacklisting transitive package dependencies Danny Milosavljevic
2020-09-20 22:00   ` bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu Mark H Weaver
2020-09-22  2:36     ` Maxim Cournoyer
2020-09-24  4:41       ` Maxim Cournoyer [this message]
2020-09-26 18:57         ` bug#43501: gst-plugins-bad cannot be built on linux-armhf Mark H Weaver

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=87pn6bvlaa.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=43501@debbugs.gnu.org \
    --cc=mhw@netris.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).