imx-base: make gstreamer1.0 packages socarch specific

Submitted by Max Krummenacher on March 7, 2019, 10:33 a.m. | Patch ID: 159394

Details

Message ID 20190307103300.15404-1-max.krummenacher@toradex.com
State New
Headers show

Commit Message

Max Krummenacher March 7, 2019, 10:33 a.m.
gstreamer and its plugins have been forked for i.MX. So all of the generated
packages should have their PACKAGE_ARCH set to SOCARCH.

Prevents, when building gstreamer for an i.MX machine followed by a non i.MX
machine:

| ERROR: gstreamer1.0-1.14.4-r0 do_packagedata_setscene: QA Issue: Package version for package gstreamer1.0 went backwards which would break package feeds from (0:1.14.imx-r0 to 0:1.14.4-r0) [version-going-backwards]
| and many more for each generated package

Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
 conf/machine/include/imx-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch hide | download patch | download mbox

diff --git a/conf/machine/include/imx-base.inc b/conf/machine/include/imx-base.inc
index 9b7cae97..44fed8b2 100644
--- a/conf/machine/include/imx-base.inc
+++ b/conf/machine/include/imx-base.inc
@@ -140,7 +140,7 @@  MACHINE_SOCARCH_FILTER_append_imxgpu = " \
     virtual/libopenvg \
     libdrm \
     cairo \
-    gstreamer1.0-plugins-bad \
+    gstreamer1.0 \
     libgal-imx \
     pango \
 "

Comments

Otavio Salvador March 18, 2019, 10:44 a.m.
Hello Max,

On Thu, Mar 7, 2019 at 7:34 AM Max Krummenacher <max.oss.09@gmail.com> wrote:
>
> gstreamer and its plugins have been forked for i.MX. So all of the generated
> packages should have their PACKAGE_ARCH set to SOCARCH.
>
> Prevents, when building gstreamer for an i.MX machine followed by a non i.MX
> machine:
>
> | ERROR: gstreamer1.0-1.14.4-r0 do_packagedata_setscene: QA Issue: Package version for package gstreamer1.0 went backwards which would break package feeds from (0:1.14.imx-r0 to 0:1.14.4-r0) [version-going-backwards]
> | and many more for each generated package
>
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>

Could you cook a PR on github for us?
Max Krummenacher March 23, 2019, 1:30 p.m.
Hi Otavio

Am Montag, 18. März 2019 schrieb Otavio Salvador <
otavio.salvador@ossystems.com.br>:
> Hello Max,
>
> On Thu, Mar 7, 2019 at 7:34 AM Max Krummenacher <max.oss.09@gmail.com>
wrote:
>>
>> gstreamer and its plugins have been forked for i.MX. So all of the
generated
>> packages should have their PACKAGE_ARCH set to SOCARCH.
>>
>> Prevents, when building gstreamer for an i.MX machine followed by a non
i.MX
>> machine:
>>
>> | ERROR: gstreamer1.0-1.14.4-r0 do_packagedata_setscene: QA Issue:
Package version for package gstreamer1.0 went backwards which would break
package feeds from (0:1.14.imx-r0 to 0:1.14.4-r0) [version-going-backwards]
>> | and many more for each generated package
>>
>> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
>
> Could you cook a PR on github for us?

Sorry for the delay, I have been offline for the last week and a bit IT
handycapped the next week. Will send a pull request beginning of April.

Shouldn't we change tbe layers README if PR is the now prefered method to
propose changes?

Regards,
Max
Otavio Salvador March 27, 2019, 2:17 p.m.
On Sat, Mar 23, 2019 at 10:31 AM Max Krummenacher <max.oss.09@gmail.com> wrote:
> Am Montag, 18. März 2019 schrieb Otavio Salvador <otavio.salvador@ossystems.com.br>:
> > Hello Max,
> >
> > On Thu, Mar 7, 2019 at 7:34 AM Max Krummenacher <max.oss.09@gmail.com> wrote:
> >>
> >> gstreamer and its plugins have been forked for i.MX. So all of the generated
> >> packages should have their PACKAGE_ARCH set to SOCARCH.
> >>
> >> Prevents, when building gstreamer for an i.MX machine followed by a non i.MX
> >> machine:
> >>
> >> | ERROR: gstreamer1.0-1.14.4-r0 do_packagedata_setscene: QA Issue: Package version for package gstreamer1.0 went backwards which would break package feeds from (0:1.14.imx-r0 to 0:1.14.4-r0) [version-going-backwards]
> >> | and many more for each generated package
> >>
> >> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> >
> > Could you cook a PR on github for us?
>
> Sorry for the delay, I have been offline for the last week and a bit IT handycapped the next week. Will send a pull request beginning of April.

I applied it myself.

> Shouldn't we change tbe layers README if PR is the now prefered method to propose changes?

Please send one for it.